Develop Bugs

[Q] AuraxTSense_8.3 bricked after one week?!??

Hi all, the very best noob is posting here
I was enjoying the last AuraxTSense rom (AuraxTSense_8.3_Official_OTA_2.2_FRF91_A2SD +...) installed on 29/01. The display is SLCD. The mobile is branded, so I created-and-used a gold card. Everything was perfect until this morning when I noticed that the display was black and there was no way to come up with an image, or text ... (it's almost black, actually I can see that lights just barely).
Since the installation of the rom was successful, I do not think that the phone is bricked, but It's a supposition. Or not?
As described on forums, I've installed the rom RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed to try to recover the mobile: I can hear the sound, the cell vibrates, ... but no more as in the beginning.
Any ideas?
Thank you!

would you mind giving some additional info like does the LED turn on, if plugged in to a charger? Does it turn on, if plugged into a computer?
Can you boot into fastboot(vol down + power)?
Did you do anything special before this happened?
How did you flash the ruu(from zip file or via computer)? Did any errors occour?
Also why would you try to flash a ruu, when you had no idea what was wrong or what you were doing? You might just have ruined it more. There is no way to know, but as it was able to run the ruu, apparently nothing was wrong.

Thank you for the reply.
would you mind giving some additional info
Click to expand...
Click to collapse
The mobile charges with charger, and USB cable attached on the PC: while charging, the LED is orange.
When off, I can power it up using the power button: the mobile vibrates and after ~25 seconds I can hear the start sound. After ~10 seconds the home+menu+back+src button lights go on for some seconds.
The display, since the start-up vibration, becames barely lighted. While the mobile is powered on, if not used, after some time the display becomes dark and I can resume its lighting pressing the power button.
While the mobile is on, if I plug the USB cable in the PC a new drive appears; it's an empty (0 bytes size) drive - I have no SD in.
Can you boot into fastboot(vol down + power)?
Click to expand...
Click to collapse
I cannot say this because I cannot see anything, but when I boot with (vol down + power) the mobile does not vibrate.
BTW I can boot with (power+back), as I have used the RUU executable to flash and it worked.
Did you do anything special before this happened?
Click to expand...
Click to collapse
nothing special, nothing more than checking the email.
How did you flash the ruu(from zip file or via computer)? Did any errors occour?
Click to expand...
Click to collapse
I flashed using the RUU, with no errors.
Also why would you try to flash a ruu, when you had no idea what was wrong or what you were doing?
Click to expand...
Click to collapse
Just followed the instructions seen on another blog/forum.
I can say that the behaviour of the mobile after the RUU update is the same of before.
Thank you.

to me that sounds like a hardware (backlight) fault...
But how could you flash the wwe-Ruu? Your handset was branded, wasnt it? Did you use the goldcard to flash the ruu? Remember to flash the original (=branded) ruu before you send it in for repair (if you do so)

RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed
hmm isnt that for amoled phones.
try http://forum.xda-developers.com/showthread.php?t=869048
and if that isnt working flash rom that came with it and send it to repair.

Yes, I flashed using the goldcard; it was working very well!
The last app I installed was juice defender, the full version, updated two days ago from the market.
I'm trying with the link proposed by madman_cro, it's now in download.
Thank you.

2 things... would it not have been better to post in the AuraxTsense page lol? I've used 8.3 since release and its near perfect, sounds like a hardware error.... screen maybe gone? There was a spate of HTC screen problems
Sent from my HTC Desire using XDA App

I have had this happen twice on Auraxtsense. Both times removing the battery for 30 secs and then replacing and rebooting solved the issue. It eventually came back to life.
In your case it could be a hardware failure ......

Im trying to flash the rom proposed by madman_cro, but today is a bad day: update fails with ERROR 170
Yes AuraxTsense is a great rom, with no doubt! I'm not considering the rom as the origin of the problem, but it would be nice to discover what's wrong in my mobile
In the case it's an hardware problem, I've asked HTC for assitance...
(PS: I have had no way to post in the AuraxTsense page as this is my first post)

oh one more thing(nearly forgoten) try to read this tread and see if it helps
http://forum.xda-developers.com/showthread.php?t=748498
maybe not the same but simptoms are simmilar

ali_smooth said:
2 things... would it not have been better to post in the AuraxTsense page lol? I've used 8.3 since release and its near perfect, sounds like a hardware error.... screen maybe gone? There was a spate of HTC screen problems
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
As you say yourself this sounds like a hw error, and such it has nothing to do with auraxtsense, so why the hell should he post it in there.
But it does indeed sound like a hw error. So you will probably have to ask htc, if the prober ruu doesn't solve it. Also slcd brick only happens after flashing a wrong rom/bootloader, so it should not possibly appear out of nowhere.

madman_cro said:
RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed
hmm isnt that for amoled phones.
try http://forum.xda-developers.com/showthread.php?t=869048
and if that isnt working flash rom that came with it and send it to repair.
Click to expand...
Click to collapse
Flashed! but with no result, same as before...
I want to restore the mobile with the original Orange FR firmware: is there the possibility to do it having the fr OTA_Bravrange_CH-FR_2.22.71.2-1.19.72.3_P_release8xcr7nx2a68060l7.zip file - but w/o the display? (I haven't found the RUU executable)
Thank you all.

mortenmhp said:
As you say yourself this sounds like a hw error, and such it has nothing to do with auraxtsense, so why the hell should he post it in there.
Click to expand...
Click to collapse
Why the hell would he do that? Because at that stage a hardware fault was suggested but not confirmed ... so why the hell not?
If it was a problem with the rom like he thought it could be, that would of been a good starting point!

I had the same thing happen with a Blackstone (Touch HD)
Don't know if this is any help, but I had exactly the same thing happen with my old Touch HD. There was a util I found that allowed me to view the phone screen and drive it via my pc through the USB port. This helped in making sure that the only issue was a lack of display, and flashing and returning to stock before sending off for repair. Not too sure if there's something similar for the Desire.
The problem was initially diagnosed as a loose connection within the phone, and the repair center fixed it and sent it back to me. A couple of weeks later exactly the same thing happened. After replacing the mainboard on the second repair visit it was all fixed and worked well (until I fed it too much voltage from a charger, but that's another story). I'd suggest that claiming this experience as your own and requesting a mainboard replacement up front may be the best way to avoid too many service visits.
You'll know that they have replaced the mainboard as they'll issue you with a new IMEI.

selling it on ebay
Thank you all! My experience with support services in Italy and the fact that the phone has been rooted/flashed, have persuaded me to put it on ebay, as is. I still haven't found the solution, so I don't know if it's an hardware problem or something else. In the doubt, I'm selling it as not working.
Hope I will come back with a new desire...
Thanks to all the forum for contents and kindness

galgoog said:
Thank you all! My experience with support services in Italy and the fact that the phone has been rooted/flashed, have persuaded me to put it on ebay, as is. I still haven't found the solution, so I don't know if it's an hardware problem or something else. In the doubt, I'm selling it as not working.
Hope I will come back with a new desire...
Thanks to all the forum for contents and kindness
Click to expand...
Click to collapse
Is it not under warranty??? Its still covered if the changes you made didn't cause the issue ( I think lol)
Sent from my HTC Desire using XDA App

Although most people have said this is a hardware error (I'm inclined to think the same) have you actually tried to hard reset the phone just incase a setting is messed up somewhere and is actually displaying at 0% backlight. Very likely it won't work but is at least worth a shot before you get rid of it on Ebay

trying again
Hi warlordxxx, having the possibility to use another phone (do you remember the 7650? ) I removed the desire from ebay and I'm now trying to best discover what's happened, as I think it's not an hardward problem too.
I'm following the directions posted on the androidiani.it forum: maybe my problem it's just a video driver problem. I will let you know the result of the operations.
Have a nice week.

Random now permanent black screen issue

Bought this phone off the electronic bay, arrived totally fine, no signs of any damage, worked just fine. Upgraded it with the sony OTA updates to 4.1 and then the screen started acting a little funny. Sometimes when hitting the unlock button it would just light up the backlight. Then a few days later it stopped ever doing anything besides lighting up the backlight. Then it progressed to doing what I show in the video.
It still plays alert tones when i get messages or calls, but obviously the phone is totally unusable, but charges up fine.
any ideas what is going on here? Called Sony for a repair, but I was unaware they just charge a flat $185 irregardless of what the problem is...ridiculous.

foofiebeast said:
Bought this phone off the electronic bay, arrived totally fine, no signs of any damage, worked just fine. Upgraded it with the sony OTA updates to 4.1 and then the screen started acting a little funny. Sometimes when hitting the unlock button it would just light up the backlight. Then a few days later it stopped ever doing anything besides lighting up the backlight. Then it progressed to doing what I show in the video.
It still plays alert tones when i get messages or calls, but obviously the phone is totally unusable, but charges up fine.
any ideas what is going on here? Called Sony for a repair, but I was unaware they just charge a flat $185 irregardless of what the problem is...ridiculous.
Click to expand...
Click to collapse
Hi,
The best way to rule out any software problems would be to flash the latest 6.2.B.1.96 ftf using Flashtool. So, first make sure that the phone has enough charge, then press and hold the volume up+power combination until you get three vibrations. Then press and hold the volume down key and simultaneously connect the USB cable when Flashtool prompts you to. Once the flashing is complete, disconnect your phone and turn it on normally.
Regards,
abcdjdj
Sent from my LT26i using xda app-developers app

I already flashed back to stock just using the sony bridge app. It seemed to work fine (nothing showed up on the screen the entire time). After the phone boots up I can hear notification sounds as it gets all my texts and voicemails/whatever else. But otherwise it still does what is shown in the video below:
here is the video again, not sure if it worked last time:
http://www.youtube.com/watch?v=jbrpsWburMw

foofiebeast said:
I already flashed back to stock just using the sony bridge app. It seemed to work fine (nothing showed up on the screen the entire time). After the phone boots up I can hear notification sounds as it gets all my texts and voicemails/whatever else. But otherwise it still does what is shown in the video below:
here is the video again, not sure if it worked last time:
http://www.youtube.com/watch?v=jbrpsWburMw
Click to expand...
Click to collapse
What bug u reported is the bug of .200 and .211 official bug.. Its fixed in .96fw.. Wipe everything when u flash .96fw... So there won't be any problems..

sudhindrakv said:
What bug u reported is the bug of .200 and .211 official bug.. Its fixed in .96fw.. Wipe everything when u flash .96fw... So there won't be any problems..
Click to expand...
Click to collapse
Well there is a slight problem.
The phone does not have an unlocked bootloader yet, so I can't use flashtool. It has been flashed back to stock using the method I mentioned above. I have just finished installing ADB because (bear with me please) there is no way to turn the phone into fastboot mode without turning it off (I cannot currently turn it off because I can't see what is happening on the screen and don't remember how this phone works when you hold down the lock key to turn it off). I can perform a hard reset, but no way to just get it to turn off entirely.
So I thought I could use adb to shut it down, but adb won't work unless I have debugging enabled, which again I can't do unless I could basically just blindly navigate the menu to those buttons.
Although if I wait until the phone is fully dead then I can hopefully get it into fastboot mode, but that only gives me one chance. Plus it has a full charge right now, so that's going to be awhile.
Any suggestions?

I can get it in to fast boot if I'm quick, but I still can't enable debugging beforehand so its semi worthless.
I've been trying to watch videos to see where the button placement is to navigate through the menu to blindly enable debugging, but I can't seem to figure it out. It also doesn't help that I have no idea what version of android is now on the phone. I used the mac sony bridge app to restore the phone, but i'm not sure if that set it back to stock stock, or what version of android it set it to.
I am also now even more confused because I connected the phone to the computer and when I browsed it, all the pictures I took were still there...which should have been wiped when I restored it with sony bridge...

figured out it was 4.1 and watched review videos until i found one that showed the menu layout (although now I realize google images would have been more helpful).
Now going to see if I can get the bootloader unlocked.
I still feel like flashing 6.2.B.1.96 isn't going to do anything, because I assume that is what the sony bridge app flashed to it. Also I don't see where you are talking about that the issue I am having was a known issue, if you could point me in that direction that would be very helpful.
EDIT: Actually I'm not sure I enabled debugging after all, as when I do adb devices, no device is listed as running, just a blank space. Though I'm still not convinced doing the above would do anything, as it is basically what I have already done, just with flash tool as opposed to the official sony route.

Anyone have any ideas? I got a torx 6 and opened the phone, checked the connection between the motherboard and phone and it is fine. Screen is still having same issue.
I would be happy to just buy a replacement part for it, but i have no idea what part is messing up. Is it the display (the touch works fine) or is it the motherboard (it seems weird that it would be this because the phone functions completely normally, I even accidentally answered a call yesterday).
If i was to try and replace the LCD (or whatever it is) would I have to replace the digitizer as well? At which point it would make more sense to just sell the phone for parts I suppose.

You can use the flash tool by bin4ry with a locked bootloader. Not sure if you're past that stage though.
Sent from my LT26i using xda app-developers app

dkconor said:
You can use the flash tool by bin4ry with a locked bootloader. Not sure if you're past that stage though.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
I'll go ahead and try that out, but is there really much of a point do you think? Considering I've technically flashed the phone back to stock using the official software, why would it be any different doing it this way?
I am asking honestly btw, not trying to sound rude. I'm thinking it is more of a hardware failure, i just have no idea what part exactly is failing.
The phone itself works totally 100% fine, the touch works totally 100% fine, the only thing that is not happening is the data getting to the screen and displaying. The screen just flashes white for a second and then fades out (as you can see in the youtube link). Or it flashes a solid block of white at the top in the middle and faded white the rest of the way down and then it slowly all fades out (or disappears immedaitely if i press the lock button. The buttons all work fine (physical and touch) and i can navigate around the phone, albeit totally blindly.
This is really frustrating, and I'm pretty disappointed to see how sony had no interest at all in helping me resolve this situation.

Flashtool works with lock and unlocked bootloader
XDAプレミアムを使用 して私のLT28hから送ら れてきた

UchihaDareNial said:
Flashtool works with lock and unlocked bootloader
XDAプレミアムを使用 して私のLT28hから送ら れてきた
Click to expand...
Click to collapse
....right i know, but why does that matter. Why would reflashing my phone help at all at this point. Did you even read my post?

Listen to us
Alright so you came to this thread for...help
We have told you numerous times to flash using this tool (dev host link):
http://d-h.st/Kb8
install the flashtool created by Binary (sorry for username spelling error)
Download the ftf
https://docs.google.com/file/d/0B18FXPCopQhkeXNoWGVWbzlRaG8/edit?pli=1
now USING FLASHTOOL (link 1)
FLASH the FTF (link 2)
A clean flash. This flash is different from the flash that Sony will provide you for obvious reasons.
Using this method will COMPLETELY remove any doubt whether the issue is regarding software or hardware. Then you dont have to "think" whether the issue is hardware related or software related.
Sorry if i sounded rude but i had a hard time comprehending why you would not use the advice given by i believe 2 different indiviuals on a questions and answers thread.

424aca said:
Alright so you came to this thread for...help
We have told you numerous times to flash using this tool (dev host link):
http://d-h.st/Kb8
install the flashtool created by Binary (sorry for username spelling error)
Download the ftf
https://docs.google.com/file/d/0B18FXPCopQhkeXNoWGVWbzlRaG8/edit?pli=1
now USING FLASHTOOL (link 1)
FLASH the FTF (link 2)
A clean flash. This flash is different from the flash that Sony will provide you for obvious reasons.
Using this method will COMPLETELY remove any doubt whether the issue is regarding software or hardware. Then you dont have to "think" whether the issue is hardware related or software related.
Sorry if i sounded rude but i had a hard time comprehending why you would not use the advice given by i believe 2 different indiviuals on a questions and answers thread.
Click to expand...
Click to collapse
Hi,
because I could not follow the advice from the first user because the bootloader is locked. The second person gave me the advice, but honestly it seemed like pretty pointless advice. I don't understand how it is "obviously different" if it is literally flashing the same firmware (at least the first advice was that). I don't think it's that strange to ask why it would be any different.
To me it sounds like I had a broken window in my house and I asked someone how to fix it. I bought the replacement glass from store A and it didn't fit. I asked for help and someone pointed me to the exact same item at store B and said that surely it would work. Do you understand why this could be confusing? I feel like about half the time people give help on XDA it is very general and people are just looking for "thanks"...
I'll definitely try this though if you think there's a chance that it might work out differently. I'll try and get it set up tonight, thanks for the encouragement, I understand I probably sound stupid, just trying to figure out what to do.

Also, I assume this flash tool won't work if USB debugging isn't enabled. As I've said in previous posts, I can click things just fine, but because I can't see what I am doing, I don't have way of knowing where to click on the menu.
Does anyone have their phone set up with this version of android still. If you could take screen shots of each click to make to get to the dubugging box (and if there is a confirmation box) i would greatly appreciate it. I only had the phone for a week before this randomly happened, so I hadn't thought to enable debugging yet, as I hadn't even thought about custom firmware yet.
EDIT: Or even just a picture of what the screen that comes up when you long press to shut the phone down. I have no way of turning off this phone right now without just waiting for it to run out of battery.
Holding down the power button for a long time does nothing, holding vol up and power restarts it, but I need a way to turn it off. If i hold the power button for like a second so instead of locking it, the menu comes up, I just can't seem to find the freakin button for power off.
(please remember I can see nothing on the screen, it is just blank).

flashtool does not need debugging when you doing the actual flashing
to turn off the phone
SIMULTANEOUSLY hold down
Power+ Vol up + Vol Down (AT THE SAME TIME)
wait for about maybe less than 25 seconds and you will experience THREE short consecutive vibrations
at this time...the phone is off
then you can begin the flashtool method

[Q] SGT3-7" Boots up w/no logo and no pic (updated to kitkat 1 day previously)

Title pretty much says the basics.
Details however are as follows.
SM-T210R, Have had this unit for about a year, always been in a case, never dropped, not a scratch/dent/ding on it and I use it every day.
Past couple weeks I was getting update notification from Samsung, I'd always put it off till I got home then not bother when I actually got there.
Finally, a long weekend for me.. I let the update run its course, No problems (500+MB's) And I believe it was upgrade to Kitkat from Jellybean.
Can't remember the exact version details.
Soooo, I use my tablet throughout the day everything seems to work great NO problems at all.
Notice my battery is down to like 20-25% and plug it in (Original wall charger and cable)
Go to get it the next morning, open the case expecting it to flash and display my lock/swipe screen, Nothing.. Not TOTALLY Black, you can see theres still a glow.
The screen still responds to touches ( I can swipe to unlock it and hear the sound)
I tried to reset power. Nope nothing except I can hear the startup tune.
Tried hard reset, nope same thing.
Tried every button combo I could think of or contort my hands/feet into.. Nope no joy.
Hit the internet... read, read, read, read, watch videos, watch more videos..
Ah-ha take the back off, disco battery, wait, replug and voila.
Nope.. not the issue
Different milliamp chargers, nope.
WTF??
Normally I'd think I did something to it, but I did nothing that I hadn't done at least 200 times already.
I'm convinced Samsung F'd my tablet w/their update, not only that but my $1200.00 drone sits idle over my holiday because my vision app resides on my sgt3.
Ideas?

My best solution so far...
Well its been like 2 days since my sgt3 lost its mind.
Found a solution.
EVGA - Tegra Note 7. (No hyperlinks allowed for me....Yet)
nvidia.ca/object/evga-tegra-note-tablet
DAYUMMMMM.
This thing blows my SGT3 right off the map.
Still would like to find a REAL solution, there's alot of configurations on my SGT3.
But in the meantime I think this'll keep me almost content.
-D-

Just download odin and the firmware for you country and flash it if it gets stuck at the boot get in recvory and wipe and flash once more works a treat
sounds like a bad flash i never let over the air upgrades there trouble always use a pc
Ps take any memory cards out before flashing once booted and working replace memory card

jasonvoor1313 said:
Just download odin and the firmware for you country and flash it if it gets stuck at the boot get in recvory and wipe and flash once more works a treat
sounds like a bad flash i never let over the air upgrades there trouble always use a pc
Ps take any memory cards out before flashing once booted and working replace memory card
Click to expand...
Click to collapse
Thanks Jason, I've not messed w/flashing the firmware through pc on this thing yet.
I've done it w/psp's, motherboards, routers etc, but never w/one of my tabs.
Just to confirm... I dont need a display on my tablet to flash it w/Odin?

dimzin said:
Thanks Jason, I've not messed w/flashing the firmware through pc on this thing yet.
I've done it w/psp's, motherboards, routers etc, but never w/one of my tabs.
Just to confirm... I dont need a display on my tablet to flash it w/Odin?
Click to expand...
Click to collapse
No, you don't need the display on your Tab, you just need Kies and Odin on your PC.
Place your Tab in Downloadmode(VolDown+Home+Power,release All buttons when you see the warning, press VolUp) then choose your PDA firmware in Odin(Obtain firmware from SamMobile) an hit start. After this boot into recovery and wipe/factory reset your tab if it's not booting!
Good Luck
Greets Daniel

xDaniel91536 said:
No, you don't need the display on your Tab, you just need Kies and Odin on your PC.
Place your Tab in Downloadmode(VolDown+Home+Power,release All buttons when you see the warning, press VolUp) then choose your PDA firmware in Odin(Obtain firmware from SamMobile) an hit start. After this boot into recovery and wipe/factory reset your tab if it's not booting!
Good Luck
Greets Daniel
Click to expand...
Click to collapse
Hey Daniel, Thanks for the info.
I found Odin was pretty easy to flash with.
I've tried 4 different FW images for the GT3-7 and taken the unit (almost) completely apart w/the exception of removing the actual digitizer and the lcd.
Same results after each install though.
It boots, plays the boot sound, but no display.
I guess next step is removing the screen.. After that I don't know what to do except possibly getting myself a lcd replacement..
Just might drop it off to one of the local shops and get them to do it that way I won't wind up paying for something and f'ing it up.
No joy w/my sgt3..

Hey Daniel, Thanks for the info.
I found Odin was pretty easy to flash with.
I've tried 4 different FW images for the GT3-7 and taken the unit (almost) completely apart w/the exception of removing the actual digitizer and the lcd.
Same results after each install though.
Even went so far as to try Kies to do the last one.
It boots, plays the boot sound, but no display.
I guess next step is removing the screen.. After that I don't know what to do except possibly getting myself a lcd replacement..
Just might drop it off to one of the local shops and get them to do it that way I won't wind up paying for something and f'ing it up.
No joy w/my sgt3..

[Q] Stuck in boot load after screen replacement

So, my screen cracked by itself but I didnt get it fixed on the warranty.
Anyway, I bought a new screen from ebay, seemed allright.
Got it yesterday. Took off the old cracked screen, maybe a bit hard cause now its super broken.
When I put the new one in the phone doesnt boot. Just shows the Sony logo then reboots in infinity.
I did PC Companion repair which didnt say anything special just that it got the work done. Still the same problem.
Did the Sony Emma program which should flash the phone the offical way, right? No problem according to the program but when I try to start the phone the same problem.
Tried flashtool and flashed the phone with official..hmm ftf file. Still the same problem.
If I connect the old, very broken, screen the screen lights up all the time on the back side of the screen (the screen doesnt show anything on front side since its really broken) but dont know really if it kind of works.
So, did I screw up the phone when I took the screen off and broke something or could a faulty screen (the new one) actually be what causes the boot loop? That seems weird to me but i gotta ask. If the phone was really dead Emma or flashtool would say so right?
Any thoughts?
Thanks

Some new information. With the old broken screen I can connect the phone to the computer and the phone pops up in explorer. Which it doesnt with the new screen. Bloody what,

bunke84 said:
Some new information. With the old broken screen I can connect the phone to the computer and the phone pops up in explorer. Which it doesnt with the new screen. Bloody what,
Click to expand...
Click to collapse
Is the "new" display unit original from Sony or a chinese replicat?
If not original, i think it is a hardware problem (chinese crap...)

moonryder said:
Is the "new" display unit original from Sony or a chinese replicat?
If not original, i think it is a hardware problem (chinese crap...)
Click to expand...
Click to collapse
Yes, its a chinese copy. So that is probably my problem.
But since it will take months to get a new one any other ideas would be very nice.
Its just weird to me how the screen causes reboots, but I guess thats it.

Hi, did you manage to get it working with an original screen?
I have the identical problem.

Same problem
I have the same problem has anyone resolved the issue
Thanks in advance

[Unsolved] Screen issues

Video of the issue: https://www.youtube.com/watch?v=XzIx9SHj6MQ&feature=youtu.be
According to my sister it has always had the screen "artifacts"as shown in the video where certain pixels are the wrong colours (which apparently never set off any alarm bells in her head... ). But apparently the screen and device stopped responding correctly a while back which i have been able to find out can be fixed by taking the back off the device. I can not use the recovery on the device since it just displays multicolored static on the screen, same thing happens when the device is plugged in to charge while powered off. I told her to get all important data off the device and factory reset it so the device is all at factory defaults to rule out software issues. After that didn't work i took the back off the device to check to see if the screen was connected correctly and to see if there were any obvious issues such as the cable being visibly damaged or disconnected etc.
Image of the issue when charging: http://i.imgur.com/Kat1RoC.jpg
So everything is stock on the device. It has never ran anything but official updates directly from Google.
The device is out of warranty and considering the cracks on the corners of the case i doubt Google/Asus would be happy to fix the device out of warranty without it getting expensive. It would be nice to fix it if it is possible or financially viable.
Any ideas and suggestions appreciated!

Have you tried a factory reset? If not, have you tried reflashing a stock rom, wiping everything?

dikidera said:
Have you tried a factory reset? If not, have you tried reflashing a stock rom, wiping everything?
Click to expand...
Click to collapse
It has been factory reset. I have not flashed a new ROM to it.
I have actually fixed that issue by putting some padding in to prevent the cable from flexing so much inside the case. So the device now functions as an e-reader and web browser. But it still cannot play video or cope with scrolling through images and so on due to the tearing. It gets worse the more that is updated on the screen. This may still be a cable issue.
I would flash a new kernel and ROM to the device but download mode doesn't work since no computer can recognize the device. In download mode and recovery the screen shows the static as shown in the image meaning i cant really use it easily. Since it is still running stock recovery i cant just flash a zip file, since download mode doesn't work it may be difficult to do the above.
But i only have experience with my own Galaxy S2 which runs custom everything. So my experience is with Odin and CWM, so i am not familiar with download mode for other manufacturers.

The second image, I know this. I was fiddling with the ribbon cables one day and I also got that distorted screen.
If it appears when charging, sounds like...the cable is not grounded or something and the signal(to/from the ribbon cable) is being distorted. But that is just a guess, it could be anything.

dikidera said:
The second image, I know this. I was fiddling with the ribbon cables one day and I also got that distorted screen.
If it appears when charging, sounds like...the cable is not grounded or something and the signal(to/from the ribbon cable) is being distorted. But that is just a guess, it could be anything.
Click to expand...
Click to collapse
Its not exclusive to charging though therefore i dont think it is power related. It happens every single time the system displays something on screen outside of Android. So the charging screen, recovery and download mode are all displayed as that.

Have you tried fiddling with said cable when you get the distorted image, in an attempt to perhaps fix it? it's odd that it appears with system messages. This sounds more and more like a true hardware issue(a defective unit) than software or a "simple" ribbon cable problem.

dikidera said:
Have you tried fiddling with said cable when you get the distorted image, in an attempt to perhaps fix it? it's odd that it appears with system messages. This sounds more and more like a true hardware issue(a defective unit) than software or a "simple" ribbon cable problem.
Click to expand...
Click to collapse
Not while it displays that image. But i have unplugged it and plugged it back in and nothing has helped.
My theory at the moment is that the cable is damaged meaning when the device tries to completely update the screen data goes missing and it struggles. Since videos dont work at all while the android flappy bird clone works flawlessly since it doesn't need to send as much data to update the screen due to the solid background colours and so on. But there are still holes in that theory, for example the issues become many many times worse when the device is in landscape mode.
So as far as i can tell it could be anything from heavily corrupted software to broken vram and anything in between including broken cable (since fiddling with that has fixed a different issue, perhaps its related) to the displays RAM for storing the previous screen update being broken. I can't tell.

Defective VRAM is also a possibility.
But I am not aware of any tool(for Android) that would allow for direct memory scanning of the VRAM. If you end up deciding the tablet is a goner, and want to buy a new one. I'd advise against another N7, it's already old, and the bugs are not worth the hassle.

dikidera said:
Defective VRAM is also a possibility.
But I am not aware of any tool(for Android) that would allow for direct memory scanning of the VRAM. If you end up deciding the tablet is a goner, and want to buy a new one. I'd advise against another N7, it's already old, and the bugs are not worth the hassle.
Click to expand...
Click to collapse
Yeah, im not aware of any either. I have also been through all the relevant debugging tools. Telling the screen to flash on update actually made the device function much better (where it flashes pink on each update) it stopped the issues from being serious. But lets face it, no one is going to want to use a device with that debugging option left enabled.