Database Develop

HELP: G1 not powering up

Hi,
i just reflashed my mobile this morning(GMT+0800, CST)
first, i flashed current radio
then, danger spl.
now, cannot power up. removed battery and tried several times without any respond.
so, what can i do?

what can you do?
get a new g1. after you flash danger, ur supposed to press home + back, not using the trackball. then your suppose to reflash your rom. if you cant turn it on, your bricked.
tell the rep it shut off while updating to cupcake and wont turn on. good luck
the members of XDA have no sympathy for you.

Lets verify it's a true brick before you give up on it.
1) did you check to see if your G1 is a PVT?
2) when you say "won't turn on" what exactly are you seeing? G1 screen? completely dead?
3) does holding camera and power to turn it on do anything different?
4) does holding home and power to turn it on do anything different?
Also, Don't mention anything about cupcake. Just say "the phone wanted to apply an update and this is what is does afterwards". Play dumb, you don't know anything about cupcake, donut, or any other pastry.

same problem
my phone is a PVT
did camera and power and it is stuck @ the screen
*my phone did this while trying to do a hard reset*
*I was unsatisfied with my cm 4.0.4. compatiable theme made by ENOCH v1.4 i believe*
*i did the reboot and pressed alt+w and it still took me to the enoch screen*
help please

my phone is a PVT -- GOOD
did camera and power and it is stuck @ the screen -- WHAT SCREEN, DETAILS PLEASE
*my phone did this while trying to do a hard reset* -- OK
*I was unsatisfied with my cm 4.0.4. compatiable theme made by ENOCH v1.4 i believe* -- OK
*i did the reboot and pressed alt+w and it still took me to the enoch screen* IS THIS REBOOT USING HOME+POWER?
help please

*I was unsatisfied with my cm 4.0.4. compatiable theme made by ENOCH v1.4 i believe*
Click to expand...
Click to collapse
OH serious business there, i heard that this theme maker added special code that if badmouth his theme it bricks your phone, lol

*it goes to the rainbow screen*
*quickly flashes to "loaiding.....no image file*
*then It gets stuck at the rainbow screen*

Fingerlickin said:
my phone is a PVT -- GOOD
did camera and power and it is stuck @ the screen -- WHAT SCREEN, DETAILS PLEASE---answered above
*i did the reboot and pressed alt+w and it still took me to the enoch screen* IS THIS REBOOT USING HOME+POWER?--------yes
help please[/QUOTE
Ive been on this site for hours trying to find answers to no avail
list of things ive done
*tried to update to new cm but download was unsuccessful, one remedy was to do a factory reset and i am @ where I am now*
*reformatted sd card*
*2 reflash to stock methods*
*i get to g1 screen and then it shows the ENOCH screen and stays there*
Click to expand...
Click to collapse

stefan.buddle said:
OH serious business there, i heard that this theme maker added special code that if badmouth his theme it bricks your phone, lol
Click to expand...
Click to collapse
lol well sheesh it shouldnt be so laggy!

If you see the bootloader screen then you still good, you ain't bricked.

supremeteam256 said:
If you see the bootloader screen then you still good, you ain't bricked.
Click to expand...
Click to collapse
what does it mean when I'm stuck @ the enoch screen/black screen/ can get my phone to fully function?

Can you boot into recovery by holding home and press power?

Fixed
I figured it out and just reflashed the rc29 update. I had to go through 3 sd cards but it worked out. Internet was also out for a majority of the day so it stopped me from beable to respond. Thanks for the assistance thought folks!

hiphopsg1holder said:
I figured it out and just reflashed the rc29 update. I had to go through 3 sd cards but it worked out. Internet was also out for a majority of the day so it stopped me from beable to respond. Thanks for the assistance thought folks!
Click to expand...
Click to collapse
Well you didn't have to go back to RC29. All you had to do is load another rom. When you flash the "danger" spl it erases your current rom, that's why everywhere it says you must flash another rom right after it. I guess people don't read anymore.

supremeteam256 said:
Well you didn't have to go back to RC29. All you had to do is load another rom. When you flash the "danger" spl it erases your current rom, that's why everywhere it says you must flash another rom right after it. I guess people don't read anymore.
Click to expand...
Click to collapse
The goal was to get it back to factory so I can return it....Sorry to upset you sir with my lack of reading skills =/

G1 possibly bricked; stuck in recovery console [researched]

i will try to be as detailed as possible. im coming from the kaiser community so go easy on me
when i had recieved the phone it would turn on go past the tmobile g1 screen and go into the recovery console. the console read. JF 1.41.
after reading around the best option i got was reverting everything back to factory settings.....and so i did. i installed the factory spl went back to rc29....then updated to rc 30 and installed the new cupcake.
everything was fine except for i couldnt get the phone activated given im an AT&T user.
this morning i finally recieved the unlock code from tmobile and when i turn the phone on with the att simcard, it gave me the triangle with the exclamation screen.
so i hit alt +l then alt w and after a reboot it would bring me back to the same screen. Also this recovery screen is diff from the jf 1.41 (im guessing this is the factory console).
now im out of ideas as to how to get this phone back in order. i would love flashing the DREAIMG.NBH but sadly my phone refuses to go in bootloader.
ive been trying to hold camera+ power and its jsut loads up the tmobile g1 screen.
any and all advice/helps are appreciated.
-thank you

so this is totally weird. i leave the phone unplugged with the battery out for about 3 hours. came back to work on it....turned it on and well it loaded and got me to the home screen ( no sim card ).
so i powered off the phone and inserted the AT&T simcard turn it on and it shows me the same screen again with the triangle and exclamation point.
how do u explain that ?!
pressed power for 3 seconds and then let go and held down the back key. it flashed the bootloader tricolor screen and then said ""everything will be reset to factory defaults .press send to reset"" and when i did that there was no change........nothing happened. ended up pulling the battery out..

Same problem..
I have very similar problem.. but mine takes much more than 3 hrs to come back.. and even then , the task manger keeps popping up from time to time in the home screen ,, so i guessed my home button was stuck or something...
After i found your "problem Sovled" post in another theread on 11th oct ..i thought i better take your suggestion before taking phone apart..
I was on 1.5 version and 2.22.19.26I radio. also i do not know whether i'm in RC29,30,33 ..
i'm really confused about all this radio,firmware ,recovery things....
Please Guide me ..

well first you need to get in your ph to find out if u have rc29. if you are able to get to home screen just hit menu - setting - about phone - all the way down it'll tell you what you are running.
i followed this guide to help me flash it to the cyanogenmod rom
http://forum.xda-developers.com/showthread.php?t=563679
hopefully it helps. but if you are able to get into bootloader unlike me then jsut flash the rc29 hopefully it will solve your problem.
my home key acted like it was stuck but now everything is working fine.

Thanks for Replying so quickly ..
I managed to go to the bootloader screen(tricolor) ..actually it went without even pressing the camera button(any idea why??) after leaving the phone without battery for about 5 hours.. and i flashed the Dreaimg-RC29 file .
Since then i'm Stuck in recovery mode again.. but this time the recovery utility is different (yellow letters)..i.e hopefully RC29 is succefully installed.
I wanted to complete doing your suggested guide before asking any more questions, but now i unable to so what shud i do now?
IS the task manger popping up involuntarily sometimes for you in the cM builds?
Can it be that you had a hardware button issue, which somehow rectified itself when going to Cyanogen..
I really appreciate your taking time to answer my questions ..

well sounds like jsut what had happened to me.
make sure you have tmobile simcard on you with a dataplan.
you're going to have to leave your phone off without the battery or just turned off for a while. from here on out it was trial and error. i kept trying to turn the phone on hoping it would go past the recovery screen once it did i activated the phone and finally completed the root process.
as for the cyanogen mod rom i think you are right. though on my initial flash i had a bunch of force closing apps but it all fixed itself upon a restart. ever since then i haven't seen the recovery mode every time i boot it.
PS: that reocvery mode that you see is the stock recovery meaning yes u have flashed RC29 sucessfully.

so i jsut flashed to CM 4.2.3.1. and well im back to square one. im booting into the recovery by default. obviously confirming my doubts about the hardware problem.
im going to try and leave the phone off for a while and see if i can get it to load up. usually that solves my problem.

Oh..
Thats depressing.. Anyways... Lets do it together then I have kept my phone unsed for about 16hrs now.. hope it works ..
Have you tried the HTC Diagonistic program for g1 (DREADIAG.nbh) ?.. I am yet to try it out as i cannot go to the bootloader..
http://www.megaupload.com/?d=7NRX7H40
which version of cyanogen were you using before this happened?

i have not tried diagnostic. iw as going to use ADB to push the recovery on there but it went into bootloader.
i was using cyanogenmod rom 4.1.9999. now i have updated to 4.2.3.1.
actually iw as working on it last night. i re did that whole guide except for downloaded the new rom and flashed it.
so as of now once again that hardware flaw is gone and the phone is working fine.

mtkhalid said:
i have not tried diagnostic. iw as going to use ADB to push the recovery on there but it went into bootloader.
i was using cyanogenmod rom 4.1.9999. now i have updated to 4.2.3.1.
actually iw as working on it last night. i re did that whole guide except for downloaded the new rom and flashed it.
so as of now once again that hardware flaw is gone and the phone is working fine.
Click to expand...
Click to collapse
Did you update from 4.1.9999 straight into 4.2.3.1? If so, that's the problem (maybe).. I suggest you install the HTC 1.6 ADP Rom (link in the cyanogen 4.2.3.1 post) then upgrade to 4.2.3.1. Make sure everything is updated.... rom, recovery & spl (before you upgrade SPL make sure you have the most recent radio version first! or you'll brick the phone). then give it a try and see what happens...

you are right. the first time i just flashed the new rom. the second time around i followed the guide except for i flashed the latest cyanogen rom.

I'm not able to make it go to the home screen even after so many attempts..
i could only manage to go to the bootloader screen once and flashed the RC29 and i'm stuck there
Can you elaborate on how you got to the Home screen , like how long you keep it off or press which buttons to start ?
I'm not in the US , and have bought this phone from Ebay (new, never used) from a seller with good feedback for G1 (wanted this phone very badly). I was using the phone for barely 3 days when i did a factory reset from the phone and this problem started occurring .
IS there anything else i can do..?
Thanks for Helping..

Still waiting for your answer

SaiSantoshD said:
I'm not able to make it go to the home screen even after so many attempts..
i could only manage to go to the bootloader screen once and flashed the RC29 and i'm stuck there
Can you elaborate on how you got to the Home screen , like how long you keep it off or press which buttons to start ?
I'm not in the US , and have bought this phone from Ebay (new, never used) from a seller with good feedback for G1 (wanted this phone very badly). I was using the phone for barely 3 days when i did a factory reset from the phone and this problem started occurring .
IS there anything else i can do..?
Thanks for Helping..
Click to expand...
Click to collapse
how did you flash the RC29? after pressing the power button
did it give you any errors? once its flashed, reboot by pressing home and back (or w/e the SPL tells you to)
it should boot into the rom

Home button problem (repaired/solved)
Firstly, thanks for responding ..
I had flashed RC29 when it had gone to the tricolor bootloader screen on its own
but after that it would not go anywhere other than recovery(exclamantion mark)
Now good news
4 hours back i opened the phone again(third time) , and took a safety pin and started scraping(gently) the non shiny parts of the connector ( daughter board to main board) .
I think it was previously shorted near that area , so by scraping removed the shorted metal joints .. and now the phone booted up to RC29 (just like that) and i even installed the cyanogen mod ..
Many thanks to u all .. hope this Comes UP in google search for people with similar problems(and there are many)...
KEYwords: Home button stuck on recovery no booting

Ah wow didnt think of that lol.. glad to see you got it to work

Stuck on G1 Logo.

Alright here's what happened. I went to root my new G1, I started to follow the steps from the Unlockr but stopped halfway through cause i thought i was going in circles I had finished at "rooted" my phone when i looked in the "about phone" i thought for sure that i hadn't. So i went and did Androids world but when i did the first step my phone got stuck. I thought it was bricked but doing some reading think its soft bricked. But i don't know what to do, i cant get to the rainbow screen or the Home+Power screen only the G1 logo. What do i do?

did you flash the the spl and radio, and flash the right one first ?

jad011 said:
did you flash the the spl and radio, and flash the right one first ?
Click to expand...
Click to collapse
I actually never got to that I don't think i ever officially rooted my phone.

Place your phone on a stack of papers and get a new one

Mjolnir106 said:
Alright here's what happened. I went to root my new G1, I started to follow the steps from the Unlockr but stopped halfway through cause i thought i was going in circles I had finished at "rooted" my phone when i looked in the "about phone" i thought for sure that i hadn't. So i went and did Androids world but when i did the first step my phone got stuck. I thought it was bricked but doing some reading think its soft bricked. But i don't know what to do, i cant get to the rainbow screen or the Home+Power screen only the G1 logo. What do i do?
Click to expand...
Click to collapse
I'm going to be real lazy and ask you to post links to the guides you used
I would google them myself , but busy and seeing as you have them in your internet history...
when is an url not an url?
when http is hteeteep
I will then have a look and see just what damage you may have done and if it can be undone

[Q] HTC White Screen - Bricked?

I have searched here and Google but can't seem to find the exact problem that I am having. Most similar issues are with different phones and I haven't found any solutions for the HTC Hero. I have been rooted for a couple of months and using CM6 (stable and nightlys) without any problems whatsoever. I have (had?) Clockwork recovery. My phone was running perfectly this morning and the battery was pretty low (down to 10%) so I pulled it and put in a fully charged battery. Now my phone won't boot past the HTC white screen. I can boot into HBoot ONLY (three skateboarding androids) and the screen shows:
HERC XC SHIP S-ON
HBOOT-1.47.0000 (HERO20000)
TOUCH PANEL-SYN0104
RADIO-2.42.01.04.27
Mar 1 2010, 16:02:39
I have tried all the options on HBOOT and can get into FASTBOOT but am unable to reset device, go into recovery, etc. It just goes back to the white HTC Screen after choosing one of these options and never boots up. I've tried with the SD card in and with it out. I even tried to RUU with the .5 Sprint official release but when I run it, the program said my phone was not found and told me to make sure it was plugged into the computer which of course it was. I also tried to run the RUU in FASTBOOT USB mode but still receive the same error.
When I run adb shell on my PC it says the device was not found. When I'm stuck on the white HTC screen if the phone is plugged in to the computer and I unplug the usb from the phone it vibrates 5 times quickly and the screen goes off, but the green notification light is blinking. From this state I am unable to power up the phone at all without a battery pull.
I just don't understand how my phone can go from being PERFECT to FUBAR when the only thing I did was replace the battery. I'm hoping someone can help me. I am eligible for an upgrade but really don't want to spend the $$ right now for an EVO or Epic when my area will never see 4g and the extra $10 is ridiculous.
My setup prior to this morning when I pulled the battery:
Clockworkmod Recovery
CM 6 nightly (Full-73)
BFS #11 kernel
FireRat custom data partitions
And I was rooted with Universal Androot

Have you tried booting into recovery by holding Home and pressing Power? From there you could try wiping everything then reflashing the ROM of your choice.
Have you tried putting the original battery back in and just recharging it fully, then trying to boot?

chromiumleaf said:
Have you tried booting into recovery by holding Home and pressing Power? From there you could try wiping everything then reflashing the ROM of your choice.
Have you tried putting the original battery back in and just recharging it fully, then trying to boot?
Click to expand...
Click to collapse
When I hold home and press power, I just get the white HTC screen of death. When I hold volume down and press power, I get the HBOOT screen and when I try to boot into recovery from that screen it again gives me the HTC screen of death. There is no way past the HTC Screen other than HBOOT and Fastboot. I also charged the phone with the original battery as you suggested and it still did not boot up beyond the HTC screen.
This afternoon I was in the FastBoot screen and plugged my phone into the USB that was connected to my computer. It changed to FastBootUSB and I was able to run the RUU. The program said that the ROM was successfully updated but I sat there for an hour with another white HTC screen before I unplugged the USB and then the phone shut off and I got the 5 quick vibrates. I really think it's toast. RIP, it was such a good phone!

debh945 said:
When I hold home and press power, I just get the white HTC screen of death. When I hold volume down and press power, I get the HBOOT screen and when I try to boot into recovery from that screen it again gives me the HTC screen of death. There is no way past the HTC Screen other than HBOOT and Fastboot. I also charged the phone with the original battery as you suggested and it still did not boot up beyond the HTC screen.
This afternoon I was in the FastBoot screen and plugged my phone into the USB that was connected to my computer. It changed to FastBootUSB and I was able to run the RUU. The program said that the ROM was successfully updated but I sat there for an hour with another white HTC screen before I unplugged the USB and then the phone shut off and I got the 5 quick vibrates. I really think it's toast. RIP, it was such a good phone!
Click to expand...
Click to collapse
Well you'll be the first to kill it this way but I'm sorry to here that and my touch screen is almost toast so ima start a first to
Sent from my HERO200 using XDA App

rulyskull said:
Well you'll be the first to kill it this way but I'm sorry to here that and my touch screen is almost toast so ima start a first to
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Dang, that sucks. I was torn between getting an upgrade or buying a used Hero on Ebay until I find a phone I want. Turns out my phone was only 11 months and 10 days old so I'm still under warranty. My new Hero will be here Tuesday. I'm hoping it doesn't come with the .7 update but if so, I'm hoping I can RUU back to the .5 and re-root. Anyone know if this is possible? Thanks.

debh945 said:
Dang, that sucks. I was torn between getting an upgrade or buying a used Hero on Ebay until I find a phone I want. Turns out my phone was only 11 months and 10 days old so I'm still under warranty. My new Hero will be here Tuesday. I'm hoping it doesn't come with the .7 update but if so, I'm hoping I can RUU back to the .5 and re-root. Anyone know if this is possible? Thanks.
Click to expand...
Click to collapse
Try the one click root(forget What section in here) but ima wait to get the epic or something better
Sent from my HERO200 using XDA App

Have you tried ruu'ing it?
Sent from my HERO200 using XDA App

Vandelay007 said:
Have you tried ruu'ing it?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Yep, I was finally able to RUU while the phone was in FASTBOOTUSB mode and the program on the PC said the ROM was updated successfully but it still never got past the HTC white screen. When I boot into HBoot by holding the volume down/power button the screen flashes a bunch of things so fast I can't read them but it seems like it says something about HCERMG Image Not Found.
The Sprint tech(?) hooked it up and tried to diagnose, install the software but couldn't either. Anyway, since it is under warranty I get a new Hero on Tuesday. I am just baffled at how this happened when all I did was change the battery. You don't realize how much you love something until it's gone. I'm currently using my old Instinct and I find myself constantly turning the screen sideways and wondering why the display won't turn.

Same issue here, (2nd time actually). Last time I was able to put the HERCIMG.zip on the root of my SD Card and then load it with HBOOT, and then I was back to stock and all was good. However since then my HBOOT was updated to 1.47 and now the HERCIMG.zip doesn't work, it says "Main Version is older!" Update Fail!
I haven't figured anything else out yet. Is there an updated HERCIMG.zip for 1.47?

SportsPT said:
Same issue here, (2nd time actually). Last time I was able to put the HERCIMG.zip on the root of my SD Card and then load it with HBOOT, and then I was back to stock and all was good. However since then my HBOOT was updated to 1.47 and now the HERCIMG.zip doesn't work, it says "Main Version is older!" Update Fail!
I haven't figured anything else out yet. Is there an updated HERCIMG.zip for 1.47?
Click to expand...
Click to collapse
Do you mind telling me what you did (twice lol) that put your phone in this unusable state? Like I said I'm not sure how this happened and don't want to repeat it with a replacement phone!

Ok, I put the HERCIMG.zip on the root of my SD Card (found it through Google and had updated 1.47 HBOOT). I booted up holding the volume down and power and the blue progress bar filled up on the right side and when it was finished it went back to the HBOOT screen. I rebooted the system and still have the white screen of death. I'm convinced there's really nothing else I can do to get it running again and must painfully wait until my new phone comes in on Tuesday.

Couldn't tell you how it happened, may have to do with the battery completely dying, but not sure. I tried what you did but got the same results. I think what we need as an updated HERCIMG.zip that works with HBOOT 1.47

While in fastboot, did you try
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash data data.img

unCoRrUpTeD said:
While in fastboot, did you try
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash data data.img
Click to expand...
Click to collapse
I tried all kinds of fastboot commands in FASTBOOTUSB mode through adb but always received the error "remote not allowed" or something to that effect.

debh945 said:
I tried all kinds of fastboot commands in FASTBOOTUSB mode through adb but always received the error "remote not allowed" or something to that effect.
Click to expand...
Click to collapse
What about when you power on the phone normally. You should be able to get into adb shell when it is booting up.
I am going to try fastboot flash boot.img right now on mine and see if I can't get something.
Edit:Haven't tried. Working on a multiboot and now I only have one more obstacle.

unCoRrUpTeD said:
What about when you power on the phone normally. You should be able to get into adb shell when it is booting up.
I am going to try fastboot flash boot.img right now on mine and see if I can't get something.
Edit:Haven't tried. Working on a multiboot and now I only have one more obstacle.
Click to expand...
Click to collapse
If I was not in the FastbootUSB mode, there was only the white HTC screen and adb showed "no devices". I appreciate your help but I can't troubleshoot any longer as I had to turn my phone in to get the new one via warranty replacement. Your efforts might help someone else though with the same problem.
ps, I've been following the multiboot thread very closely and can't wait until this becomes a reality!! That will be so awesome!

debh945 said:
If I was not in the FastbootUSB mode, there was only the white HTC screen and adb showed "no devices". I appreciate your help but I can't troubleshoot any longer as I had to turn my phone in to get the new one via warranty replacement. Your efforts might help someone else though with the same problem.
ps, I've been following the multiboot thread very closely and can't wait until this becomes a reality!! That will be so awesome!
Click to expand...
Click to collapse
Did you pay the extra for warranty or are all heros on warranty for 12 months? Who did you sent the phone to or did you just go to the sprint store?

obsanity said:
Did you pay the extra for warranty or are all heros on warranty for 12 months? Who did you sent the phone to or did you just go to the sprint store?
Click to expand...
Click to collapse
All Heros have a 12 month warranty, I didn't pay extra. I first called Sprint Customer service and since it wouldn't boot for them to troubleshoot on the phone she gave me an Eticket number and the location of the nearest Sprint store with a repair center. I took it in and the tech (?) hooked it up to his computer and could not fix it either so he said he would order me another and it would be here on Tuesday. This was Saturday evening. I received a call today (Monday) from the Sprint Store that my replacement phone was in. Picked it up and rooted it in 5 minutes with Universal Androot, installed Clockwork Mod Recovery, Nandroid restored a backup from the old phone's SD card and I was back in business in 1/2 an hour! Probably TMI, I realize you only asked how I got a new phone but I'm thrilled to have my Froyo back!

Awesome! Makes me feel better trying different ROMs

Funny thing I found this thread, this exact same thing happened to me today.. Hero is completely done.. Getting a replacement tomorrow... I was running firerats also which I can't blame but I'm not running firerats on my new device... Since I installed firerats I've lost 2 8gb sd cards and a phone...
Weird thing is, I had applied the unrevoked-forever and eng spl mod/hack, now when I boot into bootloader it says s-on like what the hell happened? How did I lose s-off and root all together after restarting my phone.

[Q] Stuck in rainbowish seria10 screen

I have been given a G1 because it is "stuck in recovery." I have dealt with quite a few phones in my time, but this one does not appear to be rooted.
Sometimes it boots into the bootloader, where it prompts me to update the image. Once the image is updated it goes into a rainbowish screen that displays:
DREA100 PVT 32B
HBOOT 0.95.0000
CPLD-4
Radio-1.22.12.29
Seria10
Home+power gets me to stock exclamation recovery.
No buttons stuck that I can find.
Googling and searching the forums is just kind of confusing me more. Is the phone rooted? I got it to boot once, but all I could do was emergency call since I didn't have a Sim card in. If I had to make a guess I would say it's running 1.6 based off the notification bar and dialer.

I've flashed a few images, and done a ton of research. Nothing seems to work! If anyone knows anything, please help?

Nonentity018 said:
I have been given a G1 because it is "stuck in recovery." I have dealt with quite a few phones in my time, but this one does not appear to be rooted.
Sometimes it boots into the bootloader, where it prompts me to update the image. Once the image is updated it goes into a rainbowish screen that displays:
DREA100 PVT 32B
HBOOT 0.95.0000
CPLD-4
Radio-1.22.12.29
Seria10
Home+power gets me to stock exclamation recovery.
No buttons stuck that I can find.
Googling and searching the forums is just kind of confusing me more. Is the phone rooted? I got it to boot once, but all I could do was emergency call since I didn't have a Sim card in. If I had to make a guess I would say it's running 1.6 based off the notification bar and dialer.
Click to expand...
Click to collapse
You can reflash your G1 with GoldCard method.

Thanks! I'll gve it a try and let you know!

nhutdm said:
You can reflash your G1 with GoldCard method.
Click to expand...
Click to collapse
I can't seem to get a working goldcard =/
Something I've noticed that's strange is if I don't turn the G1 on for a while it will boot into the OS, but it tells me 'please insert sim' and I can't do anything. If I restart it, right back to bootloader.

Nonentity018 said:
I can't seem to get a working goldcard =/
Something I've noticed that's strange is if I don't turn the G1 on for a while it will boot into the OS, but it tells me 'please insert sim' and I can't do anything. If I restart it, right back to bootloader.
Click to expand...
Click to collapse
In the stickies at the top, under informative links there is a method for registering your device without a Sim using adb to bypass google setup and enabling wifi, and then going back into setup.
Sent from my ADR6300 using xda premium

baboonsRus said:
In the stickies at the top, under informative links there is a method for registering your device without a Sim using adb to bypass google setup and enabling wifi, and then going back into setup.
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
Bookmarked and I'll give it a try next time it decides to boot into the OS.

sounds to me like your un-rooted and on stock 1.0 1.5 or 1.6... with no sim you wont be able to do much, you need to downgrade and run google by-pass method then root it

if the rainbow screen keeps popping up then your camera button is stuck
i highly doubt your phone is rooted, if it is no custom recovery
get the camera button to unstick and then follow this link
http://wiki.cyanogenmod.com/wiki/HTC_Dream:_Rooting

demkantor said:
if the rainbow screen keeps popping up then your camera button is stuck
i highly doubt your phone is rooted, if it is no custom recovery
get the camera button to unstick and then follow this link
http://wiki.cyanogenmod.com/wiki/HTC_Dream:_Rooting
Click to expand...
Click to collapse
I took the phone apart to make sure it wasn't stuck and... it doesn't seem to be. Is there a particular guide for this? Maybe there's something I'm not seeing. Also if the button's stuck then why does it load into OS if I don't touch it for a while?

its probably a little stick not stuck, try using some electronic parts cleaner or rubbing alcohol on it.
the only way i know how to get to the rainbow screen is by holding the camera button down.

demkantor said:
its probably a little stick not stuck, try using some electronic parts cleaner or rubbing alcohol on it.
the only way i know how to get to the rainbow screen is by holding the camera button down.
Click to expand...
Click to collapse
Well, I just took the whole thing apart and air dusted (it's all I have at the moment) and made sure nothing was restricting the button. It is still stuck in bootloader, so I'll try some rubbing alcohol tomorrow and get back to you.
I appreciate the replies!