Related
As Swype is only available as a closed beta or as release within an OEM build, it should not be posted, or linked on XDA.
I'm the beta community relations rep for Swype (Brian Resnik, if you're over on the Swype forums).
First of all, yes we're watching you HAHA. I'm obligated to wag my finger at you all for distributing our software without a license. A little patience will go a long way. Trust me, the more the brass hears about people illegally copying Swype and feeling entitled to a free version (yes, we know there's no copy on the market for you to buy, but you have to respect that OEM distribution is our chosen business model), the less they want to support a beta program at all. The better we play nice with eachother, the sooner more people get into the beta!
Click to expand...
Click to collapse
Ya might want to look in the Nexus One application forum...
Carloswithac said:
Ya might want to look in the Nexus One application forum...
Click to expand...
Click to collapse
yup, it was posted there first
@mssmison
But you know... I will buy Swype first day it will be released - thanks to these leaks
Swype has updated their page with the new beta instructions. It appears at this point to be a limited public beta, as it will only be available for a couple of days, and requires you to enter your email address to get the download.
So threads with download links will still not be allowed.
Get the info here; http://beta.swype.com/
mssmison said:
Swype has updated their page with the new beta instructions. It appears at this point to be a limited public beta, as it will only be available for a couple of days, and requires you to enter your email address to get the download.
So threads with download links will still not be allowed.
Get the info here; http://beta.swype.com/
Click to expand...
Click to collapse
It's really hard to find, that you have edited your post after several hours from adding it
Swype
just go to swype's page and get it. It is working fine on my G1 with SuperCSDI rom.
h t t p://beta.swype.com
I don't see why they have to hate =[
Need the .apk.
Dont want to register my email. Get enuff junk already. Where can we download the .apk? Post it please.
is XDA commercial now?
I gave swype my email and got the .apk from them.
Izord said:
Dont want to register my email. Get enuff junk already. Where can we download the .apk? Post it please.
Click to expand...
Click to collapse
You do realize that the whole point of this thread is to say not to post the APK, right?
When they take off the stupid download limit for the Beta for registered testers, I'll actually support not posting links.
FirstNoobToBrickHisPhone said:
When they take off the stupid download limit for the Beta for registered testers, I'll actually support not posting links.
Click to expand...
Click to collapse
What do you mean? You can't download it several times?
Brut.all said:
What do you mean? You can't download it several times?
Click to expand...
Click to collapse
I've downloaded mine many times (4 or 5) due to flashing the phone over and over testing things
Nieylana said:
I've downloaded mine many times (4 or 5) due to flashing the phone over and over testing things
Click to expand...
Click to collapse
Yeah, I understand. I just wanted to know whether I should not download it too many times, but backup&install it instead.
Gents,
I think Ive abused my swype membership --- ive installed it maybe at least 30 times on two phones since March. I've lost the "swype" function and it is basically a nice blue HTC_IME standin. No complaints, but wheres the swype at on Swype?
Droid X comes with it stock. Beautiful app. I might have known someone (a friend of course) who hooked his friends up with Swype on their HTC Eris's. He told me that he went and Googled it and found it pretty quick.
Swype.apk
mssmison said:
As Swype is only available as a closed beta or as release within an OEM build, it should not be posted, or linked on XDA.
Click to expand...
Click to collapse
I understand that you have chosen a particular business model. I think however that it is unfair that it is not sold via the Android Market. What about phones like the Nexus One which now is an official developers phone? The Nexus One did not come with Swype and I would like to have the option to use it. (And yes, I did sign up at swypeinc's website waiting for the beta to reopen) Unless you give people the chance to purchase your product people will find ways around your chosen business model. I haven't myself downloaded the apk and I agree xdadevelopers should heed your warning.
I'm not really sure what the hang up is for the swype "brass." This program is being released on select phones already, right? Plus I've never heard complaints about it and would love to try it too. I'd gladly pay for something like this (after a trial) so I'm not really sure what the deal is.
Most of us love new software to play with and improve our phones with. However, a big turn-off for us can also be controlling companies like this. If they don't start providing us a valid route to buy or at least use this product, then they're going to lose in the end. The community is large enough we can throw together our own program to do this crap. Hell, shapewriter keyboard already does this and is free to boot and since I can't even use swype, it might as well not exist in the realm of gesture-based keyboards as far as I'm personally concerned.
I must concur with the rest of the community when I say that choosing not to retail a highly requested, fully functional app shows that the Swype folks are off their rockers. However, if they don't want us to obtain their app and lose customers as a result, that is their prerogative. I'm sure most of us will just find the APKs elsewhere online.
CyboLabs is Proud to present
Open Bump!
What is Open Bump?
Open Bump is a recreation of the closed source Bump project run by Codefire.
It will allow you to "sign" your boot images in the same way that Codefire does it, only you don't need an internet connection.
Click to expand...
Click to collapse
What Open Bump is NOT
lets get the obvious out the way. It won't axe murder you.
It is not a direct reverse engineer of Codefire's implementation. I found the key and iv on my own
The magic bytes were taken from Codefire's method however. If anyone has insight has to how they were found, please shout up.
It does NOT take your private data so you can use it. Tin hatters feel free to double check
Click to expand...
Click to collapse
How did I find this out
I had a general idea of what to look for, having heard that the exploit is related uicc, and is signed with a cipher.
Dropping the aboot image in to Ghex led me to finding a reference to "uiccsecurity". Using the bytes around this, I found a repeat of 32 bytes, which was followed by 16 bytes which formed something that resembled "SecureWallpaper".
As you can probably guess, this was mainly trail and error backed by common sense and logical thinking.
you can programmatically find these values with the python script:
Python:
aboot_name = './aboot.img'
aboot = open(aboot_name, 'rb').read()
key_end = aboot.index('uicc')
key_start = key_end - 32
key = aboot[key_start:key_end]
sec_key_start = aboot.index(key, key_end)
iv_start = sec_key_start + 32
iv_end = iv_start + 16
iv = aboot[iv_start:iv_end]
deciphering some already generated "signatures" proved that these were the key and iv used for "signing" the images.
Click to expand...
Click to collapse
What is coming next?
Inspecting the signatures that were originally uploaded and the ones that people can generate now, I found only one pattern.
The only similarities were the first 16 bytes of each "signature". I believe that only the magic number is needed, and none of the garbage that follows. This has been confirmed by the LG G3 dev from CyanogenMod, Invisiblek Done
Click to expand...
Click to collapse
How to use it?
I don't know how well this will run on anything other than linux, so for now.. I won't talk about it.
First, ensure you are using python2
then run the script
Code:
python2 open_bump.py "/path/to/boot.img"
flash the output, and enjoy
Click to expand...
Click to collapse
Thanks to:
Obviously, this wouldn't have been possible without Codefire since I wouldn't have known where to look, or that it was exploitable. And it was them that found the magic key.
Big thank you to @pulser_g2, who offered invaluable input on cryptography
Big thank you to @invisiblek, who I mercilessly kanged the main part of the image padding script from
note:
The original part of finding this information out was done on my own with guidance from pulser. The final results of this are posted above.
XDA:DevDB Information
Open_Bump, Tool/Utility for the LG G2
Contributors
cybojenix
Source Code: https://github.com/CyboLabs/Open_Bump
Version Information
Status: Beta
Created 2014-11-23
Last Updated 2014-11-23
Thanks, thats great news to have an open source tool here!
Do you see any chance that this could be integrated into CWM/TWRP so that the recovery rom could bump the boot/recovery images before flashing?
Because the boot/recovery.img has to be extracted from the ROM-zip before flashing, bumping it here would make sure that the phone can boot the image even with the newer bootloader.
This would be great for rom-devs since they don't have to change anything and it would even bump roms that are not maintained anymore.
g4rb4g3 said:
Thanks, thats great news to have an open source tool here!
Do you see any chance that this could be integrated into CWM/TWRP so that the recovery rom could bump the boot/recovery images before flashing?
Because the boot/recovery.img has to be extracted from the ROM-zip before flashing, bumping it here would make sure that the phone can boot the image even with the newer bootloader.
This would be great for rom-devs since they don't have to change anything and it would even bump roms that are not maintained anymore.
Click to expand...
Click to collapse
simple answer, this can be added to the build step really easily. See this commit
edit:
of course it may be useful to make a c program to do this.... I shall think on it.
Propably stupid question but i ll give a shot. Since we have the magic key we cant just skip the bump stuff totally? As i can understand, i dont wait official developer team join the bump train, thats why the damn development of the device is really back while the hardware is more than capable.
**To the OP i wish i could give you a thousand likes sir!
After getting the bootloader may be open G3؟؟
Why not use the original Bump?
Quote:
Codefire has been extremely vague about their method, obviously to prevent someone else replicating their results.
They are also storing people's data unnecessarily, and even adding some information relating to the user in to the "signature", possibly for tracking purposes.
As a result of it being an external service, many reputable teams (which won't be named unless they want to be) have said they will not use it, and would rather wait till LG releases the official unlock method.
Finally, Codefire have said the sha1sum of the boot image is required. Whether they knew or not, it is NOT required, and I will be changing this tool to compensate for that.
Click to expand...
Click to collapse
Happy you found a new exploit for us builders and devs, just feel like you kinda disrespected codefire team by accusing them of things before actually talking to them, seems a bit counter productive, this may piss them off and next device you can kiss new exploits by them good-bye,
just my 2 cents on the matter,
i'd remove the line...
in any case thank you very much, i will add it to my build script
---------- Post added at 08:34 PM ---------- Previous post was at 08:29 PM ----------
nikosblade said:
Propably stupid question but i ll give a shot. Since we have the magic key we cant just skip the bump stuff totally? As i can understand, i dont wait official developer team join the bump train, thats why the damn development of the device is really back while the hardware is more than capable.
**To the OP i wish i could give you a thousand likes sir!
Click to expand...
Click to collapse
"Bump stuff" has nothing to do with users, the devs and builders do the "bumping", and development of the G series has nothing to do with bumping, it just takes time to bring everything up
Good job cybojenix. (moderator edit: watch your language please)
Way to ruin a good thing.
I'm done with Android now. You can do it all now - since you obviously know better than me and everyone else.
I don't appreciate people trying to blackmail me - EnderBlue and Cybo both.
Don't believe me? http://hastebin.com/gulumezawi.txt
Good job guys. Way to ruin unlocks for all future LG phones.
If I *EVER* decide to come back, I will not be releasing anything as free or open source. You've sullied my impression of the open source community. Anything I do will be private releases from now on.
LG hadn't patched Bump, and they were going to leave it alone for us as long as we kept it as a service.
Well, looks like that's over and done with.
Bump included a hash of the image that you uploaded and a hash of your developer ID, and some random junk bytes. That's all. It's exactly what we said it was doing.
Well, hey, now you're free to take over and write roots and unlocks for all LG phones since you obviously have the talent to do so.
Let's be honest though, without my team's hard work that you stole, you wouldn't have been able to do any of this.
But you knew that, you're just a bottom feeder.
I don't get angry often at all- but congrats! You've succeeded in making me mad! Achievement unlocked!
I'm done. Your turn.
EDIT: Also, you know you can't open source your project either considering it contains 'stolen' LG crypto keys. https://github.com/CyboLabs/Open_Bump/issues/1
Have fun with that one.
thecubed said:
Good job cybojenix. (moderator edit: watch your language please)
Way to ruin a good thing.
I'm done with Android now. You can do it all now - since you obviously know better than me and everyone else.
I don't appreciate people trying to blackmail me - EnderBlue and Cybo both.
Don't believe me? http://hastebin.com/gulumezawi.txt
Good job guys. Way to ruin unlocks for all future LG phones.
If I *EVER* decide to come back, I will not be releasing anything as free or open source. You've sullied my impression of the open source community. Anything I do will be private releases from now on.
LG hadn't patched Bump, and they were going to leave it alone for us as long as we kept it as a service.
Well, looks like that's over and done with.
Bump included a hash of the image that you uploaded and a hash of your developer ID, and some random junk bytes. That's all. It's exactly what we said it was doing.
Well, hey, now you're free to take over and write roots and unlocks for all LG phones since you obviously have the talent to do so.
Let's be honest though, without my team's hard work that you stole, you wouldn't have been able to do any of this.
But you knew that, you're just a bottom feeder.
I don't get angry often at all- but congrats! You've succeeded in making me mad! Achievement unlocked!
I'm done. Your turn.
EDIT: Also, you know you can't open source your project either considering it contains 'stolen' LG crypto keys. https://github.com/CyboLabs/Open_Bump/issues/1
Have fun with that one.
Click to expand...
Click to collapse
First off, I didn't black mail. I gave your team notice about open sourcing it after reverse engineering the LG bootloader, not your "signatures".
It's your choice if you want to leave Android. Pinning the blame on me is somewhat childish though.
LG not patching Bump? That's a ludicrous statement, and even if it's true, it's good that this script got released. That way they know it should be patched, since having it a service clearly makes all the difference to them.
The hardest part of your teams work was getting the keys. If you know where to look, then it's easy enough to get engineering builds which I suspect contain the master magic bytes which you released.
I'm honestly shocked at your reaction though. I gave your team all the credit and stated which parts I did myself. The part about the service, and the deception was justified.
You tried to obscure something which by logic can't be obscured. That's how so many people realised they can just append the bytes to the image.
So which one would you rather have, LG not patching the exploit (as you so claim), and having an unknown number of people in china running around flashing custom boot images, or have everyone know how to do it to force LG to recheck their security measures.
What I did may not have been fantastic for the community, but what you did was insanely dangerous for the 90% of LG users.
All you did was make it so LG locks down the bootloader. And really 90% of users??? There probably isn't even 3 percent of the LG base on this website. All you did was screw everybody else over so you could have YOUR OFFICIAL CM.
As well people saying you didn't do enough and are still using there signing key as well as attacking it as well.
Way to think about yourself. You didn't care about the 90% or you wouldn't have done this.
I personally hope LG locks down the bootloader now. Go the way Samsung did and put an efuse on it and prevent downgrading. Hopefully all this happens with lollipop so you can screw over the rest of the LG crowd.
cybojenix said:
it's good that this script got released. That way they know it should be patched, since having it a service clearly makes all the difference to them.
Click to expand...
Click to collapse
"Hey let's potentially close all future LG unlocks and thus the chance to use CyanogenMod on future LG devices then. Just so I can get the current CM builds to say 'Official' and get a big pat on the back from the CM dudes who probably don't care about me too much."
Is that what went through your mind? That instant gratification and ignorance really shows who you are because that's exactly what I see from this OP of yours. Enjoy your 15 minutes of fame. You probably just killed a chance for years of it.
savoca said:
"Hey let's potentially close all future LG unlocks and thus the chance to use CyanogenMod on future LG devices then. Just so I can get the current CM builds to say 'Official' and get a big pat on the back from the CM dudes who probably don't care about me too much."
Is that what went through your mind? That instant gratification and ignorance really shows who you are because that's exactly what I see from this OP of yours. Enjoy your 15 minutes of fame. You probably just killed a chance for years of it.
Click to expand...
Click to collapse
Yes, because I've been such a massive supporter of cm. (sarcasm in case you didn't realise).
I started reverse engineering the bootloader for research purposes. If it was more complex than what I have said above, then I probably wouldn't have done this thread.
If it weren't for the fact that the magic stays the same across all signatures, then I also wouldn't have done this thread.
The response I got from them when I contacted them before releasing this was pretty much one of lack of care. So I went ahead and posted it.
I couldn't care less about fame. In fact there isn't really a lot I do care about, but I won't have the community alienated in to thinking the codefire service was such a great thing.
And once again, I refuse to take the blame for their team leaving Android.
whoppe862005 said:
All you did was make it so LG locks down the bootloader. And really 90% of users??? There probably isn't even 3 percent of the LG base on this website. All you did was screw everybody else over so you could have YOUR OFFICIAL CM.
As well people saying you didn't do enough and are still using there signing key as well as attacking it as well.
Way to think about yourself. You didn't care about the 90% or you wouldn't have done this.
I personally hope LG locks down the bootloader now. Go the way Samsung did and put an efuse on it and prevent downgrading. Hopefully all this happens with lollipop so you can screw over the rest of the LG crowd.
Click to expand...
Click to collapse
See my other post, I don't care about cm.
Fair enough, 3% are here, so this benefits the security of 97% of lg uses, if the claim that lg was alright with it running s a service is true.
Either way, I did nothing wrong
cybojenix said:
I couldn't care less about fame. In fact there isn't really a lot I do care about, but I won't have the community alienated in to thinking the codefire service was such a great thing.
Click to expand...
Click to collapse
So you only care about ruining good things, and other people's work?
Lol sorry I think I'm done with you. By cybo
savoca said:
So you only care about ruining good things, and other people's work?
Lol sorry I think I'm done with you. By cybo
Click to expand...
Click to collapse
Tbh I thought it would have been clear by now what I care about. Then again I may have been wrong about considering you one of the smart android people.
I care about learning and sharing knowledge. Which is precisely what this thread did.
cybojenix said:
See my other post, I don't care about cm.
Fair enough, 3% are here, so this benefits the security of 97% of lg uses, if the claim that lg was alright with it running s a service is true.
Either way, I did nothing wrong
Click to expand...
Click to collapse
I saw your PM to autoprime in IRC, it was "I am going to post what I found or you do, either way its going there", it wasn't lack of care, it was that you just stated a fact and left, it was a very rude unthoughtful thing to do, also don't try to BS everyone with your research, you and about 100 other people found the "magic keys", the problem is those "magic keys" were placed there by team codefire, you didn't find them, you found that they were using the key and copied their work, anything else you say is a lie, at least the other 99 people who found this had the basic respect to not post it unless the original team allowed it.
There was no reason to post this, their site was working fine, and if you used the API there was no problem of tracking since it just uses a UID to identify to the server.
at least admit you were wrong and say you are sorry, they won't fix anything but will gain you a minimum amount of respect
sooti said:
I saw your PM to autoprime in IRC, it was "I am going to post what I found or you do, either way its going there", it wasn't lack of care, it was that you just stated a fact and left, it was a very rude unthoughtful thing to do, also don't try to BS everyone with your research, you and about 100 other people found the "magic keys", the problem is those "magic keys" were placed there by team codefire, you didn't find them, you found that they were using the key and copied their work, anything else you say is a lie, at least the other 99 people who found this had the basic respect to not post it unless the original team allowed it.
There was no reason to post this, their site was working fine, and if you used the API there was no problem of tracking since it just uses a UID to identify to the server.
at least admit you were wrong and say you are sorry, they won't fix anything but will gain you a minimum amount of respect
Click to expand...
Click to collapse
Wrong, I stated that I was going to open source it, meaning the work of put in to getting the key and how it's used to get the original magic.
It was after that that I realised the final magic is the only thing needed. I actually worked out how to get the magic key a few hours ago, but since I don't have the right images, it won't be globally usable.
Fair enough, I apologise for pointing out the flaws in codefires service, and that they took it badly.
cybojenix said:
See my other post, I don't care about cm.
Fair enough, 3% are here, so this benefits the security of 97% of lg uses, if the claim that lg was alright with it running s a service is true.
Either way, I did nothing wrong
Click to expand...
Click to collapse
OK. If you did nothing wrong please do explain this
Enderblue-"well, would you be willing to open source it so we can have a official cm support?"
IoMonster-"so it would make storm already worse then what it is now? *paraphrasing for language
IoMonster-"no"
Seems like be said he didn't want it open source but you still went ahead any way.
http://hastebin.com/gulumezawi.txt
And then you saying your going to push it for vs985 even after he said no.
I don't know who Enderblue is, and I'm not affiliated with him..
whoppe862005 said:
OK. If you did nothing wrong please do explain this
Enderblue-"well, would you be willing to open source it so we can have a official cm support?"
IoMonster-"so it would make storm already worse then what it is now? *paraphrasing for language
IoMonster-"no"
Seems like be said he didn't want it open source but you still went ahead any way.
http://hastebin.com/gulumezawi.txt
And then you saying your going to push it for vs985 even after he said no.
Click to expand...
Click to collapse
cybojenix said:
I don't know who Enderblue is, and I'm not affiliated with him..
Click to expand...
Click to collapse
It isn't like it matters if you are or not. It says right in the chat he doesn't want it open sourced. I'm sure about 99% of the people on here have seen that already and I'm pretty sure you have seen it as well.
It states right in the chat he didn't want it open sourced.
whoppe862005 said:
It isn't like it matters if you are or not. It says right in the chat he doesn't want it open sourced. I'm sure about 99% of the people on here have seen that already and I'm pretty sure you have seen it as well.
It states right in the chat he didn't want it open sourced.
Click to expand...
Click to collapse
but the chat wasn't with me, so your point is null
autoprime had ample opportunity to say "don't do it yet", or "go talk to IO". but no, no objections were made.
Codefire treated the service like any other company would treat their unlocking service, so I treated them like a company and showed how it was done.
Before I start saying anything and before anyone starts ranting or fighting or whatever I want to make one thing crispy clear: I don't want, under any circumstances, to fight or argue in any way with other developers, contributors, users, whatsoever nor do I want to claim anything as correct. I am anytime ready to accept it if I am proven wrong for anything. Show me a proof against what I said and I will accept it. I'm not claiming anything to be right what I'm saying, but as long as it is not proven wrong I'm assuming it is right. Of course some statements base on assumptions and guesses, hence there is no reason for ranting about something particular I said that I am not entirely sure of. I just want to get this out because it has been sitting inside of me for a while and this is the only way I can get it out without offending or insulting anyone.
A statement from my side regarding TWRP and ROMs for the OP5:
I have seen many device trees so far, and the "official" TWRP as well and I'm pretty disappointed to see people not wanting to work together. Of course there are exceptions, for example I have been working together with @benschhold and @gtpitch on TWRP as well as on ROMs and it has been a pretty good experience so far. But I have also seen @Dees_Troy releasing his own TWRP. I tried to contact him and whoever is behind TWRP earlier to get a working TWRP up and running and official. No response. At least I haven't seen anything. I am anytime ready to work together and build working stuff, but I'm not ready to see something that is exactly the same as I did (his TWRP literally has the same, if not more, issues than mine, as far as user reports have told us) and releases it as an official product which should have been tested and does not even fix the issues we have so far.
I know mine is unofficial and I have stated nowhere that this would be official but if you check the sources used for my recovery as well as take the user reports into consideration you will notice that none of the issues we currently have on the now latest recovery image, that is version 72, have been fixed in either mine or his recovery. I would have liked to work together with developers to build a stable, fully working custom recovery with as many parts of it totally free and open-sourced for anyone to inspect. Regarding authorship, I'm anytime ready to correct authors in case they are wrong. What I am not ready for is seeing others taking my work and putting it under their own authorship so that nobody will know about what I did and instead honor the non-existent work of others misleadingly causing the community to think I would have stolen the work from others.
As I already said, I am open to any corrections regarding this.
Another aspect is the custom ROM section. While it's all good and fine to see ROMs coming out for the OP5, none of these are actually stable and fully tested. They might have been flashed and booted up and roughly checked for functionality but not actually tested for quality (not claiming anything here). I really can see a race between ROMs, maybe even a war, everyone perhaps even stealing the work of each other and claiming to be first but of course saying it's super highly experimental and whatsoever.
Why is this happening? I know I have very low reputation for saying anything in this matter, even though I am lead developer and co-founder of a ROM. I don't want to claim that anyone stole my work, and I don't want to be showing examples as they might not even be right because some things can really be done by anyone without seeing what others did. But still, everyone is racing against each other, except for a few ROMs, and trying to say hey yo we brought this rom out for jellyburger super fast and we are the best... blablabla, whatsoever, make sure to decrypt, make sure not to do this not to do that, note this doesn't work.... I guess y'all get the point.
Why do people work against each other and not together? Just trying to be the best, the first, whatsoever? I mean it's cool when you are first and best but it's not cool pretending to be so and in reality just having taken a WIP tree from whatever github profile you just went on and saying your ROM is the first, while in reality you actually don't have any idea about what you are doing. Guys, really.... I appreciate when people do in fact help bringing up custom roms for the OP5, I admit that I also take advantage of that for building my own rom, but I also try to improve it, contribute to it, to make sure others have access to my work and using it without changing authorship. Of course many developers e. g. copy whole directories into their device tree instead of getting the whole commit history in, and, to some extent, that is more or less acceptable, because there is no really convenient way of doing so, but at least, when picking individual commits, do keep authorship. Thanks for your understanding and I hope this community does not become corrupted.
I'm open for a peaceful discussion in this thread, let's get it started!
Cheeseburger developers and testers who can provide logs shall join https://t.me/joinchat/AAAAAEN_kkG6_WJe8IlG2Q
nadejo said:
Cheeseburger developers and testers who can provide logs shall join https://t.me/joinchat/AAAAAEN_kkG6_WJe8IlG2Q
Click to expand...
Click to collapse
Is not a bad beginning, but there actually is a dev group, so in case anyone wants to work together with each other, let me know. (Developers only)
Sad but true how many ROMs for the op5 have there source in the op?
Surely it's better for all of us to work collectively towards building a better base
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
a g bell said:
Sad but true how many ROMs for the op5 have there source in the op?
Surely it's better for all of us to work collectively towards building a better base
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Trees don't have to be equal but everyone should share contributions and help each other.
xdvs23 said:
Trees don't have to be equal but everyone should share contributions and help each other.
Click to expand...
Click to collapse
The general issue here is we all work opensource even if they are official teamwin they could just copycated your changes(im not saying this just assuming), dont want to insult anyone here but thats how it goes opensource projects are open and you cant change this, on the other hand they could actually start working on it legitely even if your recorvery is pretty stable(i would say 99%) they started it before but were able to get it to same point but later. As for now we need more developers in kernel section but i see you doing a good job keep it up my dude. :good:
MasterDomino said:
The general issue here is we all work opensource even if they are official teamwin they could just copycated your changes(im not saying this just assuming), dont want to insult anyone here but thats how it goes opensource projects are open and you cant change this, on the other hand they could actually start working on it legitely even if your recorvery is pretty stable(i would say 99%) they started it before but were able to get it to same point but later. As for now we need more developers in kernel section but i see you doing a good job keep it up my dude. :good:
Click to expand...
Click to collapse
The point is that it seems to be that they don't even care about their users. Don't quote me on that, as it might be wrong, but it seems to be that they simply just want to look down on other developers and be the big guys.
While I try to provide good support as much as possible, and release all my changes mostly individually, he simply gave it out once and every now and then might eventually look at the last 5 posts and maybe answer. I mean... I know he probably has alot of work to do but still. Released something officially without even checking for bugs. They say they make sure they provide quality but I can't see the quality there.
And for the other thing you mentioned... Most of the things they have in their tree really seem to be something that has been around for a longer time, but not actually made by themselves and just committed recently:
I don't really know why everyone tells to.keep authorship and maintaining a commit history and what not but end up simply copy and pasting the whole tree and commit that at once. Whatever. If this doesn't stop soon, I will start thinking about whether it is really worth doing this because from my point of view this is just looking down on me and releasing something that does not even work quite as well just to keep me away. I know I might be wrong anytime but this is what it feels like.
xdvs23 said:
The point is that it seems to be that they don't even care about their users. Don't quote me on that, as it might be wrong, but it seems to be that they simply just want to look down on other developers and be the big guys.
While I try to provide good support as much as possible, and release all my changes mostly individually, he simply gave it out once and every now and then might eventually look at the last 5 posts and maybe answer. I mean... I know he probably has alot of work to do but still. Released something officially without even checking for bugs. They say they make sure they provide quality but I can't see the quality there.
And for the other thing you mentioned... Most of the things they have in their tree really seem to be something that has been around for a longer time, but not actually made by themselves and just committed recently:
I don't really know why everyone tells to.keep authorship and maintaining a commit history and what not but end up simply copy and pasting the whole tree and commit that at once. Whatever. If this doesn't stop soon, I will start thinking about whether it is really worth doing this because from my point of view this is just looking down on me and releasing something that does not even work quite as well just to keep me away. I know I might be wrong anytime but this is what it feels like.
Click to expand...
Click to collapse
The next thing here is we shouldn't really assume anything cuz it might be making us look stupid, i would generally say to not care about what they do and i can say that most phones i had, used twrp from users there was no official ones and even if there was it wasn't functioning like other.
Right now how i see it is they opened a thread and called it official(i don't remember if they called it stable) and most users like official stuff so this generally looks funny from your pov, from mine too as i am self called open source developer and i know general ideas behind being open.
The only issue here i can see is that he doesn't respond to you soo it looks bad i really wouldn't assume anything cuz it can piss off a few ppl that's what i want to generally tell you to kindof watch out on the community around this because it already looks weird. If you want you can pm me with your telegram nickname and ill add you to a group where we work on a kernel fixing a small gelatinous issue some(me included) have. Would be for best if he answered to your pms soo you can have a talk and for now it looks like "stolen" work but at the same time we shouldn't assume stuff, for now i don't really know what to say on this whole matter it really looks quite weird and i don't like it too.
MasterDomino said:
The next thing here is we shouldn't really assume anything cuz it might be making us look stupid, i would generally say to not care about what they do and i can say that most phones i had, used twrp from users there was no official ones and even if there was it wasn't functioning like other.
Right now how i see it is they opened a thread and called it official(i don't remember if they called it stable) and most users like official stuff so this generally looks funny from your pov, from mine too as i am self called open source developer and i know general ideas behind being open.
The only issue here i can see is that he doesn't respond to you soo it looks bad i really wouldn't assume anything cuz it can piss off a few ppl that's what i want to generally tell you to kindof watch out on the community around this because it already looks weird. If you want you can pm me with your telegram nickname and ill add you to a group where we work on a kernel fixing a small gelatinous issue some(me included) have. Would be for best if he answered to your pms soo you can have a talk and for now it looks like "stolen" work but at the same time we shouldn't assume stuff, for now i don't really know what to say on this whole matter it really looks quite weird and i don't like it too.
Click to expand...
Click to collapse
Yeah that"s what I thought too but on the other hand, if you don't say anything, then nothing will change. Perhaps it won't change even after saying, but often it does.
You can add me to the telegram group if you want to, pm me the group link and I'll join but I can't promise to constantly be active there throughout the day.
xdvs23 said:
Yeah that"s what I thought too but on the other hand, if you don't say anything, then nothing will change. Perhaps it won't change even after saying, but often it does.
You can add me to the telegram group if you want to, pm me the group link and I'll join but I can't promise to constantly be active there throughout the day.
Click to expand...
Click to collapse
tru dat.
So, got my Mi Mix 2 yesterday, and because I'm gonna unlock & liberate it with LOS (MIUI = eww imho), I created an account over at account.global.xiaomi.com.
But no confirmation mail arrived.
So I went and checked the logs of my mail server, and, the mail from Xiaomi got rejected, because of a misconfigured helo greeting. (my mail server doesn't like non-resolvable helo greetings - a best practice to combat spam)
But because my mail server is also a polite mail server, it gives a temporary error (450) in that case, which a. makes the sending server try again and b. gives me a chance to whitelist false positives.
Alas, that mail system hasn't tried again since, and it's now 12 hrs later.
So, first impression of XaaS (Xiaomi as a service): Meh!
End of rant, I feel better now.
Welcome to the club. The initial xiaomi setup is always a pain... Which is why moving to AOSP ROMs is always my first step on these as well.
Best of luck.
Well, to be fair, I finally discovered the Resend link on the account creation page, hidden in plain sight. :angel:
And in the meantime I was able to create an account, figure out the necessary steps to get to the actual unlock process (learn some chinese, firewall piercing, I'll spare you the gory details), and am now waiting for 72 hours to pass.
But yeah, so far, exact opposite of unlocking other devices.
Sent from my h870 using XDA Labs
Honestly, too dramatic lol.
Am a Chinese here. Do you really need to learn some Chinese to unlock the device? Sorry but that somehow is quite funny to me.
Just tried. Haha, it's true that it keeps jumping to the Chinese version page, though all you need is to click the most obvious button. Hmmm, I can't believe XiaoMi still struggle with this given that it has quite a few overseas markets already. Maybe should post a feedback to them.
Yeah, parts of the accout website system have room for improvement - I really needed Google Translate, because nothing was obvious to me, it all looked the same, and I did not find a way to switch to english.
Ultimately, the search function saved my life.
Just going to Developer Options - Mi Unlock Status on the phone would have saved me some hassle (has instructions, even in german), but the LOS installation instructions don't mention that, I only found out later.
Oh well, live and learn. I managed in the end. Makes the whole thing even more satisfying I guess.
Sent from my h870 using XDA Labs
what guide should i follow for this phone to root it? android v10
You must be new here. I believe you have to be on Android 8 to be rooted and plus, it's pointless from what I read, anyways. For one, your phone will never fully charge and 2, I'd already inquired about it, the rooting process ends up not being dependable and your phone will no longer be a daily driver. So, the thought of it is a no for me.
I doubt there's even a way to go back to Android 8 and any necessary security patch levels.
https://forum.xda-developers.com/ga...r-development/root-extreme-syndicate-t4043723
You don't have to be on oreo right now for it to work, you just need a combo firmware that uses the same bootloader revision as what you're currently on. You can currently get an oreo combo firmware up to revision 4. Basically it's a "modded" oreo firmware that uses the same bootloader version as newer firmwares.
Please change title or close this thread. Got me excited for nothing
Why close ? Its informative.
Now i know i need to sell my phone caz it cannot be rooted.
How ever, S8+ on 9.0 had root but some devices such as mine were turning into brick attempting to root them due to bootloader version conflict which was not identified by root method or person who wrote the method.
Bricked several S8+ phones attempting to root. Was too afraid to try my last one.
Hell, am not made of money buying phones every time root turns it into a brick where even EDL'ing wont fix it.
What about this ?
How to root Samsung Galaxy Note 9 SM-N960U With Odin Tool - Gogorapid
(Last Updated On: October 29, 2019)How to root Samsung Galaxy Note 9 SM-N960U With Odin Tool
www.gogorapid.com
I dont like to just follow steps on some dodgy website, i'd rather follow steps here on forum since people can validate it.
Too scared to try, too little information about side effects.
tonycstech said:
What about this ?
How to root Samsung Galaxy Note 9 SM-N960U With Odin Tool - Gogorapid
(Last Updated On: October 29, 2019)How to root Samsung Galaxy Note 9 SM-N960U With Odin Tool
www.gogorapid.com
I dont like to just follow steps on some dodgy website, i'd rather follow steps here on forum since people can validate it.
Too scared to try, too little information about side effects.
Click to expand...
Click to collapse
Yeah, don't trust random websites. They mostly contain generic procedures that are either vastly outdated or downright wrong.
I have a rooted N960U, and this is what it takes to get there:
To actually be able to root an N960U, you have to be on a software version with an Android security patch level of February 1, 2021 or older (if you look at the baseband version under software information in the About phone section under Settings, the 5th digit from the right should be a 7 or lower number). Anything newer than that is unrootable as far as I know. And for the rooting procedure, you have to unlock the bootloader first which currently requires a paid service as mentioned in the following post:
https://forum.xda-developers.com/t/...iers_fix_safetynet_aio.4217753/#post-85381639
Finlay someone giving useful info.
I looked at the sampwn website for unlocking service and i didnt like it.
It threw some kind of subscribe message at me covering entire page so i couldn't even see what the website is all about.
Then it constantly showing "someone purchased this or that" and opens a chat i dont want to see.
Those are 3 red flags for a fishy website so i have to pass.
I did how ever manage to look at the purchase process page and it was also full of red flags.
It was asking too much personal information.
It did not say what you are buying, how much you going to pay for it or what payment method is accepted.
Entire website has a theme of a scammer website, or at the very least it was built using those themes and thus it acts just like it.
Telegram, discord username required ? What if i dont have one ?
Do you want my password to my bank as well ?
Card number with expiration date and full name address and 3 security digits to pay ?
Are you F'ing serious ?
I dont know a single website that sell you stolen serial keys or cracked software that ask you this much information and claim "its required"
Besides, if there is a paid way, there must be a free way.
Who is this guy, owner of some sort of unlocking device ?
Whats the point of locking it if some lone wolf can unlock it anyway ?
Very sketchy.
tonycstech said:
Finlay someone giving useful info.
I looked at the sampwn website for unlocking service and i didnt like it.
It threw some kind of subscribe message at me covering entire page so i couldn't even see what the website is all about.
Then it constantly showing "someone purchased this or that" and opens a chat i dont want to see.
Those are 3 red flags for a fishy website so i have to pass.
I did how ever manage to look at the purchase process page and it was also full of red flags.
It was asking too much personal information.
It did not say what you are buying, how much you going to pay for it or what payment method is accepted.
Entire website has a theme of a scammer website, or at the very least it was built using those themes and thus it acts just like it.
Telegram, discord username required ? What if i dont have one ?
Do you want my password to my bank as well ?
Card number with expiration date and full name address and 3 security digits to pay ?
Are you F'ing serious ?
I dont know a single website that sell you stolen serial keys or cracked software that ask you this much information and claim "its required"
Besides, if there is a paid way, there must be a free way.
Who is this guy, owner of some sort of unlocking device ?
Whats the point of locking it if some lone wolf can unlock it anyway ?
Very sketchy.
Click to expand...
Click to collapse
Whatever method is being used to unlock the bootloader on these models has not been made public, so that's why there are only paid ways.
I can't speak for SamPWND as I used the first link with UNSAMLOCK, and the guy running it was quite helpful and did things quickly. But you do need to contact him through Telegram.
This is certainly not for everyone, so you really have to be sure you want it as it's a one-time, one device only thing. Otherwise, you'll have to look at the Exynos models or the international Snapdragon N9600 model for freely available bootloader unlocking and rooting methods.
SamPWND is a group on telegram i joined.
But i cant contact anyone there. All i get is what the owner posts.
How am i suppose to contact the owner if i want to unlock my bootloader ?
Jeezes ! Why they make things more complicated then they need to ?
In any case, the owner of that channel is some guy named Mohammad Afaneh
Are you F'ing kidding me ?
I am not sending my phone to some guy named Mohammad. Hell no !
He either hack it or put ship me a bomb back that will explode when i open it.
tonycstech said:
SamPWND is a group on telegram i joined.
But i cant contact anyone there. All i get is what the owner posts.
How am i suppose to contact the owner if i want to unlock my bootloader ?
Jeezes ! Why they make things more complicated then they need to ?
Click to expand...
Click to collapse
That's pretty strange for a Telegram group. Check the UNSAMLOCK one then as that's the one I used and had no problems with.
But remember that only older software versions are eligible. If yours is later than February 2021, then you won't be able to do anything.
tonycstech said:
SamPWND is a group on telegram i joined.
But i cant contact anyone there. All i get is what the owner posts.
How am i suppose to contact the owner if i want to unlock my bootloader ?
Jeezes ! Why they make things more complicated then they need to ?
In any case, the owner of that channel is some guy named Mohammad Afaneh
Are you F'ing kidding me ?
I am not sending my phone to some guy named Mohammad. Hell no !
He either hack it or put ship me a bomb back that will explode when i open it.
Click to expand...
Click to collapse
Afaneh has a good rep on XDA, for all I've seen. But I read you about Telegram, kinda irritrates me how it's taken away from the much more available xda forums. I could join, but like I was saying elsewhere just last night, I'm already way too "joined" as it is.