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.
Hey guys, I have LTE enabled so OTA updates do not work. I need some help with my options for flashing.
In the past, I flashed my Nexus 4 with MinimalABD, taking the ROM apart and flashing over certain folders to keep my data intact. I don't know if that method will work on 4.4. I also don't know what we need to do to get LTE on this latest update (as in, if anything has changed.)
Could someone help me? It's really just the constant "You have an update" that is bugging me. I don't think anything fun happens in this latest OTA. Hopefully this is the last OTA for me as I want the predicted new Nexus come December!! And it would be great to get a Nexus phone I can actually get OTA updates for without issue!!
I haven't backed my data up in a while, I probably should do that too. (Also, regaining root after a flash, anyone have a reliable method for that? And for tethering on T-Mobile.)
thehyecircus said:
Hey guys, I have LTE enabled so OTA updates do not work. I need some help with my options for flashing.
In the past, I flashed my Nexus 4 with MinimalABD, taking the ROM apart and flashing over certain folders to keep my data intact. I don't know if that method will work on 4.4. I also don't know what we need to do to get LTE on this latest update (as in, if anything has changed.)
Click to expand...
Click to collapse
In case:
a. the bootloader is unlocked and you can start Nexus 4/7 in fastboot mode
b. N4/7 is connected to a PC
c. you can get response from N4/7 with a command in a Dosbox: fastboot devices
You could flash the update manually.
Download the required factory image and the Nexus Root Toolkit (NRT) of Wugfresh.
Install NRT and extract the required factory image in a directory of your choice.
In that directory you need the files: fastboot.exe - AdbWinApi.dll - AdbWinUsbApi.dll
Copy those files from the NRT.
From the extracted factory image you need the required zip file extracted from the factory image.
Example Nexus 4: image-occam-ktu84p.zip
Connect the phone to USB. Use NRT to put the phone in fastboot mode.
Open the above directory in a dosbox as administrator.
Type the required command to update.
For N4: fastboot update image-occam-ktu8p.zip
Remark 1.
After that root is gone. Reroot with the NRT of wugfresh.
Remark 2, flashing the radio.
When you extract the factory image for N4 there is also an update image for the radio.
You can flash the N4 with: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.03.img
But on my N4 the LTE tricks does not work. For LTE you need an older version of the radio image.
Remark 3.
I used this manually method to avoid the hassle of backup and restore.
Hello guys,
I own a nexus 4
i would require help in ota issues.
previously when google had launched the 4.4.4 update
my device showed me an error of code 7
the android with exclamatory mark stating update failed
then i had contacted google regarding the issue they told me to flash factory images
but inspite of backup i lost few data
now the same thing is happening with 5.0
i got notification saying update avilable and after download and install twice i get an error code 7
in 4.4.4 issue my device was non rooted with boot loader unlocked
in 5.0 issue my device is rooted with boot loader unlocked
i am on completely stock android only rooted no tweaks or changes to the rom
now if i flash factory image i loose my data for sure.
if at all i backup entire rom in cwm custom recovery
then move that .zip created by backup to my pc
then flash factory image
custom recovery then restore data
will it work
i am very concerned about my phone data as well as the ota
please guys need help
thanks and regards
-AK
hey i had also some error 7 problem.
this helped me.
http://forum.xda-developers.com/showpost.php?p=56916654&postcount=3344
The link says
I resolved the fingerprint Problem (set_metadata_recursive: some changes failed) by flashing the factory Images without the Wipe command
1. Download Factory IMG for Android 5.0 for*Nexus*4
2. Unpack the file and open the folder (make sure the zip file is in the same folder as your ADB/Fastboot folder)
3. Open the flash-all with an EDITOR (flash-all.sh for Linux or Mac flash-all.bat for Windows
4. Remove the -w option from the last line: The line should now read:*
fastboot update image-occam-lrx21t.zip
5. Reboot your phone to the bootloader and execute the flash-all file
But if I edit -w
And flash it
Will it remove all my data
Or its just a kind of ota
Also
Yesterday I tried to backup from twrp
And flashed all of lollipop without editing
Then flashed twrp and selected to restore only data
When rebooted it got into boot loop
Thanks bro fixed the issue with the help of that link without losing my data
Hi,
Currently on build LRX21P. (5.0 for the 2012 Nexus 7 wifi)
I recently received a notification that an OTA update to 5.0.2 was available.
When I tried to install it, the tablet would reboot into TWRP and stay there.
It looks like the update installed a file /cache/a6645eee89af34f58db74f6a1ad93fe400fcfc7b.signed-nakasi-LRX22G-from-LRX21P.a6645eee.zip but TWRP can't install it. I have attached the logfile from TWRP.
Any suggestions? I would much rather do an upgrade than wipe in order to install the 5.0.2 image.
Thanks!
Download the factory image from Google's website. Extract the system.img file from the zip. Use fastboot to flash: "fastboot flash system system.img". It worked fine for me.
On other devices I have been advised to NOT take an OTA if I had a custom recovery, even with a stock ROM. So one had to flash back to stock recovery before taking the OTA.
I have been trying to see if the same is true for the Nexus 7 with Android 5.x, but haven't found a definitive answer yet.
jbaumert said:
Download the factory image from Google's website. Extract the system.img file from the zip. Use fastboot to flash: "fastboot flash system system.img". It worked fine for me.
Click to expand...
Click to collapse
That worked perfectly. (used WUG toolkit to flash).
Thanks!
Hi, I have a Nexus 7 2012 wifi nakasi & my 5.1.1 OTA just landed. As my Nexus is rooted using CF-auto-root & had a TWRP 2.8.5.1 recovery flashed, I fastboot flashed the recovery.img from the 5.1.0 archive & then clicked the button to install the OTA.
It gets half way through, then just says "error". How do I get it to be more informative & could I fix it by just flashing the system partition from my 5.1.0 archive before running the OTA, then re-rooting & re-flashing TWRP?
Thanks
Had the same issue.... Just flashed the update without wiping the use info, so far seems to have worked... Not yet noticing much improvement though so don't get to excited.... Will keep watching it to see if it still crashes in sleep mode whilst sitting in the desk doc/charger...
Sent from my Nexus 7 using XDA Free mobile app
---------- Post added at 07:40 AM ---------- Previous post was at 07:32 AM ----------
Update: loads of system & none system apps still hanging and force closing some without the usual report/wait/OK option
So far:
- Google map
- Android System
- Facebook
- BBC iPlayer
- Chrome
Probably worth a full wipe and re flash to remove any gremlins.....
Sent from my Nexus 7 using XDA Free mobile app
FIXED
JustinSB said:
It gets half way through, then just says "error". How do I get it to be more informative & could I fix it by just flashing the system partition from my 5.1.0 archive before running the OTA, then re-rooting & re-flashing TWRP?
Click to expand...
Click to collapse
I just flashed the system.img from my 5.1.0 archive (the recovery had already been flashed from the first time I tried it), waited half an hour for the OTA to flag up again & it all worked perfectly & upgraded exactly as it should. I haven't tried to root it again yet, as I want to see if it makes a difference.
So that's it, if your Nexus 7 2012 wifi won't let you install the 5.1.1 OTA, flash system.img & recovery.img from the 5.1.0 archive & you will be good to go, with all of your existing software, settings & data still intact. Naturally, you will need to re-root it though.
I flashed the 5.1.1 recovery, boot, and system images and then did a full wipe in recovery. Upon booting into the system, I was offered to restore my previous apps and data which all worked well but took a while to download and install the apps. I had to spend some time setting up the screens but 5.1.1 is running very well (better than 5.1) and I've since flashed twrp to get root. I do believe the wipe is important to get the best performance from the update.
I agree with the poster above me. Not wiping the device, cobbling together some unapproved update scheme pulled out of your ass, then complaining the performance sucks is just plain stupid. Do it right, and it will run butter smooth. But hey, I'm perfectly OK with snapping up several N7's DIRT CHEAP when all the idiots who can't follow instructions start dumping them on eBay and Craigslist thinking they're "broken". I have two cars that could use an in-dash install.
JustinSB said:
Hi, I have a Nexus 7 2012 wifi nakasi & my 5.1.1 OTA just landed. As my Nexus is rooted using CF-auto-root & had a TWRP 2.8.5.1 recovery flashed, I fastboot flashed the recovery.img from the 5.1.0 archive & then clicked the button to install the OTA.
It gets half way through, then just says "error". How do I get it to be more informative & could I fix it by just flashing the system partition from my 5.1.0 archive before running the OTA, then re-rooting & re-flashing TWRP?
Thanks
Click to expand...
Click to collapse
JustinSB,
Since you've already flashed your ROM's stock recovery, I *think* the problem you're encountering is the same one I had when I moved from 5.0.1 to 5.1: The rooting procedure you're using installs a non-stock kernel, which resides in the boot.img partition and is detected in the pre-flash checking phase of things in the OTA update.
If it were me, and I wanted to save a significant amount of time on the update (i.e. keep my userdata and bootloader partitions the same), I'd download the 5.1.1 image archive, uncompress/untar/unzip all the archives, and do the steps outlined here. They involve wiping the cache, recovery, boot, and system partitions and flashing the latter three with the updated images. Definitely do not fail to do any of those steps. Fwiw, and as I note later in that thread, I didn't re-flash the bootloader as it's the same in both ROMs.
All I did to finalize things was to boot to twrp via fastboot and generate a Nandroid back up, and then re-root using the CF-Auto-Root procedure. Afterwards I was set and experienced no particular system slowdowns. The whole process took about 15 minutes, including waiting for the dalvik-cache to reinitialize. I typically do not flash twrp, I just boot to it from fastboot as needed.
As a poster has pointed out in his non-diplomatic way, this is not the recommended path to updating, so if you encounter problems going this route, you can always do the full reset thing and re-load all of your userdata from a back up as a second option.
Which ever path you decide to follow, I wish you good luck.
cheers,
john
Well, I guess I'm going to do the unthinkable and reply to my own post to say that I've just followed the procedure I described above, this time to update from 5.1 to 5.1.1. It also took a total of 15 minutes with the longest portion of that time taken by the dalvik-cache reinitializing during the first reboot.
Good luck to you, OP. I hope that you upgrade goes as smoothly.
cheers,
john