Develop Bugs

A few questions... (Android! Omnia!)

* Mod EDIT *
Thread closed until moderation team has had an opportunity to properly review as a result of soliciting donations.
Hey everyone,
As you may all know, there’s a fairly large demand to put Android on the Omnia. After researching it myself, I decided since no one else is doing it I’ll take the incentive and give it my best shot. Don’t get too excited, since I may not get very far. But before I begin, there’re three questions I have to ask:
*NOTE: I own a Verizon i910 Omnia*
1. How do I extract the bootloader, kernel, and rom from the device? I’ve tried all sorts of rom kitchens and utilities and the things I get are either useless or work but only with i900 roms I downloaded and therefore not very helpful.
2. I need to disassemble WM’s device drivers (for the screen, touchscreen, buttons to start), and port them to a custom Linux kernel (that’s what Android will be placed on top of). What software do you recommend (for disassembling WM drivers for ARM in PE format)? A day’s worth of google searching turned up little to nothing.
3. This will involve flashing my one and only Omnia with bootloaders, kernels, and roms that, in all likelihood, will brick my device as I test it. I read in certain places something about a “jtag” cable. Can I use this to flash data directly to the chips without any kind of software running on the phone? If so, what kind of information can you provide? I don’t really care about my warranty, considering what I’m going to do to it To rephrase the question, what options (besides returning the phone) do I have to recover it if it gets bricked?
If anyone wants to offer their support I’d really appreciate it. I need people experienced with the inner workings of a WM device and also people experienced in Linux, specifically device drivers.

it would be great if you could install the Android OS. but i think we need to wait for the official drivers for Android, even if they would be released by Samsung. i start thinking it is impossible.

I honestly doubt Samsung will go the extra mile for a single product (even one as awesome as the Omnia) and port an entirely different operating system to just one of their products. This is one we're gonna have to do ourself. It is possible to do, I'm just stuck right now because I don't know how to dump the i910's rom, which contains all the device drivers I need to make a full-featured port of Android possible. This is what I need help with. It's really not that impossible, it just takes a bit of work.
Mods, could you move this thread to "development and hacking"? It would probably be seen by the people I want it to be seen by there. Thanks.

hey..dude.. checkup this from this group of ppl @
forum.xda-developers.com/showthread.php?t=431329
may be u can join ..

Hey Guys, I've got an Omnia as well and really really want Android on it. Although I am unable to script. I thought of a way to contribute a bit as well. I set up a website to raise money for the first person or organisation that pulls it off to run Android on the Omnia.
Have a look here:
I chipped in a €100 myself as well to make a start. I hope you guys can contribute some money as well so that it motivates the developers even more.
For the developers out there: "We know you can do it!"
* Mod EDIT *
Link Removed

How can an project be real. If Basics are unknown?
Qualcomm, QCT Tools, Firmware structure etc...
For study:
http://www.4shared.com/file/108584795/bb49ee52/I900_090226.html
Big thanx to barisyalcin.
For Android on Omnia. Good Luck.
The way is the Destination.
Best Regards

Why even bother installing a shell?
the android on the omnia only installs a shell compound, it does not actually convert the omnia into a full fledged Android phone.
I would just scrap it and pick up an actual android phone.

Porting Android to Wave (Replace Bada)

Has anyone tried it yet, what was the outcome?
Is it possible?
Please share your ideas, views and suggestions here.

I think i read somewhere about it, but the project is not continue, unfortunatelly :/
search, maybe you'll find something

Hey Abhishek...
Why do you need to create another thread...??
There are two ongoing threads on the same topic... And if you are interested please head on to those to find out the info about porting android on bada..
Dont create unnecessary threads.... I suggest delete this... or after sometime all we will see in the Bada Section is useless threads....

*facepalm*
Read other topics WWW.ANDROIDPORT.NEt there is the wavedroid project.

Go away and come back when you have some progress for us wavedroid.

Still wondering if wavedroid is a money making exercise or a genuine attempt at getting Android over. The delays don't help the impression this is an exercise being led by folks more eager than actually having the skills to accomplish the task.
I'll be the first to eat my hat if this ever comes to fruition, but I won't be donating anything to something that at this point seems to have only updates on various delays.
Hows this for an interesting post on the JetDroid website...
Not sure why you need the expensive software, it is nice and would help but 95% of the works is already completed for you guys.
To start:
Look for phones with same hardware then use that parts from their android and put the parts into a custom version. You can reuse the /sbin and /system folders from the android sdk virtual machine or if you want better performance use the /sbin and /system of a similar hardware phone android version and just add your init , init.rc , zimage and package this into a rom or dual boot like we do.
CPU:
The wave / Samsung-Intrinsity S5PC110 cpu is much more supported than our s3c6410 and used even by Apple so look at idroid , samsung crespo , HTC 4G android , samsung i9000 for sources for your android files to start from.
Screen:
The screen is possibly the same as S8000 or Spica, wave 3.3" the rest is in other samsung opensource files you just need to mix and match parts.
Obstacles:
The biggest problem might be the cpu and screen + andreno or powervx or Mali display driver but android.so will work until you get to the video driver.
Camera:
Camera is in M910 samsung opensource files / other 5MP camera, there is only a few 5MP camera from that samsung uses so might need to work on the code if you can not find it from a same camera android phone version that is already working.
Now make a good WaveDroid version:
Once you have all this and have it working then you can build a clean custom version of android optmized for your phone. CM for HTC 4G phones might work with almost no or little changes possibly just in the kernel.
The samsung opensource website has the SCH-W850 / SPH-W8500 / SPH-W8550 , this could share some hardware with Samsung Wave as well, similar number codes. Look for a recent code release nov/dec 2010 or later.
Click to expand...
Click to collapse
After reading that, I felt I could almost make an android port myself lol. Clearly there are some very knowledgeable and experienced persons out there.
What really bugs me is the Wavedroid folks have been asking for money for months, yet have shown not a shred of proof they have accomplished anything. Secondly, folks have been asking (rightfully so), why you have not implemented a Paypal widget so people can see just how much money you have raised so far. I know you are using illegal software and thus don't want to let everyone into your inner circle to see the progress, but you have shown and proved absolutely nothing. There are more doubts than positive feelings at the moment.

Please don't let this thread grow to one of two-three pages which is worth nothing, there is already another one just for this purpose

Android port is stuck because programmers dont have any programm to edit the bootloader of wave,so they can not do the port...
If anyone knows any free programm to edit ARM 7 files (like IDA 5.7) please give it to them.
But if nobody knows any programm for this case the have to wait until they have enough money form donations to buy the IDA 5.7
(sorry for my english)

This is outrageous, the fact that you need commercial tools to do what your looking to do clearly denotes your level of incompetence. Look at idroid. i didnt see them asking people for money to buy tools?? And i would say that Apple did a much better job locking down the i range then samsung did with the Wave. If you have stumbled at the starting block just forfeit the race.
Prove to us that you know what the f**k your doing and then you can have your donations.
Generally i supported this project, but then you asked for money. Money changes everything.

sabianadmin said:
This is outrageous, the fact that you need commercial tools to do what your looking to do clearly denotes your level of incompetence. Look at idroid. i didnt see them asking people for money to buy tools?? And i would say that Apple did a much better job locking down the i range then samsung did with the Wave. If you have stumbled at the starting block just forfeit the race.
Prove to us that you know what the f**k your doing and then you can have your donations.
Generally i supported this project, but then you asked for money. Money changes everything.
Click to expand...
Click to collapse
I agree with U

Asking for money, without providing any scrap of proof that anything is even going on, is what irks people here. Not even a simply paypal donation widget exists so folks can see what the $ count is too.
Too many red flags on this one. I know I'm not the first to ask for proof, or even just something other than "we are working it, it'll be done soooooon, give us all your moneys roflwtflolbbq"
So many other android ports happened without need for this software. And also may I point out what seems total ineptitude on the wavedroid team's part. The Galaxy S contains pretty much the identical hardware as the Wave does. In fact you find me a phone that has identical hardware, one running android, the other something else, and tell me we already have as near an android phone as you're going to get. Compared to other port projects, this should have been done in a weekend to be honest.
wavedroid are bogus, and will accomplish nothing just like all the so called Android to Wave projects and groups previously.

I agree with sabian. I don't know a **** about how difficult or easy is this, but i'm pretty sure that there are good developers around here. Why couldn't you start a new project?

I aggre with you guys,it is very odd that they ask for money without doing anythink...
I just posted that if you know any free software that works with ARM7 files it would be good to inform then...
But they have a very good reason to ask for money because if they can not edit the bootloader they can not load anythink else from bada...if they do that the project it would be almost done because wave and galaxy s have similar hardware so with some fixes to scripts they will have a very good androidport to wave..

Bootloaders, Rooting, Manufacturers, and Carriers (long read)

Original Article
Background​I don't believe that I need to introduce myself, but if I do my name is P3Droid. I am a phone enthusiast and have been working in the Android platform for 17 months. I have been very lucky in my short time on the Android platform. I think more than anything I have been lucky enough to be in the right places at the right times. The day I first saw and played with the Droid (OG) I thought “that is the ugliest damn phone I've ever played with”. Then I was asked back into the store by my friend (nameless) to get some time with the Android platform and he began to explain to me how open the phone was and how a “smart” person could do anything they wanted to the phone. That turned what I thought was an ugly phone into the sexiest beast ever. I guess that was approximately October of 2009, and I was excited about the possibilities and dove right in without checking the depth of the water.
I spent much of the year on an open phone and an open platform, and sometime in July I picked up a Droid X. I soon found a great bunch of friends and we formed Team Black Hat. Really wanting to break the bootloader, we spent more hours working on it than we did our 9 – 5 jobs. Eventually we came to the conclusion (with help from some unique resources), that we were not going to accomplish our objective. Every so often we still pluck away at it, but we have moved on to other things that will help people enjoy their Droid phones.
Fast forward to October 2010. I'm still in love with the concept of android, and I've done more than my share of developing, themeing, creating ROMS and even hacking. *Having been involved in so many things and having developed some unique contacts, I have been privy to information that is not disseminated to the masses. Some of this information I was asked to sit on. Some information I sat on because I felt it was best to do so for our entire community. You have probably seen me rant on occasion about what I thought the community was doing wrong and causing itself future pain. Each of those days I had received even more disheartening information. So where does this leave me? It leaves me with a difficult choice to make. What to tell, how much to tell, and do I want to give information out that could possible be slightly wrong. I've worked very hard to verify things through multiple sources, when possible, and some other information comes from sources so reliable that I take them at their word.
This brings me up to today. I've tossed and turned regarding how to say this, and how to express all of the information and my feelings in regards to this information. I guess the solution is to just let you all decide for yourselves what you think and what you want to do.
One Shoe Falls​
Beginning in July, we (TBH), began hearing things about Motorola working on ways to make rooting the device more difficult. This was going to be done via Google through the kernel. No big deal we thought, the community always finds a way. When Froyo was released and there was no root for some time we became a bit concerned but soon there was a process and even 1-clicks. This was good news and bad news to me, because it simply meant that they would go back to the drawing board and improve upon what they had done.
During this time there were still little rumors here and there about security of devices, and other such things but nothing solid and concrete. Until November.
The Other Shoe Falls​
Beginning in October, the information began coming in faster and it had more of a dire ring to it. It was also coming in from multiple sources. I began to rant a little at the state of our community, and that we were the cause of our own woes. So what did I hear?
1. New devices would present challenges for the community that would most likely be insurmountable, and that Motorola specifically – would be impossible to hack the bootloader. Considering we never hacked the previous 3G phones, this was less than encouraging.
2.Locked bootloaders, and phones were not a Motorola-only issue, that the major manufacturers and carriers had agreed this was the best course of action.(see new HTC devices)
3. The driving forces for device lock down was theft of service by rooted users, the return of non-defective devices due to consumer fraud, and the use of non-approved firmware on the networks.
I think I posted my first angry message and tweet about being a responsible community soon after getting this information. I knew the hand writing was on the wall, and we would not be able to stop what was coming, but maybe we could convince them we were not all thieves and cut throats.
Moving along, December marked a low point for me. The information started to firm up, and I was able to verify it through multiple channels. This information made the previous information look like a day in the park. So what was new?
1. Multiple carriers were working collaboratively on a program that would be able to identify rooted users and create a database of their meids.
2. Manufacturers who supply Verizon were baking into the roms new security features:
a. one security feature would identify any phone using a tether program to circumvent paying for tethering services. (check your gingerbread DroidX/Droid2 people and try wireless tether)
b. a second security feature would allow the phone to identify itself to the network if rooted.
c. security item number 2 would be used to track, throttle, even possibly restrict full data usage of these rooted phones.
The Rubber Meets the Road​
So, I wish I had more time to have added this to the original post, but writing something like this takes a lot of time and effort to put all the information into context and provide some form of linear progression.
Lets get on with the story. March of this year was a monumental month for me. The information was unsettling and I felt as if we had a gigantic bulls-eye on our backs.
This is what I have heard:
1. The way that they were able to track rooted users is based on pushing updates to phones, and then tracking which meid's did not take the update. There is more to it than this but that is the simple version.
2. More than one major carrier besides Verizon has implemented this program and that all carriers involved had begun tracking rooted phones. All carriers involved were more than pleased with the accuracy of the program.
1. What I was not told is what the carriers intended to do with this information.
3. In new builds the tracking would be built into the firmware and that if a person removed the tracking from the firmware then the phone would not be verified on the network (i.e. your phone could not make phone calls or access data).
4. Google is working with carriers and manufacturers to secure phones, and although Google is not working to end hacking, it is working to secure the kernel so that no future applications can maliciously use exploits to steal end-user information. But in order to gain this level of security this may mean limited chances to root the device. (This item I've been told but not yet able to verify through multiple sources – so take it for what you want)
5. Verizon has successfully used its new programs to throttle data on test devices in accordance with the guidelines of the program.
6. The push is to lock down the devices as tight as can be, but also offer un-lockable devices (Think Nexus S).
The question I've asked is why? Why do all this; why go through so much trouble. The answer I get is a very logical one and one I understand even if I don't like it. It is about the money. With LTE arriving and the higher charges for data and tethering, carriers feel they must bottle up the ability of users to root their device and access this data, circumventing the expensive tethering charges.
What I would like to leave you with is that this is not an initiative unique to Verizon or Motorola, this is industry wide and encompassing many manufacturers.
So what does all this mean? You will need to make your own conjectures about what to think of all of this. But, I think that the rooting, hacking, and modding community - as we know it - is living on borrowed time.
In the final analysis of all this I guess I'll leave you with my feelings:
I will take what comes and turn it into a better brighter day, that is all I can do because I do not control the world.
Disclaimers:
I am intentionally not including any names of sources as they do not want to lose their jobs.
This information is being presented to you as I have received and verified it. *
I only deal with information pertaining to US carriers and have no specific knowledge concerning foreign carriers.
Click to expand...
Click to collapse
Thoughts? Is there a future for Rooting?

Dear HTC, can we have our phone back

Before you start to think I am about to scream "GPL, GPL, GPL," stop for a second, take a deep breath, and sympathize with the thousands of power users and developers who have been left in the dark and/or ignored in regard to their device being partially unlocked with a seeming false advertisement. This is an opinionated piece in the regard of actually getting what we asked for and were promised to receive.
Not long ago, users and developers alike relied heavily on hackers and logic to achieve S-OFF to get the full experience of their desire for a great(er) experience on their Android phone. Some people buy an overlay device like HTC with Sense, Motorola with Blur, and so on, knowing what entails when they get it, but they anticipate running a stock experience or a heavily optimized build from one of the developers in this community. Recently we took a moment to talk with ToastCFH and Dees_Troy from TeamWin, who are responsible for HTC Dumlock. HTC Dumlock makes the unlocked device further accessible for a few more phones.
Last week we purchased some T-Mobile One S units for our developers and one of them was chosen to go for a test drive and to try out HTC Dev Bootloader Unlock. This is where we got to know each other and a bit more about HTC's online utility, which nonetheless has disappointed thousands more than just a bit. I am going to let everyone know now: do not plan on just stopping at rooting this and calling it a day, I tried to remove bloat with Root Explorer and came to a brick wall of denial. I found out you also cannot flash custom kernels in recovery mode.
"What is affected in retrospect when I unlock?" Let me answer that: It actually cripples your phone. It's probably less risky to take a chance and go for an S-OFF method that could potentially brick your device. As per numerous reports, and some insight from ToastCFH and Dees_Troy, there is a plethora of issues with this process and many gripes and speculation just coming from myself.
A cobb without a Kernel: Flashing a kernel is similar to trying out walking on coals. You have to do the following (coming from ToastCFH at XDA):
fastboot boot recovery alternaterecovery.img
Here's some thought: If you flash a crap/test kernel that doesn't boot, not only can you not pull the battery you have to relentlessly use your power button to get yourself out of the mess to get the phone to shut off (HTC One series). The reason you can do it through "booting" recovery as opposed of using the one you flashed: The boot method is actually using the boot/temp partition, which in the end, is not really the boot partition.
HTC, why are you doing this? Aren't you supposed to be trying to deter users from chasing exploits and trying to gain S-OFF? It sure doesn't seem like it. From this perspective, it seems you will be are pissing off and running away potential customers instead. The image you see above is the warning you receive in HBOOT after unlocking the device via HTC Dev. Note that it doesnt say "unlocked" but a very menacing "Tampered," a word that carries a different set of connotations altogether.
All your system are belong to HTC: ROM Manager uses a script to replace your recovery while in Android. The slight issue is, it requires root. Root is the center of the development universe when it comes to ROMs, kernels, mods and the likes of the bunch. HANDS DOWN, most of the alterations you make to your phone while booted in Android utilize root and the system partition. This is not only a P.I.T.A., it can be a deal-breaker. I will get to that point in a bit. First, let's take a look: How do I tinker with something if the manufacturer tells me I can but in reality I can't? Conundrums. It's amazing: You cannot remove the bloat from your phone, you cannot replace the recovery and you sure cannot replace the boot image while booted in Android/Sense.
Radio killed the kernel dev star: Yes, radio. Those cool P*IMG.zip files you flash in HBOOT, that's out the window... Unless you get an RUU (ROM Update Utility) and go back to the stock firmware. With older HTC devices with S-OFF, you could slap a P*IMG.Zip (essentially a firmware/radio update in HTC's update.zip format) on the SD card and boot into HBOOT. It would check and flash it for you. That whole proces is gone; this entire process of being able to do this on the mobile side is now gone. You will now need a computer to flash the file.
To need or not to need... That is the question: Toast brings up another excellent point: If these measures have to be in place (maybe due to carrier request) why not provide the proper documentation to support the device? We're pretty sure when someone unlocks this device they understand they are giving up any firmware support from HTC.
Then why not give us documentation or utilities to flash fimware.zips from recovery like HTC does? When HTC was the proud Nexus device there was full support and documentation available on how to flash firmware on their devices. This made anyone choosing an HTC device blessed with knowing that their device was not only open and unlocked, but when flashing firmware that it was being flashed correctly to Google and HTC's standards. This code has now been moved out of recovery since right before the move to edify scripting and moved to vendor/htc/ (not arguing this choice as thats where it belongs from a maintaining point of view). But the problem is that vendor/htc is proprietary now. Which means Documentation and support for flashing firmware correctly is not available and left to developers of recoveries for the community to figure out. One would think if HTC was standing behind us that they would step up and give us a PROPER/OPEN/REAL unlock, or if they cant for the lame excuse of security concerns, then give us the documentation and utilities to flash the boot and firmware partitions properly. I mean really... what is there to lose there?
- ToastCFH
An excellent point, and most of you will probably agree with his bomb of logic. At the end of the day, he is right; the unlock method is crap and we find it more of a hinderance and crippling intent rather than a compliance to the developer community who has made them the number one development device for so long. Recently Samsung has taken the torch and led its dedicated developers with fulfilled promises and standards.
HTC, why would you do this? That is far too easy. Clarification, reason, justification, etc., it isn't needed. It's about doing the right thing. HTC has kept the proverbial sprinklers on and now the unlock tool is watered down. My advice for the power user/modder/dev is that this tool is essentially useless. We have been the number one spot for developer support by giving free devices to developers and UI designers to make the device even more fun and unique. We will continue to support, drive, and advocate open development on a supposedly open platform and follow those who make it what it is today. With that being said, it makes us skeptical in giving devices to people that HTC seems to have set a navigation route to Failure Avenue, and know that the developer on hand won't feel shorted. HTC, let us own our devices. Some love the hardware, some love the software, but in the end we love Android.
Lastly, GPL. It is is not made to stretch the maximum time available and take your time. It is probably a good suggestion to set up an HTC gitweb or something of the nature to ensure that when the device is available, the developers that you "support" so much can have free reign at improving your device and moving forward at their own pace. That making the final connection to the developer house, letting the user and developer free you from providing software support. Release the source, fully alert and vigilant. We know it takes time to clean code, but the One X (international) community could really use some tasty kernel source code right about now.
One last note: HTC may not be able to further assist with the firmware/software/OS once unlocked, but you can still support your hardware by giving some documentation on how to proceed with an unlocked device. Giving someone a flashlight with no batteries in a dark house isn't an ideal method of answering our call.
Sincerely,
Your Customer.
If you read this, please take a moment and support your developers and modders that enhance your phone life everyday, by tweeting, sharing or posting on Facebook the following quote:
" @HTC we want our phones back! http://tinyw.in/LNSn "
Thanks to everyone who has read and contributed to this piece.
****
My contribution.

I made it about 60% through and I still don't see s-off released. ;p

acer73 said:
Before you start to think I am about to scream "GPL, GPL, GPL," stop for a second, take a deep breath, and sympathize with the thousands of power users and developers who have been left in the dark and/or ignored in regard to their device being partially unlocked with a seeming false advertisement. This is an opinionated piece in the regard of actually getting what we asked for and were promised to receive.
Not long ago, users and developers alike relied heavily on hackers and logic to achieve S-OFF to get the full experience of their desire for a great(er) experience on their Android phone. Some people buy an overlay device like HTC with Sense, Motorola with Blur, and so on, knowing what entails when they get it, but they anticipate running a stock experience or a heavily optimized build from one of the developers in this community. Recently we took a moment to talk with ToastCFH and Dees_Troy from TeamWin, who are responsible for HTC Dumlock. HTC Dumlock makes the unlocked device further accessible for a few more phones.
Last week we purchased some T-Mobile One S units for our developers and one of them was chosen to go for a test drive and to try out HTC Dev Bootloader Unlock. This is where we got to know each other and a bit more about HTC's online utility, which nonetheless has disappointed thousands more than just a bit. I am going to let everyone know now: do not plan on just stopping at rooting this and calling it a day, I tried to remove bloat with Root Explorer and came to a brick wall of denial. I found out you also cannot flash custom kernels in recovery mode.
"What is affected in retrospect when I unlock?" Let me answer that: It actually cripples your phone. It's probably less risky to take a chance and go for an S-OFF method that could potentially brick your device. As per numerous reports, and some insight from ToastCFH and Dees_Troy, there is a plethora of issues with this process and many gripes and speculation just coming from myself.
A cobb without a Kernel: Flashing a kernel is similar to trying out walking on coals. You have to do the following (coming from ToastCFH at XDA):
fastboot boot recovery alternaterecovery.img
Here's some thought: If you flash a crap/test kernel that doesn't boot, not only can you not pull the battery you have to relentlessly use your power button to get yourself out of the mess to get the phone to shut off (HTC One series). The reason you can do it through "booting" recovery as opposed of using the one you flashed: The boot method is actually using the boot/temp partition, which in the end, is not really the boot partition.
HTC, why are you doing this? Aren't you supposed to be trying to deter users from chasing exploits and trying to gain S-OFF? It sure doesn't seem like it. From this perspective, it seems you will be are pissing off and running away potential customers instead. The image you see above is the warning you receive in HBOOT after unlocking the device via HTC Dev. Note that it doesnt say "unlocked" but a very menacing "Tampered," a word that carries a different set of connotations altogether.
All your system are belong to HTC: ROM Manager uses a script to replace your recovery while in Android. The slight issue is, it requires root. Root is the center of the development universe when it comes to ROMs, kernels, mods and the likes of the bunch. HANDS DOWN, most of the alterations you make to your phone while booted in Android utilize root and the system partition. This is not only a P.I.T.A., it can be a deal-breaker. I will get to that point in a bit. First, let's take a look: How do I tinker with something if the manufacturer tells me I can but in reality I can't? Conundrums. It's amazing: You cannot remove the bloat from your phone, you cannot replace the recovery and you sure cannot replace the boot image while booted in Android/Sense.
Radio killed the kernel dev star: Yes, radio. Those cool P*IMG.zip files you flash in HBOOT, that's out the window... Unless you get an RUU (ROM Update Utility) and go back to the stock firmware. With older HTC devices with S-OFF, you could slap a P*IMG.Zip (essentially a firmware/radio update in HTC's update.zip format) on the SD card and boot into HBOOT. It would check and flash it for you. That whole proces is gone; this entire process of being able to do this on the mobile side is now gone. You will now need a computer to flash the file.
To need or not to need... That is the question: Toast brings up another excellent point: If these measures have to be in place (maybe due to carrier request) why not provide the proper documentation to support the device? We're pretty sure when someone unlocks this device they understand they are giving up any firmware support from HTC.
Then why not give us documentation or utilities to flash fimware.zips from recovery like HTC does? When HTC was the proud Nexus device there was full support and documentation available on how to flash firmware on their devices. This made anyone choosing an HTC device blessed with knowing that their device was not only open and unlocked, but when flashing firmware that it was being flashed correctly to Google and HTC's standards. This code has now been moved out of recovery since right before the move to edify scripting and moved to vendor/htc/ (not arguing this choice as thats where it belongs from a maintaining point of view). But the problem is that vendor/htc is proprietary now. Which means Documentation and support for flashing firmware correctly is not available and left to developers of recoveries for the community to figure out. One would think if HTC was standing behind us that they would step up and give us a PROPER/OPEN/REAL unlock, or if they cant for the lame excuse of security concerns, then give us the documentation and utilities to flash the boot and firmware partitions properly. I mean really... what is there to lose there?
- ToastCFH
An excellent point, and most of you will probably agree with his bomb of logic. At the end of the day, he is right; the unlock method is crap and we find it more of a hinderance and crippling intent rather than a compliance to the developer community who has made them the number one development device for so long. Recently Samsung has taken the torch and led its dedicated developers with fulfilled promises and standards.
HTC, why would you do this? That is far too easy. Clarification, reason, justification, etc., it isn't needed. It's about doing the right thing. HTC has kept the proverbial sprinklers on and now the unlock tool is watered down. My advice for the power user/modder/dev is that this tool is essentially useless. We have been the number one spot for developer support by giving free devices to developers and UI designers to make the device even more fun and unique. We will continue to support, drive, and advocate open development on a supposedly open platform and follow those who make it what it is today. With that being said, it makes us skeptical in giving devices to people that HTC seems to have set a navigation route to Failure Avenue, and know that the developer on hand won't feel shorted. HTC, let us own our devices. Some love the hardware, some love the software, but in the end we love Android.
Lastly, GPL. It is is not made to stretch the maximum time available and take your time. It is probably a good suggestion to set up an HTC gitweb or something of the nature to ensure that when the device is available, the developers that you "support" so much can have free reign at improving your device and moving forward at their own pace. That making the final connection to the developer house, letting the user and developer free you from providing software support. Release the source, fully alert and vigilant. We know it takes time to clean code, but the One X (international) community could really use some tasty kernel source code right about now.
One last note: HTC may not be able to further assist with the firmware/software/OS once unlocked, but you can still support your hardware by giving some documentation on how to proceed with an unlocked device. Giving someone a flashlight with no batteries in a dark house isn't an ideal method of answering our call.
Sincerely,
Your Customer.
If you read this, please take a moment and support your developers and modders that enhance your phone life everyday, by tweeting, sharing or posting on Facebook the following quote:
" @HTC we want our phones back! http://tinyw.in/LNSn "
Thanks to everyone who has read and contributed to this piece.
****
My contribution.
Click to expand...
Click to collapse
Done
Sent from my HTC Desire HD using Tapatalk

Done

I would share it but its got to many bad grammatical mistakes that makes its a hard read plus doesn't specifically request things like S-OFF. The sentiment surely is right though.

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.