Database Develop

Bricked g1 help

Hi two days ago i decided to put the jachero rom on my g1 and it said i had to update the radio so i did then put the latest spl so i did and after i renamed the spl to update.zip and applied it. my phone got bricked and i cant apply the dreaimg.nbh to wipe everything and cant go to recovery and i dont know if it will never work again?? please heelpppp!!! oh yyeah and im 13.

what do you mean brick? which radio did you install and which spl did you install after that?
does your phone turn on at all?

um
i put the radio 2.22.6i and idk about the spl and it just says tmobile g1

Alanrocks15 said:
Hi two days ago i decided to put the jachero rom on my g1 and it said i had to update the radio so i did then put the latest spl so i did and after i renamed the spl to update.zip and applied it. my phone got bricked and i cant apply the dreaimg.nbh to wipe everything and cant go to recovery and i dont know if it will never work again?? please heelpppp!!! oh yyeah and im 13.
Click to expand...
Click to collapse
it seems like you're pretty bricked.
Please give more information on your procedure.

If you cannot boot into recovery (home + power) or the bootloader (camera + power) then it is most likely bricked. If you have insurance, just tell T-Mobile that your phone told you that there was an update available, and when you clicked OK, the phone restarted and then you were stuck at the G1 screen.

um
well i dont know anything how to flash cyanogen
on the jachero page it said get the latest spl so i updated and after that canot go into recovery
so i only have warranty no insurance

Alanrocks15 said:
well i dont know anything how to flash cyanogen
on the jachero page it said get the latest spl so i updated and after that canot go into recovery
so i only have warranty no insurance
Click to expand...
Click to collapse
if you dont even know what your putting on your phone, you kinda deserved it...
Use your warranty, tell them there was an over the air update and ur phone ran out of battery in the middle of it.... and read up/think before doing something like that again...
theres really nothing you can do now. You need to give us more detailed procedures if you want a second opinion

well
i did know what to do but since i already have the latest radio then i just put the spl and if i get another g1 if i already have the hard spl do i need to put the latest because igot the hard spl from another forum but since the jachero page told me to update it i did that maybe i dont have the latest radio but no since anymore and thank you i will tell tmobile i got a ota but didnt the ota thing stop like 3 weeks ago i dont think they will believe me that i just got an ota barely

Alanrocks15 said:
i did know what to do but since i already have the latest radio then i just put the spl and if i get another g1 if i already have the hard spl do i need to put the latest because igot the hard spl from another forum but since the jachero page told me to update it i did that maybe i dont have the latest radio but no since anymore and thank you i will tell tmobile i got a ota but didnt the ota thing stop like 3 weeks ago i dont think they will believe me that i just got an ota barely
Click to expand...
Click to collapse
So? Just say that you had your phone off for a few weeks cuz you went on vacation and chose to bring another phone for safety's sake, and when you got back, you turned on the phone and presto! OTA update...

Alanrocks15 said:
i did know what to do but since i already have the latest radio then i just put the spl and if i get another g1 if i already have the hard spl do i need to put the latest because igot the hard spl from another forum but since the jachero page told me to update it i did that maybe i dont have the latest radio but no since anymore and thank you i will tell tmobile i got a ota but didnt the ota thing stop like 3 weeks ago i dont think they will believe me that i just got an ota barely
Click to expand...
Click to collapse
1) Use full stops, 'cos that's near impossible to read.
2) No, hard SPL will not work you need Haykuro's SPL.
3) Your phone will only have bricked it you had the old radio OR you did not have a PVT board. Did you look in the bootloader before you flashed the new one? I'm guessing not.
4) Luckily there was a security (I think it was security) update that was just released, so they shouldn't qustion it.

ok sorry
Ithink the warranty will cover it

I would go with the OTA story especially since there was just an OTA update released that has been pushed to phones over the last few days. I know a few people who also didn't read up before they started flashing and they too bricked their phones however, the OTA story worked most of the time. This is really your only choice seeing that you don't have insurance on the phone. Good luck

Just use the OTA story again lol
Tmobile wont hassle you too much about it.
Make sure you download the Radio that Haykuro provided, flash it, then boot into the bootloader to make sure it reads properly. Also verify that you have a PVT board.
Put the update.zip with the SPL on your phone AND VERIFY THE MD5 CHECKSUM (you should do it with the radio too actually)
and continue to follow the proper directions.
If you brick after following that, use the OTA story again but stick to HardSPL lol

what is checksum and pvt board?

Alanrocks15 said:
what is checksum and pvt board?
Click to expand...
Click to collapse
PVT board is the board that won't brick when flashed with the Danger SPL. Just another design. You can check your board revision by booting into bootloader (camera+power).
md5 checksum is a special key that is tied to the file that is generated based on that file. If the file that you downloaded is corrupt or different compared to the original file, the md5checksum will be different, letting you know that you need to re-download the file or risk a brick.

help help help help
please somwbody help please...my g1 t mobile freeze in g1 screen...i can't power+camera, power+volumen down, no bootloader screen nothing, only freeze in g1 tmobile screen...
when press action botton and power a blue led come on but nothing happend...
somebody can help me with any information
jtag pin outs...or somenthing to solve this problem..i come from panama

help help help help
please somebody help please...my g1 t mobile freeze in g1 screen...i can't power+camera, power+volumen down, no bootloader screen nothing, only freeze in g1 tmobile screen...
when press action botton and power a blue led come on but nothing happend...
somebody can help me with any information
jtag pin outs...or somenthing to solve this problem..i come from panama

jommega said:
please somebody help please...my g1 t mobile freeze in g1 screen...i can't power+camera, power+volumen down, no bootloader screen nothing, only freeze in g1 tmobile screen...
when press action botton and power a blue led come on but nothing happend...
somebody can help me with any information
jtag pin outs...or somenthing to solve this problem..i come from panama
Click to expand...
Click to collapse
nothing you can do. its bricked. call tmo or get it replaced by whatever warranty you have

well im getting a replacement g1 and i wanna root it again but i dont wanna brick it and theres a post that is here on xda and its called
"how to root, flash recovery cyanogen, parition sd to fat , ext2 and 3 , how to flash radio nd spl and install jachero"
is this a good post?

Thanks guys this helped a lot wow its been almost 2 years so yea thanks a lot guys
Sent from my SGH-T959 using XDA App

stuck on G1 screen

So i got a new G1 after the previous one never got signal (took it to a shop and they sent me a replacement)
i downgraded to rc 29
rooted/put cm recovery 1.4 in
the most recent radio was already installed (62.50S.20.17H_2.22.19.26I)
flashed haykuro's spl.
then, as usual, it says "press home+back" to reboot.
so i did.
however, the phone is stuck at the white G1 screen. I tried to do reboot with home+power, and with camera+power, but both of those went to the G1 screen and stopped.
I can't see what's going on (adb logcat simply says -waiting for device-. is there another command?)
so should i wait on the screen, or did i make a mistake. If so, then where did i go wrong and how should i have done it?

If you can not get into recovery or bootloader, just set down, yell, smack yourself in your head and then take it back to the shop for another one cause you my friend BRICKED your phone. Another phone bites the dust, don't feel to bad I have done it before too

any idea how it happened? so i can avoid doing it again later?

Did you have a pvt board? If so then you are just a small statistical error. I have bricked a phohne before that have a pvt board, newest radio, all the requirements for it to work ,and the phone still bricked ,but it was around the release of cupcake so i told my friend to call tmobile and tell them he got an ota update and his phone wouldn't get passed the g1 screen, and they sent him another and the new spl flashed just fine on it

Not sure cause you said that the newest radio was already on there which would be the usual suspect, when you say it was already there do you mean before you downgraded to rc29 if so when you downgrade it also downgrades the radio and you have to flash it back on

not sure about the board - im assuming there's no way to check now?
and as long as you can "prove" (or lie, really) that the phone broke on its own, theres no limit as to how many replacements you can get, right?
...It downgrades the radio too?
well, theres my problem.
Anyway, thanks for the quick help guys

Yes it overwrites everything except a custom splash image but hey now you know, I would say that is what got you, when you get your new phone go into the bootloader and the first peice of info will say it is either a pvt or dvt board

If you just got your g1, chances are it did not ship with the latest update, none of the 3 I got like 2 months ago did so just say it was upgrading a ota update and froze and they will give you another one

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 )

Is my G1 bricked?

I decided to get in on the Android experience and bought a used G1 off ebay. When I got it (supposedly unlocked, but it wasn't ) it was running Cupcake 1.5 with the CRC1 build. One oddity that was stated in the auction listing is that the phone would not do a Factory Reset. When I tried it, it would go to the rainbow boot screen, but I could restart it (both a battery pull or a Menu/Home/Power press) to get back to life. I read several pages, both here and at cyanogen's page to make sure I would do the root process correctly with the eventual goal of getting this thing to cyanogen's Froyo 2.2 version. Needless to say, it has failed ... at step 1 no less. I reformatted the SD card (a 2 GB SanDisk) to FAT32 with WinXP, loaded the DREAIMG.nbh file, and rebooted the phone. The gray screen with blue text came up for the reflashing process, so I hit Power to continue. The "Update in Progress..." text shows and the bar moves until completion. After pausing momentarily at the end of the progress bar, it shows:
00018003
DREAIMG.nbh - FAIL
BOOTLOADER - OK
RECOVERY - Fail
BOOT -
SPLASH1 -
SYSTEM -
USERDATA -
RADIO_V2 -
Update Terminate
UPDATE FAIL
The rainbow boot screen says:
DREA100 PVT 32B RUUNBH
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Sep 2 2008
Serial0
The phone will now not boot past the rainbow screen. Note that if I have an SD Card with the flash image in the phone that it will go to the flash screen even if I do not hold the camera button (maybe that is normal). I searched Google for "00018003 "Recovery - FAIL"" and even it can not find any one who apparently is having the same problem.
I have repeated the update attempt several times with identical results. I downloaded the file multiple times from different locations, but the md5 has always matched regardless of where I get it from. I reformatted the card from Linux (Ubuntu) and I tried another SD Card (8 GB AData). Does anyone have any ideas on what to try? I am adept with Linux, but am a newbie to Android.
Thanks.
Code:

jeph36 said:
I decided to get in on the Android experience and bought a used G1 off ebay. When I got it (supposedly unlocked, but it wasn't ) it was running Cupcake 1.5 with the CRC1 build. One oddity that was stated in the auction listing is that the phone would not do a Factory Reset. When I tried it, it would go to the rainbow boot screen, but I could restart it (both a battery pull or a Menu/Home/Power press) to get back to life. I read several pages, both here and at cyanogen's page to make sure I would do the root process correctly with the eventual goal of getting this thing to cyanogen's Froyo 2.2 version. Needless to say, it has failed ... at step 1 no less. I reformatted the SD card (a 2 GB SanDisk) to FAT32 with WinXP, loaded the DREAIMG.nbh file, and rebooted the phone. The gray screen with blue text came up for the reflashing process, so I hit Power to continue. The "Update in Progress..." text shows and the bar moves until completion. After pausing momentarily at the end of the progress bar, it shows:
00018003
DREAIMG.nbh - FAIL
BOOTLOADER - OK
RECOVERY - Fail
BOOT -
SPLASH1 -
SYSTEM -
USERDATA -
RADIO_V2 -
Update Terminate
UPDATE FAIL
The rainbow boot screen says:
DREA100 PVT 32B RUUNBH
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Sep 2 2008
Serial0
The phone will now not boot past the rainbow screen. Note that if I have an SD Card with the flash image in the phone that it will go to the flash screen even if I do not hold the camera button (maybe that is normal). I searched Google for "00018003 "Recovery - FAIL"" and even it can not find any one who apparently is having the same problem.
I have repeated the update attempt several times with identical results. I downloaded the file multiple times from different locations, but the md5 has always matched regardless of where I get it from. I reformatted the card from Linux (Ubuntu) and I tried another SD Card (8 GB AData). Does anyone have any ideas on what to try? I am adept with Linux, but am a newbie to Android.
Thanks.
Code:
Click to expand...
Click to collapse
How much is your phone charged...charge it full and then try again....

I obviously can no longer see the meter in Android. I charged it with the phone off to a green LED and still get the same result.
Possible other relevant information:
When charging from my computer with the phone off, the LED is red, not orange. I did not notice this at first as I have not had the phone long enough to know what is "normal".
If I power up with the USB connected to my computer, the rainbow screen looks almost identical except it does not have the text "Serial0". If I unplug USB then that text appears after a couple seconds. Does that mean I can get do some serial communication that would help with the problem?

Are you sure you have the right dreamimg.nbh file? There is 2 of them. Did you put .zip after it?
sent from my superfroyo dream

I used cyanogenmod's wiki (and other pages with identical or similar instructions) which indicates to name the file exactly DREAIMG.nbh, so that is what I did. Is there a different reason I should use .zip? I also chose to do RC29 as I am assuming this phone is a US phone (I purchased from a US seller). Is there an easy way to tell which phone I have (US or Europe)? Should I try RC7, or will that completely brick the phone if it is the wrong version?
Thanks.

No you won't brick the phone. I don't know what version you'd want. I'm in usa. Never had to deal with the other. The only way you'll brick your phone is by messing with danger spl 1.33.2005 just remember if you downgrade. It changes your spl and radio. The whole package. Then you want to flash radio back to 2.22.23.02. Or 26I in your case. Before flashing danger spl. But your not even there yet. Yeah make sure you have a .zip after dream nbh file on root of your sd card. Before flashing.
sent from my superfroyo dream

Well that answers that question. I tried the RC7 for Europe and after the "Loading..." and "Checking..." stages it shows:
0028002
Not allow
and drops back to the rainbow. So I definitely have a US phone as expected.
What is the .zip file that I should have on my SD card? I do not see that in the instructions to get to the state where my phone is rooted.

Just make sure before you flash the dream nbh you have a .zip after it before you flash it
sent from my superfroyo dream

I am still not sure what you mean by the .zip. I tried renaming DREAIMG.nbh to DREAIMG.nbh.zip, but that could not find a file for updating. Then I tried putting a .zip file on the sdcard at the same time as the DREAIMG.nbh file and that did not help. So if you could shed some light on that, maybe I can make some headway.
Thanks.

I have made no progress on this over the last 24 hours. I tried several more flashes to see if eventually one would take, but I always get the same result.

man where have you been or maby where have I been? That was a very good information on the dangers of danser spl. If I have seen this earlier I would not have bricked two G1's. I know know what I did wrong. Never heard it explained that way.
Thanks

I am not sure what you mean. I have only tried to downgrade to the RC29 image as the first step toward rooting the phone. I am beginning to wonder if the previous owner did some failed mod's prior to me owning it and that is why it is stuck in the state it is in. Has anyone ever seen anything like this before?

What's going on. Pm and let me know where you guys are at. Not gonna keep coming back to this thread.
sent from my superfroyo dream

this is intresting as i have similar mobo in same situation, though I had even recovery... the phone would stay fine in hboot, BUT when i tried to go and put the .nbh file it went about 2/3's then the screen turns off and thats it... i cant get into this mobo have to wait with battery out for a few min and then i can go back into hboot
is there a solution? some other nbh file to flash? or do i need to go the jtag/serial route :/ which i have but it takes almost few hours to do with slow wiggler jtag

I never got a solution. As that phone was mostly just a temporary Android experiment for me, I gave up and got myself a new Samsung Vibrant. I still have the G1, though, if anyone has a solution ... Otherwise it will probably go on eBay as a non-working/bricked/for-parts phone.

jeph36 said:
I have made no progress on this over the last 24 hours. I tried several more flashes to see if eventually one would take, but I always get the same result.
Click to expand...
Click to collapse
This should help:
http://theunlockr.com/2010/04/26/how-to-load-a-custom-rom-on-the-htc-g1-dream/
Follow instructions to the letter. Looks like the whole procedure was made easier.

[Q] Running out of options - soft brick on 1.33.0006 spl

Okay, so a few years ago I successfully rooted my boyfriend's G1 and swore never again to go anywhere near the process.
However, said phone has now been given to my boyfriend's dad, and he's managed to install a couple of custom roms. In the last week though, he's totally screwed it up. Didn't seem to follow any sort of backing up process, or can even tell me what tutorial he was following to get it in this state.
The phone hangs at the splash screen. I can get into fastboot/hboot but there are only a few options available.
SPL is 1.33.0006 which I can gather is bad from my reading.
Hboot info is:
Dream PVT 32B Ship S-on
Hboot - 1.33.0006 (Dream11000)
CPLD-4
Radio-2.22.19.261
I have tried:
Initially I just tried going into recovery mode (I think that's what it's called - home & power) and wiping the data to see if that stopped the screen hanging. It didn't.
Putting rc7 dreamimg.nbh on the phone and loading via hboot/fastboot. When I do this it fails saying 'Main version is older.'
After doing some searching, I see someone mentioned this would mean you need to use the goldcard method. I vaguely remember having to do this a few years back on the phone when I rooted it the first time.
I go through the process, following an unlockr tutorial (can't post the link - sorry).
However, I get the same response through fastboot - 'main version is older'.
At this point I decided to try flashing a recovery image via the adb. Go through the process of installing everything etc. but when it came to installing the usb drivers for the phone, it failed although it did install the htc bootloader. I checked using adb devices command to see if it was picking anything up and it was however, when I go into the command prompt and try to do anything I just get a <remote: not allow> message.
It's only after I look for <remote: not allow> message error that I understand that 1.33.0006 is a 'perfect' SPL, and explains why I can't really do anything.
I really didn't want to resort to forum posting (one of the reasons I swore never to go near the G1 again after rooting was because I *know* I'm not tech savvy enough to be messing around with this stuff), but after spending around 6 hours over two days on this I'm absolutely stumped. The problem is, I'm stubborn so I hate to give up after spending so much time on the stupid thing (bye bye flexi day), so if anyone has any suggestions, or if they could just tell me it's a lost cause then it might help.
Thanks for your time...

do you have the UK version of phone or the US version?
can you get into recovery?

Sorry, it's the UK version - I can get into recovery (if that's home and power ?) I think. Thanks.

What nbh file was flashed prior to this? (almost sounds like the states someone was in after flashing the sappimg on a dream with 1.33.0013d..
Well first thing is to make a gold card if you don't already have one.. Then we can try one of two things. (you can make it on another phone, its a property of the sd card not the phone)
1) (may have the same main version is older problem but easy if it works) place the Orange nbh:
orange-1.58.73.2.nbh (MD5: aca4dee0c1ece7e9773f2ecbdfbba7c0)
onto the root of the goldcard named DREAIMG.nbh
If this works (or at least flashes the s=off SPL) you are in the clear simply use fastboot to re-install the 2708+ recovery/radio/spl then install a rom as per here
2) If option 1 failed... well this is an annoying process.. and risky if you take shortcuts so don't ..
A -- This time put the rogers e911 patched nbh rogers_1.89.631.1.nbh MD5:25bfcc329679e4869b3d65f673e463ac
onto the root of the goldcard named DREAIMG.nbh
This is the larges "main version number" in an official nbh for the Dream we have.
If that fails to flash (try again) if it still fails.. well I'm not sure what to do if both boot/recovery are failing (short of jtag anyway)
B -- If it succeeded you now (despite any labels on your phone) have a rogers dream.. (I mention this because working with an ebi1 radio is a bit different than the ebi0 and you don't want to brick your phone)
Ok next step is re-root: http://forum.xda-developers.com/wiki/index.php?title=Rooting_HTC_Branded_EBI1_Dreams
(Sections A-D inclusive)
C -- Before installing a rom.. now that an eng SPL is installed you can use fastboot (and only fastboot with the 3.22 radio) to install the 2708 radio and thus have a more commonly supported system:
per Follow this 2708+ install
remember do not install a 2.22 radio via recovery while a 3.22 radio is installed you will brick your phone
--
Best of luck.. really sounds like something happened that ought not have.

Thank you!
Option 1 didn't work - I still got the 'main title is older' message.
However, option 2 (after a small wobble) worked! First time I tried it, it failed stating 'partition update fail!' but after a reboot (which showed the rogers logo - a change from before) and a retry, it worked! I followed the rest of the provided instructions and installed the BIFFMOD V2.1-EZTerry 2708 port and all is well!
Thank you so much again for your help, it really is appreciated. I would not have been able to do this without your help - I've sent a small donation through as a token of thanks.
I've learnt more about G1s than I ever wanted to know, but thanks to you (and the information provided by the XDA community) it wasn't all wasted time!