tag:blogger.com,1999:blog-89328073071572685102024-03-13T12:19:20.863-07:00PlaygroundUnknownnoreply@blogger.comBlogger4125tag:blogger.com,1999:blog-8932807307157268510.post-74323098502098216032018-06-03T18:56:00.002-07:002018-06-03T18:56:12.313-07:00Notes on Repairing/Recreate Windows 10 EFI Bootloader without ReinstallationFor whatever reason, my windows installation has its bootloader on a different drive. i.e., say the windows 10 is on disk 1, but its bootloader is on disk 0. The computer has to access disk 0 in order to have disk 1's OS running.<br />
<br />
Unfortunately, my boot drive is finally dead yesterday, so I was unable to boot up despite the OS itself being good.<br />
<br />
Here are few steps I did:<br />
<br />
<ol>
<li>remove the dead disk 0. (with disk 0 connect, my BIOS would stuck at POST)</li>
<li>boot into ubuntu live CD, use GParted to move the OS partition and make a room of 500MiB before it</li>
<li>Create the EFI partition. it is just a FAT32 partition with boot label. </li>
<li>use a windows 10 installation media, hit shift+F10 to enter cmd, then use <span style="font-family: "Courier New", Courier, monospace;"></span><br /><blockquote class="tr_bq">
<span style="font-family: "Courier New", Courier, monospace;">"bootrec /RebuildBcd"</span></blockquote>
<span style="font-family: "Courier New", Courier, monospace;"></span><br />to create the bootloader</li>
<li>For whatever reason, now I can see the bootloader, but it somehow won't get me into windows 10. So now I used the windows 10 installation media's repair tool, and it automatically repaired it. (note I tried using this step before everything else, but it won't work until I create the EFI partition manually)</li>
<li>Done</li>
</ol>
<div>
<br /></div>
<div>
<br /></div>
Feiyanghttp://www.blogger.com/profile/12187496900408316319noreply@blogger.com2tag:blogger.com,1999:blog-8932807307157268510.post-59360260874749018942017-04-19T17:04:00.002-07:002017-04-19T17:04:47.457-07:00Notes on Using the same Bluetooth LE Mouse (Microsoft 3600) with Windows and Linux without Re-paring<span style="font-family: Courier New, Courier, monospace;">This note intends to collect the key steps of my implantation. It is mainly instructed and inspired by this post as well as its comments: http://console.systems/2014/09/how-to-pair-low-energy-le-bluetooth.html</span><br />
<span style="font-family: Courier New, Courier, monospace;"><br /></span>
<span style="font-family: Courier New, Courier, monospace;">The idea generally is to have the mouse working with windows, and then copied its credentials to linux.</span><br />
<span style="font-family: Courier New, Courier, monospace;"><br /></span>
<span style="font-family: Courier New, Courier, monospace;">My OSs are windows 10 64bit and Ubuntu 16.04 64bit with 4.10 kernel;</span><br />
<span style="font-family: Courier New, Courier, monospace;">Mouse is Microsoft 3600</span><br />
<span style="font-family: Courier New, Courier, monospace;"><br /></span>
<br />
<ol>
<li><span style="font-family: Courier New, Courier, monospace;">have bluez and blueman installed in linux (so it works with BLE mouse)</span></li>
<li><span style="font-family: Courier New, Courier, monospace;">pair the mouse with linux and then windows. (so it is working in windows)</span></li>
<li><span style="font-family: Courier New, Courier, monospace;">extract credentials from registry. (use "psexec -s -i regedit", find and export as txt: "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\BTHPORT\Parameters\Keys\<MAC of BT adapter>\<MAC of BT mouse>")</span></li>
<li><span style="font-family: Courier New, Courier, monospace;">Fill the credentials to Linux ("/var/lib/bluetooth/<MAC of BT adapter>/<MAC of BT mouse>/info")</span></li>
<li><span style="font-family: Courier New, Courier, monospace;">Restart BT service ("/etc/init.d/bluetooth restart")</span></li>
</ol>
<div>
<span style="font-family: Courier New, Courier, monospace;"><br /></span></div>
<div>
<span style="font-family: Courier New, Courier, monospace;"><br /></span></div>
<div>
<span style="font-family: Courier New, Courier, monospace;">Below are detailed mapping and manipulation for step 4 above:</span></div>
<div>
<ol>
<li><span style="font-family: Courier New, Courier, monospace;"> Make sure the MAC of BT mouse is correct in Linux. If they are different, rename the directory in linux to match the MAC found in Windows. (Examine it character by character. This file for mine was always off by one bit by default in linux)</span></li>
<li><span style="font-family: Courier New, Courier, monospace;"> "LTK" -> "Key" under [LongTermKey]. Remove anything other than hex character (e.g. whitespace and dash), and convert to upper case. </span></li>
<li><span style="font-family: Courier New, Courier, monospace;"> "ERand" -> "Rand" under [LongTermKey]. Do <b>BYTE-WISE</b> reverse and then convert hex to dec. (e.g., "12 AB" -> "AB 12" -> "43794")</span></li>
<li><span style="font-family: Courier New, Courier, monospace;"> "EDIV" -> "EDiv" under [LongTermKey]. Convert hex to dec. </span></li>
<li><span style="font-family: Courier New, Courier, monospace;"> "IRK" -> "Key" under [IdentityResolvingKey]. Remove anything other than hex character</span></li>
<li><span style="font-family: Courier New, Courier, monospace;"> "CSRK" -> "Key" under [LocalSignatureKey]. Remove anything other than hex character</span></li>
<li><span style="font-family: Courier New, Courier, monospace;"> Leave "EncSize" and "Authenticated" unchanged</span></li>
</ol>
</div>
Unknownnoreply@blogger.com3tag:blogger.com,1999:blog-8932807307157268510.post-41191330225552414122017-04-18T11:55:00.002-07:002017-04-18T11:55:18.364-07:00Notes on Pairing a Bluetooth LE Mouse with Linux<br />
Pair in ubuntu setting failed;<br />
With bluez and blueman installed (and bt service restarted), it pairs and works out of box<br />
<br />
Ubuntu 16.04 LTS with kernel 4.10 amd64<br />
Microsoft Mouse 3600<br />
Intel 8260 WLAN/BT module<br />
Lenovo P50 laptop<br />
<br />
Unknownnoreply@blogger.com5tag:blogger.com,1999:blog-8932807307157268510.post-10785765661733539782016-11-29T15:45:00.001-08:002016-11-29T15:45:12.914-08:00AptX (Apt-X) Support Checked for Google Pxiel, Moto X (Gen 1), and Moto E (Gen 2 Verizon LTE)After checking Bluetooth HCI snoop log with Wireshark, as mentioned <a href="http://android.stackexchange.com/a/85668">here</a>, I checked AptX supportability of few devices: google pixel, moto x (gen 1, 2013), moto e (gen 2 Verizon LTE). All using stock software without root.<br />
<br />
Some logs are collected recently, and some are few years ago. I just decided to review these logs and summarize my findings. <br />
<b></b><br />
<b>My results shows that Pixel does not support AptX; the rests do.</b><br />
<br />
What surprises me a bit is the fact that Moto E Gen 2 Verizon LTE does support AptX, while the AptX official website does not have it as AptX enabled device. (Link <a href="https://www.aptx.com/products?field_product_brand_tid=2">here</a>, accessed Nov 29 2016)<br />
<br />
Screenshots of Wireshark are shown below.<br />
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://1.bp.blogspot.com/-niYqX2nOGvg/WD4Rx9jhFKI/AAAAAAAApQ8/U2aftakMnvUGCEv3i09hM7MLAy4UifomgCLcB/s1600/MotoX.PNG" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="211" src="https://1.bp.blogspot.com/-niYqX2nOGvg/WD4Rx9jhFKI/AAAAAAAApQ8/U2aftakMnvUGCEv3i09hM7MLAy4UifomgCLcB/s320/MotoX.PNG" width="320" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Moto X Gen 1 2013 (XT1053 GSM unlocked)</td></tr>
</tbody></table>
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://2.bp.blogspot.com/-pOKRMLONDaE/WD4Rx8OsZVI/AAAAAAAApRE/Q2plvfT3ddESAj-kyf38Vq0lQY1wMvFLACLcB/s1600/Pixel.PNG" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="213" src="https://2.bp.blogspot.com/-pOKRMLONDaE/WD4Rx8OsZVI/AAAAAAAApRE/Q2plvfT3ddESAj-kyf38Vq0lQY1wMvFLACLcB/s320/Pixel.PNG" width="320" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Google Pixel (NA model, Verizon)</td></tr>
</tbody></table>
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://2.bp.blogspot.com/-EFTl5gObffE/WD4Rx8iwASI/AAAAAAAApRA/P7iyLP0JuUoyD_JDwIJiDHtLz45lUW-aQCLcB/s1600/MotoE.PNG" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="211" src="https://2.bp.blogspot.com/-EFTl5gObffE/WD4Rx8iwASI/AAAAAAAApRA/P7iyLP0JuUoyD_JDwIJiDHtLz45lUW-aQCLcB/s320/MotoE.PNG" width="320" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Moto E 2nd Gen LTE (XT1528 Verizon)</td></tr>
</tbody></table>
<br />Unknownnoreply@blogger.com2