Database Info

Official HTC EVO 4G Source Released

The EVO 4G Source is listed on http://developer.htc.com
http://member.america.htc.com/download/RomCode/Source_and_Binaries/evo_4g-2.6.29-e1cabff5.tar.gz
Mirrors are here: http://forum.xda-developers.com/showthread.php?t=718136
maejrep said:
Other tips:
copy the built wifi and wimax modules over to /system/lib/mobules. "make" builds them automatically:
Code:
./drivers/net/wireless/bcm4329_204/bcm4329.ko
./drivers/net/wimax/SQN/sequans_sdio.ko
Click to expand...
Click to collapse
Steps I used to build and deploy a kernel built from this source: http://forum.xda-developers.com/showpost.php?p=7066759&postcount=91
You will need a development environment, steps I used to build a Ubuntu development environment in VirtualBox (stop at step 7): http://forum.xda-developers.com/showpost.php?p=6826894&postcount=100
I haven't tested this, but instead of copying over the default supersonic config (supersonic_defconfig), you can try this
netarchy said:
Alternatively you could cd supersonic-2.6.29-e1cabff5, adb pull /proc/config.gz && zcat config.gz > .config (with your phone hooked up via usb to snag the config it's currently using in case it's different from the default), and then do your make.
Click to expand...
Click to collapse

Vinny75 said:
The EVO 4G Source is listed on http://developer.htc.com
http://member.america.htc.com/download/RomCode/Source_and_Binaries/evo_4g-2.6.29-e1cabff5.tar.gz
Getting 500 server error right now, anyone able to pull it down
Click to expand...
Click to collapse
WOOOT !!!!

Wow, I honestly didn't expect it this soon after how long the Hero took . I can't download it yet either, must have JUST popped up.

OMG it's true I thought for sure this was a misleading title

it wont download >/..neither will the hero one

FINALLY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

This is great news. Now the devs can actually try all their fix as well as get custom kernel uv/oc without breaking anything. Can't wait for all those.

Same here hopefully up by tomorrow finally can get some proper ROMs going.

Awesome! Maybe the FroYo rumors are true as well...

No way! I just checked earlier today. Haha.
Sent from my PC36100 using XDA App

Oh my god, please someone compile Froyo w/ these drivers and make a Senseless UI!

mcjx said:
Oh my god, please someone compile Froyo w/ these drivers and make a Senseless UI!
Click to expand...
Click to collapse
+100000000

Is it alright for me to say 'F*CK YES'!?

Very exciting times.

wow... downloading now

Yep...download works now!

yep its working now

this is so sweet

It's downloading! I feel all tingly inside.

extracting now...........

[THINK-TANK] EB13 Source a Rebranded DKxx Source? : Cleaned Source Inside : (87.4 mb)

Searching through the EB13 source in /arch/arm/boot/ I came across three files of interest, victory_test_kernel.tar, recovery.bin and zImage, I ran over hear excited since I thought Sammy was throwing us a bone to get some custom kernels running early, but nevertheless in true Samsung fashion the files of interest come from October 1st of all dates, and seem to be before DK28. That's Sammy for you. You'll have to wait until Monday to get anything truly EB13.
-rwxr-xr-x 1 android android 5.5M Oct 1 08:22 victory_test_kernel.tar
Click to expand...
Click to collapse
This got me thinking, maybe Samsung is just had this source for a while now and this is the outcome of all their edits they've made through the leaked stages, this being the final product, anyways, here is a totally cleaned version of the EB13 source that takes half the time to download and is ready to be compiled with a few edits to victory_03_defconfig and build_kernel.sh.
Code:
Edited victory_03_defconfig to add initramfs source and cleaned
various aspects of unneeded files let behind by Samsung.
If your a dev coming from the DI18 source you might find it interesting to know that the default config is no longer ares_003_defconfig, but is victory_03_defconfig.
Click to expand...
Click to collapse

Yo didnt you say that you was working on MIUI and few other roms?How is that coming along?

bubby323 said:
Browsing the EB13 source and took a peak at /arch/arm/boot and found victory_test_kernel.zip. Flash with Odin, should work great on any DK28 rom, using rfs.
I also found recovery.bin which can be flashed to bml8 for the stock Samsung recovery experience you'll find which I assume is 3e. here
Click to expand...
Click to collapse
Do I get to keep root? How is the GPS? More questions that no one can answer this quickly...

u say for RFS?
What does this mean for ext? Is that going to have to be updated or something based on this new releases or no ?

honestly not to knock bubby but i wouldnt bother, wait like 40 mins there will be cwm3 friendly versions that keep root and have ext4/rfs etc etc

shabbypenguin said:
honestly not to knock bubby but i wouldnt bother, wait like 40 mins there will be cwm3 friendly versions that keep root and have ext4/rfs etc etc
Click to expand...
Click to collapse
Granted, this post was mostly for devs in the first place, just letting everyone know and uploading resources for those who dont want to dig through the source and wait for it to download.

yea i get that bubby, and i thank you for it
plus its good to let end users know there is work being done behind the scenes

shabbypenguin said:
honestly not to knock bubby but i wouldnt bother, wait like 40 mins there will be cwm3 friendly versions that keep root and have ext4/rfs etc etc
Click to expand...
Click to collapse
Ok thought so, btw do we still have to wait til monday, to get things really going like roms even with this?
I read elsewhere that the source doesnt help if we dont have the modem and kernal from the ota?

theres work on the kernel right now, may not be done fully but there is work.. the ota will give stuff like modem and the rom itself. dont be surprised to see test builds before thern tho

shabbypenguin said:
theres work on the kernel right now, may not be done fully but there is work.. the ota will give stuff like modem and the rom itself. dont be surprised to see test builds before thern tho
Click to expand...
Click to collapse
Thought so, i will wait til next week, maybe mid week and, probaly be an update for everything and and and update zip for the new modem.

The initramfs seems to be half-developed there is alot of junk added, and stuff *seems* to be alot missing comparing everything to DK28.

it an old build.. it was compiled on 10/2010 pre dk28 kernel
lock the thread

noobnl said:
it an old build.. it was compiled on 10/2010 pre dk28 kernel
lock the thread
Click to expand...
Click to collapse
HMM, meaning the source has old stuff in it??

noobnl said:
it an old build.. it was compiled on 10/2010 pre dk28 kernel
lock the thread
Click to expand...
Click to collapse
That's odd why would they include old stuff in the source. Junk has been left everywhere.

davidrules7778 said:
Thought so, i will wait til next week, maybe mid week and, probaly be an update for everything and and and update zip for the new modem.
Click to expand...
Click to collapse
<delete>..............

davidrules7778 said:
HMM, meaning the source has old stuff in it??
Click to expand...
Click to collapse
Excellent avatar! "Who ARE you....!!?"
Anyway, Seems that without the kernel and modem the source isn't the end al be all. I'm dying to get f'n TV out working on this phone though. I can continue to dream.

bubby323 said:
That's odd why would they include old stuff in the source. Junk has been left everywhere.
Click to expand...
Click to collapse
Sprint figures we need something to do? ;-)
Sent from Bonsai v 5.0.3

ZenInsight said:
Excellent avatar! "Who ARE you....!!?"
Click to expand...
Click to collapse
What are you talking about? Are you being an ass?

So is this an old source or is this thread a mistake its new EB13 source? I am so confused after reading this thread.

ryno502 said:
So is this an old source or is this thread a mistake its new EB13 source? I am so confused after reading this thread.
Click to expand...
Click to collapse
Sammy posted it as new eb13, however it apparently has some very old code in it...hmmmm.

Epic GB kernel sources! (11/22/11 EI22 keyfix kernel)

11/22/11 Update: Added "reboot bml8 recovery" patch for ROM Manager suppport.
11/8/11 Update: Updated keyfix kernel with the EI22 initramfs. Also, Samsung has placed the previous official (and now labeled EI22) source tarball on their opensource site.
10/24/11 Update: It appears that Samsung has removed the "official" Epic GB source tarball from their website. I've mirrored it for anyone interested in the original release. For anyone actually looking to build with the sources, you're probably better off using Rodderik's GitHub
10/19/11 Update: As everyone's found out by now, Samsung released official Epic GB sources last night. There's not that many changes to our device in the official source tree compared to the previous, but a few appear to be subtlely important (see abbreviated deltas). It still needs some work to get into a buildable state, but it does appear to work great on EH17!
I've updated most of my patches for GB, conveniently packaged together. I've also uploaded a new EH17 kernel that works on stock (rfs) EH17 ROMs and includes the keyboard fixes with optimized values, along with userdebug and kexec support. Feel free to give it a try.
Meanwhile Rodderik is updating his GitHub repo to include all these patches for folks to clone from, stay tuned.
Happy hacking!
So apparently when Samsung released the kernel sources to the Mesmerize's Gingerbread update a month-and-a-half ago, that source tree contained almost-buildable kernel sources for our device as well.
I've patched the sources (removed modemctl definition, added tfsr driver, compile right camera driver) to build for the Epic. I've also built a custom EH17 kernel combining these sources with the EH17 initramfs. It's essentially stock EH17 with ro.debugging=1, adbd always-spawning during recovery, and testkey signature verification. I'll get to porting over some other patches (like the dropped key fix) soon.
As for compatibility with EH17, the source tree itself appears to have been checked out on 8/30 and looks to include everything EH17 does. I ran "strings Image | sort -u" on both kernels to make sure there weren't any obvious strings/symbol differences between them. The ones that remain appear to be minor, but legitimate fixes.
Thanks to jt1134 & Rodderik for pointing out that the Mesmerize source released contained Epic code, and Tortel & ugothakd for testing.
GitHub repo, thanks Rodderik!
To build:
Grab SCH-I500_USCC_Opensource_Update3.zip SPH-D700_GB_Opensource.zip from opensource.samsung.com, extract.
Run "make mrproper" to get rid of atlas (Mesmerize) config junk.
Patch to complete Epic support.
Build with EH17 initramfs as usual, use victory_8G_defconfig for kernel configuration.
Mirror links:
Official GB sources: SPH-D700_GB_Opensource.zip (originally posted on opensource.samsung.com, since removed.)
Epic GB source patches: kernel-GB-3a-patches.tar.gz
Source-compiled, keyboard fix EI22 kernel: kernel-GB-3a.tar.md5
(URLs for Mesmerize tree patches removed, although they're still valid.)

Flashed this yesterday(11/13). Working good so far.
Edit: Oh, and first! Sorry iSaint
Sent from my SPH-D700 using Tapatalk

HAHAHAHA! Epic. I love you guys!

Yeah, um, I love you. <3 lol.

No. I was first. I tested it lol
[edit] actually, tortel was first. but that was before i got on board.

Hmmmm...who would of known part of our kernel source was right under our noses
Sent from my SPH-D700 using xda premium

It just occurred to me that, with this finding a lot of good can happen, as well as ICS tomorrow. Depending on timezone I should say.

Sweet. Hopefully this'll help cm7

Heart just stopped beating LOL!
What about stratosphere then?
Oh well nice work!
Sent from my SPH-D700

winning
bet samsung was just watching and waiting to see how long it took one of you/us to figure it out, lol.

this is wonderful news

Ceelos09 said:
Hmmmm...who would of known part of our kernel source was right under our noses
Click to expand...
Click to collapse
Ideally there would be one Samsung Android kernel source tree that would contain code for our device as well as all their others. However, I've been checking somewhat recently and code for Epic never appered in the GT-I9000 sources (which have been updated recently) nor in the Stratosphere ones.
It didn't occur to me to check the Mesmerize sources sooner, but as the only US device with an official GB release (still?) it shouldn't have been much of a surprise. It's also worth nothing that there appears to be GB sources for the Indulge in there as well. I'm not sure of their buildability though.

GREAT work mkasick.... everyone be SURE to thank him!

SWEET !!!

Exciting! Do the cm7 guys know about this, or is already used in the build we have?

Neckberg said:
Exciting! Do the cm7 guys know about this, or is already used in the build we have?
Click to expand...
Click to collapse
I'm not sure, JT helped Decad3nce with CM 7 though and they both hacked the EH17 kernel to work for this. So hopefully it's something Decad3nce can use.
He said he was moving so he probably won't be back until tomorrow.

Neckberg said:
Exciting! Do the cm7 guys know about this, or is already used in the build we have?
Click to expand...
Click to collapse
The main CM7 people are Decad3nce and jt and they haven't been on irc today.

this is exactly what we been needing...THANK YOU VERY MUCH mkasick!! You rock my friend!

Downloading now - going to see if I can compile a bootable kernel
Sent from my CyanogenMODed Epic

Neckberg said:
Do the cm7 guys know about this, or is already used in the build we have?
Click to expand...
Click to collapse
I believe JT was the one who discovered the Mesmerize sources were pertinent to us. He might've been able to compile something, but at least Rodderik was stuck on the missing tfsr driver without the right debugging bits.
I discovered this worked somewhat haphazardly when Rodderik mentioned the Mesmerize sources to me. They booted the first time with EH17 on SD, but wouldn't boot from flash. Since I was able to get it to boot off SD, debugging was a good deal easier.
In any event, it's a drop-in replacement for the current kernel used by the Epic CM7 build, so I'm sure they'll make good use of it sooner or later.
Actually what I'm curious about is if the reboot problems still persist with this. I haven't had one yet, but they haven't been a problem with stock EH17 on my device either.

[CLOSED]||Evervolv 2.2]

This thread is no longer active. Jomeister plans to continue work on Evervolv. He will open a new thread for that purpose.
Introduction
The purpose of this thread is to coordinate work on the AOSP-based Evervolv 2.2 ROM for Skyrocket (and its sister, T989).
Skyrocket is not an officially supported ROM by Evervolv, but we have fully integrated device and vendor directories in their tree. Therefore we get fixes from the main tree and also have the ability to push fixes to Evervolv's tree. This is something we could never do when we worked directly off the Code Aurora source.
Our desire is to give the dev community a single codebase to coalesce around. Hopefully, with more devs working on the same project, we can progress faster towards AOSP.
To build, follow the instructions here (choose ev_skyrocket-eng at the lunch menu):
https://github.com/Evervolv/android
Or, the short, short version:
Run "repo status" and make sure you have no local mods.
Run "repo sync" and make sure it completes without error.
Run "rm -rf out" to remove any old compiled stuff
Run ". build/envsetup.sh" to set up your environment
Run "lunch ev_skyrocket-eng" to select the target
Run "make -j4 otapackage" (adjust -j option to match your # of processors)
What works:
2D/3D graphics, hw accel of gui, bluetooth, gps, nfc, wifi, sdcard (int+ext), MTP/PTP over USB
What doesn't work:
audio, calls, camera, cell data, sms, anything else you can think of
Issues are being managed on Github:
https://github.com/Evervolv/android_device_samsung_skyrocket/issues
Want a ROM link?
Then follow the instructions to build a ROM! The point, at this time, is to get devs involved in the process. The ROM is not ready for anyone to try out or use at this point. There are many problems left to solve.
Want to help?
Are you a dev with a Skyrocket and a burning desire to get AOSP for your phone? Please, check out Evervolv and start debugging! The Github Issues link above is a great starting point.
Jomeister and RaverX3X graciously agreed to join forces here. We hope other devs join too!
Current Dev Contributors:
jomeister15
RaverX3X
topprospect
Credit and Thanks:
Xboarder56 for the original Evervolv Skyrocket device tree
romracer for the unsecure mods to the ICS kernel

Changes Log:
04/11/12: Posted succint build instructions
04/11/12: Fixed unstable-ness of GUI (link)
04/06/12: Build now boots on its own boot.img (link)

this is on 4.0.4 now?
Sent from my GT-P7510 using XDA Premium HD app

BaconStep said:
this is on 4.0.4 now?
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
yes because google has released 4.0.4 sources and ota updates to nexus.

wali01x said:
yes because google has released 4.0.4 sources and ota updates to nexus.
Click to expand...
Click to collapse
Sweet!
Sent from my GT-P7510 using XDA Premium HD app

Looks great, will try building/debugging when I get my Ubuntu box up again!
Sent from my SAMSUNG-SGH-I727 using XDA

I'll be helping out as well, just got me a T989. I was working on cm9, but I'll switch to this. Hope I can help.

This is obviously a stupid question, and probably not the place to be asking it, but it is going to be asked anyway so.. I understand what the device tree is, but why is it not possible to pull one from the existing ICS leak?

giant420 said:
This is obviously a stupid question, and probably not the place to be asking it, but it is going to be asked anyway so.. I understand what the device tree is, but why is it not possible to pull one from the existing ICS leak?
Click to expand...
Click to collapse
No stupid questions here. A fully compiled ROM like the ICS leak obscures a lot of the details about how to build the ROM from scratch. You have to reverse engineer a lot of what Samsung did to compile AOSP, plus how to avoid pulling in too much Samsung bloat code. Hope that helps.

more or less were going to keep as much samsung out of it as we possibly can . Yes u can kang in stuff from the leak but then that actually causes more issues in the long run then doing it right the first time ;P.

bsbachert said:
I'll be helping out as well, just got me a T989. I was working on cm9, but I'll switch to this. Hope I can help.
Click to expand...
Click to collapse
I think we as a community should still continue working on things such as CM9 and AOKP in addition to Evervolv, just to give people as many options as possible. The good thing that Evervolv device trees are very similar to those required by CM9 and AOKP, so with a few hacks here and there I'm sure we can get those building as well. I don't know about the other devs, but I definitely have enough time to collaborate on multiple projects, as long as I'm not the sole carrier.

ur killing me. I finally managed to get media server to stay up for msm8660 audio pulled from the leak with jos isotope a4 with some other libs and bins. acdb pulling audio policy was still a problem though.
This is definitely for the better though. I was uncomfortable with all those Samsung libs bins and blobs, especially after staring at them under IDA. like raver said it woulda been a nightmare later on.
This is great though, everyone on the same pile should make this go a lot faster.

im very excited for this.

What's IDA?
Sent from my SGH-T989 using XDA

Wow. This build is going to b epic! Can't wait guys. Nice work so far

LawStud3nt said:
What's IDA?
Click to expand...
Click to collapse
http://en.m.wikipedia.org/wiki/Interactive_Disassembler
crazy what u can find in those blobs. helps a lot for debugging though

all I know is I love evervolv on my nexus one its super baller... Thanks to all 3 of you guys
Sent from my SAMSUNG-SGH-I727 using xda premium

Any updates? Got ants in my pants waiting for this one!

softballjunkee13 said:
Any updates? Got ants in my pants waiting for this one!
Click to expand...
Click to collapse
Thanks for the interest.
We will post updates as they happen. Right now we are just trying to organize and get everyone on the same page.
Sent from my SAMSUNG-SGH-I727 using Tapatalk

topprospect said:
Thanks for the interest.
We will post updates as they happen. Right now we are just trying to organize and get everyone on the same page.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Click to expand...
Click to collapse
OK...enjoy the holiday as well!

MD3 OTA officially pulled per Samsung Open Source Release Center

[SAMSUNG OSRC COMMENTS DELIVERY NOTIFICATION]
♦ classification : mobile_phone ♦
♦ model name : SCH-I535_NA_JB ♦
Hello,
MD3 FOTA service was stopped recently because the sw version has data issue.
So we'll release the new binary fixed the issue soon.
And the opensource for new version will be posted.
Thanks.
Click to expand...
Click to collapse
Got this email a few minutes ago. Guess this explains why the source request was taking so long.

well good to know at least there on top of things
just now how long till it's fixed

LLStarks said:
Got this email a few minutes ago. Guess this explains why the source request was taking so long.
Click to expand...
Click to collapse
I was just checking out that site...so the link it has for MB1 for SCH-i535 is the full MB1 OTA you can flash basically?

No, you can't flash anything from that site.

Aaaaaaand this is why we want an unlocked bootloader, Verizon.
Sent from my SCH-I535 using Tapatalk 4 Beta

NinCaptain said:
well good to know at least there on top of things
just now how long till it's fixed
Click to expand...
Click to collapse
One day for Samsung to fix and 3 months for Verizon to test and approve.

LLStarks said:
Guess this explains why the source request was taking so long.
Click to expand...
Click to collapse
Source for what ? I'm new to Samsung devices, but not Android, and they only have to release source for the kernel. This recent update didn't include a new kernel, did it ? If Samsung uses other open-source code, I didn't know.

hallstevenson said:
Source for what ? I'm new to Samsung devices, but not Android, and they only have to release source for the kernel. This recent update didn't include a new kernel, did it ? If Samsung uses other open-source code, I didn't know.
Click to expand...
Click to collapse
I'm not sure what the OP is talking about . The radio/modem is not open source, its Verizon proprietary. So unless the bug is in the Samsung portion open source does not apply

hallstevenson said:
Source for what ? I'm new to Samsung devices, but not Android, and they only have to release source for the kernel. This recent update didn't include a new kernel, did it ? If Samsung uses other open-source code, I didn't know.
Click to expand...
Click to collapse
Kernel source, there's a new kernel with each update. At least there is when referencing the date it was compiled. I won't claim to say I read code/source but there's definitely a few adjustments between one compiled OTA kernel and the next.
DigitalMD said:
I'm not sure what the OP is talking about . The radio/modem is not open source, its Verizon proprietary. So unless the bug is in the Samsung portion open source does not apply
Click to expand...
Click to collapse
The modem being proprietary isn't the main concern. If what OP has posted is true, Samsung is just withholding VRBMD3 kernel source to push another OTA after which they'll provide kernel source for that newer OTA.
Llstarks just wants source and there's nothing wrong with that. Just means we have to wait a little longer is all.
Sent from my SCH-I535 using Tapatalk 4 Beta

Well, we wanted the source so we could figure out what was going on between the camera blob and the trust zone partition.
Camera wasn't loading with a MD3 tz.