JBQ posted:
Setting up AOSP support for Crespo meant that I had to drop Dream and
Sapphire. That opened up more possibilities about using AOSP on retail
devices: the only variants of Dream and Sapphire that were designed
for AOSP work were the ADP1 and ADP2, which are rare, whereas any
retail Nexus S can be unlocked. Nexus S gives you both the openness
that comes with the ability to unlock it and the security that comes
with the ability to lock it back.
Click to expand...
Click to collapse
(emphasis mine)
Could the ability to unlock and relock the bootloader have been planned by El Goog? Is this a part of a business model? Does Google find this to be ideal? Are they, perhaps, recognizing the developer community, and showing a commitment to be even more open?
Samsung has had some "oversights" lately. I want to say there was something with the Galaxy S and rooting, but I'm not remembering well. I know that the Vibrant came with AT&T frequencies, yet was launched on TMo. There was a very simple way to enable those frequencies, because the unlock codes were stored on the phone. Now we've got the ability to unlock and relock a bootloader on the S. The unlocking of frequencies could be an oversight, as well as the bootloader. Or is this something that's been planned, with input from Google? Could Google have found a partner who's willing to be as open as possible?
I just found it a very interesting comment. Perhaps I make too much of it...
Thought for sure I'd get a response out of this. No one finds it interesting?
The Nexus One has "fastboot oem unlock" but not lock.
I'm guessing Google just told Samsung to add a lock command and will most likely tell all future "Nexus" handset manufacturers to do the same.
Very doubtful these commands will ever make it to any other Android device aside from the Nexus line.
I suppose they saw that they were getting tons of N1s returned with unlocked bootloaders and they repaired them anyways, so they probably decided to just allow the "lock" function to be used...
Although it really doesn't change anything tbh, and if it works like the lock, it will wipe everything on the phone which kinda sucks
As it was said, it is very doubtful we will see that kind of easy unlocking on other devices! This is a dev device, so it has to be "more open" to allow devs more flexibility.
I don't think Google ignores the dev community and I'm pretty sure they are happy it exists, because it makes Android better (I wouldn't be surprised if some of the official features were inspired from here and there )
I think you're correct in Google is simply making it easier for developers to root and flash custom Android builds to the phone. "Fastboot oem unlock/lock" are planned features of this phone according to Tim Bray, so there is no question.
One of the points made during the "Is Android Open" debate around the blogs/twitter was that the OS may be open, but there isn't much hardware that is. They probably paid attention to the debate seeing as Andy Rubin himself weighed in, as such we continue to see the Google experience phone as being open (enough).
On a side note: when the NS was released, every blog I saw (Engadget too) ran a headline about how quickly the phone was rooted.. If you run an Android-specific blog and held this opinion, seriously check yourself cause you're an idiot. I've been trying since January to find a "go to" Android specific blog and it doesn't exist. Still best just letting Engadget/BGR/Lifehacker filter the BS
crachel said:
I think you're correct in Google is simply making it easier for developers to root and flash custom Android builds to the phone. "Fastboot oem unlock/lock" are planned features of this phone according to Tim Bray, so there is no question.
One of the points made during the "Is Android Open" debate around the blogs/twitter was that the OS may be open, but there isn't much hardware that is. They probably paid attention to the debate seeing as Andy Rubin himself weighed in, as such we continue to see the Google experience phone as being open (enough).
On a side note: when the NS was released, every blog I saw (Engadget too) ran a headline about how quickly the phone was rooted.. If you run an Android-specific blog and held this opinion, seriously check yourself cause you're an idiot. I've been trying since January to find a "go to" Android specific blog and it doesn't exist. Still best just letting Engadget/BGR/Lifehacker filter the BS
Click to expand...
Click to collapse
I like this one:
http://www.androidpolice.com/
Paul22000 said:
The Nexus One has "fastboot oem unlock" but not lock.
[snip]
Click to expand...
Click to collapse
That's not entirely true. Nexus One's with S-OFF can use the fastboot oem lock command to re-lock their bootloaders. It's just that there's not many of them floating around!
Related
I want to start this discussion because I haven't seen it anywhere and I read several Android forums. I love the platform and it's "openess" but it seems that requirements from Google fall just short of making this the best platform ever for handsets.
We are all screaming at Motorola about the signed bl but we aren't focusing enough on the greater issue. The Android license from Google seems to allow this or maybe it is less specific to Google than to some other entity but I don't speak lawyerese so i'm not sure. Anyway, here is what I keep reading from Motorola...
"The use of open source software, such as the Linux kernel or the Android platform, in a consumer device does not require the handset running such software to be open for re-flashing. We comply with the licenses, including GPLv2, for each of the open source packages in our handsets"
My point of discussion is this, why aren't we asking Google what they can do? Why can't Google simply state that "we will not allow our software to be damaged in this way"? Why do they allow Verizon, at&t, Motorola, HTC or anyone else manipulate their software in a way that brings so much resentment? Is it not in Google's best interest to force this platform to remain open? I realize this is a double edged sword because open means people can do what they want, which holds true for companies also but I think that everyone realizes that Google's intent was that this would benefit everyone, not just the companies.
Also, everyone seems to forget that HTC is messing around with trying to lock down the NAND. Just because geniuses get past the protection doesn't mean that HTC isn't trying. If the Droid X is a huge success, even with this restriction in place, then what makes any of you think that the rest will not follow suit?
Because open means that you can do whatever you want with it. There is nothing stopping anyone from using it, modifying it for their own uses, and putting it in any device that would support it. That's why a company can strip down all of Google stuff from it and put Bing if they want to, and Google wouldn't be able to complain. The whole point of open and free software is that you compete by actually being the best at something. You keep Google stuff in Android because well, they work best.
Now, when you put Android in a device you manufacture, you do have the rights to do whatever you want with the device. This seems to be a hardware protection on top of the software ones. You know how DRM'd mp3 stop working? well, it's not much different, except that now there is physical damage.
True, these measures defeat the whole purpose of being open, but what the heck. Being truly open means making a great product, and then not complaining when someone grabs it and beats you with it. You have are always competing to deliver the best product, and that's why open is awesome.
Who was it that said: "I can't agree with what you are saying, but I will defend to the death your right to say it"?
Open goes both ways. The company (Motorola) has every right to lock down the bootloader and prevent others from flashing.
You guys are looking at it as if Motorola did this to prevent people from flashing custom roms. The real reason they did it was to prevent others from stealing their rom and porting it to another phone. If you like the "ninjablur" UI, you need to buy the DroidX.
Ryan Frawley said:
Open goes both ways. The company (Motorola) has every right to lock down the bootloader and prevent others from flashing.
You guys are looking at it as if Motorola did this to prevent people from flashing custom roms. The real reason they did it was to prevent others from stealing their rom and porting it to another phone. If you like the "ninjablur" UI, you need to buy the DroidX.
Click to expand...
Click to collapse
Actually, I don't agree. I'm pretty sure one could extract those widgets if you really wanted to. (They "Ain't all that" if you ask me. - And yes, I did buy an X yesterday and love it. Just ain't crazy about those widgets).
I think the real reason this is locked down is to prevent custom ROM/Root access to enable tethering. There are other issues I'm sure, but at the top of the list is to protect that revenue Big Red is trying to generate.
As to Google 'Stopping' the carriers from locking this down, please understand that if the carriers can't protect their revenue streams, they simply won't allow the phones on their network, and that would hinder the growth of the OS in general.
Don't take any of my words as endorsement of VZW/Moto actions. I'll be first in line to flash/root my phone when/if its ever possible. I'm just a realist. VZW wants $20/month for WiFi Tether. They are going to do as much as reasonably possible to keep you from doing that for free.
In a related note, 2.2 Froyo does tethering natively. I expect this to be crippled/disabled when we get our update in a couple of months.
I don't agree with the idea that companies would stop supporting the platform. The Droid has been a cash cow for verizon and it is an open book. Google could easily ask that their platform remain open for all to enjoy.
Beyond that, if Google allows them to gimp their OS then Google has created something entirely for the benefit of companies and not at all for the general population. I don't believe this is true. I think that the changes will start with Android v3.0. Google will start getting more pissy about custom crap especially if it makes their product seem worse and increase the chance that Android will be looked upon negatively.
Despiadado1 said:
I don't agree with the idea that companies would stop supporting the platform. The Droid has been a cash cow for verizon and it is an open book. Google could easily ask that their platform remain open for all to enjoy.
Beyond that, if Google allows them to gimp their OS then Google has created something entirely for the benefit of companies and not at all for the general population. I don't believe this is true. I think that the changes will start with Android v3.0. Google will start getting more pissy about custom crap especially if it makes their product seem worse and increase the chance that Android will be looked upon negatively.
Click to expand...
Click to collapse
Its the same problem with windows, the OS gets blamed for what hardware vendors do to it... we see this $400 computers getting compared to Apples $1500+ computers and thats some how proof windows sucks, I never had problems with Vista being slow, but people and there $400 computer did.
The problem with Android, specifically the scrolling smoothness, is the vendors custom Android OS setups...
FtL1776 said:
Its the same problem with windows, the OS gets blamed for what hardware vendors do to it... we see this $400 computers getting compared to Apples $1500+ computers and thats some how proof windows sucks, I never had problems with Vista being slow, but people and there $400 computer did.
The problem with Android, specifically the scrolling smoothness, is the vendors custom Android OS setups...
Click to expand...
Click to collapse
To be fair, I think the scrolling smoothness is half crappy hardware and half Android's lack of hardware acceleration.
Mikerrrrrrrr said:
To be fair, I think the scrolling smoothness is half crappy hardware and half Android's lack of hardware acceleration.
Click to expand...
Click to collapse
No some custom roms fix those issues because they enable the hardware acceleration, which again shows that Google really should crack down on some of these custom versions of Android on phones.
Zaphod-Beeblebrox said:
Actually, I don't agree. I'm pretty sure one could extract those widgets if you really wanted to. (They "Ain't all that" if you ask me. - And yes, I did buy an X yesterday and love it. Just ain't crazy about those widgets).
I think the real reason this is locked down is to prevent custom ROM/Root access to enable tethering. There are other issues I'm sure, but at the top of the list is to protect that revenue Big Red is trying to generate.
As to Google 'Stopping' the carriers from locking this down, please understand that if the carriers can't protect their revenue streams, they simply won't allow the phones on their network, and that would hinder the growth of the OS in general.
Don't take any of my words as endorsement of VZW/Moto actions. I'll be first in line to flash/root my phone when/if its ever possible. I'm just a realist. VZW wants $20/month for WiFi Tether. They are going to do as much as reasonably possible to keep you from doing that for free.
In a related note, 2.2 Froyo does tethering natively. I expect this to be crippled/disabled when we get our update in a couple of months.
Click to expand...
Click to collapse
Motorola has said so itself. The reason Droid X is locked down is because they don't want people stealing their custom UI. Widgets are only part of this UI. The inability to flash custom roms is merely a consequence of protecting their UI.
FtL1776 said:
No some custom roms fix those issues because they enable the hardware acceleration, which again shows that Google really should crack down on some of these custom versions of Android on phones.
Click to expand...
Click to collapse
Ah. Didn't know that.
This article just appeared:
http://www.businessweek.com/magazine/content/11_15/b4223041200216.htm
http://www.engadget.com/2011/03/31/google-tightening-control-of-android-insisting-licensees-abide/
Basically it says Google is calling out it's OEM to stop gross customizations and reduce fragmentation of the Android OS
this is great. People posting obviously don't get it. They aren't locking down anything, just making it so that companies can't take advantage of the users and fail to release updates. The os will still be as customizable as ever
Yeah it will still be just as open. But if companies customise it too much they won't be able to use the Android name. Although withholding the source code is not very open source and will hurt small companies/devs.
Explains it well http://gizmodo.com/#!5787565/google-finally-fights-back-against-android-fragmentation
fiscidtox said:
this is great. People posting obviously don't get it. They aren't locking down anything, just making it so that companies can't take advantage of the users and fail to release updates. The os will still be as customizable as ever
Click to expand...
Click to collapse
Well, 2.3.3 DOES increase the security and remove most of the malware* that are used to root the phone. So some of the exploits WILL go away. Certainly in that sense, it is more locked down.
*It is malware aka trojans, that's used to root; mostly Latoor G and J. I have to put the rooting software into a directory that's not scanned by my AV/AS.
here!!
(In Traditional Chinese)
Only HTC doesn't seem to unlock the hboot now!!
For those wondering here is a google translate version of the text on the page - that is why it is in bad english
Sony Ericsson last month promotional offer for mobile phone unlocking Bootloader, as it were the entire mobile phone industry has some new territory like. Samsung announced soon also Twitter 『If Google does not oppose, they will also unlock the phone Bootloader』. Motorola has been silent today audible.
Motorola promised by the end of this year's Android device for its offer unlocking services, users can own brush from a ROM.
Now even unlock a Motorola also provides that only four brands in the Android HTC did not respond due to the unknown when it said it will adhere or surrender it.
Click to expand...
Click to collapse
Sounds like HTC made no commnet
So I would say this article is one way or another. Plus maybe something is lost in that translation a little.
HTC, to this point, seems pretty good with being unlocked. I've had my Evolution now since it came out and its fully customized. The new Evolution after it also looks that way. I really thing, aside from Motorola, that the carriers may start being he ones to ask to lock or unlock he bootloaders. ISPs in the US finally out caps on bandwidth last year, I would see locked bootloaders being next. Really time will only tell, but hopefully we get to keep our freedoms. The FCC approved a device is ours when we buy it, therefore we should be able to do what we want. Hopefully companies keep that in mind instead of trying to lock stuff down.
The big business rreason is that an unlocked device lets a user stay with that device longer, as it can be customized wig the latest software features. Unlocked devices really force companies to invest in research to give us better hardware now, costing them more money. As anyway can really developed the software that goes into the phones.
My thoughts anyway...
~Max
√ This Message Sent From CM7 Nightlies HTC-Evo4G ™
Can you really blame them? I wonder sometimes how many Android returns are due to user screw ups, just look at the kindle fire forums, every other thread is, "help I bricked my fire"
I know this is a dev forum, but it doesn't surprise me at all that manufacturers are making it tougher.
Discuss
Sent from my Rezound using Tapatalk
Shouldn't matter, we know the risks of modding our phones, we pay for our phones and a lot more than we should over the life of a contract and even with upgrade price, we own our phone and should be able to have the bootloaders unlocked.
-Sent from my Droid 2-
It will be great to get our devices with S-OFF and eng S-OFF in advance.
We will not spend so much time with rooting then
Lol, 98% of kindle fire "brick" threads aren't actually bricked.. Being a kindle owner myself, its actually just because the computer doesn't recognize the device when it is stuck at fastboot.. (Easy fix by uninstalling all adb drivers and letting windows find the driver when you plug the kindle fire back in) The symptoms are like brick because it only powers on and it stuck at the kindle fire logo until you change the bootmode via computer...
I can see it now...
Hi Google?
What can I help you with?
My 5 second Google search led me to believe I could flash my street fighter rom to my phone?
::face_palm::
The main problem about unlocking bootloaders is the user itself.
A lot of people are throwing themselves in unlocking, rooting etc etc without reading and pay attention to the warnings. So, if my neighbour can do it, i'll do myself... The technical background is not the same for everyone, so it's not as simple as this.
I ve to admit that i blocked two or three devices (HTC desire HD, Xperia Arc, SGS2) but all the answers were here, if we know how to search unbricking a device only takes a few seconds/minutes to do.
Since the marority of newbies will not read, and search correctly in this forum, the brands will continue to lock their bootloaders to avoid problems with the 95% of users who think they know, but they don't.
I Am Marino said:
Shouldn't matter, we know the risks of modding our phones, we pay for our phones and a lot more than we should over the life of a contract and even with upgrade price, we own our phone and should be able to have the bootloaders unlocked.
-Sent from my Droid 2-
Click to expand...
Click to collapse
I think that is why htc is offering an official unlocking tool, that will void your warranty. That way, you can do what you want, but htc isn't on the hook when you brick it.
e334 said:
Lol, 98% of kindle fire "brick" threads aren't actually bricked.. Being a kindle owner myself, its actually just because the computer doesn't recognize the device when it is stuck at fastboot.. (Easy fix by uninstalling all adb drivers and letting windows find the driver when you plug the kindle fire back in) The symptoms are like brick because it only powers on and it stuck at the kindle fire logo until you change the bootmode via computer...
Click to expand...
Click to collapse
Now look at it through the eyes of the average user. Is that really just a common sense fix?
It is in no way in the OEM's best interest to unlock the bootloader. For them, it's nothing but trouble. Those who want a back door will find one, the tougher it is to get into, the more idiots you can eliminate from the equation.
z33dev33l said:
Now look at it through the eyes of the average user. Is that really just a common sense fix?
It is in no way in the OEM's best interest to unlock the bootloader. For them, it's nothing but trouble. Those who want a back door will find one, the tougher it is to get into, the more idiots you can eliminate from the equation.
Click to expand...
Click to collapse
I think part of why mfgs are still apprehensive of unlocking bootloaders is because they want to protect their code sense, blurr, etc... Some folks are changing there tune. Curious that unlike unlocking Google experience devices some mfgs are developing there own "unlock tool" I'll be apprehensive about using any tool from an mfg. I'm sure they'll CYA and you'll take all of the risk..
nrfitchett4 said:
Can you really blame them? I wonder sometimes how many Android returns are due to user screw ups, just look at the kindle fire forums, every other thread is, "help I bricked my fire"
I know this is a dev forum, but it doesn't surprise me at all that manufacturers are making it tougher.
Discuss
Sent from my Rezound using Tapatalk
Click to expand...
Click to collapse
like many have mentioned, we know what were doing to our phones by rooting/modding, but the manufacturer is treating us like little kids by not trusting us (looking @ you motorola)
Sent from my MB870 using xda premium
Haha, i'm one of those "haaaaah bricked my kindle fire" and yes i was just stuck in fastboot, some reading i build my fix
fastboot -i 0x1949 boot CWM5-B2.img
Click to expand...
Click to collapse
For the manufacturer open bootloader means trouble, people will just brick there devices.
An other interesting argument i was stumling i going like: "We have to look the bootloader to keep the software integer for people not messing with the drm of music / videos. "
yea, i believe they just wanna protect their code
All arguments for a locked bootloader are invalid.
Does your PC have a locked bootloader? NO.
Can you install whatever OS you want on it, provided it is architecture-compatible? YES.
Do PCs get messed up during botched OS installations? Sure they do. Do companies suddenly lose billions and go out of business as a result? NO.
Locking the bootloader on a device is censorship. End of story.
synaesthetic said:
All arguments for a locked bootloader are invalid.
Does your PC have a locked bootloader? NO.
Can you install whatever OS you want on it, provided it is architecture-compatible? YES.
Do PCs get messed up during botched OS installations? Sure they do. Do companies suddenly lose billions and go out of business as a result? NO.
Locking the bootloader on a device is censorship. End of story.
Click to expand...
Click to collapse
I agree. Besides the number of people who actually mess around with their phones are a small amount. I'd say maybe less than 2% (and that's being generous).
If you don't want a locked bootloader, get a Samsung.
synaesthetic said:
All arguments for a locked bootloader are invalid.
Does your PC have a locked bootloader? NO.
Can you install whatever OS you want on it, provided it is architecture-compatible? YES.
Do PCs get messed up during botched OS installations? Sure they do. Do companies suddenly lose billions and go out of business as a result? NO.
Locking the bootloader on a device is censorship. End of story.
Click to expand...
Click to collapse
Also, do PC companies care if you overclock your PC? No.
Bottom line, all in all, this is one of the best posts I've ever had the privilege to quote on XDA.
I Am Marino said:
Also, do PC companies care if you overclock your PC? No.
Bottom line, all in all, this is one of the best posts I've ever had the privilege to quote on XDA.
Click to expand...
Click to collapse
And why the hell not? A smartphone is nothing more than a pocket-sized computer with telephony features. Any desktop from the past thirty years can also make phone calls provided it's connected to a network. So the fact that a smartphone makes calls does not make it less of a computer.
It's a computer. A very small computer that fits in your pocket, that also has phone functions. I long for the day when I can buy a barebones smartphone and install whatever OS I want on it, Android or MeeGo or Ubuntu Mobile or Symbian or Windows Phone or whatever other mobile-oriented OSes are out there at the time.
I just long for the day people get complete control of something they actually own.
synaesthetic said:
All arguments for a locked bootloader are invalid.
Does your PC have a locked bootloader? NO.
Can you install whatever OS you want on it, provided it is architecture-compatible? YES.
Do PCs get messed up during botched OS installations? Sure they do. Do companies suddenly lose billions and go out of business as a result? NO.
Locking the bootloader on a device is censorship. End of story.
Click to expand...
Click to collapse
I have no problem with unlocking of bootloaders. But I do agree with OEM stance that unlocking of bootloader may void your warranty. Same thing if you mod your engine on your car, you may void your warranty for the engine. I agree that you should be allowed to mod the phone, just that htc shouldn't replace it when you screw it up. I think htcdev is about as balanced as we are going to get on it.
I know its too early but what do you guys this about rooting/custom roms for venice?
BB ceo said (something along the lines) that they will only make an android device if it is secured enough. WOuld that mean a locked bootloader etc? Moreover, it is using a much more secure kernel (http://berryflow.com/2015/09/blackberrys-android-slider-using-hardened-linux-kernel/) and i've read that some beginner's tools (eg enabling developer's options, sideloading apps etc) are blocked.
So what do you guys think? As for me, I believe in this community and i know one way or another, we will be able to install our favourite custom roms/apps on venice. Although I dont know if it would happen 2 days after launch of 2 years after the device reaches the market!
Btw cant wait for the device! I hope blackberry becomes a force again after this phone. I'll buy it the day it's bootloader gets unlocked + root is acheived
Do you have a source on the Priv blocking sideloaded apps? That would be very unfortunate. Locked bootloader is a given but I would still like to be able to install my favorite apks.
I can't see things like developer options/USB debugging etc being outright blocked. That just seems like a great way to alienate the majority of the userbase that a device like this is targeted towards.
This is my main concern... I want this phone, badly. But after having a G4, having to wait for root and still not having any decent roms I won't get the Priv if it doesn't at least get root. It's stock-ish android so I can deal with lack of roms but no root, no sale.
Sent from my LG-H811 using Tapatalk
No idea why anyone here thinks they would do that. Even on BB10 devices installing apks is allowed - and they sure wouldn´t do otherwise on an Android device - that would be crazy.
and yes, bl will be locked and encrypted - root - well that will be something to wait for.
:good:
Bootloader WILL be locked, that's a no brainer. But locking out sideloading, developer options is not possible without TOTALLY killing interest and sales. Blackberry desperately needs Priv to succeed. This is their last chance to avoid becoming the next Nokia. So no, we will have at least sideloading available. Honestly, it doesn't matter if they lock out all these essential features, if they release at least the kernel source and device tree day-and-date with the phone. If you have these, we're better off building a CM 12 (or 13:fingers-crossed ROM for the Priv.
Zer0.exe said:
Do you have a source on the Priv blocking sideloaded apps? That would be very unfortunate. Locked bootloader is a given but I would still like to be able to install my favorite apks.
Click to expand...
Click to collapse
sorry I cant give you a source. I read this on reditt or a blog post
MSF Jarvis said:
Bootloader WILL be locked, that's a no brainer. But locking out sideloading, developer options is not possible without TOTALLY killing interest and sales. Blackberry desperately needs Priv to succeed. This is their last chance to avoid becoming the next Nokia. So no, we will have at least sideloading available. Honestly, it doesn't matter if they lock out all these essential features, if they release at least the kernel source and device tree day-and-date with the phone. If you have these, we're better off building a CM 12 (or 13:fingers-crossed ROM for the Priv.
Click to expand...
Click to collapse
hmm. So do you think it would be possible to unlock the bootloader or it can never be unlocked?
btw slightly offtopic, but is there any phone which has a completely locked bootloader (ie has never been unlocked)?
Welp a leaked pic about the security settings confirms developer options can be enabled, so sideloaded apps is probably a go to. False alarm, peeps!
Zer0.exe said:
Welp a leaked pic about the security settings confirms developer options can be enabled, so sideloaded apps is probably a go to. False alarm, peeps!
Click to expand...
Click to collapse
Link?
HyperM3 said:
Link?
Click to expand...
Click to collapse
http://n4bb.com/blackberry-priv-64-bit-4k-video-confirmed/
The beautiful glass weave is also shown off. I love it on my Z30.
pluto7443 said:
http://n4bb.com/blackberry-priv-64-bit-4k-video-confirmed/
The beautiful glass weave is also shown off. I love it on my Z30.
Click to expand...
Click to collapse
Thanks for that! I am really looking forward to this device. Im all or nothing on this with my Nexus 6 right now.
rollerdyke44 said:
hmm. So do you think it would be possible to unlock the bootloader or it can never be unlocked?
btw slightly offtopic, but is there any phone which has a completely locked bootloader (ie has never been unlocked)?
Click to expand...
Click to collapse
there must be some poor phone that didn't get a bootloader unlock, and I firmly believe the Priv is gonna join their ranks as soon as it gets released.
Sent from a Cool Phone stuck with crappy KingUser
rollerdyke44 said:
btw slightly offtopic, but is there any phone which has a completely locked bootloader (ie has never been unlocked)?
Click to expand...
Click to collapse
Look at the recent crop of AT&T and Verizon Samsung phones. Their bootloader are locked up tighter then...... Well we will just say their locked down [emoji1]
Sent from my Nexus 6 using Tapatalk
http://i-cdn.phonearena.com/images/...aked-hands-on-photos-plus-official-images.jpg In fact, this image outright confirms that you can sideload/ use developer options.
I wouldn't count on too much. The developer options could have easily been changed and some removed. As BB main selling point is security I expect this device to be one of the harder ones to crack.
As for the bootloader questions. Yes there have been a few that were uncrackable, a dirty hack to by pass has worked on some.
I imagine root is just a matter of time. Unless they lock the system partition, which other manufacturers have done in the past (Looking at you HTC). Even so, it has been done and s-on/off has been cracked before. Alternatives to locking include e-fuses, like in legacy motorola devices.
Bootloaders on the other hand, we're probably going to have to get some concrete evidence. It is most likely locked in my personal opinion.
This is all just speculation. Hopefully Blackberry can find a good balance.
htko89 said:
I imagine root is just a matter of time. Unless they lock the system partition, which other manufacturers have done in the past (Looking at you HTC). Even so, it has been done and s-on/off has been cracked before. Alternatives to locking include e-fuses, like in legacy motorola devices.
Bootloaders on the other hand, we're probably going to have to get some concrete evidence. It is most likely locked in my personal opinion.
This is all just speculation. Hopefully Blackberry can find a good balance.
Click to expand...
Click to collapse
The efuze us still used in many devices and if I know blackberry they will have it check against its servers for security. Once it detects root it will most likely disable the device. Or most of the functions that use BB servers. Remember everything is routed through Blackberrys servers in Canada so if their servers go do so does the device.
zelendel said:
Once it detects root it will most likely disable the device. Or most of the functions that use BB servers.
Click to expand...
Click to collapse
I would be completely fine with them locking out the BB services when root is discovered. But locking down the hardware would be overstepping their bounds. It's our hardware, not theirs. I know that doesn't mean they couldn't still do it, I just think it would be a jerk move.
It would be like if Microsoft bricked xbox machines that have been modded. They don't, they just ban you from XBox Live if they detect it. I think it should be the same approach.
Yes but even MS has locked the bootloader on Many of their 32 bit machines now. Also I have a link that you might want to read where is passed then modding our devices at all will become illegal.
https://www.eff.org/issues/tpp