Database Develop

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

my brick ?

no adb and no fastboot on pc
i can go into recovery but when phone boots it goes straight to tri color screen a.k.a bootloader with serial0
i tried downgrading it shows down grade on bootloader but not booting to rom what am i not doing

any suggestions

mods close thread solved by reflashing org.spl

ok it happen again and this time flashing stock spl is not working any help any one

Well it's very probable that by flashing your stock spl that youre now running a perfected spl which won't let you get any further, If you do manage to get back into the rom adb erase and flash a new recovery and spl because it sounds as if your recovery is fried. If you want help from others it would be a good idea to include rom, spl, radio, recovery that you're running so we can better assist you. every combination is different and often it's something as simple as a radio/rom mismatch or an overclocking issue

ok im at complete stock everything

rooted or unrooted?
one second thought.. try downgrading and re-rooting your phone via old school rc29 rom versions..
something has obviously gone awry. lets see if flashing an older rom will get you into the phone and then you can flash a new recovery, spl and radio from there.
http://forum.xda-developers.com/showthread.php?t=442480&page=35
Sometimes you just gotta redo everything because of software mismatches and extra crap in your phone that isn't supposed to be there.

i had bought the phone like that stuck on bootloader i fixed it after i tried to flash the org. spl it didnt flash but after reset it booted fine after rooting and using the danger spl and cannon complete eclair my carmera went bugging so i decide to downgrade and reroot i flashed the rc29 but it went back to the first problem again

all eclair roms have problems with cameras.. but this sounds more like there's just something not right.. could be anything from your radio to your recovery.. Full wipe and restart the process I no longer have a g1 but im pretty sure if i downgraded from 2.1 to rc29 my phone would act screwy too.

i did the full wipe formated sd cards i am at a brick wall with out a brick

thatruth132 said:
i did the full wipe formated sd cards i am at a brick wall with out a brick
Click to expand...
Click to collapse
set up sdk/adb and see if your phone is being found or not with the command
Code:
/cd
cd AndroidSDK/tools/
adb devices

i have adb installed correct its not picking up in adb at all no fastboot of course

I don't know i maybe wrong but think you should start all over again
downgrading to v1.0
although i am not that experience
please wait for someone how know

nothing i try is catching

still needing help

And we still don't know what you have installed..
1) make sure your phone is off: boot into the spl by turning on the phone while holding down camera.. tell us all the text on that screen
2) power off your phone again and enter recovery (power on holding home) if it loads do you see any version info? Or just an icon in the center of the screen.. if it dosent load tell us that
3) can you boot into a system (in your case I assume not but if others are reading) tell us the build number and rom if possible in about phone. If it wont boot tell us that.
4) Last what carrier and country is the phone originally from. (This changes what "stock" is)
With all of this information we can find the correct path to solve any issues.. usually without resorting to jtag.

DREA 100 PVT 32B
HBOOT 0.95.0000
CPLD 4
Rado 2.22.19.26I
Sep 2 2008
At this point, I searched around again for 30 minutes or so, and saw the stuck camera button problem and took off the back battery case and performed a restart and still went straight to the SPL with almost no delay. The camera button depresses properly and doesnt seem to be stuck.
After all this, I figured I should just start off fresh, so I flashed the DREAM.nbh for RC29 that is listed everywhere in order to get root. On restart, I held down the camera button, and the white screen comes up to ask if I want to boot image.
I do, and everything goes off without a hitch, I press action key to restart and end up at the SPL screen again, this time, my radio is down to v1.2 instead of v2.2 so I know I changed something. I have done this update twice just to make sure everything is going right but I am still stuck at SPL.
Sorry for the extensive post, but as you can see, I did a bit of trouble shooting before I posted this.
1 did that
2 did that regular recovery
3 can not boot into system on 1.5 cupcake signed-kila-ota-148830.de6a94ca.zip
4 tmobile usa

anything i know its not bricked

OK you have rc29 installed. That is the original android with 1x radio. So software wise you are fine. (Ie not bricked)
The problem is you need to enter normal boot and are always entering the spl instead?
My guess is the camera button is stuck..
The real button is surface mounted on the main board what you press is a user friendly piece of plastic on top of that, attatched to the phone's cover.
If you have any warranty get T-Mobile to take a look.. Otherwise you can try opening it and cleaning it out.

i tired that and i actually switched the mother boards and check the buttons and nothing is stuck when i update to rc29 it lets me when i update to cupcake it lets me the text even changes on bootloader but not actual boot

Hangs on TMobile splash, no recovery but SPL works

Hey all.
I've spent about two hours combing the forums and other resources here and can't seem to find a straight answer. I'm new to this, and may not be using the correct search terms, so I apologize if this has already been discussed in great detail (and I'm sure it has).
I acquired an old TMobile G1 from a friend. Turning it on dumps me to the carrier splash, and hangs there indefinitely. Recovery mode using Home + Power doesn't work. However, Camera + Power gets me into the Rainbow SPL, and from there I can succesfully flash DREAIMG.nbh from an SD card. However, upon rebooting, the system still hangs at flash. I can re-flash DREAIMG as many times as I want, but nothing ever changes.
Info from SPL:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
Am I flashing the correct image? Does something else need to downloaded or placed on my SD card for this to work. I'd like to stress, this is the state I received the G1 in, and I have no clue what was done to it before.
Thanks in advance for any help you guys can provide!

go here:http://forum.xda-developers.com/showthread.php?t=442480
and start with rooting rc29

Already tried that, sadly. RC29 is the NHB I've been working with all this time, and I still get nothing after flashing that from the rainbow SPL.
EDIT: Also, I have no clue if this means anything, but I left it to charge earlier, and when I came back a few hours later, the keyboard lights and face buttons were all lit up. Is that normal?

Set it to boot NORMAL and LEAVE IT TO BOOT. This takes a while. Don't panic when it doesn't boot up in 3 seconds!

It's been about 40 minutes. Think I should leave it a little while longer?

SteveZissou said:
It's been about 40 minutes. Think I should leave it a little while longer?
Click to expand...
Click to collapse
No, now reflash RC29 and try again. If it still takes >= 40 minutes, then your hardware's fried.

Another thread of "My G1 won't start"

hello all, i need help again this time.
let's get to the point.
this morning, i tried to charge my G1 because the battery has yellow color.
when i charged the phone, after around 5 minutes, suddenly my G1 restart itself and then after the "G1" logo, the screen go all black, sometimes not all black but there's a little glitch (white-green-purple-all little colors.)
the phone got heated on the bottom part everytime i power-on it, even just on battery (not charged).
i tried "Camera + Power", it's only getting to that red-blue-green-white screen that shows :
"DREA100 PVT 32B
HBOOT - 0.95.0000
CPLD-4
Radio-2.22.23.02
Sep 2 2008
Serial0"
Click to expand...
Click to collapse
and it stops there for AGES . won't do anything.
i tried "Home + Power", i tried to hold down that two buttons for 25 second more, but it keeps normal boot, shows G1 logo, and then black screen again.
i tried "Menu + Power", it just the same as "Home + Power"
my G1 has never been rooted, it's all original, i haven't done any system upgrading-downgrading things.
the charger is the original one, original from htc
the battery is new, i've just changed it one month ago.
that's all the informations that i can give.
so, anyone can help me solving this problem?

no one's wiling to help me?
anything you can say is helping me.
is my G1 bricked? but i didn't do anything to the system, not rooting nor flashing etc.
just normal charging and everything bad happened

It's not bricked. Hopefully, all hardware is still working. I'd say try for warranty stuff first, but if you have to, you could try downgrading using the DREAIMG.nbh then upgrade using the various zips (check unrooting guides, they have upgrades from 1.0 [dreaimg.nbh] to 1.6, latest update)
I don't have any links, but google is your friend.

Tony_SpaZ said:
It's not bricked. Hopefully, all hardware is still working. I'd say try for warranty stuff first, but if you have to, you could try downgrading using the DREAIMG.nbh then upgrade using the various zips (check unrooting guides, they have upgrades from 1.0 [dreaimg.nbh] to 1.6, latest update)
I don't have any links, but google is your friend.
Click to expand...
Click to collapse
DREAIMG.nbh is the RC29 right?
only the image, and i don't need any SPL or update.zip, right?
i guess i'll try this one, thanks

Please abide by forum rules. No need to create 2 threads on same topic. Thread closed

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.