Stuck at bootloader (rainbow) - G1 Q&A, Help & Troubleshooting

Just received my G1 today. Haven't changed anything, went through first boot, got everything setup to my liking, downloaded a few apps from the market.
Rebooted the phone since it looked like I lost data connectivity, and it's now stuck at the bootloader screen. It doesn't seem that the camera button is stuck, I can push it and feel actually depress. Booted into recovery and did a factory reset/wipe, still no good.
Should I be able to reflash an original ROM image from recovery to get going again? (After I hunt down an SD card)

... how can you be "stuck" at the bootloader if you can already access the recovery?
Couple of things you can try:
1) Reflashing the ROM (since you can access recovery right?)
2) If you're actually stuck in the bootloader and can't get to any other screen, you can try:
Code:
fastboot reboot
3. If that doesn't work, you can try reflashing DREAIMG.nbh (RC29) and starting over.

Yea, it boots right to the bootloader. If I hold power + home it goes into recovery, but that doesn't get me anywhere.
Tried reflashing RC29 via the bootloader. After it's complete, I press the action key to reboot, and it goes right back into the bootloader.
Where am I supposed to enter in "fastboot reboot"?

Is there anything I should try updating at the recovery screen via SD card?

if you just got the G1 recently and you haven't installed any custom software on it and you're already having theese issues why not just exchange it for one that actually works instead of going through the headache of trying to fix it? Especially if the software hasn't been modified and you keep getting thrown into the bootloader

That'll be the next step. I didn't buy it locally tho, through the web, so I'd like to see what I can do before I go that route.

if you use the rc29 DREAIMG.nbh it writes over everything, so if your phone still dosn't load you may have a more serious problem, exchange may be your best bet

I've sent an email to the vendor I bought it from about exchanging it.
I've noticed that when booting into recovery, after pressing alt - L, the top of the screen says :
Android system recovery utility
E:Can't open /cache/recoverfy/command
Then it lists out the Alt commands.

possibly try downloading the DREAIMG.nbh file again, format your sdcard to fat32 once more, let your phone boot into the bootloader and apply the update and cross your fingers and pray to wich ever god you believe in

I've left the battery out all night. I was in the process of formatting the sd at the computer again, and tried powering on the G1. Holy crap it boots up!
Now I'm back to the problem of no data services. I can surf the web all I want on the dash, I know I have a data plan. I'll have to give t-mo a call I guess, since I can't get the G1 registered now.

laszlo462 said:
I've left the battery out all night. I was in the process of formatting the sd at the computer again, and tried powering on the G1. Holy crap it boots up!
Now I'm back to the problem of no data services. I can surf the web all I want on the dash, I know I have a data plan. I'll have to give t-mo a call I guess, since I can't get the G1 registered now.
Click to expand...
Click to collapse
ya i would call t mobile .they would prob replace for ya sounds like some thing weird going on!good luck

Ok, definently sending this back. It has stopped working again. I'd turn it off from the menu, swap out the SIM, and when I go to turn it back on, it'll boot to bootloader again. Reflashed later today for kicks, booted bootloader 1st time, booted up correctly the 2nd time (but didn't have SIM in), booted a 3rd time with SIM in to try to activate, but it went to bootloader again. Any subsequent boots are all to bootloader.
I'm thinking it's crappy hardware.

Still intermittent booting. Until I get the goahead to send it back for an exchange, what else do we think I should try. Could it be the radio version? I tried to update with an HTC radio, but the signature didn't let it load. What, if any, radio downloads will work with a stock G1?
I'll try a few more things tonight, and post up what happens. Maybe check out tmobile's downloads for firmware updates.

If I didn't buy the phone directly from t-mobile, would they be able to do anything for me if I take it in to a store?

laszlo462 said:
If I didn't buy the phone directly from t-mobile, would they be able to do anything for me if I take it in to a store?
Click to expand...
Click to collapse
No they won't. Your best bet is to contact HTC cause the phone is still under warranty, but you better contact them soon cause the phone is about to be a year old on Oct. 20th I believe.

I'll try that then, since all I got for a response from the seller was "has the issue been resolved yet?" I'll check with HTC today about the manuf. warranty.

Related

Tilt Stuck on Boot Screen

I apologize first off for another boot problem thread.
First, I have never messed with my rom. I never flashed it or anything. The most I have done is load KaiserTweak and TomTom. Basic stuff.
I went to turn on my phone this morning and it stayed on the AT&T boot screen. It just freezes. I kept trying to soft reset the phone and at one point it loaded with like the default settings but nothing worked. The start menu only had the Today listed. The phone wouldn't work either. From then on, it always sticks on the AT&T boot screen.
I tried removing the battery and the sim card for a few hours and that didn't help. I tried turning on without the sim.
I am hoping to fix without a hard reset. I don't want to lose all of my contacts and all the data saved on the phone. Is there any way to save this stuff?
That's why you should always have scheduled backups at least once a week. I don't see this being fixed without a hard reset. You did everything that i would have personally suggested (taking out battery and everything for a few minutes). If all fails, you can always go into bootloader mode and reflash the ROM.
Is there no safe mode way to access the device? How about any work around so the computer can access the flash data without the device being in active sync mode?
Highly doubt it and i've never read anything about accessing the device when it's not on. It seems so sporadic and from the looks of it, only a reflash will get you going again.
This reminds me of back when I was trying to flash my Kaiser to 6.1... had exactly the same issues. Even worse actually since the problem started when I flashed a ROM wrongly, also without having an original to fall back to. Cue a night of trying to flash over my mistakes!!
I recall having some success with some specific mtty commands... argh, I'd bookmarked hundreds of threads on it back then but have since lost them all. All I know is there are a few commands you can type which may just get the phone booting again. Bit useless of me but it's a start!!
Ah, check these threads:
http://forum.xda-developers.com/showthread.php?t=371154 This one will erase all data
And post #2 demonstrates use of using the mtty boot command here:
http://forum.xda-developers.com/showpost.php?p=1765045&postcount=2
Those kinds of commands I managed to get my phone working with.
I figured out how to boot to the tri-color boot screen. The computer regonizes it and the boot command in mtty just does the same thing as turning it on.
Since my computer is now linked to the phone, isn't there some way to access files? Any commands in mtty that will work? Any other program out there that might help access the memory?
No one has any ideas about how to access the memory?
Did you manage to fix this in the end?
Got the very same problem with mine which hasn't been flashed in any way.
vigilante_xix said:
Did you manage to fix this in the end?
Got the very same problem with mine which hasn't been flashed in any way.
Click to expand...
Click to collapse
Never was able to figure it out. I had to reload from scratch.
Good luck with your issue. Hopefully some of the suggestions around here and elsewhere will get you back up and running.

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

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.

g1 help, cant get past triangle screen.

Ok so i got this g1 for free. I dont have t-mobile im on att. Im also nostranger to HTC ive been using the Diamond and TYTAN 2 for years now!
So when i first turned the phone on it would boot into android and tell me i needed a t-mobile sim. Well my plan was to get an unlock code and use the phone with ATT. Anyways for some reason i turned the phone on and and it started booting to the triangle screen... Id treid alt l then wiped the phone and reverted back to stock settings but it still boots to the triangle screen. I have no idea why the phone just started doing this. I also have no idea the history of the phone if its ever been rooted or anything. I need to get this phone working again so i can attempt to unlock it.
I tried to follow the unroot article to get back to stock but when i put the spl on an sd card named update.zip it wouldnt install it says no signiture found verification failed. I also downloaded rc29 and renamed it to update tried to install but that failed with a diffrent error.
Im not sure why im going straight to the triangle screen like i said i never screwed with the phone at all i just turned it on and it started doing that. Im turning the phone on by taping the end call button.
I know you said you tried to follow the steps to root the phone but it sounds like you didn't do it the correct way.
If you have the RC29.zip you need to unzip it and move the Dream.nbh file over to the root of your SD card. Then press and hold the camera button while powering on the phone. It will go to a gray screen where it SHOULD say "Press power to install update" you do that....DO NO INTERRUPT THIS PROCESS! and then once that is done you should be back to the very bare bones stock G1. Problem is you need to do more than that to get Root access, and the rest of the steps would require being signed in. There should be a thread on here somewhere about signing in w/o a SIM card which you need to search for and follow.
here is the best root guide if you haven't found it: http://forum.xda-developers.com/showthread.php?t=442480
ya i havent tried the above article yetl i tried to unroot the phone, not root it. Becuase it saidit would revert back to stock settings and im not sure wether the phone has been rooted.
.
I will work through this a little bit later but like i said the phone goes straight to the triangle exclamation point screen where you press alt l or whatever alt combo you want. So there is no way i can tell if its below rc30... Also screwing around earlier i held down the camera button and tapped end call it still went to the same screen with the triangle. Maybe that becuase theres no spl installed? Like i said this phone was working fine and then it just stoped booting into android and started going into this recovery mode or whatever it is, so im not even sure if rooting is what i need to do. As of right now i jst want it to boot up again and tell me no sim card found so i can work from there.
The triangle screen is stock RECOVERY.
You have set the boot recovery flag.
Try pressing home-back when you're in there.
boorishid said:
ya i havent tried the above article yetl i tried to unroot the phone, not root it. Becuase it saidit would revert back to stock settings and im not sure wether the phone has been rooted.
.
I will work through this a little bit later but like i said the phone goes straight to the triangle exclamation point screen where you press alt l or whatever alt combo you want. So there is no way i can tell if its below rc30... Also screwing around earlier i held down the camera button and tapped end call it still went to the same screen with the triangle. Maybe that becuase theres no spl installed? Like i said this phone was working fine and then it just stoped booting into android and started going into this recovery mode or whatever it is, so im not even sure if rooting is what i need to do. As of right now i jst want it to boot up again and tell me no sim card found so i can work from there.
Click to expand...
Click to collapse

Any way to recover from boot loop?

Ok, first of all I know it's been said not to mess with Framework. I read that too late =/
I was trying to install a status bar replacement, which overrides framework-res.apk. It sent it into reboot loop. I can get to recovery screen, but factory reset doesn't do anything of course.
I also can get to bootloader. It gives me the following:
===
Bootloader
29.01
Battery OK
OK to program
Transfer mode:
USB
===
It's connected through USB and bootloader recognizes that. My question - is there a way to push original framework-res.apk back to the phone or is it completely bricked?
I posted in an existing thread about this already, but figured I might have more luck with a new thread.
If you
Code:
adb devices
does it show up? I'm unfamiliar with this type of situation. =p
Oh sorry, forgot to mention that. adb devices doesn't show anything in either recovery nor bootloader.
When connecting through USB and starting bootloader, I can hear the sound of device found on my PC, but it doesn't get found and is listed as "S Flash OMAP3630 MI" with a ? mark in device manager.
Yikes, can't help you with the obvious then (just pushing framework-res.apk again).
Yeah, I was really hoping to somehow get in there with adb
As suggested in another thread, I tried applying .604 update, but it aborts when verifying current system with CityID.apk as a reason. I removed it along with other bloat from the phone.
Also when trying to remove app files I don't have on the phone from update.zip, it fails when verifying the update file.
hey its me again, take a look at this!
http://www.droidxforums.com/forum/d...your-x-stuck-bootloop-you-want-look-here.html
Thanks for the link!
That guy got lucky cause it bricked after he put all the bloatware back on the phone lol. So he had all the default apps. Mine gets stuck when verifying my system and complains about CityID.apk missing. And as we figured out, your previous suggestion with removing files from the zip messes up its integrity.
So I went to a Verizon store and got a replacement ordered. I was afraid they'd start asking if I'd rooted it, but apparently the guy helping me didn't even know what that is He tried a factory reset and then just ordered a new phone.
Thanks for your suggestions, guys!
He may not of known that the x has been rooted yet lol. Or you can just find something small and miniscule to complain about on you phone to get a new one. When the dare first came out I had a new one at the end of every month just for the fun of it. And they where always replaced with a brand new phone. Did that for atleast 5 months before getting a cheap wm phone because they felt bad about all the hassles I had.
Sent from my DROIDX using XDA App
Did the same thing with mine, except my framework file is there, just renamed. I tried last night to figure out how to change the name back with adb but never could.
to the OP, how did you get to that Bootloader? The only thing I have been able to do is get into "Android System Recovery (2e)", which is done by holding Home while powering up the phone. If you hold Home, you'll get a screen with Android next to an exclamation point sign. At that screen you can press Search to open up the menu system, and then you have the ability to reboot, apply update.zip from microSD, wipe data/factory reset, and wipe cache partition.
I am trying to get into ADB so I can potentially work on this phone and fix it. At the moment I am boot looping like nobody's business
-EDIT-
Found the answer myself on this forum: "Hold down the power+vol down+camera button."
This works, but from what I can tell, it puts the phone into a basic USB flashing mode that is useful if you wanna reflash the ROM. At the moment there isn't anything available which could be flashed onto the phone (need to wait for an SFP file?), so I'm stuck waiting.
If/ when the 2.2 update leaks, I believe I can at least try to install that via MicroSD while in System Recovery Mode. I already unbricked my phone once by doing that, but then removed exactly the wrong APKs so now I cannot use that trick a second time
Yep, that was exactly my experience. If I didn't remove bloat apk's, I'd be able to apply .604 update, but...
And yeah, bootloader doesn't do much at this point since we have no way/no ROM's to load.
As far as I remember, Verizon have one month return policy, so I'd suggest just taking it to them. I had my replacement ordered with no questions asked. I just said I was installing an app and it rebooted and went into a loop.

Categories

Resources