Related
Hey guys,
I have this weird problem on my diamond 2G's screen...My touch screen, if seen from side ways,shows a spectrum like thing(green redish) in the center of the screen(1/2 inch by 1 inch)
Also the touch sensitivity has been affected bcz of that. I have to press a little harder than d other part of the screen. but it works flawlessly...
So i dont know wat could be wrong with my diamond(if anythng)...
Please help...
Not quite sure of "Diamond 2G", but assuming its P3700, I've seen a similar thing happen right after I've flashed the HSPL. As far as I recall, it was all good after I flashed a custom ROM. Could possibly be a image rebasing issue...
Yeah its diamond p3700 only...actually i have my hardspl installed installed since a long time...never happened before...
Also, have been using custom rom since a long time...i thought it would be hardware related..but if u sayin u had the same problem and it went away...i will try flashin a new rom and will report back...
Thanx
@openwicked...
I just wanted to ask one more thing..as u mentioned that it happened after installing hard spl...so u suggesting its a software thing...
but i tried removing the battery too..and it still shows dat spectrum thing...also if i touch it, it spreads..as in it doesnt increase in size but the same effect if u touch an lcd screen..the moving of the liquid inside...
does that sound familier???
Sounds worse than I thought. The spectrum persistence will stay for a few seconds (maybe more depending the amount of time the capacitors take time to get discharged completely), but isn't the kindof thing I faced though.
In anyway case, the board support packages (be it QUALCOMM or anything) are quite close to the hardware and can affect display (among other things) adversely. I'd recommend you fall back to the stock ROM/Radio for now.
Do let me know if it helps.
Ok guys, Long time lurker, First time poster here.
Been hanging out around the forums for a while now, but this is the first problem I've ever had that I just couldn't figure out on my own.
Screen dead. Have to return to TMO. What to do about existing rom???
Last Saturday night I was playing around with my phone before bed. Everything was fine. Woke up in the morning and the screen was dead.
The backlight comes on but no display what so ever. No HTC screen, no bootflash, no nothing. Everything else still works.
I can feel events happening on the screen when I touch so the digitizer is clearly up to snuff.
Also I have been able to get the phone into fastboot from memeory, so its a start.
I contacted Tmo about a replacement and it arrived today. I'm running GingerVillian 1.4. So the big question is what do I do about the ROM on my phone. Also, what happens if they get the phone back and discover it has been rooted. Will I get a bill for the full price of the unit? Anybody know??
The way I see it I have three options, but if I'm missing something please let me know.
1. Attempt to flash stock ROM via recovery using up down vol and track pad. And just not worry about S-off. If it looks the look, will they check Hboot for s-off???
2. Attempt a side by side deroot using the new G2 and the broken one next to each other.
3. Physically damage the memory somehow preventing the phone from booting.
#2 seems like the worst option simply because I will have no way of verifying that any step in the process is successful... (Scary prospect) of course this applies to option 1 as well but I figure I could go through the flash process two or three times just to be sure. Option three doesnt exactly sound like a winner either, just putting it out there.
Comments please, a little help would be greatly appreciated.
I would go for the blind flash of pcimg10 from sd root. Then plead ignorance. Confused tho ...did u say u can see the bootloader txt or no?
Sent from my HTC Vision using XDA App
No, screen displays jack squat, nada.
Also wasnt there a huge writeup about how I'm not supposed to flash pcimg10...?
Bluetygator said:
No, screen displays jack squat, nada.
Also wasnt there a huge writeup about how I'm not supposed to flash pcimg10...?
Click to expand...
Click to collapse
Depends on how you're rooted. I'm gfree'd and every now and then I'll copy that out to sd root and reflash it. It flashes fine, unroots the phone, but still leaves s-off. I've been thinking about this - again- after reading your post because I've thought this would be the worse-case scenario. That is a screen in some state where you just can't see what's going on.
If it were me, I'd at least want the factory load on it and hope that should they run some diags, put on a new LCD then boot it up, it could all be done without really noticing the s-off in bootloader.
For me though, I just would have a hard time physically damaging it - that would get me a 130$ refurb on my handset protection or if I tried to just kill some internal IC like the ram, I'd be even more worried they'd eventually find that for what it was.
edit: obviously your number 1 is the easiest since it's just answering volume up after giving it a few minutes on boot to parse the pcimg10 file.
edit2: okay, how about, hook jumper cables to it, blast it, then send it back and just claim you were hit by lightning
I'm perm rooted using visonary r12.
Yeah not going to damage it. I just wouldn't have it in me.
What worries me is if I flash pc10.img and something goes wrong I would have no way of even knowing it. Was thinking about just regular old CM6.1.
You people worry too much. Just send it in. As long as they receive an intact G2 with no physical damage to the screen (this bit is crucial if you got a swap out for anything screen-related) then you'll be just fine.
I have read on more than one occasion that if you cant turn on or see screen, as long as ur void stickers are still intact, and there is no water damage (moisture detectors all ok) they do not care.
Though not confirmed.
EDIT..... But if I were in your position then I would do as ZKID suggested with the pc10img thingy.
if there is nothing on the screen, it sounds to me that maybe the copper ribbon on the phone that attached the bottom of the phone with the keyboard to the screen portion could be damaged or loose... this happend with a buddies g2 and he was rooted and everything like you... he just sent it in as is and they never mentioned anything to him or gave him any problems because if it. he thinks they just saw the screen wasnt working and that was it.
Hello dear friends!
HTC let me down Kind of stupid phones indeed at least desire...
I have my phone for quite a time now, it is rooted with unrewoked, clockwork recovery and s-on. I flashed many different roms in the past and everything was brilliant. In a pas half-a-year or so I stayed with only one ROM - MIUI-Au. I kept updating it to the newer versions and so on and on. Never had any random reboot or something. At least maybe it was because of some strange app or something else. But now it started to reboot randomly and constantly!
Phone gets hot abit and it just reboots, and never comes to android homescreen again, until I put out the battery, hold it for few minutes, pop it back and then it boots. But as soon as start to play music, or run a game the phone gets hot abit and reboots again. and so on and on. I thought maybe it was a miui issue. So I tried to flash different roms, but guess what? None of the even boot! The main screen shows and with the same second it bootloops again and forever!... (
Even from recovery it sometimes reboots randomly. So i managed somehow to flash my miui back and it at least boots. But it is very unstable now, I barely can use my phone now
PLEASE WHO CAN HELP ME????
My warranty probably out of date, and my phone is rooted, I dont think HTC would accept it...
any thoughts? friends?
What have you set the CPU max to?
Sent from my HTC Desire using xda premium
Thank you for response! Appreciate, really!! I didn't set it, I left everything by default I think! Because as i said, i even tried flashing different roms, not only miui.
What else could be? By the way, with stock froyo rom If I remember correctly, sometimes it became extremely hot, but I didnt get any reboots from that. But now, it gets just a little bit hot and it seems that this causes the reboot...
Now what I just noticed, I get reboots even when the phone is idle. And it is not even warm!
If its not getting hot then I'm confused lol. It sounds like a actual hardware fault. Sorry I can't help with this one
Sent from my HTC Desire using xda premium
cluendo said:
My warranty probably out of date, and my phone is rooted, I dont think HTC would accept it...
any thoughts? friends?
Click to expand...
Click to collapse
try and get it taken back to stock if you dare.
The phone hasn't been out 2 years yet, which is how long the warranty is.
Thank you! But is there any possibility to fix it without HTC involvement? Maybe it is not hardware issue ? Can it be because phone is rooted and I flashed many roms to it ? I didnt try AOSP roms since reboots started, I will try to pop in Cyanogenmod or other and see if I will get reboots.
Would rerooting my phone and updating my recovery fix the problem?
and Note: yesterday I tried to S-OFF my phone, but I can't even do that with my unstable MIUI. It rebooted in the middle of the process..
I had a similar problem, apparently it's not uncommon on the early revisions. I sent mine to HTC and they replaced the mainboard.
Thank you for answer! But what if my phone is bought through a contractor?
Can just call HTC and ask the for repair? Or should I contact my contractor first ?
Just give them a call and they will try to help you out. I had a very good customer service experience with them when my desire had some issues.
They will require a proof of purchase though. If you managed to get the receipt from your "contractor" (I am unsure what you mean by a contractor), then there should be no problem.
Sorry for misleading word, I meant T-Mobile. I bought my phone under contract. I think I have a receipt. I even have whole box and stuff of the phone somewhere in my drawer.(just sayin ). So how is customer service of HTC? Poor, good ? I heard you need to tell them that you did a factory reset and that didn't help. Is that true. Also if I will unroot my phone, will they know it was rooted anyhow?
Ahhh....this overheating issue seems common. How they can release faulty phones?? No clue.
thanks for answers mates!
In Singapore, HTC service is really good. Phone was still under warranty.
It took me just one (real) call to confirm a repair order. The first call I was just checking to see what options were available to me.
The second call was an actual repair request. And the third call was me pestering them for a pickup date. heehee
In Singapore, repairs were done via courier. They picked it up and 1 working day later, they sent it back.
Naturally, you will probably need to impress upon them that you tried everything to fix your phone (which I hope you did which includes proving to yourself that it's not the ROMs fault).
You will definitely need to reset everything back to zero. In my case, I downloaded an RUU to totally reset everything back to STOCK, which included removing clockworkmod recovery. You WILL need to create a goldcard for this though so bear in mind that it's not exactly a case of a simple flashing procedure. At least not if you don't already have a goldcard.
Sorry if I overread it at some point, but you speculated at the beginning there could be some faulty app causing this, but you never meantioned performing a full wipe. Have you full wiped yet? Just to make sure it is indeed no software problem.
greets
Thank you for your answers. At the moment I have SuperNova classic ROM. ( 2.3.3 + Sense 2.1) But my phone crashes again and again, it is so annoying and causes me so much trouble.
I never tried a reset or unroot and return to original rom. Im just wondering now, would this help to remove or at least remove those reboots?
Today I was in my work and i was keeping my phone in my jeans pocket. it got hot as u would expect when keeping in pocket and suddenly it rebooten, then it went into a bootloop and started to bootloop 7 times in a row quickly. then again and again. It became very hot at that time.
For the interest, what exact hardware faults causes these reboots and why phone gets even hotter if you keep it on boot loop. If I keep phone cold, the rom usualy stays normal, without reboots. but as soon as I start using my phone, texting or calling for at least 5minutes of using it just reboots.
as I said- really annoying thing :S
I remember my happy times with miui, apps and no reboots Was fun!
cheers for helping!
I would give full wipe / factory reset a chance, and maybe RUU.
At least try it before sending phone to htc.
It is hardware problem, search forum. Fresh ROM without SD card, enabled WIFI and GPS, running G navigation, back of the phone is warm - restart after few minutes.
Maybe someone know how to read info form the phone right before reset? We could understand why the phone is reseting and hopefully add some patch.
Reboot-loop experience
Hey,
i had the same problem over the last few months: In the beginning my phone restarted only when it got hot, but it got worse over the last few weeks, in the end i was not able to use two apps at the same time (music and mytracks) or even to surf the internet longer than a few minutes. The problem did noticeably decrease when the phone was cool - tested by putting it on a fan or in the fridge. Yet, Skype was regularly killing it. As i really love my phone (and especially the AMOLED-Screen!) i did not want to resign. The battery cover contains some metal which is supposed to enhance heat dissipation - so i attached a little thermal pad to the hotter bottom of the phone to improve contact with the head spreader. Unfortunately it did not entirely fix the problem. Yes, it improved the situation a little, but it got even worse after a week or two - in the end i had to turn it in.
So i decided to take it to the Telekom-Shop. They were very kind and told me they would call the other day to confirm that the replacement would have been shipped. It took a few days longer, but i got a phone with the AMOLED-Screen! The employee said it was a used mainboard in a new case, completely refurbished. They only replaced the main unit, i kept the battery, sd-card, charger and so on. Now i have a working Desire again!
Terminator
Similar?
Hi i on the other hand have similar problem, qiute anoying one, my desire, cm7 hboot, s-off, insert coin cm7 rom, have phone freezing in diferent situations, sometimes its working sometimes just freezez and i need to get battery out and turn it one and sometimes several times in row to get it working again???? RUU and go to give phone in service? plaese advice?
@cp6ija Sandisk SD card? If yes, smash it.
nvm
cant delete post so just posting gibberish
Hi,
I had Sandvold's ICS 0.16 installed and disabled vibration when ring and my Desire reset...
Now, all it does is sit there with a black screen buzzing..
Battery out reset, removed sdcard, etc..
I've tried getting into recovery mode via power+back & power+voldn, etc.
No joy at all.
PC cannot see the phone when plugged in via USB (tried running RUU, that couldn't see it).
My main questions:
Is there any method available to recover from this? I've tried what I can (understand) but obviously no luck..
The phone's under warranty.. but guess this will be void as I'm s-off, etc etc? Will HTC be able to detect this?
See the link in my signature.
Sent from my HTC Desire using Flashes and Thunders
Thanks.. guess you meant the last link 'How the HTC works.."
If so. are you implying that my radio has corrupted and so it's shagged (or the bootloader's knackered... how could that happen?)
How can I tell which of those scenarios is the one I've got? Hpw do I know it the radio hast started?
If it is the radio that's knackered, I flashed that over a week ago and the mobiles been power-cycled many times in that period...
Or am I missing the point here?
I have another working Desire, could that help me in anyway to get the broken Desire to work....?
Oh well, with the lack of responses I guess the phone's bricked :crying:
Main question I have is if it's sent back to HTC, are they likely to fix it under warranty in its current state?
Added to this, anyone know what I did wrong, so I don't do it with my other Desire.
kevcal said:
Oh well, with the lack of responses I guess the phone's bricked :crying:
Main question I have is if it's sent back to HTC, are they likely to fix it under warranty in its current state?
Added to this, anyone know what I did wrong, so I don't do it with my other Desire.
Click to expand...
Click to collapse
As I could see many users are complaining for getting a permanenr brick after installing ICS roms, and most of them after Sandvold one. Just take a look at bricked threads in the past month or so. Am I right?
Sent from my HTC Desire using Flashes and Thunders
Hadn't realised that - would have avoided the ICS route if I had.
Was happy with SuperNova until I thought Sandvold's ICS was stable
Still can't figure what actually went wrong.
It may be that it's not about rom, but you never know.
Sent from my HTC Desire using Flashes and Thunders
Well sending it off to HTC, hoping they'll fix it under warranty........:fingers-crossed:
THIS LIMITED WARRANTY SHALL NOT APPLY IF THE DEFECT WAS CAUSED THROUGH ANY OF THE FOLLOWING:
a) the Product serial number, the accessory date code the IMEI number, water indicator or the warranty seal has been
removed, erased, defaced, altered or is illegible; or
b) deterioration of the Product due to normal wear and tear; or
c) use other than in accordance with the user manual, rough handling, exposure to moisture, dampness or extreme thermal
or environmental conditions or a rapid change in such conditions, corrosion, oxidation, unauthorized modifications
or connections, unauthorized opening or repair, repair by use of unauthorized spare parts, accidents, forces of nature, or
other actions beyond the reasonable control of HTC (including but not limited to deficiencies in consumable parts) unless
the defect was caused directly by defects in materials or workmanship. This Limited Warranty does not cover physical
damage to the surface of the Product including but not limited to cracks or scratches on the LCD screen or camera lens; or
d) the defects caused by the fact that the battery has been short-circuited or by the fact that the seals of the battery
enclosure or the cells are broken or show evidence of tampering or by the fact that the battery has been used in
equipment other than those for which it has been specified; or
e) the defect was caused by a defective function of the cellular network or other system; or
f) the Product software needs to be upgraded due to changes in cellular network parameters; or
g) the defect was caused by the fact that the Product was used with or connected to an accessory not approved or provided
by HTC or used in other than its intended use and where it can be shown by HTC that such defect is not the fault of the
Product itself.
Click to expand...
Click to collapse
kevcal said:
Well sending it off to HTC, hoping they'll fix it under warranty........:fingers-crossed:
Click to expand...
Click to collapse
g) the defect was caused by the fact that the Product was used with or connected to an accessory not approved or provided
by HTC or used in other than its intended use and where it can be shown by HTC that such defect is not the fault of the
Product itself.
Click to expand...
Click to collapse
Reading that makes me think they won't since rooting your phone and installing custom roms is against the intended use by HTC and in this case it really wouldn't be their fault. Having said that, if you contact them and they say they will then by all means get it fixed and I hope it turns out well for you
pawan1993 said:
Reading that makes me think they won't since rooting your phone and installing custom roms is against the intended use by HTC and in this case it really wouldn't be their fault. Having said that, if you contact them and they say they will then by all means get it fixed and I hope it turns out well for you
Click to expand...
Click to collapse
"used with or connected to an accessory"..
Doesn't sound like anything to do with roms to me... just unsupported hardware..?
Ah , reading the next bit I see what you mean:
"used in other than its intended use"... well I used it as a phone ...
Act dumb @ htc shop
Sent from my HTC Desire using xda app-developers app
Exactly.
Mobile's been returned Hopefully repaired(!) - will find out when I get home..!
Still wish I knew what I did though that caused the brick - bit apprehensive about playing around with it now!
Bricks are relatively rare though I guess.
Looks to me that Radio was corrupted - ie no charging light, but it did constantly buzz...
I programmed the radio over a week before it failed.. could it have flashed badly and setting Sandvold's ICS to 'not buzz when ringing' accessed something bad in the radio ROM and caused it to corrupt??
This doesn't sound likely...?
Next question is (bearing in mind I'm gonna avoid Sandvold's ICS just in case it was that!), what do I go for.
Questions I have...
I guess for a fully functioning mobile, the only option is to stick with GB..?
Do I need to go S-OFF any more to install ROMs?
Do I need a custom HBOOT any more?
Kev
kevcal said:
Questions I have...
I guess for a fully functioning mobile, the only option is to stick with GB..?
Do I need to go S-OFF any more to install ROMs?
Do I need a custom HBOOT any more?
Click to expand...
Click to collapse
1. based on your second and third questions, yes, stick with GB. 'fully functioning' definition varies between users, but the fact that the JB and ICS roms have Alpha/BETA status should tell you what you need to know. the choice is still yours though!
2. not strictly necessary, but is much more useful if things go wrong. so use revolutionary to s-off
3. if you're asking this question i wonder whether you know what the custom hboots are? you flash a custom hboot depending on the rom's system size. should be in the first post of each rom, if not search the thread for 'hboot'...strictly speaking you don't necessarily need a custom hboot, but most of the time you'll run out of space much quicker if you don't. once you understand what the hboot partition tables are it will make sense . you need s-off to change hboot, so this pretty much answers question 2.
Okay will stick with GB for now.. then again the JB roms are looking better all the time...
Okay will S-OFF again.. just wondered if it could have had any bearing on why my mobile bricked.
You're right - not really sure what a custom Hboot is.. it allocates different sized partitions for specific roms then?
Will have a read to try to understand things a bit more.
Thanks for clarification or at least putting me on the road to clarification(!)
kevcal said:
not really sure what a custom Hboot is.. it allocates different sized partitions for specific roms then?
Will have a read to try to understand things a bit more
Click to expand...
Click to collapse
http://alpharev.nl/
Sent from my HTC Desire
Typical - phone worked for 24 hours...
Now, doesn't power on.. screen stays black - no vibrate when I push power button.
Green led turns on when plugged into usb, when I press the power button the green led goes off, but screen still black - nothing happening.
Power button with 'back' or 'vol-down' depressed does nothing, black screen only.
Any ideas, or do I return it (again).
This will be the 4th time - will they be amenable to giving me a replacement do you think?
Well mobile back from HTC a second time; ran fine for a couple of days, so installed Supernova and all running fine now.
Gone S-OFF but left flashing radio alone - seems to work with 5.11.05.27 fine.
So that's it, will avoid ICS, etc just in case, but have no idea whether that's why the phone got screwed...
Mmm.. have now installed Mildwild with no problems..
Really think it was something to do with Sandvold'd ICS release, but have no way of knowing..!
My HTC one M7 is acting up very strangely. It is an ebay phone and it does work normally and shows no sign of abuse or damage. The screen however has some sort of random glitching. Horizontal lines appear at the top of the screen near the app drawer and then ghosting vertical lines appear as well especially with icons. The screen will also be a lighter color than normal. This happens about 80% of the time the screen is turned on. The other 20% it looks fine. It happens on boot screen and on Fastboot screen as well.
From what I can tell it had some custom firmware on it as the Fastboot screen showed tampered but it was S-On. Recovery would not load at all, just was blank then reboot. Showed 4.4.3 until I did a factory reset and then it showed 4.2.2. I tried using Rumrunner, and Firewater. I had WeakSauce working but could never get S-Off. I installed HTC Sync and did a repair which brought me up to 4.4.3 Sense 6 and no way to S-Off other than sunshine.
I don't want to shell out the money for Sunshine though if the screen is going to go bad. What do you guys think? I called HTC and it is 3 months out of warranty. Maybe I should try to get it to do a purple tint so I can send it in under that.
isaacws said:
My HTC one M7 is acting up very strangely. It is an ebay phone and it does work normally and shows no sign of abuse or damage. The screen however has some sort of random glitching. Horizontal lines appear at the top of the screen near the app drawer and then ghosting vertical lines appear as well especially with icons. The screen will also be a lighter color than normal. This happens about 80% of the time the screen is turned on. The other 20% it looks fine. It happens on boot screen and on Fastboot screen as well.
From what I can tell it had some custom firmware on it as the Fastboot screen showed tampered but it was S-On. Recovery would not load at all, just was blank then reboot. Showed 4.4.3 until I did a factory reset and then it showed 4.2.2. I tried using Rumrunner, and Firewater. I had WeakSauce working but could never get S-Off. I installed HTC Sync and did a repair which brought me up to 4.4.3 Sense 6 and no way to S-Off other than sunshine.
I don't want to shell out the money for Sunshine though if the screen is going to go bad. What do you guys think? I called HTC and it is 3 months out of warranty. Maybe I should try to get it to do a purple tint so I can send it in under that.
Click to expand...
Click to collapse
I am not sure if it is related to this issue.
https://code.google.com/p/android/issues/detail?id=70846
I was not able to determine what rom setup was on the phone that I couldn't S-Off. It was debloated and tamper flag was on. Tamper flag is off now but screen still is buggy.
Sounds like a hardware issue. Taking the ota to 4.4.3 and sense 6 should eliminate a software issue from being the culprit. Boot into fastboot, select recovery, and do a factory reset ....if that doesnt help, then my money is on a hardware issue.
ccarr313 said:
Sounds like a hardware issue. Taking the ota to 4.4.3 and sense 6 should eliminate a software issue from being the culprit. Boot into fastboot, select recovery, and do a factory reset ....if that doesnt help, then my money is on a hardware issue.
Click to expand...
Click to collapse
He sees the lines even in fast boot which makes me think it is definitely a hardware issue. I doubt factory resetting is going to do any good.
disconnecktie said:
He sees the lines even in fast boot which makes me think it is definitely a hardware issue. I doubt factory resetting is going to do any good.
Click to expand...
Click to collapse
Yea, I agree. But I hate to be the guy with nothing but bad news!
Hey guys thanks for the input. I went ahead and spent the money for Sunshine and I am now on CM11. Still have the same issue. I am thinking it is hardware as well especially since it shows in Fastboot and booting animations. I am thinking it is a memory issue though since it is random as to when it will be clear vs lines. I saw a post about LCD screens on laptops that showed common issues and the one that resembled my problem was a video ram issue. Not sure if there are tweaks I can do in CM11 to control that.
It still wasn't a bad deal since I only paid $100 for it and it has a clean esn.
Thanks guys, if I figure out a work around I'll post it.
isaacws said:
Hey guys thanks for the input. I went ahead and spent the money for Sunshine and I am now on CM11. Still have the same issue. I am thinking it is hardware as well especially since it shows in Fastboot and booting animations. I am thinking it is a memory issue though since it is random as to when it will be clear vs lines. I saw a post about LCD screens on laptops that showed common issues and the one that resembled my problem was a video ram issue. Not sure if there are tweaks I can do in CM11 to control that.
It still wasn't a bad deal since I only paid $100 for it and it has a clean esn.
Thanks guys, if I figure out a work around I'll post it.
Click to expand...
Click to collapse
Sounds to be more like a loose or broken cable to the LCD. That may be why you got it so cheap.