why the heck well yeas it happened to me 2 Finally I recieved my killswitch. I never had TegraOTA update active...it happened just right after a regular reset with an recovery Image. .I am really sad now I have to apologize! I LOVED MY PYRO!....
This is just a warning keep on the custom side with your pyros! **** that stock Mellow!
Ill try my best to not cry..but heck...
cheers guys maybe someday I'll be back with another pyro!
love
bencozzy said:
My Pyro is stock I asked nvidia to whitelist the serial because it's a development device.
Click to expand...
Click to collapse
U had luck with your request?
bencozzy said:
They told me they did when I requested the Vulkan api build. I also never requested a replacement not sure if that plays into their decision making.
Click to expand...
Click to collapse
Uh, yeah. The whole killswitch process only starts when you fire up your replacement tablet for the first time & set up an internet connection.
That is the ultimate reason why you put your radios to Airplane before flashing, and even before booting, you flash the remove TegraOTA zip file in TWRP.... heck, even a clean flash would be good too.
deleted
daniyo27 said:
That is the ultimate reason why you put your radios to Airplane before flashing, and even before booting, you flash the remove TegraOTA zip file in TWRP.... heck, even a clean flash would be good too.
Click to expand...
Click to collapse
Removing the SIM if you've got the LTE version, clean flashing if using stock images & skipping the WiFi setup. Imo that's the best way to do it, you get all the time in the world to remove TegraOTA whichever way you're comfortable with.
It's honestly a bit sad that some people don't take the time to do this stuff properly.
Here is what I think happened: i had Recovery erased..you know why. So I were on stock with nethunter and suffered from random reboots. That's why I tried reflash it. Once the regular Recovery was installed i got Killswitch es ???*
NVM, just realized he did it through a manual flash, not OTA.
NVM again, I am bad at reading. So he flashed a recovery image then got the OTA after he rebooted. So again, why is Nvidia still pushing this update if they have known it was bricking devices since January.
deleted
Can you explain please all the steps you did until the kill? Ibinstalled 4.1 stock update from.nvidia site on my pyro. Before booting the os i deleted tegraota with the zip and erased recovery with fastboot. But i havent turned on the wifi yet.
Sent from my LG-E975 using XDA Free mobile app
deleted
So now you have the pyro on stock with the original update and connected to internet. But is killed?
Sent from my LG-E975 using XDA Free mobile app
---------- Post added at 08:29 AM ---------- Previous post was at 08:18 AM ----------
The problem is that i cant install a custom rom
Sent from my LG-E975 using XDA Free mobile app
deleted
Can you tell me please which version of xposed? Id like to unstall it. I also freezed with titanium almost all nvidia apps and services. If the kill switch is an update sent by nvidia servers, deleting tegra ota would be safe, and also the recovery, so nothing can be flashed. Did you check if the kill is triggered for your pyro?
Sent from my LG-E975 using XDA Free mobile app
---------- Post added at 08:55 AM ---------- Previous post was at 08:53 AM ----------
So, if the kill is contained in the stock images and you were connected to internet while using the stock image, you would have been affected by the kill switch. But youbsay its working, so i think theres no kill in.the stocks
Sent from my LG-E975 using XDA Free mobile app
deleted
I installed 4.0.1 before the 4.1 and tablet worked (but never cinnected). Can you "system update" on your settings after flashing the nomoreota zip?
Sent from my LG-E975 using XDA Free mobile app
deleted
Its not green. Its the nirmal g updater. When.i.was stock 5.1.2 i deleted manually tegraota apk and "system update" on settings was disappeared. Maybe the g updater is another way to kill the tablet?
Sent from my LG-E975 using XDA Free mobile app
Is your pyro working now?
Sent from my LG-E975 using XDA Free mobile app
Yes?
Related
Might be an answered question. Was just wondering if there's anyway to disable the autoupdate. I like my S4 the way it is right now and don't want any chance that it might autoupdate to android 4.3 which can mess up rooting etc even though i have rootkeeper. At least til issues with new android ver are all clear. So anyway to disable this auto os update? thnx..
Your rooted that's enough to disable I believe cus it wont update if modified. .I might be wrong
Sent from my SPH-L720 using xda app-developers app
And I have never seen my phone's auto update.
w7excursion said:
And I have never seen my phone's auto update.
Click to expand...
Click to collapse
Rooted my nexus 10 and that didn't prevent it from dnlding the update. At least it has the decency not to go ahead w installing the downloaded update. Now I hv this constant notification on the status bar to install it. Don't want this to happen also to S4
4.3 is at least 1-2 months away so I doubt you need to do this. And got a blunt is mostly right. Being rooted will not allow the installation to happen. It will download the update and tell you have a system update but it won't install on its own.
Sent from my SPH-L720 using Tapatalk 4
daniel4653 said:
4.3 is at least 1-2 months away so I doubt you need to do this. And got a blunt is mostly right. Being rooted will not allow the installation to happen. It will download the update and tell you have a system update but it won't install on its own.
Sent from my SPH-L720 using Tapatalk 4
Click to expand...
Click to collapse
So any danger of me inadvertently clicking on the update notification and update happens and wiping out my settings? or rooting won't let it updated at all and to update you have to go back to stock first?
wildpig1234 said:
So any danger of me inadvertently clicking on the update notification and update happens and wiping out my settings? or rooting won't let it updated at all and to update you have to go back to stock first?
Click to expand...
Click to collapse
The only way of being able to update its just having a rooted phone with no mods in someway and also having stock recovery, if you are rooted with a custom rom or mods and have a different recovery then yes if you click the update accidently then you wont have no problem what so ever its just going to abort.
Sent from my SPH-L720 using xda app-developers app
ROMANTiC KiD said:
The only way of being able to update its just having a rooted phone with no mods in someway and also having stock recovery, if you are rooted with a custom rom or mods and have a different recovery then yes if you click the update accidently then you wont have no problem what so ever its just going to abort.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
On my rooted S4 (CF-auto-root), I also have TWRP recovery installed. So this would qualify then as a different recovery? Additionally i also got MF9HotspotMod-Odexed and international SIM unlock on there. So i am guessing all this should be enough to prevent any update?
OTAs won't flash in custom recoveries. If you for some reason hit install update it would boot into recovery and try to install but fail.
Sent from my SPH-L720 using Tapatalk 4
Given that there's no way to reflash the factory image, is it still safe to remove all the AT&T bloat using Titanium Backup? Right now I have all the AT&T bloatware frozen and it doesn't impact anything, but I just want to if it'll change if I completely uninstall the AT&T programs i.e. My Locker, Blurb Checkout, etc. Would this impact my ability to receive firmware updates or unroot and reset the handset? I should mention I'm probably going to be selling the phone when the Nexus 5 comes out so I still want to be able to unroot and factory reset (as long as it can reset, it doesn't bother me if the AT&T bloatware is gone).
I guess that depends on what you mean by "safe."
I removed almost all of the AT&T stuff except for the update service and the hotspot app, and I know I'll never miss them even without a recovery option.
If you need a recovery option, then probably best to not remove anything and use Safestrap to experiment with other roms.
Don't delete it, freeze it. That way if you mess something up you can defrost it.
If your on MF3 I wouldn't touch anything and just use safestrap.
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
There is always risk.
I learned the hard way... I touched too much stuff with Tibu on my stock ROM and it doesn't even work anymore. I can't do anything with it... luckily I have safestrap still until they release an mf3 factory image for Odin or kies I can't do anything with my stock ROM.
Sent from my SGH-I337 using xda app-developers app
jd1639 said:
Don't delete it, freeze it. That way if you mess something up you can defrost it.
Click to expand...
Click to collapse
This
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
I removed all att and samsung bloat except for watch on and several services. We should put a list together of safe package to remove.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
re: safe to remove bloatware
[email protected] said:
I learned the hard way... I touched too much stuff with Tibu on my stock ROM and it doesn't even work anymore. I can't do anything with it... luckily I have safestrap still until they release an mf3 factory image for Odin or kies I can't do anything with my stock ROM.
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
About the time you posted this last night I was freezing apps. Apparently too many. Phone will not boot past the at&t logo now. I can still boot into my custom rom slot 1 so I'm not at a total loss, but would really like to know if there is anyway to replace/defrost those frozen apps on the stock ROM via the ADB terminal running on my custom ROM. Seems like you could just copy and overwrite the package files on the stock ROM... Which leads me to my ultimate question of what does TiBackup Freeze option actually do? Uninstalling would remove the app and files from the system completely so since they are still present it seems there would be some sort of a control file that you could edit manually to defrost the app(s) in question.
Any help on this matter would be greatly appreciated.
I've read a few times that best buy can do a factory restore, yet every time someone says they are going to ask their "friend" at best buy for the method/procedure for the restore they drop off the grid... Is this a possibility?
---------- Post added at 11:31 AM ---------- Previous post was at 11:26 AM ----------
jd1639 said:
Don't delete it, freeze it. That way if you mess something up you can defrost it.
Click to expand...
Click to collapse
As long as you don't reboot it =)
Can you defrost it if you have rebooted and now you can't get past the at&t boot logo?
colbur87 said:
I removed all att and samsung bloat except for watch on and several services. We should put a list together of safe package to remove.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't recall the urls but there are already a few in-depth lists of safe bloatware to remove from our phones..
@xda_n I'm not too sure I'm still researching on this, but haven't really been actively looking for it. Not in a rush really because I'm not going to sell my phone or anything so I'm just going to wait on Samsung to release the mf3 file via Odin or kies. I'm just using vision-x and shostock which is giving me better battery and performance than stock and still have stock feel so I'm not in too much of a rush to fix my stock ROM yet. My stock ROM would boot but it would say com.android. something and it'll freeze. I accidently tried to do a factory reset after deleting all the apps via tibu so I couldn't recover any files I saved and froze so i learned my lesson and don't want to deal with best buy right now.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
MD5.tar!!!
I'm not sure if you guys found this thread or not, but I'm so thankful, I decided to pay it forward and share it. PERFECTO.
http://forum.xda-developers.com/showthread.php?t=2502003
Droid Maxx on 4.4, unrooted (due to update). Every time I try to uninstall any app the phone soft reboots and the app remains. Anyone else experiencing this problem? I've found people in similar situations with devices like the Nexus 4 but their only fix was reflashing stock firmware and I'd prefer to not have to do that... Any solutions?
SORRY; please move to troubleshooting thread this doesn't belong here
Have you tried booting into Safe Mode and uninstalling the app there?
What about using House of Moto to flash back to stock 4.4 with keep data?
I had the same problem. You have to flash the dev image for Maxx 4.4. I'll be home in a few hours and will edit this post with a link if you haven't found it by then.
opt05 said:
Have you tried booting into Safe Mode and uninstalling the app there?
Click to expand...
Click to collapse
Yes i have - same result
I'm in a droid mini using the posted ota and I can install and uninstall just fine. The update you have, is it the one that was pushed officially, or the file from the other thread?
Sent from my XT1030 using Tapatalk
---------- Post added at 12:50 PM ---------- Previous post was at 12:45 PM ----------
Summersett said:
I had the same problem. You have to flash the dev image for Maxx 4.4. I'll be home in a few hours and will edit this post with a link if you haven't found it by then.
Click to expand...
Click to collapse
Had no luck trying to find it. What is the Dev image?
Sent from my XT1030 using Tapatalk
The fix that I used was found in the "Who's gonna leak the Soak Test?" thread: http://forum.xda-developers.com/showpost.php?p=48813998
I recommend reading the other posts in that topic (after the "fix" reply) to see what other uses had to do and what did or didn't work for them. I had to do all steps, including all of the fastboot stuff, to get mine to work, but it did retain all data. Good luck!
just had this issue, go ahead and place the 4.4 ota on your root again and flash it through your recovery menu. Just like you did to get 4.4 originally. You won't lose any files but it will fix your system data which right now is goofed up.
A simple try is to clear cache in system recovery. Can't hurt.
Sent from my XT1080 using Tapatalk
Kickbut101 said:
just had this issue, go ahead and place the 4.4 ota on your root again and flash it through your recovery menu. Just like you did to get 4.4 originally. You won't lose any files but it will fix your system data which right now is goofed up.
Click to expand...
Click to collapse
Worked perfectly, thank you very much
I just followed the guide to flash back to NCG kernel, reroot and flash NE9 kernel. So far everything is lovely except for after a phone call I always get an error: "Unfortunately, Context Service has stopped." Any idea what this is and how to fix it?
wrongway213 said:
I just followed the guide to flash back to NCG kernel, reroot and flash NE9 kernel. So far everything is lovely except for after a phone call I always get an error: "Unfortunately, Context Service has stopped." Any idea what this is and how to fix it?
Click to expand...
Click to collapse
Are you on a custom ROM, if so witch one?
Misterxtc said:
Are you on a custom ROM, if so witch one?
Click to expand...
Click to collapse
No, stock ROM. Never flashed a ROM, Knox 0x0.
I believe I found a solution. I have installed Greenify, but it was disabled under my accessibility services. Apparently that's how it is set by default after downloading it, even when rooted. I turned Greenify on under Settings < Accessibility < Greenify and rebooted my phone. I made a few calls and received one and no more Context Service Errors for me. I am quite curious as to what Context Services are and why Greenify would cause those errors as I do not see any information on it relating to the S5, so if anyone has any idea why this happens, feel free to shed some light on it.I wonder also if Context Services are safe to freeze..
Problem returned with a vengeance after several reboots. Now I boot the phone sometimes and there are no errors, other times and constant FCs. Could I have somehow gotten a corrupt Context Service apk when I flashed to Stock Odin, or the NCG or NE9 kernels? Anyone know what Context Services actually is and if it's safe to freeze if there isn't a fix? I found a similar thread for someone having this issue on the At&T variant and someone replied that his Context Service apk was possibly corrupt and that he PM'd him a new one. http://forum.xda-developers.com/att-galaxy-s5/help/context-services-stopped-t2837895/post54614539 If this is something that is possible to do, I would greatly appreciate it.. I've looked both on Google and here and there seems to be very little info on Context Services, so I do not wanna freeze something that's unsafe to freeze, but these errors are killing me. Any help will be greatly appreciated.
Edit: Totally removed Greenify and the problem is gone. I would love to use Greenify, but I would like to know I can do so without causing issues. Does anyone know how Greenify would cause ContextService FCs?
Logcat
i have a logcat of the issue occurring, both by itself and induced via having my girlfriend call my phone. i took this to the xposed forum first and was told it appears not to be module related. if anyone can give me any input on this, i would really appreciate it
i thought it was just me.. however stock rom works fine for me its my custom build i get the fc on.. i dont have greenify in my rom so not sure if thats the root cause or not.. i will try something and report back
Sent from my SM-G900V using XDA Free mobile app
---------- Post added at 03:46 PM ---------- Previous post was at 03:29 PM ----------
ok so clearing data/cache doesnt help.. i also deleted it and pulled one from stock base pushed and set perms with no luck either.. ill keep searching but were not the only ones with this issue..
mines a deal breaker cuz it fcs after every call as well as i cant send sms lol
Sent from my SM-G900V using XDA Free mobile app
elliwigy said:
i thought it was just me.. however stock rom works fine for me its my custom build i get the fc on.. i dont have greenify in my rom so not sure if thats the root cause or not.. i will try something and report back
Sent from my SM-G900V using XDA Free mobile app
---------- Post added at 03:46 PM ---------- Previous post was at 03:29 PM ----------
ok so clearing data/cache doesnt help.. i also deleted it and pulled one from stock base pushed and set perms with no luck either.. ill keep searching but were not the only ones with this issue..
mines a deal breaker cuz it fcs after every call as well as i cant send sms lol
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
i've figured out if i try to install ANY modules by wanam, the issue occurs. greenify isn't the problem, i know that much. let me know if you find any progress and i''ll do the same for you.
wrongway213 said:
i've figured out if i try to install ANY modules by wanam, the issue occurs. greenify isn't the problem, i know that much. let me know if you find any progress and i''ll do the same for you.
Click to expand...
Click to collapse
i flashed back but can you by chance go to a rom it was working on? ive read somewhere that if you have it working then back it up with tibu then on new rom restore its data and it might fix it.. it doesnt work pullin from rom for some reason
Sent from my SM-G900V using XDA Free mobile app
A rom it was working on? I've only ever been on stock rom in slot 1, not sure what you mean.
Sent from my SM-G900V using XDA Free mobile app
wrongway213 said:
A rom it was working on? I've only ever been on stock rom in slot 1, not sure what you mean.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
so its always fcd since youve got the device?
Sent from my SM-G900V using XDA Free mobile app
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
wrongway213 said:
A rom it was working on? I've only ever been on stock rom in slot 1, not sure what you mean.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
also theres a dif between stock slot and rom slot 1.. im on stock slot
Sent from my SM-G900V using XDA Free mobile app
No, since I flashed back to NCG, rerooted and flashed NE9 it's been happening. I've never flashed a rom, just rooted on stock slot in safestrap
Sent from my SM-G900V using XDA Free mobile app
wrongway213 said:
A rom it was working on? I've only ever been on stock rom in slot 1, not sure what you mean.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
I'm not sure if this will help but from what I've read ss has a problem when using a rom slot instead of the stock slot I've seen a lot of the rom devs change the procedure from using a rom slot to using the stock slot.
http://bit.ly/1brshoa
bad bone said:
I'm not sure if this will help but from what I've read ss has a problem when using a rom slot instead of the stock slot I've seen a lot of the rom devs change the procedure from using a rom slot to using the stock slot.
http://bit.ly/1brshoa
Click to expand...
Click to collapse
yeah i'm in stock slot, not rom slot. didn't mean to post that, but thank you anyways
Anyone know if a Nandroid backup from before I ever originally took the OTA, stock rooted NCG, would fix my problems, and more importantly, if it would trip Knox or not if I restored it via Safestrap?
I haven't read anywhere of someone trying it yet. I was wondering too good question
http://bit.ly/1brshoa
wrongway213 said:
Anyone know if a Nandroid backup from before I ever originally took the OTA, stock rooted NCG, would fix my problems, and more importantly, if it would trip Knox or not if I restored it via Safestrap?
Click to expand...
Click to collapse
lol read the many posts about it floating around.. i restored my ne9 rom just fine many times.. nothing we can do with the vzw s5 will trip knox at this time so dont know why you even mention it lol we cant flash bootloaders
Sent from my SM-G900V using XDA Free mobile app
elliwigy said:
lol read the many posts about it floating around.. i restored my ne9 rom just fine many times.. nothing we can do with the vzw s5 will trip knox at this time so dont know why you even mention it lol we cant flash bootloaders
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
plenty of posts saying safestrap won't trip knox, had not heard from anyone as to what restoring a nano would do until i specifically asked this question yesterday though... you referring to a certain thread containing these many posts? because until i asked, the safestrap thread even made NO mention of nano backups as they relate to knox...
Never had that but I did get documents have stop once an it never did it again not sure what was up with that ?
Is there an actual fix for the "Unfortunately, Context Service has stopped" error? I really made a stupid mistake yesterday and froze some system apps in Titanium Backup. At first I was getting a bootloop when the OS tried to load the apps and thought I was going to have to wipe data, but I used adb push to send the entire system/app folder to my phone (got the files/folder from my wife's phone who has the same phone on same ROM - I'm 90% sure it is the rooted KOT49K/ANCG build of Verizon GS5). This adb push allowed my phone to boot entirely, but now everytime I boot the phone up, I get the Contest Service error message. So I just backed up Contest Service 2.0.3 using Titanium Backup on her phone, then put the 3 files it created onto my phone and tried using Titanium to restore Context Service 2.0.3 to my phone but to no avail. I tried restoring app only and also restoring app+ data but the restore never completes in TB (ive changed TB to INDIRECT mode too) but it doesn't fix the problem. When I start the restore, it does stop the error message from constantly appearing but only until the next reboot.
So does anyone know how I can stop from getting this error message? I have another working Verizon GS5 on the same ROM at my disposal.
Downloads now Available
Full rom for wifi variant
http://ota.nvidia.com/ota/data/post...d-signed-wx_na_wf-full_ota-32256_546.1774.zip
Full rom for LTE variant
http://ota.nvidia.com/ota/data/post...d-signed-wx_na_do-full_ota-32256_546.1774.zip
Instructions :
Have a custom recovery installed preferably TWRP here:https://docs.google.com/file/d/0B3qCG4HlT_xFY0R3RFIxV0YzZTg/edit?usp=docslist_api
Flash full rom image from above
Then supersu for root here: http://download.chainfire.eu/supersu
The install flashify app from here to reinstall TWRP IMG as it rewrites upon flashing firmware https://play.google.com/store/apps/...app&pcampaignid=APPU_1_HrtfVbPRFsvT7AaC84DoAQ
Changeling for 3.0 lollipop 5.1
Yep. Seeing it on my rooted ST. Has anyone found the full update for US LTE yet?
I've just downloaded it. I'll test it tomorrow!
Just got the notification but wont install on twrp so need full ROM to flash
Ok, I have it installed now. I can't say anything about speed yet, but the controller connected pretty fast and updated itself
Just popped up, but I'm rooted with unlocked bl, so waiting for the right version.
Can anyone that's installed it post the build number?
Sent from my SHIELD Tablet using XDA Free mobile app
Installed and first tests are positive. Need more testing though nut will be for tomorrow. Nice birthday present ? !
Sent from my SHIELD Tablet using XDA Free mobile app
---------- Post added at 11:19 PM ---------- Previous post was at 11:05 PM ----------
Here i have LMY47H.32256_546.1774
Sent from my SHIELD Tablet using XDA Free mobile app
I tried downloading Full OTA by replacing build number in link, but it seems its down...
What did you try?
Here's the OTA link since nobody posted it yet:
http://ota.nvidia.com/ota/data/post...ota-from-29979_515.3274-to-32256_546.1774.zip
(For the record, that's for the wireless version)
Anybody remember what was the link format for the full ROMs?
Edit: Never mind.
This should be the full ROM for wireless version:
http://ota.nvidia.com/ota/data/post...d-signed-wx_na_wf-full_ota-32256_546.1774.zip
OM*G just this afernoon i rooted my shield with kingroot andere ofcourse OTA fails .. Grmbl
Sent from my Nexus 5 using XDA Free mobile app
If you're currently rooted, the FULL version is what you'll need to flash in your custom recovery (TWRP, CWM, Phils) - don't forget to ALSO re-flash the latest stable SuperSU.zip in recovery AFTER flashing the full ota .zip and BEFORE rebooting if you want to keep root!
This is the FULL rom for the 16GB Wi-Fi model (says NA, but it's the same for all Wi-Fi models worldwide):
http://ota.nvidia.com/ota/data/post...d-signed-wx_na_wf-full_ota-32256_546.1774.zip
I've downloaded and successfully updated...(755MB). FWIW, my TWRP custom recovery survived the update.
Link to the 32GB LTE model for North America has been updated in the OP above.
32GB LTE ROW (Rest Of World) version is:
http://ota.nvidia.com/ota/data/post...d-signed-wx_un_do-full_ota-32256_546.1774.zip
Sent from my SHIELD Tablet using XDA Free mobile app
An Droid said:
This may be the full rom for North America Wi-Fi:
http://ota.nvidia.com/ota/data/post...d-signed-wx_na_wf-full_ota-32256_546.1774.zip
Downloading now, so can't confirm...
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
I ninja edited at the same time
It's also still downloading for me (relatively slow speed), but judging by the size it should be the correct file.
Didn't flash for me. In twrp
gavin-phelan said:
Didn't flash for me. In twrp
Click to expand...
Click to collapse
I'm guessing you flashed the OTA not full ROM (because there's no way you've already downloaded it), and probably over a rooted system, right?
Sorry your right lol downloading full ROM now
Replacing wf with do seems to get the LTE NA version. Downloading now and will give it a try.
http://ota.nvidia.com/ota/data/post...d-signed-wx_na_do-full_ota-32256_546.1774.zip
Finished flashing. Works perfectly.
An Droid said:
This may be the full rom for North America Wi-Fi (if you're rooted, this is the version you'll need to flash in recovery - don't forget to re-flash SuperSU in recovery after flashing the .zip and before rebooting if you want to keep root):
Downloading now, so can't confirm...(755MB)
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the link! Wish they had a faster server (going between 350-450KBps).
I only rooted after the last update, so let me make sure I have this straight. Flashing this from CWM should update my Shield just like the OTA update would done the way nVidia intended it right (i.e. leave my data and apps in tact)? It's my understanding it will leave the bootloader unlocked but otherwise remove everything that made my phone rooted (CWM and SuperSU). If I didn't reflash the recovery or SuperSU right away, I could do it later, right?
full ota for wifi US flashes fine inTWRP booting now.
Thanks for the links buds