A little background;
I bought an HTC Dream used a few weeks ago, I successfully rooted it, and installed Cyanogen 6, and used the phone for a couple weeks afterward. Then late yesterday the touchscreen decided to die. The LCD screen functions fine, it is simply the touchscreen that has failed.
Literally every touchscreen device I have ever owned in my life has done this, I don't know why, but it makes me paranoid. As it turns out, this phone was no exception. It's one of the reasons I will never get a phone without a physical keyboard.
Of course, without the touchscreen, I cannot use the phone, as I cannot operate the unlock screen that displays after the display times out. Thus, I hope in vain that perhaps it's a software issue and attempt to wipe and re-ROM Cyanogen 6 in the recovery screen, using the zip file of Cyanogen 6 I still had on the root of the SD card. Now, the phone hangs on the Roger's logo screen.
So my question is this; should I bother trying to get a touchscreen digitizer part for this phone, or do you guys think the problem is more widespread than that?
Could a faulty touchscreen cause the phone to flip out during booting and hang or do you guys think it's perhaps the 'motherboard' that is faulty and I should start thinking of all the creative ways I can use a new paperweight?
Any advice would be appreciated. I like the design of the HTC Dream I'll try to replace this one I have to.
(As an aside, I am back to rocking my old Sony Ericcson W200 I got second hand from a friend many months ago that I was so very desperate to get rid of when I got this HTC Dream. Finally having a full keyboard and a real operating system was like having a massive thorn in my head finally removed. Now I'm stuck in T9-land again. I am so very, very sick of this thing's stupid orange face, not to mention the Roger's logo from the HTC Dream at this point. )
Just a suggestion, if you have a a screen protector on, maybe try taking it off?
Well I will try that if I can manage to fully boot this thing again, but the thing is the phone was working perfectly fine, even with the screen protector, and then the touch screen decided to randomly stop responding to touch. No changes were made to the phone at all.
Do any of you know how I might use adb to view what exactly it's doing while it attempts to boot?
Any help would be appreciated.
You mean
Code:
adb logcat
?
But it's working only if at least your kernel is initialized propery and your system starts to boot up.
Sent from my Gingerbread on Dream using XDA App
Ah thank you for the reply!
I think you're correct, adb is perpetually 'waiting for device' while the phone attempts to boot.
I can boot into the bootloader and interact with that via fastboot and boot into recovery and interact with it via adb just fine at this point. What would you suggest I do to at least coax this thing into fully booting anything? Is there a particular image I could flash that you recommend for specifically debugging hardware/software issues?
Seems to me, you have a wrong kernel installed. Can you post your SPL/Radio combo pls?
Sent from my Gingerbread on Dream using XDA App
DREAM PVT 32B END S-OFF
HBOOT-1.33.2005 (DREA221000)
CPLD-4
RADIO-3.22.26.17
Apr 20 2009,15:30:43
So you have a 32b with 3.22.x radio ... I would expect 2.x radio and 32b or 3.x radio and 32a.
Nevertheless, I do not have such a deeply knowledge about possible combinations, but you probably could try to flash one of these kernels. For sure Terry will be able help you.
I will try those. It should be noted that I was using this phone with the current radio/Kernel quite successfully for a couple weeks before it decided to have the touchscreen stop responding and then not boot. I had made absolutely no changes to the phone immediately beforehand.
Thanks for your help, though.
It works! That Kernel update seems to have made my phone bootable again! AND the touchscreen works! Thanks! It's like christmas up in here!
I was using this used Sony Ericcson W200 that I tried to replace with this HTC Dream, and now I can finally go back to a phone that has a real operating system! Thank you!
Touch screen
Hey my touch screen is not working either so what is it that i need to do i dont have it on me right now..
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
Hi, I'm having a big problem with my device, I've bought the European version and didn't touch the ROM or radio for a cool 3 months, but I often update to the latest Cookie HT, and lots of different apps. Then it got a weird behavior that if I use the device and it got a little hot it would restart by itself and after the restart got stuck on the white logo screen. It would happen often when plugged and Activesynced to my computer.
I lived with this situation for the past month but now I had enough, I've updated the radio to the latest I could find, and the ROM to Energy with Cookie HT.
Now it's worse, I can't get it to stable on the Home screen, I can see it but can't play with anything, stuck...
And BTW when it get stuck the bottom of the phone is quite hot, even if I left it for quite some time.
Edit : The Sense UI isn't loading and it actually a good bug, cause the device is running smoothly even on ActiveSync. It feels like the CHT is to blame, at least the latest one to date.
Edit 2 : Sorry, I was wrong, now it got stuck during SPB backup restoring connected to ActiveSync.
Edit 3, Sorry 2 : I've let it cool, turned it on and somehow the CHT is back and working wonderfully, this is weirder then I thought.
Edit 4 : I've managed to run Android 2.1 Desire and it was running good until it got a little warm and then froze. I'm beginning to suspect this is a hardware issue.
I realy need help feaguring this one out.
I've replaced a couple of Radio versions and this device keep jamming up, it's now unusable. I need to get it relaxed and cold before I try to turn it on again.
Can it be that the ROM is responsible ? should I go back to the stock with no mod at all (it would KILL me though).
I'm frastrated and thinking of selling the phone if anyone would buy this piece of crap.
i am in the same boat mate.
mine is going back to htc tomorrow.
In the end i removed everything and took the rom/radio back to stock still the 'heat' issue exists.
It has been like this on test for nearly two weeks if i try to run the youtube app the phone switches off anything more intense and it hard resets itself.
I have learnt that if you leave it too cool down battery out etc it will switch back on and if you do nothing but make phone calls it will be ok?
Having read alot it appears this issue happens if the device goes over a certain temp. For example folks have been moaning about the phone switching off if used in a car whilst charging running sat nav.
I advise you to contact htc as i have done.
you may have already done this, but did you do a task 29 before flashing the rom (task 29 wipes the phone and gives you a clean base to start from). Also delete the application data on your mem card(important). If your phone wont boot you can enter the bootloader by removing batt and holding vol down as soon as you you put the batt back in,This will put you onto bootloader screen ( if you have hspl installed?) from here you can do task 29 and reflash your chosen rom. Oh and make sure you have required radio for the rom you choose. hope this is of some help thought id try
Just wanted to update that HTC took an effort and accepted my unwarranted device for fixing. They replaced the board and sent it back on their expense. The device now is working flawlessly !
Thanks to HTC for a GREAT customer service and support !!!
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]
Sorry if this is in the wrong section or somthing, i dont know how to use this site
just before last Christmas 2010, i bought a HTC HD2 off eBay for £200.
it comes with windows mobile 6.5 but like many other HD2 owners, i put an android on. Anyway, everything was working perfect, but last week i dropped my phone on a gravel path and all the screen cracked. Luckily, it was just the glass that cracked, and not the actual LCD...so the actual touch screen still worked as well as the rest of the phone.
i continued using my phone for a while, whilst the screen was cracked as the rest of the phone was working perfectly, then my mum found a repair company that will fix it for me online - htcphonerepairscouk
so i paid £70 for the new digitizer and screen and sent my phone off.
I got it back in the post about half an hour ago and every time i start android up it waits for about 20 seconds and it just restarts, and goes on forever no matter what. its nothing to do with the OS as i tried hard and soft reboots and trying a different rom. i called them yesterday and they told me that it was the motherboard that broke and it would cost more than the actual phone to repair the motherboard. they obviously messed it up when fitting the new screen as it was working perfectly with MIUI android before i sent it of (despite the cracked screen)
what do i do as its their fault my phone wont work now? it definitely worked before i sent it. and is there a way to fix it? thanks so much!
check teh battery pins carefully, especially teh middle one. they bend easily and cause rebooting part way through the boot sequence.
did u try booting while on the charger? that works for me sometimes when it restarts
Sadly it may well be linked to dropping it, if it was hard enough to crack the screen its hard emough to damage the board as well, I suspect its going to be expensive if you follow it through
Help phone restarting every couple seconds after installation of 2.3.7
hello i am unsure if i am in the right section to ask for help but considering i cant post anything yet i thought this section would be a great place.I recently put android 2.3.7 on my phone tytung...it reads under settings kernel version:[email protected]#130......build is gwk74(nexushd2-gingerbread v3.2a nand) It just recently started starting over and sometimes it cuts off and i have to push the power button for it to come back on other times it does a soft reset.I am out of options and i want to remove this android off of my phone.(if possible) Can someone please help me to understand if this is a ongoing problem with all htc hd2 with nand android or if i should just install another android rom..;(
Hi there,
your first thought might be: Ah jeez another one posting the same **** 2000 people posted before ^^. But anyways i think my problem is a special case:
yesterday i wanted to flash another radio to my htc magic via clockwork recovery. However something must have gone wrong. After the recovery rebooted my phone i got stuck at the "htc magic" splash screen. Pressing the home or the back or vol-down button or home and back button at the same time doesnt change the situation. still stuck at splash screen. fastboot and recovery dont seem to work.
After some really bad panicking minutes, i pulled the batery out of the phone and let it rest, while googling and searching the **** out of every forum on the net. Some minutes later i reassembled the battery and started the htc magic without pressing any other buttons, hoping it would juts boot and say "kidding ))" on the display. but yeah ... it didnt ^^.
Now im coming to the odd part, which differs from most other posts i saw on other forums and here on xda: after quite a while my htc magic suddenly made that "bling bling" sound, as it did whenever it started android successfully. i nearly burst into tears when i heard that sound, hoping that i would be able to access the phone via fastboot or adb. but ... i wasnt able to :S. the screen went black after that "bling bling" sound and stayed that way until i pulled the battery again.
i could repeat that procedure and reproduce the sound and behaviour, but i couldnt access the phone via any possible way i could find on the web :S.
hopefully somebody, who knows more can help. my last step would be jtagging the phone. but the tools are kinda pricy for such an "old" phone. and i couldnt find anyone in my area who could borrow me the tools or repair the phone for cheap money.
thanks in advance im counting on your knowledge
Try this low cost JTAG
tested by me with 2 T-Mobile Mytouch 3G
thanks for your fast response. if jtagging really is my last chance:
- what did you pay for all the parts of the schematic ?
- how long did it take you to put everything together?
- do i need a parallel port on my computer, or is it possible to use an usb port ?
- and do you think a newbie to smoldering and stuff could be successfully assembling all those parts?
- can you provide me with links and/or other pictures, which could help me?
thanks again for your effort
kinda exciting this whole thing :>