[Q] Can I update? - Nexus 7 Q&A, Help & Troubleshooting

Alright, so I'm running 4.2.1, and I'm rooted. I want to update to 4.2.2, but will this brick my nexus 7? Will it just unroot? How should i go about this?

No it won't brick it but you may lose root. There are many guides to manually flashing the OTA on unlocked and rooted Nexus 7.
Sent from my Desire HD using xda premium

You might not be able to update even though you are on stock ROM because in order to root n7 we need to unlock the bootloader and hence you cant
Sent from my Nexus 7 using xda app-developers app

This is the extracted factory image for 4.2.2 - in both odexed and deodexed verisons, rooted with insecure boot, init.d support & busybox - easily flashed from CWM or TWRP - data & apps are preserved.
http://forum.xda-developers.com/showthread.php?t=2148337
As always, backup first off to PC or cloud storage as a matter of precaution first. From download to prep to finish, less than 20 minutes - which is the path that I took, directly from 4.1.2 rooted to 4.2.2 and rooted.
Have fun !

Related

[Q] OTA update to 4.2.2 problems

My 7 is unlocked and rooted, using Nexus Root Toolkit. I did an OTA to get to 4.2.1 some time ago and that went well. Root and unlock persisted. I am now getting OTA options for 4.2.2 from the System menu. First time I got and error in Android's belly. I restarted and was still in 4.2.1. System then said that I was up to date. A week or so later System told me again that OTA was available and I got the same result.
Any suggestions as to how I can do the update?
rsipson said:
My 7 is unlocked and rooted, using Nexus Root Toolkit. I did an OTA to get to 4.2.1 some time ago and that went well. Root and unlock persisted. I am now getting OTA options for 4.2.2 from the System menu. First time I got and error in Android's belly. I restarted and was still in 4.2.1. System then said that I was up to date. A week or so later System told me again that OTA was available and I got the same result.
Any suggestions as to how I can do the update?
Click to expand...
Click to collapse
You have two choices
1. Flash the stock 4.2.2 image using fastboot from here https://developers.google.com/android/nexus/images
Or
2. Flash this in CWM recovery (note this link is for the wifi model) http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
You have to restore everything except relocking bootloader ... To be able to update ...when u finish ..just re-root
Sent from my Nexus 7 using xda premium
Same thing happened to me, I had to unroot and then root again after update.
Sent from my HTC Desire S using xda app-developers app
heat361 said:
You have two choices
1. Flash the stock 4.2.2 image using fastboot from here https://developers.google.com/android/nexus/images
Or
2. Flash this in CWM recovery (note this link is for the wifi model) http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
Click to expand...
Click to collapse
Thanks for your post. I tried this using Clockwork and got a very long error message. I will quote part of it.
assert failed_apply_patch_check("/system/bin/debuggerd", "a2323a0c8 and a lot more
This is followed by error in file
I saw something about busybox changing some system files.
Any ideas??
How do I unroot without whipping all data?
Sent from my Nexus 7 using xda app-developers app
Search this forum for "OTA debugged"
There are only a few threads - read them all before you take any action.
This particular problem appears to be caused by StickMount.
You don't need to delete everything, nor do you need to flash the ENTIRE stock image - only the boot.img and system.img (via fastboot) without doing a factory reset or any other wiping.
This will unroot the ROM, and (of course) prevent StickMount from working. So you should over flash a SuperSU root kit afterwards (via custom recovery).
This very same problem may recur on the next OTA - so for goodness sake's, make a nandroid backup before you re-install StickMount and give it root privileges.
bftb0 said:
Search this forum for "OTA debugged"
There are only a few threads - read them all before you take any action.
This particular problem appears to be caused by StickMount.
You don't need to delete everything, nor do you need to flash the ENTIRE stock image - only the boot.img and system.img (via fastboot) without doing a factory reset or any other wiping.
This will unroot the ROM, and (of course) prevent StickMount from working. So you should over flash a SuperSU root kit afterwards (via custom recovery).
This very same problem may recur on the next OTA - so for goodness sake's, make a nandroid backup before you re-install StickMount and give it root privileges.
Click to expand...
Click to collapse
Sorry for being a numpty... can someone put the above into a mini step by step guide for me.. I'm stuggling with the terminology.
I rooted my Nexus and have since forgotten anything techie regarding it. I have StickMount and cannot update to 4.2.2..
How do i flash boot.img and system.img via fastboot, where do i get these files from, what versions etc do i need? And over flash SuperSU root kit?
What is OTA?
Basically, I think i need a newbie guide. I am techie enough to achieve most things normally.. i just don't know the android system at all, and what i did know to be able to root it i have completely forgotten!
Any guidance would be very much appreciated. Cheers.

[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

[Q] Nexus 7 Jellybean 4.3 update

hi,
apologies if this has been asked before but my searches have not found a clear answer. i have a 2012 nexus 7 Rooted and running JB 4.2.2.
the OTA update to JB 4.3 fails everytime. it gets so far and then shows the android logo with a red triangle exclamation and just "error"
it reboots back to home screen after a minute or two.
my device was rooted using WUGS toolkit and TWRP recovery. i just did the basic rooting so i could use stickmount and have done nothing funny with the device since.
i have seen many guides about flashing 4.3 update that will wipe the device which i really want to avoid.
will it work if i just un-root and re-lock the device with the toolkit and then run the OTA update or is it more complicated than that.
Lemegeton300 said:
hi,
apologies if this has been asked before but my searches have not found a clear answer. i have a 2012 nexus 7 Rooted and running JB 4.2.2.
the OTA update to JB 4.3 fails everytime. it gets so far and then shows the android logo with a red triangle exclamation and just "error"
it reboots back to home screen after a minute or two.
my device was rooted using WUGS toolkit and TWRP recovery. i just did the basic rooting so i could use stickmount and have done nothing funny with the device since.
i have seen many guides about flashing 4.3 update that will wipe the device which i really want to avoid.
will it work if i just un-root and re-lock the device with the toolkit and then run the OTA update or is it more complicated than that.
Click to expand...
Click to collapse
Same Here!, I had TWRP recovery and I'm rooted, so Just Flashed stock recovery and I though I can update easily. But now I can't!
-By the way, I did not change any system file.
Since you have Stickmount did your error message reference a bad file check on 'debuggerd' in the /system/bin folder? It seems Stickmount may replace or alter that file and you have to put back an original for 4.2.2 to successfully flash the update with TWRP. After replacing 'debuggerd', the update flashed just fine for me. Are you sure you didn't get any text other than 'Error'? Are you sure you didn't freeze or delete any system apps?
It also happened to my nexus 4, they recommended to use this way: (It won't erase the data)
http://forum.xda-developers.com/showthread.php?t=2377307
hey, the error has no message or info. it literally says the word "error" with red exclamation and thats it. i have not touched any of the system apps or done anything that could upset the system files.
i will try the suggestion from alipashang77, thanks
sorry but those instructions are for the samsung galaxy nexus phone.
does not apply to my nexus 7 tablet.
any suggestions
Lemegeton300 said:
sorry but those instructions are for the samsung galaxy nexus phone.
does not apply to my nexus 7 tablet.
any suggestions
Click to expand...
Click to collapse
There's tonnes of older posts with all the info you'll need. Gotta just search more.
Ota will erase everything except your internal/external sd cards. Plus ota wont work if anything system wise had been altered. You'd have to Odin stock 4.2.2 then do ota.
No reason why you can't just flash a 4.3 rom like anything else tho.
And in all cases, wiping your data and apps is best. You gotta back it up. Restore after. Apps and their data anyway. Restoring system app data is never ever a good idea.
Sent from my cellular telephone
Device won't update via OTA with a custom recovery. And 4.3 OTA will fail if you're rooted. So in order to get OTA make sure you have stock recovery and unroot, then as long as you haven't modified anything system wise it should update successfully. And no, OTA updates will not wipe any data.
Sent from my Nexus 7 using xda premium
thanks everyone. its finally updated to 4.3. i backed up my data and then flashed the stock 4.3 image and that failed and the device would not boot. i thought it was bricked but it let me flash the 4.2.2. image and then the 4.3 OTA update worked.
:good::good::good::good::good:
hi guys i know that the previous reply was that flashing to the 4.2.2 worked then the OTA worked, however i have an explaination for people that were stuck like me
i JUST managed to upgrade my nexus 7 to 4.3 (JWR66Y)
i found a helpful link to upgrade from http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1
after following all the steps, my i wasnt able to flash the bootloader (bootloader-grouper-4.23.img).
after doing some googling today, i found that it is the bootloader in the 4.3 update that is different (according to http://forum.xda-developers.com/showthread.php?t=2417097&page=2) and that you need the JWR66V bootloader img file (which is also the bootloader-grouper-4.23.img) they explain it in the link above, and have a download link for it there.
so in order to do the update, what you need to do is follow the steps from the 1st link (extract all the files etc in place), but before flashing, copy the bootloader from the 2nd link into your platform-tools folder, then follow the steps to flash.
as long as you follow the steps, and skip step 10, you will keep your data also
hope that helped
95Z28 said:
Device won't update via OTA with a custom recovery. And 4.3 OTA will fail if you're rooted. So in order to get OTA make sure you have stock recovery and unroot, then as long as you haven't modified anything system wise it should update successfully. And no, OTA updates will not wipe any data.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Per WugFresh's advice, if you're rooted and using stock reovery, you still can OTA update.
Link: http://www.wugfresh.com/nrt/faqs/
vndnguyen said:
Per WugFresh's advice, if you're rooted and using stock reovery, you still can OTA update.
Link: http://www.wugfresh.com/nrt/faqs/
Click to expand...
Click to collapse
Past OTAs would be successful when rooted, you would usually just lose root access. But the 4.3 OTA won't work while rooted, you'll just keep getting the failed message.
Sent from my Galaxy Nexus using xda premium
95Z28 said:
Past OTAs would be successful when rooted, you would usually just lose root access. But the 4.3 OTA won't work while rooted, you'll just keep getting the failed message.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
ok thanks. I'm on 4.3 and only root with stock recovery. So if the 4.4 available I will unroot and then OTA. Thanks!

Flash OTA with TWRP

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.

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.

Categories

Resources