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 =/

UK G1 bricked after installing Shop savvy - help please

Hi guys,
UK G1 (Dream) phone recently updated to the 1.6 build, all working fine.
Yesterday I tried installing the free app Shop Savvy. the phone resetted itself after install and sat on the G1 boot screen permanently.
Now phone will pass this boot screen (Tmobile G1)
Tried:
Recovery mode - will not work at all
Quick boot - brings up the multicolour screen but does nothing after.
**PHONE IS NOT ROOTED**
looks like I have had the phone JUST over a year, not looking good...
Any ideas?

You can boot in to the SPL/bootloader so thankfully you haven't bricked
If you're on a contract with tmo you could take it back to the store and they should give you a replacement, but where's the fun in that?
If you want to fix the problem yourself, all you need to do is downgrade to firmware 1.1, then accept the OTA update to 1.6.
Here's the procedure:
1)Put the phones SD card in to a card reader and format as fat32
2) Extract this file and copy it to your SD card as 'DREAIMG.nbh'
3) Put the card back in the phone and hold down power and camera to boot in to the bootloader.
4) Flash it. (Action button is the trackball).
It's a good idea to leave the charger plugged in and have a decent amount of charge in the battery (eg 40%+).
Afterwards the phone will restart and you will need to re-enter your google account info. All your apps and data will be gone, but there's not much we can do about. You can set things up and install apps while you wait for the prompt to update.

Thanks alot AdrianK,
Really appreciate the steps and info, nice one
I have done some flashing on other phones etc so I have no problem with this. However, I am wondering how a normal app such as Shop Savvy could corrupt my ROM and am wondering if it might not be better to get a new phone as this one could have hardware fault?
What do you think?
Silver.

OK,
did exactly as you said Adrian. Phone went through all the flashing routine then, right at the end said press action button to continue (trackball) every time I press the trackball phone returns to the bootloader screen
What now?

SilverfoxUK said:
OK,
did exactly as you said Adrian. Phone went through all the flashing routine then, right at the end said press action button to continue (trackball) every time I press the trackball phone returns to the bootloader screen
What now?
Click to expand...
Click to collapse
I think you can take the battery out restart the phone

Thanks but unfortunately I have already tried that.
Phone just sits on the G1 boot screen as before...
Any other Ideas?
is that ROM you linked for me a UK ROM Adrian?

Once you get to RC7 use these to build back upto 1.6
http://code.google.com/p/official-android-firmware/downloads/list

SilverfoxUK said:
Thanks but unfortunately I have already tried that.
Phone just sits on the G1 boot screen as before...
Any other Ideas?
is that ROM you linked for me a UK ROM Adrian?
Click to expand...
Click to collapse
Yeah that's the RC7 ROM, the UK ROM for 1.1. RC29 is 1.1 for US phones.
This is all very odd, especially that it was an app that caused it, or as you suggested possible hardward failure. Oh well, I guess all you can do now is take it back to tmo.

[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 at the X, move on to a new phone?

I recently bought this Nexus off eBay and it worked fine.
Owner said it had problems with the SD card, but it seemed to be working, for they said it wouldnt read, when it does.
Anyway, it had cyanogen mod 6.1.1 on it, and I hate the setup...so i changed roms. That was a success, but when i flashed a sense rom thru clockwork(most updated) it said:
E:Error in /sdcard/N1Sensation_v0.4.zip
(Status 0)
Installation aborted.
Now, when i flash any roms, whether it says it installed correctly, it doesnt change anything. Now it's stuck at the 4 color x with the unlock icon. Any advice is good advice!
In my hboot, it says:
*** UNLOCKED ***
NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0b15
TOUCH PANAL-SYNT0103
RADIO-5.00.00.04
Oct 12 2010, 14:33:16
HBOOT
Etc. Etc. Etc.
Thanks for any help!
Edit: I fixed the issue with why it failed, was my fault, didnt partition the card...but i was flashing a stock rom and it said complete and when i rebooted it stayed at the X and then powered off. Since then has never turned on. I don't know what to do. Nothing will turn it back on. I have a universal charger that charges the battery and it said the battery is full. I need help!

Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??

Dude Random21 said:
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Click to expand...
Click to collapse
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.

matistight said:
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
Click to expand...
Click to collapse
Try flashing CM7. Also...before you do...you may want to search for a format.zip from a member named temasek. It'll wipe your phone...clean. Real clean. Then flash CM7. try that.
also....those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.

SiNJiN76 said:
Try flashing CM7.
those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
Click to expand...
Click to collapse
I can't flash anything. Phone wont react to anything anymore. Hoping one of my family members can fix it. But if I get it on I will try that.
I am pretty sure i waited long enough, but who knows. I didn't partition my card, which may have been the problem. And also it was S-On....which i thought was odd when it had a custom firmware.

Unlock bootloader. Flash recovery. Boot into recovery. Wipe everything. Flash rom.

Why do you guys keep suggesting software stuff when it's probably a hardware problem he can't get the phone to boot up so he can't do any of that.
Although there is one thing I want you to try before your family take a crack at it to take it apart and what not, it's a long shot but it's your last chance if it's software. Hold down trackball and press power keep holding trackball for another 5-10 seconds (better to long then to short) then connect it to the computer via USB you could see a popup notification saying that it's looking for driver software if you do then it's software and we need to reflash everything and might need to unlock the bootloader. Now if you don't see a popup notification I would still go check in the device manager and check for an unidentified device probably in other (it should be extracted so that you can see it).
If this doesn't work then sorry but I think it's a brick

Because in order to find out if its truly a hardware problem you need to try every software fix first.
Op mentioned nothing of trying fastboot as well. Software fix is free hw is not. That is why we suggest software fixes.
Sent from my Nexus S using XDA App

Let me remind you guys, THE PHONE WONT TURN ON AT ALL REGARDLESS OF WHAT I DO. I can post a YouTube video to show everything. It'd be very random for it to be hardware because it just turned off and will not turn back on. If there is any software like an RUU out there, that would help, if not, ill have to buy a bottom piece and warranty it out. But I'd feel bad because that isn't the right thing to do.
I don't expect you guys to fix it and I and very thankful of your help! But the phone won't turn on at all. So telling me to flash roms doesn't work. Imagine it as flashing a rom with the battery out of your phone. I am wondering if there's an adb way or something to get it to turn on and restore to stock?
With all that said, any help is amazing help and I am very grateful that this isn't a post I have to bump! Thank you so much, when I go on the PC, ill thank the helpful posts
Sent from my (finally) permanent root Sensation 4G

Then it is a brick if it won't turn on at all. The entire getting stuck at the x thing confused me to think it was powering on.

You have me confused sir, I'm not quite sure what good it is your looking for a RUU for. If the phone truly won't turn on/go past the X screen and you have it on a charger with no LED notification, then the phone is bricked. When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom. If you can still get to the bootloader screen then you are not bricked and should retry everything from scratch.

Thread Closed
xsnipuhx said:
When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom.
Click to expand...
Click to collapse
Sensation based, but it was a Sense rom
Confirmed it is bricked.
Sold on eBay for $100
Bought for $77
Semi-Winning.
Thread Closed

[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!