Database Develop

Bricked G1

right i know how i bricked my G1
did spl before radio .. so the outcome is basiclly it hangs on the screen thing
i passed the phone down to my little brother so hes been using it for some time i ain been on the g1 scene for quite some time until yesterday he started ranting on bout me upgrading his system to the Hero ports
my main question was is there a way to recover this problem
or am i going to have to go tru my friends at t-mobile
thanks in advance

1) You posted in the wrong forum. How is this post in way Android Development?
2) Learn to use periods. It's hard to understand what you are trying to say.
...So you bricked your g1?
Sorry, nothing can be done.

shaji007 said:
right i know how i bricked my G1
did spl before radio .. so the outcome is basiclly it hangs on the screen thing
i passed the phone down to my little brother so hes been using it for some time i ain been on the g1 scene for quite some time until yesterday he started ranting on bout me upgrading his system to the Hero ports
my main question was is there a way to recover this problem
or am i going to have to go tru my friends at t-mobile
thanks in advance
Click to expand...
Click to collapse
Shaji... 1st off how is your little brother using a "bricked" phone? If it is bricked it can't be used let alone have the ROM updated to the Hero ROM's. Also there are several threads over in the " Dream android development " that should provide you with PLENTY of information that you seek... good luck with T-Mobile...
peace

...tell T-Mobile you got an OTA update and phone never booted past the first screen after. You're phone is bricked ,get a new one.

shaji007 said:
right i know how i bricked my G1
did spl before radio .. so the outcome is basiclly it hangs on the screen thing
i passed the phone down to my little brother so hes been using it for some time i ain been on the g1 scene for quite some time until yesterday he started ranting on bout me upgrading his system to the Hero ports
my main question was is there a way to recover this problem
or am i going to have to go tru my friends at t-mobile
thanks in advance
Click to expand...
Click to collapse
I did the same thing the night Haykuro came out with all his new stuff for that. I flashed SPL before radio, but I was able to fix it. I'll pull up the email I worked out with him, PM me for it.

Disconnect usb, take out the battery and plug it back it, connect usb, boot the phone into the recovery mode, go to the console.
Enter then type this: echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
You now can access to ur sdcard from your computer, download a rom, change it to "update". Reboot the phone again, now try to wipe and install the update. After you install the update, flash the radio first, then the SPL. Let me know how it works out for you.

thanks for all the information people

@shaji007 Your post is quite confusing, can you tell us what you did in order? Can the phone get in to recovery (power+home) or the bootloader (power+camera)?
@phuthanvinh If you brick you can't get in to recovery.
@lukekirstein You know how to bring bricked G1's back to life? This I gotta see...

right basiclly
i followed the guide how to downgrade root n hack etc
did all that
then upgraded to one of JF builds
then i was going to install the hero ports that have been flying around
however this is my fault i wasnt really concentrating and i upgraded the spl before the radio
so yea its bricked on there
i just thought xda might have a way of fixing it back up
getting it replaced with t-mobile is of course no problem but i dont want to go through the hassle

lukekirstein said:
I did the same thing the night Haykuro came out with all his new stuff for that. I flashed SPL before radio, but I was able to fix it. I'll pull up the email I worked out with him, PM me for it.
Click to expand...
Click to collapse
yea okay I don't believe you...If haykuro was able to fix it why hasn't he posted a fix? No why havent YOU posted a fix?

shaji007 said:
right basiclly
i followed the guide how to downgrade root n hack etc
did all that
then upgraded to one of JF builds
then i was going to install the hero ports that have been flying around
however this is my fault i wasnt really concentrating and i upgraded the spl before the radio
so yea its bricked on there
i just thought xda might have a way of fixing it back up
getting it replaced with t-mobile is of course no problem but i dont want to go through the hassle
Click to expand...
Click to collapse
Right, yeah, you're screwed. Just tell tmo that the update bricked it, but don't say bricked, just act dumb
I wouldn't hold out much hope for lukekirstein's unbrick method that no one has over heard about before...

Problem just arrived

I was trying to load up my gf's G1 and I had a cyans newest rom and pretty much all was working good. Now my friend decided to try the boot screen flasher to load a custom boot image and well it was not working so he said that it was the SPL and I told him that not to worry about it...But he did it anyway and now when the phone loads it stays on the G1 screen. I tried to load into recovery (home+power) to see if I could nandroid but no dice. Any Ideas...I would like this to work by time she gets home as I am creating a playboy theme for her phone.
P.S. I decided to let my friend know not to touch my phones by a nice punch in the arm
P.P.S. I know I should search for this but I am time crunching thanks to my friend and need to get this working again for her ASAP

I would give him a little more than a punch.... if he flashed the SPL
and you cant get to the SPL (Cam+Power) or recovery (Home+Power)
then your phone is bricked....
just so you know... the boot screen flasher has two options..one for the standard/engineering/hardspl and another for the haykuro SPL

Yeah When I do camera power I still get the G1 screen

Sorry but this is a brick. Not fixable.
Try not to actually kill your friend, but he definitely deserves a serious beating.
There is one thing that's worked on a few magics/sapphires, but I don't think anyone's had it work on a g1.. you might as well give it a try since it's literally your only shot: You need to have fastboot drivers already installed and working on your pc and a copy of the engineering or hardspl.. plug your phone in by usb but don't switch it on and execute this command:
Code:
fastboot flash hboot hboot.img
You should get the message "Waiting for device...", now hold [camera] power the phone on and hope. If it doesnt work, try pulling and reinserting the battery a few times. The idea is to get fastboot to recognise the phone before it trips up and start the flash, but as I said I don't know if this has ever worked on a g1. It has been reported that this is more likely to work with linux than windows as it reacts to usb devices much more quickly.

goldenarmZ said:
Sorry but this is a brick. Not fixable.
Try not to actually kill your friend, but he definitely deserves a serious beating.
There is one thing that's worked on a few magics/sapphires, but I don't think anyone's had it work on a g1.. you might as well give it a try since it's literally your only shot: You need to have fastboot drivers already installed and working on your pc and a copy of the haykuro spl.. plug your phone in by usb but don't switch it on and execute this command:
Code:
fastboot flash hboot hboot.img
You should get the message "Waiting for device...", now hold [camera] power the phone on and hope. If it doesnt work, try pulling and reinserting the battery a few times. The idea is to get fastboot to recognise the phone before it trips up and start the flash, but as I said I don't know if this has ever worked on a g1. It has been reported that this is more likely to work with linux than windows as it reacts to usb devices much more quickly.
Click to expand...
Click to collapse
fastboot only works in the spl though. the radio never calls the spl if the radios outdated.
also, why would you want to send haykuros spl back on the phone, when thats what caused it to brick in the first place.
can you link me to where the magic people got it to work? because i doubt their brick is the same as this

B-man007 said:
fastboot only works in the spl though. the radio never calls the spl if the radios outdated.
also, why would you want to send haykuros spl back on the phone, when thats what caused it to brick in the first place.
can you link me to where the magic people got it to work? because i doubt their brick is the same as this
Click to expand...
Click to collapse
to the first part of your statement: thats our best guess but noone REALLY knows, so if you dont want off the wall, maybe fix your phone solutions, then go else where
and i do agree that using HARDSPL versus haykuro would prolly be better idea, but its worth a shot nonetheless, depends all on where the fastboot code exisits and where exactly the phones hang, if you have some specific details that the rest of us are missing then do SHARE
and from what ive heard you'll need to be running linux for the reasons above (windows being slow as balls to do anything, and "security" {hostility} protocols applied to the usb bus)

B-man007 said:
fastboot only works in the spl though. the radio never calls the spl if the radios outdated.
also, why would you want to send haykuros spl back on the phone, when thats what caused it to brick in the first place.
can you link me to where the magic people got it to work? because i doubt their brick is the same as this
Click to expand...
Click to collapse
That's what I thought til I saw this thread too, but the magics were spl bricks or I wouldn't have even posted it You're right tho, I meant to recommend hardspl, not haykuro's.. slip of the fingers. I've edited the post.
I'll try to find the magic thread again.. I can't quite remember where it was though..

ESKIMOn00b said:
to the first part of your statement: thats our best guess but noone REALLY knows, so if you dont want off the wall, maybe fix your phone solutions, then go else where
and i do agree that using HARDSPL versus haykuro would prolly be better idea, but its worth a shot nonetheless, depends all on where the fastboot code exisits and where exactly the phones hang, if you have some specific details that the rest of us are missing then do SHARE
and from what ive heard you'll need to be running linux for the reasons above (windows being slow as balls to do anything, and "security" {hostility} protocols applied to the usb bus)
Click to expand...
Click to collapse
what do you mean by no one already knows? We do know. i dont think youve been following xda very closely.
read the the threads that relate to the spl because all that info is already shared. Heres the summary
IPL>SPL>Android
when the link from IPL>SPL is broken.... there is nothing
Fastboot is on the SPL.
Its not "the rest of us" that don't know this....its just you
@Golden
Im surprised that hasnt been looked at yet. However..the spl bricks are probably very different from the ones on the G1
reason being is that Magic users are using Magic radios and Magic SPLs
These G1 bricks are from using G1 Radio and ported Magic SPL's
Technically, any magic radio should be compatible any magic spl
their bricks would easier to fix as the proper software is probably still on there while g1 may or may not recognize the software such as the magic spl

Please help ASAP

Hello everyone,
I have a rooted g1 and I was putting on the 2.1 rom on my phone. I was following a guys instruction off of youtube but it totally messed my phone up. Now its stuck on the pitcure with the open box pointing a yellow arrow on the phone right next to it(the update screen), what do I do??? Thanks for your help.

You dont even have root then...If it shows what i think your taking about....You should follow this simple enough my little brother(7yr) could master it:
http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/

no i have root access i already had about 5 other roms on there but this guy said that you need a radio update sign. the guys site is http://www.youtube.com/watch?v=QfPI9Qdagd0&feature=related

Sagz326 said:
no i have root access i already had about 5 other roms on there but this guy said that you need a radio update sign. the guys site is http://www.youtube.com/watch?v=QfPI9Qdagd0&feature=related
Click to expand...
Click to collapse
If you had root why did you flash the radio again?
That gives bricks applying radio after having root is pointless.
What are you trying to do?

i dont know im a noob if you dont know by know. well is there anything i can do???

Sagz326 said:
i dont know im a noob if you dont know by know. well is there anything i can do???
Click to expand...
Click to collapse
Just tell me everything you did, step by step.

ok first i put both of his zip files on my sd card then turned off my phone and turned it on with the home key, then i backed up my phone, then a factory wipe/reset, then applied the radio update, then tried to apply the other zip file but couldnt, so i rebooted my phone and now im stuck

Sagz326 said:
ok first i put both of his zip files on my sd card then turned off my phone and turned it on with the home key, then i backed up my phone, then a factory wipe/reset, then applied the radio update, then tried to apply the other zip file but couldnt, so i rebooted my phone and now im stuck
Click to expand...
Click to collapse
radio and spl?'
But you have to have a custom recovery image before you can flash either of those.

i think it was just a radio but not sure. but i followed that guys video step by step and now im in this position

yeah i have amonra

Sagz326 said:
i think it was just a radio but not sure. but i followed that guys video step by step and now im in this position
Click to expand...
Click to collapse
Ahh you might brick, you seem to have flashed the Radio made for HTC hero not G1....Notice the title: "How to get Android 2.1 on HTC Hero"
To use Hero 2.1 on G1 it shows it here @ XDA, you only needed Haykuro SPL and the 26I radio/
If rec mode is working then you arent brick or if you can get into bootloader.

how do i get in rec mode or bootloader

Hold down home when turning on the phone=recovery
Hold down camera button while powering on= bootloader
If you can't get into either one of those, likely bricked. I know with WM devices flashing a radio for another phone is one of the fastest ways to brick your phone, Android seems to be much more forgiving, so hopefully you will be lucky and if recovery and bootloader don't work, you can possibly get ADB to work.

If you don't figure out how to do this BEFORE you do it, you will likely brick your phone, if not sooner, soon enough. Doing it along with a video isn't enough to make sure you won't brick your phone.
Read through the steps of rooting, flashing a basic, stock ROM, do that a time or two, and then get into the more up-to-date stuff.
Your method of going about a new task is going to... well, it isn't going to work, unless you are really, really lucky.

Please Please someone help me! tmobile uk g1

Hi all,
I’m in desperate need of some of your wealth of experience, i have managed to root and flash my g1 with - rc9 JFv1.51_CRB43-EU.zip (Jesus freke), and recovery-RA-dream-v1.6.2.img recovery image!. Now i want to update to a newer rom!
Now for the problem, the recovery program allows me to flash many of the rom's available but none of them work after the flash completes it just loads the g1 screen and stops there i have left it on that screen for about 10 min’s and nothing at all happens, but then it will allow me to flash back to rc9 JFv1.51_CRB43-EU.zip absolutely fine no issues every time?. Do i need to install anything else before updating to Open Eclare 2.1.1 or SuperD1103-blk.? I’m in the UK with a UK g1 mobile if that makes a difference?

crusader0071 said:
Now for the problem, the recovery program allows me to flash many of the rom's available but none of them work after the flash completes it just loads the g1 screen and stops there i have left it on that screen for about 10 min’s and nothing at all happens, but then it will allow me to flash back to rc9 JFv1.51_CRB43-EU.zip absolutely fine no issues every time?.
Click to expand...
Click to collapse
Just use the top three wipes available in Anon's recovery menu: Wipe System/Data (1st), Davilk Cache (2nd), Ext Partition (3rd). If you haven't partitioned your SD card into FAT32, Ext2, 3, or 4 and Linux-Swap, do so now with the Recovery menu. You must backup your fat32 first, because a total repartition will totally blank your data. Good luck!

crusader0071 said:
Hi all,
I’m in desperate need of some of your wealth of experience, i have managed to root and flash my g1 with - rc9 JFv1.51_CRB43-EU.zip (Jesus freke), and recovery-RA-dream-v1.6.2.img recovery image!. Now i want to update to a newer rom!
Now for the problem, the recovery program allows me to flash many of the rom's available but none of them work after the flash completes it just loads the g1 screen and stops there i have left it on that screen for about 10 min’s and nothing at all happens, but then it will allow me to flash back to rc9 JFv1.51_CRB43-EU.zip absolutely fine no issues every time?. Do i need to install anything else before updating to Open Eclare 2.1.1 or SuperD1103-blk.? I’m in the UK with a UK g1 mobile if that makes a difference?
Click to expand...
Click to collapse
Make sure you partition your sd card and then try like the above said....or maybe try flashing death spl.
http://forum.xda-developers.com/showthread.php?t=625886&highlight=Death

thanks for trying to help but....
hi thanks for your help but ...
i have partitioned the card via anons recovery flasher, i have set my 8gb to 96mb swap , 1.5gb ext2 and the rest is used for fat32.
i have also gone throught the menu and deleted / erased the top 3 as requested but when i install a new rom it still freezes on the g1 welcome screen? please help!

G1ForFun said:
Make sure you partition your sd card and then try like the above said....or maybe try flashing death spl.
http://forum.xda-developers.com/showthread.php?t=625886&highlight=Death
Click to expand...
Click to collapse
hi i just noticed im using Hard Spl update at the moment ? how do i update to Haykuro?

i think i have totaly broke my phone? - i downloaded haykuros spl and flashed it via the anons recovers flash image from sd card, and now i can no longer get in to the recover menu? and no fast boot please please help me !

crusader0071 said:
i think i have totaly broke my phone? - i downloaded haykuros spl and flashed it via the anons recovers flash image from sd card, and now i can no longer get in to the recover menu? and no fast boot please please help me !
Click to expand...
Click to collapse
This is YOUR FAULT for NOT READING!!!!
You installed an SPL meant for an HTC MAGIC onto your HTC DREAM. It *CAN* be made to work, HOWEVER, you failed to read and understand what is required to actually do it safely.
SPECIFICALLY, you are stuck in boot mode 3 -- boot to recovery, and because you changed the SPL, your recovery partition is UNABLE TO BOOT.
You are BRICKED, and the only way out is to use a hardware interface called "JTAG", which requires you to disassemble the phone.
SPECIFICALLY:
You missed the part of that thread that says "MOD EDIT PLEASE READ THIS THREAD FOR UP TO DATE INFORMATION".
I have no sympathy for you. That instruction is in big purple letters.

hi thanks for your info, do you know anyone or anywhere i can get my phone jtagged?

How could you mess it up with step by step instructions....lol...I am being dead serious....it doesn't get more clear than this.
IMPORTANT: Before going any further make sure that you have PVT board. You can do this by rebooting your phone and holding the camera button. The first line should say "PVT" if you see "DVT" then DO NOT flash this because odds are you will get a brick but If it says "PVT" then you are good to go.
First you are going to need to download the latest radio and the SPL. both can be found here http://code.google.com/p/sapphire-port-dream/ There is also a new radio that is compatible that can be found here http://forum.xda-developers.com/showthread.php?t=640535
Prior to starting the installation process please make sure that your battery has a good charge. Also DO NOT pull your battery out at anytime during the installation process. I know it seems like common sense but I read a thread where someone had pulled their battery in the middle of the installation process and they ended up with a brick.
Now that all that's out of the way lets get started!
1. Copy "ota-radio-2_22_19_26I.zip" or "G1-radio-2_22_23_02.zip" and "spl-signed.zip" onto the root of your SD card.
2. Reboot into recovery. I suggest using the RA-dream recovery you can download it here http://forum.xda-developers.com/showthread.php?t=566669
3. Wipe your phone "factory data reset" (this step isnt really necessary since your phone is wiped after flashing the SPL but I always like to wipe before flashing anything)
DO NOT SKIP THIS NEXT STEP OR YOU WILL BRICK YOUR PHONE
You must have the latest radio "2_22_19_26I" or "2_22_23_02" to flash this SPL if you already have the latest radio you should not have to flash it again but it will not hurt if you do flash it again. When in doubt flash it anyway.
4. Flash the Radio "ota-radio-2_22_19_26I.zip" or "G1-radio-2_22_23_02.zip" it will install and then it will ask you to reboot to finish the installation, so reboot, it will then finish installing and then reboot back into recovery.
5. Flash the SPL "spl-signed.zip" it will install and then ask you to reboot to finish the installation, so reboot, it will then finish installing and reboot into recovery so you can flash your ROM

i cant get in to fast boot or recovery i just get the g1 screen, if i press camera and power or if i press home and power i just get the g1 nothing else

crusader0071 said:
i cant get in to fast boot or recovery i just get the g1 screen, if i press camera and power or if i press home and power i just get the g1 nothing else
Click to expand...
Click to collapse
Did you follow those steps when flashing the SPL? Did you even flash the radio before flashing the SPL?
It sounds like you have no idea what you did to your phone which is never a good sign (and usually means you shouldn't even be flashing custom radios/spl's/roms)

no i did not, i was asking for help for the last 2 or 3 days? i did what i thought was right but it was not. can i fix it or not?

heres what you do
ive did this too lmao jus go here www*androidhustler*blogspot*com ( THE * ARE REPLACEMENTS FOR . BECAUSE I CANT POST A OUTSIDE LINK SO U GET WUT IM SAYING SWITCH THE * WITH A . ) THEN SCROLL DWN TO A POST CALLED THE 2010 HOW TO GET CYANOGEN LATEST. DO ALL STEPS AND DONT RUSH. IF YOURE G1 DOESNT BOOT UP PROPERLY THEN I QUIT THIS SHYT BRO. LOL FOR REAL AND IF U HAVE ANY QUESTION EMAIL ME AT [email protected]*COM

crusader0071 said:
no i did not, i was asking for help for the last 2 or 3 days? i did what i thought was right but it was not. can i fix it or not?
Click to expand...
Click to collapse
Sigh....I would go buy another phone off Craigslist or something similar.
Next time...please read before flashing....Although I'm sure you will after the last mishap.

the only way to fix your phone is to buy a doner phone with a broken screen or something cheap off of ebay
there is NO KNOWN WAY to fix it without a doner (the jtag method isnt do-able yet)

I know here in town...there are so many G1's up for sale around the $150 mark in really really nice condition.
That's where I'd be looking if I bricked my G1. Well...I'd be replacing it with a HD2 probably...lol

garok89 said:
the only way to fix your phone is to buy a doner phone with a broken screen or something cheap off of ebay
there is NO KNOWN WAY to fix it without a doner (the jtag method isnt do-able yet)
Click to expand...
Click to collapse
What do you mean by jtag method isn't do-able?
ezterry did mine without an issue.

details
Sleeepy2 said:
What do you mean by jtag method isn't do-able?
ezterry did mine without an issue.
Click to expand...
Click to collapse
have you got contact details for ezterry? if so pm me please.

as far as i can see the jtag is still in testing?

This noob is in the UK anyways. Let him figure it out.
Wrong section, soft bricked his own phone and freaking out.
Please READ. You are from the UK so your English isn't bad. You have no excuse for not following instructions.
Ways to fix your phone:
1) motherboard replacement
2) JTAG (experts are not anywhere near you though)
3) buy a new phone
Mods please get this out of here

Hard Bricked my G1. Any way to unbrick it?

Hi everybody,
I was trying to load the cyanogen mod to my G1
Had Android 1.6 and Radio 2.22.23.02
I downgraded to RC29 successfully
Rooted my phone
Loaded recovery-RA-dream-v1.7.0.img. Flashed successfully
Then started following instructions below:
wiki . cyanogenmod / index.php / DangerSPL_and_CM_5_for_Dream
I got stuck in step 6
It is probably because downgrading to RC29 also downgraded my radio version. I did not check the radio version again after I downgraded
Using danger.spl bricked the phone
I searched online and found some solutions with JTAG, but I am in Turkey and do not have access to purchasing these from ebay or the know-how to apply them (as you can tell from my mistake above!)
1) I found the below solution, but not sure if it will work:
code . google / p / android-roms / wiki / Unbrick
They say it will only work if you have soft-bricked your G1. I'm not sure
2) Others say I need to call T-mobile Customer care (where I purchased the phne from), but that was about a year and a half ago. How long is the warranty on the G1? 1 year or 2 years?
3) And yet others say use it paper-weight
Should I go for option 3?
What do you think?

Wiki Instructions
What is DangerSPL?
This SPL is actually a port of the Magic/MT3G (Sapphire)'s SPL to the Dream/G1. Called danger because not only does it wipe your data in the repartition process (data can be restored with Nandroid restore after flashing DangerSPL), it has a chance of bricking your phone if you would ever choose to downgrade the radio after flashing it (see below for compatible radios). Never flash a 1.x, 4.x, or 6.x radio with DangerSpl
It is not required for CyanogenMod versions 4.X (CM4) and below, but required for the CM5 series on the G1/Dream.
Why is it required for the CM5 series on G1/Dream?
The G1/Dream's /system partition was originally created to take ROMs up to 64MB. The CM5 series for the G1 & Magic/MT3G is currently too big to fit on this partition.
Why don't Magic/MT3G users have to apply it?
The Magic/MT3G (Sapphire)'s /system is set to take ROMs up to 96MB by default, so no SPL change is needed.
Is it dangerous?
While the method of applying it has been perfected over the course of its use, any modification of SPL/Radio/ROM carries with it an inherent risk. That being said, if you pay attention, follow instructions, and plan your approach, it is actually an easy process.
How do I check if I already have DangerSPL?
Boot into fastboot mode by turning the phone on while holding the camera button and pushing the power button. The second line contains your SPL version. If it ends in 2005 (eg 1.33.2005) then you have DangerSPL installed already. The line with RADIO tells the radio version, which is important if you don't have DangerSPL. To leave fastboot mode, press MENU+SEND+END at the same time.
Installation
Warnings
Make sure that you have a full battery during the steps below and at no point remove power from the device (i.e. no battery pulls!). See the first two bullets in troubleshooting regarding battery use after flashing CM5 and fixes for higher-than-expected battery drain.
There has been some development/debate over DVT/PVT and bricks. Optional reading (but still recommended): XDA forum
Prerequisites
A rooted G1/Dream
A compatible radio (IMPORTANT: If you just rooted, the RC29/RC7 install includes a 1.x radio and you MUST install one of the 2.x radios below before DangerSPL)
2.22.23.02 seems to get more bars for T-Mobile US customers, though non-US users might have better luck with 2.22.19.26i.
(HardSPL/Engineering Spl Users) Radio installations can be had by fastboot flash radio radio.img after extracting radio.img from the .zip
Either of the following radio versions is acceptable.
Radio 2.22.19.26I
Radio 2.22.23.02 (G1)
Rogers Dream users: A 3.X radio is Danger compatible (eg 3.22.26.17)
Failure to meet the Prerequisites WILL result in a BRICK!
Files required
Danger Spl
gapps-ds-ERE36B-signed.zip, Mirror1
Latest CM5 for Dream/Sapphire
ONLY Roger's Dream users: EBI1 kernel for 5.0.x
Steps
It has been brought up that Clockwork Recovery struggles with this guide, so Amon_ra is v1.7.0 recommended. If you have CM or older recovery, upgrade to Amon_Ra first.
Please if you need to diverge from these steps for any reason start over from step 1 when you return.
Boot into Fastboot (Power on the phone holding the camera button) This will either show a screen with dancing androids or a "rainbow" splash. Here you will find the hboot/radio version:
radio 1.x: You will need to upgrade this to a 2.x radio before running this process.. please upgrade and re-do this step (Ie. verify you see the updated radio in fastboot before continuing)
radio 2.x: You may press MENU+SEND+END at the same time and proceed (unless hboot-1.33.2005 is installed; indicating you already have dangerSPL)
radio 3.x: You may press MENU+SEND+END at the same time and proceed (unless hboot-1.33.2005 is installed; indicating you already have dangerSPL)
Copy DangerSPL (spl-signed.zip), CM 5.0.x, and gapps-ds-ERE36B (& Ebi1 port if required) to the root of your sdcard.
Reboot/Boot into your custom recovery by holding down the 'home' key before the G1 splash appears.
Make a Nandroid Backup (ext not required) (recommended for upgrading users, not required for freshly-rooted users)
Flash DangerSPL (spl-signed.zip). It will install and then ask you to reboot to finish the installation
Reboot as prompted at the bottom of the screen. This will finish installing DangerSPL and reboot back into recovery so you can flash your ROM.
Once back into recovery Wipe Data/Factory Reset
Flash CM 5.0.x THEN gapps-ds-ERE36B (& Ebi1 port if required); then reboot (Boot may take longer than normal)
Login to Android/Google as per usual
If you want to restore the nandroid backup (to attempt an unrecommended no-wipe upgrade between CM4.2 and CM5)
[Optional] Reboot to recovery, and issue a Nandroid Restore, then follow the regular instructions .
This command will attempt to restore user data.
Restoring will also restore your previous Firmware, so you have to follow the instructions to get 5.0.x again
Note: If this causes undesired consequences (ie bootloops, FC's, etc) then run Fix Permissions/'Fix UID Mismatches'.
***************************************
Instructions for the 'soft-brick' (I think)
How to Un-Brick Your Phone
(Method 1)
Ok so you're trying to put this really cool new custom ROM on your phone and then suddenly, your phone won't start up…well my friends, you have got yourself a bricked phone. The thing you worry about the entire time you're rooting, and flashing your phone, has now become reality. Well, fear no more, for I, CTDroidBeast have found a way to unbrick your device!
It's really easy. It's actually easier then rooting your phone, believe it or not.
Ok, you will need a new SD card, because I bet if you use the one out of your device your computer will not be able to read it. But if it does then HEY, you're in luck. You don't have to spend your money on a new SD card.
So let's get started.
Step 1: Turning Off Your Phone
Because you have a bricked phone, you can't just hold the power button. So if your phone is not already off then you're going to want to take out the battery.
Step 2: Preparing Our SD card
Take out your SD card and put it into an SD card reader or some type of other adapter so that we can view it from our computer. If you cannot view the SD card on your computer then you're going to need a new SD card.
Download DREAIMG-RC29.zip and unzip the file.
Reformat the SD card to FAT32 and copy the DREAIMG.nbh onto it.
Safely eject the SD card.
Put the SD card into your device.
Step 3: Wipe The Phone
Hold home and press the power button.
When you see the image of an ! mark, open your keyboard and press Alt + L if you cannot see any command options.
Do a factory reset by pressing Alt + W or just using the trackball.
When the reset is done, go ahead and hold the camera button and select the reboot system now option with your trackball.
Step 4: Flashing The Phone
Once the grey screen pops up (or the white screen if your phone was rooted with JesusFreke) it will ask you to hit a button to start installing the image…press that button. DO NOT DO ANYTHING TO STOP THIS PROCCESS. It will take about 8-12 minutes.
When the image has completed the installation (it will say completed), go ahead and press the green, red, and menu buttons at the same time. The phone will reboot.
And your done! Your phone is now unbricked!.

Please help!

YOU FAILED.
If you don't take the time to read and learn what you are doing, why should anyone take the time to help you?
WHY would you EVER install RC29? IDIOTIC MOVE!
WHY would you EVER install deathSPL? IDIOTIC MOVE!
I say you deserve what you got.

lbcoder said:
YOU FAILED.
If you don't take the time to read and learn what you are doing, why should anyone take the time to help you?
WHY would you EVER install RC29? IDIOTIC MOVE!
WHY would you EVER install deathSPL? IDIOTIC MOVE!
I say you deserve what you got.
Click to expand...
Click to collapse
I was just following the Wiki instructions ( Full Update Guide - G1/Dream Firmware to CyanogenMod ) here:
My radio before downgrading was 2.x, so I assumed it would still be the same after the RC29 downgrade, but it turns out the downgrade also dongrades the radio to 1.x
therefore death spl bricked the phone
I should have checked the radio version for a 2nd time before flashing death spl
Is there any way to fix this now??

HEARTBREAKER123 said:
I was just following the Wiki instructions ( Full Update Guide - G1/Dream Firmware to CyanogenMod )
Click to expand...
Click to collapse
You did not follow the instructions.
You deliberately skipped step one on the danger spl instructions. Put there so that those who didn't realize the radio had become downgraded didn't do what you just did. You also ignored the warnings on that page that rc29 installs the 1.x radio.
HEARTBREAKER123 said:
Is there any way to fix this now??
Click to expand...
Click to collapse
What part of not having the right radio will brick your device wasn't understood..
by all means hope your recovery is messed up and that you have access to fastboot when you attatch a USB wire.
Otherwise there is jtag. .. bit more complex than flash spl-signed.zip after being 100% sure a 2.x radio is installed however..
Another option is replace it.. some have found replacing the main board + daughter board of a working phone in bad cosmetic shape (screen cracked) a cheap alternative here than a brand new dream. Still requires reading the service manual to properly disassemble what you need without having a bit of a mess.. particularly if you skip a step.
My recommended solution is to find a phone you can deal with stock firmware buy it and sell the rest of your dream as is.. you want root you need to understand the instructions not just follow them.

Alright, well I think he got the point - he should have followed instruction better
I'll keep it as straight forward as possible, no there is not a way you can unbrick your phone without the JTAG tools. T-Mobile's warranty is only one year, afterwards they will not replace your device for any reason.
The soft brick solution you posted will not work, because you have a hard brick.
I believe you only have a couple of solutions.
a) Get a new G1
b) Buy an old G1, preferably one with a broken screen so its cheaper, and place the motherboard of that G1 into your current one
c) Work with some members of XDA and see if you can work out an arrangement to get you the JTAG tools, though this is unlikely to work and difficult to do.
I'm sorry that you have broken your G1, it's a terrible feeling to break your phone in this way where everything is physically still perfect. I believe your best bets are probably solution "a" or "b", you can shop around locally and see if you can find anything
Best of luck.

Thanks for the help.
I think I will try and get another G1 to see if I can replace the motherboards

HEARTBREAKER123 said:
Thanks for the help.
I think I will try and get another G1 to see if I can replace the motherboards
Click to expand...
Click to collapse
You know, if you're going to all the trouble of taking it apart and planning on essentially throwing the mainboard in the trash anyways, what do you really have to lose in attempting to jtag the thing? $2 worth of components and a couple hours of your time? Worst that happens is you fry it, in which case you were planning on trashing it anyway.

lbcoder said:
You know, if you're going to all the trouble of taking it apart and planning on essentially throwing the mainboard in the trash anyways, what do you really have to lose in attempting to jtag the thing? $2 worth of components and a couple hours of your time? Worst that happens is you fry it, in which case you were planning on trashing it anyway.
Click to expand...
Click to collapse
Like the OP said, he lives in Turkey and is unable to purchase these items on eBay.

SolemnWishing said:
Like the OP said, he lives in Turkey and is unable to purchase these items on eBay.
Click to expand...
Click to collapse
Turkey is NOT a back-woods country and there ARE LOTS of sources besides ebay. In fact, ebay is the LAST place you should look for electronic components.
I GUARANTEE that the required components can be purchased in STORES all over the place in Turkey.

lbcoder said:
You know, if you're going to all the trouble of taking it apart and planning on essentially throwing the mainboard in the trash anyways, what do you really have to lose in attempting to jtag the thing? $2 worth of components and a couple hours of your time? Worst that happens is you fry it, in which case you were planning on trashing it anyway.
Click to expand...
Click to collapse
$2? I thought Jtag cost like 70 bucks

racerxgt said:
$2? I thought Jtag cost like 70 bucks
Click to expand...
Click to collapse
Okay, I have good news and bad news
THe good news is that I was able to find someone with a jtag adapter and he fixed the phone for me for $50
Being more careful this time, I went through the wiki steps and installed CM 5.0.8 and gapps-ds-ERE36B-signed
Yaay!
But then I noticed that CM6 was out, and that it had flash, so why wait, right?
I flashed CM6 with no problems, rebooted the phone, logged in, everything seemed OK, except that I didn't have google apps
So I flashed gapps-mdpi-FRF91-signed.zip and... I wasn't able to log on to google!
You know the menu that asks you to sign in to your google account at the beginning
It says "touch the android to begin"... And when I touched the android, it wouldn't ask for my username and password.. Right click would go into 'Wireless Settings', and I was able to successfully define an APN and get a 3G connection, however, even after all that, and when the phone had reception,
touching the android would make the android change color, but it wouldn't let me go to the next step!
So I decided to flash the previous google apps
Now the phone does not boot in normal mode
I can access the bootloader and the fastboot menu (both Camera+Power and Home+Power work fine), but I am not sure how to fix the problem I have
I tried downgrading to Android 1.5 and starting over, but when I go into the bootloader menu, I see 3 androids with skateboards and the following options:
CAMERA_STEP2 : Hboot mode
SEND: Reset device (Doesn't reset, it just reboots when you try)
ACTION: Restart to hboot
MENU: Power down
And when you are in hboot mode, you can't click anything
How can I revert to CM 5.0.8??
Also, is it normal for the new gapps to cause this type of an error?

HEARTBREAKER123 said:
Okay, I have good news and bad news
THe good news is that I was able to find someone with a jtag adapter and he fixed the phone for me for $50
Being more careful this time, I went through the wiki steps and installed CM 5.0.8 and gapps-ds-ERE36B-signed
Yaay!
But then I noticed that CM6 was out, and that it had flash, so why wait, right?
I flashed CM6 with no problems, rebooted the phone, logged in, everything seemed OK, except that I didn't have google apps
So I flashed gapps-mdpi-FRF91-signed.zip and... I wasn't able to log on to google!
You know the menu that asks you to sign in to your google account at the beginning
It says "touch the android to begin"... And when I touched the android, it wouldn't ask for my username and password.. Right click would go into 'Wireless Settings', and I was able to successfully define an APN and get a 3G connection, however, even after all that, and when the phone had reception,
touching the android would make the android change color, but it wouldn't let me go to the next step!
So I decided to flash the previous google apps
Now the phone does not boot in normal mode
I can access the bootloader and the fastboot menu (both Camera+Power and Home+Power work fine), but I am not sure how to fix the problem I have
I tried downgrading to Android 1.5 and starting over, but when I go into the bootloader menu, I see 3 androids with skateboards and the following options:
CAMERA_STEP2 : Hboot mode
SEND: Reset device (Doesn't reset, it just reboots when you try)
ACTION: Restart to hboot
MENU: Power down
And when you are in hboot mode, you can't click anything
How can I revert to CM 5.0.8??
Also, is it normal for the new gapps to cause this type of an error?
Click to expand...
Click to collapse
*FACEPALM*

goldenarmZ said:
*FACEPALM*
Click to expand...
Click to collapse
Don't facepalm just yet
I managed to go back to 5.0.8 after doing everything from scratch
I guess I will use it like that for a while until CM6 / google apps stabilizes

HEARTBREAKER123 said:
Okay, I have good news and bad news
THe good news is that I was able to find someone with a jtag adapter and he fixed the phone for me for $50
Click to expand...
Click to collapse
I bricked my G1 as well, but I'm not in the US
Do you have an idea what the JTAG adapter looked like ?

wow you guys sound mean to the poor guy when he was just making a newbie mistake. i remember when i was making all of those mistakes...hell im still making those mistakes and even thou i have gotten my fone to freeze on the g1 logo or even just go into a constant reboot im glad iv been able to fix the problem everytime and still dont know what im doing im just learning. but hey isnt that procedure that you have up there an unrooting procedure???? and for those getting the wrong gappss try downloading the tiny mdpi on the dream that one worked for me, the mdpi didnt work at all till i tried that one got it from the cyanogenmod site. by the way i gotta say thanks to all the devs, which i had a brain like yals id love to join in on developing but im kinda an idiot here lol

spike210 said:
wow you guys sound mean to the poor guy when he was just making a newbie mistake. i remember when i was making all of those mistakes...hell im still making those mistakes and even thou i have gotten my fone to freeze on the g1 logo or even just go into a constant reboot im glad iv been able to fix the problem everytime and still dont know what im doing im just learning. but hey isnt that procedure that you have up there an unrooting procedure???? and for those getting the wrong gappss try downloading the tiny mdpi on the dream that one worked for me, the mdpi didnt work at all till i tried that one got it from the cyanogenmod site. by the way i gotta say thanks to all the devs, which i had a brain like yals id love to join in on developing but im kinda an idiot here lol
Click to expand...
Click to collapse
bigest mistake evar was probably buyng tha damn mobo ...you see i have 3 HTC's 1 HTC Dream that work's just fine , 2 T Mobile G1 that it's a piece of **** ( it got's nothing in comon with HTC dream it's just a cheap crap copy of the original ) and 3 it's a HTC with Win Mobile wich i think it's by far the most stable mobile operating sistem for now , all of you will say that it does not work like that , but think about this .... how manny win mobo's hawe ever been bricked?! and how manny android mobos are there bricking every day ? your android will brick eventualy ... oh yeah and i am selling 2 HTC dream Black and white
Thumb's upp if you are born in the rong generation )