Database Info

Cyanogen ports Android 2.1 to G1 and MyTouch 3G

(taken from engadget)
Droid, Milestone, Eris, Moment, Spica, even the Hero, all have had their Eclair, one way or another. G1 and myTouch 3G? Not so much. But don't worry, Android early adopters, because Cyanogen's got your back. Most all the bells, whistles and hardware-accelerated graphics of Android 2.1 are coming to the HTC Dream, Magic and Sapphire in CyanogenMod 5.0.7, and you can see a video of a T-Mobile G1 running the new build after the break. Twitter buzz indicates the ROM will be out any minute now; the dev himself tweeted that it's ready to go and just needs G1-friendly bite size packaging.
There is video also.
Tried to submit with links but got "To prevent spam to the forums, new users are not permitted to post outside links in their messages. All new user accounts will be verified by moderators before this restriction is removed."
Got to engadget(dot)com to see.
engadget(dot)com/2010/04/29/cyanogen-ports-android-2-1-to-g1-and-mytouch-3g/
www(dot)youtube(dot)com/watch?v=3HVBVlAui3s&feature=player_embedded
Update: Don't stay up all night waiting -- Cyanogen says he's got "two more bugs to kill" and is "hoping for a test1 public beta tomorrow night."

Sweet this is really gonna annoy my bro xD he's been banging on about his nexus and how much it cost and how great 2.1 is

what about 32A?

this looks great!!!!...cannot wait for this to come out. I have tried some other various ports of the 2.1 they all seemed very choopy and needed alot more work... I am a very busy guy that needs stuff to work when I tap the screen to make it work, Cant wait around for things to happen....Cyanogen's build looks very smooth and responds very well....when will we know when it gets released?

For the latest news, including the release (which should be tonight according to cyanogen) you can keep an eye on twitter(DOT)com/cyanogen

I haven't really looked forward to the release of a ROM in a while. If what Cyanogen is saying in his Twitter is all correct (everything working with 2.1), then this one is the one.

xyrcncp said:
I haven't really looked forward to the release of a ROM in a while. If what Cyanogen is saying in his Twitter is all correct (everything working with 2.1), then this one is the one.
Click to expand...
Click to collapse
I totally agree with you on this one.....I was having a hard time putting the latest super D rom back onto my G1 after flashing one of the other 2.1 ports...so I am now currently running [ROM]TheOfficial DONUT TMO, ADP & AOSP (dream/magic)(EBI0/EBI1) [3/17/2010] -- v2.6.3 (which is also found here btw) with the Buuf theme...it is an alright ROM but this 2.1 port that Mr. Cyanogen released with help with other various "modders"....it looks great...flashin it as I am typing (YAY)
THANX TO ALL MODDERS INVOLVED WITH THIS BUILD

just a quick thought....i just finished flashing this rom to my G1 and I was thinking that it would be cool to add the nexus "X" boot screen that would cross over into the cyanogen symbol....would try to make it myself but I do not have the slightest clue on how to do that!!

Just to let everyone know the rom is up and running great. I got it on my mt3g 32B. Only thing is that the LED notification light is purple. Could anyone please tell me how to change it. thanks.

Does this work with the mytouch 1.2 with 3.5 jack? I am new to this and hoping to get some help. I just want to make sure I got this right.
1. Backup my phone. What do I use to do this?
2. Root my phone.
3. Flash phone with new rom.
If anyone could point me in the right direction on how to flash a phone I would appreciate it. Thanks

HyDrO84 said:
just a quick thought....i just finished flashing this rom to my G1 and I was thinking that it would be cool to add the nexus "X" boot screen that would cross over into the cyanogen symbol....would try to make it myself but I do not have the slightest clue on how to do that!!
Click to expand...
Click to collapse
yes i know that I am quoting one of my previous posts but....THIS ROM IS F-IN AWESOME
GREAT JOB MODDERS!!!!!

AOSP 2.1: How functional will this be?

Basically, how quick could we expect a straight AOSP port of 2.1 and how functional will it be? I know that the 2.2 build is missing camera, 4G, and MMS, but will we have those same limitations since the source code of 2.1 is already out?
-------------------------------------
Sent via the XDA Tapatalk App

Nah--we've got the libraries for 2.1 from the original ROM; all we need is access to flash what we desire, and we can put together an AOSP 2.1r2 build in short order (24 hours or less) that's fully-functional.

Shidell said:
Nah--we've got the libraries for 2.1 from the original ROM; all we need is access to flash what we desire, and we can put together an AOSP 2.1r2 build in short order (24 hours or less) that's fully-functional.
Click to expand...
Click to collapse
When you say the libraries I assume you mean because we already have 2.1 on the evo.
I know with the hero it was a ***** to get the camera, cause HTC has not release the .29 kernel source, so we were stuck with the .27 until toast finally built his own .29 kernel. He is such a stud. By the way it was prolly less than a month ago they got the camera in a 2.1 full aosp rom.
I would think it would not be anything like this though.

Roman G said:
When you say the libraries I assume you mean because we already have 2.1 on the evo.
I know with the hero it was a ***** to get the camera, cause HTC has not release the .29 kernel source, so we were stuck with the .27 until toast finally built his own .29 kernel. He is such a stud. By the way it was prolly less than a month ago they got the camera in a 2.1 full aosp rom.
I would think it would not be anything like this though.
Click to expand...
Click to collapse
I think we have a lot more support coming over to the Evo than we had with the Hero. Shouldn't be that long, but its just a matter of getting that kernel source. Your right though, with Toast on our side I dont think anything is impossible. The good thing about Android is you can flash another image in no time at all, so if you wanna see what its all about (Without Camera, MMS, and whatever it was) then you can flip back and fourth just to see the difference. Apps2SDK will be a big plus since we wont be needing to go to the market everytime to get all of our widgets and things back. My mouth is watering as im less than 43 hours from getting her juiced and ready to go!

Thank you for asking this question! (I was going to but was too lazy.) Unfortunately I'm going to wait to get the Evo until there is a way to get AOSP 2.1 (or fully functional 2.2) on it. I hate Sense with a passion. So, good luck everyone and may you quickly make our dreams come true!

Stunna4life888 said:
Shouldn't be that long, but its just a matter of getting that kernel source.
Click to expand...
Click to collapse
We already have kernel source
We tried the 2.1 camera libs in 2.2 (hint came from the fact that Toast saw that the froyo N1 ROM does not replace the camera library as part of its update from 2.1 to 2.2, indicating that the library itself works unmodified between 2.1 and 2.2), but it failed due to a prelink map mismatch: the N1's froyo build expects the camera lib to load itself at location "XYZ" (in memory), as it was built that way for performance reasons, and works that way on the N1. However, the HTC library (different camera) does not load itself at the same location the N1 expects it (call it "ABC"), and was not stripped with the apriori prelink utility. So the framework refuses to load the library because it can't load it where it expects it should be loaded from.
I didn't try an AOSP 2.1 ROM yet, so it feasible that it may load it properly... However, due to the fact that the EVO has hardware that is not supported in Android 2.1 (FFC, 720p video, wimax, HDMI out, etc), HTC has rolled their own framework modfiications. If the camera lib requires any of those modifications (99% guaranteed, it *does*), the library won't be able to find those modified APIs, and will still fail.

Are any devs working on this?
-------------------------------------
Sent via the XDA Tapatalk App

TheBiles said:
Are any devs working on this?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Yessir. At work now but as soon as I get home I am going to recompile my AOSP build for the Evo and pray that it works. As Maejrep said I don't expect the camera to work (either front or back). I know 4g won't work. But I'm hoping I can get a basic build working and then go from there.

chuckhriczko said:
Yessir. At work now but as soon as I get home I am going to recompile my AOSP build for the Evo and pray that it works. As Maejrep said I don't expect the camera to work (either front or back). I know 4g won't work. But I'm hoping I can get a basic build working and then go from there.
Click to expand...
Click to collapse
I appreciate it! However, it sounds like the same things will be broken in that build as the Froyo build. Kind of disappointing, since I at least want the rear camera working. I don't care about MMS/4G/front cam.

TheBiles said:
I appreciate it! However, it sounds like the same things will be broken in that build as the Froyo build. Kind of disappointing, since I at least want the rear camera working. I don't care about MMS/4G/front cam.
Click to expand...
Click to collapse
Well we will just have to see. That's the thing. The cam theoretically should work however we don't know yet. With the front cam and the HD recording you never know what they did to the libraries. I've been thinking and I don't see why it won't work. I guarantee you 4g won't work off the bat. We might be able to hack that in though.

chuckhriczko said:
Yessir. At work now but as soon as I get home I am going to recompile my AOSP build for the Evo and pray that it works. As Maejrep said I don't expect the camera to work (either front or back). I know 4g won't work. But I'm hoping I can get a basic build working and then go from there.
Click to expand...
Click to collapse
If you need any help testing, feel free to contact me. I am very interested in an AOSP ROM, and I'd be more than happy to help out.

Any update on this, guys?

Will Froyo be available for polaris someday?

As you know, Google has published Froyo sources. And there is a froyo on SF already. I tried it on my POLA100. It installed and launched well. No wifi, bt, camera, external sound, gps, 3g... Nothing except phone—can receive and send calls. For my humble opinion it runs as fast as current speeded eclairs, even dialer runs almost immediately. Will it see future on polarises, or it's time to think about some native android device? =)

..................deleted

I dont know what you expect from our devs here.
As far as i know the source is only a few days old (23.june).
At this moment eclair is about to get fully functional camera, stable builds, battery life and a good competition between the roms.
So if you neeeed it that much it would be the best to buy a native android device that gets the latest versions first.
---------
So there will be a delay, it depends on how much changes must be done.
I hope that android will become more and more a real alternative for our device.
Since im using android on my polaris i think its like i bought a totally new device and im really happy about it.
Another thx to all devs, modders here ;D

dertester123 said:
I dont know what you expect from our devs here.
As far as i know the source is only a few days old (23.june).
At this moment eclair is about to get fully functional camera, stable builds, battery life and a good competition between the roms.
So if you neeeed it that much it would be the best to buy a native android device that gets the latest versions first.
---------
Click to expand...
Click to collapse
off topic, we're on enthusiastic dev forum

dertester123 said:
I dont know what you expect from our devs here.
As far as i know the source is only a few days old (23.june).
At this moment eclair is about to get fully functional camera, stable builds, battery life and a good competition between the roms.
So if you neeeed it that much it would be the best to buy a native android device that gets the latest versions first.
Click to expand...
Click to collapse
Sorry for possible intonation and meaning misunderstanding. Actually I didn't complain or tried make somebody do something. I appreciate all the devs for their work, It is really great challenge for them to port and adapt builds and eclair gets almost perfect lately. My question was actually just a question about possible future. There could be some hardware restrictions, incompatible drivers, who knows what else, right? So it could be no future for Froyo on polaris at all, that was my question about actually. But dzo has already answered it with uploaded froyo build which installed and launched on my polaris, so I am glad that there is possible oportunity for Froyo and polaris. And of course I am not agitating to get native android phones, and not laughing on enthusiasts here, forgive me my english. =)
iD

ah sorry too, got you wrong^^
sometimes hard if everybody is translating ;D
In the vogue thread they started the froyo development by incubus.
First build is on with bug, but he tries to get a build with most things working this night ^^
Faster than thought

[GINGERBREAD] Android 2.3 port from SDK for 32A/NR.

I made it for fun and it is NOT usable and will not be before we get official source
http://saraev.ca/signed_120810_223045.zip
working:
- data/radio (no incall microphone)
- wifi
not working: everything else
please do not report bugs. I know whats not working but can fix NOTHING for now

Good job. IMO these ports will be unusable for the next few months until cyanogen comes up with a release.
It was like that with eclair and later froyo. History tends to repeat itself.

Woot Woot, Hopefully once we get the source this can become stable. The magic lives on. Not many froyo builds I tried for the 32a werent that easy on battery life. Hopefully this turns out good. Hope the devs will work together to create a stable rom, instead of having their own builds with pros and cons.

If 2.3 ever starts working on 32A + NR, I am jumping ship asap! I miss vanilla android

eyegor said:
Good job. IMO these ports will be unusable for the next few months until cyanogen comes up with a release.
It was like that with eclair and later froyo. History tends to repeat itself.
Click to expand...
Click to collapse
There is no beginning no end. We are never be alone
HTC planning any updates in the future for "oldest" device? :/

eyegor said:
Good job. IMO these ports will be unusable for the next few months until cyanogen comes up with a release.
It was like that with eclair and later froyo. History tends to repeat itself.
Click to expand...
Click to collapse
I would have to agree with you except for I think I read on Cyanogen's twitter page that they will NOT be supporting first gen devices after CM6.1 which I assume meant NO ported 2.3 for us.
Hopefully I am wrong.

where is that quote? can't see it

good job!!!!!!!! hahahahaha

Did anyone1 tried on OR and cm Bcrook kernel???

i want to make a team for dev this rom to work full on magic..contact me..

nice hopefully it will fully work

Download does not work?

Really impressive work Hope to see this fully working.

what changes are needed for this to boot on 32b?

This is all well and good and I'll try it if I get my repaired phone back and can once again have a spare to play with.
However is it reasonable to expect this to ever be usable? We don't seem to be able to get a fully working 2.2 under the new radio so why would 2.3 ever get enough attention or drivers? I used 2.2 for a long time on the old radio but I really needed to use the new radio and have since gone back to 2.1 since it is now my daily driver again.
This will be great fun once I can put the Magic back to dev use.

I tested this on my g1, with a pershoots kernel over top so that it boots. And I was wondering how you got wifi to work? I tried replacing many things, but still get an error starting wifi supplicant daemon on logcat.
Just curious, not like I expect anything to ever become usable haha

studjuice said:
I tested this on my g1, with a pershoots kernel over top so that it boots. And I was wondering how you got wifi to work? I tried replacing many things, but still get an error starting wifi supplicant daemon on logcat.
Just curious, not like I expect anything to ever become usable haha
Click to expand...
Click to collapse
hm did you replace wlan.ko ? you should
also take a look at init.sapphire.rc:
Ive changed wpa_supplicant service a little because wlan_loader is not used as in eclair/froyo roms. my *wpa_supplicant.exec* loads the firmware and then starts *real* wpa_supplicant.
I realy dont have an idea whether firmware & tiwlan.ini are different for trout/sapphire. if they are you can edit wpa_supplicant.exec to load propper firmware files..
EDIT: this will not be usable untill we get gingerbrad sources published by google. then maybe cyanogen will do a build for us. I heard he will not support sapphire/trout anmore and if and *only if* it is true I will try to make a working one. I hope it isn't true and cyanogen will still suport our devices because he can do it better than me for sure

saibot64 said:
where is that quote? can't see it
Click to expand...
Click to collapse
twitter.com/cyanogen/statuses/8805829046177792
twitter.com/cyanogen/statuses/10393734621433856

*bump* any news, updates, anything?
found this
http://phandroid.com/2010/12/15/gingerbread-source-headed-to-aosp-soon-now-the-real-fun-begins/
Hopefully we can get a working build, dont wanna let the magic die.

Porting
Anyone done any work porting this? I'm currently working to compile this for my fender. Hopefully with the new radio. Which I've read doesn't work, so... anyone found a working one? I'm running eclipse to compile but if you'd like to help, let me know what you use and I'll send you what I've got.

[4.1] JellyBean Dev thread

I'll keep this post upto date with the last on the status of the build.
I've updated the manifest and it's inline with cm10. https://github.com/TeamICS/manifest_ics_cm/tree/jellybean
Builds are located here.
Nightlies are here or here
If you are not using firerats or don't know what that is make sure you use one of the "_shrunk" nightlies.
Currently the room boots. Lots of things work, here is what doesn't:
Bluetooth (pairing)
HW Acceleration (not likely)
Anything missing from CM10
Known issues are:
Headphone + speaker plays when headphones are in
<--previous-->
IT LIVES!
The build doesn't flash, but it successfully built. You need to use firerats as the system partition is over 173mb by itself. Not sure of optimal settings as it doesn't flash but we're getting closer.
Complete repo diff and repo status is here:
https://gist.github.com/3095432
Things disabled at build:
audioinwrapper from srec
libaac/libFDK
compiler-rt
maybe others.
Please note I haven't cleaned anything so it's quite messy and some stuff isn't pushed up to the repos yet. However it builds and that's a big step. It's off to bed and work tomorrow so I won't get a chance to work on it until the evening/friday.
Very close to a build, libaac is the only blocker, I've reached out to cyanogenmod guys to see if they have any ideas to fix aac, without completely rewritting the asm code. The problem is armv6j doesn't support smmul, clz and others in thumb mode, but armv7 (and the few devices with thumb2 on armv6t2) do. I don't have enough experience with arm asm to figure out how to rework the code to convert from 32 bit operations to 16bit operations. Also valgrind is not supported in armv6 (and can't be) so its disabled.
problems building aac, due to asm code, currently disabled a blocker
problems building srec due to audio issue, disabled
haven't ported camera
So far there is only two show stoppers, first is the audio because its changed again slightly. Shouldn't be too hard to work around. Second is cm team is still porting over all armv6 patches. Building on armv5 get stuck at audio, but armv6 get stuck on some asm code in bionic.[/sstrike] aac. AAC is being a really PITA!
<--Original Post-->
So I'm sure some of you guys are watching the I/O live. For those that aren't it's offical Jellybean will be 4.1. It's got loads of new and nice features. A lot of performance upgrades and the most important thing is the annoucement of the platform development kit. It's got all the low level details and apis need to port hardware to android.
Source code will be released in mid july, which is when the real development starts.
The hardwork everyone did on ICS, jaybob, matt, evervolv team and everyone from the G1, hero and eris forums laid the foundation. The main issue that has always held the heroc back has been the drivers. We have a great .35 kernel but with ICS a lot of the framework, that is hardware <-> software interactions changed. Thats what our audio issue was at first, and the camera. Audio was fixed by porting gingerbread patches and legacy audio support. The camera was tougher but eventually fell to the power of the community! The only two major things left are camcorder and full gpu acceleration.
The PDK will hopefully provide the last little bit we need to get acceleration working fully. It's no magic but from the keynote sounds like it might provide the information we need. Or it might not. Won't know until it lands on the web.
Overall jellybean is a step further from our old heroc's but there is still almost 20k devices officially running cm7! We obviously still have a community here who has yet to upgrade so the new goal is jellybean or bust!
As more information and sources are released I'll update the thread. I plan to port our TeamICS github account to Jellybean as soon as it's released. With luck everything will compile and be in the same boat as ics but only time will tell.

Thank you so much for posting this thread! I would have never knew about this. I'm willing to contribute to Jellybean although I'm with the Evo Shift now. I can make AOSP whenever the first jellybean Rom is released hopefully fixing some things!

count me in, i still have a few months on my heroc left until i upgrade
most of the fixes that happened from eligorom should be able to be applied to jellybean, as its basically the same rom as ics (from early reports)

I really need to add it to a signature when here in the HeroC forums, but:
My HeroC has been inactive on a carrier for the last year +, that being said, I still use the crap out of the device when I can, for a clock/alarm, music, GVoice and GrooveIP phone calls when home...
Basically, I would LOVE to see this thing continue to get updates, I still run CM7 over CM9 or ICS because for me, I see the most performance with CM7. Your talk of the PDK has me excited that I might see equal or better performance out of Jelly Bean on my HeroC!
TYVM, keep us updated

im pretty sure jellybean is going to run equal with ics for us, since hardware acceleration is still not available to us
i've been scouring the web for a solution, but no dice so far. we can turn off hwa, but i see no performance increase from doing so
from what i read, its going to take a module and some tweaks, so its going to take a dev with alot of time and knowledge on their hands to get us up to par with the adreno 200, which may never happen (although i hope it does, the heroc is awesome)

Thanks for sharing! Hard!

Not to sure if it can get 4.1. I'm having troubles getting it on the Evo Shift right now...

whoshotjr2006 said:
im pretty sure jellybean is going to run equal with ics for us, since hardware acceleration is still not available to us
i've been scouring the web for a solution, but no dice so far. we can turn off hwa, but i see no performance increase from doing so
from what i read, its going to take a module and some tweaks, so its going to take a dev with alot of time and knowledge on their hands to get us up to par with the adreno 200, which may never happen (although i hope it does, the heroc is awesome)
Click to expand...
Click to collapse
So will Project Butter have no effect on the Hero? I would think that it would at least have some effect in adding smoothness.
Sent from my SPH-D710 using xda app-developers app

I have to say I'm really exited about this. I ran ICS a few times on my hero with no problems, but I'm still using it as a daily even though I'm sure it would run fine. Ive been thinking about upgrading, but i don't see why. I really don't like any new phones. Their too big, no track ball, and i just simply don't like any of the new phones out right now. So all that being said... JELLYBEAN !!!!!

Source is out!
https://groups.google.com/forum/#!topic/android-building/XBYeD-bhk1o
edit: Not quite yet.
I'll update the TeamICS github with a new manifest for it as soon as it's out. Good news is that I happen to have tomorrow off so looks like I'll get a nice full day of playing around and trying to get it building. As with ICS I suspect most things will be broken, audio, dalvik, etc. So we'll have to port the ICS patches to jb. Once cm updates it's sources to jb, then we can switch back to them as they will have most of the patches in place already.

Shelnutt2 said:
Source is out!
https://groups.google.com/forum/#!topic/android-building/XBYeD-bhk1o
edit: Not quite yet.
I'll update the TeamICS github with a new manifest for it as soon as it's out. Good news is that I happen to have tomorrow off so looks like I'll get a nice full day of playing around and trying to get it building. As with ICS I suspect most things will be broken, audio, dalvik, etc. So we'll have to port the ICS patches to jb. Once cm updates it's sources to jb, then we can switch back to them as they will have most of the patches in place already.
Click to expand...
Click to collapse
I change my mind, i do think the hero can run jb BUT im not to sure about 5.0 or whatever they call it.. i upgraded to the evo shift and love it!! Just letting y'all know because this might be the last upgrade sadly said :/
Sent from my BNTV250 using xda premium

awesome, cant wait to see the first source build
ill help in whatever way i can, i just cant dl source because of my crappy internet connection (but if i can find someone to borrow faster internet from for a few hours ill most definitely dl source and try to contribute back that way)

Lol may take me a while before I can start porting for the hero again..
My current projects for the evo shift:
Motoblur
Porting Sense
4.1
3.0
Thats pretty much it =)

Well the cyanogenmod guys are making quick work of jellybean. Every hour more and more patches are ported over. Good news is we are very close to a build. Here are the current issue and workarounds.
Audio doesn't build, working on porting it over
problems with v6 in dalvik, changed to arm mode and ported ics *.S files
problems building aac, due to asm code, currently disabled
problems building srec due to audio issue, working on porting audio
haven't ported camera
Currently hungry and looking for lunch :fingers-crossed:

Shelnutt2 said:
Well the cyanogenmod guys are making quick work of jellybean. Every hour more and more patches are ported over. Good news is we are very close to a build. Here are the current issue and workarounds.
Audio doesn't build, working on porting it over
problems with v6 in dalvik, changed to arm mode and ported ics *.S files
problems building aac, due to asm code, currently disabled
problems building srec due to audio issue, working on porting audio
haven't ported camera
Currently hungry and looking for lunch :fingers-crossed:
Click to expand...
Click to collapse
So excited. My Hero has a sweet tooth.

Ha yeah to be honest the hero is getting more development on ics then my evo shift because y'all have aokp.. I need help with someone getting it to work on my evo shift.. We just had a ICS Kernel released so that better get some devs working .. Even though we lost A LOT to the evo 4g lte sadly said..

megaghostgamer said:
Ha yeah to be honest the hero is getting more development on ics then my evo shift because y'all have aokp.. I need help with someone getting it to work on my evo shift.. We just had a ICS Kernel released so that better get some devs working .. Even though we lost A LOT to the evo 4g lte sadly said..
Click to expand...
Click to collapse
I dont know about AOKP. Sure it was ported, but what work has there been done on it since? Honestly ICS ran super smooth for me on my Hero, especially coupled with V6SuperCharger. I was using LauncherPro on ICS to add to the smoothness, but the V6SuperCharger allows for smooth use of Apex.

yeah, it wasnt aokp that accelerated our cause, aokp has only been around for a few weeks for us so far. it was jaybob's ics aosp rom that really kicked things into gear. that and stritfajt with the camera fix, and the guys over at hero gsm for all the different tweaks and fixes, and mongoosehelix over at eris that kicked butt with evervolv for us. im sure im missing some people, but it doesnt make them any less important to the cause.
and last but not least all the testers and rom flashers that gave excellent feedback
i look forward to seeing jb run like ics

So the reason it's unflashable was because it's over the 170mb limit of the phone. Even though I'm using firerats there still seems to be a hard limit of the recovery and fastboot. The solution is to use a newer recovery, anything cwm 3.x or higher works. The dev phone I'm using had 2.5 cwm and that was the issue. Now it flashes fine. Only problem is for some reason sh didn't build, so now I'm looking to see why it didn't build.

we can cut out some cruft, like live wallpapers, and ringtones/notification sounds. live wallpapers dont work well on heroc anyway.
the sh error is boggling me too, supposedly its mksh symlinked as sh, which should have worked as thats how it is in ics roms.
im on the job lol
edit: yeah something is definitely rotton with those permissions, i checked them against an ics rom and everything checks out, but we still get the permissions error. i'm wondering if its the update binary possibly? ill do some checking and let you know one way or the other