My favorites | Sign in
Project Home Downloads Wiki Issues Source
How To: SPLs for Dream.
Updated Oct 8, 2009 by




About SPLs

This page contains information about SPLs for the HTC Dream (aka T-Mobile G1 and ADP1). What is a SPL? The SPL, or Second Program Loader, in conjunction with the IPL comprise a device's bootloader. Aside from bootstrapping Android, the bootloader also fulfills various diagnostic functions. One of these functions is the manipulation of data in the device's internal flash ram. Depending on the SPL installed, the user can apply a signed NBH file, flash nand images, and more. Note that the SPL is installed and operates independently of the Android build that runs atop it.

Currently there are three SPLs available. The G1 variant is the SPL that is installed in stock T-Mobile G1 phones. The Engineering variant is found in the Android Dev Phone 1. Finally, the HardSPL is a modification of the Engineering variant by cmonex, with additional hacker-friendly functionality. HardSPL is the recommended SPL.


The SPLs are packaged in the familiar format and install from the recovery console in the same fashion as other update files:

  • 1. If you are installing onto a G1, your G1 must have a modified recovery partition. If you have one of JesusFreke's Android builds installed, then you have a modified recovery partition
  • 2. Download the desired SPL zip file (SPL Downloads), rename it to and copy it to the root of your sdcard. As usual, remember to use a USB cable with a ferrite core and dismount your USB drive before disconnecting.
  • 3. Reboot the phone into recovery console and flash the update with ALT+S.
  • 4. To confirm it has installed properly, power on the G1 with END + Camera to enter the bootloader. When you are done, press CALL + MENU + END to leave the bootloader.
  • 5. To revert a G1 to its factory original SPL, simply use the G1 Original SPL.

HardSPL (recommended)

VER: HSPL10.95.3000
MD5: 6502af25b9e9fbe1322cc405559af1ca
SHA1: 59485b21f69acb6e9f70a4cd5ff4aefea722fc50

HardSPL is a modification of the Engineering SPL by cmonex. In addition to the functionality of the Engineering SPL, HardSPL also allows NBH files to be used without matching the CID (carrier ID) check. At the current time the main benefit of this is to allow European G1s flash American NBH files and vice versa. All other features and attributes of the Engineering SPL (such as the ability to flash the mtds from nand backup images) are present. Using the Nandroid backup scripts to create nand backups for this purpose is recommended.

Engineering SPL

VER: HBOOT-0.95.3000
MD5: 8008e01cb2c35e06b704e4dfb624ce4e
SHA1: d94f087b9eed8f59bc90d84c290ce475dbee07f9

The Engineering SPL is a custom SPL installed in devices intended for Android development. It has existed since before the launch of the G1 and is now available to the general public as preinstalled on the Android Dev Phone 1, the official development device sold by Brightstar Corp. This SPL, in addition to flashing signed NBH files, can also flash nand dumps through the use of the fastboot protocol (as defined in the legacy bootloader documentation). This is a convenient way to flash the mtd partitions and can be greatly useful in the event that an undesirable build of Android is advertently or inadvertently installed.

This SPL was first originally dumped from a G1 which dream_kill received as a replacement from T-Mobile by cmonex and JesusFreke. The file was released by Disconnect on his webpage.

G1 Original SPL

VER: HBOOT-0.95.0000
MD5: ae58b427b797707c453f3b3fa9d13c76
SHA1: aac5b75c348ee33c29aa24612d23a5e626a8c075

This is the original SPL which is installed in a stock G1. It is easily distinguished by the "trademark" red-green-blue bootloader screen which appears in many HTC phones. This SPL does not support the fastboot protocol and thus will not allow the user to flash nand backup images.

Before the leak of the TC4-RC29 and TC5-RC7 signed NBH images, users running stock RC30 and RC8 were unable to downgrade and install modified Android builds. On January 1st, 2008, xda-dev user chavonbravo leaked the aforementioned files, which allowed users to downgrade G1s through the original SPL. This SPL was dumped by damien667.

Comment by, Jul 11, 2009

I have tried to apply the HARD Spl but Ihave just bricked my new HTC Magic. I have downloaded the HARD Spl from the links in this page. Is there any chance to recover it? it is completely dead.

Comment by, Jul 11, 2009

Remove MAGIC from the heading, it is better. Since the SPLs here are for G1, I guess.

Comment by, Aug 25, 2009

Same here... not with this spl but similar I bricked my Magic... any advice besides get a new one ;)


Comment by project member, Sep 4, 2009

These SPL's are for the G1, the Magic is a different beast in regards to the SPL. Are you guys on the T-Mobile Magic? Also which SPL version did you have? i.e. 1.33.0006 or 1.33.0010?

Comment by, Sep 27, 2009

Is there any way to see which SPL and PPL I am running? I had an adventure with my phone when I found out JF stopped. I tried to go from JF to CyanogenMod? - This at the time was not a common problem on the forums so I decided to wing it. I now know that I had no need to go back to RC29 in order to change to Cyan4.1.1.

Long story short... I think at this point there is a conflict with my SPL and PPL. (I dont know if PPL is the official term for Primary program loader or not). Or a conflict with my Modversion ( and Firmware (1.6) Or my ect. ect.

Is there a resource that you know of that will allow me to view the compatibility of overall phone stuff?

It is on and running now. Earlier today my phone died and when I powered back on I got the G1 Original SPL tri color screen with the Serial0 line across the middle. Every now and then when I refresh it it would flash to a white screen and you could see for a SECOND "No image file" and it would revert back to the tri color screen with serial0 on it.

Okay. Battery out Home+Back takes me to my CyanogenRecovery? and I start wiping and Installing Any Zip on SD. Nothing was getting my phone off of SPL. Eventually I pressed my Camera+Power+Back after hooking it up via USB to my PC. It turned on and loaded Cyan amazing ROM. I was flabbergasted and I do not think that would ever work again.

I am not turning my phone off untill I think this through. Lol. I am not sure if It will load correctly or (I am 75% sure it will) go back to the SPL screen from H*ll.

I know Cyan is redoing everything ATM. I love the ROM and want to stick with it untill he dishes out barebone 4.1whatever. Maybe I should run Hero with HardSPL? I am a noob with a vocabulary so I apologize if my post is confusing, but I am so confused.

Here is all of the info that I know about my phone: Model#: Tmobile G1 Firmware Version: 1.6 Baseband Version: 62.50s.2017u_2.22.19.261 Kernel Version: Modversion: CyanogenMod?- Build #: DRC63 cm-recovery-1.4 And apparently I have the HBOOT-0.95.0000

Please help. I have been working at this for about a week now and I really need a experts opinion. Thank you!!!!!! Oh... By the way... Brick is when your phone is so fried that it wont turn on right?

Comment by, Nov 13, 2009

i put the in my sd card then go to the menu to load it. whatever its calle, i forgot. but it says it fails to open it because its not authorized or something. im using the original G1 SPL

Comment by, Nov 25, 2009

Hi pookeysi,

Similar problems. I get "No Image File!" everytime on boot. Unsure why and tried everything. To get around the problem I flashed boot.img to recovery partition and I can boot normally while holding the home button.

Total pain!

Comment by, Dec 26, 2009

So I wonder if there is a max number of times you can flash a new rom? I was not having any issues until just a few days ago when I decided to try out a 2.0. Everything flashed and booted up but when I decided to go back to my other rom my G1 decided it wouldn't boot past the "android" logo. Anyways after a full day of messing around with it I finally was able to flash the rom again, but only after going completely stock and then re-rooting. After I re-rooted and flashed the rom I tried flash an update to it and ended up with the same problem, a blank, back-lit screen after the "android" now I'm back to stock roms. It doesn't do me a whole lot of good as a paperweight LOL. I did narrow it down to having trouble after updating the SPL.

Comment by, Jan 3, 2010

drewlael, did you do a wipe of the dalvik cache and ext before flashing rom?

Comment by, Jan 18, 2010

hi every body , i am farhan from pakistan , i waz trying to update a hard-spl i think so the memory waz 872kb , after putting folder on my sd card i restart my mobile into cm-recovery-1.4.img and i was using build number jf1.5adp after doing a update my mobile is bricked i m trying to flash my mobile by pressing (camera+power) key but my mobile is not going into flash rom and after g1 t-mobile logo its not showing anything. plz help me some one i m very tens about it plz.

Comment by, Mar 12, 2010

How do I install a modified recovery partition? Every time I try to install anything from JF, it gives me signature errors. Any help would be appreciated as I am trying to install unsigned custom ROM with Fido APNs on a un-activated phone (if it's even possible or if it even makes any sense). The phone (used G1) freezes a couple of seconds (random, 10-30 sec) after booting and showing the activation screen. i've been running around for days looking for an answer. Thanks!

Comment by, Mar 31, 2010

I suggest ONLY writing the SPL using recovery IF you are moving between consumer/engineer matching pairs, i.e. 0.95.0000<-->0.95.3000 or 1.33.0005<-->1.33.2005.

Recent experimentation has proven that SPL BRICKS are caused by getting locked into BOOT MODE 3 -- boot to recovery. In this mode, the device will IGNORE boot-time signals, such as holding down the CAMERA button to enter fastboot. IF the recovery partition is UNABLE TO BOOT, you have a brick.

BOOT MODE 3 is triggered by writing radio/SPL images through recovery mode. It is because this is a 2-stage install, requiring the flag to be set in NAND. If you only use recovery to switch between matched pairs, then you are guaranteed that the recovery WILL be able to boot up.

Switching between non-paired SPLs, such as 0.95.x000<-->1.33.x005, you should ALWAYS use FASTBOOT. When using fastboot, the image is installed IMMEDIATELY without needing to set the boot-recovery flag, and so the device does NOT get STUCK in a recovery-boot with a possibly non-functional recovery image, hence NO BRICK.

Through experimentation, we have found that using this method allows radio/SPL combinations previously though to be GUARANTEED BRICKS to function happily, like using a 1.x radio image with 1.33.2005 SPL. As long as it isn't stuck in a recovery-boot, you will always be able to access FASTBOOT MODE and use that to write anything you like.

Comment by, Sep 7, 2010

I agree with DroidHacker? for best results on upgrading your spl, however never, i mean never try to flash the HTC Magic spl to a G1... now heres why, the "T-Mobile Magic" is the MyTouch? 3G 1.2 which uses different hardware (32A) i'm not sure if the same applies to the Sapphire SPL, in theroy since they use the same hardware (32B) that should work, but always ALWAYS try and find an SPL made for the HTC Dream or ADP0 those two are blood cousins to the G1

Comment by, Sep 10, 2010

Hi, I successfully istalled HardSpl? but why when I start in fastboot mode there is the warning "no image File"? everything seems works seamlessly so why this warning? On the other side I have got problems with flashing recovery images: I can't get a permanent flash (i.e. starting in recovery mode dosn't show the menu but a "danger signal") the dalvik-cache wiping is somewhat involved? thx.

Comment by, Jan 27, 2011

Hi, i just have one problem.. i just finished the whole setup for cyanogen6.1 on my G1 tmobile.. and i tought i did everything right. but it loops in the blue skating android screen.. can someone tell me what to do? tnx

Comment by, Apr 25, 2011

I cannot install HardSpl?..

I've downloaded the file, verified the MD5, renamed it to, and copied it to a freshly formatted 2gb SD card (fat32).

I used UniversalAndroot?-1.6.2-beta5 to root the G1

I enter the recovery app, press alt-s, and get a this:

E:No Signature (5 files) E:Verification failed Installation aborted

Please help!

Comment by, Jul 13, 2011

same problem

Comment by, Dec 1, 2011


Comment by, Mar 18, 2012

my htc magic magic went off and could never be powered on again let alone booting. in the middle of installing RUU_Sapphire_HTC_Europe_2.20.401.2_HTC_CH_release_signed_NoDriver? on the fon it went to 60% when off please can someboby help me am loosing my magic t-mobile.thanx

Sign in to add a comment
Powered by Google Project Hosting