Database Users

The future of unlocking?

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!

Locking off bootloaders

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.

New root exploit is increasingly unlikely

Quite a few of us xda lurkers are itching to get root on our devices, but the DRM-debacle of the Sony phones has made many, including myself, hold off with unlocking the bootloader. Instead, we've put our hopes to new exploits that would allow root while keeping the bootloader locked, thus making it possible to keep all DRM functions in place, and also to restore the phone to factory conditions with the bootloader intact.
However, as Chainfire explains in the post below, the chances of any such exploit surfacing are slim. He says it's more important than ever to buy phones with unlocked bootloaders if we want to keep root.
Sadly, I'm afraid he's right and that the official bootloader unlock is the only way we'll be able to get root in the foreseeable future.
What do you guys think? Worth it or not?
Check out Chainfire's post on G+:
https://plus.google.com/113517319477420052449/posts/VxjfYJnZAXP

Fruktsallad said:
Quite a few of us xda lurkers are itching to get root on our devices, but the DRM-debacle of the Sony phones has made many, including myself, hold off with unlocking the bootloader. Instead, we've put our hopes to new exploits that would allow root while keeping the bootloader locked, thus making it possible to keep all DRM functions in place, and also to restore the phone to factory conditions with the bootloader intact.
However, as Chainfire explains in the post below, the chances of any such exploit surfacing are slim. He says it's more important than ever to buy phones with unlocked bootloaders if we want to keep root.
Sadly, I'm afraid he's right and that the official bootloader unlock is the only way we'll be able to get root in the foreseeable future.
What do you guys think? Worth it or not?
Check out Chainfire's post on G+:
https://plus.google.com/113517319477420052449/posts/VxjfYJnZAXP
Click to expand...
Click to collapse
Well it's @Chainfire talking, who are we to doubt him? I'm only waiting for a way to backup my TA-Partition (DRM keys), I wouldn't mind losing some features. Even tho I must agree that losing some camera quality is really annoying, but Android is pretty open source so I have no doubts that people will find something to reverse the algorithm loss or create their own.
And also when the occasion occurs that I need to send my device out for repair, that they don't refuse it due to an unlocked BL

I'm sure that's true in the long run, just not sure if it's true now.
It's economics. The security bugs are going to get fewer and further between, but they will arguably never be eradicated. You should expect it to take longer and longer to find new exploits, but I wouldn't bet a wooden nickel that there are no exploits left.
More likely, we will reach a point where the cost of finding an exploit is so great that they're no longer worth looking for to a critical mass of hackers.
On the bright side, the implementations get better all the time, and I see very little about my z3c that I would like to change if only I had root.
And I do think Sony should find a way to make the early rooters whole again. I feel terrible that so many people's $500 phones have been seriously degraded by a completely reversible software change.

Dsteppa said:
Well it's @Chainfire talking, who are we to doubt him? I'm only waiting for a way to backup my TA-Partition (DRM keys), I wouldn't mind losing some features. Even tho I must agree that losing some camera quality is really annoying, but Android is pretty open source so I have no doubts that people will find something to reverse the algorithm loss or create their own.
And also when the occasion occurs that I need to send my device out for repair, that they don't refuse it due to an unlocked BL
Click to expand...
Click to collapse
True, but as I'm sure you're aware, backing up the TA-partition requires said exploit to be found in order to get root. So I think it'll be a looong wait. [emoji20]

He still thinks root will be achievable in the early editions of Android L so I think it's safe to say root will arrive for this device under a locked bootloader, it will just take a bit longer than it has in the past to find an exploit.
Sent from my D5803 using XDA Free mobile app

This is really disheartening. It's kinda ironic that Sony, who in recent times has been raised in its support of the developer community of its phones, and even won XDA's OEM of the Year, has such a downer in its phones.

I know this doesn't work for everyone but I'm hopeful that the new AOSP L camera API will mean that AOSP custom roms have some native low light enhancement processing. Maybe...

Chances improve with new software so I t could happen with android L too.

pricey2009 said:
He still thinks root will be achievable in the early editions of Android L so I think it's safe to say root will arrive for this device under a locked bootloader, it will just take a bit longer than it has in the past to find an exploit.
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
Yup, but we're still looking at about five months wait considering Sony won't ship L until Q1 2015. Even then, there's no guarantee an exploit will be found.
Maybe I'm overly pessimistic about this. I do, however, have high hopes for the new camera API's regarding camera quality and post processing.
Personally, every day without root is a little painful, so I'll never last all those months. As soon as there are custom kernels available and a ROM like CM or PA, my locked bootloader goes bye-bye.

Chainfire is talking about the su daemon and problems running it (on Android L). He does not say anything about a root exploit. It seems you misunderstood his post.

zxz0O0 said:
Chainfire is talking about the su daemon and problems running it (on Android L). He does not say anything about a root exploit. It seems you misunderstood his post.
Click to expand...
Click to collapse
Let's hope Sony make or have made some little security mistakes.. To quote his post:
" Of course, this is all dependent on OEMs implementing everything exactly right. If a certain OEM doesn't protect one of their services correctly, then we can leverage that to launch the daemon without kernel modifications. While I'm fairly certain this will be the case for a bunch of devices and firmwares, especially the earlier L firmwares, this is not something you should expect or base decisions on."
Here's hoping they have missed something.
Sent from my GT-I9300 using XDA Free mobile app

pricey2009 said:
Let's hope Sony make or have made some little security mistakes.. To quote his post:
" Of course, this is all dependent on OEMs implementing everything exactly right. If a certain OEM doesn't protect one of their services correctly, then we can leverage that to launch the daemon without kernel modifications. While I'm fairly certain this will be the case for a bunch of devices and firmwares, especially the earlier L firmwares, this is not something you should expect or base decisions on."
Here's hoping they have missed something.
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
Let's wait until January for the first android L release then :crying:

I've rooted two weeks ago and still enjoying the phone

zxz0O0 said:
Chainfire is talking about the su daemon and problems running it (on Android L). He does not say anything about a root exploit. It seems you misunderstood his post.
Click to expand...
Click to collapse
This.
The post was mainly aimed at Android L...

Google hired one of our very own (Towelroot) and iPhone's pioneering hacker so it's going to get tougher. I hope they hired him only for NSA purposes.

That move by sony is just stupid. if they wanted to protect their code, why not store it into the camera firmware (referring to the camera algorithms)?
Why do they have to kill Miracast?
Obviously that is the other side of the medal. investments on security = far less exploits available. we are gonna wait a while, but as a developer I really really miss Xposed. Each time I look at my G2 a little tear drops.
No way I'm gonna root loosing DRM keys. The camera is already weak (to be honest I would be used a word beginning in shi but let's be polite) so I'm not in any way gonna make it worse.

zxz0O0 said:
Chainfire is talking about the su daemon and problems running it (on Android L). He does not say anything about a root exploit. It seems you misunderstood his post.
Click to expand...
Click to collapse
Yes he does:
"As stated above, it seems for now that modifications to the kernel package are required to have root, we cannot attain it with only modifications to the system partition.
Combine that with a locked bootloader (and optionally dm-verity) and a device becomes nigh unrootable - exactly as intended by the security guys.
Exploit-based roots are already harder to do thanks to SELinux, and now because of the kernel requirements for persistent root, these exploits will need to be run at every boot. Exploits that make the system unstable (as many do) are thus out as well."
Then he goes on to say:
"Of course, this is all dependent on OEMs implementing everything exactly right. If a certain OEM doesn't protect one of their services correctly, then we can leverage that to launch the daemon without kernel modifications. While I'm fairly certain this will be the case for a bunch of devices and firmwares, especially the earlier L firmwares, this is not something you should expect or base decisions on. It is now thus more important than ever to buy unlocked devices if you want root.
It might also mean that every firmware update will require re-rooting, and OTA survival mode will be broken. For many (but far from all) devices we can probably automate patching the kernel package right in the SuperSU installer ZIP. We can try to keep it relatively easy, but updating stock firmwares while maintaining root is probably not going to work as easy and fast as it did until now."

zxz0O0 said:
Chainfire is talking about the su daemon and problems running it (on Android L). He does not say anything about a root exploit. It seems you misunderstood his post.
Click to expand...
Click to collapse
How can anything be a root exploit if it doesn't result in a functional su? I read Chainfire's post as Google making it impossible to elevate privileges from within Android, necessitating kernel level exploits which in turn will require unlocked bootloaders to install.
Once we get to where the bootloader has to be unlocked it's really not a root exploit anymore, is it?

michyprima said:
Why do they have to kill Miracast?
Click to expand...
Click to collapse
Because they don't want to support Miracast without HDCP. Remember that Sony is also a content provider. While that may be as annoying for a normal user as the degradation in camera quality, their approach actually still is developer friendly. Request a code - get full control over the device, at the cost of losing some functionality (software functionality). It's as simple as that. CM and other roms work perfectly fine on Xperia devices, and if you want to implement an equivalent camera algorithm, you're free to do so.

Iruwen said:
Because they don't want to support Miracast without HDCP. Remember that Sony is also a content provider. While that may be as annoying for a normal user as the degradation in camera quality, their approach actually still is developer friendly. Request a code - get full control over the device, at the cost of losing some functionality (software functionality). It's as simple as that. CM and other roms work perfectly fine on Xperia devices, and if you want to implement an equivalent camera algorithm, you're free to do so.
Click to expand...
Click to collapse
Can only agree to that. If you buy a Sony phone to act like a Sony phone (most people do!) then one should leave it as it has been delivered by Sony. If you can't agree to how it is, Sony gives you the option to unlock the BL and do whatever you want to do with the HW, but don't expect it to work/act as before. Personally, I have no issues with that at all.
On a different note, Linux/Android is comprised of x million lines of code. There're bugs in this code, there're bugs in the compiler, bugs in Java, bugs even in the Hardware etc. etc. There's no reason to believe (or fear) that Linux/Android would ever be perfect or non-vulnerable. Root will come, it's only a matter of effort and time...

Droid Mini XT1030 Rooting and Unlocking Bootloader for Free

Please help me in this. i need root apps and unlocking . coz i have no money etc ..... i need to root my device and want to install cm 12 on my device ....

Um... So do I. Do the research yourself, and spend time. This is so spam-like, and the research is ridiculous.

Yup.... Why motorola is treating customer like this. We paid u n that's it. I think they should provide unlock code for Droid mini as they do for others.
Sent from my XT1030 using XDA Free mobile app

Well, a few things. First off, if you are on android 4.4.4, there is no unlock for your bootloader. Next, there is a "free" rooting method, but based on what you have said thus far, I am going to go ahead and recommend against it. Motorola absolutely *SHOULD* provide bootloader unlock codes for any user not on contract, that wants one. The reason they do not is their agreement with Verizon Wireless stating specifically that they will not give unlock codes for Verizon devices that are not Developer Editions. Motorola phones that are supported are hard to come by, especially if you are a Verizon customer.
Personally, if your Mini is in good shape, (no scratches, dings, etc) i would sell it and hunt out another Mini or a Maxx on 4.4 on Ebay. (i have now done this successfully with a Mini and a Maxx) then you can (yeah, i know you don't like this part) pay $25 to get Sunshine to unlock the bootloader. Maybe that sounds like a lot of $$ for what it is. What i can say is a Dev edition of the Maxx (i know, i had a real one) is about $680 new. The retail version of the same phone was $550 or so. Even buying the phone from Motorola, you still paid more for Bootloader Unlock. I am old enough in the Android community to remember guys like Dan Rosenburg that never asked for $$, (or if you were insistant on paying, he asked you make a donation to charity), and also rooted every other device I have owned before the Mini for free. That used to be how it worked. Now, the only people interested are professionals who are literally spending time and money to find and utilize exploits. If you are really new, you should read up on security vulnerabilities, the qfuse system, and read up on the Azimuth Security blog and see what exactly was involved in the last run of bootloader unlocks. it isn't just someone playing code monkey and making a script. it is bricking (sometimes beyond all repair) $300-600 devices in an effort to make an unlock that might yield the money invested back.
As you said, and I live at the moment, you do not have money. This, my friend, sucks. I can say that in order to invest in my android devices, i have sold other things i cared about less (rare vinyls, extra devices, etc.) The reality is, $25 is not very hard to come up with if you are determined. Principally, at first glance, i disagreed with the premise of paying for what i feel should be an inherent feature of any android device, but when Motorola themselves say nothing will change the policy, I would much rather pay the money and know i am unlocked. google #unlockthedroids and you will see my names (kitcostantino, medicbeard, etc) a time or two...believe me i have tried. Motorola sells a crapload of devices to Verizon. Unfortunately, that means that Verizon (and also ATT) have too much clout and control over the Moto devices they sell for use on their networks.
The reality is, in the forseeable future, there will be less and less opportunity to unlock a retail device that is not a developer or pure edition. Security software checks and hardware gets better and better. the Devs that get through have a harder and harder time, and the knowledge is becoming more and more specific. I actually messaged DjrBliss on Hangouts to ask if he had any plans to work on the Turbo bl and he told me it was a stressful part of his life he was glad to be past. Honestly, he was so completely nice and cool about a total stranger contacting him, it blew me away. One of the most amazing exploit creators with ZERO pretentiousness, totally chill, and glad to talk to a fan (i have used his exploits on many of my phones). With dudes that capable not wanting to invest their time and efforts, we are left with mostly security experts to find our unlocks.(who can potentially make a crapload of money with their time and skillsets). Is $25 a lot compared to what these guys could be making? nope. but in all honesty, as I am inclined to do myself, I suggest you read up on anything Motorola related with regard to Qfuse, security checks, etc. The new age of exploits is upon us. The end user is going to have to be far more intelligent and far more comfortable doing things themselves to have control over their devices. In a way, it is a good thing because users that cannot do anything without a one-click or an app will be weeded out. In another way, it is horrible for android development, because those that do not have time, nor money to invest will get lost in the shuffle if they cannot buy a dev or unlockable device. I wish you the best man.

Can you guys learn to help instead of standing here complaining? For example, learn to deal with the All-PKG QHSUSB-DLOAD, download crap, be fearless and flash onto your device....

https://m.youtube.com/watch?feature=youtu.be&v=KyDnN3_hAmA

do u have root for 4.4.4?
do u have root for 4.4.4?

kaifkhan15 said:
do u have root for 4.4.4?
Click to expand...
Click to collapse
Yes.
http://forum.xda-developers.com/showthread.php?p=60085162
Sent from my locked but not stocked XT1080.

kaifkhan15 said:
do u have root for 4.4.4?
Click to expand...
Click to collapse
I use Kingroot to get my phone rooted. However, I failed to install TWRP by Flashify.

lwang9 said:
I use Kingroot to get my phone rooted. However, I failed to install TWRP by Flashify.
Click to expand...
Click to collapse
You rooted your phone but your phone's bootloader was still locked.

damiloveu said:
You rooted your phone but your phone's bootloader was still locked.
Click to expand...
Click to collapse
Im pretty sure he has an unlocked bootloader and then used kingoroot to Root.

method for 6-7.7
Hello, is it possible to get root for Droid mini with SU 6-7.7 somehow?

not as far as i know. not wp off full root at the very least. i have two droid maxx stuck on that same firmware with some success with temp root with kingroot, but reboot kills it. the newest firmware doesn't even do that.
Sent from my DROID Turbo using XDA-Developers mobile app

Nothing is updating.
Sent from my Nexus 6

DRM keys, worth losing or not?

This post over at the recovery/kernel dev thread seems to suggest that locked bootloader root and recovery might actually be impossible to achieve on the Z3+, so I've started to consider unlocking, having previously been adamant about not doing it. Losing the DRM keys is what prevents me, though.
Does anyone have a full list of lost features that go with the keys? I'm aware of some camera stuff, the Bravia engine, and noise cancellation.
Also, some users have reported at least partial restoration of DRM functions (not keys!) on previous Z devices, is that/will that be possible on the 3+?

+1 . I am in the same boat as op!
Sent from my Xperia Z3+

What features are lost? Anyone?

For me its not worth it
Some potential problems are as follows:
Bravia engine stuff and all that
Camera software is degraded especially low-light(can't confirm if this was changed with the z3+)
Sound EQ thingies and NC stops working
Drm Keys
Updates and stuff are not accepted anymore(OTA, PCC)

not worth it. additional to hasona's post :
-Xperia Lounge feature (eg: free movie)
- Screen mirroring
etc.
Currently i can live without root.
Adguard, Helium, will do the necessary needs atm.

And Sony is "committed to the openness of Android" or somesuch. I didn't know purposeful limiting counts as being committed.

monx® said:
not worth it. additional to hasona's post :
-Xperia Lounge feature (eg: free movie)
- Screen mirroring
etc.
Currently i can live without root.
Adguard, Helium, will do the necessary needs atm.
Click to expand...
Click to collapse
Currently I can live without root too, only thing I'm missing being not rooted is that I can't edit mixerpath to make my headphones louder,but still can live without that (but it would be cool to have it )
Sent from my E6553 using XDA Free mobile app

[NUMINIT] said:
This post over at the recovery/kernel dev thread seems to suggest that locked bootloader root and recovery might actually be impossible to achieve on the Z3+, so I've started to consider unlocking, having previously been adamant about not doing it. Losing the DRM keys is what prevents me, though.
Click to expand...
Click to collapse
Everything is impossible? says who? this will take time at least 9-10 months or 1 year to achieve root. Awesome devs at XDA always come with new exploits. :d
Don't unlock till then.

chesterr said:
Everything is impossible? says who? this will take time at least 9-10 months or 1 year to achieve root. Awesome devs at XDA always come with new exploits. :d
Don't unlock till then.
Click to expand...
Click to collapse
Once the z5 is out and they find a away for that, the z4 is sure to follow, with the same method.
Sent from my Xperia Z3+/Z4.

I have no issue with loosing that functionality to gain root..
If blocked updates are an issue, you can just flash newest ftf to get back to unrooted.. but right now, there is no way to get DRM back.

Personally I bought this phone for the express purpose of rooting it so I just assumed I'd loose the DRM keys from day 1.
[NUMINIT] said:
And Sony is "committed to the openness of Android" or somesuch. I didn't know purposeful limiting counts as being committed.
Click to expand...
Click to collapse
I think you've gotten Sony's intentions wrong mate. At least there's the option of unlocking the bootloader, albeit by loosing some phone functions. Most other companies they'd lock the bootloader away forever if unlocking meant compromising on proprietary software, or unlock their bootloader and not develop any customised functions as they'd be compromised if the bootloader got unlocked. At least Sony have a way for us to unlock the bootloader and also keep their IP safe. It's a compromise, and one that I'm happy to take.
Sony are one of the few companies that release their source code for their phones to the public. As far as I'm aware, the only other manufacturers only do so when they make a Nexus device and Google force them.

serrin85 said:
Personally I bought this phone for the express purpose of rooting it so I just assumed I'd loose the DRM keys from day 1.
I think you've gotten Sony's intentions wrong mate. At least there's the option of unlocking the bootloader, albeit by loosing some phone functions. Most other companies they'd lock the bootloader away forever if unlocking meant compromising on proprietary software, or unlock their bootloader and not develop any customised functions as they'd be compromised if the bootloader got unlocked. At least Sony have a way for us to unlock the bootloader and also keep their IP safe. It's a compromise, and one that I'm happy to take.
Sony are one of the few companies that release their source code for their phones to the public. As far as I'm aware, the only other manufacturers only do so when they make a Nexus device and Google force them.
Click to expand...
Click to collapse
You're right, I worded that more harshly than necessary. I was just so pissed that I bought an expensive phone I can't fully own without losing functions I paid for.
I do think it's silly to protect their software like this, though. Who would risk a massive lawsuit by stealing the IP that gets blocked with unlocking the BL?
Anyway, since you've unlocked, have you personally noticed much difference in everyday use?

Not worth.
My Z3+ wen crazy after some updates from Google (I think just after time when Google changed their logo). I was getting ~40-60 alerts "Google Services can't start" just after reboot. And they were jumping from time to time all the time. My phone was unable to reach google services so it was impossible to retrieve any updates, impossible to install or remove anything. This means impossible backup SMS/Call logs too (I didn't have any apps installed). Yeah I had Sony Xperia Transfer app, but this app will not let you transfer data to any other phone except SONY. Thank you SONY.
Decided perform factory reset. BUT, factory reset button from menu didn't worked. It simply did nothing. Was thinking bring phone to service, but then I need remove my mail accounts (I'm keeping job data there and I probably would be fired and get some 5-number-USD fine if I'd disclosure that info). Removing accounts didn't worked too.
Tried perform factory reset via adb, but no success. Decided boot into boot loader as in my good old nexus 4 and perform factory reset from there. Found some link on web that SONY gives you unlock code gently and you can do that yourself. What could be better, I thought?! Yeah, I've rebooted my phone, reset it and was happy again.
But after few days I've noticed that when I try zoom with my camera just a little, it simply freezes or performs 1 frame / 3-5 seconds. If I try record something - similar **** is happening. Quality is terrible too comparing what I had before. And then I found out about DRM...
So now I have one of top expensive phones with one of worst cameras.

[NUMINIT] said:
You're right, I worded that more harshly than necessary. I was just so pissed that I bought an expensive phone I can't fully own without losing functions I paid for.
I do think it's silly to protect their software like this, though. Who would risk a massive lawsuit by stealing the IP that gets blocked with unlocking the BL?
Anyway, since you've unlocked, have you personally noticed much difference in everyday use?
Click to expand...
Click to collapse
Well people port google apps all the time. Granted, no one's been sued yet, but there is a real likelihood that people are going to try it.
I don't think Sony are that worried about joe blow modder, but one of two things:
1) As part of their contract with the third party who they've leased the license from requires them to secure it (which may mean locking the bootloader)
2) Samsung or some other manufacturer would steal their code.
I'm just speculating, but Sony aren't making life difficult for everybody (and themselves) just for ****s and giggles.
I haven't noticed much difference, but then i didn't spend much time with it unlocked. I doubt loosing the drm keys will make the camera laggy.

serrin85 said:
Well people port google apps all the time. Granted, no one's been sued yet, but there is a real likelihood that people are going to try it.
I don't think Sony are that worried about joe blow modder, but one of two things:
1) As part of their contract with the third party who they've leased the license from requires them to secure it (which may mean locking the bootloader)
2) Samsung or some other manufacturer would steal their code.
I'm just speculating, but Sony aren't making life difficult for everybody (and themselves) just for ****s and giggles.
I haven't noticed much difference, but then i didn't spend much time with it unlocked. I doubt loosing the drm keys will make the camera laggy.
Click to expand...
Click to collapse
Would it not be possible to just use a different camera app or will that be the same?

serrin85 said:
Well people port google apps all the time. Granted, no one's been sued yet, but there is a real likelihood that people are going to try it.
I don't think Sony are that worried about joe blow modder, but one of two things:
1) As part of their contract with the third party who they've leased the license from requires them to secure it (which may mean locking the bootloader)
2) Samsung or some other manufacturer would steal their code.
I'm just speculating, but Sony aren't making life difficult for everybody (and themselves) just for ****s and giggles.
I haven't noticed much difference, but then i didn't spend much time with it unlocked. I doubt loosing the drm keys will make the camera laggy.
Click to expand...
Click to collapse
The camera is laggy as hell as per 5.0.2 anyway, so that's not an issue. I'm more worried about low-light shots. Unlocking absolutely ruined then on my Yuga.
Plus there are things such as the Bravia engine and noise cancellation which I really like

Is anyone willing to test this one on his UB?
http://forum.xda-developers.com/cro...deodex-xperia-z5-themes-home-widgets-t3207016

cjm1979 said:
Would it not be possible to just use a different camera app or will that be the same?
Click to expand...
Click to collapse
You can use a different camera app, but the Sony magic mojo (noise filter etc) is only found in the stock app. That is to say unlocking the bootloader nerfs the stock camera app, the camera hardware itself is untouched.

serrin85 said:
You can use a different camera app, but the Sony magic mojo (noise filter etc) is only found in the stock app. That is to say unlocking the bootloader nerfs the stock camera app, the camera hardware itself is untouched.
Click to expand...
Click to collapse
So if we had a camera app that does equivalent post-processing Sony's apps we would not lose any picture quality? Does this also mean that any 3rd party app that accesses the camera does not take advantage of any DRM-licensed functionality, and they will work exactly the same way after unlocking the BL?

steveeJ said:
So if we had a camera app that does equivalent post-processing Sony's apps we would not lose any picture quality? Does this also mean that any 3rd party app that accesses the camera does not take advantage of any DRM-licensed functionality, and they will work exactly the same way after unlocking the BL?
Click to expand...
Click to collapse
So I use 'A Better Camera' for taking pictures, as the stock app overheates the device incredibly fast. But if the stock sony camera app is working it's much faster than a third party app. But this is is only my own opinion, don't know, if that's always the case and if this depends somehow on the DRM key stuff. (Locked BL, using the 28.0.A.7.24 FW)