yashsingh1/xdaforums huggingface dataset:
[Moto X Q&A] jayboyyyy:
Ya I edited my last email app similar to those instructions and just replace the security check with 1 or 0 or whatever it was that made it think it ran the check already. If I get bored I'll work on the Verizon apk this weekend. I haven't touched the stuff in a while so I might not but I'll post the apk if I get around to it. Drinking can inhibit the process though.

Edit: if someone is already doing it and I just missed that info let me know in the chance I do decide to do it this weekend.
[Moto X Q&A] jayboyyyy:
verizon moto x

I am currently working on the email.apk. there is also the exchange2.apk that i believe will need to be edited as well.

When I edited the email apk a couple of years ago I just went to these lines and returned true and false. These lines check to see if the policies are enabled I believe.

.method public isActive(Lcom/android/emailcommon/provider/Policy;)Z
.registers 1
.parameter "policy"

.prologue
const/4 v0, 0x1

return v0
.end method

.method public isActiveAdmin()Z
.registers 1

.prologue
const/4 v0, 0x0

return v0
.end method

I then tried to recompile it and i got an error stating that two registers were required for one of the two changes. I haven't looked at which line yet because I know I don't know enough to figure out why it needs to registers. Here is the error.

c:\MotoX>java -Xmx512M -jar smali.jar out -o classes.dex
out\com\android\email\SecurityPolicy.smali[1659,4] This method requires at least
2 registers, for the method parameters

so this is where i am and this is what im stuck on. Ill attach the entire smali file so anyone that can help can take a look at the entire code. Ill also attach the security admin smali in case that matters.

Ill also begin working on the exchange apk, but this apk didn't exist the last time i did this so I'm not sure what I'm going to do with it. Like I said, Im not good at this stuff I just really want an exchange security bypass for my Moto X.
[Moto X Q&A] jadeddjay:
i have been messing with that ExchangeNoPIN-v6.0 found in here

i am have a dev edition, rooted, on the 4.4.4 ota. i believe on 4.4.2 i had it working simply by flashing the zip on twrp but this was not the case with 4.4.4. i tried a bunch of different things by trial and error... eventually what i ended up doing the following get this to work (not sure which step was the key).

you have to make sure to clear data and cache in both email and exchange service apps first

i copied email.apk and exchange2.apk from the zip in the aforementioned thread into my phone.

interesting bit on 4.4.4 is that email.apk is in /system/priv-app and exchange2.apk is in /system/app

i took manually copied both apks into /system/app and /system/priv-app using root explorer, and set 0644 permissions for each, rebooted, didnt work, so then i simply manually installed both of them by clicking on the apks (from the original directory, before they were copied to the system folders). this installed them as an "update."

after I did this, everything was working.
[Moto X Q&A] shamelin73:
Use a program Nine is is an awesome Exchange client and has either device or application support. Keeps me from locking down my device with the stock exchange client.
[Nexus 7 (2013) General] oldblue910:
THe JSS15R OTA comes with a new bootloader. Can someone let me know what the new version is? Thanks!
[Nexus 7 (2013) General] sfhub:
Mini guide for flashing stock factory image:

You must have your bootloader unlocked to flash the factory images released so far.

You have the OPTION to wipe your data but it is best to back up anything important AND copy off the phone

Download the factory image from here:

http://developers.google.com/android/nexus/images#razor

Unpack using 7-zip or winrar.

You may need to unpack twice

once to get the .tar file from .tgz

another to get the actual razor-jss15r directory from the .tar

unzip razor-jss15r-addon.zip into the razor-jss15r directory (from previous step)

boot your tablet to the bootloader using Power+VolDown

connect via usb cable to pc

If you have problems with drivers, use the adb_driver.zip from this post

in command prompt in the razor-jss15r directory type EITHER

flash-all

(this WILL perform factory reset and wipe your data, including virtual sdcard, starting completely fresh)

OR

flash-all-nowipe

(this WILL NOT wipe your data, nor your virtual sdcard, allowing you to preserve your setup)

You can ignore the warning about the 3 missing .sig files in the status.

Google didn't sign these factory restore images, which is incidentally why you need to be unlocked to flash.

If you have issues after upgrading, the first thing you should try is factory reset (backup your apps and sdcard if needed)

Whenever you preserve your data whether it be factory image or natural OTA, there will always be a

small percentage

of users who will encounter instability, depending on what apps they are using
[Nexus 7 (2013) General] devilsmack:
3.15
[Nexus 7 (2013) General] sfhub:
For future reference, diffs between 3.15 and 3.14 are in aboot and tz. rpm, sbl2, sbl3 stayed the same.
[Nexus 7 (2013) General] sfhub:
Could someone please perform the following and post results:

reboot tablet

su

dmesg | grep "firmware version"

This will tell you if your touchscreen firmware has been updated.

Thanks.
[Nexus 7 (2013) General] kkd28:
can anyone confirm that the cover wake up issue has been solved?
[Nexus 7 (2013) General] hoodie666:
on terminal emulator - > firmware version: 0xa042

with JSS15R installed from twrp

edit -- > its _fw_packet_handler : firmware version .... maybe not what op is looking for - thats whtat the command gave in terminal emulator .
[Nexus 7 (2013) General] roy827:
So it is still 042 firmware then.

Personally, I think that there has to be something changed on the new update to fix more screen problems. Because mine is definitely better than before on jss15q/ts10. Now is perfect even with 10 fingers...
[Nexus 7 (2013) General] bandit_knight:
Did you roll the ts10 back before the update or installed on top of it?
[Nexus 7 (2013) General] gogol:
If I am using the ts10 multi touch fix....

Will that ts10 fix stay if I install this update?
[Nexus 7 (2013) General] oldblue910:
Probably not, but you also probably won't need it after the update.
[Nexus 7 (2013) General] gogol:
Because last time sfhub said that his ts10 fix stay, even though you don't flash it.
[Nexus 7 (2013) General] roy827:
Yes i did, used the unlock.

FYI [MENTION=1299673]sfhub[/MENTION] my buddy, here is what you may need:

"E:\adb>adb shell

shell@flo:/ $ su

su

root@flo:/ # dmesg | grep "firmware version"

dmesg | grep "firmware version"

<4>[ 2.101989] [ektf3k]:[elan] __fw_packet_handler: firmware version: 0xa042"
[Nexus 7 (2013) General] sfhub:
TS10 will stay on your tablet even after the update. When you are comfortable with what comes with the update, run ts-unlock and you will then get the touchscreen software that came with the update upon first reboot (which is part of the process of loading ts-unlock)
[Nexus 7 (2013) General] sfhub:
Yes, that was what I was looking for. It confirms the touchscreen software in the JSS15R kernel is the same as what was included in JSS15Q.

That doesn't automatically mean there is no fix, just that if there was a fix, it wasn't located in the touchscreen firmware.
[Nexus 7 (2013) General] lomonic:
my touch is perfect so far after upgrading. for those who installed the ts-xx fixes, make sure u install the ts-unlock before you update.

the difference is so visible in YAMTT .. just do multi fingers cross overs of axis and you visibly see the differences. there's no more twitchy or jerky touches, and hopefully no ghost touches for those who were experiencing it. good fix so far.
[Nexus 7 (2013) General] sfhub:
The interesting thing is it was confirmed earlier that the touchscreen firmware in JSS15R is the same as JSS15Q.

That would mean any fix for the touchscreen would have had to be contained outside of the firmware, either kernel or android runtime.

If that is the case there is a good chance all the older firmware would start behaving better on JSS15R.

Anyway, as an aside, you can run ts-unlock before or after the update. Either way you will end up with the same touchscreen firmware, and if the new fix is as we currently theorize, outside of the firmware, you'll have the same benefits.
[Nexus 7 (2013) General] lomonic:
Ah good to know.. I've done some further testing with the new update and it is indeed improved with regards to touch sensitivity and accuracy. That said I did a crazy fast tap on yamtt in the same spot - not exactly what anyone would do in daily use, and touches do still get stuck. Google maps And earth works well thou. Chrome Still lags randomly and chromebeta still has random reboots but those are likely app related.

So all in all, improved but still room to work on. Hope it fixes those with really major problems.
[Nexus 7 (2013) General] Anders1:
This OTA update would be really interesting to test, however, I've modified my build.prop slightly (rooted stock JSS15Q) so the update fails. Could someone please upload the original unmodified build.prop for JSS15Q?

Many thanks in advance!
[Nexus 7 (2013) General] sfhub:
Those are the boot.img files to flash in fastboot/bootloader. They weren't meant to be flashed in TWRP/recovery.

boot to bootloader mode (Power+VolDown)

fastboot flash boot boot.img

The zip only contains the boot.img for the version you downloaded.
[Nexus 7 (2013) General] fcng:
Me too

I'm having the same issue too. I'm using a Portenzo case and it takes at least 1 minute to turn the screen on after I opened the case cover. It works immediately if I just closed the cover and opened it in a few minutes.
[Nexus 7 (2013) General] sfhub:
Turn on bluetooth as a workaround.
[Nexus 7 (2013) General] fcng:
Battery Life

Would that eat away my battery life?
[Nexus 7 (2013) General] sfhub:
In my experience unless you have an active BT connection, the difference in battery life is not noticeable. Also as a side benefit you can configure WiFi to turn off during sleep (and still have the magnetic unlock work), in which case, you might even see a net increase in battery life, at the expense of your network connection taking an extra second to be enabled when turning on your tablet.
[Nexus 7 (2013) General] fcng:
It works....

sfhub,

Thanks for the tip. I'm already using the app"2X Battery - Battery Saver which puts WiFi to sleep when the screen is turned off and triggers it back on when the screen is on. It really saves battery life. I'll keep track of the battery usage with BT on. I'll report back.
[Nexus 7 (2013) General] sfhub:
BTW you can accomplish the same thing by changing the advanced options for WiFi.
[Nexus 7 (2013) General] peeyourownpants:
thanks a bunch. had stickmount freeze up a bunch and couldn't adb sideload 4.4 with a debuggerd error. flashed the jss15r-debuggerd.zip in OP and was able to upgrade! i have a raging clue for you guys right now! kitkats!
[Nexus 7 (2013) General] mjb152:
I'm rooted and using the latest TWRP, the sideload failed with a debuggerd message, so I flashed the jss15r-debuggerd.zip in OP , rebooted fine, then I sideloaded 4.4

The upgrade seemed to go ok, it started to optimise the applications and finished, then it said finishing boot, an dit never did. Left it over an hour, forced rebooted and now I just get the startup animation in an endless loop. I tried to run sideload again, but it leaves me in the same position.

what shall I do from here ?
[Nexus 7 (2013) General] sfhub:
There are always a small percentage of OTA upgrades that hang on boot for various reasons. Some are incompatible apps, some are corrupted user data.

If you have a backup, just boot into recovery and wipe data/factory reset. That will very likely get you booting again. Then restore your backup, just the apps, not the OS stuff.

If you need to backup your user data, you can try using fastboot to temporarily boot into twp and then copy the userdata stuff off the tablet or do a nandroid backup of the user/data partition. You do need to be unlocked though and if you haven't done that already, then it'll unfortunately force a wipe before unlocking, which wouldn't help you.
[Nexus 7 (2013) General] mjb152:
think I need to do a full wipe, might be better. Trouble is, when I try and go into recovery mode I get the fallover android sign, and then my only option is a apply update from adb. the flashall command just hangs waiting to see the device.
[Nexus 7 (2013) General] sfhub:
At the fallen android

Press/hold power , then press/release VolUp , then release Power

In that exact sequence

You'll see a menu, use VolDown to scroll to wipe data factory reset, then press power to select
[Nexus 7 (2013) General] froggydoddy:
ALL my OTA's end up failing at the end and I hang at the TWRP screen and have to manually hit "reboot". Of course the updates never take. So I've been using your files to update all along. Same thing just happened with my KITKAT OTA. Any plans on adding that one here as well so that we can successfully update?
[Nexus 7 (2013) General] sfhub:
Is there any error message in the status logs?

If there is, post it and I'll try and figure out the issue.
[Nexus 7 (2013) General] froggydoddy:
I don't think so. Everything seems to go fine. Then it just stays at the reboot options screen. I hit reboot, system. The tablet reboots and the update isn't applied. This is what always happens to me with OTA's. That's why I had the use the updates provided by this thread. Running the latest TWRP and SUPERSU (1.75)
[Nexus 7 (2013) General] sfhub:
Is there any message when you run the OTA updates?

It should at least say things like

Removing unneeded files...

Patching system files...

Unpacking new files...

Unpacking new recovery...

Symlinks and permissions...

Writing DDR...
[Nexus 7 (2013) General] froggydoddy:
It says a bunch of stuff. I'll have to pay closer when I try to update again in 3 days. The OTA's usually show up every 3 days.
[Nexus 7 (2013) General] sfhub:
If you want, you can manually force the OTA by sideloading it. Instructions are in the first post.

It is very important to look at the status messages. It will give you a clue as to why things are failing to upgrade. Without those messages it would not be time efficient to guess the cause as there can be many many causes.
[Nexus 7 (2013) General] sean67854:
Would it be possible to just rename the debuggerd.backup file, or do I have to flash the replacement?
[Nexus 7 (2013) General] Melarsa:
I know you posted this for JSS15R awhile ago, but I just wanted to let you know that this was the ONLY way I was able to keep my data and successfully update from 4.4 to 4.4.2 after a failed update. The OTA failed, ADB sideloading the update failed, using various custom recoveries and the stock recovery made no difference, nothing I Googled worked. I kept seeing:

"E:Error in /tmp/update.zip

(Status 7)

Installation aborted."

Then I was stuck in a bootloop and figuring I'd be forced to completely wipe everything and start from stock until I found this guide.

I applied the same idea of making a batch file without the -w command for the factory image of KRT15S, flashed it, and was finally able to boot. Then I ADB sideloaded the 4.4.2 update.zip and was successfully able to update to KOT49H. Thank you so much, you saved me the hassle of losing my data!
[Nexus 7 (2013) General] lespaulman67:
Is this update in the USA and is people getting it yet? What part of the states. Please post and let us know when and where and how it did for you. Let us know if you kept the ts20-lock.img or Unlocked it before install.

I am in IL. I don't see it yet.
[Nexus 7 (2013) General] oldblue910:
It's not based on region. It's totally random. The rollouts go to X% of devices per day. With phones, some have speculated that it could be random blocks of IMEI numbers, but on a WiFi-only tablet, I'm not sure. Either way, it's almost certain it has nothing to do with region.
[Nexus 7 (2013) General] Tony_YYZ:
I'm on JSS15Q with TWRP and SuperSU. I know I have to revert to the stock JSS15Q recovery for the OTA to work. In regards to SuperSU, I had originally flashed the v1.51 zip package but I updated the SuperSU app via the Play Store to the latest version. Does that mean I am in the clear or do I have to manually flash a zip package of v1.55 or later for it to not fail at the end of the OTA upgrade?
[Nexus 7 (2013) General] oTeMpLo:
.... deleted...
[Nexus 7 (2013) General] ldkud50:
Version 1.55 and above will update. After update though, SuperSU said binary wasn't installed. I went to TWRP flashed the latest SuperSU 1.65 zip and fixed permissions under advanced and all was good.
[Nexus 7 (2013) General] Tony_YYZ:
So I do indeed have to go and manually flash the latest version of SuperSU before attempting the OTA?
[Nexus 7 (2013) General] EricGarcia:
Stock ROM with TWRP 2.6.1.1

So I flashed the JSS15Q->JSS15R OTA using TWRP 2.6.1.1.

It flashed successfully but I didn't wipe cache (am I suppose to?) after that and hit reboot system and then it gave me a notice that I lost root access and to swipe to fix it and I did.

It rebooted and I opened root checker and it said I wasn't rooted. I then downloaded SuperSU 1.6.5.zip from Chainfire and flashed it in TWRP. Didn't wipe cache again. Rebooted system but didn't get swipe to fix root access message.

My two questions are, first, I now have root access again but when I open GooManager or Root Checker I get a message about “has been granted superuser permissions for an interactive shell" and I never remember seeing that message before I flashed the OTA.

The reason I'm asking about the first question is if it might have anything to do with the following because now when I boot into TWRP and go to reboot system I get that message again that I lost root access and to swipe to fix. I swipe to fix and it reboots and I still have root access when check again.

I'm just curious why is TWRP telling me I'm not rooted and for it to swipe to fix root access when I'm already rooted? Is it because I didn't wipe cache after the flashing processes?

Apologies for the lengthy description. Just wanted to be as detailed as possible.
[Nexus 7 (2013) General] ldkud50:
If you have SuperSU 1.55+ and its working you don't have to manually update first. I am saying I had to manually flash after update because it didn't keep root because SuperSU said the binary wasn't install. Said perform manual root process. I think when you go to the PlayStore Chainfire specifically states a manual root has to be done with 4.3.

So just flash SuperSU in recovery fix permissions.

Hope this helps. Its just what I did and everything seems to be fine.
[Nexus 7 (2013) General] Tony_YYZ:
Sorry, I think there is some confusion. I had originally flashed SuperSU 1.51 in Recovery but have since updated the SuperSU app from the Play Store to the latest version. Are the two things one in the same? Or are they separate and I have to go and manually flash 1.55 or later regardless of the SuperSU app version?

Hope that cleared it up.
[Nexus 7 (2013) General] ldkud50:
If you are updated to the latest SuperSU your done, just update to JSS15R. Then flash SuperSU1.65 after. Because the update breaks root .
[Nexus 7 (2013) General] MattDN93:
For those wanting the update and not seeing it (I haven't had success with this OTA due to the early rollout stage; but this helped me "see" JSS15Q) try clearing the data for "Google Services Framework" [DON'T FC THE APP]. You'll see in the OTA screen say last update was 01/01/1970. Check for updates. If nothing, repeat (possibly 4+ times) and that may increase your chance. I don't know the logic behind this but when I tried this with JSS15Q the update didn't show automatically, but picked up when I followed these steps.

On another topic, there's issues with "pil_gss" wakelocks draining battery/causing heavier battery use being lobbed around in the Google Product Forums, any word on if this update fixes that?
[Nexus 7 (2013) General] Gorgtech:
I´ve also installed the update and upgraded the bootloader; no more multitouch issues for me too :good:
[Nexus 7 (2013) General] hoodie666:
Dont generally have problems in daily use especially because i always hold the tablet but still can see lots of twitching on YAMTT if tablet is on a surface.

JSS15R with no ts-xx files ever installed
[Nexus 7 (2013) General] Muikkuman:
Hmm didn't work for me.
[Nexus 7 (2013) General] DT84:
Removed and add back your Google account after updated or you'll have some problems using Google apps.
[Nexus 7 (2013) General] EricGarcia:
Did you wipe cache after flashing the OTA and SuperSU 1.65? What do you mean “fixed permissions under advanced"?
[Nexus 7 (2013) General] habylab:
You really should update TWRP!
[Nexus 7 (2013) General] iorikun:
Sorry for a newbie question, but how do you update bootloader exactly? I have unlocked bootloader with TWRP. I was going to update via factory OTA image and reapply the SU update.
[Nexus 7 (2013) General] bso44:
Just flash this zip in recovery:

http://xdaforums.com/showpost.php?p=45667262&postcount=2
[Nexus 7 (2013) General] iorikun:
Thanks a bunch!
[Nexus 7 (2013) General] sfhub:
Bootloader gets updated automatically when you install the ota.
[Nexus 7 (2013) General] ldkud50:
I did wipe cache.

---------- Post added at 05:37 PM ---------- Previous post was at 05:32 PM ----------

I went to advanced in TWRP and clicked fix permissions and I did wipe cache.
[Nexus 7 (2013) General] habylab:
Refused to flash on mine, as far as in aware I'm on the latest supersu, not sure why the binary failed to load, or whatever the log said.

Sent from my maybe one day to be CM i9300. That day won't come unless the camera improves!
[Nexus 7 (2013) General] sfhub:
If you can post the exact message it would be easier to diagnose
[Nexus 7 (2013) General] EricGarcia:
Yep that fixed the TWRP issue. I no longer get “swipe to fix root access" when reboot system in TWRP.
[Nexus 7 (2013) General] habylab:
Of course! I get two:

assert failed: getprop for both ro.product.device and ro.build.product for both == flo.

error executing updater binary in zip '/sdcard dow (cut off I assume, end of line)

I tried flashing the latest SuperSU script to see if that helped, non. Even flashed the new bootloader but nothing. Might just wait for OTA.

Glad I could help!

Sent from my 6 core baby, using Chrome.
[Nexus 7 (2013) General] May82:
I was on 15Q with ts-10

- Used the boot-ts-unlock.img

- Sideloaded the update

- rebooted a couple times

No luck. touch screen is fine when held (outside of a case) but is jumpy and has a few ghost touches if holding two points on the same axis while in a case or flat on a desk. Back to TS-10 for me I guess. I really wish they could get this fixed. Very aggravating.
[Nexus 7 (2013) General] sfhub:
Are you on LTE n7 or using deb version of recovery?

It is complaining that it doesn't think you are running WiFi n7.2 based on the build.prop included with the recovery you are running.
[Nexus 7 (2013) General] sfhub:
That is unfortunate. There was some hope the fix was implemented outside of the touchscreen firmware because the touchscreen firmware didn't change between JSS15Q and JSS15R so the earlier positive outcomes could not have been from an updated touchscreen firmware.
[Nexus 7 (2013) General] frelnik:
Unfortunately I have to echo what others are saying. The update did not improve my touchscreen issues when the device is sitting on a surface and not held in my hand. I continue to have trouble with two finger operation (especially in the Maps app).
[Nexus 7 (2013) General] AnarchoXen:
Flashed using the zip in the other section with no issues. Why wait?
[Nexus 7 (2013) General] danvee:
Update had no effect on touch issues or freezing, but has introduced RR when 'awake'. Previously only occasionally when asleep.

Chrome rolled back and disabled. GPS off.

Curious...
[Nexus 7 (2013) General] habylab:
I think Franco's kernel may be at fault, latest update has a hybrid diskram. Will change to older kernel to test.