Note: The update packages linked down below are for ARM devices (basically for the Windows RT OS)
After contacting Microsoft, and doing research for at least a few weeks, I found a solution to this major problem.
Alright, so I got a permanent solution for the Windows Update searching disaster!
Step 1: Restore your Surface RT with the recovery image from the microsoft website. (optional)
Step 2: Set up your surface and head to Windows update.
Step 3: Search for updates, after 30m-1h you will see a firmware update, press install without modifying the update list.
Step 4: After the installation got succeeded, and your surface rt restarted go ahead and search again for updates.
Step 5: Again you will see a package of updates, this update includes the Windows RT 8.1 Update 1 update (kb2919355).
Step 6: When you finished installing the updates and your surface rebooted again, go to "installed updates" and check if kb2919355 is installed.
Step 7: If not, try to install the updates again. If yes, start searching for updates again.
Step 7B (Read before doing): IF kb2919355 is not installed and you are stuck on the search for updates part please download THIS file, turn off your WiFi, install the file by opening it, restart when finished and turn on WiFi
Step 8: Once Windows Update is searching for at least 4 hours we came at the point where most of us are stuck.
THE SOLUTION
Step 9: Download kb3173424 from HERE.
Step 10: Download kb3172614 from HERE.
Step 11: Turn off your Wifi, and reboot the surface.
Step 12: Install kb3173424 by opening it.
Step 13: Reboot the surface.
Step 14: Install kb3172614 by opening it.
Step 15: Reboot the surface.
Step 16: Turn on your Wifi, start searching for updates and after 10+/- minutes you will see 180+ updates coming your way .
I hope this helps a lot of people, since it was a major problem on the Surface RT.
Don't forget to hit that donation ehh... Thanks button!
Great work and thanks for the help ill try this on my surface 2 when I have more free time. I basically did that but instead got to the point where I was able to manually install the update 3 (which was about 60 updates in) and just stopped there and blocked updates so I could use the store without errors and use the development tool to run ported desktop apps.
mattschwantes said:
If this really works, you are heroic. How did you figure this out?
Click to expand...
Click to collapse
I restored an image on my surface RT more then 80 times in total. Contacted Microsoft which couldn't do anything and just told me to live with it. And finally came at the conclusion that 8.1 update 1 did something with the Windows update module (still doing research what exactly went wrong with that update).
However I tested this 2 times on my own tablet I can guarantee you this will work!
mattschwantes said:
My friend, you are very dedicated. Much more than MS it appears. I tested your method on a Surface 2 last night. It works great. Excellent work.
Click to expand...
Click to collapse
Glad I could help!
Hmm. I can't say if it is working or not yet. After finally fixing the errors I was getting after a reset (80240440) now I am updating, and after 2 large installs I still have no kb2919355. In fact I don't even have it's pre-requisite of kb2919442. I would really hate to be the guy that discovered this not working for every RT out there. :crying: I will just keep installing large groups until I either get them or it gets stuck again, and I will be absolutely sure to update this for the benefit of others.
Update: It worked, but I had to download and restart 5 separate sets of updates. My theory is that it is tied to the wi-fi connection. I had several errors at first indicating that I wasn't able to connect to the update servers. Internet Explorer worked fine so I went chasing a red herring looking at network settings, firewall etch. Then I brought the Surface from my living room into my office, where the router is, and suddenly it is working perfectly. So my point is, remember that this thing is finicky, and don't take any chances. The community thanks you Stjinchan, awesome job.
CptDraco said:
Update: It worked, but I had to download and restart 5 separate sets of updates. My theory is that it is tied to the wi-fi connection. I had several errors at first indicating that I wasn't able to connect to the update servers. Internet Explorer worked fine so I went chasing a red herring looking at network settings, firewall etch. Then I brought the Surface from my living room into my office, where the router is, and suddenly it is working perfectly. So my point is, remember that this thing is finicky, and don't take any chances. The community thanks you Stjinchan, awesome job.
Click to expand...
Click to collapse
Glad it worked! I love helping people!
Holy cow it works. Thank you so much I've been trying to resolve this issue for weeks. I didn't even have to reformat it.
Stjinchan said:
Alright, so I got a permanent solution for the Windows Update searching disaster!
Click to expand...
Click to collapse
This is awesome, can't wait to test it. But what about the Update 3 for Windows RT 8.1 (KB3097667) ?
I didn't read anything about it in your guide.
Niel86 said:
This is awesome, can't wait to test it. But what about the Update 3 for Windows RT 8.1 (KB3097667) ?
I didn't read anything about it in your guide.
Click to expand...
Click to collapse
After you installed the 2 mentioned updates manually windows update should be fixed and you are able to receive all the updates including update 3 through windows update again.
Stjinchan said:
After you installed the 2 mentioned updates manually windows update should be fixed and you are able to receive all the updates including update 3 through windows update again.
Click to expand...
Click to collapse
Thanks mate, I'll try it ASAP on my Surface RT
I can't manually install the first of the two updates, it say it's not possible to install it. Looks like I miss the 2919355 after the two big bacth of updates.
Any idea?
I'm very surprised and somehow happy to let you guys know that my Surface RT updated itself to the latest Update 3 after few days of downloading updates.
I was ready to follow this new guide, downloaded the manual updates but I've never used it.
I started everything by restoring Windows, keeping all my data and just refreshing WinRT, after that I started the typical updates cycles but something was different. I noticed I was missing the Kb2919355 (update 1), some of the updates were titled "KB **WhateverNumberItIs** without KB2919355", so I was a bit concerned but instead of the KB2919355 my Surface keeped find new updates in a very small time. After another batch of 137 updates, which took almost 3 hours to install, few other not important ones, here I am with my Windows 8.1 RT Update 3.
I really did nothing different from the previous 7/8 times.
Thank you, it works!
Now my Nokia 2520 tablet is back to life.
Not working for my Surface 2
I already have the first update listed to install, but when I try to install the second one it just says searching for updates on this computer...
Is there anything else I can try like resetting it? I just got it today.
amazing
Thank you for detailed instructions.
Advice for others, the key update we're looking for is the only one that ends with "55", so it's easier to search for it, just check the KB numbers in update history until you see it.
Also, another advice, DO NOT lightly install any optional updates. At the end of the process you will see a few optional updates. Please google each and every KB number, some of them caused big problems in the past! I personally installed 3 updates out of recommended list, including the new start menu and some other fixes that no one complained about.
In my case it took a couple days of waiting until my device got and installed the kb2919355 update, and I could take the matter into my own hands.
Now I just installed the two updates, and started searching for updates online.
Let's see where does it take me.
It's a completely new surface RT I purchased for laughable money to see if I could use it as a portable typewriter
For others out there who are still going through the process, the timeline was as follows:
- Friday 4pm I reset the device to official image, and started searching for updates (not connected to my microsoft ID, just local account)
- Friday 5pm I got a message about firmware update, downloaded and installed
- Friday 6pm I set it to search for updates, and left it at work.
- Saturday night I came to check it out, and it told me it wants to install updates. I installed some updates, there was no kb2919355 update, so I set it to search again
- Monday morning I cam full of hopes, the device told me it wants to install some updates, but kb2919355 wasn't among them. I installed whatever was ready, and set it to search again.
- It was still searching at 1pm. I got tired of waiting, and went to power menu. It suggested "Update and restart", so I chose it. It installed 50 updates, kb2919355 was amoung them, but failed.
- I fiddled around for 5 minutes, and it said that 3 updates were available (without searching), kb2919355 among them. Installed them, restarted.
- Then as per instruction, installed 2 updates manually (wifi off) and rebooted.
- searched for updates, took 10 minutes and voila! 161 important updates, and 8 optional.
- took an hour to download all 161 important updates, then about 2 hours to install.
- patience is a virtue! After installation of all 160 updates above, surface offered to do a restart. After clicking the Restart button, it spent >30 minutes with Restarting and a spinning circle. I was pondering about hard-resetting it, but then it started showing progress of update installation, so wait and wait until it does.
- Took about an hour to finalize updates installation. Like I mentioned at the beginning, I installed 3 optional updates (carefully chose them out of the list of 6)
- only then I connected my microsoft account, installed and updated all Metro UI apps (do not start using them before you update them, trust me on this one).
Stjinchan said:
Note: The update packages linked down below are for ARM devices (basically for the Windows RT OS)
After contacting Microsoft, and doing research for at least a few weeks, I found a solution to this major problem.
Alright, so I got a permanent solution for the Windows Update searching disaster!
Step 1: Restore your Surface RT with the recovery image from the microsoft website. (optional)
Step 2: Set up your surface and head to Windows update.
Step 3: Search for updates, after 30m-1h you will see a firmware update, press install without modifying the update list.
Step 4: After the installation got succeeded, and your surface rt restarted go ahead and search again for updates.
Step 5: Again you will see a package of updates, this update includes the Windows RT 8.1 Update 1 update (kb2919355).
Step 6: When you finished installing the updates and your surface rebooted again, go to "installed updates" and check if kb2919355 is installed.
Step 7: If no, try to install the updates again. If yes, start searching for updates again.
Step 8: Once Windows Update is searching for at least 4 hours we came at the point where most of us are stuck.
THE SOLUTION
Step 9: Download kb3173424 from HERE.
Step 10: Download kb3172614 from HERE.
Step 11: Turn off your Wifi, and reboot the surface.
Step 12: Install kb3173424 by opening it.
Step 13: Reboot the surface.
Step 14: Install kb3172614 by opening it.
Step 15: Reboot the surface.
Step 16: Turn on your Wifi, start searching for updates and after 10+/- minutes you will see 180+ updates coming your way .
I hope this helps a lot of people, since it was a major problem on the Surface RT.
Don't forget to hit that donation ehh... like button!
Click to expand...
Click to collapse
On step 7 = if KB2919355 still hasn't installed, do you continue checking for updates or remove whats been updated and start again, ive been trying this for 3 days now
ouatitw said:
On step 7 = if KB2919355 still hasn't installed, do you continue checking for updates or remove whats been updated and start again, ive been trying this for 3 days now
Click to expand...
Click to collapse
Continue checking for updates till you are stuck in the endless search. You should got the *355 update before that loop.
Stjinchan said:
Continue checking for updates till you are stuck in the endless search. You should got the *355 update before that loop.
Click to expand...
Click to collapse
The surface has 196 updates installed, it hasn't found anymore for over 12 hours - it still hasn't found KB2919355, i have reset the machine approx 3 times now and i always get this far only. Is KB2919355 available to install manually ?
ouatitw said:
The surface has 196 updates installed, it hasn't found anymore for over 12 hours - it still hasn't found KB2919355, i have reset the machine approx 3 times now and i always get this far only. Is KB2919355 available to install manually ?
Click to expand...
Click to collapse
Hmm, could you try to install this manually and report back to me if it worked? If so I will add it to the guide.
Stjinchan said:
Hmm, could you try to install this manually and report back to me if it worked? If so I will add it to the guide.
Click to expand...
Click to collapse
Stjinchan................... YOU ARE A LEGEND !..................... it worked, after 5 days of resets and refreshes you have resolved my issues, KB2919355 would never install via windows update itself. I am currently installing 210 updates at present........ I turned off WiFi and installed KB2919355 manually it took approx 40 mins to verify and install, from then i followed from step 9 of your guide and now things are looking good, so far i have 210 updates to install and after approx 3 hours installing as we speak we are at update 184 ...................... so we are almost there. Thank you for providing the standalone KB2919355 file ! That was the problem for me. I am delighted that forums such as XDA help people to resolve issues such as this its just a pity Microsoft themselves cant help more - credit to you STJINCHAN !
Related
Got this method to work to get the update on Rogers Lumia 900.
I have Windows 8/Zune and the Lumia 900.
1- Connect your Windows Phone to a PC and launch the Zune software.. note put the phone in airplane mode
2- Click on Settings/Update. Allow the software to tell you whether an update is
available. If so, skip this guide. If not continue to the next step.
3- Click the check for update button again, and this time immediately disconnect
your computer from the internet. Do this by pulling the Ethernet cable, disabling Wi-Fi, etc. ( I have just disabled the Ethernet adapter) But you should this as soon as the update starts, as your procedure will take some time!!!
4- You should receive a notification that an update is available.
5- Now reconnect to the internet and continue with the update process through the Zune software.
Just to add to it... it updates to 7.10.8779.8 first. Then redo the steps above to get to 7.10.8783.12 .. and then again to 7.10.8858.136 .. which I believe is 7.8
note.. I got the above information from
http://wmpoweruser.com/windows-phone-7-8-update-now-on-zune-regardless-of-carrier-and-model/
This also seems to work on my HTC Radar, but I haven't finished patching it yet. I will post the instructions on the HTC Radar forum.
What firmware did you end up with?
No matter how many times i try to do this method it just isnt working for me, which leads me to believe the update has not yet been pushed to my area.
Worked for me on ATT, it's all about the timing (took three tries to get it to work). I would recommend using the disable adapter method, as it's much easier to disable quickly.
Rennoc said:
Worked for me on ATT, it's all about the timing (took three tries to get it to work). I would recommend using the disable adapter method, as it's much easier to disable quickly.
Click to expand...
Click to collapse
disable adapter?
Open your adapter settings in the OS, after you click the update button in Zune right click on the adapter and click "Disable"
Hi all, I was messing with the Verizon software Upgrade Assistant and managed to upgrade my SM-G930V from 6.0.1 to 7.0. Here are my steps so feel free to give it a try yourself.
DISCLAIMER: I am not responsible if the install fails and your phone is bricked blah blah blah. I also cannot guarantee this will work for everyone.
Let's get started!
1. Plug in Galaxy to computer
2. Pull down notifications and tap USB Charging
3. Select Software installation
4. Find Verizon Mobile in My computer or This PC (It will look like a CD Drive)
5. Run the VZW Software Upgrade Assistant
6. Follow the installation steps on screen
7. Run the upgrade assistant. It will check for an update and download it for you.
8. Change the phone to File Transfer mode the same way as above from the notification menu
9. Click Upgrade! The update files will be sent and your phone will reboot into download mode.
10. Wait as it will take a while. Your phone will reboot to Recovery and install the update now.
11. After another reboot, you will see "Upgrading Android" as it optimizes your apps. This can take a while based on how many you have.
12. You may get a prompt saying some apps must be upgraded. Just follow the onscreen options.
13. You're done! Enjoy android 7.0!
Hope this helped you get the update! Feel free to ask questions. I'm more than happy to help to the best of my abilities. I'm no expert, however.
this is what i had to do on mine......it kept giving me error 402 when I tried to wifi OTA
Thanks OP! The SW update on the S7 Edge I just bought kept stating it was up to date, but it was running Android 6.0. Your steps def solved that issue! One tip was that the VZW SW got hung up forever trying to run some type of update, but the real "VZW Software Upgrade Assistant" that I need to run was hidden down in the systray. I ran that one and all was smooth... didn't even need to open ODIN. lol!
Unlocked?
agapedisciple said:
Thanks OP! The SW update on the S7 Edge I just bought kept stating it was up to date, but it was running Android 6.0. Your steps def solved that issue! One tip was that the VZW SW got hung up forever trying to run some type of update, but the real "VZW Software Upgrade Assistant" that I need to run was hidden down in the systray. I ran that one and all was smooth... didn't even need to open ODIN. lol!
Click to expand...
Click to collapse
I have the unlocked S7 (930U), is it possible to flash it to the Verizon version with this? I'd like to get Wi-Fi calling and Advanced Calling features.
hi all i recently buy a new phone that is Samsung Galaxy S7 and then i used it i come to know that it is Verizon G930V and Converted to G930F.
please someone let me know how i can update my mobile to nougat.?
please help me :'(
it says my firmware is not supported, any other ideas
I bought this phone from second hand, and sadly it had been officially updated to the latest Oreo firmware (A720FXXU9CSKA) so I'm now stuck with binary 9.
I have tried every and each method to enable OEM unlock in my dev options (date trick, MiracleBox and z3x procedures) to no avail :/
I was wondering if I'm really screwed up or if anyone can help me or if anyone has OEM unlocked with binary 9. Thanks for any info!
nevertechdose said:
I bought this phone from second hand, and sadly it had been officially updated to the latest Oreo firmware (A720FXXU9CSKA) so I'm now stuck with binary 9.
I have tried every and each method to enable OEM unlock in my dev options (date trick, MiracleBox and z3x procedures) to no avail :/
I was wondering if I'm really screwed up or if anyone can help me or if anyone has OEM unlocked with binary 9. Thanks for any info!
Click to expand...
Click to collapse
https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
matkali said:
https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
Click to expand...
Click to collapse
That's the date trick I was trying to refer to. Have tried it a few times but not working for me
It finally worked!
Dear lord, I'm finally on Lineage OS. My life is complete now!
I found some steps here. In summary, flashing latest firmware for your binary and then following the steps (verbatim) included in the link did the trick for me. It looks like the date trick works but you need to first set it 10 days behind, then after first reboot set it 10 days ahead, and after the other reboot add it up to 8 days.
After that if you don't see OEM unlock under developer options, give it a day or so and it will eventually show up! By the way, the steps were shared by the user "nacho2018" so make sure to check that info out.
I'm so freaking happy right now lol hope this helps somebody. I really had lost any hope; this is surely the hardest Android device I have ever worked on...
nevertechdose said:
Dear lord, I'm finally on Lineage OS. My life is complete now!
I found some steps here. In summary, flashing latest firmware for your binary and then following the steps (verbatim) included in the link did the trick for me. It looks like the date trick works but you need to first set it 10 days behind, then after first reboot set it 10 days ahead, and after the other reboot add it up to 8 days.
After that if you don't see OEM unlock under developer options, give it a day or so and it will eventually show up! By the way, the steps were shared by the user "nacho2018" so make sure to check that info out.
I'm so freaking happy right now lol hope this helps somebody. I really had lost any hope; this is surely the hardest Android device I have ever worked on...
Click to expand...
Click to collapse
can you explain in more details!
matkali said:
can you explain in more details!
Click to expand...
Click to collapse
For this to work, you must flash the oldest firmware available for your binary version through ODIN.
IMPORTANT: Make sure your SIM card is not inserted before flashing firmware.
How do I know what's my binary version?
Answer below, quoted from a post by @corsicanu on his RMM state issue thread:
You can find out what bl/modem rev you have by checking the current build number of your current rom. Let's take A520FXXU7CRL8 - in this build number 7 is the revision, leave other numbers and letters for some other time. To be able to flash older firmware it must be same revision, or odin will fail. Search on the firmware related websites for older fw of your phone/region that has that same revision. So for the device mentioned before A520FXXU7CRHA is the oldest fw that can be flashed.
Click to expand...
Click to collapse
Once the firmware has been flashed, follow these steps:
Skip everything on the first boot setup including WiFi settings (you'll connect to the Internet later)
Enable developer options and disable automatic system updates from there
Connect to a WiFi network and go to software update under settings and disable automatic software update
Go to date and time settings and select for the time to be set manually. Set the date to be 10 days BEHIND from your current date
Go to developer options and turn it off (click on the right top corner toggle)
Now go to software update and check for a manual update, after result is shown restart your device. IMPORTANT: After the phone has rebooted, your date and time should be reset to the current time automatically
Go to date and time again but this time set it to be 10 days AHEAD, then check for software update one more time and reboot once finished
After reboot, go to date and time and add 8 more days AHEAD (you should be 18 days ahead of your actual date at this point) and perform a software update check once again and restart your phone
As a last step after the final reboot, enable developer options again and OEM unlock should be available!
If this didn't work for you at first try, wait a day or two for the toggle to show up. If you still don't see OEM unlock after those 48 hours, start over and try again.
Thanks
nevertechdose said:
For this to work, you must flash the oldest firmware available for your binary version through ODIN.
IMPORTANT: Make sure your SIM card is not inserted before flashing firmware.
How do I know what's my binary version?
Answer below, quoted from a post by @corsicanu on his RMM state issue thread:
Once the firmware has been flashed, follow these steps:
Skip everything on the first boot setup including WiFi settings (you'll connect to the Internet later)
Enable developer options and disable automatic system updates from there
Connect to a WiFi network and go to software update under settings and disable automatic software update
Go to date and time settings and select for the time to be set manually. Set the date to be 10 days BEHIND from your current date
Go to developer options and turn it off (click on the right top corner toggle)
Now go to software update and check for a manual update, after result is shown restart your device. IMPORTANT: After the phone has rebooted, your date and time should be reset to the current time automatically
Go to date and time again but this time set it to be 10 days AHEAD, then check for software update one more time and reboot once finished
After reboot, go to date and time and add 8 more days AHEAD (you should be 18 days ahead of your actual date at this point) and perform a software update check once again and restart your phone
As a last step after the final reboot, enable developer options again and OEM unlock should be available!
If this didn't work for you at first try, wait a day or two for the toggle to show up. If you still don't see OEM unlock after those 48 hours, start over and try again.
Click to expand...
Click to collapse
Firmware in newer or older
---------- Post added at 06:55 PM ---------- Previous post was at 06:22 PM ----------
The first time you ask to delay 10 days and the second time to delay it again for another 10 days.
step 6- time does not reset to current time automatically
drjis said:
step 6- time does not reset to current time automatically
Click to expand...
Click to collapse
didnt for me either..
Hi,
I have applied firware update for years without problems but today I am stumped.
I tried to update todate from 6ETLL firmware to the newer 6FUBD both Android 11.
Set up Odin using 3.14.4 and started ok.
Then I had the install stopping and disconnecing to the phone.
Eventually I disconnected the phone lead and it now wont boot passed the error message -
An error has occurred while updating the device software.
Use the Emmergency recovery function in the Smart Switch PC software.
So I installed this on my pc it it fails to recognise the phone even in Emmergency recovery mode.
I have tried all methods of trying to reboot the phone but it always comes back to the above arror message and wont go into recover mode or download mode.
I did not but this from O2 but directly from Samsund and its just out of warrantee.
I dont know wheer the service center is in the Uk and thats a lst resort anyway.
Any suggestions please.
Repaste from my other reply on the UI3 update :
"
Odin hates thunderbolt - If you plan on using a USB-C port make sure it's not thunderbolt. It will fail half way in and freeze. Get a well rated cable and do it via USB concentrator directly
If you get stuck and you cannot access recovery via key combo or smartswitch emergency recovery use Odin
Open options and select get device info - It will reboot directly to the recovery if it was previously written (check the log). After that disable the get device info option and reconnect the cable (select files for flashing again - should go smoothly.
If after the reboot and setup you get a moisture warning on the USB port - this does not make nay sense but it works - Turn off the Note, plug in a usb cable on the PC and reboot the phone connected to the cable - It will reset the sensor warning and should work flawlessly.
Hope to have helped - Had a bit of a jarring adventure setting this one up this time.
The lag in the animation is there, however, I think it's the animation timer that is set higher (slower) it's not slow "per se" but it shows. "
Bomm,
I must say.... I dont know how to thank you. Your post saved my Note 10.
I emailed Samsung repair and after 2 days they said phone xxxxx if you need it repaired under warrantee.
I waited a week for the phone to lose its battery and when booted back on charge cane up with the same error.
So I went back on xda and you had kindly posted the exact fix I needed. I didn't expect that. I know now if I have the same issue again. It was my pc I think using usb-c to usb-c like you said. Thank you so much.
I didn't get any warnings at all. booted up fine.
Johny1fin said:
I didn't get any warnings at all. booted up fine.
Click to expand...
Click to collapse
had the same issue. I was stumped at first too
I've tried all the posts but when I say start in odin, the phone restarts and gives an error
As you say you are super, my friend, I applied it step by step, the phone entered the download mode.
Not sure why you want Q or above on the 10+.
I'm still running on Pie/One UI. Fast, very stable and zero issues. Last reload was back in June.
If the OS is running well and fulfilling its mission let sleeping dogs lie.
One issue is if we don't keep up to date then at some point Samsung will stop support on a particular phone and the phone can be years out if date.
They may then be on a version unsupported by the apps suppliers and will be more difficult to sell if you want to buy a new phone.
Johny1fin said:
One issue is if we don't keep up to date then at some point Samsung will stop support on a particular phone and the phone can be years out if date.
They may then be on a version unsupported by the apps suppliers and will be more difficult to sell if you want to buy a new phone.
Click to expand...
Click to collapse
No problem here. All my PCs, their XPx64/W7 OSs as well as my Androids Kitkat/Pie OSs are now unsupported.
No issues and all continue to fulfill their missions.
Forced learning curves waste my time and offer little in return. My last learning curves were from Kitkat to Pie and XPx64 to W7.
I stopped updating with the best versions of both MS and Android. I don't rat's arse if it stays like that for the next 10 years... or if my Windows machines mutate into Pie or Linux machines
Whatever works best for me.
It's not just the bugs that won't get fixed it's the vulnerabilities as well, then the apps stop working. I actually enjoy upgrading my kit and amon Windows 10 21h1. Anti virus packages mat stop working as well.
Johny1fin said:
It's not just the bugs that won't get fixed it's the vulnerabilities as well, then the apps stop working. I actually enjoy upgrading my kit and amon Windows 10 21h1. Anti virus packages mat stop working as well.
Click to expand...
Click to collapse
I've never had a malware or virus issue that required a factory reset in over 7 years of using Android. More than half of the time was using out of date OS's. My current Pie OS is over a year out of date.
99% of rootkits, viruses etc are uploaded by the user. There's no protecting the stupid.
I have redundant complete backups so a factory reset will cost me normally 2 hours and at worst case 6-8 hours if I need to restore the SD card.
You waste far more time then this fighting with the bugs, the learning curve and the forced factory reset that a major firmware update requires.
I get to use the OS of my choice... you get whatever they throw at you and the ride that comes with it.
Trying to get a hold of someone at VZW but thought I would try here.
For business reasons when updating our Tab S4 tablets I need to get them to Update 14 and then stop there-- I reset them and then enroll them in SOTI Mobicontrol to be able to block further updates until we have a chance to test it. Until this morning I could update devices from Update 9 to 10, 10 to 11, and so forth until installing Update 14 and locking it down.
The first two tablets I tried this with today take Update 12 (to Android 10) but then they skip Update 13 and 14 and offer Update 15 only. I reset the device and get the same behavior, no way to get to Update 13. I then tried the Upgrade Assistant software but that also only offers Update 15.
Is there some big issue fixed in Update 15 that is so important that they wont' let me take the intermediate updates?
Thank you,
Matt
mattman10987 said:
Trying to get a hold of someone at VZW but thought I would try here.
For business reasons when updating our Tab S4 tablets I need to get them to Update 14 and then stop there-- I reset them and then enroll them in SOTI Mobicontrol to be able to block further updates until we have a chance to test it. Until this morning I could update devices from Update 9 to 10, 10 to 11, and so forth until installing Update 14 and locking it down.
The first two tablets I tried this with today take Update 12 (to Android 10) but then they skip Update 13 and 14 and offer Update 15 only. I reset the device and get the same behavior, no way to get to Update 13. I then tried the Upgrade Assistant software but that also only offers Update 15.
Is there some big issue fixed in Update 15 that is so important that they wont' let me take the intermediate updates?
Thank you,
Matt
Click to expand...
Click to collapse
Now I'm no expert, but could you download the ODIN firmware files for the 13.1 update and manually update it that way?