Database Users

G1 Black Screen Fix? Bricked?

Hello all,
I have recently upgraded from my g1 to an HD2. HD2 is a great phone but still miss android . Anyways, today I wanted to get my g1 to work without a sim or data plan and was about to start working on it when my g1 screen dimmed to just the blacklight with a black screen. I turned it off and tried turning it back on but it just comes up with the backlight on a black screen. It does not even get to the G1 screen. I cannot get to recovery mode or any other mode for that matter. I have searched around but not found any real solution to this problem (if there is one). I am thinking my phone is bricked but have heard possibilities using ADB. I have never used ADB before and if anyone knows if this is a possible fix to my problem that would be great. It would be nice to know if it actually could fix my problem before looking into it and learning it all while finding out it has no chance of fixing my problem. I have tried using my sim card and a different sd card so those are not causing the problems.
So the background of what I am running on my g1. Right before I got my HD2 I was using Cyanogen version 4.2.14.1 with and ext 3. I had no problems with it until now. I got my HD2 a week ago and my g1 has been on about twice in that time without a sim card just for comparing purposes to the HD2. Then just today (about 2-3 days since I last turned it on) the screen just went black and I had my problems. I cannot return my phone because it has been over a year and I dont have insurance on the phone so these are not possibilities for me unfortunately. I also don't really want to get parts from other g1's and take apart and put my g1 back together. I am just looking for something with ADB or any other possible solution to the problem (if one exists).
Any help would be greatly appreciated!

I had this happen to me before. Apparently, it was a hardware GPU problem that would cause a boot loop because it couldn't draw anything on the screen. This happened on SuperD, AOSP, Cyanogen, and stock Donut.
If your problem is the same, you should be able to get into recovery, regardless of your ability to see what you're doing. Easy way of telling is to hit Camera+End on boot. If it doesn't vibrate, you're able to flash still. You may be able to get the screen back temporarily by either pulling the battery or letting the battery die and recharging.
Anyways, I ended up flashing the DREAIMG.nbh, and trying to upgrade back to 1.6 to remove traces of hacking. (Be careful if you have DangerSPL, you want to restore the default before flashing DREAIMG.nbh) I eventually got the screen working on 1.6, but it died again, so I sent it in to T-Mobile and got a replacement. I'm now using AOSP with no problems.
One small note, however, I did start having my problems using Cyanogen's mod. May want to bring it up with him?
Sorry if this sounds scatterbrained, it's a bit late and I should be asleep right now.
e:Just realized you said the warranty was void. You may be able to get something out of what I did, though? Good luck, in any case.

Thanks very much for the help even though it was really late. I did understand pretty much everything you said and I tried the camera plus power button and it didn't vibrate so it should mean I probably can flash things still. I have drained the battery and am charging it back up to see if that helped.
I have a friend who knows ADB so I am going to have him look at it to see if we can't get it working through there. Also the G1 screen has been popping up but then fading right when its about to change to the boot animation. So we will see how things go and I'll try a couple different things and report back if anything seems to work or open up more possibilities.
Thanks again for your information.

Ok, so my friend and I were going to flash a rom through fastboot. It was responding and such so we knew we were able to get it in there.
Anyone know what the command to flash a rom in fastboot is and if there are specific instructions to follow?
Any help would be greatly appreciated!

coolookoo said:
Ok, so my friend and I were going to flash a rom through fastboot. It was responding and such so we knew we were able to get it in there.
Anyone know what the command to flash a rom in fastboot is and if there are specific instructions to follow?
Any help would be greatly appreciated!
Click to expand...
Click to collapse
google it. i did and got about 100 links telling me how to do it. "unroot g1 with fastboot."

sorry i have the same problem, but my g1 is not rooted nor has it been flashed before, my friend messed it up somehow? wen i turn it on all there is is a blank highlighted black screen. What do yall suggest i should do

r3s-rt said:
google it. i did and got about 100 links telling me how to do it. "unroot g1 with fastboot."
Click to expand...
Click to collapse
First of all we are not trying to unroot the phone just flash another rom
Secondly we already tried your "fantastic" method of using google before coming to the forums

Ok I think I just bricked my G1
I was following the steps on theunlockr.com and was following the steps to the T like I always do.
The problem incurred after flashing the spl. I flashed the correct radio then ir rebooted and went back into recovery mode. Then I flashed the spl all seemed well home+back and never rebooted. It stayed on a black screen for over 30 mins. So I took out the battery and waited a few mins and put battery back in and same thing. Just a black screen nothing I can do. I have tried holding home+power and camera+power and back+power nothing. I am stuck have looked it up and this is the best forum I have found to post in.
Any input would be great.
thanks
nate

[Q] Dead HD2? please help?

Hey everyone, I have been trying to diagnose my HD2 alone for quite some time now, and thought maybe someone on XDA can help. So when i first got the phone, it ran just fine, about a month in i decided it was time to load it with a cooked rom. I used Energy rom because i loved the look. Before i had huge problems flashing it in the first place, after i got the flash to stay stable, the phone ran just fine. A while back (2010) i dropped the phone and cracked my glass. After replacing that, i had problems with the boot all over again.
When my phone boots it will boot 50% of the time, it will either freeze on the boot image (no red text) or just start up like normal. after 12-24 hours of general use, the phone will just freeze up and i will need to pop the battery out. Once i put it in, it will not boot unless i let it sit for a while. the longer i let it sit, the longer the phone stays working before it freezes. it seems that the longer it sits past a day doesnt matter, but it does increase the odds of booting in the first place. only a few times has it posted the rom number and not booted.
Im wondering if this could be a mainboard problem, or something im overlooking. I also had android problems back when 2.1 was ran from the exe. i also ran many other roms, and just recently the Nand 2.2 droid.
My biggest problem is ive spent over $100 USD trying to fix the glass/lcd.
Any imput would be greatly appreciated. so what do you think?

mdnelson09 said:
Hey everyone, I have been trying to diagnose my HD2 alone for quite some time now, and thought maybe someone on XDA can help. So when i first got the phone, it ran just fine, about a month in i decided it was time to load it with a cooked rom. I used Energy rom because i loved the look. Before i had huge problems flashing it in the first place, after i got the flash to stay stable, the phone ran just fine. A while back (2010) i dropped the phone and cracked my glass. After replacing that, i had problems with the boot all over again.
When my phone boots it will boot 50% of the time, it will either freeze on the boot image (no red text) or just start up like normal. after 12-24 hours of general use, the phone will just freeze up and i will need to pop the battery out. Once i put it in, it will not boot unless i let it sit for a while. the longer i let it sit, the longer the phone stays working before it freezes. it seems that the longer it sits past a day doesnt matter, but it does increase the odds of booting in the first place. only a few times has it posted the rom number and not booted.
Im wondering if this could be a mainboard problem, or something im overlooking. I also had android problems back when 2.1 was ran from the exe. i also ran many other roms, and just recently the Nand 2.2 droid.
My biggest problem is ive spent over $100 USD trying to fix the glass/lcd.
Any imput would be greatly appreciated. so what do you think?
Click to expand...
Click to collapse
Mate, I think it's rather hardware related problem. You better go back to the repair center before your warranty expires

silverwind said:
Mate, I think it's rather hardware related problem. You better go back to the repair center before your warranty expires
Click to expand...
Click to collapse
I went back right after i cracked the glass, and they said my insurance never covered it, even tho i pay extra on my bill for it. i voided the warranty when i replaced the lcd too
Does anyone know where i can get it fixed say under the counter or anything?

Bricked or what?

Hi again guys. I dont know if i ralle can use the term bricked or not, but i guess so. After a funny day with a couple reboot and new "radio" image my Legend want start anymore. The screen is just black, even if i hold down vol down/up and power. So the big question.... Is this phone bricked? If so, can i fix it?
EDIT: The LED does not even respond when charger is plugged in.
Sorry for the lack of English.

if it is bricked - try this.

I dont even get to fastboot The phone is completely dead/black

Are you S-OFF? I've never known a S-ON Legend be completely bricked like that!

No i'm still S-ON because of the d*** HBOOT 1.01
Only thing i've done so far is root+CM7. And yesterday when i played around with ROM Manager i had to remove the battery upon a crash.

Apparently same problem as here : http://forum.xda-developers.com/showthread.php?t=1096083
This is really weird...
I dont even get to fastboot The phone is completely dead/black
Click to expand...
Click to collapse
I think you are in trouble...
RomManager is maybe the source of your problems, what did you do with ?
Did you have errors during the radio installation process ? and which radio were you flashing ?

Here the story. I rooted my phone and switch to CM7 and notice that my GPS did not work with stock radio verision (dont remember wich) I upgraded to 7.08.35.21 and the GPS finally workt again with some minor interrups. Did some reading and decided to upgrade again to 7.13.35.05.
The installation went well untill the end. A picture was shown, a mailbox lookalike with an arrow pointing at a foolish looking droid dude. The only thing i could do was to remove the battery, after that the phone was dead.

SGT John Doe said:
Here the story. I rooted my phone and switch to CM7 and notice that my GPS did not work with stock radio verision (dont remember wich) I upgraded to 7.08.35.21 and the GPS finally workt again with some minor interrups. Did some reading and decided to upgrade again to 7.13.35.05.
The installation went well untill the end. A picture was shown, a mailbox lookalike with an arrow pointing at a foolish looking droid dude. The only thing i could do was to remove the battery, after that the phone was dead.
Click to expand...
Click to collapse
me too it sucks

Is it still under warranty? (Obviously not as you're rooted, but would it be if you weren't rooted?) If so, try sending it to HTC they might just replace it if they can't see for themselves that you're rooted!

If you says its a firmware update that caused the phone to not turn on they just JTAG it without checking,reflash the latest update (and sadly HBOOT) and send it back

bonesy said:
If you says its a firmware update that caused the phone to not turn on they just JTAG it without checking,reflash the latest update (and sadly HBOOT) and send it back
Click to expand...
Click to collapse
ok but they could ask what update and stuff possibly just thinking i might ring them soon whats the worse thing that could happen if they work it out? Just out of question?

madcat340 said:
ok but they could ask what update and stuff possibly just thinking i might ring them soon whats the worse thing that could happen if they work it out? Just out of question?
Click to expand...
Click to collapse
They will send it back unfixed and say the warranty is void. Even if they know its rooted they might still fix it for you, it depends.

It's my fault that the phone is broken and i'm willing to take that blame A clean conscience makes me sleep better at night
I dont know how it is in the rest of the world, but in my country there is a high fee if they notice that the owner has done something with the firmware etc. Thanks anyway for all the respons and help, and remember guys, stay away from Rom manager

You only have to say that it said update available then when it restarted it did this.. If they say anythign after its been sent then just plead ignorance.Its not like they cant afford to repair one phone

bonesy said:
You only have to say that it said update available then when it restarted it did this.. If they say anythign after its been sent then just plead ignorance.Its not like they cant afford to repair one phone
Click to expand...
Click to collapse
well i'm going to say something like that. Generally because my phone was buggered before then (signal problems and locking into airplane mode) though i'm rooted i still wouldn;t think i'd get away with it
does it matter if the root is S-ON i'm just thinking off my chances

PM sent, I can fix hard bricked Legends with JTAG.

Possibly bricked forever - Stuck at Sumsung logo endless reboot

Stupid thing is that I can do everything to it aside from getting it to boot all the way to work! I tried reflashing OEM roms and I tried custom roms. They all work just fine and it just won't boot all the way. I can turn it on and off, use format option, download mode and magldr. I keep my sim out and memory card. Before this all happened I always used OEM OS. Last thing I did was check my bank account, close the browser and click the power button to turn it into sleep mode. Few weeks ago I did have an issue with it for a day. It kept turning on and off constantly boot to random points. Mostly to the AT&T screen. It would boot all the way rarely and I got it to stay on a couple times for about 10 mins to copy all my stuff from it. Is it possibly something to do with the hardware being a POS and Just crapping out for no reason because cell phones are poorly made expensive bricks?

I've seen this issue across the forum several times. Unfortunately, just one case seemed to "return" to life, without understanding the reasons behind the "lapse".
What I can suggest you can do (and feel free to disagree) is get in touch with Cottula (creator of MAGLDR) and see if you can help you. You can send him the phone, maybe he can analyze it and get something out of it.
GL, mate, and if you find a solution, I'm sure other folks here would be glad to hear it.

Ahhh ok thats what I figured. I browsed a bit, but most of what I saw is people couldn't do anything. I didn't see anyone saying they could do as much as what I can do with it. I'll try your advice and see if maybe he could help. I took apart the phone to see if maybe someone came loose, though I saw nothing. Clean as a whistle. What I think maybe happen is it burnt up finally. I notice at times it would run extremely hot, mostly when I'm talking on it for more then an hour.

Well, for your sake I hope it's not burned out (hardware issue). I hope it has some software component that's screwed and that has a chance of being investigated and maybe fixed.
Also, the getting hot while talking/browsing for periods more than 30 min it's a known issue. It's however supposed to be quite warm, but not actually really hot, if you know what I mean. It it however possible that exposing the phone to higher temperatures to cause hardware issues.
In any case, I wish you good luck. Who knows?

I gave AT&T a call to see what they could do. The software warranty is 6 months past and she wasn't able to override anything that much passed over. Though I was able to get my 2 years wavered and get a early upgrade. So I got myself a Xperia Ion. I'm happy I don't have to put up with a flip phone for another 4 months. lol
I tried working on my focus a bit more playing with zune and other programs I found. Though I don't see it coming back to life trying all the different ROMs. I would think to make it work again is to re-flash the actual phone bios itself. Just like a computer starting it still uses DOS then loads the OS. I don't know how a phone works to much, but I'd assume same process. Something to do with the root-root of the phone telling it to be stupid and not boot properly.
Another note, where is the best place to sell this to get some money out of it? Screen and other pieces of its hardware are 100%. Should I try ebaying it?

I had a similar issue, last thing i did was removing the SD card before re-flashing the MGLDR and custom ROM

This may just be it for me :(

Well after just recently getting another shift(not new), it too has died on me . While running jellybelly i got a lockup and went to pull the battery. That was the last time my phone was on lol. Happened yesterday afternoon, tried connectiong to usb, every one of the 3 batteries i have wont work, wall charger to get it on. Nothing. Not sure how or why cause it was running fine. Now it just wont turn on. Not sure what to do since i cant adb or fastboot. Wont go into recovery or anything either before anyone asks. I think its just dead. I'll keep playing with it trying but if it doesnt work, this is it for me guys. Sad considering the recent progress on this device. I'll probably stay on the forums though. If anyone else has had this problem lmk.

Very sorry to hear that. This really is an awesome device once you take off its leash
Anyway good luck with whatever replacement you happen to get! Don't be a stranger