HTC Hero (Sprint) 2.1 ROM developer kit

[Jerry Hildenbrand]

I've de-compiled the official Sprint 2.1 release. Below are links to the radio, the boot.img, the extracted files from the boot image, a /system dump, and the system.img

None of these files are for flashing to your phone, they are only for ROM developers

Boot Image extracted files

System folder dump

radio image

boot image

system image

Tools - (32 bit unyaffs, signing keys, perl scripts to make and extract boot image)


Enterprising ROM developers could open an existing ROM built from the last leak, drop these files inside and overwrite whats existing, rezip and resign.

If the included unyaffs binary doesn't work on your system, open the terminal in the folder, delete unyaffs and run

gcc -o unyaffs unyaffs.c

to compile against your system.


Please don't link to these files directly. Just point people to this thread.

 

[Robchaos_]

awesome. Thanks Gbhil!

This is from the official from sprint.com, not their official from the leak posted on xda, correct?

Maybe you could clear something up for me too.
How could the "official" that was leaked on the 14th have the same md5 checksum but a different overall file size then the official sprint release from their website?

I am convinced that despite what some people say, there were some changes made in those last couple days.

I flashed a rom based off the leak and had audio loss within an hour, but then since my phone was going back to sprint for a warranty replacement in a couple days anyways, I took the plunge and just used the official RUU from sprint. I had no audio loss problems in the 24 hours I was running it.

No one on xda has felt the need to use the official from sprints website, all the roms are based off the leak from the 14th. Maybe they know something I dont. Is the md5 checksum based off the decompiled or is it applied after everything is compressed? Maybe they just used a different method to zip it all up that resulted in a smaller file size?

Also if I wanted to, I could just flash the boot.img to my phone, since we don't have source for 2.1 yet, none of the roms out there right now are really able to add special services like lowmemkiller or overclock unless they are using the source that was ported from the eris, right?

Thanks!

 

[beezy]

awesome. Thanks Gbhil!

This is from the official from sprint.com, not their official from the leak posted on xda, correct?

Maybe you could clear something up for me too.
How could the "official" that was leaked on the 14th have the same md5 checksum but a different overall file size then the official sprint release from their website?

I am convinced that despite what some people say, there were some changes made in those last couple days.

I flashed a rom based off the leak and had audio loss within an hour, but then since my phone was going back to sprint for a warranty replacement in a couple days anyways, I took the plunge and just used the official RUU from sprint. I had no audio loss problems in the 24 hours I was running it.

No one on xda has felt the need to use the official from sprints website, all the roms are based off the leak from the 14th. Maybe they know something I dont. Is the md5 checksum based off the decompiled or is it applied after everything is compressed? Maybe they just used a different method to zip it all up that resulted in a smaller file size?

Also if I wanted to, I could just flash the boot.img to my phone, since we don't have source for 2.1 yet, none of the roms out there right now are really able to add special services like lowmemkiller or overclock unless they are using the source that was ported from the eris, right?

Thanks!

The roms i put up have the custom lowmemory management and they are not built from the eris source.If you want to oc then you would have to use that source until htc decides to give us the new one.

 

[Jerry Hildenbrand]

Rob -

These are from the official at Sprint's site. The actual files are the same from the "leak" as they are from the "official". You're probably right that the compression ratio, or possibly the scripts used to auto-install in Windows are different.

What i would do is pull the actual kernel from this build, and add it to the boot image from Beezy's rom or from the option 3 version from last month. This way you can have a customized lowmemkiller setting even if the kernel itself isn't changed. This would be like using a 3rd party lowmemkiller app from the market, but will save some app space.

Warning -- your new Hero may show up already updated an non-rootable

 

[Robchaos_]

Rob -

These are from the official at Sprint's site. The actual files are the same from the "leak" as they are from the "official". You're probably right that the compression ratio, or possibly the scripts used to auto-install in Windows are different.

What i would do is pull the actual kernel from this build, and add it to the boot image from Beezy's rom or from the option 3 version from last month. This way you can have a customized lowmemkiller setting even if the kernel itself isn't changed. This would be like using a 3rd party lowmemkiller app from the market, but will save some app space.

Warning -- your new Hero may show up already updated an non-rootable

heh I would have been very upset if my new hero showed up with 2.1 preloaded. I got it a couple days ago with 1.5 on it! So that is weird, now I know that you have verified that the leaked and official release are the same, it is strange that I had audio problem with the last leak, and not with the actual ruu. Maybe its that even with a complete wipe, just flashing an update.zip doesn't always overwrite all the stuff it should, I've had some weird things happen after wiping and flashing before that obviously were left over from the previous rom. Maybe it was remnants from flashing the eris kernel that mess something up. I will check out beezys rom with the memkiller, and I will have to play around with the source you posted up!