When one unlocks the bootloader on an Android device, the device then shows a "Bootloader Unlocked" warning splash screen. This is a general Android thing, not specific to the OP6T.
On the Moto Z2 Force (my previous phone), there was a way to hide that warning screen by flashing logo.bin. See thread:
https://forum.xda-developers.com/z2-force/development/remove-bootloader-unlocked-warning-t3702353
I have no idea if an approach like this would be relevant to our OP6T, but wondered if there could be something similar.
Thanks
dismembered3po said:
When one unlocks the bootloader on an Android device, the device then shows a "Bootloader Unlocked" warning splash screen. This is a general Android thing, not specific to the OP6T.
On the Moto Z2 Force (my previous phone), there was a way to hide that warning screen by flashing logo.bin. See thread:
https://forum.xda-developers.com/z2-force/development/remove-bootloader-unlocked-warning-t3702353
I have no idea if an approach like this would be relevant to our OP6T, but wondered if there could be something similar.
Thanks
Click to expand...
Click to collapse
Intriguing, but idunno.
Doubtful. Logo.bin is encrypted in most recent Android phones because the locked bootloader exists for a reason other than stabbing the customers in the back. So, I am confident that logo.bin mods will not work, since there are some machine codes embedded into the image file, meant for the phone to check if it's legit or not.
Sent from my OnePlus 6T using Tapatalk
This quest is vane.
All is hardcoded and all devs that tried to hack the files failed.
The only question in fact is: what is your problem with this screen? It lasts 5 secs and only when your reboot....
There are many more crucial things to deal with
Striatum_bdr said:
This quest is vane.
All is hardcoded and all devs that tried to hack the files failed.
The only question in fact is: what is your problem with this screen? It lasts 5 secs and only when your reboot....
There are many more crucial things to deal with
Click to expand...
Click to collapse
There may be more crucial things to deal with, and yes it's only showing for a few seconds, but that doesn't mean it's not important to the OP. It annoys the crap out of me as well but will admit I don't have the knowledge to even attempt looking for a solution. Just because you see it as nothing more than a minor annoyance doesn't invalidate his or others annoyance level over it. I'd love to see a solution to it but am aware one is probably not coming.
jestyr8 said:
There may be more crucial things to deal with, and yes it's only showing for a few seconds, but that doesn't mean it's not important to the OP. It annoys the crap out of me as well but will admit I don't have the knowledge to even attempt looking for a solution. Just because you see it as nothing more than a minor annoyance doesn't invalidate his or others annoyance level over it. I'd love to see a solution to it but am aware one is probably not coming.
Click to expand...
Click to collapse
My concerns about it are twofold:
1) If someone reboots my device without my knowing it, it's a dead giveaway that...well...the device is physically attackable.
2) When I inevitably pass this phone down to my wife, it will annoy her. Also, she has far worse opsec than I do.
Also, on some phones, possibly this one (OnePlus 6T), the logo.bin image file is deeply embedded inside the second stage UEFI bootloader (aboot), meaning if you try, you will definitely brick it, since it obviously will cause the bootloader to either be quite upset that the logo.bin now no longer pass the cryptography checks, or worse, be completely corrupted.
Sent from my OnePlus 6T using Tapatalk
dismembered3po said:
My concerns about it are twofold:
1) If someone reboots my device without my knowing it, it's a dead giveaway that...well...the device is physically attackable.
2) When I inevitably pass this phone down to my wife, it will annoy her. Also, she has far worse opsec than I do.
Click to expand...
Click to collapse
1) that's exactly why Google is against 'root' and why many manufacturers forbid bootloader unlock.... And why phones are encrypted
And why nearly all phone that permit bootloader unlock have this type of screen
Far less annoying than the warning that never stops in your car if your don't put your belt....
Actually, Google don't really care about rooting nowadays (they allow you to unlock the Google Store version of Google Pixel phones' bootloaders - if they are so against rooting, why do they give you a choice to unlock the bootloader), but they're more concerned about whether root agents are being hijacked (which is why Magisk have Superuser lockout protection, and I use it to only authorize the legit apps), and what the hackers (and cops hellbent on violating the privacy rights laws) would find once they get ahold of the Linux device block handles (like /dev/sda0 for instance) leading to the SD cards and embedded SSD.
So Google have had a right reason to encrypt the whole SSD; it's for your own protection and privacy, something you should be worried about especially after a few high profile security breaches.
In the end, it's never about rooting, it's always about the ramifications of if someone have a hold of your phone. Of course the argument against rooting is useless nowadays anyhow because when you unlock the bootloader, the phone automatically wipes itself clean leaving nothing for the suspects to try and steal (as the bootloader also do perform TRIM wipe too to make sure there's nothing left behind).
Sent from my OnePlus 6T using Tapatalk
Striatum_bdr said:
1) that's exactly why Google is against 'root' and why many manufacturers forbid bootloader unlock.... And why phones are encrypted
And why nearly all phone that permit bootloader unlock have this type of screen
Far less annoying than the warning that never stops in your car if your don't put your belt....
Click to expand...
Click to collapse
Google can't be said to be "against root," really. We continually see phones released with bootloader unlock allowed natively. I mean, all of Google's own phones - Pixels, Nexuses (Nexi?) - have permitted oem unlocking since basically ever (Ok, not sure about the Galaxy Nexus). All of the OnePlus phones have permitted it (save the new T-mobile 6t). It's mostly the CARRIERS who forbid it because they have a vested interest in making sure you can't take your phone to another network. Oh...and Samsung.
Full disk encryption is about user privacy, and I can't stress enough how important it is, but it's a separate argument.
I understand the underlying motivation for employing a warning screen like this. For someone who doesn't understand all this stuff, having a blatant warning is beneficial because they will know their device has been tampered with. On the other hand, I'm fully aware of the risks involved with unlocking, rooting, etc. I choose to do it because I'm using it to enhance the functionality and security of the phone for my very specific use-cases. That said, if I could mitigate one additional threat by not broadcasting to everyone that my bootloader is unlocked, maybe the attacker moves on to an easier target.
Whether you like it or not isn't really important to my motivation for asking these questions.
Those questions are asked since OnePlus 1, years ago.... Answer will always be the same. Impossible to get rid of the warning screen
Striatum_bdr said:
Those questions are asked since OnePlus 1, years ago.... Answer will always be the same. Impossible to get rid of the warning screen
Click to expand...
Click to collapse
People keep saying that, I don't buy it. It's been done on too many devices when someone has been determined.
Here is the Nexus 5X thread, it had some details about how it's done on that device. Perhaps it would be useful or provide some ideas?
The problem is, Nexus 5X's bootloader use different disk partition compared to OnePlus 6T's, and OnePlus made a change to how the bootloader protect itself ever since OnePlus 5T phone was shown to be vulnerable to the bootloader console and UEFI payload partition attacks.
So don't be surprised if you attempted the Nexus 5X boot splash trick on the OnePlus 6T's bootloader, only to have to use the Qualcomm Snapdragon processor tool to get it back to life.
Sent from my OnePlus 6T using Tapatalk
After a little bit of research, it's kind of possible to install a modified UEFI payload bootloader (abl / aboot) on the Snapdragon 845 phones like our OnePlus 6T. It will be tricky because of the UEFI XBL bootloader agent which is very strict about the file size / cryptography checks even if *it* is technically already unlocked, it still acts like a locked bootloader for a good reason.
TLR, it is possible to replace the bootloader unlocked warning splash screen on the OnePlus 6T, but the encryption and UEFI security check will stop you short of attaining your hacking goal.
Sent from my OnePlus 6T using Tapatalk
Related
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.
So I noticed Moto has the unlocked the bootloader on their Razr M.
They priced it at $549 - I was reading their FAQ and they made mention to unlocked boot loaders not being able to install some apps from the google play store? Has anyone run into this at all? There sure is a lot that Moto says may break and have issues after unlocking the bootloader of a supported dev. model.
LET'S MAKE SURE YOU KNOW WHAT YOU'RE GETTING INTO FIRST.
In case you didn't know, Bootloader is a little bit of code that tells your device's operating system how to boot up. Basically, it's what makes your device start up and run the way you're used to.
Motorola has done the work to make sure your device has a fully optimized, certified and tested version of Android.
Unlocking the bootloader will allow you to customize your device, but keep the following in mind:
Unlocking your bootloader is not for the faint of heart. Unlocking your device and installing your own software might cause the device to stop working, disable important features and functionality, and even make the device unsafe to the point of causing you harm. Neither Motorola, nor your wireless carrier or retailer from whom you purchased the device, will be responsible for such damage, so please do not unlock or load any software unless you know what you are doing.
You have only yourself to blame. Once you get the unlock code, your device is no longer covered by the Motorola warranty; in other words, please don't blame us if things go wrong, even if they appear unrelated to unlocking the bootloader.
The law still applies. You still need to operate your device in compliance with all applicable laws, rules and regulations prescribed by the FCC, and any other governmental agency for that matter.
And now a word from our lawyers. Finally, in order to unlock your device, you need to agree to important legal terms, which can be found on the next page. Agreeing creates a binding legal agreement, so be sure to read them carefully.
STILL INTERESTED IN UNLOCKING THE BOOTLOADER?
First, confirm that your device can be unlocked
Currently, Photon Q 4G LTE, and DROID RAZR HD and DROID RAZR M Developer Editions can be unlocked.
For a complete list of supported devices, see What devices are supported by the Bootloader unlock program?
REVIEW ALL THE WARNINGS AND MAKE SURE YOU COMPLETELY UNDERSTAND THE IMPLICATIONS
Once you get the unlock code, your device is no longer covered by the Motorola warranty; in other words, please don't blame us if things go wrong, even if they appear unrelated to unlocking the bootloader.
Unlocking your device and installing your own software might cause the device to stop working, disable important features and functionality, and even make the device unsafe to the point of causing you harm. Neither Motorola, nor your wireless carrier or retailer from whom you purchased the device, will be responsible for such damage, so please do not unlock or load any software unless you know what you are doing.
You still need to operate your device in compliance with all applicable laws, rules and regulations prescribed by the FCC, and any other governmental agency for that matter.
Your wireless carrier may prohibit unlocked devices from operating on their network.
Finally, in order to unlock your device, you need to agree to important legal terms located on the next page. This creates a binding legal agreement, so be sure to read them carefully.
HOW UNLOCKING YOUR BOOTLOADER COULD IMPACT YOUR DEVICE
You will lose all media and content on your device and will need to reinstall all applications downloaded from Google Play.
You will not be able to watch any movies you downloaded.
Applications may not work anymore.
You may lose encryption support.
You may lose some key functions like telephone, radio, and audio playback.
You could cause permanent/physical damage to your device.
Unlocking your bootloader will not change your device subsidy lock status
If you don't understand any of the above risks or warnings, we suggest that you do not continue to unlock your device's bootloader.
If, however, you are ready to accept all the implications of unlocking the bootloader, which includes completely voiding your device's warranty, continue on to receive a bootloader unlock code.
Click to expand...
Click to collapse
I've rooted and flashed previous android handsets to Cyanogen mod before without any issues - it's fairly straight forward. Would this be any different because of the bootloader unlock?
Pardon my ignorance, I seek your wisdom xda.
Thank you
patrickisfrench said:
Would this be any different because of the bootloader unlock?
Click to expand...
Click to collapse
Unlocking bootloader resets the device to out-of-the-box state. Your files would still be kept on external sd card; internal sd card gets wiped. All the Moto warnings are there to basically scare off inexperienced users. The apps that worked with locked bootloader will surely work with unlocked one.
Google Play Movies is an example of one that wouldn't work.
[TSON] said:
Google Play Movies is an example of one that wouldn't work.
Click to expand...
Click to collapse
Wow - I just paid $550 and it won't install Google play movies? Can you explain that one?
Thanks
wado1971 said:
Wow - I just paid $550 and it won't install Google play movies? Can you explain that one?
Thanks
Click to expand...
Click to collapse
They used to not let Google play movies work on rooted devices. However, I thought they fixed that a few months ago, so unless I'm wrong I think you should be ok. Guess you'll find out tomorrow and in any event, it should DEFINITELY work if you aren't rooted. I don't think the developer device is rooted by default, right ? Just boot loader unlocked.
-Sent from my TMOUS HTC One S.-
-Stock/rooted 2.21 + 1.06s baseband-
-Hboot 1.06-
Yes you can now use Google Play movies on a Rooted, Unlocked phone. I have it running on my Cyanogen Modded Galaxy Nexus. That hasn't been an issue for quite some time.
I had that issue of not playing movies because of root about two months ago
Sent from my XT907 using xda app-developers app
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...
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
I just got couple Fire HD 8 6th Gen tablets for my kids, and thought I'd flash them right away with a custom ROM. I was quite disappointed with the absence of development for this tablet.
Anyway, as far as I understood from reading the forum (and I just started, sorry if I missed something), the first problem is the factory locked bootloader. And it sounded from a post I read like it's something that cannot be solved: http://forum.xda-developers.com/hd8-hd10/help/rooted-boot-img-t3508316 (bootloader locked discussion starts at the bottom of the 1st page).
Well, I am definitely not a pro in mobile development (I work on server side software for living), so I beg your pardon if I'm wrong. But unlocking a locked bootloader is not something unheard of.
So, I was wondering, if it could be done for other device, then probably it can be done for this one too. And the fact that it has not been done yet could mean for example, that this device is somehow different. Or, it could mean that there was no one yet with enough expertise AND the device at hand to do it.
So if the latter is true, and it's just lack of attention from good developers. Then I guess it could be arranged to donate a device to a reputable XDA dev. A dev that would be interested in having a challenge. And a free device.
I would definitely pitch in, and if you would too, please tell. And if you know an XDA dev who has expertise to do it, please tell too, and give an example of their work.
All the above is open for discussion of course, constructive suggestions would be much appreciated.
The 7" is locked but got a lot of love and is now rootable. If the guys at Kingroot that interest, we might see something but otherwise not. Until rooted, not much point porting a ROM.
So I suppose the proposition is to send a device to KingRoot guys?
...in China.....
I was wondering how the issue of locked encrypted bootloader was solved for other Fire devices. Here's how it's been done for Fire HDX 8.9: http://forum.xda-developers.com/kin...bootloader-unlock-procedure-software-t3030281 . I suppose the bug used in this method has been fixed already, this is just a demonstration that it can be done.
That was cracked using a crypto bug. Basically exploiting a weakness in the RSA encryption of the bootloader's signature. It's incredibly rare for encryption to get totally broken like this, and easily patched with system updates. Kinda got lucky on that one. Best thing to hope for first is root, then try to find a way around the bootloader's protection. These keep getting exponentially harder, and there's a lot more money on developing protections than breaking them.
I received one as a gift. I will probably never use it unless its opened up.... i mean im appreciative that someone gifted me it. But I become really upset by the fact that samsung and amazon... all the big players really lock up their bootloader and force me onto some ecosystem when i know the tablet or device could work just so much better. Anyways, if there is anything i can contribute let me know...
Download the Kingroot App then run it. After running it once or twice it will ask you to send a device request. Root may eventually be achieved for the 6th Gen but that may be as far as it gets. Very unlikely that the bootloader will be unlocked. Amazon actively puts a lot of effort into keeping them locked. Its been a while since any newer version of these Fire bootloaders have been unlocked. The HD 8 5th Gen is about 2 years old and the only thing thats been achieved was root and that was done by Kingroot..... But hey nothings impossible....