Related
Has anyone made a froyo build for the cdma Hero in which everything is working? If not then why not the source has been out for awhile now so whats up peeps. Any links to all builds? ANY i said. And im not complaining just tired of searching through threads, and i have an EVO but i like my hero just the same.
Why haven't YOU made one yet?
I don't get people that make posts like this.
nope...good luck
vinny8030 said:
Has anyone made a froyo build for the cdma Hero in which everything is working? If not then why not the source has been out for awhile now so whats up peeps. Any links to all working builds?
Click to expand...
Click to collapse
Wow. Really?
exactly..lol I mean if u really want one dont complain..go build it yourself.. or keep quiet. be patient like the rest of us. and go support darch for even trying to get a froyo build to us hero users!!
Be glad we still have a few devs around to keep us hero users going for awhile.. since most have jumped ship to the evo etc.... so show some support etc if not guess u could alway go get a evo,lol
Oh man guys, he's right... I mean, it's not like devs have been working hard on giving us FroYo already... they should listen to this guy!
Really though, OP... this has got to be one of the most ungrateful posts I've read yet. If Darch the rest could give us a fully working 2.2 right now, they would... They're working hard on it, and they provide these roms to us for FREE. And then you came in here and basically clapped your hands twice and said "chop chop!"
Just be patient, and maybe a bit more respectful.
vinny8030 said:
Has anyone made a froyo build for the cdma Hero in which everything is working? If not then why not the source has been out for awhile now so whats up peeps. Any links to all working builds?
Click to expand...
Click to collapse
seriously?? you made a thread to ask this question..
1. we have a Q&A section, and this isn't it..
2. sense u are in this section, did it not occur to you to check the available ROM's for ur answer???
by the way, to the others that have commented.. i don't think this guy even knows theres a froyo version out at all.. i don't think hes tryna speed darch up or anything.. i just think he hasn't checked this forum for much of anything.
A huge part of it is that they aren't porting it - they're actually using the source files to build it for the Hero.
Darch and company are building the 2.2 rom from the ground up so there are issues being ironed out. The current 2.2 version is RC0 (Release Candidate Zero) aka its in beta meaning its open to download and use but please either help fix the bugs or at the very least report them. This is how we the users can help move collectively towards a bug free froyo release.
Wow negativity!!
I think some of you people missunderstand the point of this post. Its not to complain but to get some links all in one place for anyone who has built a Froyo for the hero. And to awnser the smartassed remark i havent built one because i dont know how. I am a mechanic and amateur computer builder.
Sorry for any confusion, just want one place for the links instead of needing to search through all the threads to find them.
bk718 said:
seriously?? you made a thread to ask this question..
1. we have a Q&A section, and this isn't it..
2. sense u are in this section, did it not occur to you to check the available ROM's for ur answer???
by the way, to the others that have commented.. i don't think this guy even knows theres a froyo version out at all.. i don't think hes tryna speed darch up or anything.. i just think he hasn't checked this forum for much of anything.
Click to expand...
Click to collapse
This isnt Q&A its a place for LINKS to any Froyo builds. I repeat ANY builds.
Ok dude, I guess I see what you were TRYING to ask/say/organize, but you did it in a real Asshattery way.
What you should have said was "Please All Devs put your FroYo Links Here"
With a message that should have said "Due to the threads bouncing around the forum, sometimes it's kind of hard to see all the options so I figure we should have links to these threads in one spot and we could make this thread a sticky".
It's no secret these devs (even though I claim one rom, I am NOT a dev. I am a kitchen user) bust their ass and take pride in the work they have accomplished making these froyo builds with no monetary gain except that they can reap the fruits of their work in using their own builds.
I know if it were me then I would have jumped the gun and taken offense and honestly I am surprised that there were not a flood of flame posts here because of it.
http://darchroms.pocketdevelopers.com/cm/willeaturcat.zip
report issues and join in on the testing like we all are darchstar is almost there
what is that willeatyourcat.zip ? is that RC0 ?
RC1
Sent from my HTC Hero CDMA using XDA App
Okay, As of now Darch's 2.2 builds are in beta. That being said they are not be posted on xda by him (just guessing here) because if he did, THOUSANDS of people would post useless questions and turn the thread into a joke.
Be patient, and wait for a final to get posted.
Or, get on the IRC channel and help test the current builds.....
My 2 cents.
I think we should give darch some $$ or petition Google to do so OR (if you can) give him a secure job providing these generous updates!
What's the incentive otherwise? This isn't OUR work.
Sent from my HERO200 using XDA App
who says "peeps" anymore or ever?
I do when I feel like typing peeps instead of 'persons I know'
Sent from my HERO200 using XDA App
thatguythatdid said:
who says "peeps" anymore or ever?
Click to expand...
Click to collapse
Ummm I say peeps every year around Easter, as in Marshmallow Peeps. YUMMMMM
Just a thought,
Whether there will be a community release of an Android ROM for vogue, which all devs come together in a team and make -maybe- one Android ROM ?
It would gain more advantage because all the devs will contribute according to their respective ideas and if this happen, it's must be a must have android for vogue.
Thank you for all the devs here that make our vogue life.
vellowax said:
Just a thought,
Whether there will be a community release of an Android ROM for vogue, which all devs come together in a team and make -maybe- one Android ROM ?
It would gain more advantage because all the devs will contribute according to their respective ideas and if this happen, it's must be a must have android for vogue.
Thank you for all the devs here that make our vogue life.
Click to expand...
Click to collapse
like one big mega rom i know they all help each other in one way or another but this mega rom would be a pretty cool idea
Honestly, it's pretty much like that already,
vellowax said:
Just a thought,
Whether there will be a community release of an Android ROM for vogue, which all devs come together in a team and make -maybe- one Android ROM ?
It would gain more advantage because all the devs will contribute according to their respective ideas and if this happen, it's must be a must have android for vogue.
Thank you for all the devs here that make our vogue life.
Click to expand...
Click to collapse
Lol - every release is a community release. That sounds funny but everybody is using something somebody else did, I guarantee it. You should go on a history walk and find out when things got done and who did them...
The installer, for instance (vilord) - we all see it every time we load a new build. it's been around for quite a while now and hasn't really needed any changes. We had a method before that that dzo had cooked up but it was, ahem, a bit confusing for some (somehow.) Or GPS - a ton of early work by srwalter. Fixes by dzo. A ton of revision by jnadke. Further enhancements by kallt_kaffe.
Obviously, none of those things would have happened without dzo.
This leaves out a ton of folks, of course - mssmison, for example, had his hands and say in just about everything when he was around.
All that to say, every dev uses a bunch of stuff that others have done. Every release is a community release. That's the way it's meant to be, that's the way it is, and we all benefit as a result.
*hugs*
EDIT:
mssmison said:
Honestly, it's pretty much like that already,
Click to expand...
Click to collapse
Right - what he said. Brevity is the soul of... something.
mrkite38 said:
Lol - every release is a community release. That sounds funny but everybody is using something somebody else did, I guarantee it. You should go on a history walk and find out when things got done and who did them...
Obviously, none of those things would have happened without dzo.
Click to expand...
Click to collapse
mssmison said:
Honestly, it's pretty much like that already,
Click to expand...
Click to collapse
Yes, i agree with that.
actually, vilord build is my first android rom on vogue and Dzo is the magician here -you are not really retire from this great forum right ?
So, i'm wondering if the ROM might goes into like this ;
"How about if i have Dzo build or K_K build with a ton of Incubus and Myn blazing design and tweak and many other contributions by all the devs here ie for the zImage, initrd, maybe some splash screen, apps or the battery performance (*Can we steal this from CM?) so i can say "This is my android stock ROM for vogue"
But anyway I'm not a programmer, I'm just a user.
thanks for sharing.
Hope this will not hurt anyone.
I'm not working on it, its not free for anyone to use, so I decided I wouldn't mess with it.
Awesome! Thanks!
Sent from my SGH-I897 using xda premium
DemonWav said:
So I ran into a lot of problems at the last minute...
I saw some people were interested in a Matted Blues port to KF1, I personally am not a fan of Matted Blues, but I decided to do the port anyways, for the community.
Anyways, presenting Matted Blues. Well, sorta. I went on the market to get the CM7 version of Matted Blues, and when I went to buy it, it turns out that I couldn't afford it. I am completely out of money, so I literally could not afford $2. (lol). So I went and got shoman94's port, which I didn't want to use because I remember he said he edited it a little. So this is NOT a real port, I will work on that port when I get the money (the whole 2 bucks...) and will actually start working on fixing all the bugs. So here we go!
-BUGS:
-Music controller on lockscreen is supa crazy, I've seen that on every 2.3 Touchwiz rom, I haven't figured out what the cause is for it yet though. I fixed i up the best I could, but I will eventually (hopefully) get it completely fixed.
-ITS UGLY! I don't know if its shoman94's edits to the notification panel or its just an older version, but I just find it extremely ugly. Not dissing on shoman94, everyone to their own, just saying that once I do an official exact port, it will be...well, an exact port.
-A lot of the colors are darker, I know this is due to shoman94 as that is how he edited. It doesn't look bad, but it is not the color that Matted Blues should be. It is supposed to be 73B6D6 and he changed it to 367999. Again, this will be fixed when I do the real port.
-Other misc. issues that are hardly noticeable and would just be a wasted effort to fix until I did the real port.
Download:
Matted Blues - Cognition 5 v2
Revert
Click to expand...
Click to collapse
Then don't use it! Don't talk **** and say it's UGLY in caps then say oh no offense. You did offend and you also didn't ask to use the work I put into it. You can take the original and make your own port. Many APK's and files are different than the Cappy. Things were made by myself and modded to my liking! I asked for permission from the author before I posted and you should do the same. I don't like you attitude here sir.
Sorry for offending you, that's not what I meant. As I said, "everyone has their own", for themes everything is opinionated. An opinion is neither right nor wrong. But regardless I did forget to put the credits up and I do see how what I said was inappropriate, and I apologize.
Basically, the situation is this......
If you want to port a theme (that someone else has created) then you need the express permission of the original creator first.
In this case, if you are to be using work by two people, you need two sets of permission.
No permission, no thread.
If you currently have not agreed this with the original creator(s) then please remove the links until you have done so.
Thanks.
DemonWav said:
Sorry for offending you, that's not what I meant. As I said, "everyone has their own", for themes everything is opinionated. An opinion is neither right nor wrong. But regardless I did forget to put the credits up and I do see how what I said was inappropriate, and I apologize.
Click to expand...
Click to collapse
I except your apology but as stated above, with me you didn't even send me a simple PM asking to use it. I can't speak for the author as I don't know if you asked him but I know he wants to be asked before it's posted. The rules here are very simple and like I had to with every port I worked on.... you need to follow the same rules.
You will find out also that all the blues are no the same hence the name mattedBlue(s) and that alot didn't match when I used that color code on my screen. All my changes were to make icons match and also prefer the deeper tones. Now I have gone through many changes since I have been working on this theme for while since Continuum 4 on froyo.
But again... if you don't like the work I did which I spent days and days on. Just don't use it at all. You don't post something saying here is this for now..... I don't like it and I'm gonna change it all later then repost it.
Opinions are fine and dandy and you have the right to it. It's just disrespectful. You should have asked to use some of it... made your changes then posted. Froili was a good example of that when he posted his version of it.
Anyways.... good luck in your port.
I remembered the rules incorrectly, sorry. The reason I used yours was because I wanted something to put up for a while before I got to the actual port, which is going to take a while. But I guess I'll just wait until I can do the actual port. And as for the Blues being the same, I really don't care, people want the theme ported so I will try to port the theme exactly how it looks. I know TW is different but that just means I'm going to have to put more work into it, which I have no problem doing...
DemonWav said:
I remembered the rules incorrectly, sorry. The reason I used yours was because I wanted something to put up for a while before I got to the actual port, which is going to take a while. But I guess I'll just wait until I can do the actual port. And as for the Blues being the same, I really don't care, people want the theme ported so I will try to port the theme exactly how it looks. I know TW is different but that just means I'm going to have to put more work into it, which I have no problem doing...
Click to expand...
Click to collapse
Its understandable as I went through the same thing. But the only thing you had to do was ask the 2 of us to use it. You also could have made changes as you went.
But things here went all askew. I personally would have asked for permission then just posted it saying here is my port of mattedblues and thanks to the author and whoever for bringing it to the cappy then just make changes as you go. Not complain about what my tastes were. It was originally made for myself then decided to share it. I posted that I made changes to it and such.
I don't want to drag this on and I'm here to share what I do because this is what android is all about. SO just respect what people do by asking permission to use it and you can make changes without cause ill feelings.
Good luck
Do you really have to ask permission to use something that is open source? I'm guessing the developers on this site haven't asked samsung for permission to use their base. I understand it is proper to give credit where it is due, but I don't think permission should be required.
Sent from my SAMSUNG-SGH-I897 using XDA App
jlsesler said:
Do you really have to ask permission to use something that is open source? I'm guessing the developers on this site haven't asked samsung for permission to use their base. I understand it is proper to give credit where it is due, but I don't think permission should be required.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
When it comes to themes yes permission is required. Themes (PNG's) are not part of the open source clause.
I can tell you that I have never said no and no one has ever said no to myself when I ask. I still haven't said no..... I just haven't been asked.
Very good green theme,thanks!
So is this theme still being worked on?
jlsesler said:
Do you really have to ask permission to use something that is open source? I'm guessing the developers on this site haven't asked samsung for permission to use their base. I understand it is proper to give credit where it is due, but I don't think permission should be required.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
That's exactly what I thought. But I have decided to forget this theme because I believe this is supposed to be an open community, open to everyone. Having a price tag on something does not make it open to everyone, so I am just not going to mess with it. Someone else can do it.
This is a discussion thread for all things custom; Building steps and tips, problem solving and issue discussion. All questions and/or comments are welcome. Be aware, although I build and customize ROMs, I am not a professional developer and cannot promise a solution for your problem. But, hopefully, we can work together to come up with practical solutions for any problems here at m7spr.
So..The things you were shut down on. Were they CM related, or Sense stuff?
Did they involve you working solo, or with a team? Give more details, get the word out.
Felnarion said:
So..The things you were shut down on. Were they CM related, or Sense stuff?
Did they involve you working solo, or with a team? Give more details, get the word out.
Click to expand...
Click to collapse
I really am leery of pointing fingers at specific people because I'm new here and don't want to make a name for myself as a whiner. But, basically it is both. The custom ROMs I am working on have all been built before by me on other devices, so that's not the issue. I have inquired about possibly collaborating with other devs on some Sense related stuff and was looking into why there was no official or unofficial release of the current CM10.2. The sense stuff really isn't my bag as much, but i was/am interested. Others are working on the CM, but with no official release in play, no one wants to put theirs out. I have built it successfully, but have no intention of trying to lay it out there when other devs have been working on it before I got here. My thing is this: when I got tired of waiting for devs to come up with new things, I was told to put up or shut up. It was good advice; I have no coding experience specifically, but I like to learn and have been successful at not only compiling and maintaining custom builds, but also starting 'Learn to do it yourself' threads in two different device forums. I like to learn and compile and share. That's it. I don't need (or want) attention or grateful fans or any of that crap. All I want to do is open the doors for more builds and more users getting off their asses and building for themselves. It seems like a win-win to me, but I feel resistance and it is disappointing. I will get off my soapbox now
I typically touch base with any dev who is the creator/maintainer of any ROM I am interested in pursuing. My experience has been more of a quick 'try it out and see what you get' response or 'it can't be done'. This is after I have asked for not only a blessing, but for relevant information and possibly assistance. Maybe I am just hitting up devs who are already frustrated and don't want someone like me asking a bunch of questions, I don't know....
BMP7777 said:
I really am leery of pointing fingers at specific people because I'm new here and don't want to make a name for myself as a whiner. But, basically it is both. The custom ROMs I am working on have all been built before by me on other devices, so that's not the issue. I have inquired about possibly collaborating with other devs on some Sense related stuff and was looking into why there was no official or unofficial release of the current CM10.2. The sense stuff really isn't my bag as much, but i was/am interested. Others are working on the CM, but with no official release in play, no one wants to put theirs out. I have built it successfully, but have no intention of trying to lay it out there when other devs have been working on it before I got here. My thing is this: when I got tired of waiting for devs to come up with new things, I was told to put up or shut up. It was good advice; I have no coding experience specifically, but I like to learn and have been successful at not only compiling and maintaining custom builds, but also starting 'Learn to do it yourself' threads in two different device forums. I like to learn and compile and share. That's it. I don't need (or want) attention or grateful fans or any of that crap. All I want to do is open the doors for more builds and more users getting off their asses and building for themselves. It seems like a win-win to me, but I feel resistance and it is disappointing. I will get off my soapbox now
I typically touch base with any dev who is the creator/maintainer of any ROM I am interested in pursuing. My experience has been more of a quick 'try it out and see what you get' response or 'it can't be done'. This is after I have asked for not only a blessing, but for relevant information and possibly assistance. Maybe I am just hitting up devs who are already frustrated and don't want someone like me asking a bunch of questions, I don't know....
Click to expand...
Click to collapse
you can start by helping to get things working in sense 4.2.2 beta rom
flex360 said:
you can start by helping to get things working in sense 4.2.2 beta rom
Click to expand...
Click to collapse
I looked your thread up and I think we'd get along great. Anybody who says 'if you don't like me, GOOD' is someone I wanna hang with. It's also funny you should mention helping with that sense version because that's exactly what I was trying to do. Sense aint even my bag, but I was going to look into it from the SVD side to see what I could learn. Maybe I just rubbed that guy the wrong way or something. Regardless, I can't promise how much help I will actually be, but I'm willing to give it a shot. Tell me what you need and the right places to look and I'll do whatever I can. Be cool
BMP7777 said:
I looked your thread up and I think we'd get along great. Anybody who says 'if you don't like me, GOOD' is someone I wanna hang with. It's also funny you should mention helping with that sense version because that's exactly what I was trying to do. Sense aint even my bag, but I was going to look into it from the SVD side to see what I could learn. Maybe I just rubbed that guy the wrong way or something. Regardless, I can't promise how much help I will actually be, but I'm willing to give it a shot. Tell me what you need and the right places to look and I'll do whatever I can. Be cool
Click to expand...
Click to collapse
do you have google hangout?
I think one issue is that there is an update to 4.3 looking for the Sprint One. This will undoubtely contain new radios and firmware that will help our phones run on 4.3+. Since this is a know update, many devs have decided to forego work on the the current 4.1.2 Sense ROMs. Some are working on the 4.2.2 Sense ROM, but with no leak, or Sprint version it is much harder work. Also, there is only source for up to 1.29. The source from the 1.31 update is not available and it has caused issues with ROMs based on that update.
Personally I don't get your complaint though. There is a lot of development and a wide selection of ROMs available from Stock Android 4.1 to 4.3 to Stock Sense, to heavily themed Sense ROMs. What exactly is not available that you want?
flex360 said:
do you have google hangout?
Click to expand...
Click to collapse
[email protected]
raptoro07 said:
I think one issue is that there is an update to 4.3 looking for the Sprint One. This will undoubtely contain new radios and firmware that will help our phones run on 4.3+. Since this is a know update, many devs have decided to forego work on the the current 4.1.2 Sense ROMs. Some are working on the 4.2.2 Sense ROM, but with no leak, or Sprint version it is much harder work. Also, there is only source for up to 1.29. The source from the 1.31 update is not available and it has caused issues with ROMs based on that update.
Personally I don't get your complaint though. There is a lot of development and a wide selection of ROMs available from Stock Android 4.1 to 4.3 to Stock Sense, to heavily themed Sense ROMs. What exactly is not available that you want?
Click to expand...
Click to collapse
This really wasn't meant to be some complaint thread with a bunch of whining; just the opposite, really. I just wanted feedback on how I am perceiving things around here. I'm cool with being told I have it wrong; was hoping for it actually. And you pointed out exactly what I mean in part. Sense this and stock that is the rule of the day here. That's ok. Everyone is allowed to like whatever they want and if sense and stock are the most wanted builds then so be it. But, I am a self-proclaimed customization junkie, for better or for worse. Personally, I like more fully custom ROM choices and have been beating my head against the wall trying to get some Beanstalk love here but without success to this point. BS is already set in 4.3 and matched with CMs 10.2 releases, so I'm stumped. If you have knowledge, I would be happy to show you some of my errors. I do think you make a great point about the whole place being in flux due to the impending 4.3 release. Like I said before, I just want to open up some development doors and get more interest in development in general. Maybe I have hit up the wrong devs or caught them at bad times. It happens.
BMP7777 said:
[email protected]
This really wasn't meant to be some complaint thread with a bunch of whining; just the opposite, really. I just wanted feedback on how I am perceiving things around here. I'm cool with being told I have it wrong; was hoping for it actually. And you pointed out exactly what I mean in part. Sense this and stock that is the rule of the day here. That's ok. Everyone is allowed to like whatever they want and if sense and stock are the most wanted builds then so be it. But, I am a self-proclaimed customization junkie, for better or for worse. Personally, I like more fully custom ROM choices and have been beating my head against the wall trying to get some Beanstalk love here but without success to this point. BS is already set in 4.3 and matched with CMs 10.2 releases, so I'm stumped. If you have knowledge, I would be happy to show you some of my errors. I do think you make a great point about the whole place being in flux due to the impending 4.3 release. Like I said before, I just want to open up some development doors and get more interest in development in general. Maybe I have hit up the wrong devs or caught them at bad times. It happens.
Click to expand...
Click to collapse
Part of the issue might be that users are afraid of using Cm as it has a nasty habit of bricking phones that no one of notoriety has looked into, acknowledged, or found a solution to.
Kraizk said:
Part of the issue might be that users are afraid of using Cm as it has a nasty habit of bricking phones that no one of notoriety has looked into, acknowledged, or found a solution to.
Click to expand...
Click to collapse
I haven't really been looking at it after my first run (I personally like Sense a lot, and AOSP didn't have a good way of dealing with the limited hardware options for me), but wasn't the brick-spree killed a while back?
Rirere said:
I haven't really been looking at it after my first run (I personally like Sense a lot, and AOSP didn't have a good way of dealing with the limited hardware options for me), but wasn't the brick-spree killed a while back?
Click to expand...
Click to collapse
A couple of people developed a "consensus" that it had been fixed. then 2 more people bricked their phones. ALLEGEDLY the CPU has a tendency to over clock itself and lock at 1.7 Ghz
This is all fine and dandy yet no one can figure out why or how to stop it.
I thought so too
Sent from my One using XDA Premium 4 mobile app
BMP7777 said:
I thought so too
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Like I said no one ever figured out why or how to stop it. A consensus was reached but then more people bricked. No developers could be bothered to take time out of their day to look into it though.
Kraizk said:
Like I said no one ever figured out why or how to stop it. A consensus was reached but then more people bricked. No developers could be bothered to take time out of their day to look into it though.
Click to expand...
Click to collapse
I saw one guy who was addressing it and taking names and such, but then I guess it just faded away. Do you know of ongoing issues like this? Can all of the bricks be undoubtedly proven to be from no other cause? I think that would be the defining characteristic of lack of support; difficulty in proving cause. My build of CM10.2 runs fine as long as I don't try to change the font with Font Installer. And I am reasonably certain that it isn't from CM all by itself. I have the same issue with Illusion ROM 4.2.2. Anybody know why we can't change the font? My thread; I can change topic if I want to
BMP7777 said:
I saw one guy who was addressing it and taking names and such, but then I guess it just faded away. Do you know of ongoing issues like this? Can all of the bricks be undoubtedly proven to be from no other cause? I think that would be the defining characteristic of lack of support; difficulty in proving cause. My build of CM10.2 runs fine as long as I don't try to change the font with Font Installer. And I am reasonably certain that it isn't from CM all by itself. I have the same issue with Illusion ROM 4.2.2. Anybody know why we can't change the font? My thread; I can change topic if I want to
Click to expand...
Click to collapse
It is the only common factor in permanent bricks. Phone gets hot, phone wont charge. All other "bricks" are user induced because people did not understand what S-Off meant, what wiping in TWRP means, what GSM means etc etc.
So how many confirmed permanent bricks and when was the last? Has anyone proven a cause? Contacted HTC or CM or Sprint? If there were twenty cases with only 5 confirmed, then it isn't that big from a larger standpoint. See what I mean? That would explain what you see as a lack of support? Has this happened to you?
BMP7777 said:
I thought so too
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Check your hangouts.
BMP7777 said:
Why does there seem to be very little development going on here and why is the development that is taking place so closely guarded? I thought everyone wanted more choices and new options..... I see that there is current and ongoing 10.2 development (hell, I've even built it), but no one wants to release it. I'm hearing that the last guy who did that got banned. So, if everyone is waiting for OFFICIAL builds to be released first, why are there none being officially worked on? Two times in the last three weeks I have inquired about wanting to work on some new development and have either been told straight out not to release or been effectively threatened with reporting before I have even begun an attempt. I don't know if maybe there has been a rash of jerks who are trying to claim ownership of work that does not belong to them or what, but I've never seen as much negativity about new builds in any thread I have been a part of. I want to claim ownership of nothing; I only want to open doors. I guess I'll just work on things for my own use and leave this forum to the guys currently running it. HMPH :angel:
Click to expand...
Click to collapse
You could build us a GSM version ROM that works on the sprint HTC One. You'd be a hero if you could do that. We've already unlocked our phones and are able to connect to the ATT / TMO but only manually. When the signal is lost it seems to still be looking to auto connect to sprint...I would think this should be a simple setting software but I know nothing about phone ROMs.
Beck04vall said:
You could build us a GSM version ROM that works on the sprint HTC One. You'd be a hero if you could do that. We've already unlocked our phones and are able to connect to the ATT / TMO but only manually. When the signal is lost it seems to still be looking to auto connect to sprint...I would think this should be a simple setting software but I know nothing about phone ROMs.
Click to expand...
Click to collapse
Man, if I could do that I'd be a GOD. :angel:
I love lamp
Haha Naw but I see your point but I love and appreciate every devolepers effort here on this forum ..there not a a lot but a bunch of smart and quietly brilliant devs here ...I'm comfortable but the more the merrier
Sent from my HTCONE using XDA Premium 4 mobile app
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.