yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] lespaulman67:
Well went from perfect Nexus 7 2013 to loading the ts10 fix then went to the JSS15Q and was running

Perfect still. Now with the newest update I decided to uninstall the ts10 and side load the new update. Well guess what I had dead spots all over again.Do you believe this bull crap .My 15 days are up. So I loaded the Ts10 fix again and boom the screen is working again. I do see more ghosting now then before with same fix.Why Google why.How can you not fix a screen problem.
[Nexus 7 (2013) General] kingston73:
This didn't work for me, tried it and it said last update was 12/31/1969
[Nexus 7 (2013) General] lomonic:
Try rebooting a few more times e.g. give it 3 tries, after u make any changes. Might help.
[Nexus 7 (2013) General] lomonic:
I did my initial tests with the tablet on a timber-table on top of some pieces of paper and it was great. Thing is, after a night of usage, it seems i'm running into some weird jumpy twitchy behaviour again, and the backspace key got stuck once.

So it really does not seem that JSS15R has anything to do with touch at all. The fresh reboot might have contributed to the early perception of improved performance for a few.
[Nexus 7 (2013) General] stfudude:
After I bought this tablet, I immediately flashed TWRP (6.0 IINM) and SuperSU 1.51. I got two OTA updates shortly after booting the tablet, bringing my N7 to JSS15Q. Then, I installed busybox. Then a few days after that, SuperSU got numerous updates bringing it to version 1.65 (Google Play store).

Then today I noticed in this thread that JSS15R update has started rolling. I tried my luck by doing manual update, but didn't get the update. So I decided to follow the steps in first post (by manually flashing OTA zip in TWRP).

I got the error like the picture attached.

Then, I launched SuperSU app to do the full unroot. I reboot after it finished removing supersu stuffs. Then I reboot to recovery to flash SuperSU 1.65 zip file (I didn't fix permission because I'm not sure what that has to do with this problem). Then I reboot to system. Then I reboot to recovery, and I select "fix permission" in advanced (I still think it's useless). And I still got the error shown in attached picture.

Can someone please help? I know habylab also got the same issue.

:(
[Nexus 7 (2013) General] habylab:
I just installed the Stock ROM in the Android Development section, the only one for R I believe.

I believe I had a mod installed, Power Menu, that caused issues. Try flashing the stock ROM, do you need a link? It doesn't wipe anything either. Hope this helps

Sent from my maybe one day to be CM i9300. That day won't come unless the camera improves!
[Nexus 7 (2013) General] Reckoning:
I was on JSS15Q with ts10 without screen problems. I unlocked the ts10 img and installed JSS15R through TWRP with any problems. Rebooted and checked with YAMTT and multi-touch jitters returned. Went back to ts10 and problems are gone. This update sure didn't fix the screen issues for me.
[Nexus 7 (2013) General] roy827:
i cant be the only with problems fixed by jss15r, and not by jss15q.

Just dont believe it, is there anyone else?
[Nexus 7 (2013) General] rndll:
My touchscreen was perfect on stock all the way through JSS15Q. I have never applied any of the 3rd party fixes. This R update has introduced the touch screen jitter problems a lot of people have been complaining about! What gives?

---------- Post added at 08:36 PM ---------- Previous post was at 08:11 PM ----------

https://www.youtube.com/watch?v=dsRtLOQRCDI&feature=youtube_gdata_player

This is so frustrating!
[Nexus 7 (2013) General] molo88:
My new nexus7 had a freeze-n-reboot just now after 13 days uptime,

When i was trying to switch accounts in Google keep.

Rooted ,TWRP, JSS15Q. SuperSU v1.60

Now I have a problem that adb can't not connect to nexus7 in Twrp sideload mode, while it is normal when nezus7 is running.

Adb version is 1.0.31.

Anyone know why I can't connect via adb sideLoad Mode?

Thanks.
[Nexus 7 (2013) General] stfudude:
I'm using stock rom. The kernel however is not stock, I'm using faux kernel. The recovery is not stock too, I'm using TWRP. I installed xposed framework , which is the only mod that "might" cause this error but I've already uninstalled the mod before flashing the OTA zip.

The definite cause for OTA failing in Android 4.3 is supersu (I've read many threads here discussing 4.3 OTA failing), but IIRC supersu version 1.5+ should not cause this error.

I don't want to wipe my tablet because I hate restoring apps and data with titanium backup. Doing so will waste my precious time. I was once a rom flasher but today I don't feel like flashing anymore. Stock rom is good enough for me, with the inclusion of xposed framework. With xposed framework there is no need to flash a custom rom to get advanced power menu or PA Halo - like multitasking.

Now if only I could flash this OTA zip without any error...
[Nexus 7 (2013) General] Gorgtech:
How can you hate TB ? Buy the prof. version, it´s worth the money and saves you a lot of time. If you also use a custom launcher ( eg. Nova Launcher Prime ), you can easily restore all your shortcuts and settings with one single click..

Some apks are worth the money and are a good investment if you intend to use Android for a long period of time ( eg. Swiftkey Pro, Nova Launcher Prime, Trickster Mod donate, TB pro ... )

I hardly need more than max. 20 minutes to set up a newer Firmware version including. all my Apps and settings..
[Nexus 7 (2013) General] rndll:
Just went back to JSS15Q and my touchscreen is fine again. :|
[Nexus 7 (2013) General] stfudude:
There is no need to tell me the the benefit of buying the pro key because I've already bought it, two years ago.

I always have to launch my apps one by one after restoring with TiBU, to make sure that the app doesn't FC and its data is intact. I have about 200 apps, mostly games. It will definitely take one day for me to do all that.

But I digress. Let's stop this off topic and focus on JSS15R OTA.
[Nexus 7 (2013) General] AnarchoXen:
I had Tablet UI and the APM flashed before going to R. I dropped R on top then the bootloader, wiped dalvik etc..fixed perms...Flo is working great.
[Nexus 7 (2013) General] oldtimer42:
Is there a changelog yet for JSS15R? Is this normal for Google to not release one?
[Nexus 7 (2013) General] lespaulman67:
How can I go back to JSS15Q Mine was perfect with the Ts10 fix. Now its not as smooth jittery on Scrolling.lagy on key hits.I'm also having problems with this site on my browser keeps refreshing over and over.
[Nexus 7 (2013) General] rndll:
I just reflashed the older pre rooted, odexed flashable zip posted here on XDA.
[Nexus 7 (2013) General] habylab:
Flash stock kernel, or like I said, the ROM.
[Nexus 7 (2013) General] Ekinnoxx:
Just flashed the OTA with TWRP 2.6.3 on my stock rooted -> JSS15Q->JSS15R OTA

Flash OK without problem

Try to unlock ts10 but not good, so install boot-ts10-lock again. Maybe for the next update :p
[Nexus 7 (2013) General] sfhub:
Post the error and I should be able to tell you what is causing the error.

Most likely your ota failure is caused by the custom kernel.

Recovery will only cause ota failure if you installed deb version. If it is flo version it will work.

SuperSU v1.55 or above will not cause ota failure.

If you get assert failure if is either kernel or modified/delete ROM file. If it fails near the end then it is superSU.
[Nexus 7 (2013) General] sfhub:
Did you ever have adb working with recovery? You need modified adb drivers to have it work with recovery.
[Nexus 7 (2013) General] sfhub:
Assuming you ran ts-unlock at some point, have you tried installing ts10 again?

If you want to go back to JSS15Q, there is a link in the JSS15Q thread to install the factory image and preserve your data.

http://xdaforums.com/showthread.php?p=44888268#post44888268

However I would try reinstalling ts10 first unless there is something else you don't like in JSS15R
[Nexus 7 (2013) General] sfhub:
If you have the energy, try running ts30 with JSS15R. I suspect you will get the same behavior.
[Nexus 7 (2013) General] sfhub:
Based on your image, the ota is complaining that your kernel (boot.img) is not stock JSS15Q
[Nexus 7 (2013) General] stfudude:
Looks like the problem is caused by custom kernel. I never thought that custom kernel can mess with OTA.

I learn something new today! (which is: custom kernel can mess with OTA update so I have to flash stock kernel).

[MENTION=3262915]habylab[/MENTION] thanks, buddy. I didn't understand what you meant by flash stock rom but now I understand. You mean I have to flash the stock kernel.

[MENTION=1299673]sfhub[/MENTION] thanks to you for clarifying what the error mean.

:thumbup:
[Nexus 7 (2013) General] sopidos:
(FYI, I pressed the "install ota" when it appeared, but since it just booted to TWRP it didn't change any thing i guess.)

So I'm on JSS15Q with ARM + SuperSU 1.65 and TWRP. I should go with the second option in the download-section right?
[Nexus 7 (2013) General] TML1504:
another reason could be the APM (advanced power menu) mod! for me this prevents the OTA from installing, due to a failing check in one of the modified files! i'm currently on Q, rooted and with APM mod...
[Nexus 7 (2013) General] fewt:
My Nexus 7 received the JSS15R update today, re-rooted and tested multitouch. Multitouch ghosting was the only problem I had with the device (other than Netflix), seems like it's been resolved for me. Able to touch type on the tablet without random jumps and characters.
[Nexus 7 (2013) General] wintermute000:
Chalk my unit up as another one that was nearly perfect on JSS15Q and now noticeably more 'jitter' when crossing axises on JSS15R.

Never used any custom touchscreen firmware etc. just upgraded stock as I went along.

I applied the JSS15R update via the tWRP flashable zips (including bootloader) in the dev thread but that shouldn't make a difference
[Nexus 7 (2013) General] sfhub:
Looks like Google forum software may have issues with so many posts on the multi-touch issue, added continuing thread.
[Nexus 7 (2013) General] Muikkuman:
I just had the update OTA and everything seems OK. Supersu 1.65 managed to keep root.
[Nexus 7 (2013) General] astuermer:
Flashed JSS15R yesterday on top of my 15Q.

So far better touchscreen experience.

1. No ghost touches so far when using more than 2 fingers.

2. Ungrounded no ghost touches so far.
[Nexus 7 (2013) General] kashporov:
Hello.

Does anyone have such a problem with jerking image? Just received tablet with JSS15J, get OTA JSS15R and after update i got this problem in every screen. Even at the boot screen. So, i tried going back to JSS15Q firmware, but it did not help - the same problem with JSS15Q.

Sorry, this forum block any oustide url for new users and i can't post video url directly, see attached file.
[Nexus 7 (2013) General] juliatan:
Stock OTA-update failed

While updating by system offered JSS15R got OTA Error with lying down Android figure.

I have Rooted Nex7/2 (Build JSS15Q) with stock bootloader. Flashed Supersu 1.5.1 with booting and not flashing unwanted TWRP. Supersu was already updated via Play Store to version 1.65.

Why with some no problem with OTA update with exact same situation as mine and others OTA-error? My (still rooted) device does not even see the update anymore, says with JSS15Q I am up to date. I bought a Nexus especially to be freed of costom recovery sh*t and have Google's fresh OTA's, but an unrooted Android is unworkable for me.

Can the problem be that in app settings I disabled every never used and otherwise still constantly running apps from Google? I disabled Agenda (& agenda-storage), Contacts, Currents, E-Mail, Gmail, Play Books, Play Games, Play Music, Google+, Hangouts Youtube and Keep. But they are still in system/apps-folder.

How do I solve this? How can I get the update to be re-offered on device again without failing? I don't want to use custom recovery anymore like on other Samsung device. I just want a rooted Nexus with original bootloader and functioning OTA-updates.

Thanks in advance
[Nexus 7 (2013) General] infectwifi:
OTA safe to install ??

Hello, i am android virgin 2 days ago :p

I have Nexus 7 2013 4.3, JSS15J, custom recovery TWRP, rooted, supersu v1.65, i believe stock kernel

I received the OTA update. What should i do. Click reboot to install and everything is OK good to go or there is a different method?

Thanks
[Nexus 7 (2013) General] MrH.uk:
I just got the update but now there's something wrong with my root, SuperSU says there's no binary installed. I'm really new to this stuff so if someone could help me I'd appreciate it.
[Nexus 7 (2013) General] kornog77:
Just reinstall your root.
[Nexus 7 (2013) General] stanglifemike:
I believe if you try to install it will just fail, since you're using a custom recovery, but no harm will be done an nothing will change. You could install the stock recovery or just wait until a developer releases this OTA in stock rooted form, or flash a custom rom that is based on this latest OTA. CleanRom is and excellent rom and is very close to stock! It hasn't been updated to this latest OTA yet, but you could try out the current version and see what you think. Just do a Nandroid(Backup) of your current setup first inside your recovery. Then you can just Restore that Nandroid and easily go back to how your device currently is without anything changing. CleanRom is what I use on mine. In fact, I've been running scrosler's roms since WinMo days on multiple WinMo devices, and on multiple Android devices as well once Android devices were released. He is very talented, and by far my favorite developer!

I received the update yesterday, but I'm waiting for scrosler to release CleanRom based on this latest OTA.

SwiftKey'ed from my '13 Nexus 7 FHD using XDA Premium HD
[Nexus 7 (2013) General] AnarchoXen:
http://xdaforums.com/showthread.php?t=2447876

Why wait...
[Nexus 7 (2013) General] fustyler:
problem with flashing

please help a noob. i was trying to flash the "Stock Rooted JSS15R - DeOdex" on top of the latest CM 10.2 build. I flashed cache and dalvik cache before i flashed JSS15R. Device was rooted with twrp and debugging mode on.

However it gets stuck on the X logo on the reboot. The same happened when I try again. Does anyone have any suggestion?
[Nexus 7 (2013) General] sfhub:
What version does it say you have in settings->about tablet?

Disabling apps would not have caused the error, ota only cares that the files are present and unmodified. If you removed the app then that would cause failure.

Usually once you get offered, you are continuously offered until it installs properly.

You can download the ota update by hand, put it in your virtual sdcard, then boot into twrp and install from there. Make sure to write down any error so we can diagnose.

For the future if you get an error with android fallen down (stock recovery) press/hold Power, press/release VolUp, release Power and you will see the error log.
[Nexus 7 (2013) General] sfhub:
Try reflashing CM10.2

What you have done is called a "dirty flash" often it works OK when flashing new versions from the same ROM developer, but whwen you switch back and forth to different ones, it is suggested you backup, wipe data, and restore.

Alternatively if you don't care about your data, boot to recovery and do wipe data/factory reset and it should get you past the X.
[Nexus 7 (2013) General] infectwifi:
Thank you but i am a noob, like a yesterday noob this is out of my comfort zone.. :crying:

I just wish there was a guide that says: "Yo bro you are this build rooted with this recovery and you want this update go ahead update you are ok, or no don't do itttttttttttttttttttttt..... you must follow this steps before you update 1,2,3"
[Nexus 7 (2013) General] fustyler:
Thanks. I reflashed CM10.2 again, and can boot into the system.

When I go into setting, it now states "cm_flo-userdebug 4.3 JLS36C eng.root.20130918.153157 test-keys"

How do I verify if JSS15R has been installed?
[Nexus 7 (2013) General] thepolishguy:
Okay - here's my situation...

I was rooted & twrp'ed. Saw there was an update. Wanted it. So in fastboot I fastbooted...

1. boot.img

2. bootloader.img

3. cache.img

4. system.img

5. userdata.img

6. recovery.img

7. and any other image file from... ...razor-jss15q-factory-4f77b811.tgz

Booted up and got the message for the update to JSS15R. But the update failed. So I tried adb sideload <filenamehere>.zip (with the actual file name) and it still failed. Tried everything multiple times. HELP!

And yes I know I can flash twrp and flash the rooted version. I want to know why this isn't working and I want to fix it!

Thanks guys for any help.
[Nexus 7 (2013) General] Richieboy67:
I just use voodoo root lock. I just run the update and voodoo root locker saves root. I'm not sure though of this will work for this one.

BTW- To those that keep getting the update notification but do not want them just press on the notification for a few seconds, click on app info and disable notifications and you will no longer be notified. This is if you have a custom rom.
[Nexus 7 (2013) General] sfhub:
It hasn't been installed, you are running cm10.2 now. If you want JSS15R I suggest you backup your data and flash JSS15R using the second link in the download section, then reboot, if it doesn't get past X, boot to recovery, do a factory reset, then restore your data.
[Nexus 7 (2013) General] sfhub:
It is very strange, I have never seen the assert fail when checking for free space.

When you flash the factory image for JSS15Q, have you tried using the flash all script rather than doing things by hand. It guarantees no steps are missed by accident.

Also you are using WiFi n7.2 right (not LTE)?
[Nexus 7 (2013) General] thepolishguy:
Yes wifi only.

I tried using the flash all but something went wonky.

I have not tried Wug's Toolkit and a complete restore. I will keep you posted. Thanks for the help.
[Nexus 7 (2013) General] mjb152:
I received the update OTA, installed it and it rebooted, I've lost root but most importantly it's wiped out twrp. Can't get into recovery mode at all. Well I did managed once, but the only option it gave me was to use adb sideload. Not sure how to proceed now, I'd like to root it again and also get twrp installed.

I have a full twrp backup, so not really sure how I can restore that to start again ?
[Nexus 7 (2013) General] ciento:
my experience

i was running stock rooted (JSS15Q) with twrp 2.6.0.0 and superSU 1.65.

received OTA notification for 15R. let it do its thing (i.e. let the software automatically install the update). installation successful via twrp. upon reboot lost root and twrp.

reflashed twrp and superSU. easy as pie. :cool:
[Nexus 7 (2013) General] sfhub:
adb reboot bootloader

fastboot flash recovery twrp.img

fastboot boot twrp.img

Press Install and select SuperSU update.zip
[Nexus 7 (2013) General] ciento:
download the latest TWRP

download the latest superSU

place superSU on your device

place the twrp in your platform-tools folder and rename it recovery-twrp.img, then type:

adb reboot bootloader

fastboot flash recovery recovery-twrp.img

from the bootloader select start recovery. twrp will start. flash superSU and reboot. good to go.
[Nexus 7 (2013) General] mjb152:
and that was worked like a treat. Many thanks, I really appreciate the advice given.
[Nexus 7 (2013) General] thepolishguy:
update

UPDATE:

So after using the toolkit to do a complete restore the update.zip flashed without a problem. So I must have missed something somehow.

Thanks.
[Nexus 7 (2013) General] :
here you goooo

https://dl.google.com/dl/android/aosp/razor-jss15r-factory-ec2d4f76.tgz

their it is jss15r factory image:D
[Nexus 7 (2013) General] PJ Clifford:
Basically the same situation here. Only difference is that I was/am in the latest TWRP (2.3.6.0?). Did the OTA. It bombed out in TWRP and the N7 rebooted. Checked version and it was still on 15q. Tried again, same result. It rebooted so fast after it bombed that I couldn't see any error messages.

I quit at that point and grabbed the pre-rooted Odex version and flashed that through TWRP. Worked perfectly. I'm ok at this point, but would like to know why the OTA didn't work.

BTW, I've read that after the download, the OTA files are already on the device and one could just flash that through recovery, but for the life of me, I couldn't find the flipping things anywhere in the file system. Where the poo are they?
[Nexus 7 (2013) General] ciento:
what version of superSU were you running? if you were 1.55 or before, the OTA will fail.
[Nexus 7 (2013) General] sfhub:
The ota update.zip should be in the cache directory, but once it runs it is removed.

It might be that only SuperSU v1.55 and above installed through an update.zip rather than through play store will fix the ota issue. I haven't looked at the online update, only the update.zip
[Nexus 7 (2013) General] txaggies07:
Update fixed my smart cover functionality. One of the past updates had broken it.
[Nexus 7 (2013) General] fustyler:
Apologies on another noob question.

After I have successfully flashed JSS15R into the device, do I simply flash CM10.2 on top to install cyanogenmod? Or will doing so remove the JSS15R update? My device is wifi only.

Thanks.
[Nexus 7 (2013) General] Muikkuman:
Wait for CyanogenMod to make a version based on latest ota
[Nexus 7 (2013) General] munggo:
just updated

Been lurking for the past month or so. First time poster.

Just updated from 66n to the new update ota..

Somehow typing on the keyboard seems a bit sticky which I never had a problem with in 66n..

Checked with ymmt all is fine though..
[Nexus 7 (2013) General] thunderger:
Can someone post content of build.prop (jss15r) file, please?
[Nexus 7 (2013) General] juliatan:
As I told in earlier post now still build JSS15Q after failing OTA. I renabled all those earlier disabled Google apps. (Extra batterydrain ridiculous Google! Fix those always running even stealth apps of ours Google please! *6&*$%##@!), but I haven't had any offering to re-update since. But after reading the new reactions on this post having to flash is unevitable due to Supersu 1.5.1 even when updated to 1.6.5 through Play Store. Hope this is going to be the last time I have to flash this tablet while remaining root, because flashing my phone or this tablet to be honost scares me a lot each and every time.

Three questions to be shure before I flash (excuse me if already mentioned in topic(s), but it all is so much information):

1. Can I instead of adb-flash temperarely boot TWRP (like I did to root my Nexus 7/2, not wanting to flash permanent TWRP on tablet) and then install the 'JSS15Q->JSS15R OTA (thanks roy827)' from page 1 with temperarely booted TWRP on my rooted Nexus 7/2 (with its stock bootloader)?

2. Can the latest Supersu 1.6.5 be flashed over the old one without first removing old Supersu 1.5.1 (with including Play Store-updates), cleaning its cache, etc. You read about people just flashing it and it works, but also you read about people who can't get Supersu working again because of crashing, etc due to corruption of old SuperSu leftovers.

3. After flashing JS15R must I directly flash new Supersu (if old Supersu does not need cleaning up first) or first reboot after update before flashing new Supersu

I really hope in the future I can get automatic OTA-updates and remain root without any problems which need flashing ever again. If that is not the case, perhaps permanent TWRP is than better But I certainly hope not.

Thanks again
[Nexus 7 (2013) General] sfhub:
Yes to your questions

adb reboot bootloader

fastboot boot twrp.img

Install SuperSU 1.55 or greater

Install JSS15R ota update.zip

Install SuperSU 1.55 again
[Nexus 7 (2013) General] juliatan:
Oké thanks.

So I can do all those steps in one session without in between reboots for applying changes/updates first before next step?
[Nexus 7 (2013) General] PJ Clifford:
Thanks for the info. I will specifically look there next time.

So, if I am hearing your correctly, I should update SuperSU to the latest version from an update.zip file from TWRP?