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] mytouch 4g wont turn on

so my mytouch 4g wont turn on even with a different battery. i plug it it in and it gives me a flash on th screen but thats it. any suggestion without sending it in

Take it to a tmo store, they'll swap it.

I got it off of Craigslist I think it was previously tampered with
Sent from my HTC Desire using XDA App

so i was in the process of doing a custom splash screen last night. i went through all the instructions on how to push the custom splash through terminal. everything went how the instructions said, but once i reboot it my phone turned off and never came back on. it doesnt power on, boot into recovery, nothing! i put the phone to charge and the red light comes on on the top left but when i take it off the charger it stays on.
i been rooted for about a month now and i was running cm7 build 8 when this happened. i just want to see if anybody has any idea on what going on. i tired everything i can think of. taking out the battery and normally powering on and nothing. taking off the battery and volume down and power to boot into recovery and nothing. taking off the battery, sd card, sim, putting back the battery and doing both normal power on and to boot into recovery and nothing.

First of all you just hijacked the guys old dead thread and second it sound like you just bricked your phone. As there is boot animation and there is slash screen. Seems like you flashed wrong thing. If the screen don't even turn on its dead then.
Sent from my HTC Glacier

Don't flame the poor guy! He's got it bad enough as is! And he didn't flash the "wrong thing" there are several threads on flashing splash screens in this phone's forum. Cut the guy some slack. He knows it may be bricked, he's just hoping it's not. And he was hoping for someone to provide some possible help. Not be be given **** for not opening a new thread.

i thread jacked because the thread was old and didnt want to clutter by starting a new one when im having some what the same problem. but no i pushed the splash image. i had already flashed a boot animation a few day back. i had call of android running on my phone as a boot animation. i just want to know is theres other methods of reaching hboot or recovery.

First of all don't put words in my mouth as my post does not contain any flame, second when I said wrong thing I meant he may not have meet the requirement for the splash image if he did correctly then obviously he would have had it up and running. Best thing for him would be going back to the original thread where he downloaded the image and asking the OP and troubleshoot it but at this point its to late all he can do now is warn others.
But if his phone is not old lol he can social engineer and play the victim card and send it back to HTC but first would be trying TMo saying he didn't get the POST OTA as he had PRE OTA and when he try to install the OTA it went blank and act like he has no idea what is going on, as he simply just want the phone to work or he will cancel service and do acting best of his life.

i already know i probably super bricked it. becuase ive bricked it before but not like this. i was able to fix it very quickly before. its like if the phone just doesnt have a battery. im just going to wait to see if anybody else has any more input. if not ill head to the tmo store see what they can do.

BlackSHELF said:
But if his phone is not old lol he can social engineer and play the victim card and send it back to HTC but first would be trying TMo saying he didn't get the POST OTA as he had PRE OTA and when he try to install the OTA it went blank and act like he has no idea what is going on, as he simply just want the phone to work or he will cancel service and do acting best of his life.
Click to expand...
Click to collapse
I do apologize for using the word flame. It was too strong. But I get fired up when people criticize instead of offering insight. If you had posted the above paragraph first, I wouldn't have had any issues. This is good and viable option. Albeit a last resort, but much better than criticizing for thread jacking. And I am the OP of the thread that he's using and am doing EVERYTHING I can to help him figure out a way to get this resolved.

coupetastic-droid said:
i already know i probably super bricked it. becuase ive bricked it before but not like this. i was able to fix it very quickly before. its like if the phone just doesnt have a battery. im just going to wait to see if anybody else has any more input. if not ill head to the tmo store see what they can do.
Click to expand...
Click to collapse
ok, I just got caught up on your issue. I am going to do a little research and see if I can come up with anything to maybe help. Do you have adb set up? What recovery are you running?

Same thing happened to me, flashed a rom rebooted and the phone never turned on again.

thanx every one for trying to help. i tried everything i can think of and i could not get that phone to power on at all. it was completely dead. so i went to the tmo store by my pad and they gave me a brand new one. now i just need to gain s=off on this one which i cant do for some reason. i dont know why since it was fairly easy to gain s=off on my other mt4g. ill figure out though.

coupetastic-droid said:
thanx every one for trying to help. i tried everything i can think of and i could not get that phone to power on at all. it was completely dead. so i went to the tmo store by my pad and they gave me a brand new one. now i just need to gain s=off on this one which i cant do for some reason. i dont know why since it was fairly easy to gain s=off on my other mt4g. ill figure out though.
Click to expand...
Click to collapse
Don't know if you used this guide yet or not but I will post it anyway http://forum.xda-developers.com/showthread.php?t=858996

toby4059 said:
Don't know if you used this guide yet or not but I will post it anyway http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
I aready got s=off but thanx anyways.
Sent from my CM7 Glacier using XDA App

Hi.
I had the same problem on my htc glacier (mytouch 4g) which was turn it on, stuck on the htcwelcome screen, keep loading and then turn off automatically. My phone is rooted and cusome flashed to the new htc 3.0 sense when this happened, i did a back up and restore to the oem mytouch sense and now it is working just perfectly. So if your phone is rooted you might give it a shot and hope it will work again

i had same prob kinda
i flashed a rom was useing it for a week and today i went to use camera and while camera was loaded the screen shut off like not beining used it did the crt thing and all then it wouln't come out of it so i pulled battary after like 5 min of a lighted black screen and went to power phone back on and nothing like no batt.....
anyways what i was geting to is that i called tmoble and they said it sounded like a hardware problem if you can plug it in to wall or car charger and nothing.. when i plug it into a usb on pc i get
hsusbs or something so u all might want to look into that.

i have s mytouch 4g it wont boot
i rooted my mytouch 4g ussing gfree and then i installed sense 3.0 rom and it worked then force closed left me in bootloader then from there flasheed cm7 worked good for 15 days then said force closed again then never turned back on aghain now when i plug it back in it tells me cannot install drivver software and it recognizes it as qhsusb_dload any solutions or its a gonner contact me at [email protected]

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

What to do when taking phone in for swap?

My S4 got REALLY hot today, and I turned it off for a wihle.
When I turned it back on, the screen is messed up. It comes on a shade of green with lots of lines. It makes it all but impossible to read anything on the screen.
Looks like I have to return it to get a swap.
Whats the best way to remove the root and anything that shows the phone was rooted... and return it to all stock...??

Since it's a hardware problem, I'd doubt they'd care whether it's rooted or not. Return it and you should be fine
Sent from my Samsung Galaxy S4 (SGH-i337) via Tapatalk 4

If you get an exchange, it would be a good idea for you to do some research and reading before you root the next phone so you will have the information you need in case something else happens to the next one. Good luck.

I hate that I may get an MF3, as Im on AMDL now.
Im not sure where you are going with your post, its not a rooting problem, Ive had it rooted from day one.
The ATT service center has one in stock, they said they have to refresh the software before giving me a replacement....... If I can get to triangle away Im going to try to reset the counter, and try to wipe and try to get the software back to factory.
I think I can get to download mode so I can get to odin...........

I let the phone sit (battery out) for a while and the screen came back to life. I thought everything was fine until I noticed when I plugged it into power it showed charging and beeped, then stopped charging, and then returned to charging again.
I plugged it into a computer and got a warning about a power surge on the usb port and the phone isnt recognized by the computer.
If its not back to normal in the AM, Im going to take it to the service center (after I remove my apps and hopefully restore root)

Check the port on your phone for a bent pin.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Nothing bent. Used an otoscope to get a good view~

Try a different charge cable?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Got the warranty exchange and yes, it is MF3
Had to send it back rooted with TWRP installed.
If they just hook it to a computer, then they will not be able to talk to the phone, lets hope thats all they do.
If they boot to the recovery screen they will see TWRP.
Im hoping they are just looking at them, seeing no visible damage and shipping them to Samsung for refurbishment..........

LG G2-D800 turning on and off by itself.

Hello All,
I have an LG G2-D800 (ATT model). It is just turning off and on by itself. I have been using the phone from almost 1year and it worked very well.
This issue has started happening couple of days back, and switches off all of a sudden when in middle of something.
I have tried factory reset and also encrpted the phone for BYOD purposes at work.
I havent installed anything new recently and was working well all long except this problem. it has become almost unusable now.
ANy suggestions on how to fix it? I am on lollipop

akusbharat said:
Hello All,
I have an LG G2-D800 (ATT model). It is just turning off and on by itself. I have been using the phone from almost 1year and it worked very well.
This issue has started happening couple of days back, and switches off all of a sudden when in middle of something.
I have tried factory reset and also encrpted the phone for BYOD purposes at work.
I havent installed anything new recently and was working well all long except this problem. it has become almost unusable now.
ANy suggestions on how to fix it? I am on lollipop
Click to expand...
Click to collapse
Without a logcat or crash message there is not way to find the cause.

I am not sure how to get it, can you let me know how to do get it

There are plenty of tut around the site. Follow the rules and you will find it.

zelendel said:
There are plenty of tut around the site. Follow the rules and you will find it.
Click to expand...
Click to collapse
I tried crash log app from google store, and it never sent me an email which I opted for with the crash log file

akusbharat said:
I tried crash log app from google store, and it never sent me an email which I opted for with the crash log file
Click to expand...
Click to collapse
Update to this now. My phone is not responding at all when I press power, volume up and down buttons.
Also when I connect to windows PC, it says USB device not recognised. I have all the drivers installed. Cant get into recovery or download mode at all.
When I check for devices using fastboot or adb, it doesnt show the device connected. my phone might have been bricked, but do not know how that happened.
Searched so many forums and threads here, but nothing helped in my case.
Can someone please let me know what to do now.

Uhm dead motherboard? You didn't flash anything recently so it's not a brick probably. Take that thing to the service if it's not reacting on pressing physical buttons. I wouldn't have high hopes for it tho.
Edit
Your phone doesn't turn on at all, right?

MilanStojkovic said:
Uhm dead motherboard? You didn't flash anything recently so it's not a brick probably. Take that thing to the service if it's not reacting on pressing physical buttons. I wouldn't have high hopes for it tho.
Edit
Your phone doesn't turn on at all, right?
Click to expand...
Click to collapse
Yes, doesnt turn on at all now..... it turned on when I tried over the weekend, battery was almost zero , so it came on ( I think so)
When connected to a PC, it is showing up as "QHSUSB_BULK"
From my reading online, it means hard brick..... I cant get into recovery,download modes or anything at all now..... definitely not motherboard
Can someone tell me how to fix this phone.
"fastboot devices" doesnt return any device
ADB or fastboot doesnt detect the phone at all.... just "waiting for device....." message

Any help here please?

Can you get on team viewer?
Sent from my LG-D800 using XDA Free mobile app

After going through your post, i'm 70% sure it's a hardware problem. Take your device to nearest service center and them know your issue.