Database Users

Ota 1.47.651.1 pulled

OTA 1.47.651.1 has been pulled as it is bricking some phones. Sprint has a internal notice floating around but I just figured that I should post this incase anyone was wondering.

Thank you for posting this. I was following the forums all day to see how the OTA was affecting rooted and non-rooted. It's ironic (and very unfortunate) that most stock users are getting bricked. Sprint not off to a good start with the EVO.

LOL much like the Hero.
I updated after monitoring, having only previously ran unrEVOked for wifi tether. Lucky for me, all is well.

Sprint is honestly not just off to a bad start with this phone, they're pretty much off to an awful start with it. Can't keep stock, can't replenish stock, bricked stock phones after OTA updates.
Not good problems to have.

I would bet it was a very small percentage that was having issues. From what I saw it was the fantom second update that was causing the problems. Anyway, some of the folks who know what to do with it, have it to take apart and use for the good of the rest of us.
Yippi!
-Roger

most non rooted getting bricked. prove it

I'm pretty glad I got mine. Helped my 4g strength somehow. I was dropping and switching back and forth (3g to 4g) and now I have full bars and drops to two bars every now and then. Also, phone works just as perfectly as before. I haven't rooted and won't until all of the kinks are worked out.

awesomeindeed said:
Sprint is honestly not just off to a bad start with this phone, they're pretty much off to an awful start with it. Can't keep stock, can't replenish stock, bricked stock phones after OTA updates.
Not good problems to have.
Click to expand...
Click to collapse
Not keeping stock is not really a bad thing for Sprint. They're just selling a ton of Evo's. And I don't think it's Sprint's fault for not getting new devices in (more likely HTC or the manufacturers) and the OTA is from HTC. Sprint would be fine if HTC could get their act together, although most of the problems are few and far between.

Is the update file available somewhere? It's still legit. I had the option to update today at work but signal was bad so I waited until I got home. By then the update got pulled and I no longer had the update option. I'd like to get the new update on my phone since I heard it improves battery life considerably.
My money is that the phone bricking was a result of non-patient users who didn't let the update finish and/or those who blindly hit "accept" without doing the slightest amount of reading (like checking the version number vs. what they already have on the phone).... ie. Those who ran the update twice.

No root, no problems. I updated when it first came out. Haven't noticed anything different.
Sent from my PC36100 using XDA App

awesomeindeed; said:
Sprint is honestly not just off to a bad start with this phone, they're pretty much off to an awful start with it. Can't keep stock, can't replenish stock, bricked stock phones after OTA updates.
Not good problems to have.
Click to expand...
Click to collapse
Not being able to keep your product in stock because the demand is so high I would say is a pretty good problem to have.

It would be great if they posted a link for a download. Palm would always put their updates on they website for download. Can any body get it from their build who downloaded it?

evoxsin said:
It would be great if they posted a link for a download. Palm would always put their updates on they website for download. Can any body get it from their build who downloaded it?
Click to expand...
Click to collapse
Here's a better version that will allow you to keep unrevoked's root:
http://unrevoked.com/rootwiki/doku.php/public/evo_ota_2_patch

ericmcintire said:
Here's a better version that will allow you to keep unrevoked's root:
http://unrevoked.com/rootwiki/doku.php/public/evo_ota_2_patch
Click to expand...
Click to collapse
But what to download? I was referring to the official ota unpatched version. Also I'm uncertain how to boot the zip. The unpatched version is posted in the xda development section. But im lost on how to load the zip. Sorry I'm completely new to android. I'm a long palm user.

gthing said:
Not being able to keep your product in stock because the demand is so high I would say is a pretty good problem to have.
Click to expand...
Click to collapse
not when the consumer has other great options available. you can potentially lose sales to competitors.

ericmcintire said:
Here's a better version that will allow you to keep unrevoked's root:
http://unrevoked.com/rootwiki/doku.php/public/evo_ota_2_patch
Click to expand...
Click to collapse
this is apparently corrupted. see the original thread in the development section.

madsquabbles said:
not when the consumer has other great options available. you can potentially lose sales to competitors.
Click to expand...
Click to collapse
Considering iPhone 4s are sold out for the next few weeks (lines outside local AT&T / Apple stores for the second round of preorders this morning)...
And I imagine the same will be true for Verizon when it drops the Droid X...
All the "hot" phones are pretty much currently sold out.

motorola razr M prototype?

hi everyone, so i recently saw motorola razr m. the thing is, it had motorola markings on it like it is some kind of prototype or test device. it was running jellybean. just the markings were a bit curious, if someone can shed some light on what it was. thanks !

mikeverne said:
hi everyone, so i recently bought a second hand motorola razr m. the thing is, it has motorola markings on it like it is some kind of prototype or test device. it works totally fine, gsm unlocked and its running jellybean. everything runs as it should, just the markings are a bit curious. ive attached a pic to see if someone can shed some light on what it is. thanks !
Click to expand...
Click to collapse
Seems kinda fishy lol
https://forums.motorola.com/posts/0dc68e3f0d?commentId=716757#716757

Somber73 said:
Seems kinda fishy lol
https://forums.motorola.com/posts/0dc68e3f0d?commentId=716757#716757
Click to expand...
Click to collapse
yea i saw that too. but that doesn't really tell me anything apart from the fact that other phones like mine were also sold(which i already knew).

It would be best to just drop the subject. You have something rare, and if you want to keep it, I would keep it quiet. The guys on the Motorola forum are launching a pretty big investigation into this. I would delete your pic and edit your OP. Don't get me wrong, I DO NOT condone illegal activity, but there is a reason these are out in the open...

Regardless of the circumstances surrounding where or how he got the phone, there ought to be someplace where this guy can get answers as to its origin or what it is exactly without everybody overreacting.
Sent from my XT907 using xda app-developers app

It is an Engineering model device and it will have a fully unlocked bootloader Status 1 when you boot into AP Fastboot mode from the boot menu.
It will also have engineering firmware with userdebug testkeys builds unless it was flashed by prior owner to stock or a custom build.
These are very valuable devices to a developer because they can run any firmware, including the engineering bootloaders and radio images, which cannot be run even on devices with unlocked bootloaders via exploit or the official Development edition devices, all of which have a Status 3 bootloader.
The good news is you can run any firmware you like safely on them, but you must flash them manually and you can't run any OTA updates until you do so because they will fail signatures and checksums on engineering builds.
There is also usually a lot of debugging binaries and apps and monitoring components on these builds that you want to disable generally.
It's a great opportunity, but comes with some greater responsibility.
The official forum, as noted above, is an extremely poor place to get this kind of information and is basically useless, as you discovered.
More of these devices have been showing up lately and I have seen several posts by confused users like yourself regarding such phones.
Consider yourself lucky and start learning how to take advantage of your rare device!

It would seem, especially from the reaction by Motorola, that it is indeed an internal phone. I'm guessing they want the IMEI so they can take someone's head off.
I doubt Motorola would go after any end users, they didn't seem too mad at the guy who posted there. Someone inside will probably not be happy after that investigation though
Sent from my XT907 using Tapatalk 4 Beta

cellzealot said:
It is an Engineering model device and it will have a fully unlocked bootloader Status 1 when you boot into AP Fastboot mode from the boot menu.
It will also have engineering firmware with userdebug testkeys builds unless it was flashed by prior owner to stock or a custom build.
These are very valuable devices to a developer because they can run any firmware, including the engineering bootloaders and radio images, which cannot be run even on devices with unlocked bootloaders via exploit or the official Development edition devices, all of which have a Status 3 bootloader.
The good news is you can run any firmware you like safely on them, but you must flash them manually and you can't run any OTA updates until you do so because they will fail signatures and checksums on engineering builds.
There is also usually a lot of debugging binaries and apps and monitoring components on these builds that you want to disable generally.
It's a great opportunity, but comes with some greater responsibility.
The official forum, as noted above, is an extremely poor place to get this kind of information and is basically useless, as you discovered.
More of these devices have been showing up lately and I have seen several posts by confused users like yourself regarding such phones.
Consider yourself lucky and start learning how to take advantage of your rare device!
Click to expand...
Click to collapse
thank you! and btw, that wasn't me who posted in the official forums lol. thats the lase place i would think of posting if i had a prototype haha.
sloosecannon said:
It would seem, especially from the reaction by Motorola, that it is indeed an internal phone. I'm guessing they want the IMEI so they can take someone's head off.
I doubt Motorola would go after any end users, they didn't seem too mad at the guy who posted there. Someone inside will probably not be happy after that investigation though
Sent from my XT907 using Tapatalk 4 Beta
Click to expand...
Click to collapse
thank you! and yea, i agree.

that convo on the motorola forum is hilarious!
buyer claimed he got it from someone he does not know that placed an ad on pakistani forum.

jco23 said:
that convo on the motorola forum is hilarious!
buyer claimed he got it from someone he does not know that placed an ad on pakistani forum.
Click to expand...
Click to collapse
uh, actually im pretty sure he is telling the truth. its sort of a Pakistani craigslist.

RSD is proprietary software, owned by Motorola. While I know it's very easy to find online, it's not intended for public use. The rules of this site forbid discussion of software installation or use unless that software is distributed by Motorola or one of its partners.
That pretty much sums it up. Had he come to xda, he'd have gotten help. He didn't seem too open to helping the Motorola guys out though, so they didn't help him. Don't see why he would lie about that, he's just a poor guy who wants his confidential Motorola property to work for him... By asking the people that someone stole it from... Yeah...
Sent from my XT907 using Tapatalk 4 Beta

guys, i am going to buy a similar "confidential" razr m phone. what do you suggest? is this going to cause software issues like installing new roms or gapps?

dasche said:
guys, i am going to buy a similar "confidential" razr m phone. what do you suggest? is this going to cause software issues like installing new roms or gapps?
Click to expand...
Click to collapse
Nope. Since it's factory unlocked, you should be able to install TWRP and go about flashing whatever you want. It might be a wiser choice to buy a regular handset, since you want have Motorola property all over the front.

[XT1053] [5.0.2] Lollipop Soak Test Download

Here is a download for the 5.0.2 soak test from Motorola for XT1053 devices. I have not tried this yet, I received this from a friend who reported it successfully working on his device.
I do not take responsibility if this file bricks, destroys, or sets fire to your phone. Use this at your own risk. I have not tested this file, therefore I cannot confirm that it works.
If you do venture to try this, please report back.
[Someone has already posted this on the other thread, removed]

[MOD EDIT:]SHAME SHAME SHAME. Signing an NDA means you're agreeing to not share details of the special program you are in.
This has been removed at the request of Motorola due to your negligence in violating the terms of your agreement.
[DARKTERMIT EDIT:]I'm not signed NDA
Screenshots
Click to expand...
Click to collapse
i smell this

habusho said:
i smell this
Click to expand...
Click to collapse
It's likely coming. But at least I'm not breaking the NDA, my friend is. Probably won't matter. I'm getting it out while I can.

Bigluc said:
It's likely coming. But at least I'm not breaking the NDA, my friend is. Probably won't matter. I'm getting it out while I can.
Click to expand...
Click to collapse
Nothing good will come out of this, please remove it. The ones installing this will likely have issues further updating.
Just wait a few more days (after 4 months a few days seem like nothing).

alexferdean said:
Nothing good will come out of this, please remove it. The ones installing this will likely have issues further updating.
Just wait a few more days (after 4 months a few days seem like nothing).
Click to expand...
Click to collapse
how exactly is patching a factory zip update complicating future updates?

DrDecoy said:
how exactly is patching a factory zip update complicating future updates?
Click to expand...
Click to collapse
The OTA updates, including soak/beta or whatever you want to call pre-release received via the Moto Feedback Network, and those pushed by the carriers, have pre-flash validation checks in them.
They check for certain things in build.prop, particular files (and checks their hash/check sum), etc. IF your phone doesn't match, the OTA wont install. In addition, with the OTA's and these leaked ZIPs including updates to GPT.BIN and the bootloader, and history showing how easy it is to brick trying to downgrade when those are involved, that could complicate trying to get back on track should Moto or the Carriers push something else out.
A while back, I think it was the Droid X, there were leaked updates, people were flashing them, they were not meant to be released and the people who installed them got STUCK unable to update for a while. It was a while ago, so my memory is fuzzy, but a process was finally found, but it took a while, and a few updates, to bring those people back in line. And it was a little more difficult due to locked bootloaders.
So practicing a little caution is a good thing.

Bigluc said:
It's likely coming. But at least I'm not breaking the NDA, my friend is. Probably won't matter. I'm getting it out while I can.
Click to expand...
Click to collapse
Nice way to justify leaking stolen software. Always amusing to see wanna-be devs pirating someone else's work and somehow justifying it to themselves.

KidJoe,
One person can update his bootloader, others supplied with system partition backups don't have to. Deployed Android doesn't require updated motoboot, or secure things. You know what I mean...
But hey, it's illegal, firstly. And secondly, let's not spoil Motorola good intentions to bring us the latest Android, and quickly. Sooon )

Can you post a link to the new post with the file?

s5610 said:
KidJoe,
One person can update his bootloader, others supplied with system partition backups don't have to. Deployed Android doesn't require updated motoboot, or secure things. You know what I mean...
But hey, it's illegal, firstly. And secondly, let's not spoil Motorola good intentions to bring us the latest Android, and quickly. Sooon )
Click to expand...
Click to collapse
Quickly is not the right word when it has being months of LP being out.

sorullo_xgrx said:
Quickly is not the right word when it has being months of LP being out.
Click to expand...
Click to collapse
I'm with Motorola on this one.
You should see s4 after lollipop update.
The battery gives Hardly 1 hour of screen time.
It has rendered the phone unusable.
At least we are getting a reasonably stable update.
Also getting features from new flagship.
Who does that

DrDecoy said:
how exactly is patching a factory zip update complicating future updates?
Click to expand...
Click to collapse
Besides other things the bootloader gets updated. It's not so easy to go back to 4.4.4.

s5610 said:
KidJoe,
One person can update his bootloader, others supplied with system partition backups don't have to. Deployed Android doesn't require updated motoboot, or secure things. You know what I mean...
But hey, it's illegal, firstly. And secondly, let's not spoil Motorola good intentions to bring us the latest Android, and quickly. Sooon )
Click to expand...
Click to collapse
Actaully, based on history with the 2013 X...
That doesn't always work right. i.e. When it was found that 4.4.2 broke MotoWpNoMo and SlapMyMoto, some tried upgrading by flashing only PARTS of the 4.4.2 rom (so they could roll back).. They ran into features not working, like App Drawer -> Settings -> Security.
We've seen other issues arise when partially flashing too, but they were a while back so my memory is a little fuzzy on the specific details.

I flashed it days ago.... My phone is fine

needleyepoke said:
I flashed it days ago.... My phone is fine
Click to expand...
Click to collapse
Quick question are you on T-Mobile. Do you have the 4g LTE or just 4g on the status bar?

sorullo_xgrx said:
Quick question are you on T-Mobile. Do you have the 4g LTE or just 4g on the status bar?
Click to expand...
Click to collapse
I'm on T-Mobile with the xt1053 and no I do not have the LTE signal BUT I do have LTE when looking in phone settings... I've heard everyone saying the same thing

needleyepoke said:
I'm on T-Mobile with the xt1053 and no I do not have the LTE signal BUT I do have LTE when looking in phone settings... I've heard everyone saying the same thing
Click to expand...
Click to collapse
Yeah same here, I wonder if moto remove the LTE on lollipop but since is just a soak test it not yet implemented , thanks

So are you thinking that after the soak test we will get another update?
---------- Post added at 02:57 PM ---------- Previous post was at 02:55 PM ----------
My nexus 5 has it don't know why they wouldn't have it in the moto..I guess it really doesn't bother me as much as not having 5.0

sorullo_xgrx said:
Quick question are you on T-Mobile. Do you have the 4g LTE or just 4g on the status bar?
Click to expand...
Click to collapse
I have TMo and the XT1053 and I'm only showing 4G but with LTE speeds. I saw a screenshot on here of someone with what appears to be a special T-Mobile build of the Lollipop soak test with LTE in the signal bars though.

Razgriz said:
I have TMo and the XT1053 and I'm only showing 4G but with LTE speeds. I saw a screenshot on here of someone with what appears to be a special T-Mobile build of the Lollipop soak test with LTE in the signal bars though.
Click to expand...
Click to collapse
Probably the actual update and not the first soak test that went live a week ago...
---------- Post added at 03:34 PM ---------- Previous post was at 03:32 PM ----------
Man I hate the day lenovo bought motorola, it just felt updates were not gonna be the same.

Shield Kill Switch

Hi figured we could use our own separate thread to discuss the killswitch Nvidia supposedly put in place on our old Shield tablets and see what has worked for those who have received their replacement units. If you've gotten a replacement please share if your old unit has been destroyed or not...if not please let others know what the old tablet has on it or what you did to attempt to prevent the brick! Thanks for helping us all out here!

As I said in the other thread, I received my new one, and my old one is still usable on rooted latest stock, unlocked bootloader, with the only app missing being Chrome for some reason. Nothing else disabled or uninstalled. Maybe they haven't turned on the server that sends the kill signal yet.

If the company wants the other device back (dunno if that is true), why keep it? You are breaking a deal while making it less appeling for companies to do this type of thing...+its a saftey risk for you and others around you.

Nvidia said they do not need it back
ManualG on the Nvidia forum said they are not requiring you send it back
"We don't require you to send it back to us to receive the replacement and are collecting them only to make it less of a burden on everyone else who dont have drop off locations like that close by." So you can keep it if you want ?

16 gig tablet, got it this morning. My original is still functional, it was stock rom, rooted with xposed on it. That's as much modding as I've done with mine.

does anyone have more informations about this killswitch?
Is it a service that needs to be deactivated or deleted or a kernel feature?
I just want to make sure it doesn't kill my old tablet when I set up the new one.
Alternatively, I could just flash an older factory image or custom firmware.

From what I've read on other forums (i.e. reddit) most have indicated that the killswitch is embedded in the bootloader and will activated on the defective tablet once the replacement tablet is registered on the nvidia side. I of course cannot confirm for this to be the case but just sharing what others have reported.

yea but it must communicate with the server then and that only works when Android is booted up and all communication drivers loaded.
So there must be another service running in Android that gives this information to the bootloader to kill itself.

If it's bootloader based, flash a bootloader from one of the older recovery images.

Will try that. BL from Update 2.2.2 should be fine?
actually if I flash it back to 2.2.2 it should be fine too since the changes to 3.X aren't that big

That should work just fine.

big time noob question but where are you getting the old bootloaders from to flash?

Until somebody's tablet gets deactivated and a log is captured during the deactivation process, everything said here or anywhere else is just speculation.

bluegizmo83 is right, however the discussion has to start somewhere so kudos to the OP for getting this thread started.

chicodelta said:
bluegizmo83 is right, however the discussion has to start somewhere so kudos to the OP for getting this thread started.
Click to expand...
Click to collapse
Oh I completely agree. I'm all for conversion. But I don't want people to get the wrong impression, like trying to flash an older bootloader. That may stop the deactivation, but it also may not. Its only speculation at this point.

bluegizmo83 said:
Oh I completely agree. I'm all for conversion. But I don't want people to get the wrong impression, like trying to flash an older bootloader. That may stop the deactivation, but it also may not. Its only speculation at this point.
Click to expand...
Click to collapse
Well said. I apologize if my post came through as a solution. I was only mentioning that as folks had mentioned a possible bootloader lock.

Any thoughts on whether flashing CM would serve as a way to circumvent the killswitch? I see that release for this tablet is already available http://forum.xda-developers.com/shi...-cyanogenmod-12-shield-tablet-lte-na-t3055043. Thoughts?

scorpionx said:
Well said. I apologize if my post came through as a solution. I was only mentioning that as folks had mentioned a possible bootloader lock.
Click to expand...
Click to collapse
No problem. As I said, I'm all for the discussion, I just wanted to make it clear to everyone that its all just speculation at this point.

I think the old bootloaders are in the old full OTA's someone correct me if I'm wrong. You can also extract them from the full OTA

chicodelta said:
Any thoughts on whether flashing CM would serve as a way to circumvent the killswitch? I see that release for this tablet is already available http://forum.xda-developers.com/shi...-cyanogenmod-12-shield-tablet-lte-na-t3055043. Thoughts?
Click to expand...
Click to collapse
To me, this is the most logical place to start at this point! Maybe it works, maybe it doesn't, but unlocking the bootloader, rooting, and installing a custom rom seem like a good starting place. If the stock devices are definitely getting wiped anyways, any changes we make now can't hurt the chances of keeping it alive!

Motorola Droid Turbo gets soak test prior to Android 6.0 Update!

http://www.phonearena.com/news/Moto...soak-test-prior-to-Android-6.0-update_id87282
The Update is official and is coming soon!!
Horaaay

Sparksys said:
http://www.phonearena.com/news/Moto...soak-test-prior-to-Android-6.0-update_id87282
The Update is official and is coming soon!!
Horaaay
Click to expand...
Click to collapse
end of the line for updates. but i love my xt1254, 2 years old and smokes most newer phones. out performs almost everything i think pff and at 21mp i can record much better amature porn lol

How much time this soak test will take?

hmm.
I SURE HOPE NOBODY LEAKS THE ROM FROM THE SOAK TEST somehow.

We don't know for sure this is 6.0, do we? There's nothing in the picture that indicates that it's 6.0. For all we know it might be another patch to stop Sunshine.

Which would really be an insult. We (VZ) can't give you OS and security updates but we darn well try to be sure you don't update your phone yourself.
FrostedWaffle said:
We don't know for sure this is 6.0, do we? There's nothing in the picture that indicates that it's 6.0. For all we know it might be another patch to stop Sunshine.
Click to expand...
Click to collapse

y8s said:
hmm.
I SURE HOPE NOBODY LEAKS THE ROM FROM THE SOAK TEST somehow.
Click to expand...
Click to collapse
Very subtle /sarcasm

I am rather counting on it. I have RR 6.0.1 and love it. It is fast, stable and has cool features. However the official build with VoLTE would have merit. I am sure it is just a matter of time.
y8s said:
hmm.
I SURE HOPE NOBODY LEAKS THE ROM FROM THE SOAK TEST somehow.
Click to expand...
Click to collapse

y8s said:
hmm.
I SURE HOPE NOBODY LEAKS THE ROM FROM THE SOAK TEST somehow.
Click to expand...
Click to collapse
Someone needs to be the guinea pig to see whether it relocks, the bootloader.

Einsteindks said:
Someone needs to be the guinea pig to see whether it relocks, the bootloader.
Click to expand...
Click to collapse
No one needs be the guinea pig, but someone does need to look at the update script to see if a bootloader relock command is in it. Betcha it isn't.

TheSt33v said:
No one needs be the guinea pig, but someone does need to look at the update script to see if a bootloader relock command is in it. Betcha it isn't.
Click to expand...
Click to collapse
This is Verizon we're talking about. Wouldn't surprise me if it does relock.

Cobra04 said:
This is Verizon we're talking about. Wouldn't surprise me if it does relock.
Click to expand...
Click to collapse
Judging from the threads of what happened to the phones of people who tried to do that, it would result in a ton of warranty claims. Verizon doesn't want that.

TheSt33v said:
Judging from the threads of what happened to the phones of people who tried to do that, it would result in a ton of warranty claims. Verizon doesn't want that.
Click to expand...
Click to collapse
Right. The potential downside is far larger than any gain to Verizon from relocking the bootloader.
They WILL probably lock down the phone from the Sunshine exploit with the new update, and probably they'll lock it down for good this time. So if you want to unlock your phone, do it before the next update.

quadcrap1 said:
Right. The potential downside is far larger than any gain to Verizon from relocking the bootloader.
They WILL probably lock down the phone from the Sunshine exploit with the new update, and probably they'll lock it down for good this time. So if you want to unlock your phone, do it before the next update.
Click to expand...
Click to collapse
while i completely agree, it would be funny if Lenovo *actually, for once fixed* what Motorola used to do. in this scenario, they should open the floodgates, and just allow unlock for all turbos bl for everyone. Two years later, i am sure there are few, if any, still retaining warranty and stuck on contract.
limit the time that you agree to keep phones bootloader locked. and always, always, always give the 1% of the 1% of users the option to buy a dev edition.
back to the point, it would cost them more money to write that into the update for the sake of us 1%ers, so i dont see it happening.
time will tell if the turbo is another a855; that phone people cling to for 2-3 years realizing upgrading isnt that necessary. I'm ready for a new one. but i refuse to buy another non- bootloader unlockable phone EVER. and nothing at all is really impressive at this point. the Axon 7 is awesome. and a maybe. but moto lost it. if they made a 2016 MXPE with an sd 820 better battery and wireless charging and all carriers radios, id pay $600 in a heartbeat. but what do 1%ers know? lol.

kitcostantino said:
while i completely agree, it would be funny if Lenovo *actually, for once fixed* what Motorola used to do. in this scenario, they should open the floodgates, and just allow unlock for all turbos bl for everyone. Two years later, i am sure there are few, if any, still retaining warranty and stuck on contract.
Click to expand...
Click to collapse
They don't give a crap about warranty claims...it's always been about control for Verizon. Used to, it was down to them not wanting people to tether and take advantage of their high/unlimited data caps...since that's been built into Android for several versions now, I'm not sure what their rationale for disallowing unlocks is. Probably to prevent what we're doing; upgrading the software on our more-than-adequate hardware.
They'd rather you lock yourself into a contract and buy one of their new phones, after all. Trying to force you to do so is worth having one of their devs spend an hour or three to port the exploit patch(es) and write a code snippet to lock the bootloader, and not providing an unlock service just saves them money.
As for Lenovorola, they couldn't care less; they've already made any money that they can off of the phones. There's zero incentive for them to help in any way, especially since the phone is over two years old and was designed/produced during the promising-looking period that Google owned Motorola. They, too, would prefer you buy a new phone, perhaps one of their increasingly-generic ones.
So yea...it's still in VZW's best interest to be slightly scummy about the bootloader situation. They'll make more money off spending a bit to continue to (try to) exert their control, rather than caring about what any of their customers want.
-----------
I like this bit at the end of the article:
There is one bit of bad news here for DROID Turbo owners. Since the device is not expected to be updated to Android 7.0, this is the end of the line in terms of Android updates for the model.
Click to expand...
Click to collapse
Considering official MM on Verizon was looking more and more unlikely to materialize, I imagine that most will just shrug their shoulders at this. It's been a given for a long time that the Turbo was hanging on to VZW's upgrade list by its fingernails.

Sweet!

@jcase says he has a copy of Verizon's Marshmallow. It's coming.
He also says it much harder to unlock the bootloader, so best to do it now if you are going to do it.

Hopefully this is another fake soak and they release it concurrently. From what I've heard, a lot of prior moto soaks were put out as otas almost at the same time. As Verizon users, we need that radio for our nougat rom!!!

koftheworld said:
Hopefully this is another fake soak and they release it concurrently. From what I've heard, a lot of prior moto soaks were put out as otas almost at the same time. As Verizon users, we need that radio for our nougat rom!!!
Click to expand...
Click to collapse
one of the reasons i quit being a soak tester, it was pointless.

quantum tao said:
one of the reasons i quit being a soak tester, it was pointless.
Click to expand...
Click to collapse
Hehe, Verizon didn't like knowing I was rooted. They dropped me from the program.