yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] sfhub:
Did you do

fastboot boot twrp.img

or

fastboot flash recovery twrp.img

If the former, you don't have twrp installed, you just ran it temporarily to install the fix for your corrupted eMMC issue. If you reboot to recovery you'll still have stock.

If the latter, then you did install twrp persistently.

Great to hear. Yes, TS10 is still loaded. I will stay loaded until you decide you you want something else and do TS-UNLOCK.

If you followed the commands I gave you, you don't have TWRP installed, you just ran it temporarily to install the corrupted eMMC issue. You'll still have stock recovery installed.

w/r/t future updates, you probably will not have any more issues. It really depends on whether the corrupt eMMC fixes Google put in JSS15Q are effective in avoiding the issue.

I'll just say that given the tablet you have, running the setup you currently have affords you the best chance to no longer see any issues.

If you get stuff like UIDs inconsistent, are you felling lucky, or suddenly get stuck with X after a reboot, then you should start getting concerned about the eMMC, but that is probably unlikely to happen, so

ENJOY YOUR TABLET TIME FOR WORRYING IS OVER
[Nexus 7 (2013) General] sfhub:
After you do

fastboot oem unlock

I would suggest you leave it unlocked and never do

fastboot oem lock

unless you restore to factory images and are returning the unit.

Leaving it unlocked just gives you more recovery options and more fexibility.
[Nexus 7 (2013) General] lespaulman67:
I did

fastboot flash boot twrp.img

But why the android on its back with red triangle !
[Nexus 7 (2013) General] sfhub:
Probably some command you thought you were running didn't run (successfully) or you thought you ran some command but you didn't, or you mixed up the image files.

Can you do

adb reboot recovery

and see if you get the fallen android again

I assure you if you are seeing that, you are running stock recovery.

BTW I am curious why you decided to

fastboot flash recovery twrp.img

instead of

fastboot boot twrp.img

It doesn't matter in the grand scheme of things, but I don't think the instructions I wrote mentioned fastboot flash, so I'm wondering if you followed different directions for installing twrp. Then we could look at what you did with those directions to figure out what would leave you with stock recovery when you thought you had installed twrp.
[Nexus 7 (2013) General] lespaulman67:
I have never messed with TWRP and I went to Process to install TWRP recovery on your Nexus 7 FLO http://xdaforums.com/showthread.php?t=2382051

for instructions and help. I tried it that way I seen but it disappeared on me I had to run it again to get the fix.zip to run.lol

I can't believe how good this tablet is running. I think people need to run your fix then update to JSS15Q just like I did the whole process. The screen looks higher res now than before with the JSS15Q without your fix. This is my 6th tablet and its perfect now.

Hope Google doesn't mess it up in the future.
[Nexus 7 (2013) General] SubMatrix:
I lol'ed :D
[Nexus 7 (2013) General] lespaulman67:
I'M serious about the screen it looks better. Maybe I just had bad ones all this time. Because I don't have a dead spot on this one.
[Nexus 7 (2013) General] sfhub:
Actually some displays have higher contrast than others and some have whiter whites than others.

Combine the two and compare it to a more pinkish lower contrast screen and it does look better/sharper even though the resolution is the same.
[Nexus 7 (2013) General] boykomac:
Ok I have the "third touch / ghost touch when unplugged and lying down" - or should I call it "the grounding issue"? Not sure anymore. So I tried 10, 20 and 30. The issue is still here, but 30 seems to kill the touch input delay / lag. My touchscreen is now perfectly responsive and fast on par with my iPhone.

I still get ghost third touch when multitouches cross the axis, but my touchscreen is so much more responsive now :) Its pretty cool.

Thanks a lot!

B
[Nexus 7 (2013) General] SubMatrix:
I'm referring to the fact that he said it looked sharper after applying your fix :)
[Nexus 7 (2013) General] kingston73:
So for now seems like my personal best result was the ts unlock. I'm using aosb with glitch kernel. With ts10 it was missed touches, ghost touches, and general badness. After tsunlock it has occasional ground issue but no missed or multi touch.
[Nexus 7 (2013) General] mdamaged:
tsunlock just makes it so you can overwrite the ts# one applied, from the OP, "Once you use the ts-unlock image, you will once again be using touchscreen updates from the manufacturer.", it should not have fixed anything, but yeah, if it worked for you, sure, why not.
[Nexus 7 (2013) General] kingston73:
I thought the ts unlock made it so the ROM in use is setting the drivers? So by doing the unlock after ts10 do I still have ts10 drivers?
[Nexus 7 (2013) General] 77kdv77:
no. each kernel contains touchscreen controller firmware. stock kernel, custom kernels, tsXX-lock, ts-unlock, all of them. at boot kernel checks whether the ts firmaware is up to date or not. if it's old it will be updated (if not locked). tsXX-lock kernels update ts firmware and lock it so that other kernels can't flash ts controller. ts-unlock also updates firmware and unlocks update possibility
[Nexus 7 (2013) General] mdamaged:
You're just back to where you were before you flashed any of the ts## ones.
[Nexus 7 (2013) General] konradsa:
Try ts11, solved my erratic and dead band problems I had with ts10. Ts11 has been flawless for me thus far for a week or so.
[Nexus 7 (2013) General] funcrusher:
ts11??
[Nexus 7 (2013) General] konradsa:
Yes, ts11, it's in the experimental set.
[Nexus 7 (2013) General] funcrusher:
Thank you - I overlooked those.
[Nexus 7 (2013) General] zerocdv:
Touch problems solved!

Hi I had some problems with my Nexus 7.

First it didn't recognize some of the touches but normally with a reboot everything was working ok.

But around two weeks ago I updated my 4.3 to 4.4.2 and I started having ghost touches, like the touch screen was way too sensitive.

I could even type my password for Chrome to sync my accounts. It was really annoying if I typed "a" the screen showed "aaa". The same was when I tried to delete I ended up erasing everything. Some of you probably have the same problem.

So I found this post and load up the ts20 because I read another post with similar problems as mine and now everything is working again!

No more extra characters in my words nor any other problem!

Android 4.4.2

Build version KOT49H

Flo 16G
[Nexus 7 (2013) General] ortori:
someone know if there is a solution for the grounding problem? when i hold the tablet in one hand its working fine but when its on a table its not working so well.. what can i do?

thanks.
[Nexus 7 (2013) General] konradsa:
[MENTION=5251520]ortori[/MENTION]: Try ts10 and ts11.
[Nexus 7 (2013) General] unknownyello:
I had the same issue as you. Flash ts10 and now my tablet is working perfectly. No grounding

or multi-touch issues.
[Nexus 7 (2013) General] ortori:
So its not hardware problem? Why Google don't release an update?
[Nexus 7 (2013) General] Henrock11:
This. Im curious to know this as well. It seems as if its software though seeing as some are having success with the fix.
[Nexus 7 (2013) General] ortori:
Anyway the fix doesn't work for me, on the table i can only use 2 fingers but when its in my hand its working perfectly.
[Nexus 7 (2013) General] :
Nexus 7 16 WiFi edition from july 2013 with grouning problems.

Tried ts11... works perfectly!

Thanks!
[Nexus 7 (2013) General] ortori:
when you say works perfectly do you mean that you put your device on a pillow and used multi touch test app and all your 10 fingers were registered?
[Nexus 7 (2013) General] :
Exactly :)

I tested in on a pillow and carpet, without usb, without hands on cover, only on touchscreen.

Without ts11 touches in top of screen (about ~40-50%) isn't correctly registered. With, everything is ok.
[Nexus 7 (2013) General] 77kdv77:
ortori, man, do you really use 10 fingers? :) where? please, name an app, that requires 10 fingers multitouch :) ok, let it be only 5 fingers multitouch. in fact, I don't even know where I could use 4 fingers… this 10 fingers multitouch is useless in practice…

ts11 https://www.youtube.com/watch?v=vf6nVmD1O_s

not perfect, but much better than stock ts firmware
[Nexus 7 (2013) General] ortori:
when my n7 is on a pillow i can only use 2 fingers maybe 3 and i tried all the images but nothing works.. :(
[Nexus 7 (2013) General] mister_uaila:
Don't know how to thank you...

I am on 4.4.2, build KOT49H; I had the touchscreen missing touches very often when not holding the Nexus 7 in my hand, especially (but not only) with the 'x' key. After trying the procedure with the ts10 tweak all issues are completely gone, and the touchscreen works flawlessly, doesn't matter where the tablet is.

You saved me from a long and tedious returning process, worse still since I need the tablet for my work.

By the way, can you tell me if I can still receive OTA updates with ts10 installed? Or do I need to revert back to original?

Anyway, please let my thanks come to you from the inner depths of my heart.
[Nexus 7 (2013) General] TheMaskedHamburger:
Unfortunately the multi touch issues worsened over the past week and the grounding issue started to reappear over the last couple of days. So I have now flashed:

TS-11 - So far no issues whatsoever in the 24 hours its been on. The multi touch issue introduced by ts-08 has been fixed. The grounding issue is also back to being fixed. No other issues exist. I'll keep an eye on it though, as I've noticed these fixes seem to have a 2 week break in period.

It may seem like all is well for the first couple of weeks, but by the end of two weeks a number of people reported their problems coming back. I have no idea what could cause this, I wonder if its possibly heat or slight changes to the batteries voltage over time. I noticed in the past when running my nexus for a prolonged period of time without a full shutoff the issues appeared to worsen. As well, a full shutdown would fix the multitouch and grounding issues temporarily.

Anyway for now TS-11 is the ticket, thanks again SF-hub for this great hack!
[Nexus 7 (2013) General] niscrulez:
I've been having this touch bug on my Nexus 7 2013. I didn't know this was so common. What Google says?
[Nexus 7 (2013) General] 77kdv77:
nothing
[Nexus 7 (2013) General] iamnotkurtcobain:
Had enough. Smashed the N7 against a wall. Display broken. Worst piece of #%#& I bought in years. Never again.

Gesendet von meinem GT-I9505 mit Tapatalk
[Nexus 7 (2013) General] 77kdv77:
send me these broken pieces of #*$% :D
[Nexus 7 (2013) General] manfio:
Bahhhh

Dont believe.... take a photo and post here...

The PPL speaks a lot, and do nothing LOL

Enviado do meu Nexus 7 através de Tapatalk
[Nexus 7 (2013) General] highpulse:
not working

nexus 7

android 4.4.2

compil KOT49H

after update , touchscreen stop working properly , i have done all steps mentioned and (im using OSX) i have unlocked my device , i enter in fast boot (i added to the folder boot-td the ADB and FASTBOOT files for mac) so i can run the command in terminal , but when i reboot the system with the command adb reboot bootloader the tablet goes to fast boot and when i insert the command fastboot boot boot-ts10-locl.img its displays this error in terminal

jonathans-mbp:~ su$ /Users/su/Downloads/boot-ts/fastboot boot boot-ts10-lock.img ; exit;

i see this line for line 8 seconds , then this line appear bellow

ERROR: could not get pipe properties

cannot load 'boot-ts10-lock.img': No such file or directory

logout

[Processo concluído]

anyone can help me out with this

thk in advance
[Nexus 7 (2013) General] 77kdv77:
are you sure that file boot-ts10-lock.img is present in fastboot directory? "no such file/directory" means that this file is absent…
[Nexus 7 (2013) General] highpulse:
Yes the .img files are on the boot-TS folder , i added to that folder the ADB and fast boot files (macintosh version) to that folder and removed the .exe files to be used in windows , i do the command as they say and not working , always showing the message i showed in the previous post!

any thing im making wrong , sorry but i only do have macintosh system in the studio , don't have any pc or windows installed on the mac system.

Waiting for any help of you guys .

sincerely

jonas
[Nexus 7 (2013) General] Anders1:
You are not referring to the boot-ts folder in your command line...

You wrote:

"jonathans-mbp:~ su$ /Users/su/Downloads/boot-ts/fastboot boot boot-ts10-lock.img"

This requires the boot-ts10-lock.img to be in the "su" folder as that is where you were when you typed the command. I only use linux but I'm guessing it would be the same in OSX.

Try:

jonathans-mbp:~ su$ /Users/su/Downloads/boot-ts/fastboot boot Downloads/boot-ts/boot-ts10-lock.img
[Nexus 7 (2013) General] highpulse:
.

Well im gonna try that command now , but why it accept the dab reboot boot loader and not the fasboot boot ?? they are all in the same folder ,, so its kind weird.gonna try it now

---------- Post added at 12:59 PM ---------- Previous post was at 12:52 PM ----------

ok works command done successfully , have small letters on top "booting downloaded image"

lets see if it work out :)

thk mate , but why repeat the download part in the command line , can you explain me ?
[Nexus 7 (2013) General] Anders1:
It all depends on where your files are stored, you wrote the complete path to the fastboot binary (which was correct) but not to the boot-ts10-lock.img file. Since you only wrote 'boot-ts10-lock.img after 'fastboot boot', it assumes that the file is within the directory you are currently in, which in your case was /Users/su. However, your file was in the Downloads/boot-ts directory so you need to specify that within the command, otherwise fastboot won't find the file.
[Nexus 7 (2013) General] marsaltito:
Do you need "su" for adb in OSX ?
[Nexus 7 (2013) General] highpulse:
:)

Explained now why its was not working , i think that since i was inside of the root folder , just running the command fast boot should know that the file was in the same directory , but now , we must specify the address for the fast boot command know were the file is located :) another learning lesson :D thk

Btw ts10 still a few glitches gonna try the outer patches
[Nexus 7 (2013) General] highpulse:
not working

well when i apply the command , it show on the top part of the screen booting downloaded image , since it don't do anything after more than 5 min , i restart it pressing on off button for around 10 to 12 seconds , i do all the step , after restarting i let it go into the system , then i run the command adb reboot boot loader and start the system again , and when i test it , the same !! im using the 4.4.2 version , is there anyway to install here the factory rom ? if yes were can i get that ?

thk in advance
[Nexus 7 (2013) General] highpulse:
:)

i have some doubts' my area is more electronics than software , entering in fast boot it says my product is TILAPIA also as the VARIANT (checking on google this is 2012 gsm asus google nexus 7 , now i have been checking for many original factory rooms , my main question is , which will be the factory room i should download to install in here ? i see a lots of rom's but none with the tilapia name , only outer (or am i wrong ) ? any help guys ?
[Nexus 7 (2013) General] dakunclear:
Just did a fresh install of kit Kat after leaving it did months I will see how it is with ts and hope for the best but as of right now it is working great
[Nexus 7 (2013) General] 318sugarhill:
I use OSX as well. My adb and fastboot are in the platform-tools folder when I first installed the SDK. On the advice of others, My SDK is right inside Macintosh HD icon, and I labeled it android. All I have to do is is open the android folder up, and then when I open terminal just type in "cd" then a space, and then drag the platform-tools folder right into terminal. From there I run all the same adb commands posted, I just have to start everything with "./"

I've had the SDK on my mac since the first day I had my HTC rezound 2 years ago. Had to update the platform-tools in order to unlock the Nexus, but other than that, anything I want to flash goes right into that folder for quick flashing.

---------- Post added at 11:52 PM ---------- Previous post was at 11:44 PM ----------

Thanks sfhub.....I was just thinking I should have just gotten an ipad mini. I've been hating this thing....and wanting to love it, since day 1 (Christmas day). This touchscreen unresponsiveness was unbearable. I really can't believe it hasn't been fixed by Google, and as Android enthusiast I won't recommend this device to anyone. I've only flashed ts10 so far, but I can tell already it's an improvement. The only way to describe my issues it seems like I have gloves on when trying to use it. After flashing, the scroll action seemed so much smoother. I'll give it a few days of testing before I claim "cure", but so far so good. I really am disappointed that a device with so much potential must be unlocked to fix a factory flaw. Most users I know will not do this, and the device will look and feel like a piece of junk to them......especially compared with an ipad.
[Nexus 7 (2013) General] 77kdv77:
two weeks with ts11. it's nearly perfect on my device :) never was better…
[Nexus 7 (2013) General] dinjo_jo:
How do i flash the img file from recovery mode cannot see the file ?
[Nexus 7 (2013) General] kingston73:
You didn't read the OP at all, did you?
[Nexus 7 (2013) General] mdamaged:
You don't. Instead, you read the OP and follow the instructions, which will tell you to use fastboot boot <name>.img.

EDIT: Ninja'd
[Nexus 7 (2013) General] dinjo_jo:
Due to some reason my Nexus 7 is recognized in windows but does not shows in fastboot says "no device found" hence was asking whether there is a way to flash it ?
[Nexus 7 (2013) General] kingston73:
If your computer and nexus are working together but you can't make it get into fastboot you might be in the wrong folder when you are trying to enter commands? I have it on my desktop, I open the folder with the ts files in it after I unpacked it and then copy that folder's address into the command prompt.
[Nexus 7 (2013) General] dinjo_jo:
No there are some problem with fast boot drivers I tried almost everything but this ****ed up Windows 8.1 does not works well , so no other way ?
[Nexus 7 (2013) General] kingston73:
Sorry, I'm no help there, still on win 7 and plan to stay there. Hopefully somebody else can chime in.
[Nexus 7 (2013) General] atamk88:
Not fully solved

I have bought my nexus 7 (2013) about one month ago and it is updated to 4.4 . since then my nexus has the famous touch screen problem which appears when the tablet is on a surface and not connected to usb (some touches are not sensed). now I have tested all the ts files from 03 to 30. in ts10 and ts11 the first problem is fixed but there are ghost touches. in ts12 and ts14 both problems are fixed but there are some problems at top and left edges of tablet touchscreen (some touches are not sensed). all the other ts files are worse. Is there any solution?:confused:
[Nexus 7 (2013) General] jomb3:
My problems stopped after i took screen protector off. I also had those same problems when my n7 was on a table or some other hard surface but when it was in my hand everything worked fine.
[Nexus 7 (2013) General] gohabs93:
Where do I get TS11 and other versions? In the first page I only see Ts10-20-30.

Thank you
[Nexus 7 (2013) General] 77kdv77:
you can take it from boot-ts-exp1.7z or boot-ts-exp2.7z on the 1st page in the 1st post
[Nexus 7 (2013) General] mdamaged:
Put it in debug mode with PTP enabled and use Koushes drivers.
[Nexus 7 (2013) General] devilgiap:
Tried all ts that everyone reported as fixed (ts8,10,11,20), all touch issues fix except Ghost touch, like when use 2 touchs as the same time, there is the ghost touch appeared randomly. But how lucky i'm, ts12 fixed this, no ghost touch, i can play my FPS games all time. Thanks you for this. Everyone can try ts12, hope this help like me did.
[Nexus 7 (2013) General] dimcreed22:
I Sended my unit because of the grounded touch screen issue and they sended me the asus service the tablet back today with the same problem,they did nothing! ,just a factory reset
[Nexus 7 (2013) General] fuser-invent:
Same thing happened to me. ts11 solved every and has been good for months.
[Nexus 7 (2013) General] konradsa:
Same here, I recommend ts11 as the first one people should try. Has solved all my issues, this is how the Nexus 7 should have been out of the box.
[Nexus 7 (2013) General] mdamaged:
I've known about this thread for a long time, but never tried the fixes because the only issue I had was the grounding one, well I finally had it and tried ts10...so far so good, thanks [MENTION=1299673]sfhub[/MENTION], I should have done this a long time ago.

EDIT: Oh, almost forgot, N7 2013 4.4.2

And YAMTT showed some ghost touches when on a soft surface trying to do 10 touches then released and the screen was going nuts, but going to reboot again and give it a chance.
[Nexus 7 (2013) General] aegixnova:
I tried every .img file but nothing worked. Gave it to an official repair centre, and they took 20 days to do a factory reset which achieved nothing. I gave it back, and they claimed to replace the LCD - taking another 20 days - yet the problem is still not fixed. This is getting out of hand.
[Nexus 7 (2013) General] konradsa:
Try ts11.
[Nexus 7 (2013) General] edlee:
Can I use flashify to install IMG file?
[Nexus 7 (2013) General] mdamaged:
I did, same deal as ts10, on ts20 right now, seems to work fine, the 10 finger thing is still a tiny bit wonky BUT, I decided to try something, I have an ipad 2, 2nd gen, (*ducks*, hey it was a gift!) Anyway, I downloaded a multi touch app for it, and guess what, it was even WORSE with 10 fingers, so I'm not going to nitpick, it's obvious touchscreens or their software can be erratic once you start throwing too many touches at it.

No, it must be done exactly as per the OPs directions.
[Nexus 7 (2013) General] Red_81:
Quick test for someone to try. I'm attempting to try this too but my device is behaving at the moment. The next time you get erratic movements or ghost touches, plug into a charger and then unplug.

I know for a fact mine works perfectly when grounded through the charger. I'm wanting to see if a quick connection to ground clears it up when it starts happening. I just can't play enough games to make it happen right now (at work).
[Nexus 7 (2013) General] dimcreed22:
everything seems great with the ts11 ,but isn't it Asus fault that it doesnt work without it? so they have to replace the tablet it self? (under warranty)
[Nexus 7 (2013) General] TheMaskedHamburger:
That post was from Feb.23, it is now March.14. TS-11 still working perfectly, no grounding/multi_touch/ghost_touch issues whatsoever. Now a perfectly working device. Cheers,

TheMaskedHamburger

---------- Post added at 06:59 PM ---------- Previous post was at 06:46 PM ----------

I tried this (well kinda), when I was testing the different touch screen variations. I thought ts09 was working (I used it on a flat computer table), but then I realized it was still plugged into the computers USB. So I unplugged it, set it down on another table and the touch screen immediately went unresponsive again/had multi touch (and maybe ghost touches). But we should let someone else check.

I wonder if battery_life/heat worsens the erratic touch screen. I noticed that when I picked up my device in the morning after charging it all night it would work perfectly for at least an hour. It would start to display issues afterwards but not to the point of being unusable. But then later in the day during the last 20% and when the device had heated up the touch screen issues became unbearable. A reset would sometimes alleviate the issues for a period of time.
[Nexus 7 (2013) General] Red_81:
My theory is the device builds a static charge over time. I notice mine is worse after long use and is especially bad when sitting on the microfiber couch. A quick connect and release to a charger should dissipate any static.