Flash OTA with TWRP - Nexus 4 Q&A, Help & Troubleshooting

Today I received the ota for 4.4 on my Nexus 4 and when I pressed "restart and install" it went to my custom recovery (which was flickering BTW Idk why never seen it do that before) and when I restarted it I wasn't running 4.4. I found the download location for the OTA would it be OK for me to boot into twrp and simply flash it like I would any other custom rom? Just wanted to ask before I did it.
Sent from my Nexus 4 using xda app-developers app

tsmith9191 said:
Today I received the ota for 4.4 on my Nexus 4 and when I pressed "restart and install" it went to my custom recovery (which was flickering BTW Idk why never seen it do that before) and when I restarted it I wasn't running 4.4. I found the download location for the OTA would it be OK for me to boot into twrp and simply flash it like I would any other custom rom? Just wanted to ask before I did it.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Hi, What format is it in? Unless it's in a zip format (which I doubt) then flagging it through recovery won't work I think .. I'll have a poke about and see what I can find ..
K
Sent from my Nexus 4 using Tapatalk 2

Hi can you tell me where you found the ota folder I am looking for it but can't locate it.I had the same problem as you.I think we need to be on stock recovery for it to install.
Sent from my Nexus 4 using xda app-developers app

Usually a root browser go to root and it is under the cache folder.
Sent from my Nexus 4 using xda app-developers app

krrunch said:
Hi, What format is it in? Unless it's in a zip format (which I doubt) then flagging it through recovery won't work I think .. I'll have a poke about and see what I can find ..
K
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
OK and yes it is in a zip format
Sent from my Nexus 4 using xda app-developers app

tsmith9191 said:
Today I received the ota for 4.4 on my Nexus 4 and when I pressed "restart and install" it went to my custom recovery (which was flickering BTW Idk why never seen it do that before) and when I restarted it I wasn't running 4.4. I found the download location for the OTA would it be OK for me to boot into twrp and simply flash it like I would any other custom rom? Just wanted to ask before I did it.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Depending on how the ota image is packaged you may want to take a look at this thread here
http://forum.xda-developers.com/showthread.php?t=2010312
[HOW-TO] How to flash a factory image / return to stock / unlock / root #
Hth
K
--------
:: Nexus 4 :: SlimKat :: Faux mainline ::
---------- Post added at 10:13 PM ---------- Previous post was at 10:08 PM ----------
tsmith9191 said:
OK and yes it is in a zip format
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Then I see no reason why you can't give it a go Make sure you have a backup of everything though before you go ahead .. I'm assuming you already have an unlocked bootloader ..
--------------------------------------------------------------
:: Nexus 4 :: SlimKat :: Faux mainline ::

Yes I do have an unlocked bootloader
Sent from my Nexus 4 using xda app-developers app

guys you can't flash the OTA while running custom recovery or roms. If you want to be on kitkat why not just download one of the many stock rooted roms out there? Make your life simple and for future reference like I said custom recovery will not flash OTA unless its been manipulated by someone

I tested flashing OTA using latest TWRP successfully on a 100% unmodified stock rom with no root. CWM on the other hand is not compatible for flashing OTA.
I do not recommend doing this, modifications to your /systems partition or root can cause it to fail and softbrick. I have heard people hardbricking their device too due to the bootloader getting corrupted in the process.
Make a backup before you flash.

I have installed franco kernel but I backed up the stock kernel and restored it. I have also used xposed but I uninstalled that as well as disabled and uninstalled the only module I was running which was gravity box.
Sent from my Nexus 4 using xda app-developers app

eksasol said:
I tested flashing OTA using latest TWRP successfully on a 100% unmodified stock rom with no root. CWM on the other hand is not compatible for flashing OTA.
I do not recommend doing this, modifications to your /systems partition or root can cause it to fail and softbrick. I have heard people hardbricking their device too due to the bootloader getting corrupted in the process.
Make a backup before you flash.
Click to expand...
Click to collapse
What do you recommend I do to receive the 4.4 update without losing data?
Sent from my Nexus 4 using xda app-developers app

tsmith9191 said:
What do you recommend I do to receive the 4.4 update without losing data?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Backup your data partition first, then follow either of the two guide links in my signature to flash 4.4 factory image without wiping data.

I had the same problem yesterday where the OTA made absolutely no changes (This method worked fine when I went from 4.2 to 4.3 under the same conditions; TWRP, unlocked bootloader, and stock ROM). It may be related to a new conflict with TWRP. I also had a hybrid radio installed, but I put the stock radio back in before I tried the OTA; however there were a couple changes associated with this such as build prop changes and LTE activation that I did not revert. Who knows. After searching this forum I came across a fix in the "Nexus 4 OTA Help-Desk" thread...fancy that. If you have the Android SDK installed, this is a really quick and easy fix.
1) Under "Factory Images "occam" for Nexus 4" I downloaded "4.4 (KRT16S)".
https://developers.google.com/android/nexus/images#occamkrt16s
2) I then followed these directions (WARNING: Note the instructions to remove the "-w" from the flash-all.bat file before you run it. This will retain all your existing data, apps, settings, etc.).
http://forum.xda-developers.com/showthread.php?t=2527142
3) I then installed the latest versions of TWRP (for recovery) and superuser (for root).
Now I have a fully functioning 4.4 install with no loss of data. I am holding off on the new hybrid radio until things stabilize a bit with that.

pjc123 said:
I had the same problem yesterday where the OTA made absolutely no changes (This method worked fine when I went from 4.2 to 4.3 under the same conditions; TWRP, unlocked bootloader, and stock ROM). It may be related to a new conflict with TWRP. I also had a hybrid radio installed, but I put the stock radio back in before I tried the OTA; however there were a couple changes associated with this such as build prop changes and LTE activation that I did not revert. Who knows. After searching this forum I came across a fix in the "Nexus 4 OTA Help-Desk" thread...fancy that. If you have the Android SDK installed, this is a really quick and easy fix.
1) Under "Factory Images "occam" for Nexus 4" I downloaded "4.4 (KRT16S)".
https://developers.google.com/android/nexus/images#occamkrt16s
2) I then followed these directions (WARNING: Note the instructions to remove the "-w" from the flash-all.bat file before you run it. This will retain all your existing data, apps, settings, etc.).
http://forum.xda-developers.com/showthread.php?t=2527142
3) I then installed the latest versions of TWRP (for recovery) and superuser (for root).
Now I have a fully functioning 4.4 install with no loss of data. I am holding off on the new hybrid radio until things stabilize a bit with that.
Click to expand...
Click to collapse
Hybrid radios are fine I have been running 4.4 and .27/84 with no issues for weeks... No need to flash the 97 if you have a hybrid radio that was already working fine. sometimes just cuz its new dont make it better...

playya said:
Hybrid radios are fine I have been running 4.4 and .27/84 with no issues for weeks... No need to flash the 97 if you have a hybrid radio that was already working fine. sometimes just cuz its new dont make it better...
Click to expand...
Click to collapse
Good to know. By the way, the 27/84 hybrid radio is the only one that would work for me (quick GPS lock). I don't have LTE in my immediate area anyway (Straight Talk AT&T), so I am in no rush, and will see how the .27/97 works out for users.

pjc123 said:
I had the same problem yesterday where the OTA made absolutely no changes (This method worked fine when I went from 4.2 to 4.3 under the same conditions; TWRP, unlocked bootloader, and stock ROM). It may be related to a new conflict with TWRP. I also had a hybrid radio installed, but I put the stock radio back in before I tried the OTA; however there were a couple changes associated with this such as build prop changes and LTE activation that I did not revert. Who knows. After searching this forum I came across a fix in the "Nexus 4 OTA Help-Desk" thread...fancy that. If you have the Android SDK installed, this is a really quick and easy fix.
1) Under "Factory Images "occam" for Nexus 4" I downloaded "4.4 (KRT16S)".
https://developers.google.com/android/nexus/images#occamkrt16s
2) I then followed these directions (WARNING: Note the instructions to remove the "-w" from the flash-all.bat file before you run it. This will retain all your existing data, apps, settings, etc.).
http://forum.xda-developers.com/showthread.php?t=2527142
3) I then installed the latest versions of TWRP (for recovery) and superuser (for root).
Now I have a fully functioning 4.4 install with no loss of data. I am holding off on the new hybrid radio until things stabilize a bit with that.
Click to expand...
Click to collapse
So the directions you have listed are the ones you found at the help desk?

tsmith9191 said:
So the directions you have listed are the ones you found at the help desk?
Click to expand...
Click to collapse
Yes, and since then in other forums, and since then in eksasol's post above.

I was in the same boat as you. Flashed stock 4.4 (entire image, not just the ota) and never lost data. I did have to reroot though.
Sent from my Nexus 4, while driving in my Evo9.

Related

[Q] Error installing Android 4.3

So I got the OTA update, but after downloading it, the install failed (dead android says: error), then the Nexus 7 reboots to 4.2.2.
I already did a factory reset, but it didn't help either...
Anyone with the same issue?
Video:
Same problem here. I haven't fixed it yet either.
Why is the right door always locked?
hasbrobot said:
Same problem here. I haven't fixed it yet either.
Why is the right door always locked?
Click to expand...
Click to collapse
I got this problem...
I download this OTA...Then it say reboot to install but it enter TWRP.
Then I put the zip to internal storage and flash but I got error.
Sent from my Sony Xperia™ sola using XDA Premium
Ben Ling said:
I got this problem...
I download this OTA...Then it say reboot to install but it enter TWRP.
Then I put the zip to internal storage and flash but I got error.
Sent from my Sony Xperia™ sola using XDA Premium
Click to expand...
Click to collapse
looks like your SystemUI.apk has been modified not in original. I would recommend to get copy of systemUI.apk from stock 4.2.2 and copy it to your tablet and using file explorer, replace it. and give a try.
jazzespresso said:
looks like your SystemUI.apk has been modified not in original. I would recommend to get copy of systemUI.apk from stock 4.2.2 and copy it to your tablet and using file explorer, replace it. and give a try.
Click to expand...
Click to collapse
yeah i have modified my SystemUI before.and also framework-res...
but i didn't save my old SystemUI,can you upload?
Sent from my Google Nexus 7 using XDA Premium App
Ashenphoenix said:
So I got the OTA update, but after downloading it, the install failed (dead android says: error), then the Nexus 7 reboots to 4.2.2.
I already did a factory reset, but it didn't help either...
Anyone with the same issue?
Video:
Click to expand...
Click to collapse
my OTA failed too, different error. this usually always the case if /system/ folder integrity check failure (error 7), means files in /system/ folder are not original or modified. Yours does not give any details, but I bet it is. to see what error, try to flash it thru CWM or any other custom recovery you use.
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
Ben Ling said:
yeah i have modified my SystemUI before.and also framework-res...
but i didn't save my old SystemUI,can you upload?
Sent from my Google Nexus 7 using XDA Premium App
Click to expand...
Click to collapse
here you go...but remember it may get another error for another file, so it is better to find stock 4.2.2 ROM (check here N7 forum, someone probably posted the link)
jazzespresso said:
here you go...but remember it may get another error for another file, so it is better to find stock 4.2.2 ROM (check here N7 forum, someone probably posted the link)
Click to expand...
Click to collapse
okay...will my data be erase when installing?
Sent from my Google Nexus 7 using XDA Premium App
---------- Post added at 09:07 PM ---------- Previous post was at 08:48 PM ----------
jazzespresso said:
here you go...but remember it may get another error for another file, so it is better to find stock 4.2.2 ROM (check here N7 forum, someone probably posted the link)
Click to expand...
Click to collapse
Tried your SystemUI,don't work...keep on stopped...so I replace back...
Sent from my Sony Xperia™ sola using XDA Premium
I guess I'll download the Nexus Toolkit, click on the flash stock + unroot button, so it flashes the stock 4.2.2 and then I'll try to OTA update again.
I already unrooted, but I think it's not a problem.
Seems like it is not fixable!
I used fast boot to push my missing file.
I used es file explorer.
I used titanium back up to make the app, system...
No way, nothing. Not the slightest luck.
(My missing app is xt9ime.apk)
I haaaaaate this situation.
the worst thing is that xt9ime.apk is asus keyboard, and it is disabled by google on nexus 7.
why should not having an app that they don't want to use be a problem. X(
Sent from my Nexus 7 using XDA Premium HD app
Are you guys with errors using SuperSU? If so what version?
It seems like that the last couple versions touch a file used by OTAs. The Dev recommends using the "Full Unroot" option in the SuperSU app prior to accepting the OTA.
jaysus145 said:
Are you guys with errors using SuperSU? If so what version?
It seems like that the last couple versions touch a file used by OTAs. The Dev recommends using the "Full Unroot" option in the SuperSU app prior to accepting the OTA.
Click to expand...
Click to collapse
I did full unroot, and I also did a factory reset, but it still fails to install.
Using Wug's Toolkit to flash stock 4.2.2 is a good idea?
Then try to OTA update 4.3 again?
Same problem
Hi,
I think I have the same problem:
What to do?
You cannot install the full image from Google using fastboot? Just back up your data(if you can) then try a fresh install.
Sent from my Galaxy Nexus using Tapatalk 2
chrisinsocalif said:
You cannot install the full image from Google using fastboot? Just back up your data(if you can) then try a fresh install.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
What is Fastboot?
Theuntje said:
What is Fastboot?
Click to expand...
Click to collapse
Sadness.
Fastboot is a utility used to control the base fastboot firmware on many Android devices. It lets you do low-level actions such as flashing a custom recovery, ROM, or kernel. Toolkits run fastboot behind the scene, but automate the commands for newer users.
I had exactly the same problem and after trying a few things, I just found a working solution for my Nexus 7.
I used the same tool I used to unlock and root a few months ago: Nexus Root Toolkit 1.6.3.
I made a backup of my files first, my idea being to reflash the 4.2.2 rom
I downloaded the system file here: https://developers.google.com/android/nexus/images#occamjwr66v
Then, in the Nexus Root Kit, launch " flash stock + unroot" and select the downloaded system file.
The flash lasts 5 minutes, and the system will reboot.
Then you need to reactivate the usb debugging .
The next action is to relock the Nexus, with the "OEM Lock" in Nexus Root Toolkit.
The system will reboot after flash.
Then, the 4.3 update will be available automaticaly but this time the installation won't crash.
I hope this could help.
el chibro said:
I had exactly the same problem and after trying a few things, I just found a working solution for my Nexus 7.
I used the same tool I used to unlock and root a few months ago: Nexus Root Toolkit 1.6.3.
I made a backup of my files first, my idea being to reflash the 4.2.2 rom
...
I hope this could help.
Click to expand...
Click to collapse
Thanks for the idea. I used a similar approach with different steps and got 4.3 and root back.
I had stock 4.2.2, stock recovery, rooted (SuperSU).
Backup data.
From the Toolkit at http://forum.xda-developers.com/showthread.php?t=1809195
- "9. Download, Extract + Flash Google Factory Stock Rom"
- Download Stock Image
- "15. Android 4.2.2 (Build JDQ39)
... followed directions to download and flash WITHOUT wiping USERDATA
I did NOT do the "relock the Nexus, with the OEM Lock".
After flashing, did the OTA update to 4.3
After OTA and rebooting, got SuperSU update and put it on my N7
SuperSU thread: http://forum.xda-developers.com/showthread.php?t=1538053
CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu
I went back in to the Toolkit:
- "10. Boot to Custom/Stock Recovery without Permanently Flashing it"
In CWM, I flashed the installable SuperSU ZIP, rebooted, and got rooted.
RocketOptics said:
Thanks for the idea. I used a similar approach with different steps and got 4.3 and root back.
I had stock 4.2.2, stock recovery, rooted (SuperSU).
Backup data.
From the Toolkit at http://forum.xda-developers.com/showthread.php?t=1809195
- "9. Download, Extract + Flash Google Factory Stock Rom"
- Download Stock Image
- "15. Android 4.2.2 (Build JDQ39)
... followed directions to download and flash WITHOUT wiping USERDATA
I did NOT do the "relock the Nexus, with the OEM Lock".
After flashing, did the OTA update to 4.3
After OTA and rebooting, got SuperSU update and put it on my N7
SuperSU thread: http://forum.xda-developers.com/showthread.php?t=1538053
CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu
I went back in to the Toolkit:
- "10. Boot to Custom/Stock Recovery without Permanently Flashing it"
In CWM, I flashed the installable SuperSU ZIP, rebooted, and got rooted.
Click to expand...
Click to collapse
Hmm, why didn't you flash directly the 4.3 factory image and the SuperSU.zip on top of it ...
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Hmm, why didn't you flash directly the 4.3 factory image and the SuperSU.zip on top of it ...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I wanted to save my data and wasn't sure if going directly to 4.3 would be safe. Was just being cautious and letting the OTA do the update.

[Q] Problem with OTA 4.3

Hey guys, got a problem here.
My nexus 4 is rooted running team win recovery. running 4.2.2
just got the notification about OTA update 4.3, really excited about it and clicked install.
phone rebooted, went to teamwin, and it looked to me trying to flash something. left it there and suddenly when back to the team win recovery home page. clicked reboot to system and don't know why i'm still in 4.2.2. checked for updates but says system is up to date.
can anyone help me with the solution?
thanks a lot
You need the stock recovery, as said in a thousand other threads. If u want 4.3 flash the system image and re-root
Sent from my Nexus 4 using xda premium
EddyOS said:
You need the stock recovery, as said in a thousand other threads. If u want 4.3 flash the system image and re-root
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Or he could just get any 4.3 ROM and flash it through TWRP.
Sent from my Nexus 4 using xda app-developers app
Aaaaand i am still waiting for my update :/
My two friends with Samsung GNex got the Update, but ME with the Latest Nexus 4 still using 4.2.2 and on stock how beautiful the feeling is haha
Thibaultvw said:
Or he could just get any 4.3 ROM and flash it through TWRP.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Or CWM
If you want it that bad. Just download the factory image from Google devs and flash it.
Then you also have stock ROM running.
Send from my Nexus 4
EddyOS said:
Or CWM
Click to expand...
Click to collapse
He uses TWRP.
Sent from my Nexus 4 using xda app-developers app
Is there any way to revert back to stock recovery in order to get the update?
Further more, is there an option to do so without re-flashing stock all together?
wizardwiz said:
Is there any way to revert back to stock recovery in order to get the update?
Further more, is there an option to do so without re-flashing stock all together?
Click to expand...
Click to collapse
You can extract the stock recovery from the factory image and flash through fastboot.
Hit thanks if I helped.
Sent from my Nexus 4 using xda app-developers app
You can get the stock 4.2.2 recovery from the 4.2.2 factory image. I did have it but as I only keep the current factory image I only have the 4.3 recovery to hand
EddyOS said:
You can get the stock 4.2.2 recovery from the 4.2.2 factory image. I did have it but as I only keep the current factory image I only have the 4.3 recovery to hand
Click to expand...
Click to collapse
OK, did some further investigations and here are my findings
1. If you have it, you can use Wugfresh's toolkit (V1.6.4 for now) and it has a utility that can simply restore stock recovery and if you want it, stock kernel as well.
2. The Toolkit will download all necessary files and prompted you before each step.
3. It will revert back permissions for the stock recovery as well
I'll give it a try later on at home.
Thanks guys
Ziv
I am a bit confused. According to the “Nexus OTA Help-Desk” thread, the way to do this is as follows:
Scenario #2
You are stock, with root. Custom Recovery without any modifications or deletions.
Continue to Section B
Section B: Flashing in a custom recovery
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery
3) Flash the OTA
4) Flash Su.zip: (SU is being updated often so check Chainfire's G+ for the latest) https://plus.google.com/+Chainfire/posts
NOTE: Root on 4.3 is not stable. Your mileage may vary.
5) Reboot
So, what is different about using this method to install the OTA and just running the OTA from the notification, and is this the incorrect method?
Is returning to the stock recovery the preferred and more or less foolproof method?
I'm not sure why there's people saying otherwise, but from my experience you don't need stock recovery to take on an OTA...
I've updated my N7 several times now from when I first bought it to 4.3 currently, all the time with a custom recovery. Unless you've changed some other files which causes an error during the OTA update, I don't believe there is a need to re-flash stock recovery at all.
@mlj11, lots of people have the OTA failing on them, even if they are on rooted factory image 4.2.2.
Why the OTA fails on rooted 4.2.2 is still unclear.
My N4 with rooted factory image 4.2.2 also updated like it should without error.
Maybe the unlocked bootloader is the issue letting the 4.3 OTA fail.
Send from my Nexus 4
@DecypherT
I'm not saying that rooted users will have no problems updating. My post was in response to people on this thread saying that a custom recovery will stop the OTA. This is false.
It can't be the unlocked bootloader (and it has never been) causing the problem otherwise you or I wouldn't have been able to take the OTA, for example. More likely it's something else.
If any of a user's system files have been altered, there's a good chance the OTA will fail. In the past that happened to me because the Stickmount app changed one of the system files. Once I replaced it though, I could update without any problems.
Ok, good points you're proving here.
Still, it looks like the (OTA) android 4.3 is very unstable.
I'm on rooted 4.3 and experience no big bugs or flaws though.
I do see a very large decrease of battery life when using the phone (screen on) and a big increase when in deep sleep. When the phone is off I almost use no battery.
Send from my Nexus 4

Jwr66y ota

Does anyone know where I can get a flashable OTA file that will keep root for the Wifi OG Nexus 7? I have seen it posted for the Nexus 4 and new Nexus 7, but cannot find it anywhere for Grouper.
VAVA Mk2 said:
Does anyone know where I can get a flashable OTA file that will keep root for the Wifi OG Nexus 7? I have seen it posted for the Nexus 4 and new Nexus 7, but cannot find it anywhere for Grouper.
Click to expand...
Click to collapse
There is a flashable ota at the link below. You may need to flash superuser 1.51 after to get root back.
http://forum.xda-developers.com/showthread.php?t=1745781
Sent from my GT-I9505 using xda app-developers app
gsmyth said:
There is a flashable ota at the link below. You may need to flash superuser 1.51 after to get root back.
http://forum.xda-developers.com/showthread.php?t=1745781
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
OK I tried that but I got a Status 7 error message and it aborted install. I have everything stock that I can think of. No custom kernel. No nothing. Any suggestions other than flashing back to stock completely via Wug's toolkit then doing the OTA through the tablet itself and then restoring everything with Titanium Backup?
VAVA Mk2 said:
OK I tried that but I got a Status 7 error message and it aborted install. I have everything stock that I can think of. No custom kernel. No nothing. Any suggestions other than flashing back to stock completely via Wug's toolkit then doing the OTA through the tablet itself and then restoring everything with Titanium Backup?
Click to expand...
Click to collapse
If you check that thread I linked to above, there a few people with the status 7 error and a few different fixes, worth a try before wiping anything, hope it helps.
Sent from my GT-I9505 using xda app-developers app
gsmyth said:
If you check that thread I linked to above, there a few people with the status 7 error and a few different fixes, worth a try before wiping anything, hope it helps.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Thanks I appreciate it!
VAVA Mk2 said:
OK I tried that but I got a Status 7 error message and it aborted install. I have everything stock that I can think of. No custom kernel. No nothing. Any suggestions other than flashing back to stock completely via Wug's toolkit then doing the OTA through the tablet itself and then restoring everything with Titanium Backup?
Click to expand...
Click to collapse
You don't need to flash the stock image and lose your data, but even if you are on stock 4.3 you still need two things: stock recovery (if you don't already have it installed) AND you need to unroot! Being rooted will throw the Status 7 error.
Here's what I did:
First flash the stock recovery for JWR66V in fastboot.
Then use the "Full unroot" option inside SuperSU.
Apply the JWR66Y update using ADB sideload.
Then reinstall TWRP and install UPDATE-SuperSU-v1.51.zip using TWRP.
After rebooting you may be surprised to see that the SuperSU app needs to be installed again (seems to be a quirk a lot of us are having). Just head over to Google play and after that all should be good.
Sent from my Nexus 7 using xda app-developers app
CatThief said:
You don't need to flash the stock image and lose your data, but even if you are on stock 4.3 you still need two things: stock recovery (if you don't already have it installed) AND you need to unroot! Being rooted will throw the Status 7 error.
Here's what I did:
First flash the stock recovery for JWR66V in fastboot.
Then use the "Full unroot" option inside SuperSU.
Apply the JWR66Y update using ADB sideload.
Then reinstall TWRP and install UPDATE-SuperSU-v1.51.zip using TWRP.
After rebooting you may be surprised to see that the SuperSU app needs to be installed again (seems to be a quirk a lot of us are having). Just head over to Google play and after that all should be good.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi, I'm looking forward to doing this step since I really want to get that OTA installed in my device. Mine is on stock ROM, rooted via wugfresh toolkit. My concern is, after doing this step, will I lose all data? Also could you please explain how to do the first step- "First flash the stock recovery for JWR66V in fastboot."? I'm still a bit new to all these things, so please bare with me.
Thanks!
http://forum.xda-developers.com/showthread.php?t=1745781&page=53
Check out this thread. I flashed the Grouper.zip file, which is the OTA modified by commenting out the validation check that results in the Status 7 error. I copied it to /sdcard along with the Supersu 1.51 zip. The ota flashed perfectly using TWRP recovery. After booting and going back into TWRP, I flashed the supersu1.51 and regained root. You do not need to unroot or flash stock recovery to get this update. No data loss. I'm stock rom & kernel, rooted with TWRP recovery.
choybel said:
Hi, I'm looking forward to doing this step since I really want to get that OTA installed in my device. Mine is on stock ROM, rooted via wugfresh toolkit. My concern is, after doing this step, will I lose all data? Also could you please explain how to do the first step- "First flash the stock recovery for JWR66V in fastboot."? I'm still a bit new to all these things, so please bare with me.
Thanks!
Click to expand...
Click to collapse
You won't lose data if you repeat the steps I took. However since you are asking how to flash a recovery in fastboot I would seriously be careful and do a bit of homework on how fastboot works. All the instructions you'll ever need can be found by searching xda. It really isn't as daunting as it sounds but you definitely need to understand how it works before trying it.
Or you could try the link that Groid posted if you aren't concerned about skipping the validation check. The process is definitely is simpler if you're "new to all these things".
I'm not opposed to using WugFresh's toolkit, he's a brilliant developer, but it's never a bad idea to learn about what happens in the background and see it with your own eyes.
Sent from my rooted GSM Galaxy Nexus

Aokp to 4.4

Hello all. I am in need of some assistance. I had bought the wifi nexus 7 (2012) rooted for my son... it had aokp rom booted on it.. my other son has a stock nexus 7 and received the update.. can someone please help me and guide me know how to update his nexus to 4.4 stock rom.. I'm not a stranger to rooting and such. He currently has the newest version of twrp recovery and bootloader 4.13.
Thank you in advance.
Sent from my SM-N900V using xda app-developers app
jjdicecco said:
Hello all. I am in need of some assistance. I had bought the wifi nexus 7 (2012) rooted for my son... it had aokp rom booted on it.. my other son has a stock nexus 7 and received the update.. can someone please help me and guide me know how to update his nexus to 4.4 stock rom.. I'm not a stranger to rooting and such. He currently has the newest version of twrp recovery and bootloader 4.13.
Thank you in advance.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
Hi, jjdicecco...
If you have a Nexus 7 with a Custom ROM (such as AOKP) installed on it, you won't be able to update it to stock Android 4.4 KitKat via the normal process of OTA updates.
Googles OTA updates do not work with Custom ROMs - only with Unmodified Stock
The reason why, is because OTA's aren't full ROMs - they consist of a collection of 'patches' that are applied (during the update process) to the system files in the preexisting version of official stock Android. But before those 'patches' can be applied, the OTA runs a checksum on all system files to ensure they haven't been modified... and a Custom ROM such as AOKP, represents a very significant modification of stock Android... so, in short, the OTA will abort with no changes made.
The only way to bring your AOKP Nexus 7 up to date with KitKat, is to forget about OTA's and flash the full factory image for Android 4.4 KitKat, available here. Essentially, you need to re-install the entire Android OS from scratch.
It's important you download the correct factory image for your specific Nexus 7... so if your Nexus 7 is WiFi only, you'll need the 'nakasi' image... if it's the WiFi & 3G model, then the 'nakasig' image is required.
Although there are toolkits that will get the job done (so to speak), I've never used them myself... and IMHO, you'd be better of using the fastboot tool that Google themselves provide.
There is an excellent tutorial available here on how to use fastboot to flash a factory image on the Nexus 7.
It looks a little daunting, but if, as you say, you're no stranger to rooting or flashing recoveries such as TWRP, then you shouldn't have much problem following it - it's actually quite straightforward.
Hope this helps... and good luck.
Rgrds,
Ged.
Thank you very much.. can I just flash a whole rom from development
Sent from my SM-N900V using xda app-developers app
jjdicecco said:
Thank you very much.. can I just flash a whole rom from development
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
Yes, you can.
If you have TWRP installed, just download the ROM .zip of your choice directly to the Nexus 7... boot into TWRP, go to WIPE>ADVANCED WIPE and clear Dalvik Cache, System, Cache and Data... BUT UNDER NO CIRCUMSTANCES, WIPE INTERNAL STORAGE... or you'll lose the Custom ROM you just downloaded. You'll have no bootable OS, and no easy means of installing one... without resort to either ADB or fastboot.
After this, use the INSTALL button in TWRP to flash that ROM. (You'll need to navigate to where it downloaded to - usually the /download folder on the Nexus 7's internal storage).
It's a good idea, though, before doing any of this, to perform a NANDROID backup of your current AOKP system using the BACKUP button in TWRP... just in case anything goes wrong with your ROM flash, or if the ROM you flashed isn't what you expected it be.
You'll then have an easy way of getting back to your current setup.
Rgrds,
Ged.

Nexus 7 2013 Android Update 4.3 to 4.4.2

Do you have problems updating Nexus 7 from Jelly Bean to Kitkat? Well I did, since the day got my hands of N7 device, it was unlocked and rooted.
Somewhere is Sep the News of Kitkat has been rolling out. In Oct my N7 device notified on the new Kit Kat upgrade. I have been trying using OTA update but each time came to "FAILED" installation and so decided to give up the idea since JB 4.3 was working fine.
Now Kit Kat rolled out 4.4.2 version and still I had the same problem, did some researched on XDA forum and tried each of their suggestion but still did not work out. I was always stuck with "KoreanIME.apk" error on recovery, perhaps something I deleted earlier on.
Using Nexus Root Toolkit Ver 1.8
Finally decided to use the Nexus Root Toolkit (NRT). The last time used it was rooting the brand new N7. Run NRT and it started gathered information and upgraded to latest NRT ver 1.8.
With the new NRT version I decided to Flash Stock + Unroot, hoping I can do the update by going back to stock. To my surprise NRT found the latest Kitkat 4.4.2 and installed on Nexus 7. Most of the data was lost but had earlier done a backup. After which just like a brand new device, log in my account and immediately all the previous Apps started to download back to the device.
Once that was done, Root the device using NRT included Custom Recovery check, the rest just follow NRT instructions to install BusyBox and all is Done!!
Apps like Watsapp had to be installed manually since it does not support tablet version. Other data were also done manually.
I would not recommend this method unless you are prepared to wipe everything clean, so do a backup first. There were no other options and this was the only method.
Hope this helps and if anyone can point out the mistake I have done, do share for others.
OTA update doesn't work with custom recovery if I'm not mistaken
OTA can work with custom recovery, I've done it several times, though the custom recovery was overwritten by the update.
Sent from my SGH-I747M using xda app-developers app
Yes, OTA in the form of .zip file can be flashed via custom recovery.
But it seems that OP's problem occurs when he's trying to update from official OTA notification, from my understanding if you try to update from official OTA notification with custom recovery installed it will fail.
Please correct me if I'm wrong since mine was done through adb sideload
I did it through the official OTA (not a zip file) with a custom recovery. There seems to be a myth out there that it's not possible, but I can say from experience that it is possible.
Sent from my SGH-I747M using xda app-developers app
clienttrace said:
Yes, OTA in the form of .zip file can be flashed via custom recovery.
But it seems that OP's problem occurs when he's trying to update from official OTA notification, from my understanding if you try to update from official OTA notification with custom recovery installed it will fail.
Please correct me if I'm wrong since mine was done through adb sideload
Click to expand...
Click to collapse
Just for clarification, besides using auto OTA update, I did tried it manually using razor and SuperSu zip files. Also as you mentioned ADB sideload. It did not work out.
Somehow using NRT was much easier, just sit back and let NRT do all the job. The only setback were the missing data. Not a big issue, anyway was nice to see the file structure cleaned up.
gc84245 said:
I did it through the official OTA (not a zip file) with a custom recovery. There seems to be a myth out there that it's not possible, but I can say from experience that it is possible.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
thanks, that's clear it up for me

Categories

Resources