Related
I have read at least 50 disinformation type posts on this site about unlocking a branded Xperia (Verizion in my case) they all seem to be wanting me to pay money to Alejandrissimo or Jinx13 but when I click on those hyperlinks they are all "Invalid post" so what am I supposed to be finding here that I missed?
There is not any topic stickied that is describing how to unlock the thing & every article / forum post / google search I find is another disinformation post with no real evidence.
I know how to flash ROM's onto android using recovery loaders.
I know how to access the program menu's in various phones
I know what the CDMA spectrum is.
I'm not some newb making this post because I need my hand held step by step to do something.
I just need some real information
If anyone has a link to a real method or anything helpful please let me know
I have researched (and watched the welcome video) on this site to find an answer and I haven't found anything.
Thanks
-Jon
Ok, so the links to the unlockers in my thread are broken. Does it mean that my post has "disinformation"? Is there any other way to unlock the bootloaders? No to both, as far as I know. I'll try to fix the links, but seriously...
About why my post (or any other helpful resource about the matter) is not stickied, I don't know nor do I care. No one reads stickies anyway.
Logseman said:
Ok, so the links to the unlockers in my thread are broken. Does it mean that my post has "disinformation"? Is there any other way to unlock the bootloaders? No to both, as far as I know. I'll try to fix the links, but seriously...
About why my post (or any other helpful resource about the matter) is not stickied, I don't know nor do I care. No one reads stickies anyway.
Click to expand...
Click to collapse
By disinformation it would seem that some exists.
droid-life reported 4 months ago ashergray(XDA) found a method to unlock the bootloader.
Why none of the methods being released or talked about is beyond me.
Also I'm confused why the method is being charged for by others but not officially it would seem.
You have to pm users on the forum to arrange a sale. Why does a topic not exist for this purpose?
All this confusing data is leading to a big headache right now. I was hoping for answers and all I find is rabbit holes on this elusive topic.
Thanks for the reply tho.
Ashergray's method was dried out (it exploited a flaw, and the flaw was fixed).I mention ashergray in the thread, as it is only fitting, in the thanks part.
About why they ask to be contacted privately or publicly, it's their business... Is there something that should be cleared in my thread, aside of the links of course? I mean, I can try to rebuild the first post if necessary.
Logseman said:
Ashergray's method was dried out (it exploited a flaw, and the flaw was fixed).I mention ashergray in the thread, as it is only fitting, in the thanks part.
About why they ask to be contacted privately or publicly, it's their business... Is there something that should be cleared in my thread, aside of the links of course? I mean, I can try to rebuild the first post if necessary.
Click to expand...
Click to collapse
You could start off by explaining why in 7 months time the boot loader is sill locked.
Or why your links to the unlock threads are dead. Both of them.
Or how I'm supposed to unlock the bootloader if these users can't provide that service any longer.
Also you could mention why Sony. being developer and hacker supportive hasn't assisted in taking Verizon's clutch off the bootloader
It is rather annoying coming from Droid x where the device is locked down with a fuse but yet a wide array of custom roms exist that bypass the locked bootloader and then coming to this phone that appears to have not progressed beyond hello world.
So you tell me where to look for an unlock because I'm fresh out of searches and ideas.
Thanks
-jon
P.s I also wonder if the exploit you speak of was patched. Why not just flash to an earlier rom with the problem still existing.
You could start off by explaining why in 7 months time the boot loader is sill locked.
Or why your links to the unlock threads are dead. Both of them.
Or how I'm supposed to unlock the bootloader if these users can't provide that service any longer.
Also you could mention why Sony. being developer and hacker supportive hasn't assisted in taking Verizon's clutch off the bootloader
It is rather annoying coming from Droid x where the device is locked down with a fuse but yet a wide array of custom roms exist that bypass the locked bootloader and then coming to this phone that appears to have not progressed beyond hello world.
So you tell me where to look for an unlock because I'm fresh out of searches and ideas.
Thanks
-jon
P.s I also wonder if the exploit you speak of was patched. Why not just flash to an earlier rom with the problem still existing.
Click to expand...
Click to collapse
1) I kindly would like to ask how I'm supposed to know why the bootloader is locked. It's a corporate decision by carriers and Sony Ericsson in which neither I, nor anyone in this forum, have any input. If I had any hard data about why Sony Ericsson doesn't cooperate in the issue, I'd say it. However, I just don't know why, and I prefer not to speak of what I don't know.
2) It seems that both threads have been wiped out of existence (which I didn't know until right now), and I see that a new site appears in Alejandrissimo's signature (http://unlock-bootloader.com/) where he's promoting his services externally (not only the unlocking, but the TA fix and hard-brick fix too). I'd guess that somebody complained about these people making business inside XDA, but then I question the idea of wiping their threads like... months afterwards. At any rate, don't worry, you still can unlock your bootloader with Alejandrissimo's help.
3) On Droid X the bootloader was bypassed because Motorola wouldn't ever unlock it. The FreeXperia team, who had bypassed older Xperia models' bootloaders, decided against it as they saw the new policy of Sony Ericsson's (unlocking phones which didn't come with carrier subsidy). I could unlock my bootloader from day one, and I'm happy to say I've helped devs here therethrough.
4) The exploit was related to the website where you could unlock R800i models. In order to unlock your bootloader, you need to give your IMEI number (an ID code for GSM phones). Ashergray could convert MEID numbers used by CDMA phones into bogus IMEI numbers, which could be used to unlock the devices. Sony Ericsson patched the website so ashergray's trick didn't work anymore.
5) My thread is a "how-to", do you really expect me to add points 1), 3) and 4) to it?
4 months is an eternity for this kind of business. Exploits get fixed (look at the PSXperia case), policies change (like HTC's and Motorola's) and threads are wiped on short or no notice.
Logseman said:
1) I kindly would like to ask how I'm supposed to know why the bootloader is locked. It's a corporate decision by carriers and Sony Ericsson in which neither I, nor anyone in this forum, have any input. If I had any hard data about why Sony Ericsson doesn't cooperate in the issue, I'd say it. However, I just don't know why, and I prefer not to speak of what I don't know.
2) It seems that both threads have been wiped out of existence (which I didn't know until right now), and I see that a new site appears in Alejandrissimo's signature where he's promoting his services externally (not only the unlocking, but the TA fix and hard-brick fix too). I'd guess that somebody complained about these people making business inside XDA, but then I question the idea of wiping their threads like... months afterwards. At any rate, don't worry, you still can unlock your bootloader with Alejandrissimo's help.
3) On Droid X the bootloader was bypassed because Motorola wouldn't ever unlock it. The FreeXperia team, who had bypassed older Xperia models' bootloaders, decided against it as they saw the new policy of Sony Ericsson's (unlocking phones which didn't come with carrier subsidy). I could unlock my bootloader from day one, and I'm happy to say I've helped devs here therethrough.
4) The exploit was related to the website where you could unlock R800i models. In order to unlock your bootloader, you need to give your IMEI number (an ID code for GSM phones). Ashergray could convert MEID numbers used by CDMA phones into bogus IMEI numbers, which could be used to unlock the devices. Sony Ericsson patched the website so ashergray's trick didn't work anymore.
5) My thread is a "how-to", do you really expect me to add points 1), 3) and 4) to it?
4 months is an eternity for this kind of business. Exploits get fixed (look at the PSXperia case), policies change (like HTC's and Motorola's) and threads are wiped on short or no notice.
Click to expand...
Click to collapse
I've sent you some PM's to remove spam / offtopic / rant from the board.
Thanks for the information tho. I wasn't aware of any of that.
It seems that the name FreeXperia is a bit of a misnomer because my Xperia is going to be locked unless I pay 25$ apparently and thats sad when I only paid 90$ for the phone used. Could have been cheaper if I had bought bad ESN(I probably should have tried)
Imagine my surprise coming from Droid X to this phone where droid X has heaps of ROM's available to everyone for free and now I have to worry about getting this device to function at the same level as my old DX with Gummy JAR rom.
I Just wish the spirit of opensource would be in this sub-forum so we could have some real development in terms of flavors of roms and such.
Do you think their is any reason the developers are all charging fee's to show the method through team viewer? I thought it could have something to do with leaking the method and then it could be fixed in later updates. but then again maybe I'm wrong.
It's not that they "show" you the method. They "perform" the method for you. I'm not sure if you can do it with Omnius as well... but if you can, it will be marginally cheaper (unlocking credits are needed anyway!) and you have no assistance.
And about the old "why charge for open source software" dead horse, which is pointless here because there is no open source software involved (the bootloaders are closed-source, SETool is closed-source, and so on):
The Free Software Foundation said:
“Free software” does not mean “noncommercial.”
Click to expand...
Click to collapse
Additionally, as I said before, the FreeXperia team has this policy: http://forum.xda-developers.com/showpost.php?p=15253598&postcount=217
Logseman said:
It's not that they "show" you the method. They "perform" the method for you. I'm not sure if you can do it with Omnius as well... but if you can, it will be marginally cheaper (unlocking credits are needed anyway!) and you have no assistance.
And about the old "why charge for open source software" dead horse, which is pointless here because there is no open source software involved (the bootloaders are closed-source, SETool is closed-source, and so on):
Click to expand...
Click to collapse
Right on. I'm following you thus far.
Question tho. I read that sony was the best company for hackers and developers right now because they actually are allowing people to get access to the bootloaders. If all this is true why are they not assisting in the unlock of branded phones?
I might be wrong on this but aren't most peoples phones branded anyways through buying a contract?
and that leads to why FreeXperia didn't realize that and find an exploit / workaround for the bootloader being locked on branded phones.
If Setool and Omnius (or whatever it's called) are able to unlock the phones then why was sony. the engineer of the device not able to perform this same task?
Also I thought locking the bootloader violates the FCC regulation. open access provision so why didn't Sony assist the FCC to bypass Verizon.
God another douche, you pay 90 bucks for your phone and you think this community owes you something. Go complain to sony.
What do you mean, Sony can't do it? Of course they can. But they have chosen to do so only with R800i non-branded phones. Considering that they locked bootloaders without any official way to unlock them on previous Xperia models, that's a big step forward. That's as far as Sony Ericsson can go: on branded phones, they must obey what the carriers want.
Please do read Bin4ry's statement:
Now think about, if we would try to hack and bypass devices what will happen with future phones? In our opinion future phones will be locked down again like X10 was, eventually even more.
So why don't use the possibilties which are give by SE? Stick to their rules and hope for more support and maybe even nicer implementations (for example a accessable bootpartition from recovery).
We like SE devices, so we don't want to hijack this (i call it) "test" which SE drives with us?
I can fully understand that U.S. users which cannot unlock are quite unhappy with the actual situation, but sorry we will NOT work on anything else than development for officially unlocked devices! That was a team decision.
Click to expand...
Click to collapse
Note that this is costing them a lot of flak because they don't use R800x models for testing purposes either, and CM7 has many issues in R800x phones.
Also I thought locking the bootloader violates the FCC regulation. open access provision so why didn't Sony assist the FCC to bypass Verizon.
Click to expand...
Click to collapse
If this is correct, sue. I'm sure you'll have backing from everyone here.
Logseman said:
What do you mean, Sony can't do it? Of course they can. But they have chosen to do so only with R800i non-branded phones. Considering that they locked bootloaders without any official way to unlock them on previous Xperia models, that's a big step forward. That's as far as Sony Ericsson can go: on branded phones, they must obey what the carriers want.
Please do read Bin4ry's statement:
Note that this is costing them a lot of flak because they don't use R800x models for testing purposes either, and CM7 has many issues in R800x phones.
If this is correct, sue. I'm sure you'll have backing from everyone here.
Click to expand...
Click to collapse
So what your saying is that CM7 is not even worth flashing even if i was unlocked?
I would be better off to root / Titanium backup / delete bloat and be done with it?
Its a shame that they are forcing most people to stay stock SE/Verizon ROM because they are scared of the repercussions of angering SE. I think even if they stay inert that SE will eventually add more DRM to "protect" the devices.
About the lawsuit. I don't believe I'm the first person to mention it. Verizon has already been sued for 25 Million i believe on another occasion and it's been said by others that they are breaking FCC Regulation. The problem would be to get something done about it and I wouldn't have those resources.
The reason for the charge is very simple. In order to unlock our version of the Play (R800x), it takes a hardware dongle and the purchase of credits to allow the software to work. All you are paying Al or whoever for is the cost of the number of credits necessary to unlock your phone. They aren't getting rich off anyone.
If there was another way to unlock the Verizon version, someone would have posted it by now. There isn't, and that's just how it is.
There is a good spirit of free info sharing on this site. You might have to do a little digging but it's there. For example, how to unroot the R800x without having an unlocked bootloader. Takes about a whole 5 minutes to do.
EDIT: I do have to say that after digging around a bit more, I don't blame you for being perturbed. While no one owes us Verizon Play owners anything, there could have been something posted and sticky to make it a bit easier to find out what is going on. And perhaps have had a bit less condescension toward us as well. Must be that UK mentality toward us Colonists!
Re: Droid X vs XPlay development -
Different phones from different brands on different carriers require entirely new learning to develop for, not to mention owning a device to work on. I'd say there's probably only about a dozen people worldwide putting in serious work on this phone.
That's not a lot. If you want more options, you may have to do it yourself.
Hi guys,
The project cheesecake thread is meant strictly for develpment where it is being researched how to unlock the bootloader of Defy. Hence anything other than dev should be kept outside or the thread gets spammed!
Lets continue the discusion here. I will try my best to keep updating the status here once a day. But owing to my schedule that may not be possible at times!
How and why to sue?:
We as owners of the device got full right for it and Moto by locking away the bootloaders is keeping us from using our device to the fullest! A detailed discussion is here in Moto forum which is worth a read.
See 47 CFR Sec. 15.21." in Page 63 of this document.
26-7: In India we may approach Consumer Forum.
Spamming links:
You can mention how much the Defy/Defy+ is used for dev and show this link to CM status (jordan/umts_jordan leads!)
Motorola community discussion for unlocking bootloader.
Facebook page and this post there
I think that we should try to interest some institution in the European Union. European Union draws attention to the rights of consumers. And the locked bootloader restricts the rights of users. We have "open" system - Android, bu we can use only versions from Motorola. The European Union may request Motorola to unlock the bootloader.
All these suing Motorola conversations are bs.
Motorola created device and sells it as is. Not being able to install latest and greatest does not restrict you to use phone's advertised features.
You can gain absolutely nothing by suing Motorola, because there is nothing illegal in not offering an ability to unlock bootloader. Not in Europe, not in India, China, etc.
yackoo said:
I think that we should try to interest some institution in the European Union. European Union draws attention to the rights of consumers. And the locked bootloader restricts the rights of users. We have "open" system - Android, bu we can use only versions from Motorola. The European Union may request Motorola to unlock the bootloader.
Click to expand...
Click to collapse
aed0101 said:
You can gain absolutely nothing by suing Motorola, because there is nothing illegal in not offering an ability to unlock bootloader. Not in Europe, not in India, China, etc.
Click to expand...
Click to collapse
Ok, but what about the public promise - Motorola said they will remove the lock. This kind of announcement could encourage many users to purchase products of Motorola. But bootloader are still locked - the company deliberately misled customers. It is an unlawful act (providing false information about a product, which may affect the decision to purchase). Anyone who bought a Motorola product after the bootloader announcement, you may feel cheated.
yackoo said:
Ok, but what about the public promise - Motorola said they will remove the lock. This kind of announcement could encourage many users to purchase products of Motorola. But bootloader are still locked - the company deliberately misled customers. It is an unlawful act (providing false information about a product, which may affect the decision to purchase). Anyone who bought a Motorola product after the bootloader announcement, you may feel cheated.
Click to expand...
Click to collapse
Do you have any copy of the public promise?! Will add it to the first post
Excellent.
Go ahead you are with us!
yackoo said:
Ok, but what about the public promise - Motorola said they will remove the lock. This kind of announcement could encourage many users to purchase products of Motorola. But bootloader are still locked - the company deliberately misled customers. It is an unlawful act (providing false information about a product, which may affect the decision to purchase). Anyone who bought a Motorola product after the bootloader announcement, you may feel cheated.
Click to expand...
Click to collapse
Jep, this makes far more sense to me than suing just because the bootloader is locked. Motorola is not the only brand that sells locked devices.
Also, if this still doesn't work, maybe talking to Google about the broken promise would help since they own Motorola now and they seem to have a more "open" policy than Motorola.
yackoo said:
Ok, but what about the public promise - Motorola said they will remove the lock. This kind of announcement could encourage many users to purchase products of Motorola. But bootloader are still locked - the company deliberately misled customers. It is an unlawful act (providing false information about a product, which may affect the decision to purchase). Anyone who bought a Motorola product after the bootloader announcement, you may feel cheated.
Click to expand...
Click to collapse
The public promise has no legal value. You can't sue Motorola for that, niether can you sue them for not unlocking the bootloader as Aed0101 said.
Regarding the law, they are in their full right and this class-action lawsuit idea will go nowhere at all. Just cut all this bull**** about the locked bootloader and move on...
Trust me, i want the bootloader unlocked just as much as you do. Either we do it ourselves eventually, either we never have one. End of story.
Motorola Defy, CM7 @ 1Ghz + CM9 multiboot
[Guide] Install double boot CM7 + CM9
[Guide][Root needed] Unsimlock your Defy
[Mod/Fix][APP]Messaging apps with ENTER button enabled!
Wow! You mean to tell me you know every obscure law regarding consumer products in every country that Motorola sells it's products? I'm impressed!
If someone thinks that they can find a crack in Moto's armor, let them. Who knows what we can gain by it. They just want to find a way to help our devs but maybe, don't know how to program.
crakeron said:
The public promise has no legal value.
Click to expand...
Click to collapse
I can't agree with that. We are talking about important functionality. Imagine, that the manufacturer says "next update will add feature X". You are looking for a device with such a function and you select Motorola - because he has to have this feature. After a while Motorola forget about the "problem". This is not a promise made by Mr. Smith, but by a huge corporation. It's a big difference.
yackoo said:
I can't agree with that. We are talking about important functionality. Imagine, that the manufacturer says "next update will add feature X". You are looking for a device with such a function and you select Motorola - because he has to have this feature. After a while Motorola forget about the "problem". This is not a promise made by Mr. Smith, but by a huge corporation. It's a big difference.
Click to expand...
Click to collapse
I agree with this comment!
Motorola has said they will start releasing tools to unlock bootloaders for its devices, started with Photon Q
http://androidcommunity.com/motorola-finally-unlocking-bootloaders-for-real-this-time-20120726/?utm_medium=twitter&utm_source=Connectandroid
S3nt fr0m my D3fy/w1u1 GB st4BL3
Motorola photon Q has boot loader unlocked..motorola announced
Maybe moto will say something like Defy is too old well only unlock new phones... motorola style loll
It has nothing to do with legal knowledge. It´s just common sense. Unfortunately, not everybody have it.
I guess the only way to gain something (if possible at all) is contacting both Motorola and Google.
visualist6x6 said:
Wow! You mean to tell me you know every obscure law regarding consumer products in every country that Motorola sells it's products? I'm impressed!
If someone thinks that they can find a crack in Moto's armor, let them. Who knows what we can gain by it. They just want to find a way to help our devs but maybe, don't know how to program.
Click to expand...
Click to collapse
yackoo said:
Ok, but what about the public promise - Motorola said they will remove the lock. This kind of announcement could encourage many users to purchase products of Motorola.
Click to expand...
Click to collapse
Moto never "promised" anything to unlock booloaders. In 2011 they said:
"In terms of your question – we completely understand the operator requirement for security to the end user, and as well, want to support the developer communities desire to use these products as a development platform. It is our intention to enable the unlockable/relockable bootloader currently found on Motorola XOOM across our portfolio of devices starting in late 2011, where carriers and operators will allow it.”
So, just an Intention to unlock where carriers and operators allow it. Trust me, a law suit is useless.
nidhish91 said:
Motorola has said they will start releasing tools to unlock bootloaders for its devices, started with Photon Q
http://androidcommunity.com/motorol...?utm_medium=twitter&utm_source=Connectandroid
Click to expand...
Click to collapse
Now this is getting interesting! This announcement deserves a new topic. I advise to do some spamming here:
http://community.developer.motorola...ader-discussion-board/td-p/22108?pubid=987654
Martijn1971 said:
So, just an Intention to unlock where carriers and operators allow it.
Click to expand...
Click to collapse
There are smartphones with unlocked bootloaders in European market. So carriers are not problem - unless we assume that carriers prohibit removing the lock only in devices of Motorola. But this is impossible.
Now this is getting interesting! This announcement deserves a new topic. I advise to do some spamming here:
http://community.developer.motorola...ader-discussion-board/td-p/22108?pubid=987654
Click to expand...
Click to collapse
Agreed! Defy has to be the second phone on their list, and spamming the forum maybe improves the chances of getting it there
Also, contacting Google could help. Maybe post it as official Android issue? Even if its specific to just one device, I've already seen things which were specific to other phones aswell.
Motorola sucks so bad We just want an unlocked bootloader, I don't think it's such a big task for them. We didn't even ask for official 4.0/4.1, we just want our bootloader unlocked...
When spamming Moto forums, post a link to the Cyanogenmod install stats page so they can see that Defy is in top 5 in all time installations of CM
In my country, Spain , the crisis ( and political corruption ) has affected our citizens. That's why there are initiatives such as the collection of requests with signature and there are a portal dedicated to it.
The portal ww.change.org and I say here because one of the requests is that Samsung annular Knox :
I can not put links because I have written very little on this forum and xda requires a minimum but is easy to put knox into de box "Buscar" and search and is the first in the list
All the world know : "Unity is strength" .
This website has won several successes.
I apologize for my bad English, and also because the portal not translated into English and other languages.
I invite you to sign petition to revoke Samsung Knox ( You can use google.translate ) .... or even better , create a similar initiative in the U.S. That will be very much more stronger.
The union of America and Europe is very powerful and can give pause to Samsung
Thank you very much.
Is not spam:
change.org/es/peticiones/samsung-eliminar-el-sistema-knox-activado-recientemente-en-las-nuevas-actualizaciones-de-software-samsung-remove-the-knox-system-on-recently-in-new-software-updates-samsung-녹스-시스템을-제거합니다-최근에-새-소프트웨어-업데이트에서합니다#
Why would they? It's actually a very good security measure for those who need it (corporate users). I don't so I rooted my 8.4 and blew the eFuse in the process. I knew what I was doing and I didn't do it by accident. I will bear the consequences in case I need repairs :shrug:
Samsung Knox fuse has nothing to do with the hardware warranty. It simply shows if the tablet was modified in a way that can circumvent KNOX security apps. That way if you bring your tablet to your employer to use on their network, the sys admin can confirm if the tablet will be absolutely secure or not. Once you modify the tablet/phone, Knox software won't install/run because the device isn't considered secure anymore.
Sent from my SM-P900 using Tapatalk
And I'm sure a petition to remove security features post-Snowden would be well received. Especially when removing it is to provide warranty services to a small subset of people who want to screw around with the s/w on their devices.
BarryH_GEG said:
And I'm sure a petition to remove security features post-Snowden would be well received. Especially when removing it is to provide warranty services to a small subset of people who want to screw around with the s/w on their devices.
Click to expand...
Click to collapse
Uffff, Snowden can not return to their country ....
I think all the manufacturers and sellers of premium tablets will soon acquire the closed Apple iPad style, and it will become increasingly difficult to have a good free terminal.
Samsung Knox is okay but is also an excellent excuse to avoid root (or loss of warranty). HDX Kindle is fantastic, but their system is closed. iPad closed. Root Sony Experia is hard to do ..... I wish this were not so, but ....
the reality is Edward should take shelter in a less democratic country, because they can not return to their country, which we all know is an example of democracy and transparency ... but do not talk politics.
I thank the programmers that allow me to root my tablet, even if I lose the warranty
and I will join to Samsung petition through change.org ... and little more (or maybe next time I will buy from another manufacturer more open)
Regards
If you want your warranty, don't root.
Simple as that.
kieroseno said:
I think all the manufacturers and sellers of premium tablets will soon acquire the closed Apple iPad style, and it will become increasingly difficult to have a good free terminal.
Samsung Knox is okay but is also an excellent excuse to avoid root (or loss of warranty). HDX Kindle is fantastic, but their system is closed. iPad closed. Root Sony Experia is hard to do ..... I wish this were not so, but ....
Click to expand...
Click to collapse
Knox doesn't stop anything. You can still root and install custom recovery; it's just that it is permanently recorded
I did not express myself well, I apologize for my bad English.
Knox does not prevent root but ... voids the warranty if root. With previous tablets we had TriangleAway thanks to Chainfire, but now Samsung has left unusable TA. This reminds me of updates to iOS that prevent jailbreak, but still is not the same .... today ..... but I think is the same way in the future.
Yesterday: you can make root
Today: if you root, you lose your warranty.
Tomorrow: impossible to root?
Does this seem right to most? Then ... nothing more to say
Regards
Spoke with my lawyer. Says I have a case against samsung.
1.) Samsung faild to password protect update option
As my almost 2 year old managed to update me to 4.4 from JB 4.1.2. When I did not want 4.3 or 4.4 due to knox.
2.) The knox feature was not advertised when selling the note 2 and other phones sold prior to introducing knox to our phones.
I don't have the money to fork over legal expenses. So lawyer said if I can find more then 400 samsung users who are stuck with knox they would take the case.
If you wish to join reply to post. Once we reach 400 will contact you all with an for proper information.
Pls only use this to count yourself in. Add a comment if you wish when adding yourself but pls no chating. Will make it easy to count who's in this way.
I'm in
rogersb11 said:
I'm in
Click to expand...
Click to collapse
They should have given the option when introducing 4.3 and 4.4 of having knox secure boot or not having knox at all.
I'm sure they could have introduced jb 4.3 and kk 4.4 and any other updates without knox and knox secure boot.
droideastcoast said:
They should have given the option when introducing 4.3 and 4.4 of having knox secure boot or not having knox at all.
I'm sure they could have introduced jb 4.3 and kk 4.4 and any other updates without knox and knox secure boot.
Click to expand...
Click to collapse
Bingo. Option is what it should be
Count on me
Throw me in the mix, can I go in twice? I have 2 notes dueces.
I'm in too.
Sent from my SGH-I317 using Tapatalk
So am I.
Tap, tap says the wicked Note +₩● ?
Kind of sad that ppl are complaining about knox secure boot and trip but no one is willing to step up and take samsung to court?
Come on guys.
This could also be the answer to removing the secure boot.
If noone steps up then samsung will continue to do this kind of crap.
In bit my Knox is tripped
I like Knox... I don't see what the big deal is. Lose the ability to root like Apple so devs have to pull a jailbreak every new version that comes out by vulnerability hunting? I've come to the conclusion that there is no need for me to root anymore. I have become the normal smartphone user who doesn't need more than what comes stock after all these years rooting and bug hunting. It is now a waste of time for me.
And you know what else?
There are millions of people who are just like me who could give a rat's ass about how Knox stops me from rooting my phone.
Before you go flaming, understand that I am talking about myself and the other millions who have no clue that XDA even exists. You can do what you need to feel better about yourself by gathering a class action lawsuit against a multi-billion corporation. Good luck with that.
[email protected] said:
I like Knox... I don't see what the big deal is. Lose the ability to root like Apple so devs have to pull a jailbreak every new version that comes out by vulnerability hunting? I've come to the conclusion that there is no need for me to root anymore. I have become the normal smartphone user who doesn't need more than what comes stock after all these years rooting and bug hunting. It is now a waste of time for me.
And you know what else?
There are millions of people who are just like me who could give a rat's ass about how Knox stops me from rooting my phone.
Before you go flaming, understand that I am talking about myself and the other millions who have no clue that XDA even exists. You can do what you need to feel better about yourself by gathering a class action lawsuit against a multi-billion corporation. Good luck with that.
Click to expand...
Click to collapse
This post convinced me to join the lawsuit. That's you opinion and it'a fair,
However I like having choice, freedom, and ownership as a consumer. I don't like having updates remove and change features that I orginally paid for
Cryingmoose said:
This post convinced me to join the lawsuit. That's you opinion and it'a fair,
However I like having choice, freedom, and ownership as a consumer. I don't like having updates remove and change features that I orginally paid for
Click to expand...
Click to collapse
I'm In
I am sorry but after reading this thread everyday I have to finally say something. You guys are trying to sue Samsung for adding security to your phone to prevent it from being easily hacked, your personal and banking information being stolen, unauthorized use, and not being able to root it and put unauthorized software on it? Got a little bit of news for you, you better start looking for some old phones on swappa and ebay because there are talks that Google is incorporating some of Knox into L OS version. Also Sprint and T-mobile have no issues rooting with the same version of Knox...so maybe you should be looking at what your carrier is doing.
And as for a 2 year old accepting the update, you had options to lock your phone with many different methods. This 2 year old accepted the option to first download it, wait while the file downloaded, then also accepted the option to install now? I do not think this lawyer has all the information. Especially when Google and Samsung on the devil's advocate side would face a much larger lawsuit if doing nothing to try and prevent the millions of non-XDA users from getting their phone hacked. Knox and locked bootloaders have nothing to do with trying to prevent the 100,000 XDA AT&T or Verizon Samsung users from rooting. It is to make the phones as secure as possible for military and business applications.
Here is sammobile's report on "L" and Knox: http://www.sammobile.com/2014/06/25...egrate-knox-into-androids-next-major-release/
KennyG123 said:
I am sorry but after reading this thread everyday I have to finally say something. You guys are trying to sue Samsung for adding security to your phone to prevent it from being easily hacked, your personal and banking information being stolen, unauthorized use, and not being able to root it and put unauthorized software on it? Got a little bit of news for you, you better start looking for some old phones on swappa and ebay because there are talks that Google is incorporating some of Knox into L OS version. Also Sprint and T-mobile have no issues rooting with the same version of Knox...so maybe you should be looking at what your carrier is doing.
And as for a 2 year old accepting the update, you had options to lock your phone with many different methods. This 2 year old accepted the option to first download it, wait while the file downloaded, then also accepted the option to install now? I do not think this lawyer has all the information. Especially when Google and Samsung on the devil's advocate side would face a much larger lawsuit if doing nothing to try and prevent the millions of non-XDA users from getting their phone hacked. Knox and locked bootloaders have nothing to do with trying to prevent the 100,000 XDA AT&T or Verizon Samsung users from rooting. It is to make the phones as secure as possible for military and business applications.
Here is sammobile's report on "L" and Knox: http://www.sammobile.com/2014/06/25...egrate-knox-into-androids-next-major-release/
Click to expand...
Click to collapse
There's a gulf of difference between a device being advertised with a feature and shipping with it and a mandatory update installing said feature.
The carriers didn't even disclose the ramifications of installing OTAs containing Knox.
I don't have an issue with updates changing features over time but something that alters your relationship with your property in such a fashion should be opt-in and after disclosing the ramifications.
TerryMathews said:
There's a gulf of difference between a device being advertised with a feature and shipping with it and a mandatory update installing said feature.
The carriers didn't even disclose the ramifications of installing OTAs containing Knox.
I don't have an issue with updates changing features over time but something that alters your relationship with your property in such a fashion should be opt-in and after disclosing the ramifications.
Click to expand...
Click to collapse
At no point did Samsung or AT&T guarantee the rootability of a device. And remember, the other millions of owners don't know about these "ramifications" as I am sure they are happy to know that their phone is more secure. Windows updates your system constantly for security updates. If that suddenly stops a Pr0n site from showing up on your PC because it is now considered malicious should they have notified you? The updates do nothing to prevent the out of the box use intended by the device. I am merely stating that this suit has no legal grounds. If you know about rooting and know about hacking, you know not to accept updates until you find out what they are. You should know ways of preventing those updates, and you should know how to secure your phone from anyone using it to accept those updates without your permission. The other millions of users out there can keep moving along blissfully happy that their phone is constantly being updated and not left in the dust.
Why should the carriers disclose that your device be more difficult to root? Rooting is not an authorized procedure supported by the carriers at all! I missed the disclosure by Sony on my PS3 that accepting the update which will allow me to access the Playstation Network is also to prevent jailbreaking it on the current revision. Add to that, read the OP...it states nothing about the carrier. It is a suit directed at Samsung. Knox does not prevent any use of the device which is authorized and supported by the carrier. Also Knox does not prevent rooting as seen on T-Mobile and Sprint forums as well as the international forums.
But I wish you guys luck with the suit and hope the lawyer is accepting this Pro Bono and no one has to dish out any non-refundable legal fees. I just wanted you all to be better informed of what you are asking.
If I'm not mistaken, the Federal government (USA) guaranteed end users the right to root access of our phones, and recently upheld that law. But does Knox really stop you from rooting it? Luckily I have avoided it because I haven't had a stock ROM for more than a few minutes on my phone since I bought it
KennyG123 said:
At no point did Samsung or AT&T guarantee the rootability of a device. And remember, the other millions of owners don't know about these "ramifications" as I am sure they are happy to know that their phone is more secure. Windows updates your system constantly for security updates. If that suddenly stops a Pr0n site from showing up on your PC because it is now considered malicious should they have notified you? The updates do nothing to prevent the out of the box use intended by the device. I am merely stating that this suit has no legal grounds. If you know about rooting and know about hacking, you know not to accept updates until you find out what they are. You should know ways of preventing those updates, and you should know how to secure your phone from anyone using it to accept those updates without your permission. The other millions of users out there can keep moving along blissfully happy that their phone is constantly being updated and not left in the dust.
Why should the carriers disclose that your device be more difficult to root? Rooting is not an authorized procedure supported by the carriers at all! I missed the disclosure by Sony on my PS3 that accepting the update which will allow me to access the Playstation Network is also to prevent jailbreaking it on the current revision. Add to that, read the OP...it states nothing about the carrier. It is a suit directed at Samsung. Knox does not prevent any use of the device which is authorized and supported by the carrier. Also Knox does not prevent rooting as seen on T-Mobile and Sprint forums as well as the international forums.
But I wish you guys luck with the suit and hope the lawyer is accepting this Pro Bono and no one has to dish out any non-refundable legal fees. I just wanted you all to be better informed of what you are asking.
Click to expand...
Click to collapse
There is a difference between guaranteeing a product's suitability for given task and actively working to reduce that capability.
For instance, let's look at car recalls. Some of them impact how your car behaves, its gas mileage, or its service schedule. Ever notice how the dealer needs your consent before modifying your vehicle?
Your example of Windows Update is equally flawed. Windows Update is an opt-in service which in fact reinforces my earlier point that Knox or system updates in general should be opt-in or at least have a provision for opt-out that doesn't involve rooting your device.
Court cases aren't decided on popularity. If they were, Roe v. Wade would have gone a very different direction (as an example).
I hope you're not a lawyer Kenny...
Honestly... there's no point in arguing. Whomever goes and does this lawsuit, have fun, good luck, and I hope no money comes out of your own pocket. Your XDA soap box will get you nowhere so go out and do what you have to do to get your rocks off. Even if you even do succeed, enjoy the years of counter-suits and appeals.
TerryMathews said:
There is a difference between guaranteeing a product's suitability for given task and actively working to reduce that capability.
For instance, let's look at car recalls. Some of them impact how your car behaves, its gas mileage, or its service schedule. Ever notice how the dealer needs your consent before modifying your vehicle?
Your example of Windows Update is equally flawed. Windows Update is an opt-in service which in fact reinforces my earlier point that Knox or system updates in general should be opt-in or at least have a provision for opt-out that doesn't involve rooting your device.
Court cases aren't decided on popularity. If they were, Roe v. Wade would have gone a very different direction (as an example).
I hope you're not a lawyer Kenny...
Click to expand...
Click to collapse
There is no further point in arguing with you as clearly you are not a lawyer either. No one mentioned popularity. Your arguments are misconstrued and have nothing to do with the focus of the lawsuit. You should reread the "opening statement" a 2 year old "accepted" the update meaning optional, not mandatory, and there are ways for anyone who can search to not accept the OTA or update.
Have a nice day and good luck. As I stated earlier, Knox is now moving to Google and the next version of Android and it also does not prevent rooting if you would just check out the other carriers. This is the main flaw in this law suit. Lawyered
Hello fellow developers and OnePlus users,
I come bearing some exciting news that could be a game-changer for those of us in the custom development community. As many of you are aware, the MSM Download Tool, a significant asset for unbricking and flashing OnePlus devices, has been restricted in recent iterations of OnePlus devices for the last few years, following the merger of OnePlus and Oppo. This move limited the tool's access to authorized service center employees, effectively locking out regular users and enthusiasts.
Today, I am pleased to announce that I have managed to bypass these restrictions, unlocking the MSM Download Tool for the OnePlus 11 and possibly the OnePlus 10 as well, although the latter remains untested at the moment. (EDIT : A few people reported that it does not works with the OnePlus 10, thus it is unclear if it has been tested with EDL packages)
This breakthrough restores the ability to fix bricked devices ourselves, a feature that was greatly appreciated by the tech enthusiast community and was a significant factor in OnePlus's popularity within these circles.
What has been achieved ?
- Log in using any credentials, and it will work
- Select an official EDL package and flash it on a Oneplus 11 (Including rebranding, works perfectly and OTAs works perfectly)
- Stability trough time : Oppo will not be able to fix it in current versions of Download Tool. The vulnerable ones will work forever. We can consider Oneplus 11 safe to that aspect.
However, I want to make a few things clear:
Limited Release: For the time being, I will not be publishing the code publicly. My reasons for this decision are twofold. First, I do not want Oppo to become aware of the bypass and fix it, preventing future use of the tool. Second, the majority of users do not have a need for this tool, and its misuse could potentially lead to more harm than good. If you accidentally brick your phone while flashing a ROM or something, reach your local authorised service/service center. There also are less moral service providers who offer remote flashing services for as low as $4.
Availability to Developers: If you are an experienced and recognized developer working on OnePlus 10 or 11 devices, you may access the unlocked tool by direct messaging me. Please provide proof of your work on these devices (commits, repositories, GitHub profile). I believe that having access to this tool will be a significant aid in our development efforts.
Advice for General Users: For regular users who might need to unbrick their OnePlus 10 or 11 devices, I recommend seeking the help of professionals.
I may consider releasing this solution publicly once we get stable builds of LineageOS for the Oneplus 11 series, but for now, this is the course of action I feel is best for the community. Thank you for understanding, and I am looking forward to seeing the exciting developments that will come from this!
If you're wondering why I am not releasing the code publicly, please read this post. I'm the first to be sorry about this, but I think this is the best that could be done for the community.
Notes :
- PLEASE, DO NOT ASK FOR THE TOOL IF YOU ARE NOT A DEVELOPER.
- I WILL NEVER ASK MONEY TO PROVIDE THIS CRACK. I DID IT FOR THE COMMUNITY. I'M NOT PUBLISHING ANY DONATE LINKS EITHER.
- I WILL NEVER PUBLISH THE OPPO DOWNLOADTOOL, ONLY MY CODE TO MAKE IT WORK, YOU'LL HAVE TO FIND THE DOWNLOADTOOL SOFTWARE YOURSELF
What a dik move to make it available only for people you choose to.
We will see how long this topic will last before getting deleted for promoting cracked software.
cavist said:
What a dik move to make it available only for people you choose to.
We will see how long this topic will last before getting deleted for promoting cracked software.
Click to expand...
Click to collapse
By your reply I assume you are not a developer. If making it available "only for people I choose to" means not Oppo, heck yeah. Of course I do not want them to study the vulnerability and patch it in future versions of DownloadTool.
By the way, I am not promoting "cracked software" as the software is untouched. I will provide the crack as a standalone solution, and developers will be able to use any genuine version of DownloadTool they want. My solution will simply allow developers to restore a device they bricked while testing their ROM or kernel without relying in Oppo/Realme authentication (because yes, any authentication works)
And if this topic gets deleted, I'll release the solution elsewhere. But that would be a sad outcome and a bad move from XDA by showing support for practices hostile to developers.
oppo_edl_hacker said:
By your reply I assume you are not a developer. If making it available "only for people I choose to" means not Oppo, heck yeah. Of course I do not want them to study the vulnerability and patch it in future versions of DownloadTool.
By the way, I am not promoting "cracked software" as the software is untouched. I will provide the crack as a standalone solution, and developers will be able to use any genuine version of DownloadTool they want. My solution will simply allow developers to restore a device they bricked while testing their ROM or kernel without relying in Oppo/Realme authentication (because yes, any authentication works)
And if this topic gets deleted, I'll release the solution elsewhere. But that would be a sad outcome and a bad move from XDA by showing support for practices hostile to developers.
Click to expand...
Click to collapse
Youre posting this on XDA, saying "hey, I have it and you ont, if you want then msg me and maybe I will share it with you".
I would say this does not help XDA community at all and its the same like creating a new telegram group or any other private space where you can do whatever.
cavist said:
What a dik move to make it available only for people you choose to.
We will see how long this topic will last before getting deleted for promoting cracked software.
Click to expand...
Click to collapse
At least this would help the development going forward.
cavist said:
What a dik move to make it available only for people you choose to.
We will see how long this topic will last before getting deleted for promoting cracked software.
Click to expand...
Click to collapse
Why would random Joes some of whom may turn out to be BBK/Oppo/OnePlus employees get access to the tool?
What's dickish about investing your intelligence, work and time and sharing the results only with the people that you choose? I've no problem with that at all.
birdie said:
Why would random Joes some of whom may turn out to be BBK/Oppo/OnePlus employees get access to the tool?
What's dickish about investing your intelligence, work and time and sharing the results only with the people that you choose? I've no problem with that at all.
Click to expand...
Click to collapse
Some people never learn. If we want this solution to hold for a few years to come, we have to take precautions. This is for the best, and if Oppo finds the vulnerability by themselves, of course I will release the solution. The sole fact I opened a public thread could gain attention from Oppo and force them to review their security, so it is easy to figure out what's going to happen if they can study my solution.
This 0-day would be really easy to fix for them, and that's not what we want. If they can't study the solution, they'll have to figure it out themselves.
oppo_edl_hacker said:
Hello fellow developers and OnePlus users,
I come bearing some exciting news that could be a game-changer for those of us in the custom development community. As many of you are aware, the MSM Download Tool, a significant asset for unbricking and flashing OnePlus devices, has been restricted in recent iterations of OnePlus devices for the last few years, following the merger of OnePlus and Oppo. This move limited the tool's access to authorized service center employees, effectively locking out regular users and enthusiasts.
Today, I am pleased to announce that I have managed to bypass these restrictions, unlocking the MSM Download Tool for the OnePlus 11 and possibly the OnePlus 10 as well, although the latter remains untested at the moment. This breakthrough restores the ability to fix bricked devices ourselves, a feature that was greatly appreciated by the tech enthusiast community and was a significant factor in OnePlus's popularity within these circles.
What has been achieved ?
- Log in using any credentials, and it will work
- Select an official EDL package and flash it on a Oneplus 11 (Including rebranding, works perfectly and OTAs works perfectly)
- Stability trough time : Oppo will not be able to fix it in current versions of Download Tool. The vulnerable ones will work forever. We can consider Oneplus 10 and 11 safe to that aspect.
However, I want to make a few things clear:
Limited Release: For the time being, I will not be publishing the unlocked tool publicly. My reasons for this decision are twofold. First, I do not want Oppo to become aware of the bypass and fix it, preventing future use of the tool. Second, the majority of users do not have a need for this tool, and its misuse could potentially lead to more harm than good. If you accidentally brick your phone while flashing a ROM or something, reach your local authorised service. There also are less moral service providers who offer flashing services for as low as $4.
Availability to Developers: If you are an experienced and recognized developer working on OnePlus 10 or 11 devices, you may access the unlocked tool by direct messaging me. Please provide proof of your work on these devices from Github. I believe that having access to this tool will be a significant aid in our development efforts.
Advice for General Users: For regular users who might need to unbrick their OnePlus 10 or 11 devices, I recommend seeking the help of professionals.
I may consider releasing the cracked tool publicly once we get stable builds of LineageOS for the Oneplus 10 and Oneplus 11 series, but for now, this is the course of action I feel is best for the community. Thank you for understanding, and I am looking forward to seeing the exciting developments that will come from this!
Notes :
- DO NOT DM ME IF YOU ARE NOT A DEVELOPER, YOU'LL ONLY GET BLOCKED
- I CREATED THIS ACCT TO PROTECT MY PRIVACY. ACTUALLY I AM A RECOGNIZED DEVELOPER ON XDA BUT I WILL NOT DISCLOSE MY IDENTITY
- I WILL NEVER ASK MONEY TO PROVIDE THIS CRACK. I DID IT FOR THE COMMUNITY. I'M NOT PUBLISHING ANY DONATE LINKS EITHER.
- The software is original and untouched, it is not hex edited. I am well aware of the hex hack allowing some sort of login, this crack is not based on that at all. The crack works using smarter ways.
- NO THIS IS NOT FAKE AND I CAN PROVE IT EASILY
Click to expand...
Click to collapse
@V0latyle @Oswald Boelcke
@dekefake @chandu dyavanapelli srry For tagging them but I think this will be useful
cazt555 said:
@dekefake @chandu dyavanapelli srry For tagging them but I think this will be useful
Click to expand...
Click to collapse
OMFG ! This is a game changer, @oppo_edl_hacker I'm DMing now. Thanks a ton @cazt555. I bricked my OnePlus 11 twice already while testing our first custom kernel builds, this will definetely help us a lot.
mvikrant97 said:
@V0latyle @Oswald Boelcke
Click to expand...
Click to collapse
I really hope the moderators will understand how important this is for us. Smart move to not publish it publicly, this thread has to stay in my honest opinion.
mvikrant97 said:
@V0latyle @Oswald Boelcke
Click to expand...
Click to collapse
I'll be honest, I'm not very familiar with the technical aspect of this.
@oppo_edl_hacker Welcome to XDA. If you have not already, please read the Forum Rules linked in my signature, and take special note of Rules 6, 7, 9, and 11:
6. Do not post or request warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community.
7. Do not sell or trade on the forums.
If you wish to advertise a product, simply contact us. We can provide ads but you are not permitted to just post it in the forums. If you do, it will be removed and you're likely to receive a ban.
The buying, selling, trading and / or exchanging of any item is now prohibited on XDA, in any forum or via Private Messages. We now use www.swappa.com
9. Don't get us into trouble.
Don't post copyrighted materials or do other things which will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably shouldn't do it here either. This does not mean that we agree with everything that the software piracy lobby try to impose on us. It simply means that you cannot break any laws here, since we'll end up dealing with the legal hassle caused by you. Please use common sense: respect the forum, its users and those that write great code.
11. Don’t post with the intention of selling something.
Don’t use XDA to advertise your product or service. Proprietors of for-pay products or services, may use XDA to get feedback, provide beta access, or a free version of their product for XDA users and to offer support, but not to post with the intention of selling. This includes promoting sites similar / substantially similar to XDA-Developers.com.
Do not post press releases, announcements, links to trial software or commercial services, unless you’re posting an exclusive release for XDA-Developers.com.
Encouraging members to participate in forum activities on other phone related sites is prohibited.
Off-site downloads are permitted if the site is non-commercial and does not require registration.
Off-site downloads from sites requiring registration are NOT encouraged but may be permitted if both of the following conditions are met:
A) The site belongs to a member of XDA-Developers with at least 1500 posts and 2 years membership, who actively maintains an XDA-Developers support thread(s) / posts, related to the download.
B) The site is a relatively small, personal website without commercial advertising / links (i.e. not a competitor forum-based site with purposes and aims similar to those of XDA-Developers.com.)
Click to expand...
Click to collapse
Please answer the following questions:
1. Is the software you are using copyrighted in any way?
2. Are you redistributing software, or offering a service? Are you selling anything?
3. Is what you are doing legal?
4. Are you advertising a commercial service?
V0latyle said:
@oppo_edl_hacker Welcome to XDA. If you have not already, please read the Forum Rules linked in my signature, and take special note of Rules 6, 7, 9, and 11:
Please answer the following questions:
1. Is the software you are using copyrighted in any way?
2. Are you redistributing software, or offering a service? Are you selling anything?
3. Is what you are doing legal?
4. Are you advertising a commercial service?
Click to expand...
Click to collapse
Hi, good evening !
The software used to flash Oppo's phone is an internal software distributed to some phone repair stores. It needs an authentication. This software was previously publicly available with no authentication, but as OnePlus has been acquired by Oppo, their policy changed and they now use the Oppo software with authentication. This makes it impossible for developers to recover their devices themselves when testing their experimental ROMs and kernels. This is the cause of a lack of custom ROMs and kernels for OnePlus devices in the last two years. This has also lead to a situation where some corrupt people ask for money (from 4$ to 75$) to remotely flash phones using TeamViewer. This frequently happens throughout XDA and there are countless examples of that.
1. I do not intend to distribute copywrited software, but only my code, which is taking action in the operating system networking stack and not the OPPO software.
2. I only distribute this code to active developers working on OnePlus 10 and OnePlus 11, so they can quickly recover their devices if something goes wrong.
3. My code does not constitutes piracy as it does not includes copywrited code at all. It is then legal. I do not distribute the original software and developers are intended to find it by themselves. This software has already been leaking for years and is easy to find online.
4. I solely do this to help the community, and do not sell anything. I will never ask for money for this, and do not have a donation link. My code will always be free for developers.
As we say, code is speach. I wrote code that can help people, and I'm offering it to developers. I just want to avoid OPPO from obtaining my code, as they could change things in the future to further restrict developers from using their devices as they intend to.
oppo_edl_hacker said:
Hi, good evening !
The software used to flash Oppo's phone is an internal software distributed to some phone repair stores. It needs an authentication. This software was previously publicly available with no authentication, but as OnePlus has been acquired by Oppo, their policy changed and they now use the Oppo software with authentication. This makes it impossible for developers to recover their devices themselves when testing their experimental ROMs and kernels. This is the cause of a lack of custom ROMs and kernels for OnePlus devices in the last two years. This has also lead to a situation where some corrupt people ask for money (from 4$ to 75$) to remotely flash their phones using TeamViewer. This frequently happens throughout XDA.
1. I do not intend to distribute copywrited software, but only my code, which is taking action in the operating system networking stack and not the OPPO software.
2. I only distribute this code to active developers working on OnePlus 10 and OnePlus 11, so they can quickly recover their devices if something goes wrong.
3. My code does not constitutes piracy as it does not includes copywrited code at all. It is then legal. I do not distribute the original software and developers are intended to find it by themselves. This software has already been leaking for years and is easy to find online.
4. I solely so this to help the community, and do not sell anything. I will never ask for money for this, and do not have a donation link. My code will always be free for developers.
Click to expand...
Click to collapse
Thank you for the response. Please respond to the PM I have sent you.
Utterly stellar work @oppo_edl_hacker
Heaps of praise to you... Your deserve a tonne of credit for this... And it should categorically be protected.
Thank you for proving me wrong, I didn't think this day would come.
Legend.
dladz said:
Utterly stellar work @oppo_edl_hacker
Heaps of praise to you... Your deserve a tonne of credit for this... And it should categorically be protected.
Thank you for proving me wrong, I didn't think this day would come.
Legend.
Click to expand...
Click to collapse
Thanks for the kind words dude
birdie said:
Why would random Joes some of whom may turn out to be BBK/Oppo/OnePlus employees get access to the tool?
What's dickish about investing your intelligence, work and time and sharing the results only with the people that you choose? I've no problem with that at all.
Click to expand...
Click to collapse
Since the current tool is working and its only an additional crack it does not change anything at all - they cannot disable it.
Also, it will just come out sooner or later, intentionally or via leak so why artificially make a closed circle on this I have no idea but everybody can do whatever they want and my single opinion will not change anything.
cavist said:
Since the current tool is working and its only an additional crack it does not change anything at all - they cannot disable it.
Also, it will just come out sooner or later, intentionally or via leak so why artificially make a closed circle on this I have no idea but everybody can do whatever they want and my single opinion will not change anything.
Click to expand...
Click to collapse
Just respect his wishes...after all we had nothing before...
Don't want a back and forth, the guy who made this possible wants this to happen and unless we want oppos attention before it's even fully realised I agree we should tread lightly.
oppo_edl_hacker said:
Hello fellow developers and OnePlus users,
I come bearing some exciting news that could be a game-changer for those of us in the custom development community. As many of you are aware, the MSM Download Tool, a significant asset for unbricking and flashing OnePlus devices, has been restricted in recent iterations of OnePlus devices for the last few years, following the merger of OnePlus and Oppo. This move limited the tool's access to authorized service center employees, effectively locking out regular users and enthusiasts.
Today, I am pleased to announce that I have managed to bypass these restrictions, unlocking the MSM Download Tool for the OnePlus 11 and possibly the OnePlus 10 as well, although the latter remains untested at the moment. This breakthrough restores the ability to fix bricked devices ourselves, a feature that was greatly appreciated by the tech enthusiast community and was a significant factor in OnePlus's popularity within these circles.
What has been achieved ?
- Log in using any credentials, and it will work
- Select an official EDL package and flash it on a Oneplus 11 (Including rebranding, works perfectly and OTAs works perfectly)
- Stability trough time : Oppo will not be able to fix it in current versions of Download Tool. The vulnerable ones will work forever. We can consider Oneplus 10 and 11 safe to that aspect.
However, I want to make a few things clear:
Limited Release: For the time being, I will not be publishing the code publicly. My reasons for this decision are twofold. First, I do not want Oppo to become aware of the bypass and fix it, preventing future use of the tool. Second, the majority of users do not have a need for this tool, and its misuse could potentially lead to more harm than good. If you accidentally brick your phone while flashing a ROM or something, reach your local authorised service. There also are less moral service providers who offer flashing services for as low as $4.
Availability to Developers: If you are an experienced and recognized developer working on OnePlus 10 or 11 devices, you may access the unlocked tool by direct messaging me. Please provide proof of your work on these devices from Github. I believe that having access to this tool will be a significant aid in our development efforts.
Advice for General Users: For regular users who might need to unbrick their OnePlus 10 or 11 devices, I recommend seeking the help of professionals.
I may consider releasing this solution publicly once we get stable builds of LineageOS for the Oneplus 10 and Oneplus 11 series, but for now, this is the course of action I feel is best for the community. Thank you for understanding, and I am looking forward to seeing the exciting developments that will come from this!
Notes :
- DO NOT DM ME IF YOU ARE NOT A DEVELOPER, YOU'LL ONLY GET BLOCKED
- I CREATED THIS ACCOUNT TO PROTECT MY PRIVACY. ACTUALLY I AM A RECOGNIZED DEVELOPER ON XDA BUT I WILL NOT DISCLOSE MY IDENTITY
- I WILL NEVER ASK MONEY TO PROVIDE THIS CRACK. I DID IT FOR THE COMMUNITY. I'M NOT PUBLISHING ANY DONATE LINKS EITHER.
- The software is original and untouched, it is not hex edited. I am well aware of the hex hack allowing some sort of login, this solution is not based on that at all. The crack works using smarter ways (networking).
- I WILL NEVER PUBLISH THE OPPO DOWNLOADTOOL, ONLY MY CODE TO MAKE IT WORK, YOU'LL HAVE TO FIND THE DOWNLOADTOOL SOFTWARE YOURSELF
- NO THIS IS NOT FAKE AND I CAN PROVE IT EASILY
Click to expand...
Click to collapse
any proof of works, or it is just a login bypass similar to any other crack, the main Problem is SLA, if you are able to bypass Oplus server to get signature back then really thanks
cavist said:
Since the current tool is working and its only an additional crack it does not change anything at all - they cannot disable it.
Also, it will just come out sooner or later, intentionally or via leak so why artificially make a closed circle on this I have no idea but everybody can do whatever they want and my single opinion will not change anything.
Click to expand...
Click to collapse
They cannot prevent already released tools from working but they can patch future versions and prevent yet to be released phones from being flashed. If we keep it closed circle, maybe OnePlus 12, OnePlus 13 will be able to be flashed. If I release the code today, we'll be sure they will not.
mark332 said:
any proof of works, or it is just a login bypass similar to any other crack, the main Problem is SLA, if you are able to bypass Oplus server to get signature back then really thanks
Click to expand...
Click to collapse
Some developers are starting to report that it indeed works for them so don't worry, if it is fake, it will quickly get known
I will discuss with some developers to release a video showing the software in action, while preventing the vulnerability to be shown.