yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Active Android Development] Tommyboy2k:
Looking for a working master patch link so I can get wifi working with hyper drive18.1 any help would be appreciated. ...
[Galaxy S 4 Active Android Development] my-blue-snog-box:
Is Hyperdrive 18.1 a 4.4.2 base? If so, try this.
[Galaxy S 4 Active Android Development] Tommyboy2k:
Thank you very much! !!
[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 Google's servers:

KRT16S Factory Image - flo/WiFi - https://dl.google.com/dl/android/aosp/razor-krt16s-factory-7235eb0d.tgz

KRT16S Factory Image - deb/LTE - https://dl.google.com/dl/android/aosp/razorg-krt16s-factory-bd6c9241.tgz

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-krt16s/razorg-krt16s directory from the .tar

unzip the addon to the appropriate directory

flo/WiFi - razor-krt16s-addon.zip into the razor-krt16s directory (from previous step)

deb/LTE - razorg-krt16s-addon.zip into the razorg-krt16s 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 or naked drivers from this post

in command prompt in the razor-krt16s/razorg-krt16s 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, try shutting down the tablet then:

if running custom recovery, boot to recovery, perform wipe cache / dalvik-cache

if that doesn't help or on stock recovery

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] sfhub:
So far

Initial impressions

Touchscreen software same as KRT16O

Kernel same as KRT16O

Recovery same as KRT16O

Changes to nfc (tap&pay?), camera, audio, drm, google backup, TTS (text-to-speech), facelock, webview/chromium, qualcomm sensors
[Nexus 7 (2013) General] AeCeEm:
Quick boot app force closes for me now. Anyone else?
[Nexus 7 (2013) General] sfhub:
Works for me.

Since you probably reinstalled SuperSU, the permissions are probably messed up.

Go to app drawer, tap on SuperSU icon and exit.

Then try QuickBoot again.

If it still doesn't work, uninstall/reinstall QuickBoot.
[Nexus 7 (2013) General] xdhall:
Excellent guide. I would suggest one change though. Users encountering instability, before jumping straight to a factory reset, should power down their device and let it sit for a couple of minutes. Then reboot into recovery and wipe your cache and dalvik cache.

That move fixes a large proportion of instability issues after a patch or flash
[Nexus 7 (2013) General] sfhub:
Thanks for the feedback, this is what it says now:

If you have issues after upgrading, try shutting down the tablet then:

if running custom recovery, boot to recovery, perform wipe cache / dalvik-cache

if that doesn't help or on stock recovery

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] jhom52:
I'm having a problem updating by TWRP my KRT160 stock and rooted N7 with the KRT16s OTA. While flashing the OTA in TWRP, I am getting an error indicating that system/bin/debuggerd has unexpected content. Any advice in solving the problem?
[Nexus 7 (2013) General] LoopDoGG79:
Are you flashing or sideloading the OTA zip?
[Nexus 7 (2013) General] sfhub:
Added to first post:

Stock missing/modified KRT16S files

flo/WiFi

update-KRT16S-debuggerd.zip

You can either run the update.zip in TWRP/CWM or hand extract the file and place in /system/bin

Don't worry that it is KRT16S version, it will pass the OTA file check and allow the OTA update to complete.
[Nexus 7 (2013) General] jhom52:
Worked!! I can always count on a sfhub posting for the right info. Thanks!!!
[Nexus 7 (2013) General] sfhub:
Added to first post:

KRT16S repackaged TWRP/CWM-flashable - flo/WiFi (thanks scrosler)

Source: slightly modified stock

Format: flash as regular update.zip in TWRP/CWM

Caveats:

this is stock functionality but not pure stock binaries so won't work with future OTAs

bootloader 4.01 flash is a SEPARATE install (needed for magnetic smart wake fix)

this is pre-rooted with init.d support

odexed and deodexed versions

preserves user data
[Nexus 7 (2013) General] neo5468:
I updated to this 3.4 mb update, and now lost TWRP and root. When I went into recovery, there was a green fallen android with red exclamation point. And it freezed whole device for like 3min. How do i get recovery back so I can root?
[Nexus 7 (2013) General] fr33styl3r7:
Hello i just saw the update on my tablet (Greece).

Here is the link in case anyone wants to apply the OTA only.

http://android.clients.google.com/p....signed-razor-KRT16S-from-KRT16O.67b84ced.zip

edit: nvm, i didn't see it was posted already.
[Nexus 7 (2013) General] sfhub:
The android fallen down is stock recovery. You can get the recovery menu by press/hold Power, press/release VolUp, release Power.

To get TWRP back just boot into bootloader (Power+VolDown)

Then in a command prompt type

fastboot flash recovery twrp.img
[Nexus 7 (2013) General] Sleepy!:
Has anyone with Deb got the 3.4 MB OTA?
[Nexus 7 (2013) General] sfhub:
So far, no one has posted receiving any Kit Kat OTAs (KRT16O, KRT16S) for deb.

Just the factory image is available in the first post.
[Nexus 7 (2013) General] Sleepy!:
Deb: Forever Alone. :(
[Nexus 7 (2013) General] lomonic:
Same here. I have TWRP 2630 and SuperSU 1.69 and thought the OTA would work when i received the OTA even prior to checking the forums. I went ahead and apply it and it went well, rebooted back into android and i quickly realised my Root is gone and TWRP custom recovery too.

So just rebooted to bootloader, flash the custom recovery and install supersu again and voila!

No significant observation with this release so far. Guess it's just a minor update
[Nexus 7 (2013) General] sfhub:
Every OTA will behave this way.

If you'd like to simplify the upgrade, don't accept the automatic OTA.

Boot into custom recovery, install the OTA manually, then immediately after that (prior to reboot) install SuperSU.

Upon reboot you'll have root and your custom recovery will be preserved.
[Nexus 7 (2013) General] neo5468:
I think that something is seriously wrong. It doesnt matter if i hold power+vol up, or power+vol down. It does the same thing. A green fallen android with red exclamation point in the middle of the screen. No stock recovery, no bootloader, nothing. I cant select anything because whole screen is black. Only green fallen android with red exclamation point in the middle of that black screen. All I can do is power off the device, and turn it on normally. Device turns on without the problem. Im actually typing this from my nexus. But i cant boot into recovery or bootloader.

Before this 3.4 mb update, everything worked fine with twrp and root. I also had unloocked bootloader, but dunno if I have now. I freaking knew I shouldnt download via OTA, but manually in twrp. Im so stupid. What should I do now.
[Nexus 7 (2013) General] Omar04:
Once again.... That is the stock recovery just hold power+volume up if I remember correctly.
[Nexus 7 (2013) General] daydreamer1204:
Thanks a lot for this great guide...I updated my Nexus 7 LTE to krt16o following your guide too.

Anyway, am on stock recovery & rooted...will I lose root if I update to krt16s by flashing the factory image with the "flash-all-nowipe" option?
[Nexus 7 (2013) General] neo5468:
Okay I somehow managed to get into bootloader and flash TWRP again. So I installed SuperSU 1.55 and now everything works. I have TWRP and root now !
[Nexus 7 (2013) General] fkfs9:
I tried to flash the ota for flo in twrp and it prompted failure due to unexpected content in system/framework/core.odex. E:error executing updater binary in zip. Anyone got this problem?
[Nexus 7 (2013) General] sfhub:
The fallen android is stock recovery, the just have an image overlaid over the menu.

In this EXACT order, press/hold Power, press/release VolUp, release Power

This will show the stock recovery menu.

As to why this happened, when you flash the ota, it resets the permissions on all files (ie root is disabled) and upon first boot, it installs stock recovery.

If you'd like to avoid this in the future, install the ota update.zip using twrp, then immediately after (prior tobreboot) install SuperSu update.zip. This will preserve root and preserve twrp.

BTW this is covered in the guide for flashing otas in the first post.
[Nexus 7 (2013) General] sfhub:
You will lose root but will keep your user data.

Factory images completely overwrite your /system directory so the root files are overwritten.

Simply boot into bootloader (power+voldown)

Then in command prompt type

fastboot boot twrp.img

Then choose install and select the supersu update.zip

Basically just reinstall SuperSU
[Nexus 7 (2013) General] sfhub:
You've probably installed some tweak that modified a system file.

If you restore the original the ota will continue.

Alternatively install the factory image from the first post and reinstall root if needed.
[Nexus 7 (2013) General] fyrmd:
In what file do I find the ota update.zip? It was automatically downloaded, and I would like to install it with twrp.

Thanks
[Nexus 7 (2013) General] sfhub:
It is in the /cache directory, or you can download from the link in the first post download section.
[Nexus 7 (2013) General] wd5gnr:
I have kit Kat installed in multi ROM. You can flash the Scott ROM using multi boot flash zip from the ROM list. You do not need to add as a new ROM.
[Nexus 7 (2013) General] xdhall:
FYI, whether or not you keep your custom recovery or root access after an OTA update depends on which custom recovery and superuser versions you have.

You can also keep root after running an auto OTA update if you are using chainfire's OTA survival mode.
[Nexus 7 (2013) General] stealthj:
If u have supersu ota preserver thingy and cwm, you don't need to do anything after ota update. My nexus is still rooted after ota
[Nexus 7 (2013) General] sfhub:
I am aware of those capabilities.

I just don't like to depend on them because they have sometimes gotten broken from release to release.
[Nexus 7 (2013) General] xdhall:
Very true.
[Nexus 7 (2013) General] sfhub:
BTW thanks for pointing out SuperSU 1.75 is out on the other thread.

Chainfire fixed that .has_su_daemon problem that was causing Koush's Superuser install to fail, so I feel comfortable recommending the 1.75 version now.
[Nexus 7 (2013) General] xdhall:
And to add to the love fest, thank YOU for being active on the general subforum. There seem to be very few active developers here, let alone users that understand the basics of linux, or even adb and fastboot. I've given you a shout out a couple of times, but it may have come off as sarcasm.
[Nexus 7 (2013) General] daydreamer1204:
thank you again for your quick reply...

anyway, did update from krt16o to krt16s factory image a few hours ago...

just wanna report that using your krt16s addon unsuccessfully as the fastboot hanged & couldn't complete the tasks (upto the point of flashing the radio)...tried for 4 times getting the same error & terminated...

after comparing the file contents, I used the fastboot.exe from your krt16o addon to replace the one in krt16s addon & tried again, bingo...flashed krt16s successfully!
[Nexus 7 (2013) General] sfhub:
My apologies. I updated the fastboot to the latest platform tools version and apparently it is now broken and complains about the system.img file being missing even though it is there.

I fixed the addon files with the older platform tools and re-tested to make sure they work.

Thanks for letting me know.
[Nexus 7 (2013) General] fyrmd:
I did this with the factory update that automatically downloaded on my N7 and everything worked great. Now on KRT16s and still rooted. The only problem, when the N7 rebooted the "System update downloaded" shows up in the notification window. How do I get rid of this?

Edit: I deleted the file from the \cache file and the notification disapeared on a reboot.

Thanks
[Nexus 7 (2013) General] sfhub:
It should eventually go away by itself assuming your version # got upgraded to KRT16S.

You can try checking for updates under settings->about tablet.

If it still won't go away you can go into /cache and remove the file and then reboot.

If it still won't go away, you open up app info for google services framework and turn off notifications.
[Nexus 7 (2013) General] icanfly77:
I was on 4.3 and upgraded to this build by side loading 16O first then allowing the OTA to update me to K1S but I just read in another thread doing this method still leaves the 160 kernel intact and in fact what I should have done is also sideload 16S as well not OTA

So what are my options now if I want the full 16S build with the new kernel? I read the 16O kernel still there is glitched?

Cheers
[Nexus 7 (2013) General] sfhub:
The kernel for KRT16S and KRT16O are the same, therefore there is nothing for you to do.
[Nexus 7 (2013) General] mayurolla:
Has anyone had any battery drain issues? I used to be able to get 2 days of my normal use out of the battery but now I have to recharge every night. Searched and searched but I could not find any battery drain reports with the 4.4 update. I noticed this with KRT16O and KRT16S.
[Nexus 7 (2013) General] myamex:
I lost root, and I flashed supersu and it's giving me no library error. How can I fix it?
[Nexus 7 (2013) General] sfhub:
When you flash or when you run?
[Nexus 7 (2013) General] JoeBruin32:
Did you fix the deb addon files? because this is happening to me
[Nexus 7 (2013) General] sfhub:
Yes I fixed at the same time but you may have downloaded earlier?
[Nexus 7 (2013) General] JoeBruin32:
I just downloaded it again and it still failed, see attached:

edit: Oh I'm stupid, I downloaded the image for the 2012 version :P lemmie try again
[Nexus 7 (2013) General] lomonic:
Yeah thanks for replying. I know that would work. was just curious to see if OTA would work well with TWRP and SuperSU 1.69 as its the first OTA i've gotten early! :D I did what you've recommended for the previous KRT16O update as i didnt get the OTA.
[Nexus 7 (2013) General] doubleho:
if i disabled some default app like keyboards,can i still sideload it?

and i also disabledbthe "back home task" bar at the bottom,does.it mean itz no longer "unmodified"

(kitkat krt16o,twrp,faux kernel)
[Nexus 7 (2013) General] sfhub:
Disabling is fine. It doesn't delete or modify the system files, just changes the configuration.

Only for this update it doesn't matter what kernel you have. Normally you'd need stock kernel.
[Nexus 7 (2013) General] JoeBruin32:
Got KRT16S working, thanks
[Nexus 7 (2013) General] doubleho:
so should i sideload it using computer or i can instantly flash it using twrp???

btw,i received the ota yesterday and i didnt install it,but then the google service drained 60% of the battery,im now forced to update...
[Nexus 7 (2013) General] sfhub:
Just copy the ota and supersu to your virtual sdcard.

Boot into twrp, install ota, and immediately (prior to rebooting) install supersu

That should be all you need to do.
[Nexus 7 (2013) General] godutch:
There is no ota for krt16o->krt16s for deb yet?
[Nexus 7 (2013) General] doubleho:
i got a "systen/build.prop has unexpected contents" while installing the ota,i added a line "qemu.hw.mainkeys=1" to disable the bottom bar,i deleted.it,reboot,made sure everything running fine and.the.bar came back.Then i boot into recovery and install the ota again,and still i hv the "systen/build.prop has unexpected contents" again.....
[Nexus 7 (2013) General] sfhub:
Added this to the first post. You can either run it in TWRP/CWM or extract the file and place it in /system by hand. Don't worry that it is the KRT16S version, it will allow the OTA to continue.

Stock missing/modified KRT16S files

flo/WiFi

update-KRT16S-build.prop.zip
[Nexus 7 (2013) General] doubleho:
thz so much,updated,first boot up didnt success,hv to boot up again now,probably unstable faux kernel on 4.4

---------- Post added at 08:59 AM ---------- Previous post was at 08:49 AM ----------

just curious,why did i delete the line i added there and.it still said it was modified??
[Nexus 7 (2013) General] bandit_knight:
Is it only me or is there a battery drain issue caused by the 'Android OS' in the latest Kitkat update?

I've had the device pretty much iddle over the last two days partly being connected to WiFi and partly being completely offline (with WiFi on). The device used 50% of its battery in 24hrs of not being used at all..

From the battery stats I can see that the biggest drainer was the 'Android OS' keeping the device awake for about 10hrs.

Is there any solution for this?
[Nexus 7 (2013) General] sfhub:
Sometimes the editor will have one space difference or an invisible newline/linefeed issue.
[Nexus 7 (2013) General] doubleho:
i hv a terrible google service drain instead....

---------- Post added at 10:07 AM ---------- Previous post was at 09:32 AM ----------

i cant flash back to stock kernel....there was an error,i downloaded the kernel (krt16s) on page 1
[Nexus 7 (2013) General] sparksd:
I'm seeing it intermittently. Difficult to run down given the loss of functionality of 3rd party battery monitor apps and wakelock detectors.
[Nexus 7 (2013) General] Dabarr:
+1... Over 30 % on each, nexus 4 and nexus 7.2

Any solutions to this?
[Nexus 7 (2013) General] unrealdtc:
Hi!

I've updated to KRT16S by side loading the OTA KRT16O, then installing the small bugfix OTA. With both KRT16O and KRT16S, I have one strange bug on the new lockscreen. If I play music (any app, including Play Music) and lock the screen, when I wake the device, the audio controls display perfectly. However, if I pause the music (using the lockscreen audio controls), turn off the screen, then wake the Nexus 7, then the audio controls don't display in the correct place (they actually display off the screen, on the right hand side in portrait mode). If I touch the screen, then they get redrawn in the correct place, and work as expected.

Any ideas?
[Nexus 7 (2013) General] xdhall:
This is your kernel playing tic tac toe. There are a couple of different ways to stop it:

1. A simple reboot can sometimes stop it

2. You might have to escalate and wipe your cache and dalvik cache

3. Escalate to factory reset

This might have happened because of an error during/discrepancy after the update, or a rogue app instigating a kernel loop. If it's due to the update, you'll be fine once you fix it. If it's a rogue app, it could come back any time that app decides to misbehave again. Checking process stats in developer settings might give you some insight (or might not).
[Nexus 7 (2013) General] petrochemicals:
Has anyone else noticed that there is no crop photo action when applying wallpapers in KRT16S. Maybe it was just me? Could someone confirm?
[Nexus 7 (2013) General] Sn00ky:
One question. When I connect to Wi-Fi does the white wi-fi icon on the notification panel mean that I am connected to Google services or the orange one? Cause I see the orange one for only 10 seconds after I connect and then it turns white. Thanks! :good:
[Nexus 7 (2013) General] doubleho:
god i dont know what is wrong,systemupdateservice is draining my battery,omg my tablet mever go to sleep according to bbs

i disable the service using romtoolbox and.reboot,the drain came back...

is it a.bug.of krt16s or i did something wrong???

this started draining when i received the ota yesterday before i flash it.using twrp
[Nexus 7 (2013) General] sfhub:
Not saying this isn't happening to you, just providing a data point. On a fresh install of KRT16S, ran Google maps for 10min last night, nothing else was run or installed. 1% after 9hours of overnight idling.

Also I had turned off background data and haven't logged into Google services.

You can probably start at the most basic state and add things back to isolate what is eating battery.
[Nexus 7 (2013) General] doubleho:
i freezes google frame.service.and there is no wakelock now,but i cant use google+......
[Nexus 7 (2013) General] sfhub:
Added deb/LTE JLS36I->KRT16O OTA to first post.

KRT16O->KRT16S OTA - flo/WiFi (thanks wilsonlam97)

JLS36I->KRT16S OTA - deb/LTE (thanks scoof2)

Source: pure stock

Format: flash with stock recovery (adb sideload) or as regular update.zip in TWRP/CWM

Guide: adb sideload

Caveats:

MUST be running respective unmodified stock (KRT16O, JLS36I, etc.)

does NOT require unlocked bootloader

if you are rooted with SuperSU 1.51 or earlier, OTA will fail near the end. See this post for explanation/fix.

if installing via twrp/cwm suggest installing SuperSU update.zip PRIOR to rebooting to preserve root and custom recovery

preserves user data
[Nexus 7 (2013) General] mokomull:
JSS15R -> KRT16S OTA url

Got the OTA update for razor (WiFi) from Jellybean to latest Kitkat (JSS15R to KRT16S). Grabbed the filename with logcat.

Filename is 7d9b309e11da82edb5373a1f59965bca89f6041f.signed-razor-KRT16S-from-JSS15R.7d9b309e.zip

Somebody will have to make this a full URL with the usual android.clients.google.com path, since I apparently can't post a URL here.
[Nexus 7 (2013) General] sfhub:
Thanks, updated the first post and gave you credit.

JSS15R->KRT16S OTA - flo/WiFi (thanks mokomull)

KRT16O->KRT16S OTA - flo/WiFi (thanks wilsonlam97)

JLS36I->KRT16S OTA - deb/LTE (thanks scoof2)

Source: pure stock

Format: flash with stock recovery (adb sideload) or as regular update.zip in TWRP/CWM

Guide: adb sideload

Caveats:

MUST be running respective unmodified stock (JSS15R, KRT16O, JLS36I, etc.)

does NOT require unlocked bootloader

if you are rooted with SuperSU 1.51 or earlier, OTA will fail near the end. See this post for explanation/fix.

if installing via twrp/cwm suggest installing SuperSU update.zip PRIOR to rebooting to preserve root and custom recovery

preserves user data
[Nexus 7 (2013) General] jmcging:
Is there an OTA for the deb/LTE that is KRT16O->KRT16S?

I've a 2013 LTE that I updated to KRT16O and can't find the OTA for it to get it to KRT16S.

Anyone?
[Nexus 7 (2013) General] sfhub:
I am sure there is, but nobody has posted it yet.
[Nexus 7 (2013) General] P.Mobile:
ok im super sorry guys but i dont want to mess my tablet up.. this is my first nexus devices.. im good with samsung & htc so im sure its not to hard... i am on android 4.3 im running clean rom.. my bootloader in unlocked.. i have twrp recovery... and i just got 4.4 OTA system update.. i kno that i cant just update cause im rooted ect... i did read this thread but dont kno what i need to flash.. what version... i need to flash a factory image and stock recovery then i can take OTA correct?? or is there another way for rooted people to update to 4.4?? also when i look in about tablet ion settings i dont see what version im on? KRT16?? please help