Database Users

OTA Update Failed

Hello,
I just noticed 1 hour ago I have 4.3 OTA update for my Nexus 10. However the update has been failed, due to vfxsound mod as far as I understand. I deactivated this app but I cant see OTA update again if I check the system updates manually it states that your system is current(4.2.2). What can I do to have this system update notification again?
My configuration:
rooted (supersu)
CWM recovery
Thank you.

Same here!
mbt28 said:
Hello,
I just noticed 1 hour ago I have 4.3 OTA update for my Nexus 10. However the update has been failed, due to vfxsound mod as far as I understand. I deactivated this app but I cant see OTA update again if I check the system updates manually it states that your system is current(4.2.2). What can I do to have this system update notification again?
My configuration:
rooted (supersu)
CWM recovery
Thank you.
Click to expand...
Click to collapse
I can't update to 4.3 because of the same reason.
In my case, I installed both vfx and vhifi.
I deactivated and turned both of them into safe mode and tried to flash the update with stock recovery.
However, I still got "assert failed: apply_patch_check system/vendor/etc/audio_effects.conf"
There is a way to get the OTA update back, but I repeatedly failed, and ended up with error.
Someone please help us!

This happens because those files have been modified and are no longer the originals. Extract the files it is having issues with from the 4.2.2 factory image, replace them and try again, or just flash system.img from the factory 4.2.2 image and run the OTA again.
Edit: Also, to get the OTA notification again, go to Settings>Apps>All and force stop "Google Services Framework" then "Clear Data". Immediately return to the "About" screen and check for a system update. If any popups come up regarding allowing location services, choose "No" or otherwise don't allow it.
While the system update downloads, remove your google account, and re-add it to avoid any issues with sync, etc. on your google account. Keep in mind if you use 2-factor authentication via google, you'll need to add a new application password for your tablet.

I succesfully upgraded the system. As you said I replaced these file with the original ones. Now It works fine. The only problem is mx player doesnt work. I think they will update it soon.

plastikowl said:
This happens because those files have been modified and are no longer the originals. Extract the files it is having issues with from the 4.2.2 factory image, replace them and try again, or just flash system.img from the factory 4.2.2 image and run the OTA again.
Edit: Also, to get the OTA notification again, go to Settings>Apps>All and force stop "Google Services Framework" then "Clear Data". Immediately return to the "About" screen and check for a system update. If any popups come up regarding allowing location services, choose "No" or otherwise don't allow it.
While the system update downloads, remove your google account, and re-add it to avoid any issues with sync, etc. on your google account. Keep in mind if you use w-factor authentication via google, you'll need to add a new application password for your tablet.
Click to expand...
Click to collapse
Thanks for your guide , my problem is same as above problem with little difference , when I click on OTA update my phone restart and go to CWM recovery and say "it is not safe package , do you want to install ?" I click yes but nothing happened . I also try to get OTA notification back as same as your instruction but nothing happened . please help me . thanks

sabx13 said:
Thanks for your guide , my problem is same as above problem with little difference , when I click on OTA update my phone restart and go to CWM recovery and say "it is not safe package , do you want to install ?" I click yes but nothing happened . I also try to get OTA notification back as same as your instruction but nothing happened . please help me . thanks
Click to expand...
Click to collapse
Did you mean, "phone"? I can only speak for how this behaves on the Nexus 10. Also, if you enable location services (sometimes it tries when the google services framework starts back up) and you allow it, the OTA doesn't seem to show up (at least not for me, perhaps it's region-based?).
I had to redo mine several times while I replaced system files that had been modified, so I know it works if it's done the way I described. 60% of the time, it worked every time.
Also, try removing your custom recovery. I don't know how this affects things for the OTA but it's a factor I didn't have to contend with.

I'm pretty sure he meant tablet. I'm having the exact same problem on my N10.
plastikowl said:
Did you mean, "phone"? I can only speak for how this behaves on the Nexus 10. Also, if you enable location services (sometimes it tries when the google services framework starts back up) and you allow it, the OTA doesn't seem to show up (at least not for me, perhaps it's region-based?).
I had to redo mine several times while I replaced system files that had been modified, so I know it works if it's done the way I described. 60% of the time, it worked every time.
Also, try removing your custom recovery. I don't know how this affects things for the OTA but it's a factor I didn't have to contend with.
Click to expand...
Click to collapse

update on stock rooted

I am on stock rooted MK2 with TWRP recovery installed. I woke up this morning to see that my phone had automatically downloaded the new system sfotware(i assume 4.4.2). The notification cant be removed from the notification bar and just says click to install. i dont want 4.4.2. My wife updated her s4 and it caused all sorts of minor issues with it. She was not rooted however. How can I get rid of the downloaded update and the notification? Also, is there a setting I can change so it wont try to automatically download updates in the future?
thanks

dbenney said:
I am on stock rooted MK2 with TWRP recovery installed. I woke up this morning to see that my phone had automatically downloaded the new system sfotware(i assume 4.4.2). The notification cant be removed from the notification bar and just says click to install. i dont want 4.4.2. My wife updated her s4 and it caused all sorts of minor issues with it. She was not rooted however. How can I get rid of the downloaded update and the notification? Also, is there a setting I can change so it wont try to automatically download updates in the future?
thanks
Click to expand...
Click to collapse
Im sure I will be needing the same information as I am still on 4.3 and want to stay here also, I can tell you I had the same thing with my Galaxy S2 and I remember I had to do something in Titanium backup to stop the update process, but I cant remember the exact steps.
I will be watching this thread closely, Thanks for asking the question!

Search fellas. On the notification . press and hold it. Then you should get a popup of "app info" select it and uncheck "show notification". This will get rid of the annoying update notifications. You can also delete the file from system although I am forgetting right now where.
Sent from my SPH-L720 using Tapatalk

daniel4653 said:
Search fellas. On the notification . press and hold it. Then you should get a popup of "app info" select it and uncheck "show notification". This will get rid of the annoying update notifications. You can also delete the file from system although I am forgetting right now where.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Did that and deleted the file! It downloads it back and the notifications resurrects again.
I froze Configupdater, Sprint Installer, System Update
Disabled System Update on start up.
Dunno what else can stop this OTA notification!!
For me it's even more dangerous because I have the 720T running sacs for 720, hence the update that the system is trying to intsall is the NAE not NAF.
To be on safe side I'm thinking unroot and get to stock MK5 then upgrade to NAF then flash sacs again. This way the update notification will go away. Tedious but thats the only way I think I can get rid of this annoying notification.
Any thoughts?? Keep in mind I'm on 720T

frukyyy said:
Did that and deleted the file! It downloads it back and the notifications resurrects again.
I froze Configupdater, Sprint Installer, System Update
Disabled System Update on start up.
Dunno what else can stop this OTA notification!!
For me it's even more dangerous because I have the 720T running sacs for 720, hence the update that the system is trying to intsall is the NAE not NAF.
To be on safe side I'm thinking unroot and get to stock MK5 then upgrade to NAF then flash sacs again. This way the update notification will go away. Tedious but thats the only way I think I can get rid of this annoying notification.
Any thoughts?? Keep in mind I'm on 720T
Click to expand...
Click to collapse
interesting... I had recently ODIN'd back to stock and saferoot'd before calling it a day and woke up in the morning to an update. I also know that the update only downloads if you're on wi-fi. I know before I ODIN'd I was already saferoot'd with a whole bunch of crapware "frozen" by TiBackup and I never got the update. not exactly sure which crapware I froze, but I did it again this time around and I still haven't seen an update message for the past week. below is a list of what I froze... if you have the time to weed out the exact crapware needed to disable the update, please let me know! would be nice to uninstall the crapware that wont affect the update from happening while cleaning up the rest of the crapware.
1Weather
ANT HAL Service
ANT Radio Service
ANT+ Plugins
BaconReader
BlurbCheckout
Bubbles
CBS Sports
com.sec.enterprise.knox.attestation
com.sec.knox.eventsmanager
eBay
EpsonPrintService
Flipboard
Google Play Books
Google Play Games
Google Play Magazines
Google Play Movies & TV
Google Play Music
Group Play
HP Print Service Plugin
KLMS Agent
KNOX
KNOX Store
Lookout Security
Lumen Toolbar
Messaging+
Mobeam Service Application
Mobile Print
MobilePrintSvc_CUPS
MobilePrintSvc_CUPS_Backend
Phase Beam
Samsung Apps Widget
Samsung Books
Samsung Games
Samsung Hub
Samsung Music
Samsung Print Service
Samsung Video
Samsung WatchON
Samsung WatchON Video
SamsungHub Updater
Share music
Share video
Smart Device Manager
SNS
Sprint - Discover Apps
Sprint Music Plus
Sprint TV & Movies
Story Album
Story Album Widget
TalkBack
Weather Widget
Yahoo! Finance
Yahoo! News

looks like the inevitable just happened... with all the above items turned off/frozen, I still got the OTA download last night! I'm rooted with the hotspot mod and despite all of that, the OTA still came through. the update is located in /cache.

dimm0k said:
looks like the inevitable just happened... with all the above items turned off/frozen, I still got the OTA download last night! I'm rooted with the hotspot mod and despite all of that, the OTA still came through. the update is located in /cache.
Click to expand...
Click to collapse
Indeed! I gave up on OTA block. The only way I can think of if you stop all framework notifications, but I dont want to do that. Got to NAF and CF rooted. Waiting for stable KK before trying it on 720T. I don't care for sparks.

As of last night I hadn't received the OTA update yet, so I decided to try to fend it off buy freezing the system update in titanium backup... I swear I'm at 10 minutes went by and I can I receive the OTA notification! So now it looks like I'm in the same boat right next to you...lol
As I said earlier back in my S2 days I remember having to freeze the "System Update" with Titanium, but I think I also remember having to boot into recovery and Wipe a cache or something, because something is placed in the cache that looks to see if the update was downloaded and installed, and if not just keeps downloading until it is. So the steps that I do remember are;
1) Freeze system update with titanium.
2) Delete downloaded system files (I'm not sure where they are located, so please help me out with this one)
3) Boot into recovery and wipe a cache or two (I can't recall if it was one or more then one, and/or which one) so maybe someone could help with that?
I am going to do some searching for the S2 instructions to see if I can find them, maybe they will help with this.... Not sure if the update process is still the same though.

0Gravity said:
As of last night I hadn't received the OTA update yet, so I decided to try to fend it off buy freezing the system update in titanium backup... I swear I'm at 10 minutes went by and I can I receive the OTA notification! So now it looks like I'm in the same boat right next to you...lol
As I said earlier back in my S2 days I remember having to freeze the "System Update" with Titanium, but I think I also remember having to boot into recovery and Wipe a cache or something, because something is placed in the cache that looks to see if the update was downloaded and installed, and if not just keeps downloading until it is. So the steps that I do remember are;
1) Freeze system update with titanium.
2) Delete downloaded system files (I'm not sure where they are located, so please help me out with this one)
3) Boot into recovery and wipe a cache or two (I can't recall if it was one or more then one, and/or which one) so maybe someone could help with that?
I am going to do some searching for the S2 instructions to see if I can find them, maybe they will help with this.... Not sure if the update process is still the same though.
Click to expand...
Click to collapse
as I stated in my last post, the downloaded update file is located in /cache. for the time being I've deleted that file and created a zero-byte file with the same name and its permissions set to read only. not sure what's going to happen if I try to update with an empty file or if I reboot, but I have it this way to hopefukky assure me that if I accidentally press update that it won't update successfully. I doubt cleaning up the OTA downloads will prevent it from downloading again unless you can somehow fake your version number.

dimm0k said:
as I stated in my last post, the downloaded update file is located in /cache. for the time being I've deleted that file and created a zero-byte file with the same name and its permissions set to read only. not sure what's going to happen if I try to update with an empty file or if I reboot, but I have it this way to hopefukky assure me that if I accidentally press update that it won't update successfully. I doubt cleaning up the OTA downloads will prevent it from downloading again unless you can somehow fake your version number.
Click to expand...
Click to collapse
Doesn't sound like a bad idea! But I can't believe there isn't a fix for this out there though. In my research I found a file for the S2 called fota-killer, you would think something like that wild be available for the S4.

0Gravity said:
As of last night I hadn't received the OTA update yet, so I decided to try to fend it off buy freezing the system update in titanium backup... I swear I'm at 10 minutes went by and I can I receive the OTA notification! So now it looks like I'm in the same boat right next to you...lol
As I said earlier back in my S2 days I remember having to freeze the "System Update" with Titanium, but I think I also remember having to boot into recovery and Wipe a cache or something, because something is placed in the cache that looks to see if the update was downloaded and installed, and if not just keeps downloading until it is. So the steps that I do remember are;
1) Freeze system update with titanium.
2) Delete downloaded system files (I'm not sure where they are located, so please help me out with this one)
3) Boot into recovery and wipe a cache or two (I can't recall if it was one or more then one, and/or which one) so maybe someone could help with that?
I am going to do some searching for the S2 instructions to see if I can find them, maybe they will help with this.... Not sure if the update process is still the same though.
Click to expand...
Click to collapse
OK I tried the fotakill.apk method and so far I have not received the notification like I was eveytime I rebooted earlier go to here http://forum.xda-developers.com/showpost.php?p=30205683&postcount=1 for the instructions I used and a link to the file.... I used the manual method rather then installing the zip thru recovery because they said the zip method is device specific..... I'll stop back in a couple days to update how it's working or b4 that if it doesn't!

0Gravity said:
OK I tried the fotakill.apk method and so far I have not received the notification like I was eveytime I rebooted earlier go to here http://forum.xda-developers.com/showpost.php?p=30205683&postcount=1 for the instructions I used and a link to the file.... I used the manual method rather then installing the zip thru recovery because they said the zip method is device specific..... I'll stop back in a couple days to update how it's working or b4 that if it doesn't!
Click to expand...
Click to collapse
24 hours and still no update message!

OK it's been 4 or do days and this fix worked for me, we have not heard anything from the thread starter so I assume he has also fixed his, thanks for the help guys!

[Q] Once again, Service Temporarily Unavailable

"Service Unavailable - Software update is temporarily unavailable. Try again later."
I swear every phone I've had, at one point or another, gets this message when I try to update. Nothing fixes it, I've tried it all. Only way I've gotten 93% of updates since my Eris is manually installing. In fact I think my first XDA post was how to resolve this, and I just had to do it myself.
So I found the stock KK ROM and, once again, will use Odin to install it and re-root, but why does this always happen? A few times, whatever. Almost all the time, thank God for XDA. Every time....ok what's going on? I backup and FDR before every update to be sure it's as clean as possible.
I've always rooted, but otherwise don't do anything. Is this just me? Does this happen a lot to other people? Is it purely coincidence? I can't find hardly any threads about it for the Note 3...
Basically....WTH?!?!

Last I checked, OTA isn't supposed to work when you're rooted...

ShadowLea said:
Last I checked, OTA isn't supposed to work when you're rooted...
Click to expand...
Click to collapse
The thing with that is I have gotten OTA's when rooted, even ones that removed root. That may have been a phone or two ago though. But the majority of the time I get this. I just don't get it, does everyone else with root only install updates manually? Maybe I should try one of those apps that temporarily unroots so you can install an update...

k1ng r4t said:
"Service Unavailable - Software update is temporarily unavailable. Try again later."
I swear every phone I've had, at one point or another, gets this message when I try to update. Nothing fixes it, I've tried it all. Only way I've gotten 93% of updates since my Eris is manually installing. In fact I think my first XDA post was how to resolve this, and I just had to do it myself.
So I found the stock KK ROM and, once again, will use Odin to install it and re-root, but why does this always happen? A few times, whatever. Almost all the time, thank God for XDA. Every time....ok what's going on? I backup and FDR before every update to be sure it's as clean as possible.
I've always rooted, but otherwise don't do anything. Is this just me? Does this happen a lot to other people? Is it purely coincidence? I can't find hardly any threads about it for the Note 3...
Basically....WTH?!?!
Click to expand...
Click to collapse
OTA is not working when phone is rooted, unroot your phone and try to update.
Sent from my SM-N900 using XDA Premium 4 mobile app

k1ng r4t said:
The thing with that is I have gotten OTA's when rooted, even ones that removed root. That may have been a phone or two ago though. But the majority of the time I get this. I just don't get it, does everyone else with root only install updates manually? Maybe I should try one of those apps that temporarily unroots so you can install an update...
Click to expand...
Click to collapse
These days, Root = No OTA.
The old method was : Enable survival mode in SuperSU (Pro needed) --> Disable Superuser --> Reboot --> Install OTA --> Reboot --> Re-enable Superuser --> Disable survivor mode.
Not sure if it still works though.

How to disable OTA updates with root?

I have rooted my phone and installed Titanium Backup. What processes do I need to freeze to prevent OTA updates from automatically downloading and installing? I tried the usually keywords, but it seems like the only process that might be an updater is ConfigUpdater. Is that all I need to freeze? Thanks.

awdrifter said:
I have rooted my phone and installed Titanium Backup. What processes do I need to freeze to prevent OTA updates from automatically downloading and installing? I tried the usually keywords, but it seems like the only process that might be an updater is ConfigUpdater. Is that all I need to freeze? Thanks.
Click to expand...
Click to collapse
If you're rooted, OTAs won't install anyway.

spotmark said:
If you're rooted, OTAs won't install anyway.
Click to expand...
Click to collapse
Can I stop it from downloading at all? Thanks.

awdrifter said:
Can I stop it from downloading at all? Thanks.
Click to expand...
Click to collapse
I don't think it will automatically download, but you're always going to have the notification telling you an update is available.

So far I've found an option called "Automatic System Updates" in Developer Options, I have turned that off. I guess there's no way to block it from checking for new updates?

I think I've figured out what to block to prevent the update from downloading. I use AdAware to log the DNS requests when the phone is trying to download an update. There where a few URLs, but the one needs to be blocked seems to be redirector.gvt1.com. After blocking this url the OTA update download will pause itself (probably because it can't reach the server). I don't know what other Google services it'll affect, but I've tried downloading an app from Play Store and searching for an address in Google Map, they still work. So I'm going to block that URL for now. I can always temporarily unblock it for certain app updates if they need that redirector url.

Same Problem here
I have a Rooted Lenovo Yoga Tab YT3-850M running Android version 6.0.1, and I am struggling with this same issue. I used TWRP and Magisk.
Even if I enable Developer Options, there is no option to turn off Automatic Updates.
And it keeps downloading and installing the OTA System Updates. It fails to install, but keeps on doing it again and again.
I don't know how to stop it. The only thing is I disabled it from doing the Update over Mobile Data, and I switched off the Wifi to get some relief.
And am now hunting online for some method to either install the OTA, and go back to Root (or) to Disable OTA Updates permanently...

Saro43 said:
I have a Rooted Lenovo Yoga Tab YT3-850M running Android version 6.0.1, and I am struggling with this same issue. I used TWRP and Magisk.
Even if I enable Developer Options, there is no option to turn off Automatic Updates.
And it keeps downloading and installing the OTA System Updates. It fails to install, but keeps on doing it again and again.
I don't know how to stop it. The only thing is I disabled it from doing the Update over Mobile Data, and I switched off the Wifi to get some relief.
And am now hunting online for some method to either install the OTA, and go back to Root (or) to Disable OTA Updates permanently...
Click to expand...
Click to collapse
If you guys are talking about ROM OTA system monthly update, then the solution is very simple.....use FOTAkill

chanh2018 said:
If you guys are talking about ROM OTA system monthly update, then the solution is very simple.....use FOTAkill
Click to expand...
Click to collapse
The solution is even simpler:
There won't be any more monthly QTA updates for this phone anyway, as the company behind the phone went bankrupt and stopped doing updates since February 2020...

Pa9an said:
The solution is even simpler:
There won't be any more monthly QTA updates for this phone anyway, as the company behind the phone went bankrupt and stopped doing updates since February 2020...
Click to expand...
Click to collapse
Yeah, we knew that, but many people don't use Feb because TWRP doesn't work well with it, so they rolled back to Jan, and that's why the OTA kicks in.

chanh2018 said:
Yeah, we knew that, but many people don't use Feb because TWRP doesn't work well with it, so they rolled back to Jan, and that's why the OTA kicks in.
Click to expand...
Click to collapse
All right...sorry, this happens if one is only readying through half the story...
...was already surprised to be the first one to have that mentioned - now this explains it :silly:
Nevermind... :angel:

did anyone find a working solution? I tried FOTAkill but it did not work. I also tried editing the build.prop, but i am still seeing the update icon appear after a few hours.
Thanks,
JD

JudasD said:
did anyone find a working solution? I tried FOTAkill but it did not work. I also tried editing the build.prop, but i am still seeing the update icon appear after a few hours.
Thanks,
JD
Click to expand...
Click to collapse
Where did you put Fotakill? Try to put it in /system/priv-app folder

chanh2018 said:
Where did you put Fotakill? Try to put it in /system/priv-app folder
Click to expand...
Click to collapse
I did try that folder as well, but it's not removing the update. The app also deletes itself upon reboot from /system/app and /system/priv-app
Thanks,
JD

JudasD said:
I did try that folder as well, but it's not removing the update. The app also deletes itself upon reboot from /system/app and /system/priv-app
Thanks,
JD
Click to expand...
Click to collapse
Hmm...that's strange....and you said it's gone after reboot which never happened to me.
Making sure you're using the right version from xda ( and your device is rooted, I assumed)
https://forum.xda-developers.com/showthread.php?t=2249350

chanh2018 said:
Hmm...that's strange....and you said it's gone after reboot which never happened to me.
Making sure you're using the right version from xda ( and your device is rooted, I assumed)
https://forum.xda-developers.com/showthread.php?t=2249350
Click to expand...
Click to collapse
I did the same exact thing 4 times in a row and it is now persistent through reboots. Try number 2 caused magisk to claim no root after reboot. Very weird.
My wife has the same phone and the exact same setup, it took 3 tries to make hers work. Her phone never lost root.
Neither phone is prompting for updates. Very cool! This is a step in the right direction.
Both phones do show the update available notification icon on the right side of the notch. Should this go away as well? I tried multiple cache/dalvik wipes to no avail.
Thanks,
JD

OTA Update failed... both unrooted and rooted!

Hi!
A couple weeks ago, I received an OTA update for my Moto G6+. Like most OTAs before, the phone downloaded it automatically but failed to install it. I was constantly getting a "Update unsucessful" error message every hour or so. Before, doing a factory reset would allow me to install the OTA , so I went through with it every two or three months, whenever there was an update available.
This time, however, I decided to root my phone. Why not. And I did! Magisk installed, Smali-patched to make fake GPS apps work fine, etc. I also unchecked the "Download updates" option in the Developer Options so I wouldn't get any updates (I can't install them, since the bootloader is unlocked now).
... but I still got one. And I'm still getting the same error every time the phone tries to install the update. So, my question is: is there any way to delete that update? I remember reading about a button combination during reboot that sent you to a menu with factory reset settings and all that, and going there would delete the OTA file from your device. I know I did it once. But I just can't find how to do it anymore!
Also, is there any way to prevent updates from being downloaded? I though that setting in the Developer Options would do the trick, but it clearly didn't.

JoeyRavn said:
Hi!
A couple weeks ago, I received an OTA update for my Moto G6+. Like most OTAs before, the phone downloaded it automatically but failed to install it. I was constantly getting a "Update unsucessful" error message every hour or so. Before, doing a factory reset would allow me to install the OTA , so I went through with it every two or three months, whenever there was an update available.
This time, however, I decided to root my phone. Why not. And I did! Magisk installed, Smali-patched to make fake GPS apps work fine, etc. I also unchecked the "Download updates" option in the Developer Options so I wouldn't get any updates (I can't install them, since the bootloader is unlocked now).
... but I still got one. And I'm still getting the same error every time the phone tries to install the update. So, my question is: is there any way to delete that update? I remember reading about a button combination during reboot that sent you to a menu with factory reset settings and all that, and going there would delete the OTA file from your device. I know I did it once. But I just can't find how to do it anymore!
Also, is there any way to prevent updates from being downloaded? I though that setting in the Developer Options would do the trick, but it clearly didn't.
Click to expand...
Click to collapse
To enter fastboot mode just press and hold volume down button while your phone is rebooting. When it's turned off just press and hold volume down + power
The latest OTA updates do not download a .zip file and save it somewhere on your device. It's stored in a cloud.
To prevent your device from starting the update you have to freeze the "Motorola-Updateservices" app.
Therefor open a terminal app and type:
Code:
pm disable com.motorola.ccc.ota

WoKoschekk said:
To enter fastboot mode just press and hold volume down button while your phone is rebooting. When it's turned off just press and hold volume down + power
The latest OTA updates do not download a .zip file and save it somewhere on your device. It's stored in a cloud.
To prevent your device from starting the update you have to freeze the "Motorola-Updateservices" app.
Therefor open a terminal app and type:
Code:
pm disable com.motorola.ccc.ota
Click to expand...
Click to collapse
Thanks. Let's see if that does the trick!