Database Users

Dead camera on every rom....

I for the life of me cant figure out why my camera is completely dead! I have FULLY wiped all caches,everything under 'WIPE' via AMONS and even formatted my SD card as well as trying an alternate SD card(both 8GB--C6speed)--never had a problem w either card on ANY ROM...ALL OF A SUDDEN the past 2days my camera goes to a FULL BLACK SCREEN,when pressing the CAMERA icon. Occasionally the taskbar will remain uptop but will timeout when screen display shutsoff. Now if i launch CAMERA via DESIRE ROM(KING),ill get the notice about clicking trackball to resume camera but as soon as i click it,the message dissapears and the screen will go back to black screen again...and repeat. I SWEAR i have DONE MULTIPLE COMPLETE WIPES AND REFORMATS so im left to believe its THE HARDWARE itself! CAN ANYBODY PLEASE LEND ME A HAND IF the similar problemhas occured...On the Nandroid backups that ive restored from FULLY FUNCTIONING bkups,if i launch NEXUS TORCH it will say CANNOT ACCESS LED---this is THE ONLY info besides the "camera wake message"mentioned earlier that i can provide. Thanks in advance and pleas edont flame for NOT being in Q&A bc this is more of a DEV related restore question.
**oh and BTW--I DID TRY TO INSTALL the DESIRE R2 cam fix and does nothing. I tried it when all was working fine early in the week and it did nothing to help FLASH timing for me,so i NAN restored back to prior state and CAMERA continued working until about THURSDAY night--regardless--PHONE is in OUT OF BOX STATE--MINUS UNLOCKED and it STILL doesnt work!---PEACE and Happy Mothers Day to any Mothers out there in XDA world!

***Captain Obvious to the Rescue!!***
Your hardware has malfunctioned. Contact HTC for a repair.

1. you may have a broken camera, try a stock rom
2. your caps lock button is definitely broken
3. you posted in the wrong section

ghostrida said:
1. you may have a broken camera, try a stock rom
2. your caps lock button is definitely broken
3. you posted in the wrong section
Click to expand...
Click to collapse
1. i should have known you were from Philly and cant read--I TRIED STOCK ROM
2. CAPS is to put highlights on key terms so idiots dont read over the fact that I DID TRY STOCK ROM---see how that helps?
3. Thanks for your informative responses---any suggestions from CAPTAIN OBVIOUS how to get service on a ROOTED device without being charged full price on the phone?? Ahhh--thought not!--So i tried here to see if anyone else had similar situation. AGAIN-thanks for your help as well SERIAL TOON--geez

If it's a hardware failure they won't charge you.

I think it will help if you go through Google Cust service first...they will end up redirecting you to HTC repair. Provide all truthful information on your issue, proving that you have done some legitimate trouble shooting and they will realize that it is a hardware issue, not the ROM flashing or bootloader unlocking that caused the problem. Someone else on the xda forums had a rooted phone with bluetooth problem and was able to send to HTC for repair for free...with a 4 day turnaround!
Good luck!

What do you base this on...Heresay?
BlueScreenJunky said:
If it's a hardware failure they won't charge you.
Click to expand...
Click to collapse
I didnt intend to sound rude,im just a little pissed right now..I Only ask bc i already had an issue in January days after receipt of phone. Issue was solved by sending me a new battery bc other was causing random shutdowns (ive since forwarded this info to another XDAmember that had exact same issue and they give him replacement phone at 1st but issue continued to occur--i told him about my story after he posted his problem, he contacted them this weekend and confirmed with me today that a new battery was on the way..see my public IM's for info). Anyway,when i was dealing with the battery issue they said they would definately NOT be able to fix under warranty bc the phone is rooted and unlocked. I can attest to the few people on here that said theyve been successful in such cases,but either way,IVE ALREADY STATED that i tried the DESIRE R2 camera kernal to see if that helps,so im not going to be dishonest and tell them i havent tried anything other than custom roms. Again..positive suggestions or similar experiences with warranty info would be appreciated....trollers looking for a funny post or to degrade people can eat one!

joshlusignan said:
I think it will help if you go through Google Cust service first...they will end up redirecting you to HTC repair. Provide all truthful information on your issue, proving that you have done some legitimate trouble shooting and they will realize that it is a hardware issue, not the ROM flashing or bootloader unlocking that caused the problem. Someone else on the xda forums had a rooted phone with bluetooth problem and was able to send to HTC for repair for free...with a 4 day turnaround!
Good luck!
Click to expand...
Click to collapse
Thanks JOSH, ill look into it tommorrow--as i stated tho--i feel im being dishonest for trying the DESIRE R2 cam and saying that they should cover it---uninformed people will assume THAT couldve caused it,even though i used phone afterwards for a few days w no side effects

Hey Milton, like others have mentioned in here might want to try flash back to stock and seeing if the problem persists. If it does then your looking at a hardware problem and you should contact HTC/google for repair.

Yea...i was thinking that from get go--(hardware prob). Im on cheesy STOCK ROM right now and have been for cpl hrs...but its obvious its gotta be hardware...NOW comes the crappy part of trying to explain it to HTC when attempting to get an RMA!--Yee Haa!

MOD PLEASE CLOSE OR DELETE---THANKS!

Milton, among the items on the very small list of things folks around here want in return for helping you is that you lay off the caps. Doesn't highlight anything that you'd want to highlight.
Doug

Okay,,,this is weird!!..My TORCH hadnt been working at all either, the whole time ive had the camera problem. Now ,the torch will work for ONE TURN ON, then if i launch CAMERA, the cam still doesnt work. i have to HOME and HOME only to get back to home screen..BACK ARROW does nothing except vibrate,indicating touch response. If i then re-launch TORCH, it doesnt work....!??SOMETHING is ODD--and im split whether its hardware- or some sorta SYSTEM file that stays stuck even after all STOCK FLASHES and everything!--again,reminder..the LED TORCH hadnt worked up until this point--unit has NEVER been dropped,slid out of pocket from 1foot high onto superthick carpet,so i doubt its a loose internal cable...Hmmm...

milton007 said:
Okay,,,this is weird!!..My TORCH hadnt been working at all either, the whole time ive had the camera problem. Now ,the torch will work for ONE TURN ON, then if i launch CAMERA, the cam still doesnt work. i have to HOME and HOME only to get back to home screen..BACK ARROW does nothing except vibrate,indicating touch response. If i then re-launch TORCH, it doesnt work....!??SOMETHING is ODD--and im split whether its hardware- or some sorta SYSTEM file that stays stuck even after all STOCK FLASHES and everything!--again,reminder..the LED TORCH hadnt worked up until this point--unit has NEVER been dropped,slid out of pocket from 1foot high onto superthick carpet,so i doubt its a loose internal cable...Hmmm...
Click to expand...
Click to collapse
That seriously hurts my eyes to look at. Try using proper punctuation and grammar. It's very simple and still gets your point across.
As for your phone. Call Google which will probably have you call HTC. People have gotten their rooted devices fixed for free if it's a genuine hardware problem and nothing caused from the rooting process.

milton007 said:
Okay,,,this is weird!!..My TORCH hadnt been working at all either, the whole time ive had the camera problem. Now ,the torch will work for ONE TURN ON, then if i launch CAMERA, the cam still doesnt work. i have to HOME and HOME only to get back to home screen..BACK ARROW does nothing except vibrate,indicating touch response. If i then re-launch TORCH, it doesnt work....!??SOMETHING is ODD--and im split whether its hardware- or some sorta SYSTEM file that stays stuck even after all STOCK FLASHES and everything!--again,reminder..the LED TORCH hadnt worked up until this point--unit has NEVER been dropped,slid out of pocket from 1foot high onto superthick carpet,so i doubt its a loose internal cable...Hmmm...
Click to expand...
Click to collapse
You should send it to HTC for repair. Charging fee or not, but thats the only option to you right now because its a hardware failure.

mikroN1 said:
That seriously hurts my eyes to look at. Try using proper punctuation and grammar. It's very simple and still gets your point across.
Click to expand...
Click to collapse
I was thinking the exact same thing, don't know where he must have learned how to type. Then you criticize people from Philly, or whatever its called somewhere, for not knowing how to read. I would say mirror that advice and learn how to type.. type properly.

Torch will work until camera app is used then it wont work again until i reboot. After reboot, torch will work ONLY on regular/lower setting. MAX brightness will not work. Toggle back to LOW setting and torch will work again. Im going to try what DOUG suggested bc that is the only thing i havent tried yet...but the way torch and camera are acting up and requiring reboots keeps me willing to try software tricks first...WHAT ties the TORCH's HI setting to the camera app adn yet keeps the LOW setting seperate!??..ill try the TORCH dev real quick for some insight on how the two work hand in hand.Thanks for anyone using their time to help instead of criticize. Sorry for mocking ones ability to read but i was quite [email protected] time bc i lost a major function on my phone.My apologies to all

Seriously Milton? More?
milton007 said:
Please DONT lend assistance to someone like this. IF they cant bither to read THE MOST SIMPLEST instructions, they should NOT be attempting this in the first place...thats just sheer ignorance...
Click to expand...
Click to collapse
The attitude, hostility and the caps are not welcome here.

Along with the others I have no sympathy for you. Learn proper grammar and get a better attitude.

Troll much? Go tell your mother happy mothers day if you have that much time to pull up old posts from people asking questions in a 'kernal forum' about basics. Basics that anyone should know, if not they stand a much better chance on damging their phone. It wasnt being ignorant. Since you know everything there is to know about everyones posts, tell me where the topic dealing with my specific camera issue has been previously posted and ill be glad to read and search thru that forum. I wasnt the one asking questions about something mentioned in the OP (uh oh i used caps--oh geesh-someones gonna be saaad now!)and numerous pages before. Im sorry i dont spend all my life on forums to know that only words approved for caps are indeed CAPITALIZED. Petty little boy-and by the way, i was trying to stress your good advice by typing your name in caps so people would credit you with the help-Sorry to have taken your precious time sir. Good day.

Hard bricked and possible hardware issue. I need advice please.

I recently received a used epic 4g when a friend replaced his phone, all was good but then yesterday the phone froze. I took the battery out and powered it back on it then took a long time to boot (2 minutes+) and once it finally did boot it was unusable and very unresponsive. I looked online and got into restore mode and then encountered a problem, my buttons at the bottom don't work therefore I could not hit the home button to select an option.
So I then used Odin to restore it (Used stock stuff). After I restored it it was working fine again. Then today i dropped it 2 feet off my bed and it went back to booting slow and then being unresponsive once booted. I then tried to restore it with Odin again but I made a mistake and didn't put the PDA file in and now my phone seems to be hard bricked (noob move I know).
I am considering sending it in for JTAG but I have some questions. Do you guys think the SLOW booting and unresponsive once booted issues were hardware issues? Will it just do that again eventually after I pay for it to be JTAG fixed? Also do you think they would be able to fix the buttons at the bottom? I would appreciate any advice.
Also please don't kick me when I am down, I know not double checking my Odin stuff was a dumb move, that's not what this thread is about.

So to just be sure, you can't power it on at all? The slow booting seems like a ROM problem. If you can get into Download mode you can fix it. If not, then you are definitely bricked and need to take it in.
If you could though, just reodin the proper files WITHOUT rushing.
I've dropped my phone everyday (I've even found out gorilla glass is ass since it cracked) but its always booted unless I did some dumb **** to it.
Sent from my SPH-D700 using xda premium

A_Flying_Fox said:
So to just be sure, you can't power it on at all? The slow booting seems like a ROM problem. If you can get into Download mode you can fix it. If not, then you are definitely bricked and need to take it in.
If you could though, just reodin the proper files WITHOUT rushing.
I've dropped my phone everyday (I've even found out gorilla glass is ass since it cracked) but its always booted unless I did some dumb **** to it.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Thanks for the reply
Correct I can't get it to power on at all. A second opinion on whether or not there was a hardware issue would nice, it just seems odd to me that the exact same thing would happen again a day later. When I bricked it I accidentally only used a pit file. When I did it right the first time I followed a guide and had a pit file and a PDA file, I assume one of those is(or includes) the ROM but I don't really know a lot about this stuff. I am considering just selling this one on ebay as-is if you guys think its a hardware issue and getting a new phone but if not I'll send it to be fixed.

JoeCow said:
Thanks for the reply
Correct I can't get it to power on at all. A second opinion on whether or not there was a hardware issue would nice, it just seems odd to me that the exact same thing would happen again a day later. When I bricked it I only had a pit file. When I did it right the first time I followed a guide and had a pit file and a PDA file, I assume one of those is(or includes) the ROM but I don't really know a lot about this stuff. I am considering just selling this one on ebay as-is if you guys think its a hardware issue and getting a new phone but if not I'll send it to be fixed.
Click to expand...
Click to collapse
try removing the battery. then try to get into download mode with it plugged into the computer only no battery also remove sd card.

tazfanatic said:
try removing the battery. then try to get into download mode with it plugged into the computer only no battery also remove sd card.
Click to expand...
Click to collapse
Thanks!! that did it. I had actually already tried that but tried it again when you suggested it I couldn't get it initially but kept trying and eventually tried unplugging it and plugging it back in while holding one and power the whole time and that got it. So was the slow boot thing happening twice just unlucky or is there something else I need to root or whatever?

JoeCow said:
Thanks!! that did it. I had actually already tried that but tried it again when you suggested it I couldn't get it initially but kept trying and eventually tried unplugging it and plugging it back in while holding one and power the whole time and that got it. So was the slow boot thing happening twice just unlucky or is there something else I need to root or whatever?
Click to expand...
Click to collapse
My guess is the slow booting was data corruption. A clean install should fix that. After Odining in the stock EL30 run it like that for a few days to see how it is working before looking into rooting it and a custom ROM.
Sent from my SPH-D700 using xda premium

kennyglass123 said:
My guess is the slow booting was data corruption. A clean install should fix that. After Odining in the stock EL30 run it like that for a few days to see how it is working before looking into rooting it and a custom ROM.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
what kenny said

Thanks guys, saved me $50s should i have sent it in. I appreciate it. I watched a few of the videos on rooting it and I saw the recovery program used to root things lets you use the camera button as apposed to the home button for selecting things. Think I should switch to that since my bottom buttons are broken? It looked like I probably wouldn't be able to navigate back in menus after selecting something but that would be better then not being able to select anything.

JoeCow said:
Thanks guys, saved me $50s should i have sent it in. I appreciate it. I watched a few of the videos on rooting it and I saw the recovery program used to root things lets you use the camera button as apposed to the home button for selecting things. Think I should switch to that since my bottom buttons are broken? It looked like I probably wouldn't be able to navigate back in menus after selecting something but that would be better then not being able to select anything.
Click to expand...
Click to collapse
If they are still broken after a fresh Odin then yes the newer CWM will work fine for you. There are widgets somewhere (don't remember) to add those buttions to your screen once you get it working right.

If the buttons really are toasted there are two fairly good onscreen button apps available. One is called Zmooth and the other is called Button Savior.

[Q] Help please. Major Touchscreen issues really really need help!

Hello xda. I searched and searched but didn't find someone with the same problem as me. If there is an existing thread, would you please direct me to it and close this one? Alright so for Christmas i got a 32gb nexus 7. it worked great for the first few months. in the last 2-3 weeks though, it was become unusable. it has a weird issue where it doesn't register my touches, and no its not a sensitivity issue, I got it to load a multhitouch counter app thing, and in the upper right corner, it randomly thinks its touching there (its completely random, but it does it more often than not). so when i try to touch something i want,the screen just spazes. and it spazes if i just unlock it and let it sit. i can't even use the tablet anymore. its not a software issue (im not 100% sure but pretty sure) because i managed to reboot into recovery and it freaked out and clicked a bunch of things (touch CWM) and just completely freaked out. so now i just leave my tablet off and let it sit there. i am debating returning it to google as a defect, but i thought id go to xda first. thanks to anyone who helps me. if you need anymore details dont hesitate to ask, i probably forgot some anyways:silly:

Before you send it back to Google go into the bootloader and do 'fastboot oem lock'

Boncey said:
Before you send it back to Google go into the bootloader and do 'fastboot oem lock'
Click to expand...
Click to collapse
yeah if i send it back im definitely going to do a factory reset im just nervous that they wont buy the "factory defect" aspect because of a few minor scratches on the screen

Lines across screen/ Hardware problem

My Asus TF300T has been starting to act up lately. When I access the settings menu faint grey lines start to appear which run across the screen. When I change to portrait the lines disappear for a split-second and then reappear black. When accessing Google Play I see the same thing. The power menu and other menus appear to have a pixelated background and are 'blocky'. It also happens in the ASUS File Manager on the white background (faint lines).
I am confused as to what's causing them. It appears to me to be a graphics-related issue as I have taken screenshots and viewed them on my computer and they appear pixelated on the TF300T but not on my computer. I have cold booted and performed a full factory reset. I have also switched to Safe Mode with no change (lines still appearing). I am using the Jelly Bean 4.2 launcher and am stock. The tablet hasn't been dropped and has been protected. It's only 4 months old and I bought it from Argos in the UK.
It's a shame because I like this tablet
Thanks.

mr.fast said:
My Asus TF300T has been starting to act up lately. When I access the settings menu faint grey lines start to appear which run across the screen. When I change to portrait the lines disappear for a split-second and then reappear black. When accessing Google Play I see the same thing. The power menu and other menus appear to have a pixelated background and are 'blocky'. It also happens in the ASUS File Manager on the white background (faint lines).
I am confused as to what's causing them. It appears to me to be a graphics-related issue as I have taken screenshots and viewed them on my computer and they appear pixelated on the TF300T but not on my computer. I have cold booted and performed a full factory reset. I have also switched to Safe Mode with no change (lines still appearing). I am using the Jelly Bean 4.2 launcher and am stock. The tablet hasn't been dropped and has been protected. It's only 4 months old and I bought it from Argos in the UK.
It's a shame because I like this tablet
Thanks.
Click to expand...
Click to collapse
If it were mine I would use App Backup. Be sure to check apps and data and when presented check copy to external sdcard.
Download stock firmware 4.2(10.6.1.8), unzip once and place on internal sdcard. If you don't receive the update notice in three minutes reboot tablet and wait another three. When you get the update notice accept and wait for completion as usual.
Good Luck!
Note: This should help decide whether it is hardware or software.

tobdaryl said:
If it were mine I would use App Backup. Be sure to check apps and data and when presented check copy to external sdcard.
Download stock firmware 4.2(10.6.1.8), unzip once and place on internal sdcard. If you don't receive the update notice in three minutes reboot tablet and wait another three. When you get the update notice accept and wait for completion as usual.
Good Luck!
Note: This should help decide whether it is hardware or software.
Click to expand...
Click to collapse
I am already using that firmware version so it won't work.
Thanks anyway.

mr.fast said:
I am already using that firmware version so it won't work.
Thanks anyway.
Click to expand...
Click to collapse
You can rename it US_epad-user-10.4.4.20 or what ever that previous version of firmware was pretty sure it was that. When update comes up it will say if want to downgrade and accept but it will just reinstall you're current version. Now not sure if your unlocked as when i did this for a random reboot issue i was unlocked but worked for me and acts just like an update everything else should be the same but do backups just to be safe.
Correction thats US_epad-epad-user-10.4.2.20 and us as doesnt have to be that if WW then use that or etc. Hope that works
And as for unlocking may not want to do that as it will void warranty if need to send it in but sure everyone know that.

aerdely said:
You can rename it US_epad-user-10.4.4.20 or what ever that previous version of firmware was pretty sure it was that. When update comes up it will say if want to downgrade and accept but it will just reinstall you're current version. Now not sure if your unlocked as when i did this for a random reboot issue i was unlocked but worked for me and acts just like an update everything else should be the same but do backups just to be safe.
Correction thats US_epad-epad-user-10.4.2.20 and us as doesnt have to be that if WW then use that or etc. Hope that works
And as for unlocking may not want to do that as it will void warranty if need to send it in but sure everyone know that.
Click to expand...
Click to collapse
OK, thanks. Will post back if it works or not. Thanks to the poster above too.

mr.fast said:
OK, thanks. Will post back if it works or not. Thanks to the poster above too.
Click to expand...
Click to collapse
Ok and if nothing else can refer to this thread for touch screen and pcb issues not sure if anyone has had same issue but can read through and ask question because alot seem experience with some of this. Good luck.
http://forum.xda-developers.com/showthread.php?t=2091233

mr.fast said:
I am already using that firmware version so it won't work.
Thanks anyway.
Click to expand...
Click to collapse
It works for me, I have used that method several times including 10.6.1.8 and 10.4.2.20. You can also upgrade and downgrade this way if you have Asus stock recovery.

tobdaryl said:
It works for me, I have used that method several times including 10.6.1.8 and 10.4.2.20. You can also upgrade and downgrade this way if you have Asus stock recovery.
Click to expand...
Click to collapse
I've placed the blob file in the latest firmware's zip folder from the (4.1 )10.4.2.20 firmware in another zip folder on the tablets root storage and nothing. I called the file WW_epaduser_10_4_2_20_UpdateLauncher.zip - any suggestions?

mr.fast said:
I've placed the blob file in the latest firmware's zip folder from the (4.1 )10.4.2.20 firmware in another zip folder on the tablets root storage and nothing. I called the file WW_epaduser_10_4_2_20_UpdateLauncher.zip - any suggestions?
Click to expand...
Click to collapse
Exactly what are you trying to do. All you have to do is raname the latest update zip after download and unzipping once from the 10.6.1.8.zip or cant remember exactly but what ever it is to WW_epad-user-10.4.2.20.zip
That the way most use and seems to work. No need to replace the blob file or etc just renaming the latest update zip to that should work and after maybe sometime either rebooting or waiting couple mins for it to show up in notfication bar. Replaceing the file inside the update zip its self may affect the signature or etc and may not work even if option does come up. Another way after placing on root of sdcard or internal storage which is what i do is just remove and replace the sdcard should pop up right away.
Yea just placing the blob file into a zip folder and naming it that wouldnt work as it checks for signatures atleast unless unlocked but not totally sure on that. Try what i had stated if your trying to downgrade take the 4.1.1 update file and name it WW_epad-user-10.4.2.20.zip or just rename the latest update zip to that works every time for me.
Tell you the truth it does sound more like a hardware problem just reflashing the update is a way to be sure. I'd more in the way of thinking of sending it in for service in your case atleast if you still have warranty i would. I've been through 2 seperat device still get random reboot with this new update tried reflashing couple times etc fixes temporarly but seems to come back almost considering sending to asus my self at this point since have warranty. Usually the best bet.

aerdely said:
Exactly what are you trying to do. All you have to do is raname the latest update zip after download and unzipping once from the 10.6.1.8.zip or cant remember exactly but what ever it is to WW_epad-user-10.4.2.20.zip
That the way most use and seems to work. No need to replace the blob file or etc just renaming the latest update zip to that should work and after maybe sometime either rebooting or waiting couple mins for it to show up in notfication bar. Replaceing the file inside the update zip its self may affect the signature or etc and may not work even if option does come up. Another way after placing on root of sdcard or internal storage which is what i do is just remove and replace the sdcard should pop up right away.
Yea just placing the blob file into a zip folder and naming it that wouldnt work as it checks for signatures atleast unless unlocked but not totally sure on that. Try what i had stated if your trying to downgrade take the 4.1.1 update file and name it WW_epad-user-10.4.2.20.zip or just rename the latest update zip to that works every time for me.
Tell you the truth it does sound more like a hardware problem just reflashing the update is a way to be sure. I'd more in the way of thinking of sending it in for service in your case atleast if you still have warranty i would. I've been through 2 seperat device still get random reboot with this new update tried reflashing couple times etc fixes temporarly but seems to come back almost considering sending to asus my self at this point since have warranty. Usually the best bet.
Click to expand...
Click to collapse
Thanks - It also sounds like a hardware problem to me but it's worth a try. In the UK if you return it within 6 months you may receive a replacement. I could also RMA the tablet.
I'll post back soon.

mr.fast said:
Thanks - It also sounds like a hardware problem to me but it's worth a try. In the UK if you return it within 6 months you may receive a replacement. I could also RMA the tablet.
I'll post back soon.
Click to expand...
Click to collapse
Ok if flashing doesnt work then yes i'd just do a replacement what i did with my original that had problems and only has 30 days but got lucky. Good luck it's worth a try there are some other threads on here on how to do it if can't figure it out but i've used i method i stated couple times and it work for flashing atleast but fix my problem temporarily. If anything else don't be affraid to ask just don't unlock or would most def mess up your chancefor rma atleast if not exchange too.

aerdely said:
Ok if flashing doesnt work then yes i'd just do a replacement what i did with my original that had problems and only has 30 days but got lucky. Good luck it's worth a try there are some other threads on here on how to do it if can't figure it out but i've used i method i stated couple times and it work for flashing atleast but fix my problem temporarily. If anything else don't be affraid to ask just don't unlock or would most def mess up your chancefor rma atleast if not exchange too.
Click to expand...
Click to collapse
Thanks. I'm in the middle of downgrading now.
Hope it works :fingers-crossed:

mr.fast said:
Thanks. I'm in the middle of downgrading now.
Hope it works :fingers-crossed:
Click to expand...
Click to collapse
Good luck also hope it works like said method should just not sure if would fix the problem could be something with your nvidia chip that process' your video sort of what it sounds like to me or something atleast is affecting your video. Like said i posted a link for you with people experiencing these types of problems just give it a read through most replace there lcds and mainboard or digitizers depending on what it is because they have no warranty but they probably would know what the problem is if you asked. As you said you can exchange it i'd just go for that my self.

aerdely said:
Good luck also hope it works like said method should just not sure if would fix the problem could be something with your nvidia chip that process' your video sort of what it sounds like to me or something atleast is affecting your video. Like said i posted a link for you with people experiencing these types of problems just give it a read through most replace there lcds and mainboard or digitizers depending on what it is because they have no warranty but they probably would know what the problem is if you asked. As you said you can exchange it i'd just go for that my self.
Click to expand...
Click to collapse
It didn't fix the problem. Still lines and graphics glitches appearing.
I'll exchange.
Thanks.
I also performed a factory reset after downgrading the tablet which did'nt work...

mr.fast said:
It didn't fix the problem. Still lines and graphics glitches appearing.
I'll exchange.
Thanks.
I also performed a factory reset after downgrading the tablet which did'nt work...
Click to expand...
Click to collapse
Well like said atleast you know now sucks i didn't fix it but didn't sound like it would. Was worth a try. Hope the new one turns up no problems should i was ok after.

Just before I return it to the store tomorrow I am still questioning the cause of the problem. The strange thing is that it doesn't appear on everything. Just on some gradients and backgrounds. Also, Google Now force closes and so does Email. I downgraded but my data was left intact, so I reset the device but the problem still persists.
Just a last final try before it goes back

mr.fast said:
Just before I return it to the store tomorrow I am still questioning the cause of the problem. The strange thing is that it doesn't appear on everything. Just on some gradients and backgrounds. Also, Google Now force closes and so does Email. I downgraded but my data was left intact, so I reset the device but the problem still persists.
Just a last final try before it goes back
Click to expand...
Click to collapse
Tell you the truth I'm not totally sure what the issue can be. It could be a number of thing but in the case of my old tf300 before i exchanged I had what looked like a finger print under the screen. Just sort of a smudge about the size of an eraser head. On black screens where screen was on like as when it starts up or loading an app it would show but since it was light colored It wouldn't show on most others. Not sure if that's the case for you but when I sent it back to Newegg they determined it was a problem with the lcd screen, maybe dead pixels they said.
In your case if you have option to just go to store I'd just do that and save your self the trouble. If other wise bought it online then maybe worth trying to figure out because also in my case Newegg took about a week of testing it before approving the exchange also I should mention there couple other problems with it. Not sure what else you can try if you had already downgraded which in most cases erases everything not sure whynit didn't for you I'm not sure what else to do. One other thing is to try ,aybe holding down the reset butoon on left side of tablet in the hole under the volume buttons. I posted a link earlier on lcd and pcb problem thread maybe you can try to ask some one there, they probably would know more most of them are fermiliar with hardware issues so might be able to tell you if it is or not but as i said might just he easier returning it and start fresh. Good luck and sorry I can't help more.
Just in case theres the harware issues thread again.
http://forum.xda-developers.com/showthread.php?t=2091233

aerdely said:
Tell you the truth I'm not totally sure what the issue can be. It could be a number of thing but in the case of my old tf300 before i exchanged I had what looked like a finger print under the screen. Just sort of a smudge about the size of an eraser head. On black screens where screen was on like as when it starts up or loading an app it would show but since it was light colored It wouldn't show on most others. Not sure if that's the case for you but when I sent it back to Newegg they determined it was a problem with the lcd screen, maybe dead pixels they said.
In your case if you have option to just go to store I'd just do that and save your self the trouble. If other wise bought it online then maybe worth trying to figure out because also in my case Newegg took about a week of testing it before approving the exchange also I should mention there couple other problems with it. Not sure what else you can try if you had already downgraded which in most cases erases everything not sure whynit didn't for you I'm not sure what else to do. One other thing is to try ,aybe holding down the reset butoon on left side of tablet in the hole under the volume buttons. I posted a link earlier on lcd and pcb problem thread maybe you can try to ask some one there, they probably would know more most of them are fermiliar with hardware issues so might be able to tell you if it is or not but as i said might just he easier returning it and start fresh. Good luck and sorry I can't help more.
Just in case theres the harware issues thread again.
http://forum.xda-developers.com/showthread.php?t=2091233
Click to expand...
Click to collapse
Thanks again
I tried the reset hole but the paper clip just goes straight in?

I've just downgraded to 4.1 and the lines disappeared. I then downloaded an OTA for Android 4.2 for the lines to then reappear.
I am about to downgrade again the then download the 4.2 firmware file instead of downloading the update OTA (in case the update file is corrupted).

mr.fast said:
My Asus TF300T has been starting to act up lately. When I access the settings menu faint grey lines start to appear which run across the screen. When I change to portrait the lines disappear for a split-second and then reappear black. When accessing Google Play I see the same thing. The power menu and other menus appear to have a pixelated background and are 'blocky'. It also happens in the ASUS File Manager on the white background (faint lines).
I am confused as to what's causing them. It appears to me to be a graphics-related issue as I have taken screenshots and viewed them on my computer and they appear pixelated on the TF300T but not on my computer. I have cold booted and performed a full factory reset. I have also switched to Safe Mode with no change (lines still appearing). I am using the Jelly Bean 4.2 launcher and am stock. The tablet hasn't been dropped and has been protected. It's only 4 months old and I bought it from Argos in the UK.
It's a shame because I like this tablet
Thanks.
Click to expand...
Click to collapse
You might try hitting it with some circuit cooler (with the cover removed of course) to see if its heat related - an upside down can of liquid air would do it. Problem is, if it is heat related, you need to provide better heat sinking, which likely means ripping your warranty sticker to get access to the IC's underneath the copper heat sink in attempt to provide better heat dissipation with thermal compound or something.
Reseating the video connector to see if its a bad connection is another viable option without creating evidence of tampering and potentially voiding warranty.
Hope this helps.

[q] no screen touches being recognized!!!

Hey XDA, Really need some help here, i'll bullet point my problem for ease of reading:
- 1st Nexus 4 bought from google had wi-fi issues so got replacement
- 2nd replacement nexus 4 was good for about 2 weeks
- randomly screen touches weren't recognized by phone so reboot fixed that
- got worse and more frequent
- now my phone does not recognize screen touches at all
- phone is completely unusable, power volume buttons work though.
- need to ask XDA before another replacement ///
WHAT I'VE TRIED:
- i was on stock, so i tried to reflash stock to get rid of gravity stock and stock kernel
- rebooting phone 3950280359283 times.
- cleared caches.
- asked google play support, they're clueless.
- problem was here before i was unrooted, on complete stock 4.4.2
- also wondering whether its a software or hardware problem. i assume hardware however.
- i still have warranty
ANY IDEAS?!? thanks.

Does a touch recovery recognize touches? If so, it could be a problem of your rom/kernel. Otherwise I think it's a hardware problem.

Creepyficate said:
Does a touch recovery recognize touches? If so, it could be a problem of your rom/kernel. Otherwise I think it's a hardware problem.
Click to expand...
Click to collapse
My screen works now. However it will still come back every now and then and is fixed by a reboot. When i made this thread it did not work for a whole day, so my device will probably breakdown again. When I use TWRP it does not recognize touches. A good decider. So i guess it is hardware?

I think so, but wait for another reply confirming that.

I'd say it's a hardware issue. Definitely get it replaced again.

Kaleptik said:
I'd say it's a hardware issue. Definitely get it replaced again.
Click to expand...
Click to collapse
Lmao. You're definitely right. It's really annoying they sent me another device with a WORSE problem. Gonna ask google for some sort of compensation. I don't really have time to fiddle with devices re-rooting them transferring all my data again and so on. Too much work.