We seem to have a lot of confusion in the Atrix forum about the implications of an encrypted and or locked bootloader.
What is a bootloader?
See this article for a decent description.
Is the bootloader on the Atrix encrypted?
We don't know and likely will not know until the phone is released and people smarter than I can look at it. No reviews, including the Engadget review, have looked at whether the bootloader is encrypted. However, some have inaccurately said that it is because the installation of non-market apps is not permitted the bootloader is encrypted. However, this is a separate issue and is a requirement imposed by ATT that has nothing to do with the bootloader.
Why do people assume the bootloader is encypted?
Motorola has a strong recent history of releasing encrypted bootloaders, see the Droid X and Milestone phones. Most of the current discussion about the bootloader is limited to what we have seen from Motorola in the past. That being said, there is some hope that the bootloader will not be encrypted. In prior phones, such as the Droid X and Milestone, Motorola relied on the eFuse feature of Texas Instruments OMAP processors. Given that the Atrix uses an Nvidia Tegra 2 chip it is unlikely that Motorola can utilize the same eFuse technology.
As a result, there is some reason to be optimistic that the Atrix will only have a locked and not encrypted bootloader.
What is the difference between a locked and encrypted bootloader?
This is a good post on the topic. Locked bootloaders are on almost all android phones, including the Nexus S. Although certain locks, such as the Nexus S, are easier to open. A locked bootloader is essentially software that is written in such a way so as to prevent you from gaining access. So far XDA devs have been very skilled at cracking locked bootloaders by finding holes in this software.
An encrypted bootloader, from my understanding, is not itself encrypted, but signed by an encryption key. The phones hardware will refuse to boot unless the software that it attempts to boot is signed with the correct encryption key. The only options to crack this protection appear to be to go around the bootloader which is unlikely or to crack the encryption which also appears unlikely. See this post for more discussion.
What does an encypted bootloader mean to me?
This post at Android Forums provides a great summary of the effects of an encrypted bootloader. If you have the time, the entire thread is very informative.
The bad news is an encrypted bootloader likely means no custom kernels. This means that custom ROMs must rely on the official kernel. It also means the OS version (Froyo, Gingerbread . . .) is limited to whatever the official release is. The good news is that root access is still be possible. Root access allows you to run certain applications as the root or administrator. This allows for a lot of customization and hacking of your phone.
In the end, an encrypted bootloader may hinder your ability to completely hack the phone.
Can an encrypted bootloader be cracked?
Unlikely. For a brief discussion see this post and read the thread for a better understanding. I am aware that there is a team working on cracking the Milestone encryption using the BIONIC platform and a distributed computing effort, see androinc.net. However, even that team admits that the second coming of the dinosaurs may occur before they crack the encryption. I believe on the Milestone that the encryption is 1024 bit, which according to androinc.net may take hundreds of thousands of years to crack using a brute force method, even on a distributed computing platform.
Can a locked bootloader be cracked?
We won't know until we see it, but likely yes. Generally all software coded by humans has some error in it that can be exploited.
Why should I care if the bootloader protection cannot be circumvented?
You don't have to. But, in today's environment, consumers are tied to a 2 year contracts but new phones are released on a 1 year or less timeline. This means the device you buy today will likely be forgotten by your carrier and the phone manufacturer long before your contract is up. The inability to load custom kernels means that consumers cannot upgrade their own phones after the manufacturer decides to no longer support the phone. The decision to stop supporting upgrades often occurs well before a phones 2 year birthday, see the Motorola Upgrade Roadmap.
In addition, many people believe that they have purchased the phone hardware and should be permitted to do anything that they please with the hardware.
** I do not claim to be an expert, I have only recanted the results of my research. If I have made a mistake please let me know.
thanks for writing this i was going to my self today as i have been fighting people all day with this, i was trying to get motorola to tell me as i had a few reps available in a forum and one said that he will get back to me shortly with an answer ... but i was having to do so with people that dont know the difference chiming in and making the q&a with moto hard even for some one who does know what hes talking about ... any how i will update when i get my reply, and thanks again for putting info in right place btw up at top you put milestone instead of atrix
What a great and informative post. THIS SHOULD BE STICKIED for the time being to prevent future threads that ask the same questions. Great job.
Sent from my MSM using XDA App
sdlopez83 said:
What a great and informative post. THIS SHOULD BE STICKIED for the time being to prevent future threads that ask the same questions. Great job.
Sent from my MSM using XDA App
Click to expand...
Click to collapse
+1 here, very informative.
Thanks and sorry about the typos.
Nice job both in the layout and in maintaining an unbiased take on the possibilities.
thankyou for explaining that so well
can we get a MOD to sticky this for a while, at least until we know whether it is encrypted or what not. could really cut down on the "does the bootloader restrict me from doing xxxxxxxxxxx?" chatter on all the threads.
+1 Great post! Guess we'll have to wait for quantum computers before we can crack 1024bit encryption in under a lifetime (seconds probably.) But very informative, I'm off to read everything you linked in your post.
Excellent post sir!
Great post! This should be required reading...
That means that if the Atrix 4G is HSUPA disabled, there's no way around it?
royalemint said:
That means that if the Atrix 4G is HSUPA disabled, there's no way around it?
Click to expand...
Click to collapse
please post in the general forum where a thread is going about this. however, it can mostly likely be resolved with a new modem driver.
I have an Atrix 4G in my hand... how can I find out if the bootloader is encrypted?
EGBTMagus said:
I have an Atrix 4G in my hand... how can I find out if the bootloader is encrypted?
Click to expand...
Click to collapse
I would like to know also. I know there are other threads about this the only problem is that there are 6 different answers/opinions.
Does not look good:
The Atrix 4G has a locked and encrypted bootloader. More bootloader related announcements are forthcoming.
http://getsatisfaction.com/motorola...tm_medium=email&utm_source=reply_notification
TinyRK said:
Does not look good:
The Atrix 4G has a locked and encrypted bootloader. More bootloader related announcements are forthcoming.
Click to expand...
Click to collapse
... and here just for the record:
https://supportforums.motorola.com/thread/45249?start=15&tstart=0
meta96 said:
... and here just for the record:
https://supportforums.motorola.com/thread/45249?start=15&tstart=0
Click to expand...
Click to collapse
I saw both of those. I am not totally convinced by a PR response, even if it is from Moto. So far the devs here in XDA seem to think it is only signed. I am inclined to believe them more, at least until I see otherwise.
Also, I need to update my OP and will try and do so tonight.
krkeegan said:
I saw both of those. I am not totally convinced by a PR response, even if it is from Moto. So far the devs here in XDA seem to think it is only signed. I am inclined to believe them more, at least until I see otherwise.
https://supportforums.motorola.com/thread/45249?start=15&tstart=0
Also, I need to update my OP and will try and do so tonight.
Click to expand...
Click to collapse
... the number of page views for this topic is bad PR, isn't it? It is just a act/react thing, you know ...
Who is your daddy and what does he do?
I dunno why but that's immediately what I thought of, lol
Sent from my MB860 using XDA App
Related
This is taken from engadget.com
HTC is legendary for its tacit support of the Android ROM cooking community. Motorola... not so much, thanks in large part to the company's policy of locking down the bootloader as a means to prevent unapproved software from running on its Droid handsets. An annoyance recently exacperated by a moderator of Moto's YouTube channel who suggested that customers looking to install custom ROMs should "buy elsewhere." Ouch. The resulting public relations kerfuffle then prompted Motorola to publish a clarification to its bootloader policy on Facebook:
We apologize for the feedback we provided regarding our bootloader policy. The response does not reflect the views of Motorola. We are working closely with our partners to offer a bootloader solution that will enable developers to use our devices as a development platform while still protecting our users' interests. More detailed information will follow as we get closer to availability.
Obviously, we'll have wait for said details to get official before calling this a shift in strategy. It's certainly an improvement over Moto's previous approach of lawyering-up with cease and desist orders. Perhaps Motorola is taking a cue from Microsoft who seems to have recently discovered that it's better to embrace than to annoy a motivated hacking community -- customers who tend to be a company's most dedicated fans and evangelists.
Good news?
Direct Link: http://www.engadget.com/2011/01/21/motorola-ready-to-make-sweet-love-to-rom-devs-and-rooters/
its a maybe. maybe they will launch our froyo locked, maybe it'll be open. we never know.
i just read this also. this could be great news or another terrible taunt whih leads to nothing.
im not gonna get my hopes up just yet.
available Q1 of 2046, stay tuned! lol
Sent from my Milestone using XDA App
Sounds like a PR stunt to quell the immediate situation before waiting for it to blow over.
Sent from my Milestone using XDA App
I dont believe in manufaturer, i believe in XDA dev's..... this a "cold water" not a hope for us.
I hope this isn't just some PR bull and moto actually enables us to load custom kernels.
That press release says nothing about unlocking the bootloader, only that they will help devs which could mean anything!
DummyPLUG said:
available Q1 of 2046, stay tuned! lol
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
LMFAO!!!
i dnt believe motorolsh!t will do that(unlocking the bootloader)
I so love my new HTC Desire! couldnt stand this situation anymore....! sorry guys...
It is just the usual PR crap which companies like them give when they screw up on the social networking front. The "..buy elsewhere.." was just a such screw up. A Royal one I would say!
They are now trying to calm down the situation by giving us this crap..
I think it's just a excuse about the bad comments in youtube video, nothing more than that.
DummyPLUG said:
available Q1 of 2046, stay tuned!
Click to expand...
Click to collapse
2046???
...that seems a little too soon... dont ya think?
Menelkir said:
I think it's just a excuse about the bad comments in youtube video, nothing more than that.
Click to expand...
Click to collapse
That seems most likely but perhaps the fallout and bad press from that will push them to do what they should have done long ago, free the bootloader in some form so we can get custom ROMs on it.
Dyonas said:
That seems most likely but perhaps the fallout and bad press from that will push them to do what they should have done long ago, free the bootloader in some form so we can get custom ROMs on it.
Click to expand...
Click to collapse
Yes, I really want to see this happening, but I don't have any hope about Motorola opening the bootloader.
If they do, ok, excelent news to the community, to all developers that will make even better ROMs and for all of us that have a Motorola phone. We can see the quality of alternative ROMs for Motorola Milestone today as example. It's obvious that the only limitation is the bootloader, so the quality can be massively improved if we can change and optimize the kernel.
But I think all people here are already tired from Motorola's position about his costumers: Censorship on comments (youtube and motorola forums), censorship on criticism (even the very good ones, Motorola does not seem to care about the opinion of his costumers), cease and desist in community cases like the ROM of Droid X and sites with roms (that its very stupid IMHO)... and the list goes on...
By the way, my only hope is, if that happens and I have not exchanged my phone yet, good.. I'll make good use of it. But honestly? I have now my last phone from Motorola.
Am I missing something? Forgive my ignorance, but what is "locked up" about the bootloader? I'm running CM6 along with the overclocked CM6 kernel, and there are tons of other custom ROMs out for the Droid as it stands. What is restricted by Motorola?
vapor63 said:
Am I missing something? Forgive my ignorance, but what is "locked up" about the bootloader? I'm running CM6 along with the overclocked CM6 kernel, and there are tons of other custom ROMs out for the Droid as it stands. What is restricted by Motorola?
Click to expand...
Click to collapse
Milestone users cannot use custom kernels. All the AOSP ROMs still have to use the SAME kernel, supplied by Mot. They lock it to the bootloader. This means problems trying to compile modules and customer kernels and no way to patch bugs.
It is much more work for devs to get stuff done for the milestone than other phone (htc comes to mind).
Examples of issues: battery life, phone sleeping, waiting for compatible kernel or hack for new android versions, swap support, vpn support, other filesystem support... the list goes on.
But you allowed to be happy with your phone. Not everybody needs these things...
Sent from my Milestone using Tapatalk
He has a very good point. Where other android device builders seem to be promoting development (Huawei excluded, theyre miser's just like Motorola), this company seems to be more prominent on the restriction of development on their devices.
One very good reason for this is that Motorola has been such a huge phone developer for such a long time, that they have probably let it go to their head. Now instead of saying "our consumers said they need this", they're sayin "we think they really only need this." I've used Motorola phones for about 8 years now, and I would DEFINITELY say someone forgot that their customers put them where their at.
I agree. Someone needs to get out there and give them a taste of Good Customer Service. I dont think restricting dev's is a great marketing idea, or revenue booster anyways. BUt then again, to each, his own.
This is PR.Nothing more.
Know motorola they do not update РСТ(Russian legal)Milestone, they do not
need to unlock this crap bootloader.
This thread is my first at XDA, and from my experience a worthy device to be discussing here.
I am expanding my nerdly endeavors to my new toy these days. I have a solid device in the Bionic, but there's still a feeling of betrayal stabbing into my core.
So what's up with this locked bootloader thing, and what are the implications?
To those, like I, who have bought a Motorola/Droid with a surely locked bootloader, might be wondering WTF?
While trying to boot into recovery, being new to Android phones, I couldn't for the damn succeed. I wonder how many noobs will never root their Motorola phones, as they fail to "Bootstrap" into recovery.
Bootstrapping into recovery, what?
Yes, dear noob if you might humbly continue to read, equipping your bootstraps is quite an important step of the process to being leet,
What you need is a way to change what boots when you start the phone, and after rooting you can install a BOOTSTRAP as it were, to instruct the bootloader as you please. In this case, it would please you to boot RECOVERY. And certainly we all understand the implications of root by now?
Language can be tricky for us newbies! Even then already-nerd kinds!
Here you are dear reader is a reverse-tutorial on our Bionic, and I presume other Motorola Droid branded devices. Let us discuss something more important at hand -- What isn't possible because of the lock-down on what happens when our phone boots? For one, I can't get the hours back I wasted while wondering WTF?
The Bionic is personally my first Android device. My ex-phone (previous to the Bionic) was Windows Mobile 6.1 as it was sold to me. Non-touchscreen I might add. Nobody cared to hack it to bits to see what was possible. From the prison of my old cell phone rose the desire to get back on the right team, where things actually continue to develop and work, and actually get better through time, and where I can freely learn how to do anything on my phone.
Webtop, for me, is something I will be promptly fixing and hacking to bits as time permits.
4G upload rate+inbuilt linux box = i want 2.
My only question remains, what isn't possible on our Bionic?
- No trackball means terminal programs or emulated keyboards typically won't be able to use necessary shortcuts. Ouch,
- Locked bootloader means something I'm not certain how to explain. I will update this note as somebody can explain more pointedly.
And feel free to contribute any elephants or brick walls you might notice about our pimping Droid Bionics. Keep it hacky fellow consumers.
Reserved so I can be the judge of what isn't possible on my damn phone!
(Maybe, I might suggest a different title and moving this to Development for better eyes to contibute?)
I am selling mine tomorrow and buying a rezound for now or maybe trade that in for the GNex. All depends on if the RZD gets s-off in the next couple weeks. I have never had a phone with a locked bootloader, and if you have only had phones with locked bootloaders you don't know what you are missing. I do, and it rubs me raw. Exact reason I went back to my tbolt, and found it to be a better phone. Unlocked bootloader. Will probably never buy a Moto phone again. This has soured my taste for their phones.
Sent from my ADR6400L using XDA App
I've been trying to figure out on the forums which device has which path to get root and wow it doesn't make sense to me. I'm no noobie but I don't get all the updates and processes.
I just want root so i can use Xposed. i don't care about loading different roms or kernels.
I bought it from swappa. It has android version 4.4, system 140.44.5.ghost_att.en.US, Build 13.11.1Q2.X-69-3
this thing sucks HARD without root. there is so much you could do that you can't. It astounds me how diligently manufacturers and carriers are about preventing you from using the phone to its fullest. So i void a warranty, i don't care...
a10fjet said:
I've been trying to figure out on the forums which device has which path to get root and wow it doesn't make sense to me. I'm no noobie but I don't get all the updates and processes.
I just want root so i can use Xposed. i don't care about loading different roms or kernels.
I bought it from swappa. It has android version 4.4, system 140.44.5.ghost_att.en.US, Build 13.11.1Q2.X-69-3
this thing sucks HARD without root. there is so much you could do that you can't. It astounds me how diligently manufacturers and carriers are about preventing you from using the phone to its fullest. So i void a warranty, i don't care...
Click to expand...
Click to collapse
I have an AT&T Moto X running Kit Kat 4.4 (from OTA) and I'm also not clear on whether I can root my phone. I'm also unclear about whether I can unlock my phone
I would also appreciate guidance and direction.
Many thanks!
The AT&T branded Moto X cannot be unlocked, but the GSM unlocked DE will work on AT&T and is unlockable. The TMobile Moto Maker Moto X will work on AT&T and has an unlockable bootloader, too, but if you unlock the bootloader on it, your warranty is void. So I would stick with the GSM unlocked DE. There may be some issues with 4G LTE on AT&T using the TMobile devices but I am not sure. That is probably covered in the forum somewhere if there are any issues.
Click to expand...
Click to collapse
Okay, so I can root, but not unlock. I think I'll wait till an easier and simpler root method is developed like there was for my Samsung GS2.
I appreciate the guidance.
CartlandSmith said:
We are lucky to even have this method. Google is making Android more and more secure by incorporating SELinux. If a root method for 4.4.2 is ever found, it will likely be even more complicated.
4.4 Security Enhancements
Also, the dev who came up with the current root method, jcase, is not interested in finding a root method for Motorola phones running 4.4.2.
So rooting now is likely your only chance at rooting. If you take the 4.4.2 OTA unrooted, it is doubtful you will ever be able to gain root because the 4.4.2 bootloader is not downgreadable.
Since the developer edition phones are so readily available from Motorola at such a good price and since only AT&T and Verizon retail/customized phones are not unlockable, there isn't much interest in trying to find a way to root locked Motorola phones running 4.4.2. Sprint, US Cellular and TMobile retail/customized Moto X's are unlockable as are the developer edition Moto X's.
Click to expand...
Click to collapse
Thanks for the thoughtful and informed reply, Cartland. My last phone was a Samsung GS2 and it was easy to root (all automated). Though I have rooted and flashed ROMs on a number of phones, this process seems complicated and readily screw-upable (not a real word, I admit). I like being rooted, so I can flash tweaked-out ROMs that are better than stock.
I'll explore rooting more and see how comfortable I am with it.
Much appreciated.
CartlandSmith said:
We are lucky to even have this method. Google is making Android more and more secure by incorporating SELinux. If a root method for 4.4.2 is ever found, it will likely be even more complicated.
4.4 Security Enhancements
Also, the dev who came up with the current root method, jcase, is not interested in finding a root method for Motorola phones running 4.4.2.
So rooting now is likely your only chance at rooting. If you take the 4.4.2 OTA unrooted, it is doubtful you will ever be able to gain root because the 4.4.2 bootloader is not downgreadable.
Since the developer edition phones are so readily available from Motorola at such a good price and since only AT&T and Verizon retail/customized phones are not unlockable, there isn't much interest in trying to find a way to root locked Motorola phones running 4.4.2. Sprint, US Cellular and TMobile retail/customized Moto X's are unlockable as are the developer edition Moto X's.
Click to expand...
Click to collapse
CartlandSmith said:
It takes some time to do it. I did it on a relative's phone. There are unfortunately some pointers that are left out of the original posts that help everything to go smoothly if you know them. You can find them in the threads, but the threads have gotten so long it makes the process take longer when you have to read through them to find all of the pointers.
If you are only flashing using RSD Lite - RSD Lite will stop you from bricking your phone.
You are never going to get a simpler method with a locked bootloader Motorola phone - it is only going to get harder and I predict the devs won't invest much energy in it going forward because it is just not worth it when there are developer editions available to us. I think those that are doing it get a kick out of it, but when it becomes too time consuming, well, they have their day jobs they have to make sure they focus enough time on to pay their bills. They get donations for this sort of thing, but I am sure the donations don't compensate them very well for all of the time they take trying to find exploits the more secure Android becomes.
With a locked bootloader, you can't flash ROMs because you don't have a custom recovery. But what you can do it use Xposed Framework and its modules like Gravity Box if you are rooted.
I spent some time this weekend rooting a relative's Verizon Moto X with a locked bootloader due to the 4.4.2 OTA coming. You have some breathing room on AT&T right now to root, but don't wait too long or you will lose the opportunity once the OTA comes.
Click to expand...
Click to collapse
I don't think I have the time or energy to go through the process of finding those pointers and then going through the root method. I'm wondering if anyone will compile those pointers (as you suggest, I have noticed with previous rooting and flashing methods, some key steps aren't described which can cause major problems).
A clarification. You say that if I just want to flash ROMs, I can use RSD Lite. But then you say that with a locked bootloader, you can't flash ROMs.
I do appreciate your taking the time.
POINTER - sell or trade your phone for a Dev edition
It is difficult to root if you can't unlock your bootloader. There is a thread in this forum telling you how to root your device with both locked and unlocked bootloader.
Rooting this device isn't difficult. If you can read and type verbatim, letter for letter, you can get root. People need to stop psyching themselves and others out.
CartlandSmith said:
Yes you can get root, but it takes a bit of work
First you have to downgrade to 4.2.2 by flashing the sbf firmware for your device.
Click to expand...
Click to collapse
can you specify what sbf is? searching didn't help. Try not to use so many acronyms for us dummies.
CartlandSmith said:
Then use RockMyMoto to get root on 4.2.2. Then use MotoWPNoMo to disable write protection.
Then reflash 4.2.2 and use SlapMyMoto.
Click to expand...
Click to collapse
do i use ODIN? what do i use to flash?
CartlandSmith said:
You will be rooted on 4.4 and write protection will be disabled when you are done with all of that.
Once you have root, be sure and freeze MotorolaOTA to stop the 4.4.2 OTA. If you take the 4.4.2 OTA, you may keep root, but write protection will be enabled.
Click to expand...
Click to collapse
Does motorolaOTA automatically download the latest updates and install them without warning you?
thanks for giving me hope!
EDIT: does anyone know if http://forum.xda-developers.com/moto-x/orig-development/script-root-moto-x-root-script-locked-t2603051 will work?
I'm getting close to knowing what to do!
But the individual steps are not very well written.
For example on the RockMyMoto page, he just starts giving you commands. He doesn't tell you what to type them into. In the video, everything is already open. I tried the command in cydia impactor and it didn't do anything. I though maybe you do it in adb, I don't really know what that is but I found adb.exe and launched it but the command window it opens goes through a bunch of commands and then closes. I can't even get past step one because he never said how he got to the point where he starts!
CartlandSmith said, in the third post, that i am supposed to reflash 4.2.2 at the end.. Did he mean 4.4? Or 4.2.2 then slapmymoto then take 4.4 over the air?
It would be really helpful (to me at least) if someone could put step by step instructions. Like humiliatingly degradingly redundant instructions for a complete idiot. I will put them up if I ever figure it all out. It's so frustrating when the instructions are so detailed from where they start, but they never show you how they got to where they are.
Thanks to everyone for the help.
EDIT: probably stupid question but does the phone ever need to be connected by USB? none of the posts mention it but all other devices i've used needed it. adb (here is a tutorial)/ isn't recognizing my device with USB connection or not. Both connected to same router, all drivers and everything updated, Debugging enabled...
No offense intended...at all....but if you value your phone, you really need to study up and read LOTS of stuff here. Until you understand what you are about to do, don't do anything.
Just trying to save you from a bricked phone. You seem very unsure of everything at this point. No one can post anything here that isn't already covered in the guides. Look at the stickies, complete Moto x guide is there.
Good luck.
Sent from my Nexus 5 using Tapatalk
Hmm i rebooted my computer and factory reset my X and now everything is connecting. Guess you should always try the IT Crowd's advice before doing anything else lol
I agree that everything is covered on this site, it's just not organized.
It seems unorganized when you don't understand. Read enough of it and it all makes sense eventually. This has everything about bootloaders, rooting...etc. BUT, you need to know what applies to your situation. And again...that comes when you understand the stuff.
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my Nexus 5 using Tapatalk
CartlandSmith said:
It's even more clear how unorganized the info here is the more educated you become.
The thing that becomes the most clear eventually is how much misinformation is posted.
Sorry but the "it only appears disorganized and unreadable and full of misinformation" because you don't understand it won't fly with those of us who do understand it.
Click to expand...
Click to collapse
The OP of the thread I linked is well organized. Its about the only one that is. Its also stickied, so should be incredibly easy to find.
As far as misinformation goes, that's due to people being quick to post advice when they clearly don't have a handle on this stuff themselves.
How to avoid the clutter and misinformation? Maybe point people to good threads that already exist instead of filling new ones with more misinformation. No? Or God forbid, suggest they search for the information that already exists? Instead of helping to grow yet another repeated thread with both good and poor information within it.
Xda's number one rule was created for a reason. To keep clutter and thread after thread of similar content to a minimum. A lot of inaccurate information gets repeated over and over as well. But, so many refuse to search cause its too much work, and just as many others condone this behavior by answering.
I know most don't agree with what I'm saying, as the forums prove with the repeated information here in truck loads. And I also know when any of us remind people of rule number one here on xda....we're called trolls, flamers and much worse....even when the reminder was posted respectfully.
So who exactly are the flamers? LOL
Its looking like reminding members to search and read and actually help them help themselves is becoming a dangerous practice. I'm tired of the misinformation and cluttered forums....and if reminding is just going to start drama at every turn, I suppose reporting the offenders is the easier option. Tho not my first choice.
But if you read this carefully, you'll see I'm completely agreeing with you. LOL. So lets agree to agree and leave it at that.
And as a member who's been around a while, I won't stop doing my part to try to cut down the misinformation and lack of respect for the xda rules. Not abiding by rule number one is EXACTLY why the mess of confusing information exists. You see that, right?
If the newer members want to make me the bad guy for this, fine. I'll be the bad guy.
And I help more people here than most as well.....but that's forgotten if you disagree with anyone or remind anyone of the rules here. Fine. Again.....call me the bad guy. Better get used to it too, I'm not going anywhere.
I'd apologize for the off topic, but this thread should have been closed anyway.
Have a good one!
Sent from my Nexus 5 using Tapatalk
CartlandSmith said:
The most confusing thing of all is why someone with a Nexus 5 self-appoints themselves to be the "hall monitor" of the Moto X forums. *shrugs*
Click to expand...
Click to collapse
Um, perhaps I own both.
How bout you drop it and stop commenting on multiple posts of mine since you appear to dislike the things I say. K?
Try the ignore member feature.
Sent from my Nexus 5 using Tapatalk
Please search before posting
Check the sticky guides before asking questions about rooting
Thanks
FNSM
kennyglass123 said:
Please search before posting
Check the sticky guides before asking questions about rooting
Thanks
FNSM
Click to expand...
Click to collapse
Ninja'd .....:good:
EDIT: Let's let the dev's have their fun without a bunch of newbs poking in on them. Sorry, devs.
Probably don't want this info to get out to the entire Internets anyways.
CZ Eddie said:
Hmmm..........
http://forum.xda-developers.com/showthread.php?p=51983540
No, you don't have root/unlock for ATT S5.
But...... hmmmm...
**** DO NOT POST IN THAT THREAD. IT IS A DEVELOPERS-ONLY THREAD. DON'T BE A DORK AND POST IN IT.
Click to expand...
Click to collapse
Pretty exciting. I am not a dev. so I dont really know how to distinguish between what exactly is going on, but a little progress and excitement is always good for the community. Not to mention the respect and bounty these devs will get once something major actually does happen.
EDIT: Let's let the dev's have their fun without a bunch of newbs poking in on them. Sorry, devs.
Probably don't want this info to get out to the entire Internets anyways.
CZ Eddie said:
Basically, evilpotatoman located a much-wanted Qualcomm tool that could possibly lead to finally unlocking the bootloader of S4, S5 and Note 3 (and others). *Possibly being the key word.
At the moment it's still not possible, but the tool apparently gives them a huge leap forward in development towards this goal.
They've been looking for something like this for a few years now I believe.
I'm not a dev, don't pretend to be one. The extent of my "development" is writing a few scripts. lol. So remember that I may be misunderstanding some things here. :good:
There are a bunch of files attached to the thread.
But none of us should bother downloading them because you have to be an ultra-dev to know how to use them.
Click to expand...
Click to collapse
My understanding i that this is the SDK for the SoC on the S5 and other phones. It includes a qualcomm dev signing cert but I'm almost 100% certain that no production phone from AT&T will accept BL's signed by the qc dev cert (or someone would have used it to sign one of the unlocked BL's by now plus if that were the case my guess is qc would be freaking out and sending takedown notices by now). So basically if Samsung or AT&T were to provide the signing key or somehow we were to brute force it(very unlikely) we would now be able to easily sign packages for the phone. So while helpful, without the signing keys it doesn't really do anything except provide more insight into how the whole secure boot process works.
http://forum.xda-developers.com/showthread.php?t=2692167&page=11
cciechad said:
My understanding i that this is the SDK for the SoC on the S5 and other phones. It includes a qualcomm dev signing cert but I'm almost 100% certain that no production phone from AT&T will accept BL's signed by the qc dev cert (or someone would have used it to sign one of the unlocked BL's by now plus if that were the case my guess is qc would be freaking out and sending takedown notices by now). So basically if Samsung or AT&T were to provide the signing key or somehow we were to brute force it(very unlikely) we would now be able to easily sign packages for the phone. So while helpful, without the signing keys it doesn't really do anything except provide more insight into how the whole secure boot process works.
Click to expand...
Click to collapse
Qc sent the takedown notice...dun dun duuunnn
Sent from my SAMSUNG-SM-G900A using Tapatalk
Hi everyone!
I heard a lot of whining about locked bootloaders and answers just to pay for unlock and etc. However no so long ago in august on xda appeared http://www.xda-developers.com/android/qualcomm-security-exploit-djrbliss/ post about new exploit in quallcom soc's which should obviously affect our phone. This could really help for people like me with locked bl.
So has anyone heard something about using it IRL?
Arstorm.Z said:
Hi everyone!
I heard a lot of whining about locked bootloaders and answers just to pay for unlock and etc. However no so long ago in august on xda appeared http://www.xda-developers.com/android/qualcomm-security-exploit-djrbliss/ post about new exploit in quallcom soc's which should obviously affect our phone. This could really help for people like me with locked bl.
So has anyone heard something about using it IRL?
Click to expand...
Click to collapse
There is no unofficial unlock of bootloaders available
This has been talked about before
If you read the last paragraph of the article you linked to (Seen here http://prntscr.com/4ph7dk) you will see that although the vulnerability was found it is also not going to be released to the general public, but given to the OEMs so they can fix it.
While this is a notable discovery, it poses no immediate threat since Rosenberg did not release his exploit to the public, which allows manufacturers to patch it before any serious damage is done. Have a look at his full report in this summary image.
Click to expand...
Click to collapse
Also, there should be no advertising of paid for services on XDA, especially since if you can unlock your bootloader it is free to do it the official way and if anyone is taking your money for an unofficial unlock you are most likely being conned because there is no unofficial unlock.
Thank you for the reply! Unfortunately highly likely there is no official way to unlock my bl. My phone is sim-free but bl unlock is not allowed so I have no idea how to unlock it.
Also I checked comments section and found "On the summary page are enough information for any dev to write a exploit " http://www.xda-developers.com/android/qualcomm-security-exploit-djrbliss/#comment-1538589467
I'm just worried because after the end of support from sony there will be no possibility to switch to newer versions of android.