Database Users

Boot Loader Lock and alternate ROMs

Hello,
I am pondering the possibility to buy the Samsung Galaxy S II and have heard quite a few rumors that this phone will have a locked and encrypted boot loader making it impossible to use alternative ROMs.
I am sure hackers will take very little time in fixing this but am still wondering. Has anyone seen tangible claims of encrypted/lock boot compared to the I9000 (which I own atm).
Thanks!

Expansys has a 32 gb model listed as coming april 11th but pricing is not yet announced

galaxinho said:
Expansys has a 32 gb model listed as coming april 11th but pricing is not yet announced
Click to expand...
Click to collapse
Yes, no definite date. Doesn't answer my question though

FRLinux said:
Yes, no definite date. Doesn't answer my question though
Click to expand...
Click to collapse
Samsung's own website mentions encryption, but doesn't give enough detail for us to know if it'll be custom ROM friendly yet. I'm sure it'll take very little time once the phone is released to let you know, just hold tight until then!

Ayrlupine said:
Samsung's own website mentions encryption, but doesn't give enough detail for us to know if it'll be custom ROM friendly yet. I'm sure it'll take very little time once the phone is released to let you know, just hold tight until then!
Click to expand...
Click to collapse
Link please?
I suppose you are referring to the data encryption that Samsung mentioned in its splash page? I really doubt they would post information about a Locked Bootloader on their website as it really wouldn't do them any good publicity wise.

sarsh11 said:
Link please?
I suppose you are referring to the data encryption that Samsung mentioned in its splash page? I really doubt they would post information about a Locked Bootloader on their website as it really wouldn't do them any good publicity wise.
Click to expand...
Click to collapse
Yeah, I said encryption. Of course we have no idea about the bootloader until it's released or someone techy gets their hands on one! That's why I said we have to wait. Sorry if my post was ambiguous.

SamFirmware just tweeted, Samsung are using same ODIN for Galaxy S II, just with new .PIT file. So it will be flashable.

Broomfundel said:
SamFirmware just tweeted, Samsung are using same ODIN for Galaxy S II, just with new .PIT file. So it will be flashable.
Click to expand...
Click to collapse
Yes saw that but it doesn't mean it is flashable just like that until you see it working. Good start anyway.

FRLinux said:
Hello,
I am pondering the possibility to buy the Samsung Galaxy S II and have heard quite a few rumors that this phone will have a locked and encrypted boot loader making it impossible to use alternative ROMs.
I am sure hackers will take very little time in fixing this but am still wondering. Has anyone seen tangible claims of encrypted/lock boot compared to the I9000 (which I own atm).
Thanks!
Click to expand...
Click to collapse
There's already a running topic on this question found here.

Beards said:
There's already a running topic on this question found here.
Click to expand...
Click to collapse
Thanks spotted it afterwards.

FRLinux said:
Thanks spotted it afterwards.
Click to expand...
Click to collapse
No problem... Your not the only one who has started a topic and found later it's already running.
That link I passed you is actually a second topic on another which was started a day earlier here.
That means we now have three topics covering the same (although each will fragment as further posts are made).

Everyone has their needs/requirements for a phone but for me-personally to fulfill my individual desires and needs it would need to be unlocked 100%. Otherwise I will jsut have to keep my captivate
As I do not approve of manufacturers locking hardware that I paid for with my hard earned money and now own.

HappyBallz said:
Everyone has their needs/requirements for a phone but for me-personally to fulfill my individual desires and needs it would need to be unlocked 100%. Otherwise I will jsut have to keep my captivate
As I do not approve of manufacturers locking hardware that I paid for with my hard earned money and now own.
Click to expand...
Click to collapse
Seem the norm these days on android handsets but keep in mind that the mobile market has always liked a locked an tight device.
Sent from my GT-I9000 using Tapatalk

SE was from the very few to lock the bootloader with X10 and now they decided to unlock the simfree Arc, HTC locked their Incredible S in another hand
I don't think sammy will lock the bootloader,just a little security for the formalities that can be easily decoded by happy devs

vegetaleb said:
SE was from the very few to lock the bootloader with X10 and now they decided to unlock the simfree Arc, HTC locked their Incredible S in another hand
I don't think sammy will lock the bootloader,just a little security for the formalities that can be easily decoded by happy devs
Click to expand...
Click to collapse
Yes over time there is always a way. But that said, new devices tend to have better boot loader locking.

Has there been any update on whether the S2 have a locked bootloader?

monkley said:
Has there been any update on whether the S2 have a locked bootloader?
Click to expand...
Click to collapse
Search this very forum. Several threads opened about this but only speculations until someone has one and messes with it.

Locked bootloader...
So I see the chat regarding the locked bootloader on the sg2...I also see people on the forum actually have the device...could they some how check and see if it is locked?
I have been going round in circles looking for a new phone...finally decided on the sam sg2 to find out they are going down the same route as moto!
So, to all the happy owners of a shiney new sg2...whats the dealo!?!?!?

owners of the sgs2 in this forum? you must be mistaken lol...
sam locking the bootloader? who told you that nonsense?

they wouldnt dare to lock the bootloader. its 1 of many reason why sgs 1 succeeded as it did.
if they want sgs2 to be a successful device as well they wont lock the bootloader. it makes sense that the bootloader will be UNlocked.. but then again you can never tell... we might be like if we will find out its locked. followed by and then after we will unlock it. leading to

I Don't Believe On The Motorola Promise About That Unlockable Bootloader

hi,
guys, I don't want to dishearten you but did you think a minute about the way motorola will unlock your bootloader in the future update??
as they will release an update.zip like in the past, I'm not really sure if they will include the unlockable bootloader inside it and, not sure also if an android update can flash a bootloader. So I am a little anxious for you guys, mine is already unlocked...

Its unlocked for ever
Sent from my MB860 using Tapatalk

Andrew149 said:
Its unlocked for ever
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
you mean locked!? right? lol

Er, dude you really need to read a little bit more on Development forum D:...
Its already unlocked!
Cheers

tan G said:
hi,
guys, I don't want to dishearten you but did you think a minute about the way motorola will unlock your bootloader in the future update??
as they will release an update.zip like in the past, I'm not really sure if they will include the unlockable bootloader inside it and, not sure also if an android update can flash a bootloader. So I am a little anxious for you guys, mine is already unlocked...
Click to expand...
Click to collapse
Moto said they are going to do it. They already dont it on the leaked future builds, not to mention the one Kenn is running which is an ATT GB. Not to mention this is the same way the did it on the Xoom. Theres nothing to worry about, its unlocked 4 ever.

lol - it's already done.

knigitz said:
lol - it's already done.
Click to expand...
Click to collapse
His point is he thinks its going to be removed from the final build. He states he is already unlocked himself.

LOL Someone needs to read through the forums. Bootloader is unlocked already.

Agree with Jay ... some one needs to read the OP ^_^ LOL
I, maybe just optimistically, think they will. The backlash, *****ing, low sales, the fact they said they would, and the fact that we have it already all points, IMO, to them releasing it. Motorola exec. - "Well the kids already have it so lets release it and make us look good." If they are on our side, at least give us what we want, they sell more. DROID - ground breaking - unlockable - sold like hot cakes. ATRIX - ground breaking - locked - not so much
posted via Atrix in lapdock

Does it really matter? For those that actually want an unlocked bootloader, they can get it in the dev forum. For the average user who will still get the OTA update, they probably didn't care about the bootloader to begin with.

Yaotl said:
Does it really matter? For those that actually want an unlocked bootloader, they can get it in the dev forum. For the average user who will still get the OTA update, they probably didn't care about the bootloader to begin with.
Click to expand...
Click to collapse
yup and average users will not probably bother coming to xda.
@OP
you are 2-3 months late regarding the creation of this topic.

madnav said:
yup and average users will not probably bother coming to xda.
Click to expand...
Click to collapse
I'm guess i'm still an 'average user' when it comes to android, but this is where I came to become a superuser (pun intended). I don't think i'm ready to mess with the HK build yet, but I definitely plan to flash a few ROMs when the official unlocked GB update comes through. And if it gets yanked before the final release, hopefully i'll know enough by then to use kenneth's version, or if worst comes to worst, the HK build.

zoso28 said:
I'm guess i'm still an 'average user' when it comes to android, but this is where I came to become a superuser (pun intended). I don't think i'm ready to mess with the HK build yet, but I definitely plan to flash a few ROMs when the official unlocked GB update comes through. And if it gets yanked before the final release, hopefully i'll know enough by then to use kenneth's version, or if worst comes to worst, the HK build.
Click to expand...
Click to collapse
It's not like the HKTW build is as unstable as the build TBH gave us. The only things that don't work is the front facing camera, and fingerprint sensor.
I just didn't restore from a backup, and you can fix the WebTop. So my phone is running fine, and it seems even more stable than FroYo (Besides the obvious bugs)

tan G said:
hi,
guys, I don't want to dishearten you but did you think a minute about the way motorola will unlock your bootloader in the future update??
as they will release an update.zip like in the past, I'm not really sure if they will include the unlockable bootloader inside it and, not sure also if an android update can flash a bootloader. So I am a little anxious for you guys, mine is already unlocked...
Click to expand...
Click to collapse
It really dose not matter if thay include the unlockable bootloader in every update or not. As long as their is a way for it to be done. Thats all the matters. Really only the N1 could be unlocked without much of any hassle. You just needed to know what commands to run,
Once its unlocked. Its unlocked. Cant go back. And just because you flash back to 1.57 or 1.83 and it no longer says "Unlocked" at the top. It is. All you need to do is flash the pudding and it will put those little words back.

pmcnano said:
Er, dude you really need to read a little bit more on Development forum D:...
Its already unlocked!
Cheers
Click to expand...
Click to collapse
this is not the case for other atrix versions than att

JayRolla said:
Moto said they are going to do it. They already dont it on the leaked future builds, not to mention the one Kenn is running which is an ATT GB. Not to mention this is the same way the did it on the Xoom. Theres nothing to worry about, its unlocked 4 ever.
Click to expand...
Click to collapse
that build is a build for developer and developer devices, there is no garantee that it will be the same for user-end releases, anyway I really hope for all people that you're right.
the sbf used to unlock our phone now (att) has been packed by someone in the dev team may by eval or 2dc... or both

JayRolla said:
His point is he thinks its going to be removed from the final build. He states he is already unlocked himself.
Click to expand...
Click to collapse
thumbs up! that's what I said

I will always have an unlocked bootloader

tan G said:
thumbs up! that's what I said
Click to expand...
Click to collapse
tang no matter what update motorola does in the future they wont be able to take away the unlock already created. with that said this post is useless, and a mod should close it, this will give the wrong idea to anyone coming to the forum looking for the unlock. who knows what motorola will bring in the future, fact remains, is unlocked and it aint going back.
"Pandora dosnt go back in the box man - he only comes out!!!!"

Dont feed the troll!!!!!!

Debunking the Atrix Myths!

1.Bootloader!
The bootloader of the atrix CANNOT be relocked after it is unlocked! Yes, I know if you flash a stock SBF file the "Unlocked" text will be gone, but it is not relocked!
Explanation/Elaboration: When you flash the pudding file, what you are flashing is a bootloader. When you key in oem unlock ******, you BLOW a fuse. Non-reversible. Hardware based, not software. So, when the 'pudding' bootloader runs, it sees the burnt fuse and knows the phone is unlocked, thus printing the "unlocked" text. When you flash back to stock, the stock bootloader doesn't even care about that fuse, and WILL NOT skip signature check in fastboot aka locked.
This WILL NOT REVERT your phone back to stock, the stock bootloader just doesn't care if you are unlocked or not. Motorola can easily check if your phone is unlocked, but USUALLY will not. DO NOT BLAME ME IF THEY DO FOR YOU! Now, stop going around saying "my phone can be relocked" =)
2. Hard brick
If you OTA to Gingerbread, and downgrade back to FroYo, you WILL get a HARD BRICK! Also, updating to v4.5.141 and than unlocking the bootloader will also cause a hard brick!
Explanation/Elaboration: Yes, it the damn fuses again When you update to Gingerbread you will BLOW a fuse in ReservedOdm[1]. If you downgrade to FroYo, you will get an Error "SVF:105:1:2" Mainly what that means is that at the lower part of the Odm[1] called 105, the bootloader expects the fuse to be '1' but found out its actually '2'. It then refuses to boot, sending the phone into NvFlash mode, which we cannot use as we require a SBK from moto.
Reference:Thanks eval-!
3.Xoom ICS release
The release of ICS for the Motorola Xoom does not help in any major way to the development of ICS on the Atrix.
Explanation/Elaboration: Yes, we do need the ICS kernel for Tegra 2. Yes, the Xoom uses Tegra 2. No, they are not the same. The atrix uses the Tegra 250 AP20H while the Xoom uses the Tegra 250 T20. Yes, the one on the Atrix is slower, but more importantly, different! (Thanks live4nyy!)
4.Carrier Unlocking the Atrix (NOT BOOTLOADER UNLOCK)
This is less of a myth, more of a guide. If you CANNOT unlock the Atrix even with the code provided (I can/will not provide), do NOT keep trying. All you are doing is wasting the number of tries you can try before the phone will not accept any more tries. What you should do is flash to an AT&T rom/radio and try again. This is assuming you want to unlock the AT&T version of the Atrix of course. Once unlocked, the Atrix can be flashed to your hearts content and will not be re-locked. (Thanks Abu-7abash!)
Any other widely mistaken facts about the atrix you want corrected?

Nice, straight forward write-up. Hopefully this helps some of the n00bs get this info through their head

matthew5025 said:
Any other widely mistaken facts about the atrix you want corrected?
Click to expand...
Click to collapse
I got one.
Myth - The Xoom having ICS will help in the development of the Atrix.
Fact - Just because the Xoom is a Tegra 2 device and running ICS does not help (or is very minimal* ) development to the Atrix.
* I don't know the exact details but I'm sure this is the gist of it.

UFOs > Bigfoot

matthew5025 said:
1.Bootloader!
When you flash the pudding file, what you are flashing is a bootloader. When you key in oem unlock ******, you BLOW a fuse. Non-reversible.
Click to expand...
Click to collapse
I'm curious. So this fuse that blows in the phone when flashed, is the only purpose of this fuse is to identify an unlocked phone? Is this fuse added to the phone by Motorola or are they required by the carriers to install these fuses?

stang5150 said:
I'm curious. So this fuse that blows in the phone when flashed, is the only purpose of this fuse is to identify an unlocked phone? Is this fuse added to the phone by Motorola or are they required by the carriers to install these fuses?
Click to expand...
Click to collapse
eFuse is an IBM invention. I posted a lengthy explanation of this a long long time ago after verifying the Atrix was using eFuse technology. When you read eval's explanation it is very accurate, except that you cannot "burn a bit". You could "set a bit" which sends the signal to overload the hardware circuit.
Carrier can specify they want a locked bootloader or not. I believe the method could be up to the manufacturer, but carrier may also specify type of bootloader lock. Of course, manufacturer may have an internal policy that all phones have a locked bootloader, but include provisions for unlocking it.
eFuse does not blow a fuse per se. This implies there is an actual fuse in the phone. eFuse (electronic fuse) is a circuit built into a chip inside the phone. When you unlock the bootloader a very small electrical charge is sent to that circuit and simply overloads it and burns it out. eFuse technology is not solely used for bootloaders. They are in many more electronic devices than you may think. eFuse is both software and hardware based. Software sends the signal, hardware circuit is blown, software checks this circuit on boot-up, when the circuit cannot be completed the software knows this, and reports, in the case of a phone, that the bootloader is unlocked.
Now, that said, this thread just serves as another one for idiots to read and ignore. All the info posted here has already been posted in a hundred other threads. Giving "myths" their own thread will just serve to create more inaccuracies as people post "myths" that they really know nothing about. Who is to say that anything posted here is any more accurate from one person to another? Sorry OP, but "myths" may actually become myths in here.
---------- Post added at 12:31 PM ---------- Previous post was at 12:25 PM ----------
ifalldownalot said:
UFOs > Bigfoot
Click to expand...
Click to collapse
This ^^^^^^^! LOL

matthew5025 said:
2. Hard brick
If you OTA to Gingerbread, and downgrade back to FroYo, you WILL get a HARD BRICK!
Explanation/Elaboration: Yes, it the damn fuses again When you update to Gingerbread you will BLOW a fuse in ReservedOdm[1]. If you downgrade to FroYo, you will get an Error "SVF:105:1:2" Mainly what that means is that at the lower part of the Odm[1] called 105, the bootloader expects the fuse to be '1' but found out its actually '2'. It then refuses to boot, sending the phone into NvFlash mode, which we cannot use as we require a SBK from moto.
Reference:Thanks eval-!
Any other widely mistaken facts about the atrix you want corrected?
Click to expand...
Click to collapse
Well as far as I know UK version is safe to flash back to froyo. I went back from 2.3 to froyo sbf few times myself and few other people confirmed this aswell.
/edit
Never upgraded OTA so my post is useles...nice!

matthew5025 said:
1.Bootloader!
The bootloader of the atrix CANNOT be relocked after it is unlocked! Yes, I know if you flash a stock SBF file the "Unlocked" text will be gone, but it is not relocked!
Explanation/Elaboration: When you flash the pudding file, what you are flashing is a bootloader. When you key in oem unlock ******, you BLOW a fuse. Non-reversible. Hardware based, not software. So, when the 'pudding' bootloader runs, it sees the burnt fuse and knows the phone is unlocked, thus printing the "unlocked" text. When you flash back to stock, the stock bootloader doesn't even care about that fuse, and WILL NOT skip signature check in fastboot aka locked.
This WILL NOT REVERT your phone back to stock, the stock bootloader just doesn't care if you are unlocked or not. Motorola can easily check if your phone is unlocked, but USUALLY will not. DO NOT BLAME ME IF THEY DO FOR YOU! Now, stop going around saying "my phone can be relocked" =)
2. Hard brick
If you OTA to Gingerbread, and downgrade back to FroYo, you WILL get a HARD BRICK!
Explanation/Elaboration: Yes, it the damn fuses again When you update to Gingerbread you will BLOW a fuse in ReservedOdm[1]. If you downgrade to FroYo, you will get an Error "SVF:105:1:2" Mainly what that means is that at the lower part of the Odm[1] called 105, the bootloader expects the fuse to be '1' but found out its actually '2'. It then refuses to boot, sending the phone into NvFlash mode, which we cannot use as we require a SBK from moto.
Reference:Thanks eval-!
Any other widely mistaken facts about the atrix you want corrected?
Click to expand...
Click to collapse
Oem lock ******
Tried?
Sent from my MB860 using XDA App

Hey Matthew, thanks for the info- I am going to Singapore on Sat for the airshow. Are there cool spots out there to get good deals on accessories for our atrix>? LOL

Not only Atrix related but a general fact, when you sim unlock a phone (atrix included) it won't ever get locked again no matter how/what roms you flash.
Sent from my Atrix 4g using Tapatalk

jgc121 said:
Nice, straight forward write-up. Hopefully this helps some of the n00bs get this info through their head
Click to expand...
Click to collapse
Thanks! Its annoying the way they keep repeating the same stuff over and over again isn't it? Drives me up the wall!
live4nyy said:
I got one.
Myth - The Xoom having ICS will help in the development of the Atrix.
Fact - Just because the Xoom is a Tegra 2 device and running ICS does not help (or is very minimal* ) development to the Atrix.
* I don't know the exact details but I'm sure this is the gist of it.
Click to expand...
Click to collapse
Thanks! Will include that point!
CaelanT said:
Now, that said, this thread just serves as another one for idiots to read and ignore. All the info posted here has already been posted in a hundred other threads. Giving "myths" their own thread will just serve to create more inaccuracies as people post "myths" that they really know nothing about. Who is to say that anything posted here is any more accurate from one person to another? Sorry OP, but "myths" may actually become myths in here.
Click to expand...
Click to collapse
The reason I created this thread is so that the next time I want to correct someone, I just link them here, instead of typing out the whole thing again.
On a separate note, I see you are really active on in the Atrix community, helping others. I would like to thank you, a person who is knowledgeable, taking time to answer their questions. Can't say the some about myself.
guidoido004 said:
Oem lock ******
Tried?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
?
ssmr2t said:
Hey Matthew, thanks for the info- I am going to Singapore on Sat for the airshow. Are there cool spots out there to get good deals on accessories for our atrix>? LOL
Click to expand...
Click to collapse
Isn't it next Saturday? And the iPhone is the "hottest" phone here, accessories for iPhones, yes, Atrix, little.
Abu-7abash said:
Not only Atrix related but a general fact, when you sim unlock a phone (atrix included) it won't ever get locked again no matter how/what roms you flash.
Sent from my Atrix 4g using Tapatalk
Click to expand...
Click to collapse
Thanks! Will include that!

Oh I will be exhibiting there for my company Tues-Friday.. I think Sat is public day.
Booo... I was hoping to get a nice atrix toys while I was out there

ssmr2t said:
Oh I will be exhibiting there for my company Tues-Friday.. I think Sat is public day.
Booo... I was hoping to get a nice atrix toys while I was out there
Click to expand...
Click to collapse
hey, hey, hey. get a room, you two. keep this thread myth related.

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.

Any Root Update for Sprint Variant?

I look through the threads and mostly what I see is T-mobile got a root. Other updates show regular roots but no mention of it applying to Sprint. Threads directed to Sprint don't say nor show much. Anyone can assist in getting a link or update for the root. I am looking very forward to it and also a mod for the DAC audio. For some reason it seems like an over rated feature as audio isn't that high as advertised and mind you I have the earphones that come free with the purchase.

I'm sure you'll see word either in the development section or in this thread. They'll need to get around a locked bootloader first.

Thanks Doug

douger1957 said:
I'm sure you'll see word either in the development section or in this thread. They'll need to get around a locked bootloader first.
Click to expand...
Click to collapse
They won't need to get around it. I don't think you WILL get around it, ever. So.

pro_granade said:
They won't need to get around it. I don't think you WILL get around it, ever. So.
Click to expand...
Click to collapse
that's what most said with the Galaxy S7 and LG G5 but they they're both rooted now

Snipars said:
that's what most said with the Galaxy S7 and LG G5 but they they're both rooted now
Click to expand...
Click to collapse
The Note 7 was rooted without unlocking the bootloader. I don't understand the under the hood specifics, but where there's a will...

Patience people. Contemporary Android is a maze of security protocols in order to get root. Not just the bootloader, but also SELinux policy, capability bounding, file-size checks, and so on. When an OEM tries to lock down a device. Really tries....It becomes hell. The phone only went on sale a week ago.
I'd suggest reading the following tale one fellow posted about his weeks long effort to chroot his Asus tablet. NOTE-his tablet had an unlocked bootloader and fastboot command access. Both are things we don't have.
https://www.thanassis.space/android.html

Skripka said:
Patience people. Contemporary Android is a maze of security protocols in order to get root. Not just the bootloader, but also SELinux policy, capability bounding, file-size checks, and so on. When an OEM tries to lock down a device. Really tries....It becomes hell. The phone only went on sale a week ago.
I'd suggest reading the following tale one fellow posted about his weeks long effort to chroot his Asus tablet. NOTE-his tablet had an unlocked bootloader and fastboot command access. Both are things we don't have.
https://www.thanassis.space/android.html
Click to expand...
Click to collapse
Not to be discouraging, but it took 18 months to get an unlocked bootloader on the Verizon Note 4.

douger1957 said:
Not to be discouraging, but it took 18 months to get an unlocked bootloader on the Verizon Note 4.
Click to expand...
Click to collapse
Oh I remember.
Me? I'm fairly well happy unrooted. About 95%