Develop Bugs

Motorola Bootloader Petition (>10K sigs & Moto Response)

Visit Groubal and sign the petition: http://www.groubal.com/motorola-lockedencrypted-bootloader-policy/
Retweet: http://twitter.com/#!/ibproud/status/52265679990169600
Facebook Page: http://www.facebook.com/unlockmoto
UPDATE (14th June 2011):
We are now over the 10,000 mark.​
I have now spoken with Motorola and gotten confirmation that Motorola plan to unlock every device that will get an update in the second half of this year. This will include maintenance & firmware updates, but is still subject to Carrier approval.
The promising sign is that Verizon has already allowed Motorola to unlock a device on their network, the Xoom, which utilizes the unlockable/re-lockable model that Motorola intends on using across their devices.
I'm still looking to work with Motorola in the coming months to help see if we can make this a smooth process for Motorola and the community.
You can read the article here:
http://ausdroid.net/2011/06/14/an-u...witter&utm_campaign=Feed:+ausdroid+(Ausdroid)
Please share this where you can and keep it alive. I will continue to work with Motorola to see if we can get this thing torn wide open.
UPDATE (26th April 2011):
We are now at ~8,700 mark.​
Motorola has now responded to me, stating that they are looking at unlocking bootloaders across their devices late 2011.
The article for the story can be found here:
http://ausdroid.net/2011/04/26/the-little-aussie-taking-on-motorola-u-s/#more-8184
We're still seeking clarity around whether this will be for current devices or only future devices.
I couldn't have gotten this far without the support of everyone here. You guys and girls have been a huge support and help me turn this snowball into a wrecking ball.
Please share this where you can and keep it alive. I will continue to work with Motorola to see if we can get this thing torn wide open.
Previous Update (4th April 2011):
We are now at ~7600 mark.​
We're starting to slow down from our initial boom, so I have now set up a Facebook page to see if we can wrangle in some supporters that don't use Twitter or XDA.
I will need your help getting this out there. So share the facebook page where you can.
I'm also looking to see if anyone is interested in helping me Moderate the page. Please PM if you are.
Original Post:
Hi All,
I have created a Groubal (online petition) to get a response from Motorola on it's bootloader policy.
>>This petition started for the Atrix, but I made sure that it was for Motorola's overall Bootloader Policy. I have reached 200 signatures in 2 weeks, but now believe it's time to expand this out of the Atrix space and into the larger Motorola Dev community.

Just signed the petition.

It could be me but non of your links work
How could you sign the petiton dedraks?

spamnco said:
It could be me but non of your links work
How could you sign the petiton dedraks?
Click to expand...
Click to collapse
Thanks for the heads up on that. I'll be more careful when copying and pasting links.

Let's try this:
http://www.groubal.com/motorola-lockedencrypted-bootloader-policy/

spamnco said:
It could be me but non of your links work
How could you sign the petiton dedraks?
Click to expand...
Click to collapse
Use this shor link: http://4by.in/4

Not that it'll make any difference but your petition is more likely to be taken seriously if comments like that of 'rich fraley' weren't included.
Signed, at length...

Step666 said:
Not that it'll make any difference but your petition is more likely to be taken seriously if comments like that of 'rich fraley' weren't included.
Signed, at length...
Click to expand...
Click to collapse
Yeah, agreed. I tried seeing if I could at least censor the comment, but no dice.
Thanks for you're support guys. I've always been a big fan of the saying "You can catch more flies with honey than with vinegar".

Famous idea. You got the sign.

i have signed

Not to kill the cause... but the issue isnt really with motorola... Isnt it with the service providers who would rather have the bootloaders on the phones locked so they can sell us services we could install for free... ie Wi-fi Calling, Tethering..
I think Motorola's hands are tied.. their customers are the service providers.
Would it make more sense to harass t-mobile and the likes over this?

Signed as well.

ketonkss4 said:
Not to kill the cause... but the issue isnt really with motorola... Isnt it with the service providers who would rather have the bootloaders on the phones locked so they can sell us services we could install for free... ie Wi-fi Calling, Tethering..
I think Motorola's hands are tied.. their customers are the service providers.
Would it make more sense to harass t-mobile and the likes over this?
Click to expand...
Click to collapse
On all phones that have locked and encrypted bootloaders, I don't think there's been one that couldn't be rooted. Once rooted, you have access to all the Tethering and WiFi Calling apps out there. So it could be the case, but all unlocking the bootloader does is let you use custom kernels that form the base of alternative roms. So bloatware be damned, it can removed fairly quickly and without even touching the bootloader.
It would be more for warranty claims, that's why the padlock picture on the very first screen's the way to go. That way if a phone is damaged due to modification, the carrier/manufacturer can turn you away due to voided warranty.

signed the partition to
i am looking into the legal side of the locked bootloader to see if theirs any loop holes in locking a phone when the manufacture is part of the open handset alliance
but i think the fastest way of the bootloader being unencrypted is to put up a cash reward for the person that unlocks it.
maybe if we can raise £1000 it might spur someone on to go the extra mile

ketonkss4 said:
Not to kill the cause... but the issue isnt really with motorola... Isnt it with the service providers who would rather have the bootloaders on the phones locked so they can sell us services we could install for free... ie Wi-fi Calling, Tethering..
I think Motorola's hands are tied.. their customers are the service providers.
Would it make more sense to harass t-mobile and the likes over this?
Click to expand...
Click to collapse
So why is my unlocked/un-branded Defy that is in no way tied to any network also cursed with a locked bootloader?
And if the networks are demanding it, how come not every manufacturer is crippling their handsets in this way?
This is a decision Motorola have made, no-one else.

#UnlockMoto
Thanks :-D
You can also join the #UnlockMoto campain and spread the word on social media networks like Twitter as well as on modding forums and such.
Start by joining the #UnlockMoto Campain for Motorola Unlocked Bootloaders! here: http://twb.ly/UnlockMoto.
Then read: http://bit.ly/UnlockMotoPage

done, signed

signed!!!

Just signed.

adlx.xda said:
Thanks :-D
You can also join the #UnlockMoto campain and spread the word on social media networks like Twitter as well as on modding forums and such.
Start by joining the #UnlockMoto Campain for Motorola Unlocked Bootloaders! here: http://twb.ly/UnlockMoto.
Then read: http://bit.ly/UnlockMotoPage
Click to expand...
Click to collapse
Thanks for posting dude, i've been sending out a tweet for the 2 causes.
Retweet:
http://twitter.com/#!/ibproud/status/50306686350655488

Open discussion

I realize that we are discussing openly the methods to root and possibly illegally obtain access to pay services, but I would expect more people to be discussing techniques and tactics for rooting 2.3.3. When I was testing smart cards, there was plenty of open discussion about memory locations to utilize, or specifically vulnerable loops... etc. What am I missing? Where is the really in depth discussions regarding acquiring root level access and the entire process? All I see is sticky'd threads about 'one click root' methods. Are there any reports of prosecution by Sprint for rooting? Any at all? PM me links please...

i heard somewhere in sprints contract they basically said the phones in your possession, whatever you do to it is up to you.

I think that most of the devs brainstorm via private chat and/or messages.
Some use mIRC channels

Where's waldo?
You already have a new account?
Sent from my PC36100 using XDA Premium App

whatsuphomie said:
i heard somewhere in sprints contract they basically said the phones in your possession, whatever you do to it is up to you.
Click to expand...
Click to collapse
The courts ruled several months ago that the end user of a purchased device can modify that device as they wish since they own it.

Thanks
htown999 said:
I think that most of the devs brainstorm via private chat and/or messages.
Some use mIRC channels
Click to expand...
Click to collapse
Thanks htown! I have seen some IRC channels around here. I have kids and don't have a lot of time for that right now, but i gotta have some fun...
Thanks to those of you who took me seriously. I'm about to install the Eclipse plugin and start some cookin in my own kitchen! I'm only a modest scripter, but ya gotta start somewhere.
I was just hoping to find some help with the EVO specific, and cel phone specific hardware interactions.
If anyone has some helpful IRC logs, such as the ADB tutorial, please PM me.

Legal action -Samsung Knox- need 400 users lawyers will take case

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

Verizon Note 4 Rooted!! Check description

As I was searching the Internet today I came across this! Can anyone verify it??
http://www.usoftsmartphone.com/t410056.html

For some reason I have my doubts about this. Not just that, but there is no link anywhere, just screenshots, which can be easily faked. This kind of thing happens in the gaming console arena all the time. People just do it for attention. Until a recognized developer we KNOW (on here preferrably......hsbadr????) can confirm this, Im going to rule it as fake.

chevycam94 said:
For some reason I have my doubts about this. Not just that, but there is no link anywhere, just screenshots, which can be easily faked. This kind of thing happens in the gaming console arena all the time. People just do it for attention. Until a recognized developer we KNOW (on here preferrably......hsbadr????) can confirm this, Im going to rule it as fake.
Click to expand...
Click to collapse
Although, he has some petty good video of startup, reboot, and maintaining root...as well as showing root checker etc. so time will tell.

The guys a FRAUD. The XDA mods locked down his thread cause he was posting lies about permanent root which he willfully failed to show verity upon request. He is only looking for attention by means of "Thanks." pay him no attention. He's a troll. lol

Farse
This looks like a waste of time...delete.

So there is no reliable system yet to root the Note 4?

They way most of you have been treating and talking about this guy, if I were him and really did have the solution, I'd say "eff ya".

plainbum said:
They way most of you have been treating and talking about this guy, if I were him and really did have the solution, I'd say "eff ya".
Click to expand...
Click to collapse
Agreed. I don't understand why everyone is so uppity. What's the harm in just being patient and having a "wait and see" attitude, instead of calling him a fraud and dropping the ban hammer just because he hasn't revealed details yet. Unless we know for certain that he hasn't achieved root, then I don't think we should push him away, even if we don't like his methods. Keep in mind that there is a language barrier here also, so there may be some misunderstanding.

He already said many times he wasn't going to release it. He said it would hurt his business and Samsung would patch it.
Which translates to I've found something that will work on many Samsung devices so if I release it I won't be able to use it to make money in my business, because having a solution for only the Verizon note 4 is not going to do his business much good as he is from outside US.

spocko said:
Agreed. I don't understand why everyone is so uppity. What's the harm in just being patient and having a "wait and see" attitude, instead of calling him a fraud and dropping the ban hammer just because he hasn't revealed details yet. Unless we know for certain that he hasn't achieved root, then I don't think we should push him away, even if we don't like his methods. Keep in mind that there is a language barrier here also, so there may be some misunderstanding.
Click to expand...
Click to collapse
All you have to do is look at his past post. He did the same thing with an LG device. Posting he has achieved root when he had not. When the mods finally asked him to provide proof he declined to answer. When he's been contacted on his site, his number, etc, etc, he declines to answer the question and left the LG community it's in a complete disarray. We don't need people posting root achieved notices just to get their thanks scores higher. The Note 4 community it's has been thru enough already. And if it was going to hurt his business to release the method, then why release I've achieved root. No thanks, the guys a complete fraud.

I can appreciate that reasoning, thanks.
Here a genuine question, not trying to be argumentative:
How is this situation with vnmobile different than the video posted showing the Galaxy S5 bootloader unlock?
http://www.xda-developers.com/verizon-galaxy-s5-bootloader-has-been-unlocked/
It appears that this dev (beaups) does not plan to release his methods either, yet he is not treated with the same disdain as vnmobile. Granted it appears that beaups has earned respect previously, but at the end of the day the same question remains: what is the purpose of sharing the video?

This guy definitely a fraud. His real name is Ngoc Vu and he's running a business selling tech equipments in Vietnam. Let me throw a few things on the table here.
1) Language barrier issue - Nope I speak his language and had visit his website and his facebood page. Just full of shi...
2)Hurt his business if he released the root fix? Another bull sh... 2 ways he could make money. a) release the fix and collect over 20k cash from XDA b) Offer a service to root the phone with a fee. Guess what? none existed.
Summary - he just want to drive traffic to his web site, and make his business more visible to the world specially XDA where everyone interested in cell phone/tablet and electronic equipments. Case closed!

i just saw this post. And i confirmed he is a Vietnamese guys. like me. ^^
But i am so surprise, because he used the Booloader and ROM from "hsbadr" of XDA forum.
- This is the post of HERO "hsbadr" (By hsbadr, Recognized Developer / Recognized Contributor on 13th August 2015, 10:46 PM) : http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3178148
------------------------AND this the post of the guy in Vietnam ^^ (it was 31-10-2015, 06:02 PM ) . in Asia country like Vietnam, the Day is first, then the Month. So his video was Oct 31,2015. After "hsbadr" released his tutorial. ^^ i wish i can upload photo for you guys.
http://vietfones.vn/forum/showthread.php?1047158
This: "N910VVRU2BOG5 - Android 5.0.1 : Fri, 31 Jul 2015" is f-u-c-king fake ^^
Pls Forgive him!!!

General Oppo MSM Tools has fallen today - I've hacked it

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.