Related
I would like to kick this project back off following the withdrawal of tuxhero.
After putting the feelers out and speaking with the developer responsible for the vogue android Kernel build & port I would like to Try and bring those guys onboard and am looking at a way to source them with a device. Further conversations need to take place and definitive project scope and tasks defined with much more transparent approach to the code development.
I have registered androidkernel.com and am asking for feedback from you all on how you think you would like things to pan out. My role is with Project Management and have a wealth of experience in that area, so I would be looking to appoint a team of people to work on the project and either set bounties for milestones or listen to other options and feedback on reaching our project goals.
Hopefully something of value can be achieved and I would be grateful to hear from the previous developers for any assistance available. We can create a website or use github or google code, opinions wanted and lets not rule anything out.
Sangreal
I would be glad to help out with this project. But since I dont have much time (I work 8-10hours/day as a developer) I would be glad if this would be an open development for all to contribute to.
Also it would be nice if the technical documents that Tuxhero has was posted to the developers so that they could be able to make progress faster.
Lets hope we can get android for our device.
I'm in agreement totally - open source, more transparency would be the aim.
very nice ...
but we should ask tuxhero, to share his researched information and diffs.
tuxhero actually didn't get anything done at all. He was making fake posts but in reality he wasn't doing anything.
Lets try not to get into any of that, but I agree there was very little transparency or visibility of code development.
I have asked Tuxhero if he could handover documentation and anything else to kickstart things so whether that is provided we shall see.
Sangreal
sangreal said:
I would like to kick this project back off following the withdrawal of tuxhero.
After putting the feelers out and speaking with the developer responsible for the vogue android Kernel build & port I would like to Try and bring those guys onboard and am looking at a way to source them with a device. Further conversations need to take place and definitive project scope and tasks defined with much more transparent approach to the code development.
I have registered androidkernel.com and am asking for feedback from you all on how you think you would like things to pan out. My role is with Project Management and have a wealth of experience in that area, so I would be looking to appoint a team of people to work on the project and either set bounties for milestones or listen to other options and feedback on reaching our project goals.
Hopefully something of value can be achieved and I would be grateful to hear from the previous developers for any assistance available. We can create a website or use github or google code, opinions wanted and lets not rule anything out.
Sangreal
Click to expand...
Click to collapse
You should get in contact with TuxHero at least to ask about his technical documentation on the Blackstone and also if he is able to share any code. There is no harm in two teams working on this brilliant project!
So are the Vogue team really willing to try and crack the Blackstone? Do they need an actual handset?
Edit: If you actually managed to WORK WITH Tux that would be awesome
Transparacy is the clue.. there are a lot of smart heads here that may decide to contribute if the project is open for all..
good luck guys..
Good luck with the management Sangreal, its looking good!
Hope you can gather a good team.
nizzon said:
Good luck with the management Sangreal, its looking good!
Hope you can gather a good team.
Click to expand...
Click to collapse
Allthough I do not use the Touch HD for the moment, I wish You all the best. I'm sure You will make it!
If TuxHero does not provide You with the documents he got, I say his intension was only to get 5 minutes of fame.
im happy this project has started, but what plan do you have in mind to get the vogue developers a blackstone? What i mean to say is that even though the blackstone is starting to get a tad dated, its still a very expensive device.
maybe you could get the donation pot from the other thread. that just about added up to the cost of a blackst... oh.
This sounds great.
let us keep this thread clean of the thing other people have done in the past.
and support the topic starter with every bit of information we could give.
i hope he could build a android kernel for the blackstone.
Just a suggestion..
Perhaps the following thing to do would be to list things what needs to be done, what is high priority and is related to what. Also if the task/s could be categorized by difficulty (read: time expected to complete).
Then after we have a list, we can start addressing task/s to people or smaller teams.
I also suggest that there would be some kind of progress bar per task (how much is completed of the task and what is the estimated time for the task to be 100% complete, what is working and what is not). Then there would be no need for people to ask questions like "when is this ready?".
The last thing I would suggest is that we make a list of people that are willing to contribute and with what (read: I would like to contribute and I have skills in ______________)
I would like to contribute with code but I have no experience of hardware coding so I guess it is better I stand aside. However, if You need a forum setup (live chat etc etc), just let me know. I do not want to step on any toes but if you need someone to help with trying to manage the project, I'm absolutely willing to give a hand.
My developing skills are close to none existent,
however any designs (web design, graphic designs and stuff like that) i can do well (or atleast other people think so)
I can also do any testing, if any of this may be useful, let me know.
- Dan
Thanks for all the suggestions so far and I will get in touch with those who have offered skills in other areas to assist where possible, I appreciate a lot of people are waiting for some value in this port and at least a fully implemented kernel.
It will take a couple of days for me to touch base with some of the developers on here and I will need to discuss things in more detail with them whilst at the same time getting the base requirements fulfilled on which to start the project off properly, after which there will be a kick off in some form.
My intention regarding getting a device for them if needed was to contribute myself as well as set up donations however bearing in mind the debacle of people donating before and nothing really progressing I am somewhat conscious of doing this properly and not in the business of obtaining something for nothing so definitely need some good suggestions on that aspect.
make a bounty
no donation, get that f**king thing out of your mind... as soon as the project is done, then open it. Not that I don't value WIP, but otherwise it will only lead to the same disasters we had in the last two attempts... (and I'm not talking about the other devices or other development attempts)
"oh yeah, why is the thing not out yet"
or
"we gave you money, where's the progress"
will be questions we always will see, even if that person didn't donate.
Let money out of the game, it spoils everything.
I personally would still love to wait for tuxhero. Not because I have donated, but simiply believe that good people is all around. BTW, it is always good to have more and more developer to join. Thanks everyone.
Apparently cash is going to be the pilot light and life cycle motivator of such a massive project. Qualified developers a project manager and loads of volunteers. The consensus is $50 (US) per person. That seems far too inexpensive if such a project is to reach a satisfactory conclusion. I agree, giving up our hard earned cash to persons unknown, for unknown effort is not a productive way to go.
What is needed is an escrow: Donations held until specific milestones area reach, as predetermined. Personally, I don't want to give, for example, $250 and some one else $50, with the expectation we each receive the same result. Then again, if specific donations are mandated then this becomes a private project. Oh boy! Back to square one.
No, here's the deal: Each person donate what they want with the donation kept secrete. Either a service or a reputable member hold the donations, perhaps in a paypal account until a bounty release is authorized.
I'm a little less than optimistic, but I am quite agreeable (and already have) to donating to this worthy effort.
http://www.cyanogenmod.com/blog/the-state-of-cyanogenmod
The State of CyanogenMod
August 21st, 2011
kmobs
6
I’ve been reading rumors that CyanogenMod’s core philosophy is changing, that we’ve been sold, or that we’ve given up and I want to go on record saying none of this is true at all. As you may know, there are only a handful of people that can approve changes for CM but a lot of developers for it. You may have noticed that we are operating at a slightly slower pace than normal, but that’s simply because we’ve been busy and real life responsibilities come before this project. No one is getting paid to work on the product.
You have most likely become aware that Cyanogen has been hired by Samsung, as that news is traveling through the Android community like wildfire. He is not leaving the project. Samsung is aware of his involvement in CM and there are no qualms from that end. He hasn’t been active recently because he is in the process of relocating to a new city for his new job, that’s all. ChrisSoyars has been hired by Grooveshark and is currently working on projects with them. Koush is working on his DeskSMS application as well as ClockworkMod recovery. And finally, my semester is starting as are my medical school interviews.
As they have before, our insane schedules will calm eventually and we can devote more time to the project. But just because we aren’t around to approve changes doesn’t mean development has stopped or even slowed for CM. There are 40+ talented developers programming behind the scenes night and day to give you the Android distribution that you have come to know and love. On top of all of the above, we are currently in a soft feature-freeze for another 7.1 RC. (You can call it a feature slushie if you like) Because of this, we are reluctant to approve new features that may prove problematic for certain devices for the sake of the stability of the entire tree.
All I ask is that you bear with us during this hectic time.
Click to expand...
Click to collapse
I seen this in my Twitter feed and figured I'd share it here. It's the story of cm. How it all started..really investing stuff. He also talks about launching an cm installer that will be available in the play store in the next few weeks. Check it out and show your support people!
http://www.cyanogenmod.org/blog/a_new_chapter
Sent from my Nexus 4 using XDA Premium 4 mobile app
this is from G+, from the developer of Focal, and why a bunch of contributors/developers for cm are upset about the whole thing..
Guillaume Lesniak originally shared:
I remained silent about the whole Focal relicensing troubles for now. There was a lot of drama between the app being GPL, and the fact Cyanogen Inc wanted to use it, which drove some frustration between me, some CM contributors, and CM leaders. As a result, to avoid any problem, Focal has been removed from CyanogenMod. I think you deserve explanations and “behind the scenes” view on how all of this happened, and to know it’s not just a last-minute decision or ragequit.
This is the true, fully-featured story of the “Focal drama”. It's not a rant about how Cyanogen Inc is bad or anything (and it can be a good thing, with a few conditions, see at the end of the post), but just an insight on how this all happened, and how some people were and are feeling.
A few months ago, I decided to work on an app to replace AOSP’s Camera app after +Steve Kondik expressed concerns about the camera experience on CyanogenMod in a G+ post. I decided to take the challenge, and build up a camera app that would be up with users’ expectations: accessible and innovative UI, but fully-featured.
You all know how that worked out - the app has been out for some time now. I’ve been keeping the “internal” CM team (read: the CyanogenMod Dev private G+ group) tuned with my progress, releasing them mockups, screenshots and videos of the progress. Luckily, nobody ever leaked what it was, even with the big storm we started with the Nemesis trailer.
A few days before we started organizing Focal’s launch, I was approached by +Koushik Dutta and +Steve Kondik . They wanted to talk to me about CyanogenMod’s future developments, that sounded cool. Koush told me in a video chat Cyanogen’s plans since he left Samsung: they found investors, and they’re ready to push forward Cyanogen Inc, a company selling services for CyanogenMod. At first, that sounded amazing, getting a few bucks for working on something I’ve been doing for free for some time. That would allow the student I am to get some stuff and get a kickstart for my future life. That would have given me the chance to spend more time on CM, as I wouldn't need to work elsewhere. Now, I didn’t have much information about what were Cyanogen Inc plans to make money, but I expected it to be through some kind of services - koush told me about CMID, which later became CMAccount, or other premium things like a one-click installer, or even a CMPhone. That sounded like a nice addition to CyanogenMod, leaving the community intact, and adding more value to the software distribution.
I had a similar chat with Steve, where he explained me some of the other aspects of Cyanogen Inc, his philosophy about it, etc. Okay, that sounds like a good plan, get me involved and enhance the open distribution I know and love. I have a few emails back and forth between Steve, Koush and me, talking about what I could work on, what I could enhance on Focal, etc. They’re telling me they’re looking into contracts, and I wait.
That’s when the “drama” started.
I got a Hangouts chat from Koush, saying that Focal would need to be relicensed because GPL isn’t ideal -- wait what, not ideal for an Open Source project?
“The issue is that we need to be able to relicense it”
“It’ll be open as GPL, but CM can do what they want with it.”
Yes, Cyanogen Inc. will need to do changes in CyanogenMod’s source code - because here’s another way they will finance the project: customization for their customers (e.g. carriers). This will imply the work done by the community will be sold to a third party by Cyanogen Inc, and that they have to do changes that they cannot put online publicly. A future conversation with Steve Kondik will reveal that they might need to put hardware-specific enhancement for some camera devices, and that has to be hacked in the Camera app code. Putting these changes inside Camera apps instead of Hardware Abstraction Layers (HAL) could break other apps, which ironically kind of go against the goal of CTS (because then, only the “official” camera app will have those enhancements). Of course, those hardware enhancements are trade secrets, so they cannot be published back to CyanogenMod’s public repositories...
So this is where I started to feel screwed. I didn’t think much further, but I felt like I had no other choice but comply with Cyanogen’s relicensing, and allow them to do whatever they want with my code, and sell it customized to their vendors. They used the Contributor License Agreement as an argument, saying that basically they could do anything with my code since I submitted it.
At the same time, the “cyngn.com” domain was discovered, and concerns rised about what the hell it was. People such as pulser_g2 started to find connections between Cyngn.com, Kirt McMaster, Steve Kondik, Koushik Dutta, and all these people working at a “secret company” in a “secret location”. From ways I cannot even explain, he was able to come up with everything Koush and Steve told me, how they’d make money, and what are their future plans. Since he already knew everything, I told him about what was going on with Focal licensing, and he came up with the fact that this wasn’t legally right: the software is licensed as GPL, the repository on CyanogenMod’s github is forked from my GitHub, so it didn’t go through the Contributor License Agreement (which only applies to Gerrit submissions), and the Berne convention can prove through the commits history that I did fully write the app, and not Cyanogen Inc. - and even if the CLA would apply, it only allows them to sublicense the software, not relicense or dual-license it without my permission.
I didn’t want to be a jerk on that licensing story, and went ahead to resolve the issue directly in private with Steve. At the same time, other people such as Andrew Dodd (Entropy512) beginned to hear echoes about something was going on with Cyanogen, and heard about the GPL licensing issues around the time Land of Droid revealed the connections. He got really upset about that, getting only silence or vague answers from CM leads, turning around sentences.
That’s where they started lying to the community, denying they had something to do with cyngn.com, denying there was a commercialization of CyanogenMod going on. When people said “Why would Focal get relicensed?” they would just say “No, it’s not relicensed. It will stay GPL.” - yes, that’s where “relicense” became “dual-license”, where the app would remain GPL publicly, but still allow Cyanogen Inc to do what they want with it. But they didn't mention that publicly.
pulser_g2 raised some points on an XDA post that became quite famous, quoted by some news websites, and raised to the attention of some CM leads.
The official answer was: “Don’t interfere, don’t reply, let it go”
So, they didn’t confirm or infirm that CyanogenMod was or was not going commercial. If it wasn’t going commercial, they would have denied it. But here, they ask to “let it go”. Why not tell the truth? For them, it was better to just sweep it under the rug. But who was right in the end?
At that point in time, I still had no news about the contracts I was meant to receive weeks ago for working with Cyanogen Inc on Focal. I pinged ciwrl, who told me to check with koush, who told me to check with Steve, who didn’t reply.
At that time, they also started scrapping features from CyanogenMod. Device’s “Advanced settings” disappeared, without getting a proper replacement first. Some features aren't considered as useful enough, and didn’t make it into the new CMHW HAL. Even if users want something, they won’t get it if it’s not useful enough. Save to external SD disappeared as well from the AOSP Camera app, because it breaks Google’s CTS. Root access is planned to be COMPLETELY removed by default, and to be downloaded in a separate package. Users don’t use root anyway, they say. All of this because of a future CyanogenMod Phone, which has to pass CTS to get Google Apps officially. Want some exotic features? Too bad. You won’t get them if Google don’t. Wasn’t that the point of CyanogenMod originally? Derp.
That’s when my concerns started to raise about the community contributions. People such as +Nebojša Cvetković contributed a lot of features to CyanogenMod’s launcher “Trebuchet”, and felt bad about not getting any reward for his work, when Cyanogen Inc. would make money out of it. Same concerns were raised by other maintainers and developers who contribute, or used to contribute to CyanogenMod. It was the last bit required for multiple people to leave the CyanogenMod development community, or for some users to simply stop using CyanogenMod. They didn’t know exactly what Cyanogen Inc was up to, but since the leaders would just lie to them to hide the truth, they felt let down. And it was clear from my chats with Steve that they had no ideas or plans, besides contracting everyone, to reward contributors. But they cannot just contract everyone, like nebkat as he’s not old enough yet to have a contract. Some other people just don’t want to be contracted, but still want to get a reward. It’s only recently that I told Steve that people would be totally happy with some perks (computer stuff, t-shirts, usb drives, devices for big contributors, etc.), and it seems like he didn’t think about that at first.
This continued for some time, until now. Cyanogen Inc is now public, and they revealed (part of) their plans for the near future. And a sentence struck me on most news sites that relayed the news: they talk about “Cyanogen’s new Camera app” -- what WHAT? So it’s Cyanogen’s camera app now? It not a CONTRIBUTION anymore?! - They claim it's their app, and I still had no news about the whole licensing thing, even if I had the chance to raise the point a few times.
This was too much this time - I pulled the alarm. I first contacted +Abhisek Devkota on why it was phrased this way, to be welcomed with a “You submitted it…” … Uhm, no, but he wasn’t going to argue with me, and told me to see that with Steve, which I did. After some chat, explaining how he could reward nebkat and other contributors, he told me that he was still waiting on me to “list my pricing, features and milestones for Focal” -- which I did, back on July 23rd. I never had any answer, seemingly because the “Focal drama started” and he got frustrated. From there, it seemed like Steve just wanted to stop dealing with it because “this is too much drama”. The exact drama part that bothers him? Well, some contributors weren’t happy about what Cyanogen Inc is. +Andrew Dodd really insisted and wanted to have explanations on WHY Focal would need to be relicensed, and why all this secrecy, without any real answer ever.
And how does Steve deals with these kind of reactions now? Easy answer:
“Oh god please tell me the story. grabs popcorn” https://plus.google.com/u/0/101093310520661581786/posts/1ev1FJpSCE3
Well, here’s your story. And here’s how they treat huge contributors like Andrew, who aren’t big enough and don’t open their mouth with the right people. The most ironical thing? If they want to dual-license, it is to make non-open changes to the apps. So, we’ll need CyanogenMod for the CyanogenMod Phone, because the code shipping on the device won’t match the public code.
Steve’s argument to avoid rewarding people, is that people wants to be “retroactively paid” - but he doesn’t seem to understand that people contributed when CyanogenMod was still a project all about open source, that wasn’t removing features from the ROM, and that had no commercial intentions. Nebkat contributed a lot of stuff in the Launcher, which is a central component of CyanogenMod today. But he did it a few months ago, “before” Cyanogen Inc, so he doesn’t deserve anything. But Cyanogen Inc can sell it to his customers.
Entropy512 wanted to clarify that point for his situation, which is true for many other contributors: “Some people like myself contribute to the project to keep our minds sharp and it's rewarding in and of itself. I make more than enough money in my day job. If someone is planning on creating a closed source fork, which is the only thing that dual licensing enables, it is no longer rewarding.”
Now, don't get me wrong. Cyanogen Inc is a huge milestone for CyanogenMod, and I can only applaud Steve for the initiative and being able to get there. There are not only dark points with the company, far from that. There’s a big bright side: CyanogenMod will become more stable, and will eventually get more features (even if they’re not going to do anything against CTS). Device support might get enhanced, since they’re paid to work on it now (even if issues existing for a LONG time aren’t fixed). And users maybe will get official support.
But the community can feel let down at some point. People from external ROMs would have loved to contribute back to CM at some point. However when Cyanogen’s leaders refers to Paranoid Android or AOKP, they call it “that other ROM”. Steve, always saying “Go ahead and fork”, isn’t actually taking seriously contributions from other developers. And since external contributors know their contributions are going to be ignored, they just don’t submit anything.
I could go on and on with many other things, how the code review is done (or rather, not done), how submissions are just -2’d without explanations, how they criticize XDA users (yes, where ¾ of their user base come from), how they complain people don’t contribute, when they DID but the patch was ignored because the maintainer didn’t want it at that time, how unstable devices are tagged as RC/stable (without asking their maintainers ; Netflix won’t run on a “stable” build of CM for exynos devices), etc. But I’m not here for that.
At this point, on my end the issue is solved, Focal is pulled from CyanogenMod. It wasn't a last minute decision, it wasn't just because I discovered it just now. It's something that has been running for around two months, and the solution was only found yesterday after a long discussion, and because it had to be stopped quickly.
I will keep on improving the app, fixing bugs, and make it better. If it’s not in CyanogenMod, then it will find room in another ROM. The app is GPL, and I will put it up on the Play Store at some point.
I have plans to raise the awareness of the importance of Open Source, and how GPL doesn't prevent any paid work, and that that there are easy ways to keep the community happy with such a situation.
And at the same time, I wish the best to Cyanogen Inc.
Keep in mind: CyanogenMod wouldn’t be what it is today without its contributors. If you’re able to run CyanogenMod on your device today, it might not be only thanks to Steve, Koushik or Ricardo. There are hundreds of people behind them who pushed many patches, and enabled many devices as a hobby. Have you ever heard of them?
Show less
73
Click to expand...
Click to collapse
Should be interesting on how all this will play out....
Can't wait for the phones...
The ironic thing is that if CM really does start putting out phones there is a decent chance that they'll be the only devices guaranteed NOT to be supproted by CM as we currently think of it today. Can you imagine CM posting links to how to root these devices, or pointing to drivers/etc so that you can build your own CM variants for them?
I really do hope that this doesn't turn out to be the case, but one of the downsides to an aftermarket project "going mainstream" is that it often results in a product that isn't really any better than the products it previously sought to replace.
I would love to try Focal sans CM...looking forward to it!
wideasleep1 said:
I would love to try Focal sans CM...looking forward to it!
Click to expand...
Click to collapse
Play store. Focal (Beta). Would post a link, but I'm on my phone. Works just as good as the version previously bundled in cm.
https://play.google.com/store/apps/details?id=fr.xplod.focal
wideasleep1 said:
I would love to try Focal sans CM...looking forward to it!
Click to expand...
Click to collapse
tvall said:
Play store. Focal (Beta). Would post a link, but I'm on my phone. Works just as good as the version previously bundled in cm.
Click to expand...
Click to collapse
simms22 said:
https://play.google.com/store/apps/details?id=fr.xplod.focal
Click to expand...
Click to collapse
LOL! Yep! I didn't hafta wait long..did I?!?!
https://play.google.com/store/apps/details?id=fr.xplod.focal
Team BBQ is EASY to remember!
Wow, I didn't know it was this bad.
Sent from my Nexus 4 using Tapatalk 4
Daaaaaamn!
This is what happens when greed, fame and money take over your life.
https://plus.google.com/106978520009932034644/posts/L8FJkrcahPs
It's the last build of CM I've had on my phone. Going to stock ROM, and using xposed modules.
For years CM being a leader on open source. But soon as they smell money/power, it all goes downhill.
Losing freedom and features, CM will try become a mainstream ROM that carriers can buy. CM will become a Touchwiz.
With no root and extra device features, since Google won't allow it.
4+ years of tireless community work and that's all you have to say? This isn't like some typical scenario that plays perfectly in your head cause it reassures certain prejudices in your life. The leads as well as their work should have earned them some good faith.
I would like to read the story of how his original plan got clouded by money and turned a cool thing into a corporate mess.
r00t4rd3d said:
I would like to read the story of how his original plan got clouded by money and turned a cool thing into a corporate mess.
Click to expand...
Click to collapse
Soon...
Wow, this is really weak. This sounds like Kindergarten to me.
Sent from my Nexus 4 using xda app-developers app
I'm starting to hate CM now
Honestly, it worked out how you would expect. Part of the problem is many of the people contributing are not able to be compensated by the new corporation (underage, etc). However, at the end of the day, they will get good people working for them on paid positions so you will have more consistent work I would presume. I don't think they will change their vision dramatically, so I wouldn't think they are going to completely sell out and destroy the project.
bozzykid said:
I don't think they will change their vision dramatically, so I wouldn't think they are going to completely sell out and destroy the project.
Click to expand...
Click to collapse
Some would argue your first point has already happened and your second point is the end-game and your last point is the worst case scenario that seems more likely now than, say, July.
Folks will need to decide for themselves whether they want to ride the company train into the company town to shop at the company store. Many are already beholden to Google/Facebook/Twiiter that they'll never even notice.
Sent from my Nexus 4 using Tapatalk 2
bozzykid said:
Honestly, it worked out how you would expect. Part of the problem is many of the people contributing are not able to be compensated by the new corporation (underage, etc). However, at the end of the day, they will get good people working for them on paid positions so you will have more consistent work I would presume. I don't think they will change their vision dramatically, so I wouldn't think they are going to completely sell out and destroy the project.
Click to expand...
Click to collapse
Despite my earlier posts, I'm willing to wait and see how things go, but MANY community-driven FOSS projects have gone through this and it rarely turns out well. It is one thing when a company starts out as a company (like MySQL) and just happens to release everything as FOSS along the way. It is another when a project starts out community-driven and tries to turn into a company, for the reason you already stated.
Healthy community projects have a very diverse set of small contributors. This means that if individuals leave or burn out there isn't a huge loss to the community. Healthy companies can really only operate if you have a small number of serious contributors. They can't pay hundreds of people, and if they paid by the patch the work just wouldn't be worth doing for the sake of the money.
Motivations for contributing to non-profits tend to be different from those for contributing to for-profits. People will just give away $200 worth of their time to a FOSS non-profit. People will usually not part with such time to benefit a for-profit unless the contribution is somehow self-serving.
The irony of this is that a successful FOSS organization that gets an infusion of cash can end up spending that money on salaries and get less labor out of the deal...
A corporate CM was bound to happen someday. Shame though. I remember reading Steve's first interviews about cm and his visions and how honorable they were. Hope the team doesn't throw it all out the window for money.
Sent from my Nexus 4 using Tapatalk 4
Moto ran the Transform the Smartphone Challenge on Indiegogo more than a year ago. 50 mods entered, only 2 or 3 ever got anywhere near a product. Moto wierdly chose 2 'winners' from the contest to receive financial and other support which were never heard from again, leaving the keyboard mod that had demonstrated demand and ability to produce on its own, scrounging for support wherever they could. Perhaps moto thought livermorium had proven they didn't need help, but moto should have known better, manufacturing is hard and tiny organizations with no cash reserves could always use support.
With the drop out of edge some months ago, only the keyboard mod remains within spitting distance of shipping. They actually did begin manufacturing and shipping units, but had to start over and recall them thanks to Motorola's issues with oreo OTAs. Now after all the delays, with some caused by moto, perhaps including their recent executive shakeups, Livermorium (the company making the keyboard mod) is struggling. I'm confident they'll pull through because they've got serious will to survive, but they shouldn't be left twisting in the wind alone. Moto needs to step and prove that an indie mod is possible, even as a slate of new mods gets listed on Indiegogo that few are willing to take seriously because of last year. Moto started this, they asked 3rd parties to invest in the ecosystem, they promised support, they made users believe their own pledges mattered and encouraged us to put up out money to help the ecosystem. They have the resources, and they need help livermorium over the finish line.
We have limited means to contact, and this is a long shot, but it's the best I've got. If Moto is worth its salt, they'll have a director of social media capable of elevating a popular request to more important eyes, but to reach even that person, we need to amplify the request. The tweet below doesn't need to be the only means of reaching out, but it has started to get some traction and a few seconds retweeting or liking it may be the best bang for the buck in reaching them. Please reach out to moto anyway you please, whether you are pro-keyboard or not, because if this mod fails, the best run, closest, most in demand of the indies (it raised more funds than all the other Transform challenge mods combined), why would anyone actually put money down on another crowdfunded mod?
I think we all know that the Moto Z line itself is resting on the edge of a bubble. It might last or it might not. All that will depend on the health of its mod ecosystem. Moto mods are the most interesting thing to hit smartphones in ages, I'd hate to see this disappear. Not just this one indie mod, but others that could follow it if it can prove that indie mods can be trusted would contribute greatly to saving the Moto Z line.
TL;DR: Your likes, retweets and replies will help elevate this request and make it more likely that Motorola will see and care about making indie mods credible for users to back and enriching motomods ecosphere at large: https://twitter.com/fortunzfavor/status/986714582659018754 If you prefer to send your own tweet, please post it and I will happily retweet and like to help elevate polite, on point requests.
While lenovo ( moto ) does have some blame in this situation , i think it's fair to also state that livermorium at least "overshot" things a bit here..
Backers have been promised at least a couple of things and the product has gone thru a ton of re-thinks and rebuilds.
Time and time again the backers had to accept that there was another change and another 'update' made to the product...
Livermorium was more then happy to go to CES and make quite a splash about the keyboard , even go as far as hinting to a retail release of the product.
While it is a logical move to take a piss on lenovo , we have to consider that a lot of the issues could have been prevented if the seemingly endless list of changes
and updates was cut out to get the product to the backers at least.
Livermorium is a little bit too eager to 'whine' about the fact that they are out of funds and that a lot of 'new problems' have come up out of nowhere.
I backed the product and i have been very patient but with a long list of shifted deadlines i must be honest and state that i have lost allmost all hope
in this project.
Lets all hope that this idea finally comes to a product very soon , the wait has been too long...
I was unaware of the issues with the mod, but I was looking forward for it as well. I'm a serious typer and I still use the T9 compact because I think it's faster and could think of a couple of situations where the mod would be dope
Sent from my unknown using Tapatalk
I apologize for the title, but this is relevant to Oneplus 10 Pro.
On approx Nov 12th last month, i joined heavily in the discussion regarding Region changing, or using MSM Tool to flash a different fw for our devices. That same day i successfully jumped from the 2419 Tmobile branded fw, to the 2415 Global FW, without a hitch. I then immediately posted success replies to those who were interested. In the 1st full reply regarding my process, i identified several "requirements" in both editing an accompanying file, as well as which version(s) were needed in order to do the jumps. Exactly 3 days later, OPPO took down their official posting that linked to the Rollback packages, and the Beta 1 Android 13 builds to download including the local update apks needed. Seamlessly they linked an identical page with NEW links to download, that had the same names almost. (i have screenshots of the file size differences for proof) ... but almost 70% of you all who attempted my instructions, but downloaded the UPDATED packages, resulted in a bootloop, or unresponsive device!
1st... im sorry for that! When i hard linked the files that i KNEW worked, i never expected oneplus to be sneaky and change the contents, but keep my links headed to these newer packages... I just really did not fathom a company which we all used to support, turning against us in an act of really sinister nature. They had to be aware that once these files were changed out, it would create numerous bootloops and bricks, yet they would not provide us an Unbrick method.
I addressed the altered files swiftly once i verified the changes, and then began urging people to be careful and also realize that there were new things that were done to the FW and i did not have any ideas how they would react, especially on the Tmobile Variants of the 10 Pro and 10 T... but i made THIS FORUM, my ground zero because doing the same method WORKED on the 10 Pro... but after a few modifications, i was stuck in the Unresponsive Brick state ppl were encountering.
(My 10T still worked like a champ though, which confused me as usually OLDER devices have less structural security than newer ones, and the 10 pro was almost a year older!! To Assume something makes an A** of U & ME.)
So with this forum as ground zero, it was where i was focusing probably close to 30-40 hrs a week, trying to troubleshoot and collaborate with other Devs/users about methods to break the MSM TOOL Authentication, so we would all have a WORKING, UNBRICK TOOL, that no one had to send some person a crypto payment to then let them log into your computer! (Stranger Danger!!!!)
It seemed like every time we had SOME MEASURE of success, either by luck, or even finding an alternative tool not meant for this device, that was capable of a successful flash.... we were instantly "knee-capped" by a sniper, and either the new tool no longer functioned properly or it outright broke.... (Secrecy Tool... used to unlock crucial Engineering Mode sections got blucked thru the instructed installation, with no new solution.... which also somehow there are screenshots of an Engineering app, RUNNING ON A ONEPLUS 10 Pro, that had 3 or 4 more options than we do.... hmmm) Anyways just one example of an OPPO intervention.
I have helped with SAMSUNG Root exploits that were SERIOUS flaws, and it took Samsung a few weeks to try patching... BUT I KNOW that BBK, with all the 40 different devices released each year, DOES NOT have a team dedicated to scouring for OUR semi-glitchy NON WORKING theories. (1st clue)
Anyways, here is the main point.... About 2 weeks ago i revealed that i was going ALL IN on finding a way to give us an MSM Flash tool that would bypass all the login stuff and let us do a local UNBRICK FLASH. I gave a few too many clues as to what my Goal Line was looking at. In about 24 hrs i was sent a "Cease and Desist Order" via email, to an address that is not associated to either THIS account on XDA, nor ANY account connected to the Oneplus Community. It was an address linked to a Qualcomm Developer profile i created, and another Android development site. Yet that site doesn't have any info linking to XDA. (2nd clue)
After the 1st order i got... i received a less formal , but just as direct email, from BBK/Oppo requesting that i stop ANY reverse engineering activity that they are now aware of my actions, and failure to comply, or if a release of any tool that had identifying data which could be proven as OPPO programming tools, they would refer my actions to the Department of Justice, cyber crimes division. I TOOK THAT ONE SERIOUSLY, and notified my family attorney! .... I then just within the past 48 hours posted some updates, as well as theories regarding other NON-ASSOCIATED programs that were readily available , and created by the manufacturer Qualcomm.... (because they cannot come at me, for apps that EVERYONE already can dl.... ) WELL UPDATE: Yesterday 12/26 around 9:39pm Central i received another FORMAL "Cease and Desist Order" from Oppo/BBK... but this time it was informing me that they intend to press Qualcomm into filing an official complaint against me, for "Copyright Infringement" , and "Illegally Accessing Unauthorized Applications by Qualcomm, to Reverse Engineer their security" ... <=== my lawyer laughed at this one.... but im not... and now i must tell you that "officially" i cannot release a public tool, if in fact i am able to mitigate their security. Under the "Bug Bounty" Programs offered by both Google, and Qualcomm, I have FULL AUTHORITY to continue researching the same thing i was doing prior to the letters. Oppo cannot TRUMP both Qualcomm, and Google who expressly approve hackers and security testers WITHOUT RESTRICTION, to do whatever we have to, in order to break their respective programs, AS LONG AS I USE THE FAIR REPORTING PRACTICES, AND NOTIFY THEM OF THE BUG/EXPLOIT FOUND... and then Once they acknowledge receipt of the complete process, a 90-day counter begins, and UNTIL THAT EXPIRES, i am not allowed to disclose, ,or discuss any specifics regarding what i have found, in order to give them adequate time to patch/replace the vulnerable process/application.
NOW HERE IS WHY I AM WRITING THIS NOTICE.... I was contacted BY VOICE, by a Qualcomm Technical Support Administrator, who was actually trying to reach out to THE PERSON WHO REPORTED ME TO OPPO.... TMOBILE ..... GOOGLE AND QUALCOMM.!!!!
I played along and when they asked me about what i was trying to report exactly, i asked them to read me back just what i had sent them , because I was "busy over the past few days, and had made several reports, so i needed a refresh of which report it was...."
They read me back THE ENTIRE EMAIL, including the header, which stated the Email address, as well as the Username (???) and then in the first sentence, they said, "Hello.... I'm sorry to contact you this way, but i did not locate any other means of contact to report criminal activity being performed on your applications and devices. My name is <XDA-NAME> ,and im a member at XDA-Developers, who has seen some alarming discussions regarding your newest Smartphone processor, and also the applications you use to interact with them... I cant go into too much detail here, because it would take much more than i feel comfortable typing, but it is urgent that you contact me regarding the XDA USER: "Beatbreakee" . I have acquired his contact email, and phone from online public data channels, and i will include those at the bottom, but you need to act fast and stop this hacker, before he creates a serious security risk in your company!"
Followed by a jumble of Email addresses... only 1 which was mine.... and several phone numbers from WAY BACK... that i havent had in years, but also one current number... which they mistakenly called ME instead of him.
So i first off want this to be noted that i have ZERO intention of revealing who the "Concerned Citizen" was that felt that my usage of the READILY AVAILABLE DOWNLOADS of QPST, and QXDM were of such a nefarious intent! So plz dont ask, because i dont Dox people.... I leave that to politicians and tv journalists....
I just wanted everyone who takes the time to read this, to be AWARE that you really cannot trust ANYONE you dont have a good repertoire with... and be advised that some of the people who ask for help, and also have EXTREMELY SPECIFIC questions pertaining to some thing youre discussing, may have totally malicious intentions as to how they use the info you tell them.
All i can say is that the user REALLY reported me, BECAUSE I WAS BOISTEROUSLY EXCLAIMING THAT I INTEND TO BUILD A FREE, OFFLINE, UNBRICK TOOL, TO STOP THE EXTORTION BY PPL WHO HAVE NO AUTHORITY TO CHARGE US FOR A SOLUTION WHICH SHOULD BE FREE.....
In other words, they snitched me out so i wouldnt hurt their gestapo over fixing our phones..... (Kinda trashy.... dontcha think!)
But thats all the details i can provide ... sorry i wont break America , any more than it already is.... So you get to stay in the shadows PERSON.... But you should know that NOW i have the green light to use any available programs/software within public domain, in order to achieve my intended goal.... because all i have to do is make the report to QualComm because THEY INVENTED AND DO THE CODING FOR THE MSMTOOL.... NOT OPPO! ..... good try! (oh and i told them EXACTLY what i was attempting to do, which is how i learned of their bug bounty... and they not only were not concerned... but they laughed because the versions we have around on the internet, are SEVERAL YEARS behind the current tools, and are neutered enough to not pose a security risk!)
So i will continue to work diligently people... but if i find success, i wont be able to give any disclosure other than confirmation, and then it will take 90 days before i can actually say something legally! This sucks, cuz we need the tool NOW.... and the Oneplus 11 is being released In January in China! (Yikes)
ok thats all.... Happy New Year everyone...... (including the person who wants our devices to stay bricked unless we pay them!)
If they sue you, just defend yourself saying that they are doing illegal activity also by blocking the user device to be repaired by third party.
This in America and Europe is illegal so they can't do anything about it.
I really wanna take a guess and say that the "certain someone" once ran around here proudly proclaiming that MSM can never be hacked and we must always pay.
This is disgusting. Make sure to forward this post to all the tech blogs and get some proof over to some people (redacted obviously). OnePlus/Oppo need to be taken to task for this. The fact that they intentionally changed packages in order to brick people trying to change regions is actually something they can be sued to oblivion for and you have all the proof. A company cannot knowingly cause damage to someone's property like that.
Also, this cements my choice to never have anything to do with OnePlus again.
That really sucks. It's probably that OppoTech123 scammer who claims to be illegally leaking OPPO MSM tools, just to charge you to use it.
g96818 said:
That really sucks. It's probably that OppoTech123 scammer who claims to be illegally leaking OPPO MSM tools, just to charge you to use it.
Click to expand...
Click to collapse
It absolutely is. There's nobody else who would gain from this that has been participating in those threads. I mean... the username is literally OppoTech...
Ph0nysk1nk said:
I really wanna take a guess and say that the "certain someone" once ran around here proudly proclaiming that MSM can never be hacked and we must always pay.
Click to expand...
Click to collapse
unfortunately i cant really confirm or deny anyone... but i will point out this... look into the thread on our 10 Pro forum, where i dropped what ive tried... completed... how i came up with the idea... who helped me in the right direction, and what i was planning as my next steps... Then you will be able to get a list of users who you can each do your own sleuthing.
Again this is not to identify the person directly... but if I was someone who felt deceived or wanted to know who i could eliminate from my conversations and dm's when they REPEATEDLY ask the same or similar questions in other XDA forums for other devices by the same mfg.... I would compile a list of everyone in that thread, then cross off every name that i know has a good rep here, all of the ppl that i have a history with... followed by any names of members who are moderators, or have threads of their own which they provided FREE, instructions/applications for helping remove or mitigate some form of restriction. (root... custom kernel... rom.... bootloader... etc) and then the list of remaining names should be pretty short. Finally take out any SENIOR members, because most ppl who reach that status are OG and not a heartless CASH GRABBER who is only here to spy for his clan of thieves, extorting ppl in need of assistance. Finally take the final few names, and check out all of their posts and replies to see if they follow a pattern , and also if they are only on threads of devices by the same manufacturer.
Any names beyond all those categories, i would NOT do DM's with, or reply directly to any informational requests from those users. ESPECIALLY if they advocate some form of payment to themselves for services that are requested in Crypto. All red flags, and reason for suspicion. But thats just my opinion of how i would decipher and determine exactly who i will stay away from. But actually its worse, because NOW weve been informed that we have ppl here who will sabotage and drop FALSE accusations in formal reports to companies, just so they can keep making $100 a week, by eliminating the people who are working on a "Free For All" solution....
Just sayin'
I mean REALLY... they straight up called me a "Malicious Hacker", who is trying to destroy the security of all their devices! .... How am i trying to destroy ANYTHING? When im actually just trying to give users a reason to still buy OnePlus devices.
Cuz when they release the 11 in a few months... i truly believe their sales are gonna decline almost 10% worldwide! And MAYBE if the company saw that several community members were working on ways to make a tool that FIXES the issue they created... they might rethink their rollout and drop us a repair tool when it drops...
It has been a long time since I have participated in any forum at all, but this, oh my god THIS.. it is on an another level.
First of all, many thanks to you and to all members who are trying very hard to give free of charge support, and fk these trash companies. Your times and efforts are appreciated.
I was deeply involved in the warez long time ago, and I just want to say that cracking/patching the MSM tool is not that hard. In fact, it is a very easy process compared to what I have experienced and witnessed with more complicated protections. It takes one dedicated releasing group to do the job once and for all.
I hope that one group will see this post, take it personally (which they usually do xD) and give OP and its team who is certainly reading the treatment they deserve.
This post proves that they are going for the money, nothing else. Hope people who said the rubbish bla bla bla of protecting devices, security issues, etc will change their bunk mindsets.
Thanks again, and hope you will be safe.
Gamenexus, LTT, UnboxTherapy should receive this info.
They reach a great amount of people and then it will have some repercussion.
And as I said, if they do anything just do it back, the amout you're gonna receive is far bigger.
beatbreakee said:
I apologize for the title, but this is relevant to Oneplus 10 Pro.
On approx Nov 12th last month, i joined heavily in the discussion regarding Region changing, or using MSM Tool to flash a different fw for our devices. That same day i successfully jumped from the 2419 Tmobile branded fw, to the 2415 Global FW, without a hitch. I then immediately posted success replies to those who were interested. In the 1st full reply regarding my process, i identified several "requirements" in both editing an accompanying file, as well as which version(s) were needed in order to do the jumps. Exactly 3 days later, OPPO took down their official posting that linked to the Rollback packages, and the Beta 1 Android 13 builds to download including the local update apks needed. Seamlessly they linked an identical page with NEW links to download, that had the same names almost. (i have screenshots of the file size differences for proof) ... but almost 70% of you all who attempted my instructions, but downloaded the UPDATED packages, resulted in a bootloop, or unresponsive device!
1st... im sorry for that! When i hard linked the files that i KNEW worked, i never expected oneplus to be sneaky and change the contents, but keep my links headed to these newer packages... I just really did not fathom a company which we all used to support, turning against us in an act of really sinister nature. They had to be aware that once these files were changed out, it would create numerous bootloops and bricks, yet they would not provide us an Unbrick method.
I addressed the altered files swiftly once i verified the changes, and then began urging people to be careful and also realize that there were new things that were done to the FW and i did not have any ideas how they would react, especially on the Tmobile Variants of the 10 Pro and 10 T... but i made THIS FORUM, my ground zero because doing the same method WORKED on the 10 Pro... but after a few modifications, i was stuck in the Unresponsive Brick state ppl were encountering.
(My 10T still worked like a champ though, which confused me as usually OLDER devices have less structural security than newer ones, and the 10 pro was almost a year older!! To Assume something makes an A** of U & ME.)
So with this forum as ground zero, it was where i was focusing probably close to 30-40 hrs a week, trying to troubleshoot and collaborate with other Devs/users about methods to break the MSM TOOL Authentication, so we would all have a WORKING, UNBRICK TOOL, that no one had to send some person a crypto payment to then let them log into your computer! (Stranger Danger!!!!)
It seemed like every time we had SOME MEASURE of success, either by luck, or even finding an alternative tool not meant for this device, that was capable of a successful flash.... we were instantly "knee-capped" by a sniper, and either the new tool no longer functioned properly or it outright broke.... (Secrecy Tool... used to unlock crucial Engineering Mode sections got blucked thru the instructed installation, with no new solution.... which also somehow there are screenshots of an Engineering app, RUNNING ON A ONEPLUS 10 Pro, that had 3 or 4 more options than we do.... hmmm) Anyways just one example of an OPPO intervention.
I have helped with SAMSUNG Root exploits that were SERIOUS flaws, and it took Samsung a few weeks to try patching... BUT I KNOW that BBK, with all the 40 different devices released each year, DOES NOT have a team dedicated to scouring for OUR semi-glitchy NON WORKING theories. (1st clue)
Anyways, here is the main point.... About 2 weeks ago i revealed that i was going ALL IN on finding a way to give us an MSM Flash tool that would bypass all the login stuff and let us do a local UNBRICK FLASH. I gave a few too many clues as to what my Goal Line was looking at. In about 24 hrs i was sent a "Cease and Desist Order" via email, to an address that is not associated to either THIS account on XDA, nor ANY account connected to the Oneplus Community. It was an address linked to a Qualcomm Developer profile i created, and another Android development site. Yet that site doesn't have any info linking to XDA. (2nd clue)
After the 1st order i got... i received a less formal , but just as direct email, from BBK/Oppo requesting that i stop ANY reverse engineering activity that they are now aware of my actions, and failure to comply, or if a release of any tool that had identifying data which could be proven as OPPO programming tools, they would refer my actions to the Department of Justice, cyber crimes division. I TOOK THAT ONE SERIOUSLY, and notified my family attorney! .... I then just within the past 48 hours posted some updates, as well as theories regarding other NON-ASSOCIATED programs that were readily available , and created by the manufacturer Qualcomm.... (because they cannot come at me, for apps that EVERYONE already can dl.... ) WELL UPDATE: Yesterday 12/26 around 9:39pm Central i received another FORMAL "Cease and Desist Order" from Oppo/BBK... but this time it was informing me that they intend to press Qualcomm into filing an official complaint against me, for "Copyright Infringement" , and "Illegally Accessing Unauthorized Applications by Qualcomm, to Reverse Engineer their security" ... <=== my lawyer laughed at this one.... but im not... and now i must tell you that "officially" i cannot release a public tool, if in fact i am able to mitigate their security. Under the "Bug Bounty" Programs offered by both Google, and Qualcomm, I have FULL AUTHORITY to continue researching the same thing i was doing prior to the letters. Oppo cannot TRUMP both Qualcomm, and Google who expressly approve hackers and security testers WITHOUT RESTRICTION, to do whatever we have to, in order to break their respective programs, AS LONG AS I USE THE FAIR REPORTING PRACTICES, AND NOTIFY THEM OF THE BUG/EXPLOIT FOUND... and then Once they acknowledge receipt of the complete process, a 90-day counter begins, and UNTIL THAT EXPIRES, i am not allowed to disclose, ,or discuss any specifics regarding what i have found, in order to give them adequate time to patch/replace the vulnerable process/application.
NOW HERE IS WHY I AM WRITING THIS NOTICE.... I was contacted BY VOICE, by a Qualcomm Technical Support Administrator, who was actually trying to reach out to THE PERSON WHO REPORTED ME TO OPPO.... TMOBILE ..... GOOGLE AND QUALCOMM.!!!!
I played along and when they asked me about what i was trying to report exactly, i asked them to read me back just what i had sent them , because I was "busy over the past few days, and had made several reports, so i needed a refresh of which report it was...."
They read me back THE ENTIRE EMAIL, including the header, which stated the Email address, as well as the Username (???) and then in the first sentence, they said, "Hello.... I'm sorry to contact you this way, but i did not locate any other means of contact to report criminal activity being performed on your applications and devices. My name is <XDA-NAME> ,and im a member at XDA-Developers, who has seen some alarming discussions regarding your newest Smartphone processor, and also the applications you use to interact with them... I cant go into too much detail here, because it would take much more than i feel comfortable typing, but it is urgent that you contact me regarding the XDA USER: "Beatbreakee" . I have acquired his contact email, and phone from online public data channels, and i will include those at the bottom, but you need to act fast and stop this hacker, before he creates a serious security risk in your company!"
Followed by a jumble of Email addresses... only 1 which was mine.... and several phone numbers from WAY BACK... that i havent had in years, but also one current number... which they mistakenly called ME instead of him.
So i first off want this to be noted that i have ZERO intention of revealing who the "Concerned Citizen" was that felt that my usage of the READILY AVAILABLE DOWNLOADS of QPST, and QXDM were of such a nefarious intent! So plz dont ask, because i dont Dox people.... I leave that to politicians and tv journalists....
I just wanted everyone who takes the time to read this, to be AWARE that you really cannot trust ANYONE you dont have a good repertoire with... and be advised that some of the people who ask for help, and also have EXTREMELY SPECIFIC questions pertaining to some thing youre discussing, may have totally malicious intentions as to how they use the info you tell them.
All i can say is that the user REALLY reported me, BECAUSE I WAS BOISTEROUSLY EXCLAIMING THAT I INTEND TO BUILD A FREE, OFFLINE, UNBRICK TOOL, TO STOP THE EXTORTION BY PPL WHO HAVE NO AUTHORITY TO CHARGE US FOR A SOLUTION WHICH SHOULD BE FREE.....
In other words, they snitched me out so i wouldnt hurt their gestapo over fixing our phones..... (Kinda trashy.... dontcha think!)
But thats all the details i can provide ... sorry i wont break America , any more than it already is.... So you get to stay in the shadows PERSON.... But you should know that NOW i have the green light to use any available programs/software within public domain, in order to achieve my intended goal.... because all i have to do is make the report to QualComm because THEY INVENTED AND DO THE CODING FOR THE MSMTOOL.... NOT OPPO! ..... good try! (oh and i told them EXACTLY what i was attempting to do, which is how i learned of their bug bounty... and they not only were not concerned... but they laughed because the versions we have around on the internet, are SEVERAL YEARS behind the current tools, and are neutered enough to not pose a security risk!)
So i will continue to work diligently people... but if i find success, i wont be able to give any disclosure other than confirmation, and then it will take 90 days before i can actually say something legally! This sucks, cuz we need the tool NOW.... and the Oneplus 11 is being released In January in China! (Yikes)
ok thats all.... Happy New Year everyone...... (including the person who wants our devices to stay bricked unless we pay them!)
Click to expand...
Click to collapse
So I'm a Qualcomm developer with licensing and I would like to talk to you for one I have information in code that you probably can use for your benefit I am personally not able to do this as I don't have a running computer at the moment I get a hold of me in private message and I can add you on discord we can talk and under no circumstances is a vendor have rights to software that is not made by them nor by their use of it or even the restriction of it is against Qualcomm licensing like I'm his bypass tools for the login information flash tools such as the MSM tool but then they solves have stopped using it back in 2016 and 2017 they're using a different type of tool now which I will not say publicly but if you want more information get a hold of me (then it was designed to be free and it should remain free that is the whole point of Open source development.
One more thing I did back up the any version of the file they switched cuz I'm noticing what you're talking about so when I go to my about phone section where it says color OS is completely different fun and completely changed plus the weight scaling font is no longer called the one font but oppo so if you need me to link the Google drive file so you can have access to the one that works cuz I used your method I have a hard copy for the na 2417 version
That is just messed up ...Its funny i went on XDA today and had a PM asking if it was me who reported you...I thought to myself who would report anybody for trying to figure out a way to help everyone who has or have a Xucked up Oneplus
phone . I have killed my phone many times to help figure this out. I have actually paid for someone to flash my phone and try to log all the info. Illegal maybe ..but would be worth it ...to get a MSM working tool to fix our phones.
Oh by the way I hope you Figure this MSM tool out ...I would help if I could code and stuff like what you do. Thumbs UP to you
Canuck Knarf said:
That is just messed up ...Its funny i went on XDA today and had a PM asking if it was me who reported you...I thought to myself who would report anybody for trying to figure out a way to help everyone who has or have a Xucked up Oneplus
phone . I have killed my phone many times to help figure this out. I have actually paid for someone to flash my phone and try to log all the info. Illegal maybe ..but would be worth it ...to get a MSM working tool to fix our phones.
Oh by the way I hope you Figure this MSM tool out ...I would help if I could code and stuff like what you do. Thumbs UP to you
Click to expand...
Click to collapse
If you're running a computer I didn't know how to code I just don't have her any computer if I'd come has software to bypass things locking up their phones so they can be flashed anyways.
Courage! I hope it doesn't come to a suit
O
beatbreakee said:
unfortunately i cant really confirm or deny anyone... but i will point out this... look into the thread on our 10 Pro forum, where i dropped what ive tried... completed... how i came up with the idea... who helped me in the right direction, and what i was planning as my next steps... Then you will be able to get a list of users who you can each do your own sleuthing.
Again this is not to identify the person directly... but if I was someone who felt deceived or wanted to know who i could eliminate from my conversations and dm's when they REPEATEDLY ask the same or similar questions in other XDA forums for other devices by the same mfg.... I would compile a list of everyone in that thread, then cross off every name that i know has a good rep here, all of the ppl that i have a history with... followed by any names of members who are moderators, or have threads of their own which they provided FREE, instructions/applications for helping remove or mitigate some form of restriction. (root... custom kernel... rom.... bootloader... etc) and then the list of remaining names should be pretty short. Finally take out any SENIOR members, because most ppl who reach that status are OG and not a heartless CASH GRABBER who is only here to spy for his clan of thieves, extorting ppl in need of assistance. Finally take the final few names, and check out all of their posts and replies to see if they follow a pattern , and also if they are only on threads of devices by the same manufacturer.
Any names beyond all those categories, i would NOT do DM's with, or reply directly to any informational requests from those users. ESPECIALLY if they advocate some form of payment to themselves for services that are requested in Crypto. All red flags, and reason for suspicion. But thats just my opinion of how i would decipher and determine exactly who i will stay away from. But actually its worse, because NOW weve been informed that we have ppl here who will sabotage and drop FALSE accusations in formal reports to companies, just so they can keep making $100 a week, by eliminating the people who are working on a "Free For All" solution....
Just sayin'
Click to expand...
Click to collapse
Oh believe me. Even without having to take a refresher, instantly two "accounts" stuck out to me because both of their ****ty attitudes, demandment of payment, and an unfortunate DM with one of them privately expressing MSM cannot be cracked and I must pay him and his friend
I have a hard time thinking of anyone else
Ph0nysk1nk said:
Oh believe me. Even without having to take a refresher, instantly two "accounts" stuck out to me because both of their ****ty attitudes, demandment of payment, and an unfortunate DM with one of them privately expressing MSM cannot be cracked and I must pay him and his friend
I have a hard time thinking of anyone else
Click to expand...
Click to collapse
C'mon man, my $100 a week livelihood is at stake here!!! Bwahahahahahahahaha, these kinds of people are too sad to even deal with. Keeping such things private that have long since been public, it's so sad it's despicable.
This is freaking unbelievable
I wish you all the very best on figuring out the msmtool and disrupt that [email protected]# 100$ a week income source
AkayamiShurui said:
One more thing I did back up the any version of the file they switched cuz I'm noticing what you're talking about so when I go to my about phone section where it says color OS is completely different fun and completely changed plus the weight scaling font is no longer called the one font but oppo so if you need me to link the Google drive file so you can have access to the one that works cuz I used your method I have a hard copy for the na 2417 version
Click to expand...
Click to collapse
thanks man... luckily i downloaded all the FW that were on the original post too... i only wish i had been a luckier person and bought my 10T prior to June. Cuz the 1st groups here that were working on rooting the 10Pro, and 10T , spooked Oppo into removing Fastboot directly from the rom. I would love access to the newer tools that QC uses. And im not doing anything that they would consider illegal , since i was directly told that "Any app that is leaked, or released is well documented prior to it hitting any public servers, because they supposedly keep a tight leash on active programming applications, and the only ones that make it to a state that can be 'hard copied' is apps that are decommissioned as out of date and unsupported. So if any app is found and functional, it can be freely used without any fear of legal action." They actually encouraged the use of "Found" Qualcomm apps, because it might reveal another security flaw that they need knowledge of so they can patch it in future versions.
But i appreciate the offer. Its just nice having someone else who can personally confirm what i stated about them changing the files. Companies like OPPO/BBK dont have the resources to dedicate a division to combing the whole internet looking for clues as to what HAS and HASNT been successful in bypassing their security. They rely on ppl like the one who tried snitching me out, and the actual chip mfg reports to change anything related. But the qualcomm guy i talked to seemed rather surprised when i mentioned "Charging a fee to people who brick their phones, to use the MSM Tool and recover it!" .... lol i dropped that bit of info on purpose, cuz if ANYTHING is illegal, it is THEM charging money for something Qualcomm intended to be used by repair techs for free!
beatbreakee said:
thanks man... luckily i downloaded all the FW that were on the original post too... i only wish i had been a luckier person and bought my 10T prior to June. Cuz the 1st groups here that were working on rooting the 10Pro, and 10T , spooked Oppo into removing Fastboot directly from the rom. I would love access to the newer tools that QC uses. And im not doing anything that they would consider illegal , since i was directly told that "Any app that is leaked, or released is well documented prior to it hitting any public servers, because they supposedly keep a tight leash on active programming applications, and the only ones that make it to a state that can be 'hard copied' is apps that are decommissioned as out of date and unsupported. So if any app is found and functional, it can be freely used without any fear of legal action." They actually encouraged the use of "Found" Qualcomm apps, because it might reveal another security flaw that they need knowledge of so they can patch it in future versions.
But i appreciate the offer. Its just nice having someone else who can personally confirm what i stated about them changing the files. Companies like OPPO/BBK dont have the resources to dedicate a division to combing the whole internet looking for clues as to what HAS and HASNT been successful in bypassing their security. They rely on ppl like the one who tried snitching me out, and the actual chip mfg reports to change anything related. But the qualcomm guy i talked to seemed rather surprised when i mentioned "Charging a fee to people who brick their phones, to use the MSM Tool and recover it!" .... lol i dropped that bit of info on purpose, cuz if ANYTHING is illegal, it is THEM charging money for something Qualcomm intended to be used by repair techs for free!
Click to expand...
Click to collapse
Like I said I'm a licensed user from so I have to stay on the guidelines of license so you'll be fine, but they have a bypass tool and other really nice tools like if you flash the wrong ram they got a tool for fixing the ram. Anyway I'll send you my discord