Related
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
Hello everybody!
I'm a LG G2 user, but i'm trying to unite all dissatisfied LG users to sign up to my petition, for more informations check my G2 thread (http://forum.xda-developers.com/lg-g2/general/petition-possibility-to-unlock-t2832013) or just read the quote from it:
Hello!
I don't know, maybe someone remembers me from P880 forum
Whatever - in that time the 4X HD had locked bootloader which no one was able to unlock it, so I decided to make a petition about it (http://forum.xda-developers.com/showthread.php?t=1852721). We succeed and we could unlock the bootloader via fastboot oem unlock in Jelly Bean update.
Now LG did it again, their G2 and G3 flagships as well as some other devices are locked as hell again. I decided today to reopen my petition and share this message to You guys so maybe we could get the unlockable bootloader again, or at least a way to unlock it like it is for example HTC phones.
Here's the link to the petition:
http://www.change.org/petitions/lg-...opportunity-to-unlock-bootloader-in-lg-phones
Let's have at least some hope for it, so we could get easier development and also G3 development could rise.
My reopened petition has 4031 supporters (for now) so it should be a little visible
Click to expand...
Click to collapse
Link to petition:
http://www.change.org/petitions/lg-...opportunity-to-unlock-bootloader-in-lg-phones
Individual emails have also the meaning. If You have a minute, please send emails to these addresses, also don't forget to mention about our petition:
[email protected]
[email protected]
(to moderators: yes, it's my copy/paste i make on few LG phones' sections, I don't spam, I just share the message to LG users and want to do something for community as I did in the past)
EDIT: I'm posting in G3's petition thread to prevent (my) spam, also G3 community is the most active, so that's why I decided to keep posting and updating there:
http://forum.xda-developers.com/lg-g3/general/petition-possibility-to-unlock-t2832032
Good idea, but these never work. I've seen a bunch of petitions against Samsung with thousands of signatures just get ignored. By the way I will sign it just to support this though
kintwofan said:
Good idea, but these never work. I've seen a bunch of petitions against Samsung with thousands of signatures just get ignored. By the way I will sign it just to support this though
Click to expand...
Click to collapse
Did You read my quote? It worked, I was one of these people who had 4X HD which was locked as f*ck on ICS, because damn NVIDIA security, just check my old thread on P880 section, some of last posts there
*sign*
reas0n said:
Did You read my quote? It worked, I was one of these people who had 4X HD which was locked as f*ck on ICS, because damn NVIDIA security, just check my old thread on P880 section, some of last posts there
Click to expand...
Click to collapse
Ya I'm signing it because yours worked last time. I was saying I've seen lately petitions with much more signatures ignored. That was also Samsung phones so maybe LG actually cares about their customers.
kintwofan said:
Ya I'm signing it because yours worked last time. I was saying I've seen lately petitions with much more signatures ignored. That was also Samsung phones so maybe LG actually cares about their customers.
Click to expand...
Click to collapse
I saw the same thing on the SG4. And on the Moto RAZR HD maxx , Moto RAZR maxx. Not to be discouraging but in these days and times with so many people learning to mod and how to take phones to other carriers , and all the simple one click root / unlock / recovery methods out there its becoming so easy for almost anyone to do what we used to have to do with cmd prompt adb and making boo table disc of Linux just to root or install whatever. These carriers and manufacturers are just safe guarding against warranty claims and losing a subsidized phone to another ..... I understand .... Do I think its right ...HELL NO My phone I paid for it don't tell me how to use it. But.....my phone I paid for it and would I want my 10 year old son to be able to do this stuff without the knowledge of how ? Nope Cuz in the end when he bricks it and I need him to have a phone when he goes off around the neighborhood or stays at a friends then guess what I gotta eat the cost. So I believe I like the idea that he can't mess it up if its not unlocked or rooted. But that should also be left up to the purchaser of the device.
I signed it, but I dont expect anything to become of it.
Signed. Good luck
SIGNED!!
I love a good petition, signed.
Sent from my LG-D959 using XDA Free mobile app
#SIGNED
Signed
Signed
signed
PLEASE READ!!!
I'm taking this action to the next level, I want to make this as public as possible, so maybe LG finally will do something!
Please upvote this reddit topic on /r/Android, everyone has to hear about it, LG must change their behaviour like Motorola did!
Here's the link:
http://pl.reddit.com/r/Android/comments/2h8edy/support_the_petition_to_force_lg_to_release_the/
we need to push it to the mainpage!
Signed...
CyboLabs is Proud to present
Open Bump!
What is Open Bump?
Open Bump is a recreation of the closed source Bump project run by Codefire.
It will allow you to "sign" your boot images in the same way that Codefire does it, only you don't need an internet connection.
Click to expand...
Click to collapse
What Open Bump is NOT
lets get the obvious out the way. It won't axe murder you.
It is not a direct reverse engineer of Codefire's implementation. I found the key and iv on my own
The magic bytes were taken from Codefire's method however. If anyone has insight has to how they were found, please shout up.
It does NOT take your private data so you can use it. Tin hatters feel free to double check
Click to expand...
Click to collapse
How did I find this out
I had a general idea of what to look for, having heard that the exploit is related uicc, and is signed with a cipher.
Dropping the aboot image in to Ghex led me to finding a reference to "uiccsecurity". Using the bytes around this, I found a repeat of 32 bytes, which was followed by 16 bytes which formed something that resembled "SecureWallpaper".
As you can probably guess, this was mainly trail and error backed by common sense and logical thinking.
you can programmatically find these values with the python script:
Python:
aboot_name = './aboot.img'
aboot = open(aboot_name, 'rb').read()
key_end = aboot.index('uicc')
key_start = key_end - 32
key = aboot[key_start:key_end]
sec_key_start = aboot.index(key, key_end)
iv_start = sec_key_start + 32
iv_end = iv_start + 16
iv = aboot[iv_start:iv_end]
deciphering some already generated "signatures" proved that these were the key and iv used for "signing" the images.
Click to expand...
Click to collapse
What is coming next?
Inspecting the signatures that were originally uploaded and the ones that people can generate now, I found only one pattern.
The only similarities were the first 16 bytes of each "signature". I believe that only the magic number is needed, and none of the garbage that follows. This has been confirmed by the LG G3 dev from CyanogenMod, Invisiblek Done
Click to expand...
Click to collapse
How to use it?
I don't know how well this will run on anything other than linux, so for now.. I won't talk about it.
First, ensure you are using python2
then run the script
Code:
python2 open_bump.py "/path/to/boot.img"
flash the output, and enjoy
Click to expand...
Click to collapse
Thanks to:
Obviously, this wouldn't have been possible without Codefire since I wouldn't have known where to look, or that it was exploitable. And it was them that found the magic key.
Big thank you to @pulser_g2, who offered invaluable input on cryptography
Big thank you to @invisiblek, who I mercilessly kanged the main part of the image padding script from
note:
The original part of finding this information out was done on my own with guidance from pulser. The final results of this are posted above.
XDA:DevDB Information
Open_Bump, Tool/Utility for the LG G2
Contributors
cybojenix
Source Code: https://github.com/CyboLabs/Open_Bump
Version Information
Status: Beta
Created 2014-11-23
Last Updated 2014-11-23
Thanks, thats great news to have an open source tool here!
Do you see any chance that this could be integrated into CWM/TWRP so that the recovery rom could bump the boot/recovery images before flashing?
Because the boot/recovery.img has to be extracted from the ROM-zip before flashing, bumping it here would make sure that the phone can boot the image even with the newer bootloader.
This would be great for rom-devs since they don't have to change anything and it would even bump roms that are not maintained anymore.
g4rb4g3 said:
Thanks, thats great news to have an open source tool here!
Do you see any chance that this could be integrated into CWM/TWRP so that the recovery rom could bump the boot/recovery images before flashing?
Because the boot/recovery.img has to be extracted from the ROM-zip before flashing, bumping it here would make sure that the phone can boot the image even with the newer bootloader.
This would be great for rom-devs since they don't have to change anything and it would even bump roms that are not maintained anymore.
Click to expand...
Click to collapse
simple answer, this can be added to the build step really easily. See this commit
edit:
of course it may be useful to make a c program to do this.... I shall think on it.
Propably stupid question but i ll give a shot. Since we have the magic key we cant just skip the bump stuff totally? As i can understand, i dont wait official developer team join the bump train, thats why the damn development of the device is really back while the hardware is more than capable.
**To the OP i wish i could give you a thousand likes sir!
After getting the bootloader may be open G3؟؟
Why not use the original Bump?
Quote:
Codefire has been extremely vague about their method, obviously to prevent someone else replicating their results.
They are also storing people's data unnecessarily, and even adding some information relating to the user in to the "signature", possibly for tracking purposes.
As a result of it being an external service, many reputable teams (which won't be named unless they want to be) have said they will not use it, and would rather wait till LG releases the official unlock method.
Finally, Codefire have said the sha1sum of the boot image is required. Whether they knew or not, it is NOT required, and I will be changing this tool to compensate for that.
Click to expand...
Click to collapse
Happy you found a new exploit for us builders and devs, just feel like you kinda disrespected codefire team by accusing them of things before actually talking to them, seems a bit counter productive, this may piss them off and next device you can kiss new exploits by them good-bye,
just my 2 cents on the matter,
i'd remove the line...
in any case thank you very much, i will add it to my build script
---------- Post added at 08:34 PM ---------- Previous post was at 08:29 PM ----------
nikosblade said:
Propably stupid question but i ll give a shot. Since we have the magic key we cant just skip the bump stuff totally? As i can understand, i dont wait official developer team join the bump train, thats why the damn development of the device is really back while the hardware is more than capable.
**To the OP i wish i could give you a thousand likes sir!
Click to expand...
Click to collapse
"Bump stuff" has nothing to do with users, the devs and builders do the "bumping", and development of the G series has nothing to do with bumping, it just takes time to bring everything up
Good job cybojenix. (moderator edit: watch your language please)
Way to ruin a good thing.
I'm done with Android now. You can do it all now - since you obviously know better than me and everyone else.
I don't appreciate people trying to blackmail me - EnderBlue and Cybo both.
Don't believe me? http://hastebin.com/gulumezawi.txt
Good job guys. Way to ruin unlocks for all future LG phones.
If I *EVER* decide to come back, I will not be releasing anything as free or open source. You've sullied my impression of the open source community. Anything I do will be private releases from now on.
LG hadn't patched Bump, and they were going to leave it alone for us as long as we kept it as a service.
Well, looks like that's over and done with.
Bump included a hash of the image that you uploaded and a hash of your developer ID, and some random junk bytes. That's all. It's exactly what we said it was doing.
Well, hey, now you're free to take over and write roots and unlocks for all LG phones since you obviously have the talent to do so.
Let's be honest though, without my team's hard work that you stole, you wouldn't have been able to do any of this.
But you knew that, you're just a bottom feeder.
I don't get angry often at all- but congrats! You've succeeded in making me mad! Achievement unlocked!
I'm done. Your turn.
EDIT: Also, you know you can't open source your project either considering it contains 'stolen' LG crypto keys. https://github.com/CyboLabs/Open_Bump/issues/1
Have fun with that one.
thecubed said:
Good job cybojenix. (moderator edit: watch your language please)
Way to ruin a good thing.
I'm done with Android now. You can do it all now - since you obviously know better than me and everyone else.
I don't appreciate people trying to blackmail me - EnderBlue and Cybo both.
Don't believe me? http://hastebin.com/gulumezawi.txt
Good job guys. Way to ruin unlocks for all future LG phones.
If I *EVER* decide to come back, I will not be releasing anything as free or open source. You've sullied my impression of the open source community. Anything I do will be private releases from now on.
LG hadn't patched Bump, and they were going to leave it alone for us as long as we kept it as a service.
Well, looks like that's over and done with.
Bump included a hash of the image that you uploaded and a hash of your developer ID, and some random junk bytes. That's all. It's exactly what we said it was doing.
Well, hey, now you're free to take over and write roots and unlocks for all LG phones since you obviously have the talent to do so.
Let's be honest though, without my team's hard work that you stole, you wouldn't have been able to do any of this.
But you knew that, you're just a bottom feeder.
I don't get angry often at all- but congrats! You've succeeded in making me mad! Achievement unlocked!
I'm done. Your turn.
EDIT: Also, you know you can't open source your project either considering it contains 'stolen' LG crypto keys. https://github.com/CyboLabs/Open_Bump/issues/1
Have fun with that one.
Click to expand...
Click to collapse
First off, I didn't black mail. I gave your team notice about open sourcing it after reverse engineering the LG bootloader, not your "signatures".
It's your choice if you want to leave Android. Pinning the blame on me is somewhat childish though.
LG not patching Bump? That's a ludicrous statement, and even if it's true, it's good that this script got released. That way they know it should be patched, since having it a service clearly makes all the difference to them.
The hardest part of your teams work was getting the keys. If you know where to look, then it's easy enough to get engineering builds which I suspect contain the master magic bytes which you released.
I'm honestly shocked at your reaction though. I gave your team all the credit and stated which parts I did myself. The part about the service, and the deception was justified.
You tried to obscure something which by logic can't be obscured. That's how so many people realised they can just append the bytes to the image.
So which one would you rather have, LG not patching the exploit (as you so claim), and having an unknown number of people in china running around flashing custom boot images, or have everyone know how to do it to force LG to recheck their security measures.
What I did may not have been fantastic for the community, but what you did was insanely dangerous for the 90% of LG users.
All you did was make it so LG locks down the bootloader. And really 90% of users??? There probably isn't even 3 percent of the LG base on this website. All you did was screw everybody else over so you could have YOUR OFFICIAL CM.
As well people saying you didn't do enough and are still using there signing key as well as attacking it as well.
Way to think about yourself. You didn't care about the 90% or you wouldn't have done this.
I personally hope LG locks down the bootloader now. Go the way Samsung did and put an efuse on it and prevent downgrading. Hopefully all this happens with lollipop so you can screw over the rest of the LG crowd.
cybojenix said:
it's good that this script got released. That way they know it should be patched, since having it a service clearly makes all the difference to them.
Click to expand...
Click to collapse
"Hey let's potentially close all future LG unlocks and thus the chance to use CyanogenMod on future LG devices then. Just so I can get the current CM builds to say 'Official' and get a big pat on the back from the CM dudes who probably don't care about me too much."
Is that what went through your mind? That instant gratification and ignorance really shows who you are because that's exactly what I see from this OP of yours. Enjoy your 15 minutes of fame. You probably just killed a chance for years of it.
savoca said:
"Hey let's potentially close all future LG unlocks and thus the chance to use CyanogenMod on future LG devices then. Just so I can get the current CM builds to say 'Official' and get a big pat on the back from the CM dudes who probably don't care about me too much."
Is that what went through your mind? That instant gratification and ignorance really shows who you are because that's exactly what I see from this OP of yours. Enjoy your 15 minutes of fame. You probably just killed a chance for years of it.
Click to expand...
Click to collapse
Yes, because I've been such a massive supporter of cm. (sarcasm in case you didn't realise).
I started reverse engineering the bootloader for research purposes. If it was more complex than what I have said above, then I probably wouldn't have done this thread.
If it weren't for the fact that the magic stays the same across all signatures, then I also wouldn't have done this thread.
The response I got from them when I contacted them before releasing this was pretty much one of lack of care. So I went ahead and posted it.
I couldn't care less about fame. In fact there isn't really a lot I do care about, but I won't have the community alienated in to thinking the codefire service was such a great thing.
And once again, I refuse to take the blame for their team leaving Android.
whoppe862005 said:
All you did was make it so LG locks down the bootloader. And really 90% of users??? There probably isn't even 3 percent of the LG base on this website. All you did was screw everybody else over so you could have YOUR OFFICIAL CM.
As well people saying you didn't do enough and are still using there signing key as well as attacking it as well.
Way to think about yourself. You didn't care about the 90% or you wouldn't have done this.
I personally hope LG locks down the bootloader now. Go the way Samsung did and put an efuse on it and prevent downgrading. Hopefully all this happens with lollipop so you can screw over the rest of the LG crowd.
Click to expand...
Click to collapse
See my other post, I don't care about cm.
Fair enough, 3% are here, so this benefits the security of 97% of lg uses, if the claim that lg was alright with it running s a service is true.
Either way, I did nothing wrong
cybojenix said:
I couldn't care less about fame. In fact there isn't really a lot I do care about, but I won't have the community alienated in to thinking the codefire service was such a great thing.
Click to expand...
Click to collapse
So you only care about ruining good things, and other people's work?
Lol sorry I think I'm done with you. By cybo
savoca said:
So you only care about ruining good things, and other people's work?
Lol sorry I think I'm done with you. By cybo
Click to expand...
Click to collapse
Tbh I thought it would have been clear by now what I care about. Then again I may have been wrong about considering you one of the smart android people.
I care about learning and sharing knowledge. Which is precisely what this thread did.
cybojenix said:
See my other post, I don't care about cm.
Fair enough, 3% are here, so this benefits the security of 97% of lg uses, if the claim that lg was alright with it running s a service is true.
Either way, I did nothing wrong
Click to expand...
Click to collapse
I saw your PM to autoprime in IRC, it was "I am going to post what I found or you do, either way its going there", it wasn't lack of care, it was that you just stated a fact and left, it was a very rude unthoughtful thing to do, also don't try to BS everyone with your research, you and about 100 other people found the "magic keys", the problem is those "magic keys" were placed there by team codefire, you didn't find them, you found that they were using the key and copied their work, anything else you say is a lie, at least the other 99 people who found this had the basic respect to not post it unless the original team allowed it.
There was no reason to post this, their site was working fine, and if you used the API there was no problem of tracking since it just uses a UID to identify to the server.
at least admit you were wrong and say you are sorry, they won't fix anything but will gain you a minimum amount of respect
sooti said:
I saw your PM to autoprime in IRC, it was "I am going to post what I found or you do, either way its going there", it wasn't lack of care, it was that you just stated a fact and left, it was a very rude unthoughtful thing to do, also don't try to BS everyone with your research, you and about 100 other people found the "magic keys", the problem is those "magic keys" were placed there by team codefire, you didn't find them, you found that they were using the key and copied their work, anything else you say is a lie, at least the other 99 people who found this had the basic respect to not post it unless the original team allowed it.
There was no reason to post this, their site was working fine, and if you used the API there was no problem of tracking since it just uses a UID to identify to the server.
at least admit you were wrong and say you are sorry, they won't fix anything but will gain you a minimum amount of respect
Click to expand...
Click to collapse
Wrong, I stated that I was going to open source it, meaning the work of put in to getting the key and how it's used to get the original magic.
It was after that that I realised the final magic is the only thing needed. I actually worked out how to get the magic key a few hours ago, but since I don't have the right images, it won't be globally usable.
Fair enough, I apologise for pointing out the flaws in codefires service, and that they took it badly.
cybojenix said:
See my other post, I don't care about cm.
Fair enough, 3% are here, so this benefits the security of 97% of lg uses, if the claim that lg was alright with it running s a service is true.
Either way, I did nothing wrong
Click to expand...
Click to collapse
OK. If you did nothing wrong please do explain this
Enderblue-"well, would you be willing to open source it so we can have a official cm support?"
IoMonster-"so it would make storm already worse then what it is now? *paraphrasing for language
IoMonster-"no"
Seems like be said he didn't want it open source but you still went ahead any way.
http://hastebin.com/gulumezawi.txt
And then you saying your going to push it for vs985 even after he said no.
I don't know who Enderblue is, and I'm not affiliated with him..
whoppe862005 said:
OK. If you did nothing wrong please do explain this
Enderblue-"well, would you be willing to open source it so we can have a official cm support?"
IoMonster-"so it would make storm already worse then what it is now? *paraphrasing for language
IoMonster-"no"
Seems like be said he didn't want it open source but you still went ahead any way.
http://hastebin.com/gulumezawi.txt
And then you saying your going to push it for vs985 even after he said no.
Click to expand...
Click to collapse
cybojenix said:
I don't know who Enderblue is, and I'm not affiliated with him..
Click to expand...
Click to collapse
It isn't like it matters if you are or not. It says right in the chat he doesn't want it open sourced. I'm sure about 99% of the people on here have seen that already and I'm pretty sure you have seen it as well.
It states right in the chat he didn't want it open sourced.
whoppe862005 said:
It isn't like it matters if you are or not. It says right in the chat he doesn't want it open sourced. I'm sure about 99% of the people on here have seen that already and I'm pretty sure you have seen it as well.
It states right in the chat he didn't want it open sourced.
Click to expand...
Click to collapse
but the chat wasn't with me, so your point is null
autoprime had ample opportunity to say "don't do it yet", or "go talk to IO". but no, no objections were made.
Codefire treated the service like any other company would treat their unlocking service, so I treated them like a company and showed how it was done.
XDA has become part of my morning routine now days. Getting up, eating and checking to see if any breakthrough came with the Sprint G4. I may just be blind, however I don't see anything coming soon. Granted it's a /newer/ phone which plays a huge role. Anyways does anybody know of anything relating to what's going on with the Sprint G4 rooting process or possible new ROMS that may be coming out if I didn't see a root already available?
Note: I'm also not the most knowledgeable when it comes to this but I know my fair share.
You should probably follow this thread for now:
http://forum.xda-developers.com/showthread.php?t=3163925
tourbound129 said:
You should probably follow this thread for now:
http://forum.xda-developers.com/showthread.php?t=3163925
Click to expand...
Click to collapse
Thank-you for the link! After I posted this I found another thread where a few developers have managed to get root with all carriers however it isn't necessarily the "easiest" way to succeed in their efforts. They just don't want so many bricked phones which I understand. However, thank-you again!
this crap is taking ridiculously long.
iiEatTurdz said:
this crap is taking ridiculously long.
Click to expand...
Click to collapse
Sprint G4 is already rooted, and chances of bootloader unlock are slim to none.
Tisch22 said:
Thank-you for the link! After I posted this I found another thread where a few developers have managed to get root with all carriers however it isn't necessarily the "easiest" way to succeed in their efforts. They just don't want so many bricked phones which I understand. However, thank-you again!
Click to expand...
Click to collapse
If you follow the directions carefully then its not so bad.
Does it have, got my Note 8 a week ago but just wondering has I have not seen anykind of movement for the US variant.
all sorts of threads and posts answer your questions..
Just search, do not be lazy
Oh wow, thanks before posting I searched and found nothing only for older versions using SamFail. Thanks anyways loooool glad to see a gooood comunity
PLUS I said that I didn't saw any kind of movement
@atrix_noob What firmware are you running ?
Alek7 said:
@atrix_noob What firmware are you running ?
Click to expand...
Click to collapse
It's on 8.0 May 1 security patch.
atrix_noob said:
It's on 8.0 May 1 security patch.
Click to expand...
Click to collapse
For the US 950U and 950U1 snapdragon there is no root for the May update. That is bootloader revision 4 and has no root at this time. Your best bet is to keep a eye on the samfail thread for updates.
If your past U3 were sol for now. I think theres only one guy working on a possible partial root. There are lots of apps for theming. Substranium and Good lock are great.
atrix_noob said:
Oh wow, thanks before posting I searched and found nothing only for older versions using SamFail. Thanks anyways loooool glad to see a gooood comunity
Click to expand...
Click to collapse
Dude.
Just search around.
Don't give us the 'lmao such a good community, how about you go and suck it because I don't want to research' attitude.
It's not our fault you couldn't be bothered to check for any activity and read around.
Plus people are tired of having others ask the same question hundreds of others have asked related to root, it's all about searching or reading.
Don't you think if someone found a way to root the newest firmware there would be a lot more sites talking about it?
Sarcasm aside, no, there is no root for Oreo Bootloaders (U4). Only Nougat with U3 or below.
luisramon17 said:
Dude.
Just search around.
Don't give us the 'lmao such a good community, how about you go and suck it because I don't want to research' attitude.
It's not our fault you couldn't be bothered to check for any activity and read around.
Plus people are tired of having others ask the same question hundreds of others have asked related to root, it's all about searching or reading.
Don't you think if someone found a way to root the newest firmware there would be a lot more sites talking about it?
Sarcasm aside, no, there is no root for Oreo Bootloaders (U4). Only Nougat with U3 or below.
Click to expand...
Click to collapse
Before posting I always use the search feature cause it's very usefull. Has you know there are multiple threads and forums and specifically a T-Mobile Model one and its pretty much dead. If YOU read above I said that I didn't see any kind of activity. Another one is that if you read more down below, I stated that all I could find is a SamFail one but it's pretty outdated. So I came here to the Questions & Answers area and posted this thread here to see if anyone had an idea of whats happening with the US models
I don't need for someone to come here and tell me
"Oh don't be lazy and use the search funtion"
Already stated on the first post. Sheesh
And yeah, thanks for the bootloader part.
atrix_noob said:
Before posting I always use the search feature cause it's very usefull. Has you know there are multiple threads and forums and specifically a T-Mobile Model one. If YOU read above I said that I didn't see any kind of activity. Another one is that if you read more down below, I stated that all I could find is a SamFail one but it's pretty outdated. So I came here to the Questions & Answers area and posted this thread here to see if anyone had an idea of whats happenind with the US models
I don't need for someone to come here and tell me " Oh don't be lazy and use the search funtion"
Alrready stated on the first post. Sheesh
And yeah, thanks for the bootloader part.
Click to expand...
Click to collapse
The thing is theres not much firmware differences between models. They might have slight baseband changes but they're all based on the same thing. So root that would work on a Verizon Note8 would work on a T-Mobile Note8.
And yes, the only one we have is sadly the V3 for those unlucky to update.
And I imagine people would check the last section of the thread to be on standby since apparently theres a new exploit that might (or might not) help.
This is why I assumed you didn't check first, but since you did (I didn't see that part), I apologize.
Amos420en said:
If your past U3 were sol for now. I think theres only one guy working on a possible partial root. There are lots of apps for theming. Substranium and Good lock are great.
Click to expand...
Click to collapse
Thanks for the heads up, I really like the root and all that stuff. Especially for getting rid of all T-Mobile crap on the phone. I'm a person that chages phone alot but I think I'll be giving this guy an exchange for another phone lol. I literally don't last a month with a phone has I like to test other brands and models
luisramon17 said:
The thing is theres not much firmware differences between models. They might have slight baseband changes but they're all based on the same thing. So root that would work on a Verizon Note8 would work on a T-Mobile Note8.
And yes, the only one we have is sadly the V3 for those unlucky to update.
And I imagine people would check the last section of the thread to be on standby since apparently theres a new exploit that might (or might not) help.
This is why I assumed you didn't check first, but since you did (I didn't see that part), I apologize.
Click to expand...
Click to collapse
Don't worry, I searched everywhere but nothing found. Sometimes you know, people spread rumors or someone may know of something that's been on progress but it doesn't come up on public threads.
I been rooting my phones literally ever since I had an Android phone and always do my reaserch before posting on forums, cause you know there's always the people that come and say "Use the search feature" and always try to avoid that.
And yeah, all I read about was on Nougat. So I'll just asume it's dead.
atrix_noob said:
Don't worry, I searched everywhere but nothing found. Sometimes you know, people spread rumors or someone may know of something that's been on progress but it doesn't come up on public threads.
I been rooting my phones literally ever since I had an Android phone and always do my reaserch before posting on forums, cause you know there's always the people that come and say "Use the search feature" and always try to avoid that.
And yeah, all I read about was on Nougat. So I'll just asume it's dead.
Click to expand...
Click to collapse
You switch phones a lot too? Same, heh. Went from having a Note 4 to iPhone 8 Plus, then Note 8, then iPX, then back to Note 8 (cause drawing), but to be fair, I do miss a little of Apple.
To be fair, it's not dead (yet) since the Oreo update landed pretty recently, plus the only tool we had for making it possible got executed pretty much, so I'd give it a little time.
And that search feature situation is a fair point.
Misterxtc said:
For the US 950U and 950U1 snapdragon there is no root for the May update. That is bootloader revision 4 and has no root at this time. Your best bet is to keep a eye on the samfail thread for updates.
Click to expand...
Click to collapse
Thanks for the tip. I'll keep an eye on it
luisramon17 said:
You switch phones a lot too? Same, heh. Went from having a Note 4 to iPhone 8 Plus, then Note 8, then iPX, then back to Note 8 (cause drawing), but to be fair, I do miss a little of Apple.
To be fair, it's not dead (yet) since the Oreo update landed pretty recently, plus the only tool we had for making it possible got executed pretty much, so I'd give it a little time.
And that search feature situation is a fair point.
Click to expand...
Click to collapse
Yeah, I have had literally all flagship phones by now except for the Huawei P20.
Last Apple Device I had was the iPX, very good device but the atmosphere of the OS makes it pretty boring to me and get bored at it pretty quickly has you can't make any changes to the look of it.
I got this Note 8, exchanged it for my iPX. The guy that maked the deal with me gave me around 200 bucks and the Note for the iPhone lol.
I love the Note 8, super fast and love the big screen.