Database Develop

Cingular 2.26 Aku2.3 w/a2dp FULLY LOADED *BETA* SCREWED ME

I have enclosed my link to the problems I have with this ROM upgrade. I am looking for suggestions other than bitting the bullet to purchase a new phone, or God help me, taking it down to Cingular to do a complete reflash if possible.
Any assistance is highly appreciated.
http://forum.xda-developers.com/showthread.php?t=276651&page=72
Regards,
jlsenter

jlsenter said:
I have enclosed my link to the problems I have with this ROM upgrade. I am looking for suggestions other than bitting the bullet to purchase a new phone, or God help me, taking it down to Cingular to do a complete reflash if possible.
Any assistance is highly appreciated.
http://forum.xda-developers.com/showthread.php?t=276651&page=72
Regards,
jlsenter
Click to expand...
Click to collapse
if you bother to read the posts u would know that the rom contain no boot loader.thats why you ipl i showing 1xxx
put the device into bootloader mode and reflash aofficial rom.
next time before posting post like this do some reading.
did anyone force you to flash this rom or any other?

faria said:
if you bother to read the posts u would know that the rom contain no boot loader.thats why you ipl i showing 1xxx
put the device into bootloader mode and reflash aofficial rom.
next time before posting post like this do some reading.
did anyone force you to flash this rom or any other?
Click to expand...
Click to collapse
Sorry faria, your wrong.....that is not what happened as you have blasted me; for as my ipl was not 1xx as you stated. I was able to go back into the boot and flash back to 2.17. ABTY, I do read and have been doing flashes of all sorts of electronics for more years that I hate to admit to. Don't be so presumptuous. Not every one can be righteous

if the rom read as 1.2 then its not the right rom

Have you tried
flashing an official rom that includes the bootloaders?
If you do this and then reflash with the rom you say screwed you your IPL should update.
This rom does not contain the bootloaders.
You may have to go buy a new battery (or borrow one that is charged at least 50% from a friend)
Start the device in bootloader mode while connected by USB by holding down voice tag and camera buttons while powering on. You should get the RGB boot loader screen with USB in the lower corner.
Flash a FULL 2.xx rom (preferably an official one from your provider), this should upgrade your IPL and SPL correctly. Then you can go back and re-flash this rom and all should be well.
From what you describe it looks pretty much exactly the same as happened to me earlier in the thread you linked. I had to go buy a new battery to get mine reflashed because I played with it so much with conflicting bootloader/OS/Radio versions that it went dead and would not re-charge in this state.
EDIT: Also if you IPL and SPL are different numbers this may indicate that you are not correctly CID unlocked (not 100% sure on this as it hasn't happened to me, but from what I read on these boards this is the impression that I get) If I were in your situation this is what I would do:
Downgrade to Button's 1.05 rom
run Lokiwiz02b and perform a CID unlock
Upgrade to a 2.xx carrier rom (pretty much everyone agrees to go with a carrier rom first)
Then upgrade to a 2.xx rom of your choice.

Zzan is putting you on the right path, yo do need to get your battery charged before you can flash though.
Also, just so you know when flashing cooked roms most of them use a hacked RUU that will always show the currently installed phone rom to be 1.2. This is so that you can freely flash between roms as the RUU will not normally let you flash to a lower rom version.
Regarding your comments to Faria, clam down. Your orignal post in the other thread is a bit jumbled and I can see where it is easy to think you might have been referring to IPL/SPL being 1.2 as you were not very specific.
When posting you will get a lot better help if you give as much info as possible and organize it clearly. For example say that the RUU showed you currently had version 1.2 Rom installed on your device then nobody thinks you are talking about IPL/SPL.
Finally, When you say things like "x's Rom screwed me" you're going to rub a lot of people the wrong way here (especially when the Rom is clearly marked as BETA). Remember that nobody forced you to flash the Rom and if you are as experienced at flashing as you say then you should have understood the risk you are taking every time you flash your device. Now you should to expect that risk to triple when you use anything marked as BETA. Maybe saying "Help, I'm having problems after flashing xxx Rom" would get you more assistance.
Take my advice with a grain of salt and realize that it is worth exactly what you paid for it so I'm not upset if you disregard everything I said.

jlsenter said:
Sorry faria, your wrong.....that is not what happened as you have blasted me; for as my ipl was not 1xx as you stated. I was able to go back into the boot and flash back to 2.17. ABTY, I do read and have been doing flashes of all sorts of electronics for more years that I hate to admit to. Don't be so presumptuous. Not every one can be righteous
Click to expand...
Click to collapse
this is what you posted;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cingular 2.26 Aku 2.3 Update - SCREWED ME
I guess I needed a reason to upgrade to the HP6925 as this update screwed me up big time. Everything appeared to be find during the update....just a very long time to reboot and setup. After setup and reboot again, very slow. The telephone function is completely gone. Icon is there, just nothing happens. Additionally appears to be processing allot of STUFF? as the processor seems to be being tasked as the screen taps are very inconsistent. I tried to restore to my 2.17 AKU2 ROM without success. The USB is no longer operative at all. I have tried to use the IR port, but it is too flaky, and bluetooth is bluetooth....no consistency; can't active sink here either. It no longer tells me about the battery, just empty information. No lights to even tell if it is charging in the cradle, or even just a power supply.
What is really bizarre, is when I tried to restore 2.17 for IR, it read the ROM as 1.2.....someone switch the LINKS load???? IR just bombs after it starts to initiate the load. Then have to go through recovery by removing battery.
Like pissing in a can with a 40mph wind :-(
HELP I HAVE TRIED ALL RESOURCES........lucky I backed up all my data, as I would have been SCREWED even more.
jlsenter
sorry. missread ,and i was not blasting you away.
but still u did not read the posts ,otherwize you would know how to restore your device.it was stated several times .
and since u stated that u been flashing all sorts ,im suprised u did not know how to restore you device. or was it the first time in this device?

Thanks Kyphur, Zzan, & Faria
Thanks for the suggestions; as it now make sense to some of anomalies that I saw. I did go back into the boot and re-flash back to 2.17 with success. The whole reason I started on this path to begin with was because 2.17 was not seeing my 2G memory card.....or should I say "not installed" to be more precise. Then after the ill-fated 2.26 install and re-flashing back to 2.17, the 8125 now recognizes the 2G memory. The 2.17 release has been very stable for me and will stay that way......., besides, my pre-ordered 8525 arrives this Friday.
Kind regards,
and personal apology to Faria if I was too FIERY

jlsenter said:
Thanks for the suggestions; as it now make sense to some of anomalies that I saw. I did go back into the boot and re-flash back to 2.17 with success. The whole reason I started on this path to begin with was because 2.17 was not seeing my 2G memory card.....or should I say "not installed" to be more precise. Then after the ill-fated 2.26 install and re-flashing back to 2.17, the 8125 now recognizes the 2G memory. The 2.17 release has been very stable for me and will stay that way......., besides, my pre-ordered 8525 arrives this Friday.
Kind regards,
and personal apology to Faria if I was too FIERY
Click to expand...
Click to collapse
all happy.....

faria said:
all happy.....
Click to expand...
Click to collapse
Group hug?

dcdivenut said:
Group hug?
Click to expand...
Click to collapse
tellytubbys...... lala...poo... ho **** cant remember the others.

I bricked my phone.

I mixed up my update files trying to update my radio and spl and installed the spl before the radio. And now it is stuck on the "t-mobile G1" screen. recovery won't work, fastboot won't work. Is there anything that I can do or is it gone for good?

Babyche43 said:
I mixed up my update files trying to update my radio and spl and installed the spl before the radio. And now it is stuck on the "t-mobile G1" screen. recovery won't work, fastboot won't work. Is there anything that I can do or is it gone for good?
Click to expand...
Click to collapse
lol......its gone....call tmobile and tell them your phone said it had an update and you said to update it and that you left it there for a while and when you came back it wouldn't get past that.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just another brick in the wall.

How did you mix up the ordering of the files? Sounds like you know which should come first...

Oh well. Thanks for the advice. I just call T-mobile and they are going to send me a new phone and give me a loaner phone until the new one arrives. Great.

I did know but I'm new to this rooting thing I just started Monday. I had my phone rooted but I messed up when i was switching roms. I didn't know I had to wipe everything when you switch to a hero rom. So I started over and picked the wrong spl from all the different files that I downloaded on my computer to do the root. Then combine that with all the different guides that I have been reading I was doomed. The funny thing is that as soon as I hit update I knew I messed up.

Babyche43 said:
I did know but I'm new to this rooting thing I just started Monday. I had my phone rooted but I messed up when i was switching roms. I didn't know I had to wipe everything when you switch to a hero rom. So I started over and picked the wrong spl from all the different files that I downloaded on my computer to do the root. Then combine that with all the different guides that I have been reading I was doomed. The funny thing is that as soon as I hit update I knew I messed up.
Click to expand...
Click to collapse
You don't need to reroot the phone to go to a hero ROM from another modded rom. You only need to flash the newest radio and then the special SPL (in that order)

Babyche43 said:
I did know but I'm new to this rooting thing I just started Monday. I had my phone rooted but I messed up when i was switching roms. I didn't know I had to wipe everything when you switch to a hero rom. So I started over and picked the wrong spl from all the different files that I downloaded on my computer to do the root. Then combine that with all the different guides that I have been reading I was doomed. The funny thing is that as soon as I hit update I knew I messed up.
Click to expand...
Click to collapse
Yessir the ol gut feeling.

that's the worst when you ****ed up and there is nothing that you can do to stop it. well unless you are like me and don't care and just do it anyway

Diceman4 said:
You don't need to reroot the phone to go to a hero ROM from another modded rom. You only need to flash the newest radio and then the special SPL (in that order)
Click to expand...
Click to collapse
I know but something happen when I went from a Cyanogen mod too a Drizzy hero rom to were it would work and kept boot looping (if that is a word) so since I don't know that much about flashing roms and all that I figured I would just start over and just install the hero rom from the beginning and that's were I installed the wrong update.

Babyche43 said:
I mixed up my update files trying to update my radio and spl and installed the spl before the radio. And now it is stuck on the "t-mobile G1" screen. recovery won't work, fastboot won't work. Is there anything that I can do or is it gone for good?
Click to expand...
Click to collapse
How would you know if you bricked your G1?will it be stuck in a certain logo it'll be stuck at?

will it be stuck in a certain logo it'll be stuck at?
hahahahahahaha yes. The very first one.

you will know your phone is bricked by the fact that it no longer wants to cuddle with you when your press power, or when it no longer gets in the mood when you press home and power, and you know all hope is lost and you will never get to the g-spot on your g1 when camera and power no longer does anything.
yes all the answers are in there lol

brick fixed brick again, SPL troubles

Y does my phone brick everytime i try to flash SPL? i know to do radio 1st, the SPL 2nd, then reboot, but when i reboot, it brick, this happened 5 times in a row, just today alone

It's not a brick if you can flash the radio and spl again. After flashing the spl you have to flash a new ROM because the spl removes the ROM.

make sure you flash the right spl for the right device, i flashed hard-spl to my 2nd gen dream and had a brick, 2005 spl worked on the replacement device

Fingerlickin said:
It's not a brick if you can flash the radio and spl again. After flashing the spl you have to flash a new ROM because the spl removes the ROM.
Click to expand...
Click to collapse
no believe me it was bricked, i couldnt do anythin, i just know how to fixed a bricked G1 thats all, but thanx 4 the info, i will try it now

djet229 said:
no believe me it was bricked, i couldnt do anythin, i just know how to fixed a bricked G1 thats all, but thanx 4 the info, i will try it now
Click to expand...
Click to collapse
Would you like to share how to fix a brick, there are many that would love this information.

Fix bricked g1
david1171 said:
Would you like to share how to fix a brick, there are many that would love this information.
Click to expand...
Click to collapse
all u have to do is unroot, have a spare SD card, format it 2 FAT32 just like in the beginning, then place the dream.nbh file on the root of the SD, the start the phone inn bootloader(u guys know this stuff) then when its done, u will have lost root access, but will still have a working G1 and can always reroot

djet229 said:
all u have to do is unroot, have a spare SD card, format it 2 FAT32 just like in the beginning, then place the dream.nbh file on the root of the SD, the start the phone inn bootloader(u guys know this stuff) then when its done, u will have lost root access, but will still have a working G1 and can always reroot
Click to expand...
Click to collapse
If you can get into the bootloader the phone is not bricked. Your terminology is incorrect. What you have is known as a soft brick.

rdfry said:
If you can get into the bootloader the phone is not bricked. Your terminology is incorrect. What you have is known as a soft brick.
Click to expand...
Click to collapse
Is that also known as a whiskey brick? HAHA

djet229 said:
all u have to do is unroot, have a spare SD card, format it 2 FAT32 just like in the beginning, then place the dream.nbh file on the root of the SD, the start the phone inn bootloader(u guys know this stuff) then when its done, u will have lost root access, but will still have a working G1 and can always reroot
Click to expand...
Click to collapse
The brick we are referencing is where the phone will not get into bootloader or recovery.

ummm... aren't you supposed to install a ROM after you upgrade your SPL? BTW, don't tell us you know what a brick is and then show that your phone is not bricked... I'm pretty sure if there was a fix for the brick it would be big news.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I had a brick, I held down the power button and the phone turned off and I could not get it to turn back on by holding the camera or home buttons. I finally found that the way to unbrick the phone was to hold down the power button and voila' it worked great
By the way I killed another G1, damn screen died out
***** and complained to t-mobile and got no where's with them, then I found the execitive custumer's relations # within 10 minutes they had me able to go get a brand new one at a store

gridlock32404 said:
I had a brick, I held down the power button and the phone turned off and I could not get it to turn back on by holding the camera or home buttons. I finally found that the way to unbrick the phone was to hold down the power button and voila' it worked great
By the way I killed another G1, damn screen died out
***** and complained to t-mobile and got no where's with them, then I found the execitive custumer's relations # within 10 minutes they had me able to go get a brand new one at a store
Click to expand...
Click to collapse
whoa i need that number

hjlow said:
make sure you flash the right spl for the right device, i flashed hard-spl to my 2nd gen dream and had a brick, 2005 spl worked on the replacement device
Click to expand...
Click to collapse
somebody can explain what is that ?? which device can I install hard SPL ?

I would like some clarification too... Last night I tried rooting my Rogers HTC Dream with the step-by-step guide using CyanoGen Mod, but on the very last step (Where it should have booted back into normalcy), it just stayed at the Rogers logo forever.
I don't think it's entirely bricked as I can get into the SPL thing (That's where you can do 'Fastboot USB', right?). I'm not sure how to get it back to normal though, I tried doing 'fastboot boot recovery.img' while the phone is in the Fastboot usb screen, and it reboots but it just sits at the Rogers logo again.
Is this thing bricked, or do I have options?

Okay, I did some more reading and now i understand a bit better...
What I have access to is the Bootloader, but I can't seem to get into the SPL. What steps do I need to take to get it back to working condition? I have a Rogers HTC Dream and I must have messed up when trying to apply the Cyanogen ROM

Holy Crap! A way to fix a Brick????!!!!!!!WOW!!!!!!!!
Hey if there's a way to fix a brick let me know cuz WOW! I would have gotten further with the last G1 I sent back to T-Mobile if I could have fixed it myself! Check your statements as you pertain it to being "BRICKED." BRICKED is not going past the T-Mobile G1 screen or not starting up at all! These newbies need to get it right! WOW! This one did give me a GREAT laugh today! This just made my day better now that I've had a good laugh!

can you get into recovery after the spl? home+power

jonzina said:
somebody can explain what is that ?? which device can I install hard SPL ?
Click to expand...
Click to collapse
Only the t-mobile g1/ADP1
rogers from canada will brick
use 1.33.2005 for rogers. its safe on that phone
the spl is the bootloader (well just think of it as the same)
in command prompt, when you type
Code:
fastboot devices
can you see your phone?
Also, if you booted off of the HTC recovery rom, your actual recovery is being replaced on each boot.
Search for the
"flash_image not found" thread in this section and look at sleepy_sanchez's method to remove the script that replaces the recovery.
EDIT
fastboot erase recovery
fastboot flash recovery *name of recovery*
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
try that
making sure the images are in the same folder as the fastboot
if that doesnt work, try
http://forum.xda-developers.com/showthread.php?p=4677631#post4677631

desperate plea for help

if anyone here who lives in Toronto ON that can fix my HTC rogers dream , please let me know im willing to pay in beer or straight cash, long story short
i get htc dream with 1.5 , i want to update to 1.6, my friend makes recovery image and puts on nandroid v2.2 and at bottom it says " build: cyanogenMod V1.4 + JF", console doesnt work, and he tried flashing via the update.zip , and since then its never gotten past the rogers splash screen. on the camera+power menu it shows the following
DREAM PVT 32B SHIP S-ON d
HBOOT -1.33.0009 (DREA21000)
CPLD-4
RADIO -3.22.20.17
May 12 2009 , 17:05:58
HBOOT
<SEND> fastboot mode
me and Ace 42 spent the last 2 days trying to fix this problem, we tried updating the "dreaimg.nbh " or w.e its called file and then we tried loading rogers htc dream roms found on this website, and it still wouldnt boot... im fearing the worst , as i cant get into console, the screen goes from
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
to just the black background with the android logo and the writing " build cyanogenMod v1.4 + JF" and its unresponsive, only way is to pull battery,
also now the fastboot menu says
DREAM PVT 32B ENG S-OFF
HBOOT -1.33.2005 (DREA21000)
CPLD-4
RADIO-3.22.20.17
APR 20, 2009 15:30:43
HBOOT
<SEND> fastboot mode
also the icons on the bottom are skateboards with the little green android guys ( before and after hboot changed)...
ok so now ace42 told me he thinks the only option left is to flash the radio, but he said theres a 50/50 chance it might permanently brick the phone since its downgrading ( i think i dont exactly remember what he said) ill get him to chime in here and say his side of this whole situation.
honestly i just want android 1.5 back, no fancy custom stuff, OR android 1.6 and as long as it works normally ill be quite happy and never touch this updating fiasco every again....

Looks to me like you flashed the danger SPL without updating to the 26I radio. I am pretty sure you own a paperweight.

please.. i dont want to hear that

ummm
you are gunna have to do this
http://forum.xda-developers.com/showthread.php?t=491350&highlight=stock+firmware
then after you do that, just either go to your settings and search for updates or root and get a CM rom

After re-reading you post, I am really not positive. I didn't notice you were using a rogers phone. The radio might be different. Hopefully someone with a rogers phone can confirm their radio with yours.

do you have another nandroid backup? if so... when you press camera+power, go into fastboot mode and fastboot flash system.img...etc, if not use fastboot to flash another update.zip

So after checking out some sigs from other Rogers users...they have the 26I radio with the 1.33.2005 SPL...so yea...I fear the worst for you. Good luck tho.

nandroid backup of the OS when the phone was working?? no i accidentally pressed the backup choice and it overwrote the original recovery with a nonworking rom

sockpuppet4 said:
So after checking out some sigs from other Rogers users...they have the 26I radio with the 1.33.2005 SPL...so yea...I fear the worst for you. Good luck tho.
Click to expand...
Click to collapse
, this is a ******* nightmare.. i dont have money for a new phone and i needed this phone for work...
cant i update or change SPL then change radio?
wait, my radio didnt change at all from the beginning to right now???
just the SPL... :|

32adream said:
, this is a ******* nightmare.. i dont have money for a new phone and i needed this phone for work...
cant i update or change SPL then change radio?
wait, my radio didnt change at all from the beginning to right now???
just the SPL... :|
Click to expand...
Click to collapse
Sorry man, it happens. Good luck to you. Maybe try and brick it all the way and get your warranty fix.

cant.. bought it second hand...

*checked spl & radio versions
*attempted to flash cyan mod
*tried micro hero
*tried regular rogers build by enomther
*console but was unable to acess
*was gonna try to flash dreaimg-rc29 but it contains older radio

ok so you can get into recovery and fastboot?

yes i can get into recovery and fastboot.

lol... chill.. this is NOT an spl brick. Sounds like your recovery image could be corrupt from a bad flash, but that's perfectly fixable. You know how to use fastboot from your pc, right? If not there are plenty of guides around here.. use fastboot to flash either cyanogen's recovery or amon_ra's.. from there, follow instructions to install CM 4.2 here: http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_Versions
Just don't flash that old radio.. thats not a 50/50 chance of brick, that's 100% cast-iron brick.
ITT: n00bs scaring n00bs.

ace42 helped me alot, i dont think he is a noob
ok from what you said, im gonna need step by step instructions on how to access fastboot from my pc. :| goldenarmz do you have gmail chat or msn??

I can't do a live chat atm, but I'm feeling helpful so I'll try to talk you through it here.. I'm just reading up on the rogers dream rooting process to try and see where you're at.
While you wait, download and indstall the android 1.6 sdk from here:
http://developer.android.com/sdk/index.html
http://developer.android.com/sdk/installing.html
You don't need to download eclipse or set up the adt, just get the SDK installed with the tools path defined.
I'm assuming you're on windows btw?

yep, windows xp

OK I think I can see where you've gone wrong. You need to have the rom you want to flash on your sdcard (im assuming its still there from your earlier tries), and you need to download givemeroot.zip to your pc:
http://www.stevebirstok.com/android/givemeroot.zip
Let me know when you've got the SDK installed and we can proceed..

i was on the other computer, im doing all this from my laptop since the usb ports are right in front of me, i actually do have the sdk, and i dont think i have the rom i want . i just want a plain android 1.6 thats optimized for the htc dream. and now its updating the sdk

Absolutely bricked?

Story, in key point format:
-Just moved, no internet at home yet (in fact I've been using tether since I only check e-mail and use FB anyway)
-At cafe... Already closed, but they agreed to let me stay about 5 minutes past closing time, no time to search. NO N00B/"SEARCH FIRST" COMMENTS PLEASE.
-Don't have any old phones
-Just got a new girlfriend and didn't think much about emergency expenses and spent most of my $ on wine n' dine with her (but at least I got some worthy "dessert", but that's another story).
-Just lost my job a week after meeting her (I stayed up all night, eventually gave into a "food coma" [see above] and came into work late) LOLOL... Woulda had a new phone budget if I was around for another 2 weeks, but noooo....
Anyway:
-Tried to install CM5 onto G1
-Installed it with the CM bootloader (or something like that, it had an orange font)
-Downgraded to RC29, successfully loaded AMON_RA
-Installed DangerSPL, rebooted per the instructions
-Stuck on the boot screen for almost exactly half an hour (5 mins after 8PM until 8:30PM), said "WTF" and pulled battery out
-According to the first few search results, my phone is "fully bricked", as in end+back/home/camera/whatever doesn't work (although when you push end+trackball the blue light turns on, whatever that means)
With that in mind, what should I do? Any hope?

Hmm well Im not an expert like most of these other guys by ANY means, but in my experience I've learned that removing the battery during a percieved "hangup" is a sure fire way to brick a G1. Trust me Ive done it, not fun.
If you can make it to the recovery screen somehow, theres still hope. On the Cyanogen Wiki, I believe theres a type of method for reflashing a rom, by booting while holding the camera button. I would recommend researching that.

Pulling the battery had nothing to do with it. The combination of 1.33.2005 SPL + 1.x radio is incapable of booting any known kernel. The misc partition was configured to boot-recovery, which overrides any key presses. So when it starts up, it figures it should launch recovery, which boots far enough for the SPL to think that its booted (otherwise it would force you into fastboot).
Your only hope right now is to jtag the thing and either wipe your misc partition or load a compatible SPL that allows fastboot.

You forgot to flash a compatible radio!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

BoomBoomPOW said:
You forgot to flash a compatible radio!
Click to expand...
Click to collapse
The funny thing is that if he had done the first sensible steps of installing an engineering bootloader (one with fastboot) and wiping the recovery partition (to force it into fastboot when recovery failed due to being wiped), he'd be fine.

DAMNITS!! I only read the "steps" portion of the instructions on the Cyanogen Wiki, which didn't even include the "radio" portion of the equation (I edited it just to avoid other people having the same problems).
lbcoder said:
Pulling the battery had nothing to do with it. The combination of 1.33.2005 SPL + 1.x radio is incapable of booting any known kernel. The misc partition was configured to boot-recovery, which overrides any key presses. So when it starts up, it figures it should launch recovery, which boots far enough for the SPL to think that its booted (otherwise it would force you into fastboot).
Your only hope right now is to jtag the thing and either wipe your misc partition or load a compatible SPL that allows fastboot.
Click to expand...
Click to collapse
Jtag? Sounds horribly hard; baking it and taking out a ROM chip? Wow.
Acecalibur said:
...by booting while holding the camera button. I would recommend researching that.
Click to expand...
Click to collapse
"-According to the first few search results, my phone is "fully bricked", as in end+back/home/camera/whatever doesn't work"
lbcoder said:
The funny thing is that if he had done the first sensible steps of installing an engineering bootloader (one with fastboot) and wiping the recovery partition (to force it into fastboot when recovery failed due to being wiped), he'd be fine.
Click to expand...
Click to collapse
Well, I was (somewhat) following the steps of the Cyanogen wiki.

EdWaRdW818 said:
Jtag? Sounds horribly hard; baking it and taking out a ROM chip? Wow.
Click to expand...
Click to collapse
Your information is wrong. There's no baking, there's no removing chips. There is just interfacing with the board. If you're handy with a soldering iron, its a cakewalk.
Well, I was (somewhat) following the steps of the Cyanogen wiki.
Click to expand...
Click to collapse
Finding all your information in one location? What makes you think that your SINGLE SOURCE of information was accurate or correct? For all you know, it was written with the INTENTION of screwing you up.