What is the difference between OTA update and Kies update??
Firmware Over The Air(FOTA or just OTA) allows you to update your firmware directly from your phone without needing a 3rd party software(like Kies or Odin).It finds only the files that need to be updated and sends those to your phone instead of reinstalling your entire firmware.Because of this OTA's are often small and don't reinstall bloatware you have removed or affect your root.Kies is Samsung's proprietary software used to connect the phone to your PC and perform tasks like update your FW and other stuff similar to iTunes with Apple.On the contrary,when you connect your wonder to Kies on your PC,it first determines if your FW is up-to date.If there's a newer FW available it will reinstall the entire FW.You're apps and data will be safe but all system apps will be installed back to stock.Some updates come via Kies only.Also updates usually take longer to 'roll out' OTA as they want to control the load on their servers.So you might not yet get an OTA notification on your phone despite other people with the same device having it.It just hasn't reached your turn. You can check for OTA's by going to Settings-->About Phone-->Software Update.
Sent from my Wonder
2g11 said:
You can check for OTA's by going to Settings-->About Phone-->Software Update.
Click to expand...
Click to collapse
You can reach the Software Update menu just dialing this secret code:
Code:
*#8736364#
If you go this way, you don't need active SIM Card nor Samsung Account as if you go through Settings-->About Phone-->Software Update
Related
A new update is available for kies. Launch your kies on pc and you will be promted to upgrade
to the new Kies 2.0.3.11082_152 version.
As normal with any Samsung kies update, you may receive "network disconnected" errors while updating.
Just be patient. Upgrade process takes about 4 minutes to complete.
On the outlook (UI), there is no notice change. But maybe new drivers were introduced to enable to "not-yet-known" upgrade process to bada 2.0.
After installing this hotfix every apps are signed as free of charge (of course they're not, and when trying to buy any of them error occurs).
Doublechecked by installing previous version and this hotfix (as there is still no standalone version).
that update didn't appear into my kies until now!!!!
A request from persons who updated : please check if sp**fing hole is patched or not
Is the installing app just once is still in there???
Is kies more buggy now???
Best Regards
@mylove90
Checked, sp**f works like a charm. The issue which unables reinstalling apps is still there.
But reinstalling the apps works in KIES 1.5.
It seems the problem is in KIES 2.0, not the server.
oh ****
they are fixing bugs with bugs or what?!
i don't get it !!!!!!
i think maybe i'll hold and won't update to this useless update
thanks Qron for the news
Best Regards
Updating now...
It's not connecting to my SGS after the update
new kies version detects beta and custom roms. bad thing.
Send a screenshot of the Bug to Samsung tech support
I got email from Samsung customer service since i complained about the reinstall bug.
They have no idea that kies is doing this and therefore they have asked for screenshots to prove it.
So go to the samsung website then log in then go to my page and then on the left click my q & a.
Send them the screenshot and make your complaint.
They are adamant that KIES is not supposed to prevent you from reinstalling your apps paid or free so its good that they confirmed that this was not their intention.
In the complaint mail I sent to Samsung on 22nd Sept, I included two screenshots.
They replied me that they are already investigating the case.
Maybe Samsung has no central co-ordinating unit to attend to complaints of clients,
each country attends to complaints separately. Just maybe...otherwise why ask for more screen shots.
Well..in that case i'll give them a complaint too & make them wake up
Kies Devs aren't working with Samsung Apps Devs
So maybe Kies Devs are making bugs while Samsung apps Devs have no idea what they did
i hope i am wrong and they are all connected
Best Regards
I have nothing but problems with the new Kies. Couldn't find phone after update, then it said drivers didn't work anymore, got it working by reinstalling drivers again but now it can't find the phone again...!
Didn't think they could make Kies any worse, guess I was wrong
Not able to update my FW through kies after moving from KH3 -> DDJE7->ddJH1->ddkd1
Not able to update my FW through kies after moving from
XXKH3 -> DDJE7->ddJH1->ddkd1 from samfirmware.. kies still shows that "The FW of this device cannot be updated"...plz reply if anyone know the fix for this..
amanjit said:
Not able to update my FW through kies after moving from
XXKH3 -> DDJE7->ddJH1->ddkd1 from samfirmware.. kies still shows that "The FW of this device cannot be updated"...plz reply if anyone know the fix for this..
Click to expand...
Click to collapse
You need to flash to any full firmware of your region.
After flashing, go to admin mode, pre-configuration setting, and install the correct csc for that region.
Then kies will be able to update your phone again.
Best of luck.
After updating Kies to 2.0.3.11082_152 on my Samsung Galaxy S2 , DeviceDataService crashes , cant do any file transfers, ironically kies reads the phones contact data. Whats going on with kies ? earlier before this upgrade it was slow but used to work fine...
I am having a problem which I think started only when I last updated kies, it gave me errors that phone not detected I restarted the computer then finally got it detected but now when I disconnect the media scanner on phone does not run hence the following problem.
1. From Camera / video camcorder window I cannot access the gallery anymore. My gallery is on External 32gb sd card.
2. Custom ringtone changes randomly then again (sometimes) its back to my preset default. (internal sd card)
I have custom folder named "my ringtones" in which mp3 files are there to set as my default ring tone & 2 of the groups use custom ring tone so I can identify which group is calling.
Now this folder is on internal SD card & its there for sure but the default ringtone set losses its setting & change to stock rom default ringtone & then I can even see my ringtone folder from settings/sound/phone ringtone & don't know how to set custom ringtone unless it shows.
Any way to force the media scanner, I don't know how it got disabled.
Seems new Version availabale 2.1.0.11095_121
Not tested yet...
Best Regards
admin mode?
spacks said:
You need to flash to any full firmware of your region.
After flashing, go to admin mode, pre-configuration setting, and install the correct csc for that region.
Then kies will be able to update your phone again.
Best of luck.
Click to expand...
Click to collapse
how can I go to/in admin mode? pls
adfree said:
Seems new Version availabale 2.1.0.11095_121
Not tested yet...
Best Regards
Click to expand...
Click to collapse
The only new thing as i see is the Podcast store
It looks so cool but no idea if we will find useful stuff in it
Best Regards
Hello
I just fresh installed the latest pre-rooted firmware (thanks as always rbox.. beer on me incoming!) and I forgot to do the "yank the ethernet cable" trick to get past the initial update. My router has the domains blocked and previously they were working fine, so I would have expected the check to fail, but it happily went though to the registration screen. Of course there are no updates since this is the latest, so no harm done this time round, but just wondering if any domains may have changed?
Also checking update status in "About" and it says last checked today (normally it just says "Checking now...."). When I click on Check for Updates, it says there was an error. Which suggests nothing has changed, but I'm confused by the above.
The other possibility is that the new firmware doesn't hang on checking for updates, so if it fails it just goes through anyway (good for peeps who are having internet trouble, etc).
Anyone else have this experience? I have updates disabled so not too worried, but just wondering for future reference in case I need to fresh install and a newer update is out.
Cheers
Try downloading the update through aftvnews, it may be your firewall isn't blocking it.
I just discovered my Asus router wasn't blocking the updates until I re-enabled the firewall.
edit:
Or may because you're on the latest update it skipped the update.
eskay993 said:
Hello
I just fresh installed the latest pre-rooted firmware (thanks as always rbox.. beer on me incoming!) and I forgot to do the "yank the ethernet cable" trick to get past the initial update. My router has the domains blocked and previously they were working fine, so I would have expected the check to fail, but it happily went though to the registration screen. Of course there are no updates since this is the latest, so no harm done this time round, but just wondering if any domains may have changed?
Also checking update status in "About" and it says last checked today (normally it just says "Checking now...."). When I click on Check for Updates, it says there was an error. Which suggests nothing has changed, but I'm confused by the above.
The other possibility is that the new firmware doesn't hang on checking for updates, so if it fails it just goes through anyway (good for peeps who are having internet trouble, etc).
Anyone else have this experience? I have updates disabled so not too worried, but just wondering for future reference in case I need to fresh install and a newer update is out.
Cheers
Click to expand...
Click to collapse
Just an observation...you shouldn't need to do the Ethernet trick with custom recovery when updating prerooted firmware. It will check for updates then nothing should happen.
I've been running the same prerooted firmware for a long time so my memory isn't perfect but I thought just updating it wouldn't take you to the registration screen??? Unless maybe this new firmware isn't set up like rbox's. Are you saying you had to setup your account, check adb and unknown sources, reinstall apps, etc? This would occur if you wiped data before installing the update maybe...
Anyways. If it running OK I wouldn't worry much about it.
KLit75 said:
Just an observation...you shouldn't need to do the Ethernet trick with custom recovery when updating prerooted firmware. It will check for updates then nothing should happen.
I've been running the same prerooted firmware for a long time so my memory isn't perfect but I thought just updating it wouldn't take you to the registration screen??? Unless maybe this new firmware isn't set up like rbox's. Are you saying you had to setup your account, check adb and unknown sources, reinstall apps, etc? This would occur if you wiped data before installing the update maybe...
Anyways. If it running OK I wouldn't worry much about it.
Click to expand...
Click to collapse
Thanks for the reply. Yes I did a complete fresh install / format data etc. Wanted to start fresh. I have done full wipe install with rbox's previous firmware in the past and I did have to do the ethernet trick to get to the registration screen. But not with this latest. My guess is Amazon have changed it so that it doesn't just hang if it encounters an error at the stage. Or something else has changed.
My router is definitely blocking the servers. Once I am in KFTV launcher, it shows they are being blocked (updates just says "Checking now..."). So probably nothing to worry about, just wanted to be ready, so to speak, in case I need to do another fresh install in future.
eskay993 said:
Thanks for the reply. Yes I did a complete fresh install / format data etc. Wanted to start fresh. I have done full wipe install with rbox's previous firmware in the past and I did have to do the ethernet trick to get to the registration screen. But not with this latest. My guess is Amazon have changed it so that it doesn't just hang if it encounters an error at the stage. Or something else has changed.
My router is definitely blocking the servers. Once I am in KFTV launcher, it shows they are being blocked (updates just says "Checking now..."). So probably nothing to worry about, just wanted to be ready, so to speak, in case I need to do another fresh install in future.
Click to expand...
Click to collapse
I tested this out. With the latest firmware that was just released by rbox. The update still shows the same error as before. After every update. I ensure that I disable the update service via SU and the update links are blocked on my router anyways. I don't do opendns as I believe in manual physical blocking.
so I rooted my galaxy tab s 8.4
I rooted and saw it installed super su. I went and ran super su to install the binarys but all it asked me to do is disable knox. which I did and was successful. I then installed twrp and that went fine. since I'm still on stock. How do I disable OTA updates? thank you in advance.
I don't know if it is the correct way to do it, but I just froze the two files called software update in the system files and one called fwupdate (I think). I can get you the correct names of the files tonight.
As promised, here are the three things I froze:
2 x Software Update
1 x FW Upgrade
Though I think you may only need to disable FWupgrade. I have just enabled the two called 'Software Update' and they seem to be connected to app updates and not OTA.
Ross_L said:
As promised, here are the three things I froze:
2 x Software Update
1 x FW Upgrade
Though I think you may only need to disable FWupgrade. I have just enabled the two called 'Software Update' and they seem to be connected to app updates and not OTA.
Click to expand...
Click to collapse
I found the two softare upgrade files and froze them with rom toolbox lite.
I could not find the FW upgrade file you are referring to.
The app I used is called 'Root App Delete' and it is available on Google Play. If you install that, then go into System Apps and select Junior mode (to freeze rather than delete), it should show in that list.
You won't be able to ota with Root and/or custom recovery installed. There's nothing to do.
Also be very careful when deleting system apps.
Ensure you have made a system backup in recovery.
A couple hours ago my phone with unlocked bootloader, twrp and magisk root installed an OTA update without me initiating it. This failed and the phone was stuck in twrp recovery and couldn't boot until I flashed a stock rom through fastboot and restored my backups.
Now I want to prevent this from happening again. How do I block the phone from checking for OTA updates?
I will have to install them manually anyway so the OTA checking is not helpful.
Same thing happened to me except I was dumb enough to try and install myself the update... You can install Titanium Backup and freeze the Motorola Update app. Also, you can go under dev options and disable automatic updates (this alone didn't work for me).
How to prevent OTA updates, without root, please?
I followed this guide, the method 4 worked for me when my phone was rooted.
http://www.droidviews.com/disable-ota-notifications-android-devices/
With help from the Google, I finally recalled how I'd done it in the past.
Initially, I thought rooting would stop OTA updates, but that may have been prior to Marshmallow or with SuperSU.
This time, I used Titanium Backup (must be rooted) to freeze the MOTOROLA UPDATE SERVICE app.
As soon as it was frozen, the OTA notification disappeared from the notification bar and I gave not seen it return, for a couple days.
Yay! I didn't want to go beyond the stock firmware version that is available and I really didn't want Oreo.
Another way is to use a firewall app.
Also you can just add Motorola's address to your 'host' file to block it
Im the opposite, I want the notifications, without the automatic installation.
Wonder if I changed the permissions of the folder the updates download to, would that prevent automatic install?
also, there is an option in developer options, to turn off OTA.
I have an unlocked Fold 3, purchased directly from Samsung. When I try to do the OTA update to Android 12, after the reboot into the updater (the robot screen), it fails every time at 25% and then reboots back into 11. I have verified Google play services are up to dare.
Anyone have an idea other than doing a factory reset and then trying?
TechnoLawyer said:
I have an unlocked Fold 3, purchased directly from Samsung. When I try to do the OTA update to Android 12, after the reboot into the updater (the robot screen), it fails every time at 25% and then reboots back into 11. I have verified Google play services are up to dare.
Anyone have an idea other than doing a factory reset and then trying?
Click to expand...
Click to collapse
Are you taking an OTA update that was pushed to your phone? Or are you trying to manually update it?
If it's the OTA, use Odin to do a fresh install. You will likely end up losing stuff but that makes it a clean install. Backup everything, screen shots for things you can't just backup, and you should be back in the saddle.
There's not much else you can do via OTA. Even Sammy will suggest a reset, but they aren't much help anyway.
Try using Samsung smart switch through a pc. Connect your phone to pc and there you can select update and it shall update your phone. Hopefully this will pass without issue.
Samsung Smart Switch
Samsung Smart Switch seamlessly transfers contacts, photos, music, videos, messages, notes, calendars and more to virtually any Samsung Galaxy device.
www.samsung.com