Solving problems by turning 1 incomprehensible error into 2 more manageable ones. I thought this only happened to Linux users.
Recently I was trying to update a Sony Vaio Fit 15E laptop from Windows Insider Slow Ring build 14931 to 14965 via Windows Update. The update would complete downloading and commence installing, but would fail during the multiple reboot process, causing the previous build to be restored.
After ensuring I had no SD cards inserted or USB devices attached, here are the steps I took to resolve it:
Defering Feature Updates
Click Update & Security.
Click Advanced Options.
Check the Defer feature updates box.
Retry the update process.
That didn’t work, so I tried:
Running the Windows Update Troubleshooter
Open Control Panel.
In the View by: dropdown, select Small icons.
Click Fix problems with Windows Update.
Follow the onscreen instructions to fix any problems that are found.
Retry the update process.
That didn’t work either, so I tried:
Deleting the C:\$WINDOWS.~BT folder
Open File Explorer.
Click the View tab.
Check the Hidden items box in the Show/hide ribbon section.
Navigate to the C:\ drive.
Delete the $WINDOWS.~BT folder.
Retry the update process.
That didn’t work either, so I tried deferring feature updates again and rerunning the update process, producing this error:
There were some problems installing updates, but we’ll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x800705b4)
So I tried:
Installing from the ISO instead
Download the latest Slow Ring ISO here. You’ll need to sign in 1st so the page knows you’re a Windows Insider.
Using WinRAR, 7-Zip, or a similar archive extraction tool, extract the ISO file to a folder.
Open the above folder.
Launch the setup file.
Set the installer to keep your apps, files, and settings and let it run.
That didn’t work either, so I tried deleting the C:\$WINDOWS.~BT again and trying to install from ISO as above. This time I got this error:
0x8007042B – 0x4000D The installation failed in the SECOND_BOOT phase with an error during the MIGRATE_DATA operation
Although this error might seem disappointing, it was actually encouraging because it was the 1st one I’d gotten that actually explained what the issue was.
After being unable to get my Subsonic DLNA server to show up reliably in my Xbox One S’ Media Player, I decided to use external storage for video playback instead. I was about to drop $50 on a 128 GB USB stick when I remembered I had a 64 GB Kingston Class 10 UHS-1 microSD card laying around. Buying a USB media card reader seemed like a more efficient solution, so I started looking into doing so.
Apparently – nearly 3 years after Xbox One’s release – no one’s bothered to try this. Or at least they never bothered to write about it, because my Google searches and forum posts turned up nothing definitive.
I wound up having to get a couple readers and try them out myself, and both of them worked. This leads me to conclude that the Xbox One does in fact support media cards via USB readers. That said, you definitely want to get the fasest reader, and the crown for that goes to the Kingston MobileLite G4. This is the only reader I found with USB 3.0 and UHS-II support, which should future-proof you for ultra high bitrate (e.g. 4K) playback given a correspondingly fast microSD card. The G4’s only downfall is it supports SD and microSD only, but when’s the last time you saw any other media card in use in the wild?
You can pick the G4 up for as little as $8.95 online, which is much less than the $50 I mentioned earlier.
Of course you want to return to TouchWiz to fix a problem. Ha, no you don’t.
Note: if you’re not running a custom ROM – i.e. you’re running stock TouchWiz – and need to do this, see Phase 4 only. You’ll need to be rooted.
If you’re running a custom ROM on your S5 and GPS can’t get a fix despite rebooting, battery pulling, flashing new builds, and using all of GPS Status & Toolbox‘s tricks, chances are you’ll need to do rebuild the GPS NVRAM. Here’s how.
Phase 1: Backup your current custom ROM installation.
Instructions (which assume you use TWRP) in Phase 9 here.
Phase 2: Wipe the phone in TWRP.
Boot into TWRP.
Swipe to wipe using the default settings.
Phase 2: Flash the latest baseband in Odin.
Find the latest baseband under the “Odin” heading here.
If you don’t already have one of those, here’s how to get one. If you’re setting up a rooted TouchWiz ROM for the 1st time then you don’t have to restore anything because it’ll already be running, so you can proceed to the next phase.
From the above archive, extract system.img.ext4, boot.img, modem.bin, NON-HLOS.bin, into a new folder on your PC.
Navigate to the folder containing the files from Step 2.
Select all files from Step 2.
In the Add to Archive window that pops up, enter a filename and desired path.
Click the Archive Format dropdown.
Click OK to make the files into a .tar archive
Flash the .tar archive from Step 4 in Odin using the AP slot as described here.
Boot into the ROM and set it up as you would a new phone, including updating all the apps on it.
Boot into TWRP.
Connect the USB flash drive containing SuperSU to the S5 using the USB OTG cable.
In TWRP, tap Install.
Tap Select Storage.
Tap USB Storage.
Select the SuperSU .zip file.
Swipe to flash SuperSU.
And that’s it. This will give you a fully stock, rooted Lollipop ROM you can boot right into.
If you run custom ROMs, the stock ROM is pretty useful to keep handy as some troubleshooting methods (especially advanced ones involving the baseband) work on it only. As such, it’s a pretty good idea to back it up so you can restore it as needed. Instructions found in Phase 9 here.
Microsoft won’t tell you how; they’d rather you buy a new headset.
Note: I can personally verify this works for the Xbox Wireless Controllers with built-in 3.5 mm stereo headset jack only. I don’t know how it works with other 1st party controllers, though the post below indicates that it should.
Basically you need a 2.5 mm TRS female to 3.5 mm TRRS male adapter. The headeset microphone does NOT work with regular 2.5 mm female to 3.5 mm male adapters.
Why write complete documentation when you can just confuse users instead?
If you reboot your PC after a Linux Mint version update (e.g. 17.3 to 18) and find things to be a bit wonky, you’ll need to power cycle the PC. The reason for this is there may have been a kernel version update, and Linux Mint always boots into the latest kernel installed. However, it does this only if the PC is power cycled. If it isn’t, the new Linux Mint build will boot using the old kernel, which causes the problems you may be experiencing.
You’d think this would be in the official version update instructions, but this is Linux, and so caveats are left to unlucky users to discover for themselves.
Radio logcats are useful for troubleshooting network connectivity, especially on modded (rooted &/or custom ROM) devices. If you’re reporting such an issue it’s often useful to provide the radio logcat in addition to the regular logcat to help the developer resolve the problem.
Follow these instructions to set Terminal Emulator to start with root permissions.
Start Terminal Emulator.
Enter logcat -b radio > /sdcard/radio_logcat.txt – This dumps the logcat file radio_logcat.txt at the root of your SD card. logcat -b radio works too, but I have no idea where it puts the file and have never tried it myself.
Reproduce this issue you’re getting the logcat for.
When you’re done with Step 5, close Terminal Emulator.
Navigate to the root of your SD card to find the file there.
Using ADB on your PC
While I know this method exists, I’ve never used it. The command to enter is adb logcat -b radio, and adb logcat -b radio > /sdcard/radio_logcat.txt probably works too.