I've noticed that a some developers (myself included) would be substantially aided in their efforts if they had access to one or more Galaxy S test devices.
I don't know how successful this will be however I've created this thread as a central place for developers to “apply” for device donations and for members to put their (presumably broken) devices up for donation.
My phone is broken, can someone fix it?
If your phone is broken and you want it fixed then a Samsung Service Centre or your place of purchase is the place to get it done. However if for some reason Samsung won't fix your phone then you can list it here and it might inadvertently get fixed, but please make sure you read this whole post very carefully!
Deciding to donate... zero liability!
If you do decide to list a device here regardless of whether you're donating or lending it to someone the developer that you donate/lend it to is in no way liable for what happens to your phone. The purpose of this thread is so users can donate devices for experimental development. As such there is definitely a chance devices could get bricked or permanently damaged (if they're not already). If your warranty isn't already voided then it certainly will be. If you're not willing to accept this then do not donate!
I would like to think that developers who have been donated devices will return the device to the donator upon request, regardless of whether the phone was donated or lent. However, just in case I would like “donators” to make clear what they expect in regards to their donation, whether they intend to donate, lend, donation time-frame etc.
Which developer gets which phone?
I think it should be up to the donator to decide what projects are more worthy or more relevant to the donator. I'm not going to assign phones to projects unless the donator requests that I do so.
How are broken devices useful?
Obviously that depends on what the developer is doing. To some developers a bricked device may be totally useless. However, for developers working on low-level interfacing (JTAG etc.) then bricked devices are basically the perfect test subject.
Shipping the device and costs.
I think it's only fair that people donating their phone shouldn't have to pay the cost to ship the phone to the developer. However, the return shipping costs (if the donator wants the phone returned) should be negotiated on per donation basis.
If the phone turns on the donator MUST disable all security features, in particular the mobile tracker functionality!
Applying/Listing
Developers or donators should fill out the following forms respectively.
--- Developer Application ---
Project Title:
Project Description:
Device Requirements:
Example 1. A Bell I9000M that in the past had access to download mode.
Example 2. Any device that charges.
Location:
Extra Information:
--- Donator Application ---
Donation Type: [Donating/Lending]
Phone Type:
Phone Status:
Example 1. Stuck in boot loop. Never had access to 3-button download mode... even tried the oven!
Example 2. Doesn't respond to power button or charger... it's dead!
Location:
Developer Requirements:
Example 1. Need the device back in a month.
Example 2. If the device gets fixed I would like it returned.
Extra Information:
----------------------------------- Developers -----------------------------------
Benjamin Dobell < celtichazard* (Returned)
dagentooboy
----------------------------------- Donators -----------------------------------
celtichazard -> Benjamin Dobell* (Returned)
Bold - Assigned
Regular - Unassigned
* - Lent
Project Title: Heimdall (and JTAG Research)
Project Description:
Heimdall is an open-source, cross-platform replacement for Odin. It is currently in alpha and is in need of testing. For more detailed information refer to the Heimdall thread.
I'm also interested in doing some JTAG research that will hopefully help bring "fully bricked" phones back to life.
Device Requirements:
Any Galaxy S (or derivative) phone in any state what-so-ever.
Location:
Melbourne, Australia
Extra Information:
I'm good with being lent or donated devices. I'm also happy to return donated devices if I'm able to fix them.
It might be worth also having "qualifications" as one of the things. Because otherwise, even 10 year olds can request phones...
I am concerned about the liability statement though honestly.. I live in Melbourne, but I am concerned that there isn't a reasonable expectation that the mobile will be working when it is returned (but yes, I'd love to see Heimdell succeed). Also, there isn't any clauses which ensure that provide leverage for mobile's to be returned.
andrewluecke said:
It might be worth also having "qualifications" as one of the things. Because otherwise, even 10 year olds can request phones...
Click to expand...
Click to collapse
I don't think it should be up to me to decide who is qualified. However I will add something to the original thread that makes it clear it is the donators choice as to who they donate to (I'm not going to automatically assign phones to people).
Lending
--- Donator Application ---
Donation Type: Lending
Phone Type:Samsung Galaxy S i9000 european version
Phone Status:
Stuck in boot loop. Never had access to 3-button download mode... even tried the oven!
Location: Country : Mexico State: Chihuahua City: Juarez
Developer Requirements:
If the device gets fixed I would like it returned.
Extra Information: The device was flashed with AT&T Rom
celtichazard will be lending me his bricked phone so that I can perform some JTAG research into unbricking Galaxy S phones.
If anyone is interested in this research and would like to donate to help cover the cost of shipping, JTAG adapters, wires, components, solder etc. that would be very much appreciated.
The Junkheap sounds like a really good idea .
The JTAG research you are talking about; I have no clue what it is. Is it also related to your Heimdall project? Because that did sound interesting.
Also, I checked out your website at the donate link, and the subjects are so horribly technical, I have no clue what that is about either. So I guess it must be really low-level high-tech ^^.
Edit: donated a little bit. Heimdall could potentially be very practical for all of us .
jjwa said:
The Junkheap sounds like a really good idea .
The JTAG research you are talking about; I have no clue what it is. Is it also related to your Heimdall project? Because that did sound interesting.
Also, I checked out your website at the donate link, and the subjects are so horribly technical, I have no clue what that is about either. So I guess it must be really low-level high-tech ^^.
Edit: donated a little bit. Heimdall could potentially be very practical for all of us .
Click to expand...
Click to collapse
First of all, thank you very much for the donation.
The research that I'll be doing with celtichazard's phone is in regards to finding a way to unbrick any bricked Galaxy S phone. The research is not immediately related to Heimdall. However, if I do manage to work out how to unbrick a phone it will definitely be beneficial for everyone. It will also have a positive effect on the development of Heimdall, as it will allow me to try more experimental functionality without worrying about having to send my phone off to the UK for repair if something goes wrong.
Project Title: JTAG
Project Description:
Trying to figure out a way to unbrick "fully bricked" phones.
Device Requirements:
Any Galaxy S (or derivative) phone in a "fully bricked" state.
Also a fully working one would be nice so I can dump the bootloader.
Location:
Madrid, Spain
Extra Information:
JTAG can bring a bricked phone back to life. If I figure out how to make this work your phone will be fully working. If not then it will still be bricked. I would be willing to return the phone in whatever state it is in when I am done. If you are in the United States a USPS flat rate priority mail box to me is $15. If you have a device that you want to ship let me know and if I need it I will pay for shipping one way.
andrewluecke said:
I am concerned about the liability statement though honestly.. I live in Melbourne, but I am concerned that there isn't a reasonable expectation that the mobile will be working when it is returned (but yes, I'd love to see Heimdell succeed). Also, there isn't any clauses which ensure that provide leverage for mobile's to be returned.
Click to expand...
Click to collapse
I only just realised you edited your post.
The liability statement is mostly in place to ensure developers aren't held responsible for damage (which may or may not have been their fault) or postage related issues.
I understand your concerns in regards to having the device returned, but quite simply there is absolutely no way to enforce such a policy. International law is largely a myth so attempting to enforce any such clause would be near impossible. If you're donating to someone within the same country then you certainly could write-up a contract. I'm not a lawyer, but if a donator wants to organise such a contract with a developer then they're certainly free to do so.
The best thing you can do is to make sure you donate to a reasonably well known developer. If the person you're donating to has a reputation to uphold then you've definitely got some leverage if things get nasty.
Regardless I sincerely hope that we won't see that sort of situation here.
dagentooboy is still looking for someone to donate or lend him a phone. His JTAG research is similar to the work I'll be doing and is extremely important. The more people we have working on it the more likely we'll come across a fix.
If someone has a bricked phone they are willing to donate/lend that would be fantastic.
I suggest to link the developer requests and the donator offers in the first post.
This should help to get a faster overview what is needed/offered.
The link to each post is in the upper right corner of each post.
And i would suggest to use this junkheap for all SGS phones (captivate, vibrant, epic 4g, fascinate & i9000), because most of rom/kernel mods could easily be ported to all sgs phones and development would be faster if developers could have access to all sgs phones.
neldar said:
I suggest to link the developer requests and the donator offers in the first post.
This should help to get a faster overview what is needed/offered.
The link to each post is in the upper right corner of each post.
Click to expand...
Click to collapse
Great idea, I just finished updating the first post.
neldar said:
And i would suggest to use this junkheap for all SGS phones (captivate, vibrant, epic 4g, fascinate & i9000), because most of rom/kernel mods could easily be ported to all sgs phones and development would be faster if developers could have access to all sgs phones.
Click to expand...
Click to collapse
Yeah all phones are accepted depending on what particular developers are after. However thus-far I believe myself and dagentooboy have been willing to accept any SGS phone (including derivatives).
yeah any GSM galaxy s phone would be fine... if it is CDMA I won't be able to test the cell side (to make sure I didn't break it).
Project Title: UnBrickable Mod
Project Description:
An end user solution to unbricking fully bricked phones with only a wire and soldering skills
Device Requirements:
an i9000 device which can have the processor removed and not replaced.
Location:
Louisiana, USA
Extra Information:
UnBrickable Mod has been performed on the Captivate and I'd like to get this modification out to you guys in the i9000 sector. This mod allows you to flash bootloaders and not think twice. Thereby increasing development and allowing for repurposing of our phones at the end of their lives as a Ubuntu device, or similar.
This modification will be fully documented and open-source. It will help the entire community get out of a jam without any additional hardware if they have the skills to solder two points on the board. I must locate these points and it requires removal of the processor. I can return the device which will be inoperative if required.
See video for explanation of how easy it will be to unbrick with UnBrickable Mod.
The execution of a single device will allow resurrection of all others.
Project Title: Thor (an alternative to Heimdall)
Project Description:
Thor is aiming to be more stable and up-to-date.
Here is an XDA thread about it.
Here is a list of new features that I want to test:
1) Ability to flash from BL/AP/CP/CSC .tar archives directly
2) Ability do download latest firmware and flash it automatically
3) Ability to flash compressed (.lz4) files directly (newly discovered)
4) You can shut down the device from GUI immediately (no reboot)
5) PIT viewer built-in, with more accurate information
6) Ability to do NAND Erase All (actually it just erases userdata)
7) Ability to do DevInfo (information about the device: model, carrier id, region, serial code)
Device Requirements:
1) Any Samsung device with Odin v3 protocol
2) Lending only, as my parents would tell me to **** off
Location:
Obviously you don't need this.
Extra Information:
None
Project: PostmarketOS, UBPorts on galaxystmd
Old device: but I have multiple. Willing to send one to device to multiple developers with experience and desire to port for proof-of-concept and/or restoring functionality to this device via mainline Linux (PMOS).
UBTouch would be a secondary effort: as it had been ported during the initial launch, but did not get migrated to the UBPorts project.
3rd effort would be porting latest Lineage, modded/optimized ROM, stripped down/optimized kernel. "One final rodeo."
1 Device per person Per Effort.
So realistically I would give each person up to three devices.
Does it seem like Google is attempting to push custom ROMs away from, or off of, their newer devices (Pixel 6 Pro)? From what I can gather reading the forums there are a lot of examples of custom ROMs that have onerous problems. But, maybe that is just the nature of the business, people tend to only post when they are having difficulties.
kcv_earner said:
Does it seem like Google is attempting to push custom ROMs away from, or off of, their newer devices (Pixel 6 Pro)? From what I can gather reading the forums there are a lot of examples of custom ROMs that have onerous problems. But, maybe that is just the nature of the business, people tend to only post when they are having difficulties.
Click to expand...
Click to collapse
I don't think Google cares one way or another about custom roms. I don't think they do anything with custom roms in mind.
Lughnasadh said:
I don't think Google cares one way or another about custom roms. I don't think they do anything with custom roms in mind.
Click to expand...
Click to collapse
This.
Google does what is in their best favor, not for the niche hobbyists. Over the years, you could see the gradual move to making ROM developers lives more complicated.
Google could very easily move away from custom development if they wanted to. All they'd have to do is move to a private license and ditch the apache and gpl open source licenses and keep all source code private. This will never happen as part of the open source platform is contributions from users across the world to improve things. Technically they could release very little device specific source as well and it wouldn't be the end all.
My first phone I developed for was a Samsung Infuse 4g. Development stopped at gingerbread and Samsung never released ICS (android 4) for the infuse due to the almost complete overhaul needed. So no device source and no kernel source from Samsung. Guess what? Within a month or so myself and a few other developers had a nearly fully functional (think there was 1 or 2 very minor bugs) infuse 4g running ICS and kept going from there.
scott.hart.bti said:
Google could very easily move away from custom development if they wanted to. All they'd have to do is move to a private license and ditch the apache and gpl open source licenses and keep all source code private. This will never happen as part of the open source platform is contributions from users across the world to improve things. Technically they could release very little device specific source as well and it wouldn't be the end all.
My first phone I developed for was a Samsung Infuse 4g. Development stopped at gingerbread and Samsung never released ICS (android 4) for the infuse due to the almost complete overhaul needed. So no device source and no kernel source from Samsung. Guess what? Within a month or so myself and a few other developers had a nearly fully functional (think there was 1 or 2 very minor bugs) infuse 4g running ICS and kept going from there.
Click to expand...
Click to collapse
Those were the good ol' days. I miss those times a lot.
scott.hart.bti said:
Google could very easily move away from custom development if they wanted to. All they'd have to do is move to a private license and ditch the apache and gpl open source licenses and keep all source code private. This will never happen as part of the open source platform is contributions from users across the world to improve things. Technically they could release very little device specific source as well and it wouldn't be the end all.
My first phone I developed for was a Samsung Infuse 4g. Development stopped at gingerbread and Samsung never released ICS (android 4) for the infuse due to the almost complete overhaul needed. So no device source and no kernel source from Samsung. Guess what? Within a month or so myself and a few other developers had a nearly fully functional (think there was 1 or 2 very minor bugs) infuse 4g running ICS and kept going from there.
Click to expand...
Click to collapse
Apart from the interest Google has in open and free contributors to the code, would that be legally possible for them to privatize and "close" Android code for Pixels given it is based on Linux? Would that fit the open source license of the original Linux platform?
scott.hart.bti said:
Google could very easily move away from custom development if they wanted to. All they'd have to do is move to a private license and ditch the apache and gpl open source licenses and keep all source code private. This will never happen as part of the open source platform is contributions from users across the world to improve things. Technically they could release very little device specific source as well and it wouldn't be the end all.
My first phone I developed for was a Samsung Infuse 4g. Development stopped at gingerbread and Samsung never released ICS (android 4) for the infuse due to the almost complete overhaul needed. So no device source and no kernel source from Samsung. Guess what? Within a month or so myself and a few other developers had a nearly fully functional (think there was 1 or 2 very minor bugs) infuse 4g running ICS and kept going from there.
Click to expand...
Click to collapse
Thank you all for the reply to my question. The reason I brought it up was because I was looking for any LOS 19 working for the Pixel 6 Pro. I was earlier directed to this one, but dev has changed.
neelchauhan said:
I am no longer working on this ROM. A13 blocks downgrading the bootloader. If you still want this, there are developer support images to downgrade with an updated bootloader.
To add, newer LOS19 builds don't boot on raviole, even the recovery fails.
I also switched to stock A13 for the time being.
Click to expand...
Click to collapse
kcv_earner said:
Thank you all for the reply to my question. The reason I brought it up was because I was looking for any LOS 19 working for the Pixel 6 Pro. I was earlier directed to this one, but dev has changed.
Click to expand...
Click to collapse
I wouldn't risk trying an a12 rom if you got a13 installed.
Custom roms are dieing for sure. The people left over are un friendly the builds nearly allways have bugs hence the amount of wingers the devs get which turns the devs into rude people. Majority of them have private sources they won't share. There dodgey ****s. I attempted to build a rom and failed and couldn't get any help. Instead every rom dev will ban u if u ask for help building there rom. Telegram is a **** storm. Mods on power trips. I have given up on the scene. Let it die with wild fire.
I start understand now a crew of 5 guys will never beat a company at there game. They might apply some patches or shot before the real devs release the proper os version but it not worth the actual bugs in the frame work. Who can trust the security of a team of guys to. They can do what they like to us from messing with the os put virus in it.
fil3s said:
I wouldn't risk trying an a12 rom if you got a13 installed.
Click to expand...
Click to collapse
As long as the A13 bootloader is installed to both slots, the worst that could happen is the firmware would run poorly.
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.