Database Users

G1 won't boot

I bought it yesterday from some guy on craigslist with a dead battery, but after chrarging it with my carger it would not boot, just the G1 screen. i can not enter the recovery menu, but the boot loader menu does work. Is there anything I can do? I tried reloading the rc29 Dreaimg.nbh, but won't boot. It has the pvt 32b and seeing as how that one is easier to root, I am hoping it's a random issue and not a rooting brick.

As a side note, I have searched. through millions of forums, google, and even my attic for answers. there is always people who get no recovery and no Boot loader screen, then there are those who can access both, but I have not heard of one who can access one witout the other.

did the guy tell u if it had been rooted? if so you can flash a custom recovery image
do you know how to use fastboot? if not have a look around and then try this:
try flashing cyanogens recovery image found here:
http://forum.xda-developers.com/showthread.php?t=523558&highlight=recovery
hopefully this will allow you to do a wipe and flash a new image
if you cant do this give me a shout and il think of something else

The guy did not tell me it wouldn't work, he said it worked fine and then this happened. i traded him an old PSP I had laying around for it, so no big loss on my side. I have emailed him, but no response. Well, How would I type in those commands? Through the phone, or the PC? Thos directions are pretty unclear.

what happened when loading the Dreaimg.nbh
Did it successfully do it? It could take a while to boot afterwords so be patient.

find a guide to setting up fastboot.if ur running windows i cant help but if u run ubuntu or some other linux i can....
after setting up fastboot
boot into the spl by holding camera+power with the usb plugged in
and type the commands in on the computer (again just follow instructions on using fastboot)
its the 2nd set you should use, the ones with "fastboot clear...." etc

Oh thanks. I have jaunty installed on my other pc will see how that goes. The dreaimg.nbh file worked. No errors. Do I just restart with green+menu+red, or was I supposed to wait?

restarting should have been fine...
http://forum.xda-developers.com/showthread.php?t=537508
you may find this useful when trying to set up fastboot in jaunty....
remember when you first plug the phone in to type "sudo adb enable-server"
then "adb devices" to make sure it is detected
the first command needs to be sudo whereas the other doesnt otherwise your device wont be detected
adding the line to bashrc didnt work for me so i tend to do it from within
~/androidsdk/tools/
and it works perfect
good luck
if u dont get a reply here i may not be looking at my computer, so u can email me or gtalk me on [email protected] and il always get it (tnx to my g1 )

I was successful in running all the fastboot/adb files in Windows, but while doing some more research, I don't think this phone was rooted. I am not getting the fastboot menu when I hit back button and my PC won't read the phone.

Last night I found out that after leaving it on for like 15-20 minutes it restarts, but after the second restart the phone died. It had been charging all day as I was using it. Seeing as how it was plugged into the PC. I am heading to a t-mobile store and am going to see if I can get a hold of an extra battery, not buy one mind you just ask "politely" to see one. Seems crazy, but I have a hunch it might be that my battery has gone dead. None of the nbh files I tried did anything except the rc30, that one caused my phone to start restarting, before it would stay on the g1 one for more than thirty minutes without a restart.

Sounds like its unrooted and stock but somehow has a corrupted rom.. It should be recoverable. Try the goldcard method to get RC30 on there:
http://forum.xda-developers.com/showthread.php?t=485364

I have been reading through that thread, but I have no idea how to actually use the goldcard that was generated. Anyone can help me through it seeing as I can not enter commands from my phone.

Ok I went to my Mac because dd command does not work under cygwin that well for me( I'm more familiar with terminals from ubuntu and OS X) Well I can't get the goldcard.img onto my micro sd card. I have been reading and no one seems to have any troubles other than actually generatiiong the gold card. I will report back after I finish the whole thread. Also they suggest an allocation size of 4096, but my sd card only gooes to 100* something.

ok, bad news, I just finished the gold card instaallation and put my sd card into my phone. Now it won't go to the bootloader. Too bad.

Good news. Yesterday I tried to boot it while placing the phone in a drawer and it booted to the recovery menu! I did not have an as card at all so there was nothing I could do so I tried to wipe everything and it finished, but it went back to where it was. I had left it in blue light mode all night. So last night I left it to try and redo what I had done, but it did not work. Atleast it goes back to the bootloader. Gold card did not work but I blame it on the CID number. I can't seem to get the right one. I'm looking though.

I realized what I did. I did not mess with it. I took the battery out last night an did not touch it till just now and it booted to the android screen then froze and restarted and went back to the G3 screen I'm going to leave it like this and see if it gets fixed by tomorrow. Than while booting try to get to the recovery menu. Hopefully it will fix the problems. I seriously think it might be the battery. Tmobile store did not have a spare one though.

Just a suggestion, may or may not work.. I got a new G1 the other day, and have rooted it, etc.. Mine did the same thing, on the G1 screen for hours, never left it.. Take the SD card out of it, and try to start it.. Mine would not load due to the partitioning, I had a 47mb ext2, a fat32, and another ext2 partition, which caused it to hang on the G1 screen.. If no luck there, this site is what helped me root mine, gives the files, and the steps.. http://www.getyourdroidon.com/wiki/index.php5?title=How_to_Root_your_G1
Just take the sd card and put it on your computer via an adapter or something to copy the files (Make sure it's formatted fat32)
If by some reason, my explanation above did work, use partition manager 9 to fix the card.

I booted it withoutth sd card, but same deal. Left it without the battery last night and got it to the recovery menu but would not find the update file. Ended up freezing on me so I went ahead and rebooted. Same deal. I guess I will try again tomorrow.

Phone booted up, was entering my log in info and it froze.... I'm still trying to fix this.

At this point, I would try to go completely back to a fresh OEM install, which I'm not sure you've done since you started to get access to Recovery.
Download the original T-mobile bootloader. Rename it to update.zip and copy it along with dreaimg.nbh to the SD card. Enter Recovery and alt-s to install the bootloader... reboot using Home+Back. It will probably lock up at some point as it's been doing. Turn off the phone and get into bootloader to flash dreaimg.nbh.
Report back after you do this.

Help needed to fix rooting gone wrong

First off im sorry im adding another rooting post to these boards.
So i decided to root my 32B magic today copyed the recovery.img over and update file from the rooting wiki, loaded recovery mode then updated, but now my phone when turned on loads to the vodafone screen and freezes id left it for afew hrs but still no luck.
Here is what i know so far:
I am able to get to fastboot and fastboot usb
I cant however get to recovery mode by pressing menu+power
I can get to the recovery mode using the sdk\tools
my problem is that im sure the fix is relativly simple i.e. load some files onto sd and start again, but the problem is that i have no other way to load the files onto the sd card than through the phone and my knowledge of adb isnt that great although has improved greatly today lol.
Im not sure how correct i am on this, but would it be a possible fix to load say a rom update.zip onto the sd card and load that through recovery mode to bring it up? If that would fix it could i possible get help on the adb code needed to pass the file from computer to the phone through fastboot usb or recovery.
Thank you very much for your help

Ok i think i have figured how to push files to my sd card however whenever i try it come up saying Failed ( remote:signature verify fail)

ok well i managed to move Cyanogen's newest rom over and update to that but its still hanging up at the vodafone screen upon booting, im lost for ideas.
Please any help how ever small would be amazing right now.

please help is desperatly needed.

i am having the same issue.... and it seems NO ONE has a bloody answer to why it is failing

I successfully update to 32A and root. Then i tried to update to MT3G OTA rom and now i'm stuck at Vodafone screen. Need help or ideas and how to recover..

i had the same problem, what i did was that i found a sd card adapter and hooked it up to my computer, its pretty quick and less hassle

waacow said:
I successfully update to 32A and root. Then i tried to update to MT3G OTA rom and now i'm stuck at Vodafone screen. Need help or ideas and how to recover..
Click to expand...
Click to collapse
take out your battery and after a few seconds put it back in, before it powers up go into fastboot(back+power) and that should do it

I still have a pretty red splash screen and stucked.
neoxtian said:
take out your battery and after a few seconds put it back in, before it powers up go into fastboot(back+power) and that should do it
Click to expand...
Click to collapse
I have same problem, but your solution didn't work for me.
I did as follows.
#1. typed following command in terminal.(well, I'm using Mac)
Code:
fastboot-mac flash recovery recovery-RAv1.2.0G.img
#2. pulled battery off from phone.
#3. pluged USB cable to phone and also Mac.
#4. pressed (ENTER) in the terminal, then fastboot-mac said '< waiting for device >'.
#5. put the battery in while pressing (back)+(power)
#6. then, pretty red vodafone splash screen come up.
#7. In the terminal, it still said '< waiting for device >'. Nothing was changed.
#8. On the phone, pretty red splash screen was still there. Nothing was changed.
Those are all I have done many times for last 2 days.
But, it didn't work.
Please let me know if there is something I missed.

I tried and stuck in the exactly same problem as [robotician]. I have MT3G.

robotician said:
#5. put the battery in while pressing (back)+(power)
#6. then, pretty red vodafone splash screen come up.
#7. In the terminal, it still said '< waiting for device >'. Nothing was changed.
Click to expand...
Click to collapse
THe red vodafone should not come up. You have to hold the back key longer perhaps, because it's supposed to go into the fastboot screen with all sorts of text and three androids on skateboards at the bottom.

@Niaski
was your rom made for the 32B or the 32A?
They are very diferent phones and mixing the roms causes the issue you are seeing.

G1 Reverted to RC29 stuck at "Android system recovery utility"

I have a (formerly) rooted G1 that I've attempted to revert to stock RC29 by following the "Full Downgrade Guide" at the CyanogenMod wiki.
My device had HBOOT-1.33.2005, so I used the suggested fastboot command to roll it back to HBOOT-1.33.2003 from the g1boot.zip file linked on that page. This seemed to go well, after which I rebooted into the fastboot (which was still the skateboarding androids screen) again and saw the new (old) HBOOT in the information.
Powered off the phone, inserted the SD card loaded with the DREAIMG.nbh linked in the page, and reflashed the phone. Rebooted with Send+Menu+End, and the phone kept rebooting at the T-Mobile G1 logo screen.
So, I attempted the flash again from the bootloader menu, which is now the "rainbow" style, and shows HBOOT-0.95.(something). It immediately picked up the DREAIMG.nbh file on the SD card and asked if I wanted to flash, chose yes. Same result again: a boot loop at the G1 logo.
I redownloaded the DREAIMG.nbh file without the download accelerator I'd used before, placed it on the SD card, and booted into the bootloader again, flashed, and still the same looping.
So, I attempted to access the "recovery mode" by pressing and holding menu while powering on. I got the G1 logo, then a black screen... pressing Alt-L showed "Android system recovery utility", and nothing else.
Now, the phone will do nothing BUT Android system recovery utility, regardless of what buttons I press or do not press, and I have to remove the battery to turn the damn thing off. Pressing Alt-S, Alt-W, Alt-X, or anything else does nothing.
Where should I look to try to figure out how to recover this thing?

Is a simcard in the phone? Can you get into recovery and wipe incase the partitions are confused?
(Edit, the hint was the sim card)

There's no SIM in the phone at the moment. I can't do anything at the system recovery, except turn the log on or off with Alt-L (which I guess means it's not frozen).
It isn't recognized by ADB anymore, since it has some bastardized version of the stock T-Mobile image that has USB turned off (right? I'm new at this. ).

A bit more info:
I can get into "blue light" mode, and the light is amber/green when plugged into a charger. Sometimes, when I plug the charger in the phone will turn on immediately; but not always.
When I start the phone up and it boots into the broken recovery console, Windows does see an "HTC Dream" device, but ADB doesn't see it.

ezterry said:
(Edit, the hint was the sim card)
Click to expand...
Click to collapse
Should I, or should I not have the SIM in? For what its worth, the phone behaves exactly the same either way.
Thanks for the help.

I just had this exact experience; have you made any progress, goatlordbob?

same happened to me.
cant fastboot, loop at G1 screen, and all i can see in recovery is: Android system recovery utility
some1 find some solution?

why doesnt there seem to b any help for this matter, smh

bull.. s**t
I'm in the exact same boat now. I followed those directions *to the letter* and it put my G1 in this state. Thanks to the wiki maintainer for such wonderful attention to detail. /s
Is there NO way to recover from this?

try to flash this nbh file.... http://www.4shared.com/file/9izdCbvo/DREAIMG.html

ldrifta said:
try to flash this nbh file.... http://www.4shared.com/file/9izdCbvo/DREAIMG.html
Click to expand...
Click to collapse
How? None of the key commands work. Like the OP I can hit Alt+L and it shows ""Android system recovery utility" but that's as far as it goes.

Anyone bothered booting using home + power?

shadowch31 said:
Anyone bothered booting using home + power?
Click to expand...
Click to collapse
Yes - T-Mobile G1 logo, then blank screen forever.

[Q] First blue screen, now boot loop.

Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.

Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?

Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.

Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]

I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.

PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)

Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)

Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.

just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..

Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.

hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!

Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started

i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off

astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??

Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little

U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App

all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^

How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link

Looks like you are not having much luck. Did you try to factory reset?

astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much

Bricked Evo... stuck at bootscreen, wont boot into recovery

I just partitioned my SD card and flashed a new rom (RunnyBliss HybriD) tonight. Everything was working fine, I just reinstalled all of my apps and everything was perfect. I went to unplug my phone from the computer (which was on charge only) and just unplugged it. After that, all of the apps I downloaded were gone and the home screen pages that I just setup were gone. I decided to reboot and see what happens and to my surprise it wouldnt boot back up. It is stuck at the white "htc evo 4g" screen. I tried to boot into recovery and it vibrates 3 times and then does nothing. I assume that the phone was actually in USB mode and I corrupted the usb by removing it without ejecting it. Long story short, I have an Evo that doesn't work and I dont know what to do. My computer wont recognize it so I cant access the SD card. Please help.

Correction: If I press volume down I can get into hboot. What do I do from here?

try to install a recovery via the bootloader

How would I do this?

npreisler08 said:
Correction: If I press volume down I can get into hboot. What do I do from here?
Click to expand...
Click to collapse
I'm kind of new to this but, in HBOOT there should be a recovery option, select that and recover the latest backup.
EDIT: If Recovery doesn't load then I'm at a lose, sorry.

I figured it out. I got a new micro usb and placed AmonRA on it and then booted into recovery, then went to usb mode and dropped a new rom on it and flashed. Big bam all fixed