Related
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
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?
Hi I just recently applied the nodo update through chevronwp7. A few days later (today), I tried to sync with zune and had an error and would not read the phone correctly, I cant remember the message.. So I shutdown the phone then turned it back on thinking it would resolve the issue. But instead the phone gets stuck at the white htc screen( the first screen that comes on after pressing the power on button).
I have flashed ansar's cingular rom successfully several times, Tried the Windows Phone Support Tool......No luck. Will not get past the white htc screen, the only way to turn the phone off is by pulling the battery.
Any help would be greatly appreciated, bought the phone from ebay for my original at&t contract.....No Warranty that I know of. Sending it in for repair is not an option. Does anyone know of a possible fix? I am using Win7 x64.
Thanks, CheSley
It's borked, this has happened twice to me now. My devices were covered under warranty though. Sorry.
http://forum.xda-developers.com/showthread.php?t=884142
This also happened to me. However my phone was still locked.
I bought mine on Craigslist so technically I couldn't claim it under warrenty but I talked to a guy at an ATT store and he said call anyway because 50% of the time they are to lazy to check. I called, was sent to a device center down the street and had a brand new Surround within an hour.
I'd suggest trying a call to ATT you might get lucky.
Fixed..
Hi there,
I also had this happen to me and unfortunetely I had one little red dot on the water sensor by the USB port so they wouldn't warrenty it for me.
Today i fixed the phone myself and it's up and running perfectly. With my issue i guess it was the SD card... Completely fried and unusable on anything. Once i put in a working SD card and rebooted the phone everything was running fine again.... It was a fresh start had nothing remembered except the stuff you purchased with your windows Live ID.
You do have to take apart the phone which could void your warrenty but this didn't matter any more in my case and i had nothing to lose..
Wasn't to hard at all..
Hopefully this helps someone else!
Coockoo said:
Hi there,
I also had this happen to me and unfortunetely I had one little red dot on the water sensor by the USB port so they wouldn't warrenty it for me.
Today i fixed the phone myself and it's up and running perfectly. With my issue i guess it was the SD card... Completely fried and unusable on anything. Once i put in a working SD card and rebooted the phone everything was running fine again.... It was a fresh start had nothing remembered except the stuff you purchased with your windows Live ID.
You do have to take apart the phone which could void your warrenty but this didn't matter any more in my case and i had nothing to lose..
Wasn't to hard at all..
Hopefully this helps someone else!
Click to expand...
Click to collapse
Good call, I was thinking it was a storage failure, but as I said mine were covered under warranty so I never voided the stickers But, if you have nothing to lose grab a small torx bit (t-4 I believe) and try it out. Then report back here.
RE
kdj67f said:
Good call, I was thinking it was a storage failure, but as I said mine were covered under warranty so I never voided the stickers But, if you have nothing to lose grab a small torx bit (t-4 I believe) and try it out. Then report back here.
Click to expand...
Click to collapse
Hi all and thanks for the quick responses. I actually just tore mine down a few minutes ago, pulled the sd card, re-flashed with original rom and it worked... luckily i have old 4gb card that might work. So far the phone says "installing apps" in the initial setup. hopefully it works... Thanks Everyone.
SD Card
I have the same problem, and no chance to claim the warranty cause I'm at Brazil.
I didn't understand what are you talking about the SD Card, this phone don't have SD Card. Did you disassemble the device?
Yes you'll have to disassemble the device to get to the card. From what I've read it's not that hard to do. Good luck.
Yeah I had that same thing happen to my Surround but luckly I had warranty. I tried everything possible to fix it but nothing seemed to work.
This same thing happened to me... I think my phone is still covered under warranty, but I have a very bad tendency to lose my receipts... So hopefully I can go and get a copy from the at&t store and get it repaired or replaced...
Excellent!!!!!! I had the same problem. I changed the SD and problem sold.
MUCHAS GRACIAS!! PURA VIDA
ok, I wll try changing the SD card
cirojascr said:
Excellent!!!!!! I had the same problem. I changed the SD and problem sold.
MUCHAS GRACIAS!! PURA VIDA
Click to expand...
Click to collapse
Nice thanks helped my friends phone out too.
Amazing i had the same situation i just removed the sdcard and replaced it and walaaaaaaa my htc boot normaly again.. thank you guys....
Hi everyone! Unfortunately, my run with my T-Mobile G2 appears to be nearing it's end.. I've had this phone since November of last year, so fortunately for me, I'm still within the 1-yr warranty. I couldn't find a legit answer on the forum so far so hopefully someone will have the information I need to know now.
Lately, my phone has been getting crazy. Sometimes it would start pressing random things by itself. Apps would start by itself, things would type by itself, etc, etc. Then, at times certain areas of my screen wouldn't work at all, most noticeably the "y," "b," and "h" on my keyboards. And this doesn't matter whether I'm using the stock Gingerbread keyboard or Swype.
To answer any questions, yes I am rooted and I have been running CM 7.0.2. I tried to flash 7.0.3 to see if that would correct my issue but it didn't. I also tried to reset the phone via Privacy within the Android UI and via Recovery, both with no avail.
My question to y'all is how can I fix this if at all? If this problem is not fixable, can someone provide me with the MOST SIMPLE guide as to how to unroot and restore my original T-Mobile stock ROM if necessary for me to send it to claim warranty.. Finally, if I resorted to claiming warranty, does anyone know if T-Mobile will be sending me a refurb G2 or a new one or a completely different one?? Thanks ... This is EXTREMELY UNFORTUNATE.
it happens to me plenty. keep the scroll pad on the side from changing angles in direct light or it goes nuts. if theres any water on the screen at all touch commands work funny. its errors in the optical touchpad and cpacitive screen technology, not the;phone itself.
edit: im stock if youre wondering
It happens even in the dark though. I think its problem with the screen.
Any word on this? the same thing is happening to my phone.
Hui,
I was also having this problem for some time and was reallythinking of replacing the phone until I finally got rid of this last week. To start with I think this is a software issue but I'm still not sure what sw is causing this. n order to fix it I had to install the rom again from scratch and did not restore anything from google. Because independent from whatever ROM I installed the issue appeared soon after I set up the phone. So if you wnt to give it try, do a clean ROM install or factory reset to your phone and then while setting up your device uncheck the option to backup and restore settings to your google account. I know that setting up everything manually does not sound great but it's better than the crazy touch screen.
Digitizer issues
Sent from my HTC Vision using XDA App
Digitizer issues, T-Mobile just replaced my original release date G2 because of it.
They will send you a refurbished model and you have to send yours back in within 7 days or they bill you $400 I believe.
Sent from my HTC Vision using XDA App
I had serious digitizer issues last month and thought for sure that my G2 was finished. Come to find out I had gotten some oil on my phone, probably from answering a text or phone call while eating at work. I took it out of its case and completely cleaned it with a cloth dampened with peroxide...not soaked just damp, and now my phone is back to normal. Give that a try and rule that out first before you replace the digitizer or phone. Make sure you clean the inside and outside of the case/skin if you have one too.
I finally figured mine out. I guess the digitizer is really really sensitive to moisture. I usually take my phone into the bathroom with me when I shower in the morning, once I stopped doing that and gave the phone some time to dry out (in a dessicant container, but rice would work just as well) my screen is back to normal. I guess the steam from the shower was enough to bring up some bugs.
I've got a NC rooted using a 16GB SanDisk mSD card with CM7 on it (not sure precisely the version but don't think it matters). I set this up with help from the xda-developers site in December 2011 and have only used the NC in this mode ever since. I bought the NC as a refurb from the B&N eBay sale in late November 2011 and the unit has a one-year warranty.
Two days ago I was using the NC looking at photos and I let the screen time out and turn off. After this the NC wouldn't turn on; didn't matter what I did. I tried holding the power button down for 10-seconds, I pulled the mSD card and tried a hard reset (power, n, vol- for 5-seconds), tried charging the battery until the stock charging cable light went from orange to green. Did everything I could think of without any signs of life in the NC.
So I brought the NC to a B&N store (without the mSD card or mentioning that I'd been running it rooted) and the moment the guy in the store hit the power button the damned thing booted to the stock OS. The guy told me that this type of thing happens frequently and he thinks there's something about the WiFi in the store "waking up" the NC's (seemed like bull-bleep to me, but the NC was running). The guy told me he'd update the OS from the 1.2v it was at to the current 1.4v and this too could help. I let him do it figuring it probably didn't matter because I should be able to reset it to the factory config if there was something about the 1.4v that screwed up the root.
The guy gave me my NC back after updating it, told me if the problem persisted he'd do an exchange, and I went into my car in the parking lot. There I put in my mSD card into the NC after doing a full shutdown and it booted into CM7 with no problems. Today, however, same problem occurred, couldn't get the screen to turn on. So I pulled the mSD card, tried all the buttons, hard reset, etc. Then I shook the unit and was then able to get it to boot to the stock OS. Did a power down, installed the mSD card, and it booted to CM7 again no problem. That was ten-minutes ago, now the screen is again dead.
Even though the NC has lived a pretty easy life inside an Otterbox case, never been dropped or exposed to water or high humidity, I'm thinking this is a hardware problem and that I should just do an exchange. I've not found any similar posts or information about this type of thing, so I'd appreciate anybody's thoughts about the matter. Specifically:
1 - If I get an exchanged unit, should I be able to boot from my mSD card or will I have to format it and re-install CM7 like I did initially?
2 - If I'm offered a Nook Tablet in place of a NC, should I take the Tablet? I know it's got more power but I understand that rooting it even via mSD card is a PIA and not as straight forward as doing so on the NC.
3 - Is there anything obvious that I'm missing here?
Thanks for the help and apologies if I missed that this is a common problem the fix for which is commonly known.
Turgidson said:
I've got a NC rooted using a 16GB SanDisk mSD card with CM7 on it (not sure precisely the version but don't think it matters). I set this up with help from the xda-developers site in December 2011 and have only used the NC in this mode ever since. I bought the NC as a refurb from the B&N eBay sale in late November 2011 and the unit has a one-year warranty.
Two days ago I was using the NC looking at photos and I let the screen time out and turn off. After this the NC wouldn't turn on; didn't matter what I did. I tried holding the power button down for 10-seconds, I pulled the mSD card and tried a hard reset (power, n, vol- for 5-seconds), tried charging the battery until the stock charging cable light went from orange to green. Did everything I could think of without any signs of life in the NC.
So I brought the NC to a B&N store (without the mSD card or mentioning that I'd been running it rooted) and the moment the guy in the store hit the power button the damned thing booted to the stock OS. The guy told me that this type of thing happens frequently and he thinks there's something about the WiFi in the store "waking up" the NC's (seemed like bull-bleep to me, but the NC was running). The guy told me he'd update the OS from the 1.2v it was at to the current 1.4v and this too could help. I let him do it figuring it probably didn't matter because I should be able to reset it to the factory config if there was something about the 1.4v that screwed up the root.
The guy gave me my NC back after updating it, told me if the problem persisted he'd do an exchange, and I went into my car in the parking lot. There I put in my mSD card into the NC after doing a full shutdown and it booted into CM7 with no problems. Today, however, same problem occurred, couldn't get the screen to turn on. So I pulled the mSD card, tried all the buttons, hard reset, etc. Then I shook the unit and was then able to get it to boot to the stock OS. Did a power down, installed the mSD card, and it booted to CM7 again no problem. That was ten-minutes ago, now the screen is again dead.
Even though the NC has lived a pretty easy life inside an Otterbox case, never been dropped or exposed to water or high humidity, I'm thinking this is a hardware problem and that I should just do an exchange. I've not found any similar posts or information about this type of thing, so I'd appreciate anybody's thoughts about the matter. Specifically:
1 - If I get an exchanged unit, should I be able to boot from my mSD card or will I have to format it and re-install CM7 like I did initially?
2 - If I'm offered a Nook Tablet in place of a NC, should I take the Tablet? I know it's got more power but I understand that rooting it even via mSD card is a PIA and not as straight forward as doing so on the NC.
3 - Is there anything obvious that I'm missing here?
Thanks for the help and apologies if I missed that this is a common problem the fix for which is commonly known.
Click to expand...
Click to collapse
Could be you are experiencing the Sleep of Death (SOD) problem. The unit is still on but can't wake up. The only thing you can do to get out of it is to hard power it off and back on. Hold the power button for a long time. Release and push again until it turns back on.
SOD happens when you leave wifi on all the time and the unit goes into deep sleep. Sometimes you can't wake it back up.
If you have this happening a lot, there is a modded wifi kernel module that helps. If you need it, PM me and I will send you a link.
If you get an exchange it should work just like yours with the SD install. Just put the same card in and should run OK.
You won't get a nook tablet without paying more. If you are happy with the color, I would stay with it. The tablet is still iffy about running other ROMs yet.
Thanks for the info. Does the SOD affect the unrooted NC? If it doesn't then I should be able to trouble shoot the problem by running the NC with the stock OS for several days and see if the problem continues. Does this sound reasonable?
Sent from my SCH-I510 using XDA
Turgidson said:
Thanks for the info. Does the SOD affect the unrooted NC? If it doesn't then I should be able to trouble shoot the problem by running the NC with the stock OS for several days and see if the problem continues. Does this sound reasonable?
Sent from my SCH-I510 using XDA
Click to expand...
Click to collapse
It does not affect the stock. That should be a good test.