Database Users

Lost 1.141 Update

Hey folks,
maybe someone can help me.
In the morning on my A500 appeared an update available message. I tried to install it, but it failed in the middle. So I got a brick, which I solved with the chinese update. Afterwards I pushed my saved system.img.
BUT: Now the Build Number says Acer_A500_1.112. instead of Acer_A500_1.112.01_EMEA_CUS7
I checked the build.prop but there the correct build number is written.
Also another check of update gimme the message, that my system is up-to-date.
Is anyone able to provide help, like EMEA flexrom.img, boot.img, or some useful advises?

There is a EMEA signed update.zip floating around. Try to restore with that one and see what happens.

I got the same "Update" message (34MB?). I don't know if it was because mine was already rooted. D/L and updated, in the middle the dreadful Triangle with the exclamation mark pops up. Bricked! Did a reboot and try to reapply the update again..Bricked again.
Is this because I'd rooted the tablet?

gotta push flexrom
You gotta push your flexrom image onto the tablet too then "FACTORY RESET". The flexrom (mmcblk0p6) has the information of the update... that is where you are getting the difference from (if i am not mistaken)...
Try that and see if it helps ... I believe it should... jejeje

xo96 said:
I got the same "Update" message (34MB?). I don't know if it was because mine was already rooted. D/L and updated, in the middle the dreadful Triangle with the exclamation mark pops up. Bricked! Did a reboot and try to reapply the update again..Bricked again.
Is this because I'd rooted the tablet?
Click to expand...
Click to collapse
Nope, mine was rooted with gingerbreak 1.20 and worked fine.
did you delete/rename any phone apks???
or delete/rename any stock software???
I have not messed or removed anything, was rooted, root-explorer/titanium loaded and updated without issue.
reran gingerbreak afterwords and all is well....

Have never seen any OTA update in Australia :|

Wish I knew what was inside this update... media player still only sees mp4, mp3... email doesn't allow exchange... I wonder how many updates we will have to wait for to get a few of the things I want?... I didn't root so that I could load updates easily but if I have to try to fix this thing up the way I did my epic then I guess I will...shame they couldn't put divx, wmv, and some other poplar codecs in this... don't they realize some of us bought this to work with too? If exchange was added I would be sorta happy... (I love my A500 short of a couple things)

ive read the update fixes the issue with the PHONE DRAIN... but that is all, there are no other changes that I know of... jejeje

threedfreek said:
Wish I knew what was inside this update... media player still only sees mp4, mp3... email doesn't allow exchange... I wonder how many updates we will have to wait for to get a few of the things I want?... I didn't root so that I could load updates easily but if I have to try to fix this thing up the way I did my epic then I guess I will...shame they couldn't put divx, wmv, and some other poplar codecs in this... don't they realize some of us bought this to work with too? If exchange was added I would be sorta happy... (I love my A500 short of a couple things)
Click to expand...
Click to collapse
Typically I ignore posts that seem to just be complaining, but you seem real torn up about this so... go to settings, accounts, add your exchange account and be happy.

Another thing that can cause the update to hang would be any edits to your build.prop (ie. Netflix early fixes, etc). Changing back to the original resolved the triangular fail icon for me and completed the update with root still installed, gingerbreak did have to be I installed again but root is still attainable.
Sent from my A500 using XDA Premium App

Alright in my case I uninstalled some of the crapware that was on the tablet but then I try to apply the update and get the exclamation. Im assuming it cant update because of the missing apps.

fcmugen said:
Alright in my case I uninstalled some of the crapware that was on the tablet but then I try to apply the update and get the exclamation. Im assuming it cant update because of the missing apps.
Click to expand...
Click to collapse
You are correct, there is a thread in the general fourm with a link to all the apk's that came stock on the system.
I can't post links yet, but either thread about the OTA update you will find your required apk's.

mapaz04 said:
ive read the update fixes the issue with the PHONE DRAIN... but that is all, there are no other changes that I know of... jejeje
Click to expand...
Click to collapse
Full charge, 3 hours... phone 40pct... overall so far more laggy.. nice update

daveid said:
Typically I ignore posts that seem to just be complaining, but you seem real torn up about this so... go to settings, accounts, add your exchange account and be happy.
Click to expand...
Click to collapse
Alright... how long has that been there? THANKS!!!

I have the /system/app folder uploaded if u need it... Here is the link...
http://forum.ppcgeeks.com/acer-iconia-a500/143826-system-app-recovery-acer-a500-iconia-tablet.html
Sent from my T7575 using Board Express

Reset back to stock and still cant update.
Ive only had my a500 for a week. I have not removed/deleted/renamed any of the stock apps. I installed gingerbreak (to root) and thats about it. oh i changed the resolution with LCD density changer. I cant update.
So i reset back to stock and still no luck. Any ideas?

Where u @ gravy? Some people still haven't gotten the update yet. I didn't get it this morning when I tried but am hoping I get it tonite when I get home... jejeje
PS... I'm in tennessee
Sent from my T7575 using Board Express

I was having all kinds of problems not getting the update to run and kept Triangle halt..
I resolved it by the following:
you dont need to do anything with Gingerbreak, its ok. The problem is for those that changed any system files. In my case, i wanted exchange, so i was using a different email.apk, well as learned from another thread here, if you look in Cache/recovery/logs, you will see a file where you can see where the update went wrong. Like i said, in my case, i saw the file size was not what was expected for email.apk. I removed the exchange account, used rootexp and renamed email.apk.old (the original) to email.apk and the obex file then the update worked correctly.
I was going crazy as i was messing with this instead of watching my heat vs the bulls 1st half.

gravyplaya said:
Ive only had my a500 for a week. I have not removed/deleted/renamed any of the stock apps. I installed gingerbreak (to root) and thats about it. oh i changed the resolution with LCD density changer. I cant update.
So i reset back to stock and still no luck. Any ideas?
Click to expand...
Click to collapse
look at your /Cache/recovery/logs for an error and post results

I had to try about 7-8 times looking in the recovery log after each time to see what .apk that i forgot that I had deleted, then put it back and try again. I finally was successful and haven't seen much difference other than no random wake ups. Maybe a little snappier.
I had mine hang in recovery every unsuccessful update which is NOT THE SAME AS BRICKING.

[Q] [Solved] How to update to the latest official firmware?

Hi,
Automatic update does not seem to work (says no updates found) so I've downloaded the latest official 3.1 image from Asus' FTP server.
However I can't manage to install it.
Put the WW_epad-user-8.4.4.5.zip to the Device Storage root through windows.
Then I reboot the eee Pad (got so frustrated that i confused it with an iPad :S) with Volume Down + Power pressed. Then pressing up.
Then I get a progressbar for around a second before a warning triangle shows up.
Any suggestions?

vidarw said:
Hi,
Automatic update does not seem to work (says no updates found) so I've downloaded the latest official 3.1 image from Asus' FTP server.
However I can't manage to install it.
Put the WW_epad-user-8.4.4.5.zip to the Device Storage root through windows.
Then I reboot the iPad with Volume Down + Power pressed. Then pressing up.
Then I get a progressbar for around a second before a warning triangle shows up.
Any suggestions?
Click to expand...
Click to collapse
Its not an Ipad for starters... >,< ''' ok so you get the file you downloaded and go deeper into it until you find the other zip. Then you just put it on your SD card and pop the SD card in your TF. a little triangle with ! should pop up on notification bar. click it and it should tell you to install update. Dont reboot it until it tells you too.

Hi,
Thanks for the info. I put the second zip on the root of the micro sd card (fat32).
However, when I insert the card the TF just says "preparing external storage" and then nothing happens.
Current build is HRI66.WW_epad-8.2.3.9-20110423

vidarw said:
Hi,
Automatic update does not seem to work (says no updates found) so I've downloaded the latest official 3.1 image from Asus' FTP server.
However I can't manage to install it.
Put the WW_epad-user-8.4.4.5.zip to the Device Storage root through windows.
Then I reboot the eee Pad (got so frustrated that i confused it with an iPad :S) with Volume Down + Power pressed. Then pressing up.
Then I get a progressbar for around a second before a warning triangle shows up.
Any suggestions?
Click to expand...
Click to collapse
Power on and voloume down button is for CWM installs so you have made it a bit confusing as to how you are trying to flash the update.
If you have downloaded an official update then you flash it by unzipping the file so that you have a folder named asus in the root of your storage card which contains all the update. You must have this folder or it wont recognise the update but make absolutely sure its the correct update for your model or you may end up with a brick.
Restart the tablet with the storage card plugged in and you should get a notification of an udpate.
I recieved my tablet with the docking keyboard on thursday, rooted, flashed CWM and updated to Honeycomb 3.1 within an hour.
Mark.

Hi, I'm in the same situation as you were : I'm not given the 3.1 update, and i can't find it on ftp.asus.com : there is 8.2.2.6 8.2.3.9 and 8.2.3.13, but no 8.4.4.5, where did you find yours ?
Has it been removed ???

mskip said:
Power on and voloume down button is for CWM installs so you have made it a bit confusing as to how you are trying to flash the update.
If you have downloaded an official update then you flash it by unzipping the file so that you have a folder named asus in the root of your storage card which contains all the update. You must have this folder or it wont recognise the update but make absolutely sure its the correct update for your model or you may end up with a brick.
Restart the tablet with the storage card plugged in and you should get a notification of an udpate.
I recieved my tablet with the docking keyboard on thursday, rooted, flashed CWM and updated to Honeycomb 3.1 within an hour.
Mark.
Click to expand...
Click to collapse
Thanks for clarifying the situation. The ASUS folder was where I went wrong. I just put the extracted zip directly on the root.
MrTweety: The 8445 files are found here as described in another thread: ftp.asus.com.tw/pub/ASUS/EeePAD/TF101/

MrTweety said:
Hi, I'm in the same situation as you were : I'm not given the 3.1 update, and i can't find it on ftp.asus.com : there is 8.2.2.6 8.2.3.9 and 8.2.3.13, but no 8.4.4.5, where did you find yours ?
Has it been removed ???
Click to expand...
Click to collapse
You have to remember that there are different regional versions i.e. us, ww, tw. You can check your version by going to settings and then about. I believe you would need the ww version and I wouldnt recommend flashing a different regional update as it may affect your wifi signal.
If you want ww 3.1 version then you can follow the tutorial in the development section which has a patched stock 3.1 version that works very well.
If you want a stock update then you will have to wait until you get a notification on your
transformer that an update is available.
Mark.

Thanks Mskip. (one more for your counter)
In fact I knew abour regions, I har a ww 2.4.4.5 tablet and i downgraded it into ww2.3.3.13 (so no glitch there, and no problem with wifi channels), but since then (2 days) no notification.
Maybe it's been removed, maybe the server for ww users is down....
Anyway, I prefer a non patched rom for the time being, so i'm downloading the ww 8.4.4.5 that's sill present on the taiwanese asus ftp (alongside with other versions).
But I really wonder why the hell i'm not notified or i can't get the ota update.

The automatic update did not work for me either.
Could be some kind of issue with Asus update services and 3.0.1 devices.
Especially if they removed the update from the global FTP.

Motorola Atrix 2.3 Update was unsuccessful.

I just recently performed an "Over the air" update on my Motorola Atrix in hopes of upgrading to 2.3.
The 200mb file downloaded so I selected "install".
I walked away and then came back to the following error screen:
www [DOT] hardreset.eu/images/nexus_one_android_hard_reset_3 [DOT] jpg
Upon resetting the handset it appears that not only did I experience an error during the update, but now I also will have to re-download the entire file.
Can anyone please advise if there is anyway to manually install 2.3? Surely it's still on the phone somewhere.

**Update:**
I tried downloading the file again but this time backed it up just incase.
It failed a second time so I tried renaming it and doing a manual update.
I received the following errors:
Verifying current system...
assert failed: apply_patch_check("/system/app/MagicSmokeWallpapers.apk", "9870b02dba63f6f0047e4d104329cf4c1d0a48a5", "9870b02dba63f6f0047e4d104329cf4c1d0a48a5", "94389fda652df9e0eaaddf25bbbac0b0dececa1c")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted...
Click to expand...
Click to collapse
I hope someone can shed some light on this!

humanix said:
**Update:**
I tried downloading the file again but this time backed it up just incase.
It failed a second time so I tried renaming it and doing a manual update.
I received the following errors:
I hope someone can shed some light on this!
Click to expand...
Click to collapse
Is the the Telstra over the air update? (as I just did mine yesterday)
It basically means that the update is doing a check to make sure certain files are still in place - in other words somehow or someone has deleted that .apk (is your phone rooted?!) and since the update cannot find it it aborts the process.
I ended up just re-flashing with RSDLite back to stock as I had exactly the same drama (I had removed helpcentre.apk), downloaded the update yet again (third time lucky...) and it worked perfectly.
I also did a full factory reset as well as formatted my internal SD card prior to updating.
Hope this helps

the key question is, have you done any modding to your phone? webtop hack, rooting, anything that would change system files?

geekygrl said:
Is the the Telstra over the air update? (as I just did mine yesterday)
It basically means that the update is doing a check to make sure certain files are still in place - in other words somehow or someone has deleted that .apk (is your phone rooted?!) and since the update cannot find it it aborts the process.
I ended up just re-flashing with RSDLite back to stock as I had exactly the same drama (I had removed helpcentre.apk), downloaded the update yet again (third time lucky...) and it worked perfectly.
I also did a full factory reset as well as formatted my internal SD card prior to updating.
Hope this helps
Click to expand...
Click to collapse
Yes, it's a rooted Telstra Atrix.
I did a re-flash using RSDlite and it did the trick. Thanks!

How to restore to specific stock? (13.3.1.0)

Hey guys,
Currently I have rooted HDX 7" with 13.3.1.0, and I want to return it to a factory-like condition (no root, no traces of anything).
I was wondering if it's possible to restore to specific stock firmware (13.3.1.0) since the new updates are out (13.3.2.1 and now 13.3.2.2)?
I tried the method described here: http://forum.xda-developers.com/showthread.php?t=2582773 and after I edited the build.prop (lowering the build number), rebooted, and then checked for update, it started to download the update "322095220" (which I believe is the latest). I was hoping it would download an update 13.3.1.0, but obviously it started to download the latest version.
What options do I have? Flash the stock firmware via Safestrap? Wouldn't it brick it since it would be writing over itself?
Are there other options?

Kindlik said:
Hey guys,
Currently I have rooted HDX 7" with 13.3.1.0, and I want to return it to a factory-like condition (no root, no traces of anything).
I was wondering if it's possible to restore to specific stock firmware (13.3.1.0) since the new updates are out (13.3.2.1 and now 13.3.2.2)?
I tried the method described here: http://forum.xda-developers.com/showthread.php?t=2582773 and after I edited the build.prop (lowering the build number), rebooted, and then checked for update, it started to download the update "322095220" (which I believe is the latest). I was hoping it would download an update 13.3.1.0, but obviously it started to download the latest version.
What options do I have? Flash the stock firmware via Safestrap? Wouldn't it brick it since it would be writing over itself?
Are there other options?
Click to expand...
Click to collapse
You can't.
If your on 13.3.2.2 keep it in airplane mode for the time being. This tool has a proven way to block ota.

Okay.
Faznx92 said:
You can't.
If your on 13.3.2.2 keep it in airplane mode for the time being. This tool has a proven way to block ota.
Click to expand...
Click to collapse
Apparently you are already rooted or you would not be able to edit Prop. The update that you want you will also find on the same page as the routing utility. Download whichever one applies to you for thor or Apollo drop on your card then erase the one it tried to download out of cache then go back and hit the update button once again it should find the one you downloaded and dropped on your Sd card then factory reset. Then if you're not interested in rooting, turn on airplane mode power off device and give it to whoever wants to use it let them know not to take off airplane mode before rooting or it will force update then who knows..

jimyv said:
Apparently you are already rooted or you would not be able to edit Prop. The update that you want you will also find on the same page as the routing utility. Download whichever one applies to you for thor or Apollo drop on your card then erase the one it tried to download out of cache then go back and hit the update button once again it should find the one you downloaded and dropped on your Sd card then factory reset. Then if you're not interested in rooting, turn on airplane mode power off device and give it to whoever wants to use it let them know not to take off airplane mode before rooting or it will force update then who knows..
Click to expand...
Click to collapse
Correct, I am rooted and still on 13.3.1.0., not on 13.3.2.2.
Awesome, I followed your advice and it worked. Thanks!
For those who want step by step instruction how to make your Kindle HDX "look like new", follow the steps here.
You will also need to modify the build.prop before you try to update.
Then download the update file, drop it on the sdcard (aka Kindle / Internal Storage), reboot and go to the System Updates section and finish the update.
If you don't modify the build.prop, you will get an error "Unable to complete update because the update file is an earlier version than the one on your device".
You will also need to do Reset to Factory Defaults, because even after the update you will still have your icons like Safestrap, SuperSU, but they will not be working without the root.
Now you have a clean Kindle HDX.
Don't forget to disable the updates again if needed!

Kill the kill switch - "ST - yy"

< include generic disclaimer here >
TL;DR
Since update 3.1, Nvidia can force updates (such as the one that bricks your tablet) to be downloaded and installed silently. No guarantees, but:
If you're on stock, delete TegraOTA (/system/app/TegraOTA or /system/priv-app/TegraOTA if you're on 5.0 or newer, or /system/app/TegraOTA.apk if you're still on 4.4) before booting into Android (the attached ZIP file does this for you, but please check with the file manager in recovery before rebooting and let me know if it didn't work), then reboot
Note: you also will need to delete TegraOTA again if you ever install an OTA from Nvidia or a recovery image
If you're not on stock, you're probably safe
EDIT: The urgent OTA is currently not getting sent out to any devices anymore, not even to those who have been getting it before.
EDIT 2: The urgent OTA is now being delivered again, this time named "ST - yy"!
What if my tablet is already deactivated?
Unless you can still boot into fastboot mode (in which case your tablet isn't really deactivated yet), your tablet is probably gone for good. The only way to fix this would be through nvflash, and using it requires the SBK that is unique to each device and that only Nvidia knows, so it's pretty unlikely that we'll ever be able to fix these deactivated tablets.
What/why/how?
In the last OTA (Update 3.1), Nvidia has made some changes to their TegraOTA application. The most important/interesting/suspicious of which is the ability for them to mark OTAs as "urgent". What this means is that these updates will be downloaded without ever notifying the user, and they will be installed without asking the user for permission first. If this is how the kill switch is delivered, all users will see is the tablet randomly rebooting and installing an update, then the tablet would never boot again. As some of you might notice, this would match what has been happening to a few users already, both here and on reddit.
But that's not all. I've been connecting to the OTA servers using various serial numbers (both found and provided to me by a few people) in hopes of actually finding the update that bricks the device. The first serial number I've tried that wasn't mine was the serial number from the screenshot on the recall page. It revealed an interesting "urgent" OTA, named "SHIELD Tablet xx - LTE", which does nothing but flash a blob (which, among other things, contains the bootloader). Many more questions appear now, but the main one is: if this is nothing but a routine bootloader update, why is it marked urgent? And why is it not attached to any Android update? But this by itself is not enough to prove anything, as I could only obtain it with one serial number, so as far as I could have known, it might had just been an internal update or something similar. (update is linked and analysed in the second post below)
Today, however, one of the serial numbers I've been given by some of the people here (thanks for the help guys!) turned out to have the same update waiting for it the next time it connected to the Internet. This rules out the possibility of an internal update, so the next somewhat obvious possibility is that this is the kill switch. Mind you, I still have no direct way of proving this without flashing the ZIP to see what happens (which I'm not planning to do myself), but I will keep checking on the other serial numbers I've gotten to see if this update turns up for them too.
The same person who has given me this serial number has also tested running the old tablet on the latest stock Android version but with TegraOTA removed, and, as expected, the tablet is still working perfectly fine now. Your mileage may vary.
How can I know if the kill switch has been triggered for my tablet?
Go to http://shield.bogdacutu.me/ and enter the full serial number of your old tablet. If the next OTA returned is "SHIELD Tablet xx" "ST - yy", the kill switch has been triggered for your tablet.
Warning: the serial number from the box of the tablet and the one etched on the side of the tablet are not complete, as they only contain the first 13 characters of the full (20 characters) serial number. You can get the full serial number from Android (Settings -> About -> Status), from the bootloader (it will be on the screen when you boot into bootloader mode), or from your computer if the tablet is or (in some cases) if it was previously connected, using various tools such as USBDeview. Example: 0413714803249000a4cf (you can try this on the page and it will return that the kill switch is activated).
Why would I want to also do the fix on my new tablet too?
The update is signed by Nvidia, and communication with the OTA server does not use HTTPS, so, for example, a malicious WiFi network could MITM your connection and cause this update (as well as any other signed update) to be flashed to your new tablet without your permission, thus permanently disabling it too. If you have the stock recovery, only updates signed by Nvidia can run. The story might be slightly different if your recovery doesn't enforce signature verification (such as TWRP and CWM by default).
Can I still get updates from Nvidia after doing this?
Not directly, but people will post OTA download links here on xda when new updates get released. I'd personally recommend that you wait before flashing though until someone here checks the new update to confirm that there's no new way for Nvidia to kill your tablet.
Many hours of work have gone into investigating this. Even if it doesn't help your specific scenario, consider hitting that Thanks button, so that I can at least know it wasn't for nothing.
I'd also like to thank the people who have given me their serial numbers to use for testing again, this wouldn't have been possible without their help: @Beauenheim, @Jackill, and @runandhide05 (who has even volunteered to test removing TegraOTA with the latest update on his old tablet :highfive

Fragments of code from TegraOTA.apk
< screenshots temporarily removed >
Also, from what I've seen so far, the update isn't delivered instantly after activating the new tablet. I don't know exactly what the rule is, but out of the 4 serial numbers that I have, only 2 have this update waiting for them.
EDIT: One more serial number from the ones I have has gotten the xx update. Only one left...
EDIT 2: All the serial numbers I have have the urgent OTA waiting for them now.

"SHIELD Tablet xx" - Update Analysis
OTA URL: http://ota.nvidia.com/ota/data/post...wf-full_ota-32256_554.0168.20150624152335.zip
yy OTA URL: http://ota.nvidia.com/ota/data/posted-roms/uploaded/st---yy--092704233775---7294.20150819152732.zip (if you don't know what you're doing, DO NOT DOWNLOAD THIS, it's very likely that this will permanently brick your device upon flashing it!!!) - also attached to this post in case this link becomes invalid
updater-script is the first file we check:
Code:
getprop("ro.product.device") == "shieldtablet" || abort("This package is for \"shieldtablet\" devices; this is a \"" + getprop("ro.product.device") + "\".");
nv_copy_blob_file("blob", "/staging");
reboot_now("/dev/block/platform/sdhci-tegra.3/by-name/MSC", "");
Suspiciously enough, this only flashes a blob to the staging partition. But what exactly does this blob do, you might ask? Well, the blob actually contains data for 9 partitions, which are automatically replaced during the next boot (before the bootloader does anything else at all, so once you've rebooted, there's no going back) with the contents present in this blob. The 9 partitions are as follows (also detailing comparison with files from update 3.1):
BCT (Boot Configuration Table) - stores some information that is needed for the device to find the bootloader stored on the other partitions, initialize the RAM and some other stuff
Status after update: probably corrupted - the previous OTAs have binary BCTs, but this update replaces it with a text file (which, while it does contain somewhat relevant information, is likely not a valid format). If this is corrupted, it's enough for the device not to be able to boot anymore.
BMP (boot logo) - intact
DTB - intact
EBT (part of the bootloader) - has a zeroed out region
NVC (part of the bootloader) - intact
RBL (part of the bootloader) - has a zeroed out region
RP4 (landscape boot logo) - intact
TOS (Trusted OS - probably part of the bootloader too) - has a zeroed out region
WB0 (related to the boot process, source file is named "nvbootwb0.bin") - has a zeroed out region
The update also contains a few other files, but those are not used at all (probably leftovers from the 5.1 AOSP update template that they are using).
DO NOT DOWNLOAD THE ATTACHMENT IF YOU DON'T KNOW WHAT YOU'RE DOING. THIS IS THE XX OTA, NOT THE ZIP THAT REMOVES TEGRAOTA!

Just as I suspected!!

Thanks a lot this is great. So the silent updater can force updating even with a custom recovery like cwm?
How to install the provided zip?
Thanks again.

tecnoworld said:
Thanks a lot this is great. So the silent updater can force updating even with a custom recovery like cwm?
How to install the provided zip?
Thanks again.
Click to expand...
Click to collapse
CWM and TWRP are both compatible with OTAs, so yes, it can. If you completely erase the recovery (fastboot erase recovery), the update can't get flashed, but the tablet will still reboot (which is at least annoying).
You can flash the provided ZIP through CWM or TWRP (but please check through the file manager if /system/app/TegraOTA still exists after installing it, the ZIP hasn't gone through a lot of testing so it might not work properly in all cases)

tecnoworld said:
Thanks a lot this is great. So the silent updater can force updating even with a custom recovery like cwm?
How to install the provided zip?
Thanks again.
Click to expand...
Click to collapse
This was to be my question too... Normal ota updates will not flash if you have a custom recovery, so how would this silent ota update?

bluegizmo83 said:
This was to be my question too... Normal ota updates will not flash if you have a custom recovery, so how would this silent ota update?
Click to expand...
Click to collapse
Normal OTAs don't work through custom recoveries because they do various checks that usually fail when you have a custom recovery (such as if the system partition is modified, by rooting for example), this urgent OTA has none of those checks

Bogdacutu said:
Normal OTAs don't work through custom recoveries because they do various checks that usually fail when you have a custom recovery (such as if the system partition is modified, by rooting for example), this urgent OTA has none of those checks
Click to expand...
Click to collapse
Oh ok! Great explaination. Thanks for all your hard work on this! I'm flashing the zip now, i'll report back if it removes the file
Edit: Ok I flashed the zip, and TegraOTA is gone. Now I will finally turn on my new tablet and set it up!

So out of interest, what do you think the chances are that thisll work?
How did you find out if the update is waiting? FYI I flashed the ZIP... All is good and it booted fine on LTE 32Gb...
Plus the deleting of the TegraOTA File has gone through... So you really think the TegraOTA removal has stopped it?
How do i check if i have downloaded randomly that update?

Great post. Hopefully that's as far as Nvidia is going to go. I flashed a custom rom on my old tablet. I'm keeping my new one stock but deleting the system app per your post. Just in case Nvidia is spiteful when I don't return the old tablet. I don't want to leave them any option of nuking the new one.

fkofilee said:
So out of interest, what do you think the chances are that thisll work?
How did you find out if the update is waiting? FYI I flashed the ZIP... All is good and it booted fine on LTE 32Gb...
Click to expand...
Click to collapse
Decompiled the OTA application. Using information from there I can connect to the OTA server directly from my PC, and request updates for any given serial number and Android version combination.
I wouldn't have posted this if I weren't relatively confident in my findings

Bogdacutu said:
Decompiled the OTA application. Using information from there I can connect to the OTA server directly from my PC, and request updates for any given serial number and Android version combination.
I wouldn't have posted this if I weren't relatively confident in my findings
Click to expand...
Click to collapse
I know fella I appreciate it. Could you check my second point? 2 x Nvidia Shields would be awesome! One for Work, One For Home

fkofilee said:
Plus the deleting of the TegraOTA File has gone through... So you really think the TegraOTA removal has stopped it?
How do i check if i have downloaded randomly that update?
Click to expand...
Click to collapse
Yes, I think it did. If that update was downloaded on your device, it would have been too late (as it reboots instantly after the update is downloaded), so I wouldn't worry about that.

Bogdacutu said:
Yes, I think it did. If that update was downloaded on your device, it would have been too late (as it reboots instantly after the update is downloaded), so I wouldn't worry about that.
Click to expand...
Click to collapse
So heres an interesting one for you, using a logical mindset, if you receive your new tablet, activate it, the next time that the old one connects to the network, it downloads this update and bricks it? But it wont technically do this until the new tablet is turned on?

fkofilee said:
So heres an interesting one for you, using a logical mindset, if you receive your new tablet, activate it, the next time that the old one connects to the network, it downloads this update and bricks it? But it wont technically do this until the new tablet is turned on?
Click to expand...
Click to collapse
As mentioned in the OP, the update doesn't get delivered immediately after you activate the new tablet. But yes, the old tablet shouldn't get the update before the new one is activated.

Bogdacutu said:
As mentioned in the first post, the update doesn't get delivered immediately after you activate the new tablet. But yes, the old tablet shouldn't get the update before the new one is activated.
Click to expand...
Click to collapse
Sorry fella missed that part, I will be donating some funds when i get paid later this month Mucho Gracias!

Totally not related to this thread, but I just went to setup my new tablet and it's not letting me restore apps & settings from my old Shield Tablet... It doesn't show my old tablet as a restore option. I doubt checked and the old tablet is setup to backup all settings and apps though. Anyone else have this issue when setting up they're new tablet?

bluegizmo83 said:
Totally not related to this thread, but I just went to setup my new tablet and it's not letting me restore apps & settings from my old Shield Tablet... It doesn't show my old tablet as a restore option. I doubt checked and the old tablet is setup to backup all settings and apps though. Anyone else have this issue when setting up they're new tablet?
Click to expand...
Click to collapse
Upgrade to 5.1 on the new tablet without restoring any data, then do a factory reset and you should get the option to restore

Bogdacutu said:
Upgrade to 5.1 on the new tablet without restoring any data, then do a factory reset and you should get the option to restore
Click to expand...
Click to collapse
AWESOME man, thank you!!