[G1 Android Development] nicksen782:
Another of my long posts..

Watch out, this guy right here can type! :)

Let's see if I can add any additional ideas here. Watch out, I'm going to be rather raw (no, I don't mean swearing.) Anger isn't going to get us much further than where we already are.

It is accepted that the boot order *chain* is Radio>SPL>whatever.

It is accepted that the chain is broken because the Radio can not call/initialize the SPL

My Explanation/Opinion: My experience would be that the chain between Radio and SPL was broken. My understanding of this is that the Radio is supposed to call on the SPL but can not because the SPL is in a different place (memory address or perhaps just initialized/called differently.) This is the break. Both the Radio and the SPL exist but the Radio can not call upon the SPL.

Important question: HOW DOES THE RADIO CALL THE SPL?

Accepted: The newest radio works with the default SPL, the Engineering SPL and the hacked HardSPL.

Accepted: The newest radio ALSO works with the 1.33.2005 SPL.

Hypothesis: The new radio works with both the old and the new SPL while the older radios only work with the older SPLs because the new Radio supports both types of call/initializations for the SPLs.

Assumption: The new radio can employ the call/initialization methods that call the older SPLs and the new SPLs. (I am assuming that there are at least 2 different call methods.)

If this is indeed true then it could also be accepted that the SPL was changed (HTC?) and HTC (it's HTC making the radio images right?) started including compatibility for this change in the SPL call/initialization section of their newest radio images.

So, the SPL was changed and the radio's latest versions needed to be modified to support the change.

The older radios must have no programming for this change and thus hang on that SPLASH1 screen because there is no further (known?) logic in the Radio image to handle such a situation.

So, at this point any solution that involves invoking the SPL (if called from the radio anyway) is useless.

So, we can accept this then: We are therefore stuck at the Radio image part of the chain.

Question: What accesses are actually available from the radio image?

What systems of the Dream has it *woken up* at this point?

Does the Radio image touch the USB plug *at all?*

Does the Radio image touch the radios at all?

I WANT TO POKE THAT RADIO IMAGE WITH A STICK! I want to make that Radio image do SOMETHING. What is it doing with the SD Card, what is it doing with the USB port, BLUETOOTH, the actual GSM/3G radio in that thing? Is it *listening* for commands from the *mother ship?* I WANT TO BE THAT MOTHERSHIP!

We all know from our knowledge/experience with hacking that anything that *listens* can be *spoken too* and manipulated into giving us access to whatever *it* has access to. What does the Radio have access to at this point?

And I have yet to read anywhere about what that "Blue LED Mode" screen is that you get when you hold Power and the Trackball in. I think I did read about it having a bluetooth feature.

Bottom line: Let's find out what the Radio can offer us (in terms of ANYTHING,) Let's find out what that "Blue LED Mode" is and let's pull out all the stops and reverse engineer that Radio until we can more fully document what it actually is that is going on.

... my regret is that I can only speak in theory about this and not actually play a more hands-on role in this.