does anyone know if razer will implement project treble? - Razer Phone Questions & Answers

I just read an article about oneplus won't implement project treble to their device and wondering what Razer will do.

Interesting!
So they've gotten smart finally on combatting the fragmentation of versions I bet.
This would be a difficult undertaking, brands/carriers "lose" a certain degree of control. That's probably why most won't do it. That's why MS had such a hard time getting carriers to stock their phones. Carriers didn't want users to have so much control. The prime example of this is anti-root policies.

I sent an e-mail to Razer support about this (I was interested too), unfortunately the reply wasn't very informative:
Welcome to Razer support!
I am afraid to inform you that at this moment I have no information regarding an implementation of Project Treble on Razer Phone!
I invite you to follow us on our Facebook and Twitter and to subscribe to our Newsletter to be always up to date with the latest news from Razer!
Click to expand...
Click to collapse
We'll have to wait and see I suppose.

Related

One app that you should avoid

I recently tried the Graphic ly comic reader app in the Windows Phone Marketplace. Hoping to find a comic reader as good as droid comic viewer I found myself very very disappointed. The controls are shoddy, pinch to zoom is flakey and you have to zoom all the way out to turn the page. This is a far cry from the original video that was shown to consumers.
I understand that newly released products are no always perfect so I figured I would share my concerns with the developer. Their response was shocking and disappointing.
We would like to improve our WP7 app much more in the future, but I
will be straight with you: due to the low sales of the windows 7
phones we have put the improvement of the app lower on our priority
list than the continual improvement of our other apps.
In the meantime: please check out our adobe air application and our
new web application at:*http://graphicly.com/
Any comics that you buy in any of our applications can be read on any
of our other applications. *Your graphicly login should work on any of
them.
Thanks
-******
graphicly
Click to expand...
Click to collapse
Now I know business is business but to release a bad product in the first place is unacceptable especially when the app merely needs some tuning. Due to the lack of planned future support I can only suggest that you guys stay away. Here is hoping that robot comics releases one on WinPho 7.
That is such a load of happy horse****. There are many apps where the developers are frequently updating and providing excellent communications between themselves and the users.
When WP7 takes off - and it will - I hope that many others are aware of the developer's attitude and shut them out. Let the money go to another comic app.
I was very dissapointed with the graphic.ly app, especially compared to what we've seen before. This attitude isn't going to get them any customers. If they're not going to put any effort in the phone app, I don't see any point in buying comics from them or getting their adobe air app.
Shame, i was hovering over it recently....
Thanks for the heads up. I like to stay away from those types of attitudes of devs and updates/support. "EA ruined a good brand after Westwood"
If it's not important enough for them, guess it's not important enough for me to use.
bernaserra said:
I recently tried the Graphic ly comic reader app in the Windows Phone Marketplace. Hoping to find a comic reader as good as droid comic viewer I found myself very very disappointed. The controls are shoddy, pinch to zoom is flakey and you have to zoom all the way out to turn the page. This is a far cry from the original video that was shown to consumers.
I understand that newly released products are no always perfect so I figured I would share my concerns with the developer. Their response was shocking and disappointing.
Now I know business is business but to release a bad product in the first place is unacceptable especially when the app merely needs some tuning. Due to the lack of planned future support I can only suggest that you guys stay away. Here is hoping that robot comics releases one on WinPho 7.
Click to expand...
Click to collapse
That's depressing. Low WP7 sales volume not good. Hopefully this app dev is just a WP7 hater.
Considering that, at least in the US, folk generally wait until their account is due for a subsidized upgrade before getting a new phone (mine just happened to drop in late November ), it makes sense that sales for WP7 haven't exploded yet. I could see holding off on making an app until WP7 grows in market share, but to release a shoddy app, charge for it, and then not support it just because it's not a cash cow yet is simply horrid customer relations. Seeing as the potential dollar is apparently all that matters to these jokers, I'll be sure and speak with my wallet, and mark this one off of the potential to-buy list.
Hilarious. TBQH.
SWYPED from my SUPASONIC
Due to the low sales of Windows Phone 7 ???
Click to expand...
Click to collapse
How would they know this when no one else seems to have this info yet? Perhaps they are basing it on the low sales of their crappy app?
iirc i read some developers are complaining because they have no way to know how much they are selling, and microsoft will start paying in february... so how does this guy know that they are not doing ok?
i call bul****
installed it just to rate it poorly and uninstall it. If you are not going to support your work then don't release it in the marketplace.
OP, I would forward that email to MS support so they know the dev isn't willing to support their app.
nrfitchett4 said:
installed it just to rate it poorly and uninstall it. If you are not going to support your work then don't release it in the marketplace.
OP, I would forward that email to MS support so they know the dev isn't willing to support their app.
Click to expand...
Click to collapse
I concur. That's a damn good idea.
WhyBe said:
How would they know this when no one else seems to have this info yet? Perhaps they are basing it on the low sales of their crappy app?
Click to expand...
Click to collapse
Exactly what I was going to post.
Lol.
Sent from my SGH-T959 using XDA App
On a more positive note, I have contacted Robot Comics, the developer of Droid comic viewer from android. I used thier app right before I went to WP7 and it was very intuitive and easy to use in portrait and landscape. It also supported locally added comics.
After emailing I recieved some very good news.
Thanks Jose! Good news: a WP7 version is in our roadmap.
Best,
--
ROBOT COMICS
Comics for Android, iPhone/iPod touch, iPad, Kindle & more
Click to expand...
Click to collapse
I am not trying to come across as anyone of importance but I love WP7 and would personally like to see it succeed so I figured the best I can do is let the developers know that they have a potential customer. Also does anyone know how I can get in contact with MS support?
bernaserra said:
On a more positive note, I have contacted Robot Comics, the developer of Droid comic viewer from android. I used thier app right before I went to WP7 and it was very intuitive and easy to use in portrait and landscape. It also supported locally added comics.
After emailing I recieved some very good news.
I am not trying to come across as anyone of importance but I love WP7 and would personally like to see it succeed so I figured the best I can do is let the developers know that they have a potential customer. Also does anyone know how I can get in contact with MS support?
Click to expand...
Click to collapse
http://social.answers.microsoft.com/Forums/en-US/windowsphone7/threads
Alex
Sorry about that message from Graphicly - it was wrong.
Hi,
Im Micah, CEO of Graphicly. I am unsure of who would provide you that message, that we are not supporting the Win7 Phone application, but it is wrong.
We continue to develop and maintain the applications that our community desire.
The WP7 app that we put out was our v1. We are working to improve the reading experience and other aspects of the application, as we know its it not perfect yet.
Of the applications we have, our Adobe AIR application has been around the longest and has the most development hours into it.
As the WP7 phone continues to grow, we will continue to develop against it.
If you have any questions, or want to discuss this further, I can be reached directly at 720-248-8499 or via email at [email protected] (GTALK too).
Again, I apologize for the confusion, I will make sure that everyone on the Graphicly team understands our product roadmap.
micah
micahb said:
Hi,
Im Micah, CEO of Graphicly. I am unsure of who would provide you that message, that we are not supporting the Win7 Phone application, but it is wrong.
We continue to develop and maintain the applications that our community desire.
The WP7 app that we put out was our v1. We are working to improve the reading experience and other aspects of the application, as we know its it not perfect yet.
Click to expand...
Click to collapse
Hopefully someone from XDA can validate, but if this is indeed true I thank you for clearing things up Its nice to see brands out there connecting with their customer and stepping up to the bat like this.
Hopefully we'll see the app improved! You could always open it up on CodePlex and let XDA hackers have at it!
It is indeed me - How would you like to verify it? I can give you my mom's phone number... How about this - we have promo codes enabled in the AIR app. Use "techcrunch" (no quotes) and get a free comic. We used it for an old techcrunch article, and I think its still alive. Then when you use the WP7 phone, it will be in there, and you can give me solid feedback on the mistakes we made.
Tell me more about CodePlex. I would be happy to let the community at it. We are doing something similar with our Win7 app. Building out APIs that are secure and can be built on is a personal passion of mine.
micah
micahb said:
Hi,
Im Micah, CEO of Graphicly. I am unsure of who would provide you that message, that we are not supporting the Win7 Phone application, but it is wrong.
We continue to develop and maintain the applications that our community desire.
The WP7 app that we put out was our v1. We are working to improve the reading experience and other aspects of the application, as we know its it not perfect yet.
Of the applications we have, our Adobe AIR application has been around the longest and has the most development hours into it.
As the WP7 phone continues to grow, we will continue to develop against it.
If you have any questions, or want to discuss this further, I can be reached directly at 720-248-8499 or via email at [email protected] (GTALK too).
Again, I apologize for the confusion, I will make sure that everyone on the Graphicly team understands our product roadmap.
micah
Click to expand...
Click to collapse
I did not want to post the name but originally I wrote the email in reply to the email I received about you guys releasing a Google web app to this emai "[email protected]"
I received a reply back from a Audrey Zarr stating what I posted. I sent her a polite email expressing my dismay with that type of business attitude and never got a reply back. I certainly wasn't trying to slander your company but knew it would be best to share this info on the web.
I understand that this is a v1 app and I would have been perfectly happy with a "we are working to improve this app" type of answer. Instead I was given the previously posted information. Currently your app is sitting at 1 star, I would hope you guys would want to improve that. Best of luck on your next release.
yeah... [email protected] is the reply email on our newsletter. Audrey is one of our engineers, and is tasked with answering questions about bugs, issues, feature requests, etc.
Your question is quite valid, and in some ways, her response (we are a small company, and we have to focus on the products our community want) is correct. Except the part about us abandoning development on the WP7 app.
A couple of other points (really just FYI). The video from the MIX conference was a proof of concept. We were asked to show off what Deep Zoom would look like in our reader, and so we did. As the months passed and the WP7 software progressed, it became clear that we wouldnt be able to have deep zoom on the finished app.
Other issues: The dev phone we had was a samsung, which is not even one of the release phones. It made things like having pinch/zoom work properly really tough.
So, do we want to make the app better? Of course we do. We want all of our apps to be solid and work at a high level. I believe that the WP7 platform has potential.
micahb said:
yeah... [email protected] is the reply email on our newsletter. Audrey is one of our engineers, and is tasked with answering questions about bugs, issues, feature requests, etc.
Your question is quite valid, and in some ways, her response (we are a small company, and we have to focus on the products our community want) is correct. Except the part about us abandoning development on the WP7 app.
A couple of other points (really just FYI). The video from the MIX conference was a proof of concept. We were asked to show off what Deep Zoom would look like in our reader, and so we did. As the months passed and the WP7 software progressed, it became clear that we wouldnt be able to have deep zoom on the finished app.
Other issues: The dev phone we had was a samsung, which is not even one of the release phones. It made things like having pinch/zoom work properly really tough.
So, do we want to make the app better? Of course we do. We want all of our apps to be solid and work at a high level. I believe that the WP7 platform has potential.
Click to expand...
Click to collapse
I understand that there were time constraints but phone operating systems as of recent seems to lean on their marketplace for success. A bunch of half baked apps won't appeal to anyone.(see palm) That was my main reason for reaching out. I also understand focusing on what the market wants, Microsoft has deep pockets and this OS will eventually be pretty successful. I will spend my money and time on apps that were well made and supported from the get go. As a vendor of comics I am sure your business relies on repeat business.

Help the International S3 get documentation for Exynos chip

Source
http://forum.xda-developers.com/showthread.php?t=1925709
AntonLiv92 said:
ManCityFC wrote a pretty good statement on the Exynos topic in the CM10 thread. Let's spread this around the Samsung Facebook pages until we get some sources! :good:
Originally posted by ManCityFC
On behalf of the ever-growing Android development community, could you please release full documentation for the Galaxy S3 Exynos chip and full source code for everything relating to it?
As you know, developers are the lifeblood of the Android ecosystem and are generally the people that are developing the most exciting and innovative applications for users. This is being put in jeopardy by Samsung's denial of this crucial information – and is now having a self-defeating effect and forcing these brilliant developers to lose faith in Android. This will ultimately see them developing for other platforms, or not at all. It is crucial that we help these developers understand the most contemporary phone architectures, so they can continue to develop great applications and firmwares for the wider community. I don’t need to tell you how the developer Steve Kondik has managed to develop the Android platform….as you hired him!!
Samsung has generally been at the forefront of mobile/cellular phone innovation and has usually allowed access to this type of non-sensitive information, so other co-innovators can continue to develop for the wider community. There appears to be an arrogance creeping in, and dare I say a slightly bullish attitude that Samsung is now bigger than the customers that are buying your products.
We know you understand the size of the Android community, in fact you also use this community yourself to unofficially beta test your own internal updates and firmware versions, so please, repay the community by releasing this none-sensitive information.
The Samsung Android community are a loyal group of people. They don’t want to move away to devices by Sony, or HTC, but their openness is forcing everybody to rethink their loyalties. Indeed we have already lost one great developer to the Sony community.
Also and finally, please bear in mind; as Samsung evangelists we push your products, we advise others, we really are major influencers. In this day and age, who doesn't ask a geek they know on Facebook for advice on their next technology purchase? At the moment, the answer is “buy Samsung – you won’t be sorry” when they are going to buy a new phone, TV, or any other device... let’s work together to keep it that way please?
Here are some of the biggest Samsung Facebook pages:
https://www.facebook.com/SamsungMobile
https://www.facebook.com/SamsungMobileUK
https://www.facebook.com/SamsungUSA
https://www.facebook.com/samsungmobilecanada
https://www.facebook.com/SamsungMobileRussia
https://www.facebook.com/SamsungMobileIndia
https://www.facebook.com/SamsungAustralia
https://www.facebook.com/samsungmobilemalaysia
https://www.facebook.com/SamsungMobileSingapore
https://www.facebook.com/SamsungMobileBelgium
https://www.facebook.com/SamsungMobileDeutschland
https://www.facebook.com/SamsungNederland
https://www.facebook.com/galaxys3forum
https://www.facebook.com/samsungsupport
https://www.facebook.com/SamsungApps
Samsung Google+ Page:
https://plus.google.com/+SamsungMobile
Let's BOMB them until they surrender! :laugh:
Click to expand...
Click to collapse
Maybe we should throw something about Jelly Bean also!

Petition to make Wave 1/2/3 source code open source - collecting ideas

Hi everyone,
I started this on Sammobile yesterday (where it is already a sticky). Also, german site Badania has wrote about it now, too. The petition is not started yet, this is only for collecting ideas and knowing about your opinions. Recently there was some 'news' saying that the Wave 3 source code was made open source, which turned out to be untrue (the file released by Samsung was only 130kB big). Big letdown for many of us, and Wave 1/2 source codes were not even mentioned.
The current situation
The thing is, at least the Wave 1/2 users desperately need an open source release to continue enjoying their devices. Both devices are great hardware, they have a big community and developers willing to put in some ellbow grease, but, we don't have the means to fix certain stuff, only Samsung has. You might think about the trouble upgrading Samsung Apps and the trouble with push and SHP in general that many Wave users have experienced in the last few weeks and months. You might think about all the small annoyances that you users ask us CFW developers to fix everyday (but we can't). You may also think of the BadaDroid project, and the tons of work put into developing a working modem driver, still with nothing to show to the public until now.
The last official Wave 1 FW is from July (with little to none improvements over the January XXLA1 release), the last official Wave 2 FW is even older. Some of you think (and with a reason) that Samsung themselves are not willing to do any more updates or fixes for these two devices. They have, more or less officialy, abandoned these devices and are not willing to put in any more work. We, as a community, on the other hand are willing to work on these - without pay even -, but our hands and feet are bound behind our backs due to the Wave 1/2 being closed source. Don't be fooled by our recent successes (design changes, ported chinese keyboard and quickpanel) - reverse engineering is like stumbling through the dark in an unknown environment, and eventually we will come to a standstill. With Bada being closed source, we will always lag behind the likes of Android.
Samsung themselves are no strangers to the idea of openness. They plan to make Tizen an open source project, they also develop highly succesfull Android devices and they also did at least say that they are interested in releasing the Wave 3 source code. Also, they are just now planning a big company image overhaul, with a new logo and a new policy of more openness. But, if nothing is done, they will just forget about the 'old' Wave 1/2 devices - guaranteed.
So, what now?
This is where you, the users, the developers, the mods, the bloggers, everyone in the Bada community come in. I've been playing around for a while with the idea of starting a petition for exactly this: To ask Samsung to release in full the Wave 1/2/3 (or for even more Wave devices) source codes. But wait, don't rush things now!
We need a big, coordinated effort, spanning all the Bada sites around the globe.
We need the petition to operate from a site that's easy to use for everyone (that means no complicated signup and no shady stuff), and we need the petition's text to be multi-lingual, translated in all the languages of all Bada countries: german, turkish, azerbaijani, arabic, polish, czech, french, italian, spanish, and a lot that I have forgotten about. We need a great, short text (not as long as this one) for the petition, so that everyone knows even from a quick glance the why's and the uses of such a petition.
We also need supporters, people willinng to spread the word on other sites, especially the big ones such as XDA or Bada-Turkiye, but also the smaller ones. We need every voice, and we need as many people in this as possible.
We need to give Samsung the choice to either publicly let down thousands of customers, or just, finally, give us the source code that we have been waiting for for so long.
Further proceeding - my suggestion
Now, this is what I suggest now:
Don't rush things - we should be collecting ideas for at least a week until we even think about actually starting a petition.
If you're willing to support this case, spread the word or even find more supporters, let us know here.
Double points if you're also a member of some non-english-speaking Bada community .
If you have any additional ideas or concerns, also let us know - this is what this thread is for, to collect ideas and coordinate this.
We need a good short english text for the petition itself (I may come up with something later myself).
We need translations for this text in as many languages as possible. And, no, I'm not thinking about Google translations, but about the good old manual ones.
Looking forward to your opinions!
Big sorry.
But this petition can only Santa Claus make true...
1.
Samsung is not alone patent holder...
Wave 1-3 use Qualcomm Hardware AND Software...
So Qualcomm patents affected...
Nearly same stuff is in hundrets of devices from other manufacturer too, because also Qualcomm...
Not only Qualcomm... think about Quram...
Security and Compression Algos...
2.
Place holder...
Best Regards
i agree this Samsung release the source code wave 1 2 3
Maybe we should think about making the petition not only about Samsung, but also about Qualcomm and Quram. Hopes for Modem drivers and the like might be slim, but chances are we'll get a step forward, at least being able to do something more. I think Bada libraries source codes are well within the realm of possibility, and we could already do a lot with them.
Also... what else could we do now, hoping to keep the Wave 1/2 development alive?
BTW: Christmas might also be a good time to make our wishes come true .
http://www.change.org/petitions/samsung-we-want-a-good-working-bada-for-all-devices#
Why not continue this petition...
with 1,435 supporters
Click to expand...
Click to collapse
Best Regards
adfree said:
http://www.change.org/petitions/samsung-we-want-a-good-working-bada-for-all-devices#
Why not continue this petition...
Best Regards
Click to expand...
Click to collapse
That would be a good thing, but - I don't think that we will get Samsung to fix it themselves, and the petitions text is not clear about alternatives such as open sourcing. I think it's a different thing.
Hi Guys...
I am a writer from Badaforums.net.
1 month back,we planed to file petition for open source bada and we got good response.
but,after sometime we dropped the plan as we needed some reliable(and known) person to file the petition.
we have a draft ready for the petition...if u want,u all can have a look at this...
we can use this to file petition if u want...I can give the text file(only to reliable person)...
link is as below :
http ://www.badaforums.net/forums/announces/petition-request-samsung-support-bada-update-t7183.html (Refer Image)
Regards,
WaveGuru
Nice...
You mean the attached one?
I hope, it is okay, that I added your portal as Supprter at our article as official supporter...
Taxidriver05 said:
Nice...
You mean the attached one?
I hope, it is okay, that I added your portal as Supprter at our article as official supporter...
Click to expand...
Click to collapse
Yes,its OK.
I don't remember whether this is the final draft or not(have to search my machine ) ,but we can use the final one.
but,before that we need to gather support from all sites.
and BTW,Badaforums is not my portal...i am just writer of that forum
Regards,
WaveGuru
waveguru said:
Hi Guys...
I am a writer from Badaforums.net.
1 month back,we planed to file petition for open source bada and we got good response.
but,after sometime we dropped the plan as we needed some reliable(and known) person to file the petition.
we have a draft ready for the petition...if u want,u all can have a look at this...
we can use this to file petition if u want...I can give the text file(only to reliable person)...
link is as below :
http ://www.badaforums.net/forums/announces/petition-request-samsung-support-bada-update-t7183.html (Refer Image)
Regards,
WaveGuru
Click to expand...
Click to collapse
Nice! I would, however, suggest to make this a bit shorter. People seem to be too lazy to read these times . Also, set the accent on the Open Source release and include Qualcomm in the petitions recipients list. Although this may sound pessimistic, I'm amost sure that Samsung themselves won't do any development or OS updates for the Wave 1/2 (and smaller Waves) themselves.
I guess I should give some more details. Also, for those too lazy too read the whole text: Just jump to the paragraph that answers your question.
What is this about?
We want to ask Samsung to release the source codes for the Wave 1/2/3 firmwares and Qualcomm to release the accompanying hardware drivers (the Qualcomm part is an additional proposal by me).
Why is this important? / Why should I promote this or participate?
For me personally, this is something of a last hope, especially for the Wave 1/2 devices. I should know being a CFW developer myself: With what we got now, we just don't get far, and there's tons of stuff that we just can't fix (because we don't know how it works, because we can't do any changes... etc). Also, think about the BadaDroid project, which will likely get a big boost from a source code release (modem driver, anyone?). Without the open sourcing we will eventually come to standstill, and that point is not too far in the future.
Why now? / How is this different from earlier petitions?
First of all: This is the first petition specifically made to ask Samsung to release the source code. Now is a good time for this, because Samsung is planning a complete brand makeover over thenext few weeks and months. With this brand makeover comes a new policy of openness, which can only be good for this petition to reach its goal.
"The Wave 3 Bada OS is already open source." / "They'll release anyways because of Open Source Tizen."
I can assure you, it is not. Although this news was on several big Bada news site during the last two weeks, the news turned out to be untrue. The file provided by Samsung is only 130kB big and contains something, but not the Wave 3 source code. It is worse for the Wave 1 and Wave 2 devices, cause these two will be just forgotten about if we don't act. Remember, Tizen is only planned for the Wave 3, and I'm not even sure if that is official.
"This won't work."
Of course, you won't have any guarantees this will work, even if you participate or promote this. The alternative - doing nothing of the like and just hoping for the best - won't most likely do you any good either (read the second paragraph for my personal opinion). Also, we're open to suggestions on how to do this the best way. We want the whole Bada community in this, and we want to listen to your opinions and proposals.
We already have supporters such as german site Badania.de, czech site mojebada.cz, US based site badaforums.net and we're in good hopes of getting even more of the big and smaller ones to support us. This is planned to be a big global effort.
"The modem driver is owned by Qualcomm, not Samsung."
So, you're interested in BadaDroid development specifically? That's right, and that's also the reason why I'm suggesting to add Qualcomm to the petitions recipient list.
Quram algorithms sourcecode is what they sell, so they won't publish it.
Qualcomm AMSS sourcecode - forget it.
Parts of Samsung SHP source - maybe, but from my experience with Samsung HQ I wouldn't count on much. ;P
If we all want to start with this petition,we have to start early and with full proof plan.
but,we will need support from whole bada community and many sites.
I am ready to help...with my blogging and ideas...
Regards,
WaveGuru
We of badaos.net (Iranian Bada forum) are ready to sign the petition. Our forum has 20,000 users (about 3000 active)
Thanks everyone for their support!
Waveguru and nip_miniw, can we add you to the list of official supporters? Maybe also your sites (badaforums.net and badaos.net)? And, don't think wrong if it has gotten a little bit silent here, we're still working on this! But, we also still need more supporters.
If you're willing to help, post here, please.
Rebellos said:
Quram algorithms sourcecode is what they sell, so they won't publish it.
Qualcomm AMSS sourcecode - forget it.
Parts of Samsung SHP source - maybe, but from my experience with Samsung HQ I wouldn't count on much. ;P
Click to expand...
Click to collapse
You're 100% right about the Quram (QMG images, anyone?) source codes, and probably about the Qualcomm AMSS source code, too. But, with your new low level BadaDroid modem driver - would we even need the Qualcomm source anymore? Also, for the rest, I think anything will help, right?
k8500 said:
Thanks everyone for their support!
Waveguru and nip_miniw, can we add you to the list of official supporters? Maybe also your sites (badaforums.net and badaos.net)? And, don't think wrong if it has gotten a little bit silent here, we're still working on this! But, we also still need more supporters.
If you're willing to help, post here, please.
Click to expand...
Click to collapse
I think I can help too,,
I have a little group named BadaIL, we rleased 5 roms until today..
what can I do?
k8500 said:
Thanks everyone for their support!
Waveguru and nip_miniw, can we add you to the list of official supporters? Maybe also your sites (badaforums.net and badaos.net)? And, don't think wrong if it has gotten a little bit silent here, we're still working on this! But, we also still need more supporters.
If you're willing to help, post here, please.
Click to expand...
Click to collapse
What should we do as an official supporter?
k8500 said:
Thanks everyone for their support!
Waveguru and nip_miniw, can we add you to the list of official supporters? Maybe also your sites (badaforums.net and badaos.net)? And, don't think wrong if it has gotten a little bit silent here, we're still working on this! But, we also still need more supporters.
If you're willing to help, post here, please.
Click to expand...
Click to collapse
Hi k8500,
I am ready to help u all.I also have a plan in place.if you want,we can discuss this over PM.
but,I believe that making Bada as an open source should be one of the thing in petition.
we should also need to ask Samsung to provide us bugfree bada...as current bada firmware is not bugfree.
if we can't play HD games with current firmware...if we need to switch off our wave every time to clear ram...then its Samsung DUTY to provide us bugfree OS which they promised.
As many said that this will not change anything... Samsung will not do this...
It will be Samsung's decision whether they want to provide their customer bug free product or not ...but as a customer...as a money payer...I want to try to make Samsung realize that what they are doing is not RIGHT.
Thanks and Regards,
WaveGuru
I think...
At first we need an overview, who will officially support this petition...
We (badaNIA) will definitely do so...
Need name of plattform and contact infos...

Let's get the minuum keyboard on the Moto 360

EVERYBODY get on and email them!! Make sure they know there's a demand! Maybe if enough people request this it will happen. Here's their email.
[email protected]
I emailed minuum and this was their response.
Thanks for letting us know! Unfortunately, based on current development priorities it seems unlikely we will have a finished version for the Moto 360 anytime soon.
If you haven't already, I recommend following us on your preferred social media network(Google+,Twitter,Facebook) and/or signing up for ourmailing listin order to receive the latest Minuum news, including any plans for a Moto 360 release.
All the best,
I joined the mailing list a couple days ago and put 360 as my watch. If demand is high enough, it will come.
I sent them an email as well saying a huge part of XDA is requesting it, etc.
A post in a different topic:
furiousgtz said:
I also emailed them last week..
"Right now we are very focused on our iOS release but we hope to resume development on our circular version soon. I recommend and signing up for our Smart Watch Mailing List(http://minuum.us4.list-manage1.com/subscribe?u=ca045cd04e580f1a87d5b9c63&id=3f537d0efb) to keep up to date with all Minuum for smart watches related news."
...
Click to expand...
Click to collapse
So be patient. It'll come. iOS just has a bigger user base than Moto 360, so that gets priority
Wim!! said:
A post in a different topic:
So be patient. It'll come. iOS just has a bigger user base than Moto 360, so that gets priority
Click to expand...
Click to collapse
I had email conversation with Prem Business Dev @ Minuum. Since there was no demand the project was put on hold. Now they are working on a working beta.
furiousgtz said:
I had email conversation with Prem Business Dev @ Minuum. Since there was no demand the project was put on hold. Now they are working on a working beta.
Click to expand...
Click to collapse
Hell ya!
furiousgtz said:
I had email conversation with Prem Business Dev @ Minuum. Since there was no demand the project was put on hold. Now they are working on a working beta.
Click to expand...
Click to collapse
Are you sure? This is an email I just got from Prem:
"Hi Omar,
Thanks for the input and we will definitely take it into consideration.
You would be surprised at the development resources necessary to completely rebuild Minuum for a circular watch face. Though we would love to just fully develop every cool permutation of Minuum, we are constrained by the resources available to us.
To be honest, the only realistic way we might be able to justify doing this is if the Android Wear A. officially opened up their platform to third-party keyboards and B. if a circular watch manufacturer engaged us in some sort of partnership.
Though this could happen, I don't see this being likely in the very near future.
Best,"
I replied back to him asking for a beta if possible or something that can at least be temporarily functional for the time being until greater resources are available.
opasha said:
Are you sure? This is an email I just got from Prem:
"Hi Omar,
Thanks for the input and we will definitely take it into consideration.
You would be surprised at the development resources necessary to completely rebuild Minuum for a circular watch face. Though we would love to just fully develop every cool permutation of Minuum, we are constrained by the resources available to us.
To be honest, the only realistic way we might be able to justify doing this is if the Android Wear A. officially opened up their platform to third-party keyboards and B. if a circular watch manufacturer engaged us in some sort of partnership.
Though this could happen, I don't see this being likely in the very near future.
Best,"
I replied back to him asking for a beta if possible or something that can at least be temporarily functional for the time being until greater resources are available.
Click to expand...
Click to collapse
Yes. From our conversion, it looks like they have been working on the Moto 360 and the keyboard is currently in development. I would like close to finish product to try because I have a feeling this might drain our battery.
furiousgtz said:
Yes. From our conversion, it looks like they have been working on the Moto 360 and the keyboard is currently in development. I would like close to finish product to try because I have a feeling this might drain our battery.
Click to expand...
Click to collapse
It has almost no effect to battery life on my g watch. If that means anything. Couldn't be that much different
Guitarboarder28 said:
It has almost no effect to battery life on my g watch. If that means anything. Couldn't be that much different
Click to expand...
Click to collapse
Agreed. Keyboards are not supposed to drain battery. Their coding is not that vast where it requires so much memory to be used. Someone got the STOCK android keyboard to come up by accident if you saw in the minuum thread. Maybe we can utilize that in the mean time? Anyone know how to enable it? I know adb has to be used. I'm assuming Minuum used the stock apk and built upon that.

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.

Categories

Resources