Database Users

G2 screen messed up?

My G2 just randomly yesterday started adding red lines and messed up colors to the screen, it's really hard to describe. I'll put up pictures later but it almost looks like the screen went to 64K colors? I've tried rebooting, flashing new ROMs, even in Recovery the android in the background has the same effect. So it must be something with the screen, anyone know what's wrong?

It sounds like the cable connecting the screen to the rest of the device is either coming loose or is damaged.
Sent from my HTC Vision using XDA App

That was my first thought as well... drop it lately?

opensourcefan said:
That was my first thought as well... drop it lately?
Click to expand...
Click to collapse
Nope... I was literally looking at it one second and it was fine, one minute later it was like that... I just bought it four days ago new and sealed off of eBay. Does HTC offer a manufacturer's warranty?

ShotSkydiver said:
Nope... I was literally looking at it one second and it was fine, one minute later it was like that... I just bought it four days ago new and sealed off of eBay. Does HTC offer a manufacturer's warranty?
Click to expand...
Click to collapse
I believe the manufacturer warranty is one year.
Sent from my HTC Vision using XDA App

Here are some pictures showing what's going on. You can see some better than others.
One
Two
Three
Four
Five
Six

Anyone? Tried contacting HTC support but all I get is
"Sorry, but either the page you were looking for can’t be found or we are having a problem making it come to life.
You might want to check out our Site Map for a full list of pages available on this site"
after I try sending an email. Any help?

It looks like it stopped dithering or something... i'd try reinstalling the rom.
Sent from my T-Mobile G2 running Cyanogenmod.

ibemad1 said:
It looks like it stopped dithering or something... i'd try reinstalling the rom.
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
I've already flashed three different ROMs.

Come on... anyone? I'm getting no help from HTC and my screen isn't improving.

You probably should call HTC

http://www.htc.com/us/support/hotline
Telephone
United States & Canada (English)
Language Hotline Days Hours
English 866-449-8358 7 days a week 6am EST to 1am EST 7 days a week

I am having the same issue with my Desire Z.
I'm wondering if it can be fixed without sending it back to HTC?

Well, both T-Mobile and HTC turned me away, saying I would've had to have gotten it from either of them to be able to be repaired. What do I do now?
Sent from my HTC HD2 using XDA App

Sirjokerthegod said:
I am having the same issue with my Desire Z.
I'm wondering if it can be fixed without sending it back to HTC?
Click to expand...
Click to collapse
That's what I'm hoping.
Sent from my HTC HD2 using XDA App

HTC does do non-warranty repair, for a price of course.

Is there any chance the ROM(s) you installed were wonky? ie were you using a beta, nightly, or something else? which ROMs have you tried? I had this happen when I used a kernel that was incompatible with the ROM I had installed, which is why I ask. Flashing a standard/respected ROM after a wipe fixed it for me.

Weaseal said:
Is there any chance the ROM(s) you installed were wonky? ie were you using a beta, nightly, or something else? which ROMs have you tried? I had this happen when I used a kernel that was incompatible with the ROM I had installed, which is why I ask. Flashing a standard/respected ROM after a wipe fixed it for me.
Click to expand...
Click to collapse
No, it's not a ROM, I've been on CM 7 RC0, CM 6 stable, stock Sense, and stock 2.2 and they all do the same thing, even in the recovery the background image has the same effect, so it's not a ROM issue.

ShotSkydiver said:
No, it's not a ROM, I've been on CM 7 RC0, CM 6 stable, stock Sense, and stock 2.2 and they all do the same thing, even in the recovery the background image has the same effect, so it's not a ROM issue.
Click to expand...
Click to collapse
It may be a defective ribbon cable for the display possibly a tear in one of the layers. I see this alot in phones I fix at work, and usually the only way to fix the issue is to replace the cable entirely. your only option is to send it out for warranty repair or buy the part yourself and do the fix.

[Q] Nexus One reboot when using 3g

hello guys I have a nexus with one gingerbread 2.3.4 and when I use the 3G network after 2-3 minutes the phone restarts. with this bug I can not use Internet
any ideas? Thanks!

Yes. Me to.

What ROM and/or kernel combo you guys using?

I have the stock rom ota gingerbread 2.3.4, nothing changed, full stock. I recently tried miui 1.5.20 the problem is the same. may be a hardware problem?

Does the phone get hot to the touch on the back? Does the phone still reboot if you turn off 3g data and you go exclusivly Wifi?
Had the same issue with my old Nexus 1. Called HTC support and they immediately said it was a defective board. RMA'd and got refurb, but at least it does not reboot when I use 3g.
Good luck.

thanks jhsiao36, think if I update the radio version 5.12.00.08 can change something or brought it in for service?

poltor said:
thanks jhsiao36, think if I update the radio version 5.12.00.08 can change something or brought it in for service?
Click to expand...
Click to collapse
I didn't help for me. I tried the 5.12.00.08 radio and it suffered from the same 3g reboots. But when I disabled 3g and used Wifi, never suffered from reboots.
If the phone is still under warranty, definitely encourage you to call them. HTC's customer and tech support is the best I've ever seen. They replaced it no questions asked, even though my phone is rooted and bootloader unlocked.

jhsiao36 said:
HTC's customer and tech support is the best I've ever seen. They replaced it no questions asked, even though my phone is rooted and bootloader unlocked.
Click to expand...
Click to collapse
+1 They are awesome to deal with. It really makes me sad that they are starting to lock down their phones, because I won't buy a phone if I can't run custom ROMs on it.
But with the radio, I highly doubt flashing to 5.12 would help. Google released the 5.08 radio with the OTA update to Gingerbread. If 5.12 was any better, I'm sure they would've included it. There had to have been a reason they stuck with 5.08.
If you aren't afraid of losing anything, or already made backups, you could try the passimg method of giving you a completely stock install. See if the problem occurs with that as well. This would rule out software vs hardware.

No one can really solve it?

JetChung said:
No one can really solve it?
Click to expand...
Click to collapse
I really don't think it can be resolve without sending it back to HTC for a replace/repair. As I said in my previous posts, I've tried 3 different ROMs - stock, cyanogenmod 6 and 7 - all exhibit the same issue - reboot when on 3g, but perfect if on Wifi. And yes, it will reboot even on a freshly install ROM (no apps installed).
HTC knows of this issue and they will replace/repair. I got a refurb and it works perfectly - stock, cyanogenmod 6 or 7.
Sorry, probably not the answer you wanted to hear, but search on <insert your favorite search engine> and you will find that this is a fairly widespread problem.

Thank you for your answer! It does not work, had sent a factory repair.

After several tests, on Monday I sent the phone in for service. I think it's a hardware problem, maybe a bad batch of motherboards.
my S / N: HT05... and your?
I will tell you just back from assistance.

Did you ever overheat it? I believe that the N1 has a problem if you really push it that it can overheat. Once it happens once it will happen again and every time it takes less and less to cause the reboot. Eventually it reboots just with 3G.
I was running mine in the car-mount with GPS, Google Maps (3G), screen on brightest, on a hot summer day while charging ... and it rebooted. Didn't think much of it but then it started rebooting every time I used GPS and charging.
In the end it was pretty near useless ... rebooting all the time. I sent it in twice (the first time they couldn't reproduce the problem) and the second time they replaced the board. Problem solved.
Now I am very careful not to overheat it.

Random reboots No matter the ROM/Kernel set up

I've been waiting a month to ask for help cause i'm stubborn and wanted to fix it on my own, but now i'm over it and accept the fact i need help haha. Basically, I've had this evo running CM7 and Destroyer with savage-zen kernels since january, i updated CM7 from a nightly to a RC and ever since i've been getting random reboots, i've tried everything, restoring my original nandroid, running stock RUU's and a combo of a million different roms and kernels with no luck, also updated radio/prl/NV. I've exhausted my resources now and dont know what else too try, anyone have any suggestions?

TimidRat said:
I've been waiting a month to ask for help cause i'm stubborn and wanted to fix it on my own, but now i'm over it and accept the fact i need help haha. Basically, I've had this evo running CM7 and Destroyer with savage-zen kernels since january, i updated CM7 from a nightly to a RC and ever since i've been getting random reboots, i've tried everything, restoring my original nandroid, running stock RUU's and a combo of a million different roms and kernels with no luck, also updated radio/prl/NV. I've exhausted my resources now and dont know what else too try, anyone have any suggestions?
Click to expand...
Click to collapse
So completely unrooted/returned to stock it STILL random reboots?
If so, sounds like a hardware related issue.

Yeah went all the way back to unrooted s-on, I was starting to think it was hardware related, thanks mattykins

I can confirm that this is a hardware issue. My first EVO had the exact same problem you had, and continued to get worse and worse to the point where it would cycle 10 times before actually staying on for a little bit.
I called Sprint and told them that I thought my phone was defective, and when I explained the problem they said it was a known issue and that it would be replaced free of charge.
A friend of mine is actually dealing with this very thing right now and he said that Sprint is now shuffling people off to HTC for defective phone replacements. If you are within 1 year of buying the phone it should be free, as per the manufacturer's warranty.

I also had this happen and got it replaced. Now I'm without root but at least my phone works. It's definitely hardware related.
Sent from my PC36100 using XDA App

I had the same problem, no matter the rom or kernel, it would reboot and get stuck in bootloop. I finally gave in and went to sprint, turned out it was something with the hardware that would heat up my battery and then when it got to a certain temperature it would cause it to reboot. Definitely take it into sprint.
Sent from my PC36100 using XDA App

Thanks everyone, but if I take it to Sprint I have the feeling ill still have to pay 100 cause the screen has a crack across the bottom.

TimidRat said:
Thanks everyone, but if I take it to Sprint I have the feeling ill still have to pay 100 cause the screen has a crack across the bottom.
Click to expand...
Click to collapse
Try anyway.
Technically you would win legally because the crack has nothing to do with the issue you're having thus the warranty is valid.
(Although I guess they could claim you must have dropped it and that could have damaged something internal)
But the worst case scenario is they say you have to pay the $100 to get a new one and if you don't you still have your phone.
The best case, they fix or replace it.
Either way, its worth a shot.

So why us Sprint detecting I'm in mikfroyo 4.62

Anyone know why when I tried to open a network support ticket they are detecting I'm on a mikfroyo rom. I changed Roms so many times the past 6months.. so what the hell is up with that:
They even said you have to be on a official Rom.. man how they detect this info is pretty funny. And how wrong it is.
But any way to fix that issue
Sent from my PC36100 using XDA App

Why do you think they would give you support when you voided your warranty by rooting and installing another ROM?
I mean seriously...

I don't need support. I do wish to inform them of their network problem here... If so I have 8 other people with Sprint who are official.. who can report the network problem aswell ... Why would I need support if my phone is perfectly fine. And besides the fact I'm not running the Rom they are indicating I am...
Sent from my PC36100 using XDA App

Again... think about it for a little bit. They don't know if you have 8 other people who are experiencing they same problem you are.
They're not going to waste their time with a problem that could be the result of a modded phone.

nemoid said:
Why do you think they would give you support when you voided your warranty by rooting and installing another ROM?
I mean seriously...
Click to expand...
Click to collapse
You only voided your warranty with HTC, not sprint. I've taken my rooted/S-OFF device many times and have talked to the store reps and they have no policy against rooted devices. There is stores that will give you a hassle just to be lazy, meanwhile other stores will ask you to simply flash back to stock to help narrow down issues caused by software or hardware.

Oh so a version from stock that just has apps removed that ate considered bloated. So that can be a phone error. Dude I've flashed many roms kernels and radios and its the network. I'm not after phone support. I don't need a warranty on my Damn phone but I pay them for service via their towers if they have issues with it then they should fix their network problems. I will pay insurion if I have phone issues its why I have them.
Sent from my PC36100 using XDA App

The guy just said to install a stock Rom and give him info. The guy was like okay 3rd party. You need to install stock . But he did agree there is probably a problem in the area.
Sent from my PC36100 using XDA App

ANyways the guy said I should keep stock until testing is done well. Im on a modified stock rom etc (testing this rom out). Anyways is there a way to show them my software/build number as stock or whatever to fool them when i re provision it to update their system?

nemoid said:
Again... think about it for a little bit. They don't know if you have 8 other people who are experiencing they same problem you are.
They're not going to waste their time with a problem that could be the result of a modded phone.
Click to expand...
Click to collapse
no they are not wasting their time providing CUSTOMER support to a paying CUSTOMER

How can Sprint finds out if your rooted with a custom Rom? Even they never saw the phone?
Sent from my PC36100 using XDA App

culua said:
How can Sprint finds out if your rooted with a custom Rom? Even they never saw the phone?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I used to Run Mikfroyo but the thing is I don't know how they know I was on a custom rom. Maybe when provision your phone it sends that data. Now I'm On a different rom but i was unaware how he knew. The guy *PinkElmo* basically just said to go back to stock ROM for the duration of the testing (sounds like he not only not has a problem with it but sounds like he uses custom as wellXD).
I'm still puzzled as to how they found out...

I also currently using mikfroyo 4.61. But I didn't start rooting after a month signing up.
Sent from my PC36100 using XDA App

culua said:
I also currently using mikfroyo 4.61. But I didn't start rooting after a month signing up.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I had to provision a few months back though... But It Got me wondering. I have been downloading a stock rom at 199mb it should take roughly 2-8 hours on the Sprints NOW DialUp Network

Sprint has a program called OMA-DM. This program has all the information from the status section of your device. When I worked for sprint we would have customers update their data profile, this would send the information to the tool. The rep can then see what rom you are on. However this did not work on AOSP roms since they do not update the profile.
If you want to fool sprint update your profile under a stock unmodified rom, then flash to AOSP, the info for the sense rom would be still in the system.
Furthermore they can see if you have updated the profile, so if you tell them that you did they will be able to see if you actually did or not.. They are also able to view all the transactions with dates and times between your phone and the tool.
My advise to you is to suck it up and run the official rom until the testing is over, usually about a week.
Also sprint has no control over a custom rom, so they automatically have you update profile and firmware to the current version to ensure that the phone is working to their standards and things that they have control over.
TL;DR - Quit complaining and use a stock rom so sprint can do their testing.

The complaining in this thread has me puzzled. Run a stock Tom for them to test, reinstall favorite Tom when done...

Pao23 said:
The complaining in this thread has me puzzled. Run a stock Tom for them to test, reinstall favorite Tom when done...
Click to expand...
Click to collapse
is your favorite "Tom" a "Tom Collins"? hahaha, sorry. i had to.

Thanks and for data profile. Just the one under updates? If so it would have shown mikg if clean rom I got a download of stock and was going to flash it when i can before Tuesday since Monday is a holiday...
Thanks for informing me how they detect what Rom your on.
Sent from my PC36100 using XDA App

I imagine sprint can know quite a bit about your phone. When I had my diamond, (or maybe it was my Evo, I forget) something wasn't working right. I got on the phone with a tech, and he proceeded to to operate my phone while I was holding my phone. I could see the screen clicks, and him going from one menu to another, operating my phone remotely. Blew me away.
As for the monitoring SW mentioned earlier in this thread, does it read build prop values? Cuz I'm guessing that's how they get your device info.
Lastly, post 2 and 3 about not expecting sprint to work on/assess your rooted phone. BS. Sprint has given mixed signals about this. I know there have been internal memos released stating they now will honor rooted phones. I think lazyness is the culprit when a comes to CSRs or techs rejecting for root. I've always taken in my rooted phone and put a stockish rom on it first, when I have a hardware problem (blown speaker, broken screen, etc.)
sent from xda app on drews ics

cmsjr123 said:
Thanks and for data profile. Just the one under updates? If so it would have shown mikg if clean rom I got a download of stock and was going to flash it when i can before Tuesday since Monday is a holiday...
Thanks for informing me how they detect what Rom your on.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yes the one under the updates.
scottspa74 said:
I imagine sprint can know quite a bit about your phone. When I had my diamond, (or maybe it was my Evo, I forget) something wasn't working right. I got on the phone with a tech, and he proceeded to to operate my phone while I was holding my phone. I could see the screen clicks, and him going from one menu to another, operating my phone remotely. Blew me away.
As for the monitoring SW mentioned earlier in this thread, does it read build prop values? Cuz I'm guessing that's how they get your device info.
Lastly, post 2 and 3 about not expecting sprint to work on/assess your rooted phone. BS. Sprint has given mixed signals about this. I know there have been internal memos released stating they now will honor rooted phones. I think lazyness is the culprit when a comes to CSRs or techs rejecting for root. I've always taken in my rooted phone and put a stockish rom on it first, when I have a hardware problem (blown speaker, broken screen, etc.)
sent from xda app on drews ics
Click to expand...
Click to collapse
They used an application call LogMeIn Rescue. It gives them the ability to remotely view/control a pc, windows or blackberry phone. Its actually a lot easier to do it for a customer more often then trying to walk them through it.
Yes the information displayed in the about phone section is stored in the build.prop.
As for the software; software plays a factor in how the device operates and communicates with the network. Sprint has designed the stock software on their devices to their standards. They know their software and how it works. Now take a custom rom, one that has be frankenstined together. How do you expect a company to properly troubleshoot and diagnose a problem that could very well be related to the customer software?
I totally agree with the laziness part on the Tech Reps, after working with the company for several years, Id have to say most of the reps were less educated or technically minded about the device that they were working with. I could not tell you how many times I would hear customers complain about the Tech Reps.
Going to a hardware issue, Custom software would not break the screen, blow a speaker, or otherwise cause physical damage to the device (with the exception of a battery). So these should have no effect on hardware warranty's or exchanges.

Galaxy S4 Vibration Not Working Fix

Story: My mom hates stock touchwiz so I went ahead and installed Cm10.1 on it. She loves it. I own an S2 myself, so its not exactly my phone.(Waiting for the new Nexus or Moto X). Today I realized that the Vibration wasn't working... Thinking it was a software problem, I quickly flashed stock firmware on it to see if that would solve the problem. I was thinking it may have been a broken kernel feature or something. This didnt solve the problem. Now I was getting worried. There may have been a possibility that the kernel could have fried the motor.
This is a $650 dollar phone. She just got it a few weeks ago. I tried different roms, kernels, everything.
I ran into an idea. I once fixed my friends stuck power button my banging it against my table. (funny I know)
Fix: Bang the phone on your knuckles or wrist. Yep. Solved the problem. Figured it was a stuck motor. HOWEVER this did not fully solve the problem. The motor would seize again after a while; Applied same process to fix it. This would only fix it for a while so, In my case, it wasn't a true fix. It may come in handy for those where it was only a stuck motor. Seems like either my vibrate motor is dislodged from the leads or the motor is Semi-DOA.
Anyways, This is a $650 phone. Really? This is Chinese knockoff quality control. There are loads of people having problems with this phone from sound issues to crazy ghosting on the screen. There isn't an excuse. Seems like imma have to set up an RMA or something.

Since your phone is rooted i would suggest to bring it to 2nd hand cellphone shops or repair shop to fix it.... maybe they can fix your problem....
If i helped don't forget to press the thanks button... :thumbup:
Sent from my GT-I9505 using
xda app-developers app

bryanchan727 said:
Since your phone is rooted i would suggest to bring it to 2nd hand cellphone shops or repair shop to fix it.... maybe they can fix your problem....
If i helped don't forget to press the thanks button... :thumbup:
Sent from my GT-I9505 using
xda app-developers app
Click to expand...
Click to collapse
I could do that. Couldnt I use stock firmware and use triangle away?
1. Restore to stock
2. Root
3. Use triangle away
4. Restore to stock again.
?? I should look like I never messed with it?
I would use my warranty while I still have it.

I think you could do that...
1. Backup current rom... use cwm....
2. Download stock rom for your phone
3. Use via odin to install...
4. After install check if your still rooted by using root checker download free from Google play...
5. If your not rooted anymore then your good to go...
* using odin is a complete wipe also root... incase you get stuck on boot loop use your backup to restore... and try reflashing it...
If i helped dont forget to press thanks button...:thumbup:
Sent from my GT-I9505 using
xda app-developers app