I had just compiled froyo from android source and wanted to flash it
But apparantly I needed a specific spl when I did "fastboot flashall -w" (one of them being 0.95.0000 or whatever, too lazy to remember..but it was one that didn't support fastboot....which is dumb lol since fastboot is saying to use it)...
So I decided to install engineering spl
I had danger spl and the 2.something radio it needs
I decided to flash it from recovery
So really g1s are impossible to brick...if you flash radio and spls from fastboot not recovery
(Most of this knowledge is from a thread about g1s and spls and bricking that I'm too lazy to link to)
What happens is that recovery FORCES the g1 to boot to recovery on next boot...even if you press buttons
And with a mismatched radio/spl recovery will not start
So you have a brick...
Moral: use fastboot not recovery
Anyways so my solution...
I had a really messed up rogers dream that had a cracked screen and bad ribbon cables...
Pretty much everything was broken except for the motherboard...
Well I decided to try and put this rogers motherboard into my tmobile g1
Even booted up into the rom I used to have (biffmod) on the rogers dream before it got screwed up beyond usability
I am posting from my g1 with a rogers motherboard in it as I speak...post....
Moral 2: you can mix motherboards between dreams
One problem is that this ROM still has the keymap for the rogers dream and my home and call button don't work
Hopefully flashing a new rom it will detect the tmobile keyboard
Well this was fun...but I don't know if I'm gonna try to flash my aosp froyo or not again...
Comment please on how you manage to flash a compiled aosp froyo...maybe ill try flashing engineering spl again through fastboot this time
oh and I like this motherboards vibrate more:P
The old one rattled like crazy
So this actually a very win situation
I got Frayo (ROM) back on and everythings beautiful
^^That was actually copied from my post here
due to laziness:P
A few more things.
Apparantly Google Apps helps find the right keylayouts...well no...
Ok so point is I flashed a ROM and erased all google apps from recovery console before rebooting
My phone button, home button, and lockscreen didn't work. there was probably more, but thats the main things i noticed.
So I (grumbling) went and reflashed this time keeping google apps
I rebooted and skipped sign in (since the ROM had that option)
Everything was fine. So i went into Terminal Emulator and blasted away google apps with rm!
They were gone and everything was working perfect.
So somehow google apps controlled autodetecting my keyboard and all. Or it could just have been a freak accident. Who knows?
Looking up...I'm thinking that 99% of you will only understand 10% of what I said:P
One because it's messy and two because there are some Android specific and G1 specific terms
Oh well, those of you familiar with Android ROMs and stuff, discuss!:D