Database Users

problem to update to 4.3 with TWRP installed

Hi guys. I have a small question and maybe a problem. I have Nexus 4 rooted with unlocked boot loader, and TWRP installed on it. And as I think with stock rom, because only done everything to root, but nothing else.
Now I have a problem: phone offering to update to 4.3. I press update. It updating and restarting, but after restart it loads TWRP. And what should I do next to finish update? Because I don't know how to make it finish updating with TWRP? What should I do with TWRP to do so? I will be very thankful for any help. Because twice was making update, but still on 4.2.2.

You need to flash the stock recovery because you can't update via OTA with a custom recovery.

You can actually OTA with TWRP.. The device should load into TWRP and complete the update. After the update you will lose TWRP and root

Rizy7 said:
You can actually OTA with TWRP.. The device should load into TWRP and complete the update. After the update you will lose TWRP and root
Click to expand...
Click to collapse
I have seen this in 4.2.2 but not on 4.3. Could you please elaborate a bit more? How did you accomplish this with all these new security policies in 4.3? Thanks.

Mercado_Negro said:
You need to flash the stock recovery because you can't update via OTA with a custom recovery.
Click to expand...
Click to collapse
This is incorrect. The best way to update is download the ota zip from here http://forum.xda-developers.com/showthread.php?t=2145848
Go to twrp recovery flash the ota zip then SU zip v1.51 reboot done. Now you got 4.3 with root and you won't lose your recovery
From my BLACKED OUT N4

spaceman860 said:
This is incorrect. The best way to update is download the ota zip from here http://forum.xda-developers.com/showthread.php?t=2145848
Go to twrp recovery flash the ota zip then SU zip v1.51 reboot done. Now you got 4.3 with root and you won't lose your recovery
From my BLACKED OUT N4
Click to expand...
Click to collapse
Sorry if it sounded incorrect to you but what you just suggested, although it works, it is not an OTA update per definition as far as I know. Please correct me if I'm wrong.

Mercado_Negro said:
Sorry if it sounded incorrect to you but what you just suggested, although it works, it is not an OTA update per definition as far as I know. Please correct me if I'm wrong.
Click to expand...
Click to collapse
When you get the notification saying there is a update on your phone you select it and it downloads flashes the ota zip. What I said is the same thing except you download it and flash it your self and by doing it this way you can flash the SU zip at the same time and not lose root or recovery.
From my BLACKED OUT N4

spaceman860 said:
When you get the notification saying there is a update on your phone you select it and it downloads flashes the ota zip. What I said is the same thing except you download it and flash it your self and by doing it this way you can flash the SU zip at the same time and not lose root or recovery.
From my BLACKED OUT N4
Click to expand...
Click to collapse
Thanks, your post above made me read that thread you linked and while it works, it's not a real OTA (notification from Google or OEMs), but let's not fall into semantics here, the thing is it works and does the job pretty much like a real OTA. Thanks again, I learned (and downloaded) something new today

Mercado_Negro said:
Thanks, your post above made me read that thread you linked and while it works, it's not a real OTA (notification from Google or OEMs), but let's not fall into semantics here, the thing is it works and does the job pretty much like a real OTA. Thanks again, I learned (and downloaded) something new today
Click to expand...
Click to collapse
The zip in the link is from Google. When someone got the notification on there phone they posted the link to the zip it would be the same file if you received it on your phone
From my BLACKED OUT N4

spaceman860 said:
The zip in the link is from Google. When someone got the notification on there phone they posted the link to the zip it would be the same file if you received it on your phone
From my BLACKED OUT N4
Click to expand...
Click to collapse
I know my friend I'm just trying to say that the affirmation "yes, you can update via OTA using a custom recovery" is not valid for someone getting the notification which is the common scenario for most people. Anyways, it's all good :thumbsup:

Mercado_Negro said:
You need to flash the stock recovery because you can't update via OTA with a custom recovery.
Click to expand...
Click to collapse
If I flash the stick recovery will I lose any data such as pics n vids?

rabidrotty said:
If I flash the stick recovery will I lose any data such as pics n vids?
Click to expand...
Click to collapse
No, you won't.

Mercado_Negro said:
No, you won't.
Click to expand...
Click to collapse
Awessome thanks bud. It's been awhile and I forgot if it did or not. You rock.

[Q] KRT16O to KRT16S ?

I installed factory image KRT16O and rooted it and also installed CWM touch recovery. Will i get the OTA to KRT16S ? Will i lose root afterwards ? Will the custom recovery cause problems ?

+1
Sent from my Nexus 4 using Tapatalk

+1
---------- Post added at 01:44 PM ---------- Previous post was at 01:39 PM ----------
I guess an ota zip will be very helpfull.

You will not get OTA with custom recovery, but you can download the OTA package and flash it using custom recovery. You will lose root, but you can either hide root or reflash it. edit: CWM is not compatible with OTA, it will soft brick the device.
sent from tapatalk

for the custom recovery part. I'm running KRT16S with TWRP 2.6.3.3, works just fine. Earlier try it with latest CWM touch, works fine too.
But I'm doing manual install (adb and image). So I can tell you anything about flashing rom.zip through custom recovery. I think it won't cause any problem by flashing rom through custom recovery.
Forgive me if I'm wrong. thanks

Thanks eksasol but can you give us a link for the OTA package(KRT16S)?

you can lose root,, you have to re flash after installing to krt16s
im sorry for my english
other way,,, you can install zip version of factory image..

If I flash back to stock recovery will I be able to get this new KitKat build OTA?

+1
CWM, root, KRT16O. Id rather just a .zip update so I dont have to go through the whole rig-a-ma-role again (other than re-rooting).

You can get the OTA through custom recovery contrary to what others are saying. The KRT16S OTA arrived for my KRT16O, and it proceeded to automatically reboot and flash through TWRP.
Custom recovery and root is wiped after that OTA update, so you will need to re-flash both.

I will try the OTA as soon as I get it. I'm on CWM but I think that if you did it on TWRP there is no reason it won't update on mine. Thanks!

what to do if I Dont want to get the O T A ? flash fota killer for 4,3 will it work,?
Sent from my nexus 4 running 4.4 kit kat

no OTA for my stock KRT16O...
I updated my N4 to the Google factory image KRT16O via fast boot through stock recover using ADB, from previous 4.2.2 stock - I chose to avoid 4.3 due to all the issues. The phone is completely stock, but no update is available yet? Could it be because I manually updated to KRT16O using fastboot? I don't see why this would stop the latest update being pushed since the phone is pure stock with zero changes to recovery or root.

Globespy said:
I updated my N4 to the Google factory image KRT16O via fast boot through stock recover using ADB, from previous 4.2.2 stock - I chose to avoid 4.3 due to all the issues. The phone is completely stock, but no update is available yet? Could it be because I manually updated to KRT16O using fastboot? I don't see why this would stop the latest update being pushed since the phone is pure stock with zero changes to recovery or root.
Click to expand...
Click to collapse
That is technically impossible, fastboot only work in fastboot mode (aka the bootloader menu). So you must have flashed it in fastboot mode, not stock recovery. You can download the OTA package from the thread in the general section and sideload it in stock recovery, or use fastboot to flash the KRT16S firmware, since you said you did it already, shouldn't be an issue.

Salty Wagyu said:
You can get the OTA through custom recovery contrary to what others are saying. The KRT16S OTA arrived for my KRT16O, and it proceeded to automatically reboot and flash through TWRP.
Custom recovery and root is wiped after that OTA update, so you will need to re-flash both.
Click to expand...
Click to collapse
Half true.
Updated yesterday the S version normally through OTA and my TWRP recovery is still there.
Only thing neeeded after was to reroot and flash custom kernel again, which I had remove to make the update.
Sent from my NookColor using Tapatalk 4

eksasol said:
That is technically impossible, fastboot only work in fastboot mode (aka the bootloader menu). So you must have flashed it in fastboot mode, not stock recovery. You can download the OTA package from the thread in the general section and sideload it in stock recovery, or use fastboot to flash the KRT16S firmware, since you said you did it already, shouldn't be an issue.
Click to expand...
Click to collapse
Thanks. Yes, my mistake, of course it was just fastboot.
I would have thought that the new build would show up OTA, but maybe it looks for 4.3 to initiate as KRT16O never actually was pushed OTA.
I guess I could update to new build via fastboot like before, but had hoped to get it OTA.
Cheers.

Globespy said:
Thanks. Yes, my mistake, of course it was just fastboot.
I would have thought that the new build would show up OTA, but maybe it looks for 4.3 to initiate as KRT16O never actually was pushed OTA.
I guess I could update to new build via fastboot like before, but had hoped to get it OTA.
Cheers.
Click to expand...
Click to collapse
You can flash image without wiping data, links in my signature. There is a KRT160 to KRT16S OTA package as well, I was hoping you could find it yourself, but I guess I'll do a bit more work: http://forum.xda-developers.com/showthread.php?t=2145848

eksasol said:
You can flash image without wiping data, links in my signature. There is a KRT160 to KRT16S OTA package as well, I was hoping you could find it yourself, but I guess I'll do a bit more work: http://forum.xda-developers.com/showthread.php?t=2145848
Click to expand...
Click to collapse
Cheers! I may wait a few days to see if the OTA comes since phone is stock untouched... But if nothing in next 2 days I'll fastboot the image.

[XT1032] OTA to 4.4.4 (falcon_umts.EURetail.en.EU)

Today I received the OTA update from Android 4.4.2 to 4.4.4 for my Moto G.
Filename:
Blur_Version.176.44.1.falcon_umts.EURetail.en.EU.zip
Md5:
fbe58f70c4922c785d55fd5a998e9628
Download links:
http://www.filedropper.com/blurversion176441falconumtseuretaileneu
http://www13.zippyshare.com/v/24209763/file.html
https://www.sendspace.com/file/ighq3s
Extra info:
- Received the OTA while being rooted & using custom recovery.
- Can be flashed using PhilZ recovery.
- SuperSU Pro survived the OTA.

Petrovski80 said:
Today I received the OTA update from Android 4.4.2 to 4.4.4 for my Moto G.
Filename:
Blur_Version.176.44.1.falcon_umts.EURetail.en.EU.zip
Md5:
fbe58f70c4922c785d55fd5a998e9628
Download links:
http://www.filedropper.com/blurversion176441falconumtseuretaileneu
http://www13.zippyshare.com/v/24209763/file.html
https://www.sendspace.com/file/ighq3s
Click to expand...
Click to collapse
Is it possible to just flash this in twrp recovery?
Ive been having this pop up every 5 mins and its driving me mad, I download it but it wont flash in custom recovery, I flash stock recovery still wont flash, ive downloaded it several times just incase it was a bad download.

feartheanonymity said:
Is it possible to just flash this in twrp recovery?
Ive been having this pop up every 5 mins and its driving me mad, I download it but it wont flash in custom recovery, I flash stock recovery still wont flash, ive downloaded it several times just incase it was a bad download.
Click to expand...
Click to collapse
It should be. I flashed it using Philz recovery.

feartheanonymity said:
Is it possible to just flash this in twrp recovery?
Ive been having this pop up every 5 mins and its driving me mad, I download it but it wont flash in custom recovery, I flash stock recovery still wont flash, ive downloaded it several times just incase it was a bad download.
Click to expand...
Click to collapse
I had the same problem, TWRP did not take the OTA file properly. Every time it wanted to boot after the install started, it started TWRP and if I restarded the device it went into a bootloop.
So I installed Philz and everything went fine!

It has been said many times already. Phliz is the way to go when flashing OTAs.
Sent from my XT1032 using XDA Premium 4 mobile app

drfr said:
It has been said many times already. Phliz is the way to go when flashing OTAs.
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I copied the zip from /cache and am attempting to install it with the latest Philz.
I get this error in Philz when flashing the zip:
Verifying current system...
"EMMC:boot:10485....................... a0" has unexpected contents.
I restored my stock kernel (was running Faux before). My bootloader is unlocked and I am rooted.
Is it possible to flash directly? Or must I restore stock recovery, flash and reroot?

Is it OK to flash this if I'm already on 4.4.4?

Quark^2 said:
I copied the zip from /cache and am attempting to install it with the latest Philz.
I get this error in Philz when flashing the zip:
Verifying current system...
"EMMC:boot:10485....................... a0" has unexpected contents.
I restored my stock kernel (was running Faux before). My bootloader is unlocked and I am rooted.
Is it possible to flash directly? Or must I restore stock recovery, flash and reroot?
Click to expand...
Click to collapse
You´ve restored wrong kernel. It may be working for you, but it is different from stock. The error says that there is something that is not supposed to be there in the kernel partition.
Nicolae-Daniel said:
Is it OK to flash this if I'm already on 4.4.4?
Click to expand...
Click to collapse
You´re kidding, right?

No.my system is tesco GB.i live in Romania.by flashing this i believe will improve connectivity.
@knizmi what do you think?

Nicolae-Daniel said:
No.my system is tesco GB.i live in Romania.by flashing this i believe will improve connectivity.
@knizmi what do you think?
Click to expand...
Click to collapse
1. You can´t flash this if you are on anything other than en.EU 4.4.2. This is not a complete ROM, but rather an update for a specific ROM version.
2. It is possible reflash your XT1032 with en.EU 4.4.2 firmware and then update it to 4.4.4, but if you don´t know what you are doing, you could brick your device (several people have when they tried to downgrade the bootloader).
3. What improvement in conectivity do you mean? Is the tesco firmware limited in any way? AFAIK it isn´t, so leave it as it is and be happy about a great phone with the latest Android version.

knizmi said:
1. You can´t flash this if you are on anything other than en.EU 4.4.2. This is not a complete ROM, but rather an update for a specific ROM version.
2. It is possible reflash your XT1032 with en.EU 4.4.2 firmware and then update it to 4.4.4, but if you don´t know what you are doing, you could brick your device (several people have when they tried to downgrade the bootloader).
3. What improvement in conectivity do you mean? Is the tesco firmware limited in any way? AFAIK it isn´t, so leave it as it is and be happy about a great phone with the latest Android version.
Click to expand...
Click to collapse
By connectivity I meant signal strength.

My US-Global XT1032 still waiting...

tonyleeloveyou said:
My US-Global XT1032 still waiting...
Click to expand...
Click to collapse
US Global already has 4.4.3. The new kernel and dialer are already there, so don´t expect any improvements besides security patches when we get 4.4.4.

I received the OTA today. Updated without problems. Stock XT1032 8GB Moto G.

drfr said:
It has been said many times already. Phliz is the way to go when flashing OTAs.
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you're still on Stock Recovery and don't want to use Philz, you can try to update the OTA by following the steps in the OP of this Post. I tried a lot of flashing, but in the end only this worked:
http://forum.xda-developers.com/moto-g/general/ota-file-indian-dual-sim-4-4-4-t2810166
Just follow the steps below the text:
REVERT TO STOCK WITHOUT LOSING DATA OR ANYTHING ELSE
Phone is unlocked, rooted and had xposed modules on it

Petrovski80 said:
Today I received the OTA update from Android 4.4.2 to 4.4.4 for my Moto G.
Filename:
Blur_Version.176.44.1.falcon_umts.EURetail.en.EU.zip
Md5:
fbe58f70c4922c785d55fd5a998e9628
Download links:
http://www.filedropper.com/blurversion176441falconumtseuretaileneu
http://www13.zippyshare.com/v/24209763/file.html
https://www.sendspace.com/file/ighq3s
Extra info:
- Received the OTA while being rooted & using custom recovery.
- Can be flashed using PhilZ recovery.
- SuperSU Pro survived the OTA.
Click to expand...
Click to collapse
i have a xt1032 too, and thought this would be the easiest way to update!
unlocked, rooted, cwm philz (6.19.2)
but i get a status 7 error during flashing.
verifying current system...
"/system/build.prop"has unexpected contents.
E: Error in in /data/media/0/clockworkmod.Blur_Version.176.44.1.flacon_umts.EURetail.en.EU.zip

dreezz said:
i have a xt1032 too, and thought this would be the easiest way to update!
unlocked, rooted, cwm philz (6.19.2)
but i get a status 7 error during flashing.
verifying current system...
"/system/build.prop"has unexpected contents.
E: Error in in /data/media/0/clockworkmod.Blur_Version.176.44.1.flacon_umts.EURetail.en.EU.zip
Click to expand...
Click to collapse
So why don´t you revert your build.prop to stock?

dreezz said:
i have a xt1032 too, and thought this would be the easiest way to update!
unlocked, rooted, cwm philz (6.19.2)
but i get a status 7 error during flashing.
verifying current system...
"/system/build.prop"has unexpected contents.
E: Error in in /data/media/0/clockworkmod.Blur_Version.176.44.1.flacon_umts.EURetail.en.EU.zip
Click to expand...
Click to collapse
Knizmi is right. You modified your build.prop file, and an OTA update requires unmodified system files. You can add files to /system without problems however, so the su binary for example isn't an issue.
Sent from my Moto G using Tapatalk

OK, and where do i find a stock build.prop?
i don't know what modifications i have, but can i replace the stock one with my current after flashing? (and do i need to?)

HI! Firstly thanks for share the zip.
I´m using cwm recovery, superSU and xposed. Can I flash the zip directly from the recovery without any change? Will I lose the recovery (coming back to stock recovery) if I succed?
I tried to install the OTA after uninstall xposed and checking the ota survival mode on superSU, but it didn´t work (bootloop).
Thanks in advance.

Android 5.0.0 to 5.0.1 Update

So I grabbed the 5.0.1 OTA, I have a rooted with custom recovery N4 with stock Lollipop, I flashed the 'KRT16O' (4.4.4) Stock recovery to 'Adb Sideload' the 5.0.1 OTA. I could not find Stock Lollipop recovery. It gives the error as shown in the picture attached, my opinion is that I should have Stock "Lollipop" Recovery to do that, RIght? Than What seems to be the problem?
Thanks in Advance...
UPDATE 1: Possible Solution
So, turns out you should be completely stock, means you should have stock recovery and NO ROOT. Stock Recovery can be Installed through 'Wugfresh' and unroot through SuperSu Setting. BUT, if you have modified even a single thing, YOU WILL A FACE ERROR as shown in the second screenshot. SO you will have to 'Fastboot Flash' the system.img from Factory image. I'm downloading The 5.0.0 Factory image right now and it will be downloaded by 2 hours.

alipashang77 said:
So I grabbed the 5.0.1 OTA, I have a rooted with custom recovery N4 with stock Lollipop, I flashed the 'KRT16O' (4.4.4) Stock recovery to 'Adb Sideload' the 5.0.1 OTA. I could not find Stock Lollipop recovery. It gives the error as shown in the picture attached, my opinion is that I should have Stock "Lollipop" Recovery to do that, RIght? Than What seems to be the problem?
Thanks in Advance...
Click to expand...
Click to collapse
You can get the stock recovery from the nexus factory images here . I would suggest just flashing the factory 5.0.1 image (don't flash userdata or cache and you should be fine).

I think OTA is only from 5.0.0 to 5.0.1.I'm having the same problem too and nobody seems to have an answer so I'll just get the factory images, flash all except user data
alipashang77 said:
So I grabbed the 5.0.1 OTA, I have a rooted with custom recovery N4 with stock Lollipop, I flashed the 'KRT16O' (4.4.4) Stock recovery to 'Adb Sideload' the 5.0.1 OTA. I could not find Stock Lollipop recovery. It gives the error as shown in the picture attached, my opinion is that I should have Stock "Lollipop" Recovery to do that, RIght? Than What seems to be the problem?
Thanks in Advance...
Click to expand...
Click to collapse

So what was Google supposed to change in 5.0.1? I think it was something important, but... I don't remember

You mean bringing silent mode back, getting a hold on the countless graphical glitches (yes, mine were all clean flashes) and maybe even grace us with a 3.10 kernel?
I was hoping on that as well, but it looks like we really are the rearmost wheel on the Google cart.

alipashang77 said:
So I grabbed the 5.0.1 OTA, I have a rooted with custom recovery N4 with stock Lollipop, I flashed the 'KRT16O' (4.4.4) Stock recovery to 'Adb Sideload' the 5.0.1 OTA. I could not find Stock Lollipop recovery. It gives the error as shown in the picture attached, my opinion is that I should have Stock "Lollipop" Recovery to do that, RIght? Than What seems to be the problem?
Thanks in Advance...
Click to expand...
Click to collapse
I had the same problem. I was on stock lollipop 5.0, rooted, with stock recovery. Tried sideloading the ota (for 5.0 > 5.0.1, about 18mb file) but it gave error. Turned out the mini sdk i was using was old version, 1.0.31. So I downloaded the newer version, 1.0.32, and then was able to update successfully.
Am attaching the rar file here, see if that helps

parkourz said:
So what was Google supposed to change in 5.0.1? I think it was something important, but... I don't remember
Click to expand...
Click to collapse
i dont know what they fixed or updated, i am seeing the same bugs that 5.0 had... still "slow" performance and the infinite recent task bug xD...

matiamb said:
i dont know what they fixed or updated, i am seeing the same bugs that 5.0 had... still "slow" performance and the infinite recent task bug xD...
Click to expand...
Click to collapse
I think it was something with security... but good to know that nothing has changed before flashing it

did we get a new kernel with 5.0 update?

alipashang77 said:
So I grabbed the 5.0.1 OTA, I have a rooted with custom recovery N4 with stock Lollipop, I flashed the 'KRT16O' (4.4.4) Stock recovery to 'Adb Sideload' the 5.0.1 OTA. I could not find Stock Lollipop recovery. It gives the error as shown in the picture attached, my opinion is that I should have Stock "Lollipop" Recovery to do that, RIght? Than What seems to be the problem?
Thanks in Advance...
Click to expand...
Click to collapse
I have the same problem. I definitely have Android 5.0, root and PhilZ Touch 6.46.3 recovery. So I found out that I have old one, the newest one is 6.58.0 BUT as author Phil3759 said, it is a dead project now and without further updates. So I will try the 6.58.0 and than other custom recovery.
EDIT: Recovery update did not help, still getting 4.4.2 fingerprint.

VinceCZ said:
I have the same problem. I definitely have Android 5.0, root and PhilZ Touch 6.46.3 recovery. So I found out that I have old one, the newest one is 6.58.0 BUT as author Phil3759 said, it is a dead project now and without further updates. So I will try the 6.58.0 and than other custom recovery.
Click to expand...
Click to collapse
I don't think I will work. Starting from lollipop, the update process is not like previous versions. It needs the system partitions to be completely unmodified. That includes the recovery partition and root to be hidden (temporary unroot in the supersu app). I tried to flash ota file with adb sideload and twrp and also cwm (both newest version) and failed. It can only be flashed successfully with stock recovery.

I heard what you are saying from more guys so I will try that.
EDIT: I made unroot and flashed stock recovery but getting error 7, which is basically the same as with custom recovery.

hk.happy said:
I had the same problem. I was on stock lollipop 5.0, rooted, with stock recovery. Tried sideloading the ota (for 5.0 > 5.0.1, about 18mb file) but it gave error. Turned out the mini sdk i was using was old version, 1.0.31. So I downloaded the newer version, 1.0.32, and then was able to update successfully.
Am attaching the rar file here, see if that helps
Click to expand...
Click to collapse
I have a rooted Nexus 4 (SuperSU installed), with stock recovery too. Can you tell me what's the easiest method to update from 5.0.0 to 5.0.1 and KEEP ROOT?

There is no solution yet.

VinceCZ said:
There is no solution yet.
Click to expand...
Click to collapse
Guys, for the ota to work you need to be unrooted and 100% stock recovery, system, and kernel.
Sent from my Nexus 5 using XDA Free mobile app

veketash said:
I have a rooted Nexus 4 (SuperSU installed), with stock recovery too. Can you tell me what's the easiest method to update from 5.0.0 to 5.0.1 and KEEP ROOT?
Click to expand...
Click to collapse
I'm not sure but I think it will break root no matter how you update from 5.0.0 to 5.0.1, and you will have to flash supersu zip again, but again, i'm not sure....

Unroot only and stock recovery is not enough, because than came install-recovery.sh error 7.

VinceCZ said:
Unroot only and stock recovery is not enough, because than came install-recovery.sh error 7.
Click to expand...
Click to collapse
Flash the system, recovery, and boot images from 5.0 in fastboot. Then try the ota
Sent from my Nexus 5 using XDA Free mobile app

I suppose it will delete user settings and all, will it not?

VinceCZ said:
I suppose it will delete user settings and all, will it not?
Click to expand...
Click to collapse
no, it won't delete anything.
Sent from my Nexus 5 using XDA Free mobile app

Shield Update 2.2 is out!

http://shield.nvidia.com/tablet-release-notes/2.2/
now to figure out how to get this to update on my rooted LTE Tablet.....

I'm rooted and just got the update. But haven't completed the update yet as I'm too lazy to reroot.

I tried using the nvidia updater, which failed since it rebooted and CWM had no idea what to do. I made a CWM backup so I am going to see how well it flashes in CWM manually.
I managed to find the OTA download location and have superSU at the ready in my downloads folder in case I have to reflash. the OTA saved as:
/data/data/com.nvidia.ota/files/ROM/shield_tablet_software_upgrade_2.2_-_lte__5.0.1.zip

Someone please report the steps on how to do this for Rooted 2.1.

CWM install zip failed. build fingerprint mismatched, its probably CWM. Will try sideloading stock recovery then installing the zip afterward, I think I remember seeing somewhere here that's how people upgraded rooted devices from 2.0 to 2.1

Omg things seem to be more snappy! The dreaded lag may be gone! I'm not rooted so I did the ota install

I'm really interested in your findings, i need to find a tutorial on how to flash back stock recovery then i can do the update and hopefully reroot.

Iorkca said:
I'm really interested in your findings, i need to find a tutorial on how to flash back stock recovery then i can do the update and hopefully reroot.
Click to expand...
Click to collapse
currently working on it right now, need about a few to upload all files and then get everything setup....

From a post on Geforce forum
fjrichman
*
*
*
*
For rooted users you'll want to use theses.
US LTE Full:*http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_do-full_ota-29979_512.4856.zip
US Wifi Full:*http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29979_512.4856.zip
I successfully updated rooted wifi using link

Awsome sounds good. Quick question to get stock recovery back all id have to do is extract the recovery.img file from the ota 2.1 file i downloaded off nvidia's site and load it like i did the CWM recovery from the root thread right?

Or (if you've got root) wait until the full 2.2 .zip is available, then download it and flash it through your custom recovery, followed by the latest SuperSU. (just like the last Lollipop update).
Interestingly, the OTA update tool has an option for "Check full update" (under the top right menu), but it doesn't seem to return anything...yet...
Sent from my SHIELD Tablet using XDA Free mobile app

Pretty much you are going
Flash Stock recovery by any preferred method
Flash Update
adb Reflash CWM recovery
Thru recovery flash SuperSU
**Profit**
Working on getting all the files in one package as of right now. Damn internet hogs in my house.

Cant we use Flashify to flash stock recovery and then updating the OTA and then reflash our recoverys and supersu.zip?

NaminatoR1254jaime.sier said:
Cant we use Flashify to flash stock recovery and then updating the OTA and then reflash our recoverys and supersu.zip?
Click to expand...
Click to collapse
Yeah, if you have the stock recovery file....

mcord11758 said:
From a post on Geforce forum
fjrichman
*
*
*
*
For rooted users you'll want to use theses.
US LTE Full:*http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_do-full_ota-29979_512.4856.zip
US Wifi Full:*http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29979_512.4856.zip
I successfully updated rooted wifi using link
Click to expand...
Click to collapse
Did you clean install, or did you dirty flash?
Just curious if this can be applied as an update our not.
Sent from my SHIELD Tablet using XDA Free mobile app

masterchiefb117 said:
Yeah, if you have the stock recovery file....
Click to expand...
Click to collapse
I dont
But Im downloading the 2.1 update stock images. Funny how I deleted the 2 gb zip yesterday and now I need it.

masterchiefb117 said:
Pretty much you are going
Flash Stock recovery by any preferred method
Flash Update
adb Reflash CWM recovery
Thru recovery flash SuperSU
**Profit**
Working on getting all the files in one package as of right now. Damn internet hogs in my house.
Click to expand...
Click to collapse
You won't be able to successfully flash the UPDATE .zip file (~94MB) on a rooted (read: modified) Lollipop version.
Recovery version is irrelevant.
You need the FULL 2.2 rom (already found above , ~731MB), flash it in your current custom recovery and re-root by flashing SuperSU again.
Sent from my SHIELD Tablet using XDA Free mobile app

ok, here's what I dug up. If you are rooted and want it NOW, get to it, otherwise wait for someone to clean up the process:
get the OTA from here: https://forums.geforce.com/default/...hread-released-2-17-15-/post/4464815/#4464815
get your latest SuperSU flashable zip: http://download.chainfire.eu/396/SuperSU/
get your recovery ready for reflashing, the OTA will install the stock recovery again. I went with: http://forum.xda-developers.com/showpost.php?p=58864006&postcount=90
boot into recovery and install zip from sideload. then choose either: adb sideload productionBL-droid-signed-wx_na_do-full_ota-29979_512.4856.zip or adb sideload productionBL-droid-signed-wx_na_wf-full_ota-29979_512.4856.zip
reboot and let the upgrade happen, you've lost root and recovery, but you still are unlocked so you just have to reflash them. get into fastboot with power and volume down, then flash recovery: fastboot flash recovery openrecovery-twrp-2.8.5.0-shieldtablet.img
load up recovery and flash the superSU zip and you're back in business.

ShrekOpher said:
Did you clean install, or did you dirty flash?
Just curious if this can be applied as an update our not.
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Wiped cache and davlik then just in case flashed supersu after rom

An Droid said:
You won't be able to successfully flash the UPDATE .zip file (~94MB) on a rooted (read: modified) Lollipop version.
Recovery version is irrelevant.
You need the FULL 2.2 rom (already found above , ~731MB), flash it in your current custom recovery and re-root by flashing SuperSU again.
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
That means a rooted lollipop user with custom recovery, can download the full ota, and dirty flash it, right?