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.
Related
http://tl.gd/drbuch
(cue Chef Excellence music sting)
Sent from Remilla, my stock ASUS Transformer
That's "excellent"
It sounds like a baby about to "make" in his diaper.
QQ moar
10chars
chatch15117 said:
QQ moar
10chars
Click to expand...
Click to collapse
Do you want to know how old I am....?
I had to google the urban dictionary to find out what that meant!
HAHA Love that website i sit there and press random learn new words lol
A rant for sure. Not sure if it's excellent.
It's an idiots rant. Listen, companies want to keep people from rooting and putting on their own ROMs because ultimately there will always be some knucklehead out their that bricks their device or burns out their CPU because they overclocked their 1Ghz processor to 5Ghz and then they have the nerve to expect a company to cover it under warranty.
Honestly, if I developed a hardware product, I would want to make it as tamper proof as possible for that very reason. Yet, I can also understand the desire to be able to do what you want with your device when you buy it. So what is the solution? Something similar to what HTC has done with the Evo 3D where they will unlock the bootloader, but you lose your right to your warranty. I consider that a fair exchange personally, and I understand the reason why.
ExploreMN said:
It's an idiots rant. Listen, companies want to keep people from rooting and putting on their own ROMs because ultimately there will always be some knucklehead out their that bricks their device or burns out their CPU because they overclocked their 1Ghz processor to 5Ghz and then they have the nerve to expect a company to cover it under warranty.
Honestly, if I developed a hardware product, I would want to make it as tamper proof as possible for that very reason. Yet, I can also understand the desire to be able to do what you want with your device when you buy it. So what is the solution? Something similar to what HTC has done with the Evo 3D where they will unlock the bootloader, but you lose your right to your warranty. I consider that a fair exchange personally, and I understand the reason why.
Click to expand...
Click to collapse
Exaaaaactly. You want root? Fine. Here. Your warranty is forever void now.
ExploreMN said:
It's an idiots rant. Listen, companies want to keep people from rooting and putting on their own ROMs because ultimately there will always be some knucklehead out their that bricks their device or burns out their CPU because they overclocked their 1Ghz processor to 5Ghz and then they have the nerve to expect a company to cover it under warranty.
Honestly, if I developed a hardware product, I would want to make it as tamper proof as possible for that very reason. Yet, I can also understand the desire to be able to do what you want with your device when you buy it. So what is the solution? Something similar to what HTC has done with the Evo 3D where they will unlock the bootloader, but you lose your right to your warranty. I consider that a fair exchange personally, and I understand the reason why.
Click to expand...
Click to collapse
I am in mixed minds about the whole thing really. PC manufacturers don't feel the need to lock down computers as much as phones are. The more locked down something is the more likely someone trying to avoid locks will screw things up.
The "secure boot" sub-rant is actually more pressing than the TF rant. I expect "mobile" devices to be locked down, and half the fun of playing with them is giving the company the finger and voiding the warranty.
Messing with my PC so that I can't install whatever OS I want on it is going too far, though. As far as I can tell, "secure boot" is either a way to force every Linux distro to pay for a signed cryptographic certificate in order to be installed on a "secure boot" PC, or a way to utterly disallow anything other than Windows8 to be installed on that PC.
Personally I wish that even PC's were like Android devices, but with the freedom to erase Windows and install *BSD or Linux at will retained .
In my experience the most troublesome majority of Windows users are too incompetent to have the equal of root access to their own machine, except to make more work for people that want to fix or break their machine. So I am in favour of the idea, sure...here's your Windows 9 PC, then charge an unlocking fee to enable making an Administrator account that can be accessed by the purchaser instead of Microsoft Update. Then we could just make extra money off whiny snots complaining none of their NOT NT ready crapware works any more, and remind them that the warrentee is void .
There's no substitute for inteligence. Stupid tax ftw!
Sent from my Transformer TF101 using Tapatalk
To all:
The Twitter post that I originally made was to let off some stream that I had with ASUS locking down the Transformer with no official way to unlock the device. I mean, rooting/unlocking is risky, but in responsible hands, it's no big deal. Yes, I see your points about the TF being a mobile device, not as a netbook, and that it should be locked by default, but I use it like a netbook, and I think it's pretty reasonable for it to be considered one, but I agree that newbies should not be tampering with the clock speed of the device, just too risky.
The main point of the post was: Why didn't ASUS provide a official way to unlock devices? They should either follow HTC and provide unlocking via a website, or just let me use "fastboot oem unlock".
Oh, and why are no HTC AT&T phones unlockable via htcdev.com?
Sent from Sukia, my rooted HTC Inspire.
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
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....
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