yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] mdamaged:
You're not supposed to flash it, just boot it.
[Nexus 7 (2013) General] Tony_YYZ:
I'll try to boot the ts10-ts30 fixes on Marshmallow this weekend and see if it works. If not, I'm going to revert to 4.4.x and try the ts10-ts30 fixes and see if one sticks. If it works, I'll just upgrade again to 5.1.1 and stay there.
[Nexus 7 (2013) General] sam298:
I meant booting. I followed OP's instructions. fastboot boot bootts10.img

If you do it in Marshmallow (weather you are rooted or not), you won't be able to boot.

Only solution is to have elementalx or other developers include the touch fix in their boot.img.

I will be downgrading to 5.1.1 as I didnt see much improvement in M - touch screen fix is a big improvement.

If anyone has sucessfully installed M and ts boot fixes, please share instructions.

See this post below to find out if stock or ts touch firmware is active

http://xdaforums.com/showpost.php?p=63173815&postcount=1707
[Nexus 7 (2013) General] mdamaged:
I have not tried it with MM, since I did this fix back before MM. That being said, it never booted with anything 5.0+, it will hang, but the firmware should still be installed, it is not writing to boot, it's writing to a different part of the device which has the firmware code, not the boot.img itself.

If it's corrupting the device so it cannot boot normally, then it might be due to dm-verity (new to android since this fix was rolled out, but it may or, if I'm wrong, may not apply to N7 2013), I might suggest you try with a kernel that has that disabled, if it still fails, then I'm wrong.

If you applied this fix pre-MM then you should not have had to reapplied the fix unless you ts-unlocked it before flashing MM.
[Nexus 7 (2013) General] illus4:
Just downgraded to 4.3 factory image (jss15q), flashed ts10 in boot-ts.7z, then upgraded to latest 6.0 (mra58k).

The ghost touches seemed to have gone. I will come back and report if there is any issues in touch screen after a few days' use or not.

Thanks for the fix.
[Nexus 7 (2013) General] JovieBrett:
Running Marshmallow on my N7 13 (wifi) with rooted stock kernel. Flashing any of those boot lock images gives no further improvement/no changes but I can boot successfully after flashing them.

Any updates?
[Nexus 7 (2013) General] sam298:
You are correct. I got stuck in bootloop after installing ts10. But when I re-installed the elementalx modified kernel, it booted. I checked the firmware version of touch driver and it looks like the ts10 is active.

No touch screen issues.
[Nexus 7 (2013) General] afremont:
That's interesting. It sounds like sfhub's locking mechanism still works, but that the newer kernels are creating some kind of hash or checksum at flash time that includes the touch-screen firmware. Then when you change the firmware, something like dm-verity doesn't like it and keeps the device from booting. That would mean that if the kernel (OS) updates the firmware itself, then it would have to re-calculate said checksum. That said, I searched all through the Lollipop code and couldn't find the firmware update code so I'm thinking that they changed how that process works.
[Nexus 7 (2013) General] yosmokinman:
^Read my post one page back. It was never supposed to boot the os and with LP it went to the recover I think. It still flashed all you had to do was reboot.

Check the location I mention in my last post and see if it changed. If you already have one flashed clean flashing M does not overwrite it.

Edit: So you have to flash another kernel after booting these now? Will a cache/data wipe or flashing stock kernel work?
[Nexus 7 (2013) General] SpecialBrewDaddy:
My N7 2013 screen is now unusable. How can I use this fix and use adb if I can't enable sub debugging within the tablet itself. I'm stuck in the choose your country screen. Any steps or alternatives you guys can suggest to use this fix? Thanks.
[Nexus 7 (2013) General] mdamaged:
If it's totally unusable this software fix probably won't help, these fixes are just re-calibrations, it sounds like your ribbon cable came undone, pop it open and make sure it's firmly seated. That being said, you should be able to attach a mouse to it via OTG.
[Nexus 7 (2013) General] SpecialBrewDaddy:
Thanks. I've tried this fix before. But I tried also to disable it and update the firmware via OTA update. Once updated, this was the scenario I'm in. If I try OTG cable and attach a mouse in it, will I be able to use it? Thanks!
[Nexus 7 (2013) General] mdamaged:
Worked for me in KitKat and works for me on Marshmallow.
[Nexus 7 (2013) General] SpecialBrewDaddy:
Will try this. Just want to open usb debugging. Once this mouse works then all will be fine LOL. Will update later what will happen.
[Nexus 7 (2013) General] SpecialBrewDaddy:
Mouse via usb OTG works! Thanks mdamaged!
[Nexus 7 (2013) General] SpecialBrewDaddy:
Yeeesss! My N7 is now usable again. There was a little bit of horizontal dead spots at the bottom. But still way more better that before. Booted ts10 for my N7. Also performed the shielding of the screen ribbon with aluminum foil. Thanks "mdamaged" for the advise.

Version : 5.1.1

Freaky sticky and unusable touchscreen

TS10 used
[Nexus 7 (2013) General] mdamaged:
Glad it worked out.
[Nexus 7 (2013) General] Tony_YYZ:
I reverted to Android 4.3 and tried ts1 through ts30. None of them seemed to fully fix the issues when doing the paint test in YAMTT but i locked in ts30 since I didn't see any real difference between the three and then flashed the Marshmallow factory image. I just finished installing all my apps and ran the YAMTT paint test. It doesn't experience the massive amounts of ghost touches anymore...yet.

I'll monitor it over the next few days and see how it goes. Such a shame, this is such a great tablet that was plagued with manufacturing issues that were never fully resolved. I can't even find anything comparable to replace it.
[Nexus 7 (2013) General] Kolij:
When i tried to write "fastboot boot boot-ts10-lock.img" in command line. My device says "no command" and stuck, i can reboot device, but i can't load ts10. I have android 6. Can you help me?
[Nexus 7 (2013) General] kokobooster:
help. I have N7 2013 32 gb MM 6.0 and i decided to fix multi-touch problem.

What i did was I downgraded using Wug's NRT from 6.0 to 4.3. and then i applied this "boot-ts10-lock.img" and it did reboot successfully. After that i revert back to 6.0 using NRT. I noticed my storage become 11.2gb it's supposed to be 26.1gb. How can i fix this? TIA
[Nexus 7 (2013) General] yosmokinman:
^Wipe data in recovery. I used twrp but stock should work too.
[Nexus 7 (2013) General] mdamaged:
Factory reset will fix the size thing.
[Nexus 7 (2013) General] ArcOnFire:
Well, I guess I have to tell my story.

Since I flashed on Lollipop (LMY48P) with ts10, the problem is lessened, but there were some rare occasions that the touch gets jumpy.

But since I updated to Marshmallow (MRA58V), my touch gets jumpy more frequently again.

So last night I decided to re-flash it again with ts20. However, after doing fastboot boot boot-ts20-lock.img , my device booted to a an error. There was android lying with chest popped a red warning side and text "Command Error".

I force it shutdown after one-and-a-half minute and powered it back on again.

The jumpy touch problem is completely gone, but I wonder if I did something wrong because that lying android after the 1st reboot.
[Nexus 7 (2013) General] _jis_:
No, it is perfectly ok. Read the OP again:

Note: if you are on Android >= 4.4 the stock 4.3 kernel will not get past the BouncingBalls

wait 120 seconds for the boot to settle down

press/hold the Power button 10-15 seconds until the tablet reboots

proceed to next step

This hack is very old and is using stock 4.3 kernel, but you are now on stock 6.0 kernel....
[Nexus 7 (2013) General] Hamsterzak1337:
Ts10 worked for me

I love you
[Nexus 7 (2013) General] ficicaaa:
does it work on 6.0.1 ?
[Nexus 7 (2013) General] _jis_:
This fix is Android version independent, but read my previous post above too and read the OP carefully.
[Nexus 7 (2013) General] gogol:
How do you check the "firmware version of the touch driver"?

I put ts10 before. Then upgraded to 6.0. It was all fine.

Then upgraded to 6.0.1 and to my surprise, I got multitouch problem! When I play a game which I must touch and move my finger all the time in the screen, it wasn't smooth like before.
[Nexus 7 (2013) General] _jis_:
http://xdaforums.com/showpost.php?p=49846548&postcount=1145

http://xdaforums.com/showpost.php?p=57363643&postcount=1619
[Nexus 7 (2013) General] yosmokinman:
^Yes so is xa044 still the current version on 6.0.1? I assume it is since I doubt they're ****ing with this anymore. I still have ts11 locked and don't care to check.
[Nexus 7 (2013) General] gogol:
Mine is ELAN_KTF3K_xa059

This is Android 6.0.1, not-rooted.

Is this still "ts"? I remember that I did ts10 really long time ago.
[Nexus 7 (2013) General] yosmokinman:
^The ts firmwares lock-in unless you booted the ts unlock you still have it.. Updates don't overwrite it.

I'm guessing xa059 is ts10 not stock which is likely still 044 on 6.0.1 (044 is ****ing **** IMO, on my tablet). I'm to lazy to ts-unlock and check. I did it from 5 onward.. nothing changed. ts11 is my ****.
[Nexus 7 (2013) General] Malth:
My USB port doesn't work, is there a way to do this without using adb over usb?
[Nexus 7 (2013) General] VicToR_AC:
It's still xa044. Just booted with ts10 and my Nexus 7 is working flawlessly.
[Nexus 7 (2013) General] VicToR_AC:
I'm here to say thank you!

Just booted my Nexus 7 with ts10.img and it's working excellent.

I had a continuous line where my touches weren't recognised, all along from the bottom to the top of the screen, something like 2 out 3 mm from the right bezel. It has always been a pain in the ass trying to erase some words or pointing the 3 dots on the right top of the screen.

On the other hand, grounding was always a frustration, touchscreen was almost unusable.

Now all those problems are gone! I'm actually writing this swiping with one finger with the tablet lying on the bed.

- It's a 16GB WiFi version.

- Touchscreen firmware was xa044 (now shows xa059).

- Android 6.0.1 MMB29O (1st January 2016 patch).

- TWRP recovery and systemless rooted.

- ASUS original mate screen protector.

- ASUS original travel cover (blue).

Just followed instructions and after the "boot boot-ts10" command it rebooted on TWRP's recovery. Just rebooted with "adb reboot" command and it booted up like always.

Rebooted 2 times more and started to work excellent, but after some tests with "Touch MultiTest" app from Google Play, it showed some blind rectangles remarked in the next screenshots:

After another reboot, there:

Then I remembered I made a change in the "elan-touchscreen.idc" file under system\usr\idc, changing "touch.pressure.scale" from 0.0048 to 0.007. So reverted back to 0.0048, rebooted twice and now working excellent as described above.

Sometimes it loses grounding, just turn off/on screen and it's back to normal.

I'll continue testing the touchscreen and post any news!
[Nexus 7 (2013) General] VicToR_AC:
Ts10 gave me some blind points in the first half of the screen starting from the bottom while not holding the tablet.

Tested ts11 and had some other blind spots on the right bezel near the top and touchscreen testers showed a thin line before the right bezel that wasn't detected.

Now on ts09 seems well calibrated. Gonna test this one.

EDITED: reverted back to ts10, the best for me. Went trough ts20/25/30 but all of them have blind spots.
[Nexus 7 (2013) General] JeviEnuh:
Thanks!

Wow thank you. Tried everything before, from removing screen protector to switching flex cables to putting more cushion on top the connections. Nothing worked.

ts10 worked for me, but i continued trying the rest to see if i could get my soft keys working again. None solved so I'm back to ts10 and having no problems at all.

There used to be ghost touches that would make tablet unusable. Turning the screen off then back on would sometimes make them stop for about a minute.

Android 5.1.1 (Since sixaxis tool isn't working with DS4 properly on 6.0.1)

Nexus 7 (2013) LTE

For others who may have lost complete touch in any part of their screen (soft keys for me), check if there are any cracks around the edge or if your digitizer may be lifting off. I have a small crack at the bottom edge of my screen (portrait mode) and that seems to have caused my softkeys not working in portrait mode
[Nexus 7 (2013) General] Voklav:
Tnx. Perfect!

ts10.img working :)
[Nexus 7 (2013) General] Zirvine:
Thank you so much. IT WORKED!!!!!

IT WORKED!!!!! First of all i would like to thank you so much for the help that you have given me. My tablet is only 3 days old but i immediately noticed something wrong with the screen. when i pinch to zoom in and out. I downloaded some screen testers and found out that certain commands/gestures do cause erratic behavior to the tablet.

Issues:

1. pinching from opposite sides (landscape) causes multiple third-finger ghost tap on the outer left part of the screen.

2. there is a dead screen at the bottom about 3mm wide just above and parallel to the navigation keys.

3. whenever i press more than 4 fingers (using multi-touch test), in a box shaped pattern, my screen creates several ghost taps. It just goes crazy.

TS10 worked amazingly for me. It took care of both issues 1 and 2. Number 3 issue could be tolerable since there are no apps that actually needs that kind of screen touching. Besides, it clearly says that the fix is meant to make the tablet more usable. Thank you so much again.
[Nexus 7 (2013) General] masri1987:
probably my mistake, but i'm in command prompt i got the nexus to reboot to bootloader via adb. then i type in fastboot boot boot-ts10-lock.img

it has been saying waiting for device for 10 minutes now.

What am i missing?

---------- Post added at 09:44 PM ---------- Previous post was at 09:30 PM ----------

got it., thanks all
[Nexus 7 (2013) General] Axel85:
Hi I bought a used nexus 7 one week ago ,coming with last stock 6.0.1.Can I use those firmwares with cyanogenmod 13?

Because I tried to flash t10s but seems worst then before the change. I have a nexus 7 32gb and with stock rom I never noticed those touchscreen issues. Today I flashed cyanogenmod and started have some small problems.Wich is the ts file from last google factory image?

If I flash boot-ts-unlock,img and then the last factory image,will I restore the stock drivers? I read some pages but I can t understand everithing perfectly

Are those drivers compatible with all touch panel models?
[Nexus 7 (2013) General] canirock:
can this work on a mac ?
[Nexus 7 (2013) General] marsaltito:
Yes , adb is key function not OS you run on computer .

Just find everything you need to run adb on osX .
[Nexus 7 (2013) General] k23m:
//oops
[Nexus 7 (2013) General] _jis_:
That is not true at all. Modified touch screen controller (TSC) firmware has nothing in common with modified system partition or OTAs in any way. You don't need to have root to load alternative TSC, only unlocked bootloader. Without root you cannot modify system partition.

Read whole thread and you will be amazed how many people solved or diminish their touch screen controller issues with those alternatively calibrated TSC firmwares including me and author (rip) of this thread.
[Nexus 7 (2013) General] marsaltito:
Lol . hahahahah you are joke boy !
[Nexus 7 (2013) General] k23m:
Thanks for your reply. The OP didn't bother to reveal what's in his files. If he mentioned firmware in his original post we would not be discussing it now. Is the 3-year old firmware patch still better than latest versions?

---------- Post added at 07:55 AM ---------- Previous post was at 07:50 AM ----------

He who laughs last, laughs longest.
[Nexus 7 (2013) General] _jis_:
This whole thread is about it and you didn't bother to read through it but at same time you didn't hesitate post your false statement and wrong request without any knowledge. That's what bothered me.

In such a case it is better be silent :angel:

That was answered many times in this thread. It depends on your particular Nexus 7 2013, because each one is unique regarding its TSC behavior with various version of stock ROM.

So there is only one right answer: you should try and test it for yourself, but be warned - it is a time consuming process.
[Nexus 7 (2013) General] afremont:
Why would someone want to install a digitizer when they can simply flash the firmware on their device with one of the packages and permanently fix their problems? Have you ever tried separating a digitizer from the glass on any mobile device, much less a Nexus 7? It's an art that takes much practice and even once you're good at it, you stand a 50% chance of breaking the glass anyway, then you have to glue them back together and not get bubbles in between. I don't know for sure, but I suspect that it wouldn't solve the problem anyway. It is my understanding that the problem is caused by different manufacturing shielding variations that were made during production. There was never a one-size-fits-all fix for these things. A digitizer and screen combination costs about $50. I fixed my wife's and my tablets by building the OS at home and including the firmware that worked best for us. As difficult and confusing as that was, it was still more manageable than trying to change the digitizer alone. Plus I get to see my name when I do Settings/About Phone. ;)
[Nexus 7 (2013) General] k23m:
Again, I read only the very first post of this thread and the conclusions were based on wrong assumptions regarding new OTA updates.

I noticed that the "fw_data.b" ektf3k firmware files in kitkat and marshmallow are identical so nothing has changed over the years. The firmware in CM12.1 which I use has several different bytes to those in stock kernel. The OP either had access to Elan's NDA documentation and patched a particular firmware or used various official Elan firmware versions in the packages posted here.
[Nexus 7 (2013) General] afremont:
Maybe it's not available now, but the various updates and releases that they put out back then had different firmware files. Most devices will work fine with one of those various files, it's just a matter of finding the one that works for you. The different release source trees had different versions. I was going to build marshmallow and include the firmware that worked for me, but I couldn't find the ektf3k file in the source tree. I'll have to look again when I decide to tinker with that stuff again. It takes about a day to compile it all on an I7-2600 machine.

Firmware files all contain a date, and are automatically flashed when the kernel boots if the date is later than the installed firmware. I think sfhub modified the date so that it never met that condition as newer releases came out, but he never released his source so I'm really guessing. I modified the routine that called the flasher so that it would flash in any firmware that had a different date, so that I could roll back. Unfortunately, that doesn't lock the firmware into place like sfhub's thingys. I never gave out the kernel I built since it was only for my device and sfhub supplied something easier for people to do.

It's been a while, but as I recall, I couldn't find the actual source file for the firmare in the tree for marshmallow, or maybe it was lollipop, I just don't remember. I'm still running the old kitkat release. I need to download the source again and try to figure it all out sometime.
[Nexus 7 (2013) General] k23m:
Please check here. I think the OP preset a sky high FW version number to prevent overwriting.

There is no firmware documentation - "fw_data.b" is just a hex blob.
[Nexus 7 (2013) General] masri1987:
this fixed it for me!
[Nexus 7 (2013) General] rodhull:
Might be useful to some if you're thinking of replacing your current Nexus 7 (2013):

I have a 16Gb model (stated as being produced in 2013), and its screen has always been flaky even from new. I managed to improve it almost entirely by using ts10 but it was never completely fixed. That version of firmware for me completely fixed the grounding issue (I could finally use it whilst it was resting on furniture or floor without me holding it which before was impossible) but I still got ghost and/or missed touches from time to time even when holding it normally. Matters got even worse after a bump cracked the glass last year in the extreme lower right corner (only ~1.5cm diameter confined to the bezel only) and the frequency of ghost/missed touches just increased.

So I decided to replace it. I love the form factor and Nexus experience so there wasn't really any other choice but another Nexus 7 (2013) and having learned on these forums that at least one person had got one that had a "December 2015" production date, hoping it would have an improved touchscreen experience...

So, I received another Nexus 7 (2013) (32Gb model this time) very recently, purchased from Argos in the UK (it does have December 2015 as the production date) and I have absolutely zero touchscreen issues with this hardware variant, so have not had to apply any of these firmwares or resort to opening the case to fiddle with shielding etc.
[Nexus 7 (2013) General] SoulSmasher:
Hello,

After applying this, if I lock the bootloader can I keep on getting ota on stock rom ? I only unlocked for this purpose.

Thanks in advance,

Edit: I can confirm this fixed my issue with flo 16GB with number 10. Touch screen is now as it should be. Thanks!
[Nexus 7 (2013) General] Sesme:
Im use ts10 on N7 LTE 32GB Elan_kTF3K_xa059

In Android 6.0.1 not-rooted

Thx
[Nexus 7 (2013) General] Natakranta:
You don't have to lock your phone/tablet bootloader to receive OTA. It has nothing to do with bootloader locked or unlocked. OTA checks only if system and (not 100% sure here) karnel are not changed from the official factory version. So unless you rooted or otherwise changed sth with system / karnel, you can still take the OTA.

But wiat a minute, we are in Nexus 7 section, what OTA are we talking about? No more updates here :D

And since you have bootloader unlocked open your eyes to new dimension and fastboot flash TWRP recovery and flash some nice ROM with root. I'd recommend Pure Nexus Mod with open gapps nano, theme ready gapps on top of it, SuperSU 2.76, and ElementalX karnel

Enjoy!

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Nexus 7 (2013) General] SoulSmasher:
Hello,

Thanks for the detailed explaination, I really appreciate that! :good:

I've been using Cyanogenmod over years with various of my phones. This is the first nexus device I've ever had, and I wanted to keep using stock nexus rom for that time being. Since I've heard this wouldn't be getting any updates I've already swiched to CyanogenMod :laugh:
[Nexus 7 (2013) General] fonixmunkee:
Running stock 6.0.1 (August security update) on the N7 2013 (wifi only), the touch screen was terrible before ParrotMod. ParrotMod made it bearable, but flashing the TS10 made it 100% functional. Thank you!

EDIT: Ooops, did a QUICK REPLY and took OP's...OP quoted.
[Nexus 7 (2013) General] akism:
The file boot-ts10-lock.img worked for me after a nexus 7 fhd screen replacement.

Thank you
[Nexus 7 (2013) General] big_finger:
hi all ,

I did step by step by this guide .

adb reboot bootloader ==>okie

fastboot boot boot-ts10-lock.img ==> waiting for device , i stuck on this step . This cmd screen displays "Wating for device " .I wait for 10 minutes but doesn't happen :(

Please give me some advices.
[Nexus 7 (2013) General] Red_81:
You do not have the correct fastboot drivers installed. I think the Android SDK would install them for your device.
[Nexus 7 (2013) General] atjun kustiawan:
Can I try this on nexus 7 first generation?
[Nexus 7 (2013) General] SoulSmasher:
Just a heads-up:

I broke my nexus's screen :( , then replaced it screen with this: https://www.aliexpress.com/item//32430562835.html and the number 10 is still working as it should with this screen.
[Nexus 7 (2013) General] fireghost:
Hello, you can update the link to the boot-ts file.7z?

file not is obtained download (