fastboot flash the factory image and install ota files.while restarted,the system encountered a error. manual restarted the system ver not 4.2.1.
it was still the original version
re-download the files, and do it again ...
Or download the tool kit in the original dev section and install the factory with that.
Little looking around you will find your answers.
Watcher64 said:
re-download the files, and do it again ...
Or download the tool kit in the original dev section and install the factory with that.
Little looking around you will find your answers.
Click to expand...
Click to collapse
May I ask you something. Jean-Baptiste Queru posted on a google+ group:
"If your bootloader is unlocked, you can unzip
image-mantaray-jop40c.zip and fastboot flash system system.img, which
won't erase your data."
Does this mean that if I have android 4.2 on my device and it's failingto update to the 4.2.1, I just have to fastboot flash system.img? And if so, how to?
Code:
KRT16S Factory Image available in Downloads section (below)
KRT16S OTA available in Downloads section (below)
As first mentioned by mdamaged in this post KRT16S "KitKat" is rolling out now.
I did not want to hijack that thread, but wanted to have a simple continuously updated first post that summarizes experiences and consolidates resources like OTA URLs, Factory Image flashing, etc.
You will soon be seeing comments from folks about how KRT16S affects the remaining Multi-touch and Random freeze/reboot issues on google product forums:
Google Nexus 7 product forum
KRT16S touchscreen experiences (near the end of thread)
KRT16S touchscreen experiences (2nd thread)
Mixed improvement with WiFi turned on and Bluetooth keyboards
pil-gss wakelock issue appears fixed
If you need to refer to the old KRT16O thread, it is here.
Initial impressions
Problems and/or fixes
Fix for SMS in deb/LTE 4.4 KRT16S available here (thx maconsultant)
Fix for WhatsApp with ART available here (thx MasterJam882)
Fix for BetterBatteryStats - install 1.15 available here
Specific to KRT16S
Audio seems to be improved, immediately noticeable in audio feedback for taps
Touchscreen software same as KRT16O
Bootloader same as KRT16O (4.01)
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
Magnetic smart wake when wifi lost or deep sleeps appears to be fixed
Fix is in 4.01 bootloader - not necessary to flash 4.4 KitKat ROM (thx meekrawb)
Some bluetooth keyboard improvements
GPS/pil-gss wakelock issues appears to be fixed
New touchscreen software.
Mixed results, will likely depend on screen, some fixed, some not, improvement from JSS15R
ghost touches with aligned fingers mostly gone
stuck touches seem to be gone or greatly reduced
may still have missed touches
may still have slight jitters with aligned finger dragging
Does NOT include GEL (Google Experience Launcher)
install extracted N5 GEL and new Google Search if you want the new experience (thx jxr94)
use Nova Launcher if you want transparent status bars
Root can be installed in the same ways as 4.3
If you use NRT (Nexus Root Toolkit) follow this procedure (thx ruggie0)
Logistics (only for people trying to downgrade or mix/match rom/kernels)
You cannot "dirty" flash from 4.4 rom/kernel back to 4.3 rom/kernel, you'll need to wipe data/factory reset
4.3 kernels will not boot 4.4 rom
New FLO-04.01 bootloader.
New boot animation, sounds, icons.
New Easter Egg (thx magnumlove)
settings->about tablet->android version (rapidly tap 4 times)
Tap "K" a few times to make it spin, then see the final prize
New ART (Android Run Time) replacement for Dalvik VM
Discussion here
Enable using settings->developer options->select runtime
Apps should be odexed (stock is odexed)
First boot will take a while (possibly 15+ minutes)
New cloud/network print options
The new tap and pay setting only shows up if you already have NFC enabled. (thx albundy2010)
To get tap and pay working you need to get the N5 version of Wallet (thx ruggie0)
Quick benchmark1, benchmark2 of 4.4 and stock Dalvik (thx Vanillalite)
Quick benchmark1, benchmark2 of 4.4 and ART (thx Vanillalite)
Change summary:
KRT16O(4.4_r1.1)->KRT16S(4.4_r1.2) - AOSP Changelog
Bootloader version: FLO-04.01
Android version: 4.4
Build/ROM version: KRT16S
Kernel version: 3.4.0-gb0eacf3 / Wed Oct 23 17:41:58 PDT 2013
Mini guides:
adb sideload (install OTA using stock recovery, no need to unlock, preserves user data)
flashing factory images (factory image restore, must be unlocked, option to preserve or wipe user data)
restore stock recovery (if you've installed custom recovery and want to go back to stock)
installing OTA-compatible root/SuperSU (will install SuperSU and fix so that it works with OTAs)
entering safe mode, bootloader, stock recovery (button press sequence can be tricky for fallen android)
Universal ADB drivers (use these if you have trouble with adb recognizing device)
Downloads:
KRT16S
KRT16S Factory Image - flo/WiFi (thanks azrash)
KRT16S Factory Image - deb/LTE (thanks azrash)
Source: pure stock
Format: flash in fastboot/bootloader
Guide: flashing factory images
Caveats:
no existing version requirements
requires unlocked bootloader
options to wipe or preserve user data
JSS15R->KRT16S OTA - flo/WiFi (thanks mokomull)
JSS15Q->KRT16S OTA - flo/WiFi (thanks EthanFirst)
JSS15J->KRT16S OTA - flo/WiFi (thanks EthanFirst)
JWR66N->KRT16S OTA - flo/WiFi (thanks TheManii)
KRT16O->KRT16S OTA - flo/WiFi (thanks wilsonlam97)
JLS36I->KRT16S OTA - deb/LTE (thanks scoof2)
JLS36C->KRT16S OTA - deb/LTE (thanks EthanFirst)
JSS15J->KRT16S OTA - deb/LTE (thanks TheManii)
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
KRT16S repackaged TWRP/CWM-flashable - flo/WiFi (thanks scrosler)
Source: slightly modified stock
Format: flash as regular update.zip in TWRP/CWM
Caveats:
no existing version requirements
this is stock functionality but not pure stock binaries so might not 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
Stock kernel/recovery (unzip and flash via fastboot/bootloader)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
flo/WiFi
stock JWR66N kernel
stock JSS15J kernel
stock JSS15J recovery
stock JSS15Q kernel
stock JSS15Q recovery
stock JSS15R kernel
stock JSS15R recovery
stock KRT16O kernel
stock KRT16O recovery
stock KRT16S kernel
stock KRT16S recovery
deb/LTE
stock KRT16O kernel
stock KRT16O recovery
stock KRT16S kernel
stock KRT16S recovery
Bootloader - flo/deb (unzip and flash via fastboot/bootloader)
fastboot flash bootloader [filename]
Bootloader v3.14
Bootloader v3.15
Bootloader v4.01
Root/SuperSU
UPDATE-SuperSU-v1.75.zip - install in TWRP or CWM for root (recommended for 4.4)
UPDATE-SuperSU-v1.55.zip - install in TWRP or CWM for root
Custom Recovery (unzip and flash via fastboot/bootloader)
fastboot flash recovery twrp.img
TWRP 2.6.3.1 (recommended for 4.4)
Stock missing/modified KRT16S files
flo/WiFi
update-KRT16S-debuggerd.zip
update-KRT16S-build.prop.zip
update-KRT16S-BasicDreams.zip
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
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
Quick boot app force closes for me now. Anyone else?
AeCeEm said:
Quick boot app force closes for me now. Anyone else?
Click to expand...
Click to collapse
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.
sfhub said:
WORK IN PROGRESS - Placeholder
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:
flo/WiFi
deb/LTE
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, 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
Click to expand...
Click to collapse
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
xdhall said:
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
Click to expand...
Click to collapse
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
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?
jhom52 said:
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?
Click to expand...
Click to collapse
Are you flashing or sideloading the OTA zip?
Sent from my Nexus 7 using Tapatalk 4
jhom52 said:
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?
Click to expand...
Click to collapse
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.
sfhub said:
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.
Click to expand...
Click to collapse
Worked!! I can always count on a sfhub posting for the right info. Thanks!!!
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
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?
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.
neo5468 said:
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?
Click to expand...
Click to collapse
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
Has anyone with Deb got the 3.4 MB OTA?
Sent from my Nexus 7 using Tapatalk
Sleepy! said:
Has anyone with Deb got the 3.4 MB OTA?
Click to expand...
Click to collapse
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.
sfhub said:
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.
Click to expand...
Click to collapse
Deb: Forever Alone.
Sent from my Nexus 7 using Tapatalk
neo5468 said:
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?
Click to expand...
Click to collapse
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
lomonic said:
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.
Click to expand...
Click to collapse
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.
I tried to install the September security update for Android oreo using flash fire and the OTA I downloaded from Google's site. But when I load up the OTA, I see a primary partitions greyed out, and like 5 secondary partitions. I do not see a vendor, or system, or recovery partitions. I do get a modem and boot partition. Has anyone encountered this before?
Imgur like below
https://imgur.com/a/zt8RJ
Bump.
I'm still having this problem and I can't update or add the latest security update. I may be flashing back to stock soon if no one can help me out.
clifford64 said:
Bump. I'm still having this problem and I can't update or add the latest security update. I may be flashing back to stock soon if no one can help me out.
Click to expand...
Click to collapse
I've been using FF on 3 devices every month since it came out (beta) but have always used the full Google image. I've never used an OTA, and have never had an issue. Only flash Boot, System and Vendor. Note the bootloader and modem (radio) versions on your device and compare with what is in the full image. You'll need to flash those separately with fastboot if there is a new version. For example the October security update contained a new bootloader (v3.75). I normally do (and recommend) a full wipe between major versions but since you are already running 8.0, just flash the full image and you'll be good. :good:
That's what I am talking about though. I have downloaded the factory image from the Google developer website and when I got to flash it, that is what I see. I don't get the normal partitions, I get a bunch of secondary ones.
clifford64 said:
That's what I am talking about though. I have downloaded the factory image from the Google developer website and when I got to flash it, that is what I see. I don't get the normal partitions, I get a bunch of secondary ones.
Click to expand...
Click to collapse
In your OP you stated you were using the OTA image, not the full image which is completely different. Load the full factory image in FF using the "Flash Firmware Package" option in the menu. Only select Boot, System and Vendor.
I am sorry for being confusing, but I've basically done what you said in the previous post and the image I posted in my OP is the result. That I'd what happens why I try to update with the factory image in FF.
clifford64 said:
I am sorry for being confusing, but I've basically done what you said in the previous post and the image I posted in my OP is the result. That I'd what happens why I try to update with the factory image in FF.
Click to expand...
Click to collapse
Don't see how this is possible because FF is reading and displaying the partitions in the image file, not reporting available partitions on your device. It parses the image file and then displays the partitions for you to select or deselect. There is a separate menu function to view partitions on the device. If you have confirmed the full image file CRC checksum is correct (not corrupted), then it sounds like it is time to fully wipe your device and reinstall Oreo. Follow the instructions on the same page you d/l the image from. Personally I would fastboot format System, Userdata and Cache partitions before I reloaded the firmware. As always backup your data before attempting this.