Reddit users will soon be able to add profile pics and bios to their profiles
Why it matters to you
In a bid to make Reddit more accessible to new users, the social network’s adding new custom profile pages.
Reddit, self-coined “front page of the internet,” will look a little different going forward. On Tuesday, the social network began rolling out a new profile page design that takes a cue from Facebook and Twitter: Users can make posts directly to pages, and users who log in can follow profiles for new posts.
The changes haven’t gone live for the larger Reddit community just yet. In a public post explaining the new profile features, Reddit’s development team said they will be limited to “a very small number [of] high-profile users” to ensure they don’t “directly impact [users’] day-to-day activities,” Reddit said.
More: Reddit CEO in whole heap of trouble with users of popular Trump subreddit
Once the revamped profiles get a thumbs-up from the initial crop of testers and profile pages roll out broadly, users will get the choice of switching to a “more prominent” avatar and adding a short biography about themselves. All logged-in users, meanwhile, will see new posts from users they choose to follow and will be able to comment — but not create new posts — on profile posts.
It’s part of a bid to make the website more “accessible” to new users, co-founder Alexis Ohanian told Reuters. “If you yourself are someone who wants to share something, it’s pretty daunting,” he said. “We’re in a position where we can start doing product improvements that are admittedly overdue but represent a real level up for Reddit.”
Reddit made headlines over the past several years, and often for the wrong reasons. Former CEO Ellen Pao, who oversaw the shutdown of subreddits accused of “hateful” behavior, was forced to resign after a petition calling for her removal received more than 200,000 signatures.
More: Google wanted to buy Reddit in 2005, but its co-founders declined offer
One particular community, r/The_Donald, featured conspiracy theories, fake news, and racist and misogynistic posts about President Donald Trump’s political opponents. Another, Pizzagate, inflamed a conspiracy theory that linked former Secretary of State Hillary Clinton to a fictional pedophile ring at a Washington, D.C., pizza parlor.
Current chief executive Steve Huffman admitted in an interview with Reuters that the site’s policy against harassment had not been adequately enforced.
“We’re making this change because content creators tell use that they have a hard time finding the right place to post their content,” Reddit noted. “We also want to support them in being able to grow their own followers (similar to how communities can build subscribers). We’ve been working very closely with mods in a few communities to make sure the product will not negatively impact our existing communities.”
Innovative prosthetic leg propels wearers through water as if it were their real limb
Why it matters to you
Just because someone is missing a limb doesn’t mean they are handicapped. With this new prosthetic leg, they are every bit as capable.
With modern advancements in prosthetic design, more people are able to continue walking despite missing one or two legs. These new limbs allow people to carry on, making it less of a disability and more of a unique quality. While designs mastered walking on land, moving through water remained a challenge. However, a new breakthrough from Northwell Health changed that, allowing a former Marine to not just simply wade in water but to efficiently swim in it, as well.
Northwell’s new project is essentially the first fully functional prosthetic swim leg. While this isn’t to say other legs won’t operate in water, it’s that they typically don’t add much of a benefit to the wearer — in other words, they tend to act more like an anchor. Instead, Northwell’s prosthetic actually propels users through water as if it were their original limb.
The new leg features a jet-black foot and a nonslip tread on its sole. Designer Todd Goldstein even crafted some components of the prosthetic using a 3D printer — for instance, one part of it is an upside down triangle of nylon and plastic located where the calf would be. This is what provides extra propulsion through the water, while cone-shaped holes allow some water to pass through so it doesn’t overpower the natural limb.
As mentioned above, Northwell tabbed former Marine Dan Lasko to put the limb through its paces.
“It feels good,” Lasko told the The New York Times after his first lap. “I can definitely feel the difference but I just have to get used to the bit of extra weight.”
Already, Goldstein has a few tweaks to make. During testing, the foot filled with water, creating an unfavorable amount of drag — Goldstein’s thinking is to add a series of holes to help release it. Additionally, the 3D-printed triangle fell off during testing, showing its need for a stronger adhesive in future models. Still, Lasko emerged from the tests pleased with the limb.
“I haven’t done that in years,” he said. “I felt good and free.”
More: Here are 7 prosthetic limbs that are so amazing that they’re almost better than the real thing
Swimming is a beneficial exercise for many amputees. Higher impact exercises such as running or jumping lead to blisters or deeper tissue wounds but laps in a pool are gentle on the skin. According to Eric Feinstein, a manager at Northwell Ventures, the final prosthetic plans to become available in the next six months. The cost intends to range between $2,000 and $5,000, depending on specific client customization.
How to flash Android O factory image on Nexus, Pixel devices
Like last year, Google has released a developer preview for Android O two months before the company’s developer conference. There’s no public over-the-air update this time around, though, so you’ll have to manually flash the system images to your phone.
More: Android O is getting picture-in-picture mode, app icon badges, and more
Google has posted factory images for the Nexus 5X, 6P, Nexus Player, Pixel C, Pixel, and Pixel XL. We should caution, however, that the first developer preview is often the buggiest. There could be bugs that brick your device, so make sure you back up your data before you do anything. Google also mentions that a public beta will be available at a later date, and this first preview is largely for developers. Still, if you want to take a crack at seeing Android O now, we put together this comprehensive guide detailing each and every step of the way.
How to flash the factory image
Flashing the factory image differs from installing the over-the-air (OTA) update in that the factory image contains the full system files for your device, whereas the OTA update contains only the upgrade information. In other words, flashing a factory image is more like completely deleting all the software on your device and replacing it. The OTA will only replace what is being changed since your last update.
Some people prefer to install the OTA update since you don’t have to do a factory reset, while others like the factory image method because it’s like starting from scratch with a fresh install of the entire system. It’s more of a pain to factory reset your device, but you are less prone to some of those annoying bugs that seem to crop up after an OTA update.
Remember to make sure all your data is backed up, because you will lose all your data on the device when you unlock the bootloader, which is required for flashing. There is no way to unlock a bootloader without a factory reset. However, if you happen to already have an unlocked bootloader, then you can forgo the factory reset if you wish. We will show you how later on, but we still recommend that you back up your data in case something goes wrong.
Installing ADB and Fastboot
In order to flash the factory image to your Nexus or Pixel device, you must have ADB and Fastboot installed on your desktop computer. ADB stands for Android Debug Bridge, and it allows you to send commands to your Android device over USB through a terminal/command-line interface such as Windows Command Prompt. Fastboot allows you to unlock the bootloader on your Android device.
There are two methods to getting ADB and Fastboot on your computer. The first is to download and install the Android SDK tools from the Android developer site. This method will work on Windows, Mac, and Linux machines. If you’re a Windows user, you can download and install Minimal ADB and Fastboot instead, which is actually the easiest method. However, we recommend installing the Android SDK tools because the download will also give you the Google USB drivers at the same time, which you will need in order for your computer to recognize your device. If you do decide to install Minimal ADB and Fastboot, you can still download the Google USB drivers separately. We will show you how to do that later.
Follow the instructions below for either installing the Android SDK tools or Minimal ADB and Fastboot.
Download and install the Android SDK tools
Click here to download and install the Android SDK Tools from Google’s developer site. There are choices for Windows, Mac, and Linux. These instructions are for Windows machines.
When asked what directory to install the software to, we recommend that you set it to C:android-sdk. If you choose a different location, just make sure you remember it.
Once the Android SDK Tools are installed, launch the download from the Start Menu.
The SDK Manager will open. Just uncheck everything except Android SDK Platform-tools and Google USB Driver. Android SDK Platform-tools is at the top and Google USB Driver is toward the bottom.
Click on Install 2 packages at the bottom right.
Check Accept license and click Install.
ADB and Fastboot will now reside in the C:android-sdkplatform-tools folder if you followed step 2 as outlined. If you chose a different directory, than ADB and Fastboot will reside in the platform-tools folder under whatever location you chose to install the Android SDK Tools to in step 2.
Download and install Minimal ADB and Fastboot
Click here to download minimal_adb_fastboot_v1.3.1_setup.exe from the XDA forums. Note: the version number could be different if a newer version is released after this post has been published.
Launch the minimal_adb_fastboot_v1.3.1_setup.exe file.
When asked which directory to install the software to, we recommend that you set it to C:android-sdkplatform-tools, since we will be using that location for the rest of this guide. If you choose a different location, just make sure you remember it.
Downloading the Android O Developer Preview factory system image
Now it’s time to grab the most recent version of the Android Nougat or Android O Developer Preview factory image. Please click on one of the following links to download the appropriate file for your device.
- Google’s Developer Preview site – Android O updates
Just make sure to select the version that matches your device. This is very important, because you must flash the Nexus 5 image on a Nexus 5. A Pixel XL image won’t work on a Nexus 5.
You will notice that each device has a bunch of links under it. Google makes it easy to revert back to an older update if you wish. The most recent update is generally at the bottom of the list. The Android O developer preview is available for the Pixel, Pixel XL, Pixel C, Nexus Player, Nexus 6P, and Nexus 5X.
Note: Google will post factory images for each and every update moving forward. This means that you can follow this guide again and continue to get the latest preview of Android O right away without the need to wait until your device receives the OTA update automatically.
Extracting the contents of the system image
The downloaded file should have .tgz as its extension, and you need to extract the contents before going further. The best thing to do is download and install 7 Zip. There is an unofficial version for Macs as well. Once 7 Zip is installed on your machine, follow these steps:
Open the 7 Zip File Manager and navigate to the folder that you saved the .tgz file in.
Double click on the .tgz file.
You will now see a file with a .tar extension.
Double click on this file to show the contents (this will take about a minute or more).
After it has opened, you should have a folder with the codename of your device as part of the title (ex. marlin for Pixel XL), Double click on it.
You should now see a collection of files. Select all of them, and click on Extract to extract all the contents. Type in the destination C:program files (x86)androidandroid-sdkplatform-tools (if you installed the full SDK) or whatever directory ADB and Fastboot are installed in.
Enabling USB debugging and connecting your Nexus or Pixel device via USB to your desktop
Now you need to make sure USB debugging is enabled on your Nexus or Pixel device. Open Settings on your Nexus or Pixel device. If you do not see Developer Options toward the bottom of the Settings screen on your device, follow these steps to activate them.
Tap on About Phone and find the Build Number.
Tap on the Build Number seven times and the Developer Options will appear on the main page of the Settings.
Tap on the Back key to see the Developer Options.
Tap on Developer Options.
Check to enable USB Debugging.
Before you connect your device to the USB port on your computer, you want to make sure you have the appropriate drivers installed. You should be all set if you opted to install the Android SDK Tools. If you instead chose to install Minimal ADB and Fastboot, you can grab them here. Since you’re working with a Nexus or Pixel device, you specifically want the Google USB Drivers. The download will be a zip file, so extract the contents where you wish, and remember the location.
Now connect your device via a USB cable, and you are ready to flash the zip file that you extracted earlier. If you’re connecting your Nexus or Pixel device to your computer for the first time, you will get a popup box on your Nexus or Pixel device stating what the computer’s RSA Key is. Just check Always Allow From This Computer and tap on OK.
If your Nexus or Pixel device doesn’t show the RSA key popup, then open the notification panel, select USB For Charging Only, and change the mode to Transfer Photos (PTP).
If your Nexus or Pixel device still doesn’t show the RSA key popup, then follow these instructions:
On your Windows desktop, go to your Control Panel then Device Manager.
You should see your Nexus or Pixel device under Other Devices with a Yellow ! mark on it.
Right-click on it and select update driver.
Choose Browse my computer for driver software, and choose the directory where the Google USB Drivers are located. If you chose to install the Android SDK tools and followed our instructions, they should be in the C:android-sdkextrasgoogleusb driver folder. If you chose to manually download the Google USB drivers, just navigate to the folder that you archived the contents of the Zip file in.
If your device still doesn’t show the RSA key approval popup, then open the command prompt on your desktop and navigate to the folder where ADB and Fastboot reside. If you followed our instructions from the Installing ADB and Fastboot section, it will be in the C:android-sdkplatform-tools folder. Just type cdandroid-sdkplatform-tools at the command prompt in Windows. If ADB and Fastboot are somewhere else, just navigate to that location instead.
Type “ADB devices” and you should get the following result:
The RSA key approval popup should now be visible on your Pixel device. Just check Always Allow From This Computer and tap OK.
Type “ADB devices” again, and you should get the following result with a different device key:
You are now ready to flash the factory image.
Flashing the Android O Developer Preview factory image
If your device doesn’t have an unlocked bootloader, follow the instructions below.
This process will require a factory reset, so make sure you have your important data backed up.
Open the Command Prompt in Windows or Terminal on a Mac and navigate to the folder that ADB and Fastboot are installed in. Again, if you followed our instructions from the Installing ADB and Fastboot section, it will be in the C:android-sdkplatform-tools folder. Just type “cdandroid-sdkplatform-tools” at the prompt in Windows. If ADB and Fastboot are somewhere else, just navigate to that location instead. To make things easier, so you don’t have to type out long directories, you can also paste it by pressing ALT and the spacebar, then choose Edit before selecting Paste.
If you’re using a Mac, you need to add the platform tools directory to your $PATH. In terminal, type “sudo nano/etc/paths”. Now enter your password, go to the bottom of the file, and enter the full path of the “platform tools” directory. Hit control-x to quit and enter Y to save.
The following ADB commands are for Windows machines. If you’re using a Mac, just add “./” before each command, for example: “./adb reboot bootloader”.
Assuming you device is already connected to your computer via USB and USB Debugging is enabled, you need to re-start it in fastboot mode. Follow one of the two methods below. Option A may be preferable because it’s another confirmation that your computer recognizes your Nexus or Pixel device.
A) Type “adb reboot bootloader”
B) Turn your device off, then turn it back on while holding down the relevant key combinations for your device. For many devices it’s Volume Up + Volume Down + Power. You can see what your device’s key combinations are here.
Type fastboot oem unlock to unlock you device. As a final warning, this step will erase everything on your device.
Type flash-all to install the bootloader, baseband firmware(s), and operating system. If you get a missing system.img error, then scroll down to bottom of this page for further instructions.
This process could take several minutes, so it’s important not to power off or disconnect the device. Once it’s finished, your device will reboot and the latest version of Android O will be installed.
You can opt to re-lock the bootloader if you wish, but assuming you will do this again with a future update, you might want to leave it unlocked, so you don’t have to perform a factory reset again. If you do want to re-lock, just follow Step 2 above and change Step 3 to fastboot oem lock. That’s it.
If your device already has an unlocked bootloader and you don’t want to do a factory reset and lose your data, follow the instructions below.
Open the Command Prompt in Windows or Terminal on a Mac and navigate to the folder that ADB and Fastboot are installed in. Again, if you followed our instructions from the Installing ADB and Fastboot section, it will be in the C:android-sdkplatform-tools folder. Just type “cdandroid-sdkplatform-tools” at the prompt in Windows. If ADB and Fastboot are somewhere else, just navigate to that location instead. To make things easier, so you don’t have to type out long directories, you can also paste it by pressing ALT and the spacebar, then choose Edit before selecting Paste.
If you’re using a Mac, you need to add the platform tools directory to your $PATH. In terminal, type “sudo nano/etc/paths”. Now enter your password, go to the bottom of the file, and enter the full path of the “platform tools” directory. Hit control-x to quit and enter Y to save.
The following ADB commands are for Windows machines. If you’re using a Mac, just add “./” before each command, for example: “./adb reboot bootloader”.
Assuming you device is already connected to your computer via USB and USB Debugging is enabled, you need to re-start it in fastboot mode. Follow one of the two methods below. Option A may be preferable because it’s another confirmation that your computer recognizes your Nexus or Pixel device.
A) Type “adb reboot bootloader”
B) Turn your device off, then turn it back on while holding down the relevant key combinations for your device. For many devices it’s Volume Up + Volume Down + Power. You can see what your device’s key combinations are here.
You will need to edit the flash-all.bat file that you extracted from the factory image, which should be in the same directory as ADB and Fastboot. Just open it with any simple text editor such as WordPad. You will see a line that starts with “fastboot -w update……..” Just remove the -w from this line. The -w flag wipes your data, so removing it will obviously stop that from happening.
Type flash-all to install the bootloader, baseband firmware(s), and operating system. If you get a missing system.img error, then scroll down to bottom of this page for further instructions.
This process could take several minutes, so it’s important not to power off or disconnect the device. Once it’s finished, your device will reboot and the latest version of Android O will be installed.
If you get a missing system.img error in Step 4 of either method, then follow these instructions
Extract all the files from the .zip file, which happens to be one of the files extracted from the original .tgz you downloaded from Google. The Zip file name probably begins with “image.” There should be various .img files within this Zip file. On top of this, you already have bootloader and radio .img files in the same directory. Just make sure all the .img files (from Zip file) and the ones that were already extracted are in the same directory as ADB and fastboot. Now you are going to flash each .img file separately.
If you don’t have either one of the bootloader or radio .img files, don’t worry, not all devices need them. It’s also important to follow this exact order. At the CMD prompt and in the C:program files (x86)androidandroid-sdkplatform-tools directory (if you installed the full SDK) or wherever ADB and fastboot reside. Remember, add ./ before each command if you’re using a Mac.
type fastboot flash bootloader [name of your file].img
type fastboot flash radio [name of your file].img
type fastboot reboot-bootloader
type fastboot flash recovery recovery.img
type fastboot flash boot boot.img
type fastboot flash system system.img
Lastly, if you want, you can wipe the cache with this command – fastboot flash cache cache.img
Now it’s time to enjoy your Android O update. Remember, you can follow this guide again when Google issues its next Android update, so be sure to bookmark this page for later reference. If we missed anything, or if you have any other tips, please don’t hesitate to let us know in the comments.
This article was originally published on July 7, and updated on March 21 by Christian de Looper to reflect availability.
Want seared scallops? The Hestan Cue smart cooking system is pricey but precise
Why it matters to you
Hestan Cue thinks novices can quickly learn to cook without making mistakes with its smart cooking system.
There is probably a reason Hestan Cue had an enclosed booth at the 2017 International Home and Housewares Show — they had people on hand making scallops, after all. Food scents wafted all around the showroom floor as chefs at various booths flipped pancakes or made pasta sauce. But at the Hestan Cue booth, the induction burner and pan were doing most of the work.
Hestan acquired Meld Smart Knob more than a year ago. The Meld was supposed to retrofit your existing stove into a smart one. That was one of Hestan’s early steps in developing the Cue, Lorin Peters, culinary media manager at the company, told Digital Trends. Instead of working with your current range, though, the Cue is an independent induction burner and pan that communicate via Bluetooth with one another to keep a consistent temperature so you never burn a pancake or dry out your chicken.
More: Bear Bowl cook pot weighs less than cell phone and folds down to the size of your wallet
The pan itself has sensors and a “smart handle” — in that it is full of tech you don’t want to throw in the dishwasher. Handwashing aside, the system is meant to make cooking foolproof. The accompanying app walks you through recipes and the burner can heat the pan to a precise temperature. That means instead of turning your burner to high heat, the app will tell the Cue to set itself to 350-degrees Fahrenheit (176.67-degrees Celsius). The app will set a timer, as well, so you know exactly when to flip them.
If you would rather fly solo, the system can be used like a regular induction burner. It has physical controls but they don’t let you dial in specific degrees; instead, you will slide your finger across the temperature control to set it to something between one and 10.
The Hestan Cue has been available for pre-order through Williams-Sonoma for a few months now. The price is $400 for the burner and $250 for the pan. Once it starts shipping in early April, the price will increase to $650 for the burner. That is pricier than the Cinder, a precise countertop grill that doesn’t require a pan. The Cinder has a much bigger footprint, though. At 12.5 inches in diameter and less than five pounds, the Cue more portable and storable than the Cinder.
Despite its hefty price, the Hestan Cue signals that we might be seeing more precision coming to cooktops. General Electric’s FirstBuild also had its Paragon Mat on display at the show, which similarly lets you set an induction burner’s temperature in degrees. Perhaps you’re noticing a theme here. Both the Hestan Cue and Paragon use induction. It may be less familiar to U.S. home cooks, but it does hold temperature better than gas or radiant.
How to flash Android O factory image on Nexus, Pixel devices
Like last year, Google has released a developer preview for Android O two months before the company’s developer conference. There’s no public over-the-air update this time around, though, so you’ll have to manually flash the system images to your phone.
More: Android O is getting picture-in-picture mode, app icon badges, and more
Google has posted factory images for the Nexus 5X, 6P, Nexus Player, Pixel C, Pixel, and Pixel XL. We should caution, however, that the first developer preview is often the buggiest. There could be bugs that brick your device, so make sure you back up your data before you do anything. Google also mentions that a public beta will be available at a later date, and this first preview is largely for developers. Still, if you want to take a crack at seeing Android O now, we put together this comprehensive guide detailing each and every step of the way.
How to flash the factory image
Flashing the factory image differs from installing the over-the-air (OTA) update in that the factory image contains the full system files for your device, whereas the OTA update contains only the upgrade information. In other words, flashing a factory image is more like completely deleting all the software on your device and replacing it. The OTA will only replace what is being changed since your last update.
Some people prefer to install the OTA update since you don’t have to do a factory reset, while others like the factory image method because it’s like starting from scratch with a fresh install of the entire system. It’s more of a pain to factory reset your device, but you are less prone to some of those annoying bugs that seem to crop up after an OTA update.
Remember to make sure all your data is backed up, because you will lose all your data on the device when you unlock the bootloader, which is required for flashing. There is no way to unlock a bootloader without a factory reset. However, if you happen to already have an unlocked bootloader, then you can forgo the factory reset if you wish. We will show you how later on, but we still recommend that you back up your data in case something goes wrong.
Installing ADB and Fastboot
In order to flash the factory image to your Nexus or Pixel device, you must have ADB and Fastboot installed on your desktop computer. ADB stands for Android Debug Bridge, and it allows you to send commands to your Android device over USB through a terminal/command-line interface such as Windows Command Prompt. Fastboot allows you to unlock the bootloader on your Android device.
There are two methods to getting ADB and Fastboot on your computer. The first is to download and install the Android SDK tools from the Android developer site. This method will work on Windows, Mac, and Linux machines. If you’re a Windows user, you can download and install Minimal ADB and Fastboot instead, which is actually the easiest method. However, we recommend installing the Android SDK tools because the download will also give you the Google USB drivers at the same time, which you will need in order for your computer to recognize your device. If you do decide to install Minimal ADB and Fastboot, you can still download the Google USB drivers separately. We will show you how to do that later.
Follow the instructions below for either installing the Android SDK tools or Minimal ADB and Fastboot.
Download and install the Android SDK tools
Click here to download and install the Android SDK Tools from Google’s developer site. There are choices for Windows, Mac, and Linux. These instructions are for Windows machines.
When asked what directory to install the software to, we recommend that you set it to C:android-sdk. If you choose a different location, just make sure you remember it.
Once the Android SDK Tools are installed, launch the download from the Start Menu.
The SDK Manager will open. Just uncheck everything except Android SDK Platform-tools and Google USB Driver. Android SDK Platform-tools is at the top and Google USB Driver is toward the bottom.
Click on Install 2 packages at the bottom right.
Check Accept license and click Install.
ADB and Fastboot will now reside in the C:android-sdkplatform-tools folder if you followed step 2 as outlined. If you chose a different directory, than ADB and Fastboot will reside in the platform-tools folder under whatever location you chose to install the Android SDK Tools to in step 2.
Download and install Minimal ADB and Fastboot
Click here to download minimal_adb_fastboot_v1.3.1_setup.exe from the XDA forums. Note: the version number could be different if a newer version is released after this post has been published.
Launch the minimal_adb_fastboot_v1.3.1_setup.exe file.
When asked which directory to install the software to, we recommend that you set it to C:android-sdkplatform-tools, since we will be using that location for the rest of this guide. If you choose a different location, just make sure you remember it.
Downloading the Android O Developer Preview factory system image
Now it’s time to grab the most recent version of the Android Nougat or Android O Developer Preview factory image. Please click on one of the following links to download the appropriate file for your device.
- Google’s Developer Preview site – Android O updates
Just make sure to select the version that matches your device. This is very important, because you must flash the Nexus 5 image on a Nexus 5. A Pixel XL image won’t work on a Nexus 5.
You will notice that each device has a bunch of links under it. Google makes it easy to revert back to an older update if you wish. The most recent update is generally at the bottom of the list. The Android O developer preview is available for the Pixel, Pixel XL, Pixel C, Nexus Player, Nexus 6P, and Nexus 5X.
Note: Google will post factory images for each and every update moving forward. This means that you can follow this guide again and continue to get the latest preview of Android O right away without the need to wait until your device receives the OTA update automatically.
Extracting the contents of the system image
The downloaded file should have .tgz as its extension, and you need to extract the contents before going further. The best thing to do is download and install 7 Zip. There is an unofficial version for Macs as well. Once 7 Zip is installed on your machine, follow these steps:
Open the 7 Zip File Manager and navigate to the folder that you saved the .tgz file in.
Double click on the .tgz file.
You will now see a file with a .tar extension.
Double click on this file to show the contents (this will take about a minute or more).
After it has opened, you should have a folder with the codename of your device as part of the title (ex. marlin for Pixel XL), Double click on it.
You should now see a collection of files. Select all of them, and click on Extract to extract all the contents. Type in the destination C:program files (x86)androidandroid-sdkplatform-tools (if you installed the full SDK) or whatever directory ADB and Fastboot are installed in.
Enabling USB debugging and connecting your Nexus or Pixel device via USB to your desktop
Now you need to make sure USB debugging is enabled on your Nexus or Pixel device. Open Settings on your Nexus or Pixel device. If you do not see Developer Options toward the bottom of the Settings screen on your device, follow these steps to activate them.
Tap on About Phone and find the Build Number.
Tap on the Build Number seven times and the Developer Options will appear on the main page of the Settings.
Tap on the Back key to see the Developer Options.
Tap on Developer Options.
Check to enable USB Debugging.
Before you connect your device to the USB port on your computer, you want to make sure you have the appropriate drivers installed. You should be all set if you opted to install the Android SDK Tools. If you instead chose to install Minimal ADB and Fastboot, you can grab them here. Since you’re working with a Nexus or Pixel device, you specifically want the Google USB Drivers. The download will be a zip file, so extract the contents where you wish, and remember the location.
Now connect your device via a USB cable, and you are ready to flash the zip file that you extracted earlier. If you’re connecting your Nexus or Pixel device to your computer for the first time, you will get a popup box on your Nexus or Pixel device stating what the computer’s RSA Key is. Just check Always Allow From This Computer and tap on OK.
If your Nexus or Pixel device doesn’t show the RSA key popup, then open the notification panel, select USB For Charging Only, and change the mode to Transfer Photos (PTP).
If your Nexus or Pixel device still doesn’t show the RSA key popup, then follow these instructions:
On your Windows desktop, go to your Control Panel then Device Manager.
You should see your Nexus or Pixel device under Other Devices with a Yellow ! mark on it.
Right-click on it and select update driver.
Choose Browse my computer for driver software, and choose the directory where the Google USB Drivers are located. If you chose to install the Android SDK tools and followed our instructions, they should be in the C:android-sdkextrasgoogleusb driver folder. If you chose to manually download the Google USB drivers, just navigate to the folder that you archived the contents of the Zip file in.
If your device still doesn’t show the RSA key approval popup, then open the command prompt on your desktop and navigate to the folder where ADB and Fastboot reside. If you followed our instructions from the Installing ADB and Fastboot section, it will be in the C:android-sdkplatform-tools folder. Just type cdandroid-sdkplatform-tools at the command prompt in Windows. If ADB and Fastboot are somewhere else, just navigate to that location instead.
Type “ADB devices” and you should get the following result:
The RSA key approval popup should now be visible on your Pixel device. Just check Always Allow From This Computer and tap OK.
Type “ADB devices” again, and you should get the following result with a different device key:
You are now ready to flash the factory image.
Flashing the Android O Developer Preview factory image
If your device doesn’t have an unlocked bootloader, follow the instructions below.
This process will require a factory reset, so make sure you have your important data backed up.
Open the Command Prompt in Windows or Terminal on a Mac and navigate to the folder that ADB and Fastboot are installed in. Again, if you followed our instructions from the Installing ADB and Fastboot section, it will be in the C:android-sdkplatform-tools folder. Just type “cdandroid-sdkplatform-tools” at the prompt in Windows. If ADB and Fastboot are somewhere else, just navigate to that location instead. To make things easier, so you don’t have to type out long directories, you can also paste it by pressing ALT and the spacebar, then choose Edit before selecting Paste.
If you’re using a Mac, you need to add the platform tools directory to your $PATH. In terminal, type “sudo nano/etc/paths”. Now enter your password, go to the bottom of the file, and enter the full path of the “platform tools” directory. Hit control-x to quit and enter Y to save.
The following ADB commands are for Windows machines. If you’re using a Mac, just add “./” before each command, for example: “./adb reboot bootloader”.
Assuming you device is already connected to your computer via USB and USB Debugging is enabled, you need to re-start it in fastboot mode. Follow one of the two methods below. Option A may be preferable because it’s another confirmation that your computer recognizes your Nexus or Pixel device.
A) Type “adb reboot bootloader”
B) Turn your device off, then turn it back on while holding down the relevant key combinations for your device. For many devices it’s Volume Up + Volume Down + Power. You can see what your device’s key combinations are here.
Type fastboot oem unlock to unlock you device. As a final warning, this step will erase everything on your device.
Type flash-all to install the bootloader, baseband firmware(s), and operating system. If you get a missing system.img error, then scroll down to bottom of this page for further instructions.
This process could take several minutes, so it’s important not to power off or disconnect the device. Once it’s finished, your device will reboot and the latest version of Android O will be installed.
You can opt to re-lock the bootloader if you wish, but assuming you will do this again with a future update, you might want to leave it unlocked, so you don’t have to perform a factory reset again. If you do want to re-lock, just follow Step 2 above and change Step 3 to fastboot oem lock. That’s it.
If your device already has an unlocked bootloader and you don’t want to do a factory reset and lose your data, follow the instructions below.
Open the Command Prompt in Windows or Terminal on a Mac and navigate to the folder that ADB and Fastboot are installed in. Again, if you followed our instructions from the Installing ADB and Fastboot section, it will be in the C:android-sdkplatform-tools folder. Just type “cdandroid-sdkplatform-tools” at the prompt in Windows. If ADB and Fastboot are somewhere else, just navigate to that location instead. To make things easier, so you don’t have to type out long directories, you can also paste it by pressing ALT and the spacebar, then choose Edit before selecting Paste.
If you’re using a Mac, you need to add the platform tools directory to your $PATH. In terminal, type “sudo nano/etc/paths”. Now enter your password, go to the bottom of the file, and enter the full path of the “platform tools” directory. Hit control-x to quit and enter Y to save.
The following ADB commands are for Windows machines. If you’re using a Mac, just add “./” before each command, for example: “./adb reboot bootloader”.
Assuming you device is already connected to your computer via USB and USB Debugging is enabled, you need to re-start it in fastboot mode. Follow one of the two methods below. Option A may be preferable because it’s another confirmation that your computer recognizes your Nexus or Pixel device.
A) Type “adb reboot bootloader”
B) Turn your device off, then turn it back on while holding down the relevant key combinations for your device. For many devices it’s Volume Up + Volume Down + Power. You can see what your device’s key combinations are here.
You will need to edit the flash-all.bat file that you extracted from the factory image, which should be in the same directory as ADB and Fastboot. Just open it with any simple text editor such as WordPad. You will see a line that starts with “fastboot -w update……..” Just remove the -w from this line. The -w flag wipes your data, so removing it will obviously stop that from happening.
Type flash-all to install the bootloader, baseband firmware(s), and operating system. If you get a missing system.img error, then scroll down to bottom of this page for further instructions.
This process could take several minutes, so it’s important not to power off or disconnect the device. Once it’s finished, your device will reboot and the latest version of Android O will be installed.
If you get a missing system.img error in Step 4 of either method, then follow these instructions
Extract all the files from the .zip file, which happens to be one of the files extracted from the original .tgz you downloaded from Google. The Zip file name probably begins with “image.” There should be various .img files within this Zip file. On top of this, you already have bootloader and radio .img files in the same directory. Just make sure all the .img files (from Zip file) and the ones that were already extracted are in the same directory as ADB and fastboot. Now you are going to flash each .img file separately.
If you don’t have either one of the bootloader or radio .img files, don’t worry, not all devices need them. It’s also important to follow this exact order. At the CMD prompt and in the C:program files (x86)androidandroid-sdkplatform-tools directory (if you installed the full SDK) or wherever ADB and fastboot reside. Remember, add ./ before each command if you’re using a Mac.
type fastboot flash bootloader [name of your file].img
type fastboot flash radio [name of your file].img
type fastboot reboot-bootloader
type fastboot flash recovery recovery.img
type fastboot flash boot boot.img
type fastboot flash system system.img
Lastly, if you want, you can wipe the cache with this command – fastboot flash cache cache.img
Now it’s time to enjoy your Android O update. Remember, you can follow this guide again when Google issues its next Android update, so be sure to bookmark this page for later reference. If we missed anything, or if you have any other tips, please don’t hesitate to let us know in the comments.
This article was originally published on July 7, and updated on March 21 by Christian de Looper to reflect availability.
Court: Claiming you forgot your decryption password can be contempt of court
Why it matters to you
The ruling holds that judges can find you in contempt of court for failing to decrypt a device that may contain evidence.
Refusing to decrypt your hard drive for authorities, even if you’ve allegedly forgotten the password, is still considered contempt of court. That’s according to a U.S. Third Circuit Court of Appeals ruling handed down this week, which upheld a lower court ruling.
The John Doe at the center of the case had argued that not decrypting his hard drives was allowed under his Fifth Amendment right to avoid self-incrimination. The man is accused of owning child pornography. Several devices were seized upon his arrest including a Mac Pro, two external hard drives, an iPhone 5S, and an iPhone 6 Plus.
According to court documents published by The Register, the defendant had voluntarily handed over the password for one of his iPhones but refused to do so for his Mac and the two external hard drives. The authorities eventually got access to the Mac with help from forensic analysts but have been unable to decrypt the external hard drives.
Through their investigation, the analysts determined that the computer had been used to download files from sites that hosted child abuse material, however these files were not found on the Mac. The police believe they are stored on the external hard drives, citing a statement from the defendant’s sister indicating that she said she saw these files on the drives.
More: Microsoft, Amazon, Apple join Google in its fight with FBI over foreign emails
The defendant had already provided access to his iPhone 6 Plus where police did indeed find incriminating material.
“Forensic analysts also found an additional 2,015 videos and photographs in an encrypted application on Doe’s phone, which Doe had opened for the police by entering a password,” said the ruling.
Based on this, the police felt that there was reasonable cause for decrypting the hard drives in the same way the other devices were decrypted. However, John Doe failed to provide access to the hard drives because “he could not remember the passwords necessary to decrypt the hard drives,” Several incorrect password attempts were made during the examination.
The judge overseeing the case thinks otherwise, though, and stated that the defendant was lying and “chose not to reveal [the passwords] because of the devices’ contents” which amounts to contempt of court.
An attorney for the Electronic Frontier Foundation told The Register that it was disappointed in the ruling. The digital rights organization is opposed to compelled password production by authorities. “Any time suspects are forced to disclose the contents of their mind, that’s enough to trigger the Fifth Amendment, end of story,” he said.
Facebook is testing a new look for its comments that looks a lot like Messenger
Why it matters to you
Conversation seems to be one of the primary purposes of Facebook and the social network is testing out a new format for people to engage in those conversations thanks to a Comments redesign.
Your interactions on Facebook might be getting a major makeover. In efforts to make all your mediums of communication seem increasingly indistinguishable from one another, the social media giant appears to be testing a new design that makes comment threads look a whole lot like messaging app threads, complete with message bubbles and all.
On Monday, a spokesperson confirmed the test to BuzzFeed, noting, “We are always working to make Facebook a more visual and engaging place to have conversations. So we’re testing multiple design updates in News Feed, including a more conversational way to comment on posts.” This is by no means the only test the company is currently conducting — it is also testing a feature that lets you see when people are in the process of typing a comment on a post (again, much like you might see in iMessage or other messaging apps), as well as having some posts pop up in new windows.
More: How to use Facebook Messenger’s secret conversations in iOS and Android
This design tweak, if fully implemented, would likely have a huge effect on all of Facebook’s nearly 2 billion users, given that comments are practically ubiquitous on the platform. After all, how many times have you engaged in a fight, or spirited discussion, via comments? Don’t worry, we’re not judging.
Of course, Facebook is always undergoing redesigns and trying out new things, so this new trial is by no means set in stone quite yet. Really, however, it just seems as though Facebook is trying to make more of its interface look like its popular Messenger app, making it harder and harder to differentiate between having a conversation in private and in public.
So if you’re seeing a new layout in your own comments, don’t be alarmed. It’s just Facebook trying out a little something new.
Like a Siri for travel, HelloGbye is a new streamlined travel-planning app
Why it matters to you
Frequent traveller? HelloGbye could take some of the headache out of the planning process by generating itineraries based on personal preferences quickly.
A new iOS app aims to take travelers from hello to goodbye even faster with streamlined travel planning. HelloGbye — launched on the app store today, March 21 — is a travel booking app and virtual assistant designed to help frequent travelers save time.
On HelloGbye, users can verbally ask or type in their travel wishes and the app will display a number of itinerary options including airfare and hotels. Tapping brings up different itinerary options. The platform also makes it possible to invite others to join in the same itinerary for group travel.
More: Travel easier with 5 apps and services for the lazy jet-setter
Besides just the speed of the voice-activated search, the app aims to shave time off the planning process by allowing users to create profiles with different preferences, like how important traveling first class is or whether having a layover-free flight is more or less important than the price of the ticket. The app also uses advanced hotel search analytics, powered by American Express. Users can also create more than one profile to, for example, create one set of preferences for business trips and another for family vacations.
The startup says the app eliminates all the forms and fields of current online travel booking options for a more user-friendly and streamlined process. The idea arose after founder Jonathan Miller was on a road trip in the middle of a storm — he tried searching for a hotel but said it wasn’t easy figuring out which ones had available rooms. HelloGbye instead offers a 30-second search by just asking the phone for what you want and getting results tailored to your profile.
“HelloGbye’s new groundbreaking search and scheduling technology dramatically simplifies the booking experience for travelers who do not have hours to waste with complicated online travel services. Unlike the traditional, time-consuming methods largely available online today, HelloGbye’s users can book intricate travel itineraries best suited to them, faster than ever before. With HelloGbye, users can spend less time planning and more time traveling,” Miller said.
Besides just the simpler booking process, users can also ask the digital assistant to make changes to those plans without sitting on hold with a call center.
HelloGbye is available on iOS as well as any web browser. The app is free to try, but there’s a $19 monthly subscription for fee-free itinerary changes, preferred hotel rates, and up to two-percent cash back on hotels.
Charge all your devices without all those wires with the Magfast Family
Why it matters to you
Have tons of devices to charge but not a ton of patience for cords and wires? Magfast Family can help.
People want what they want, and apparently, that’s a charging system that doesn’t involve a lot of cords, cables, and tangles. On March 21, the crowdfunding campaign for the Magfast Family went live, and in about 15 minutes, managed to reach its goal of $300,000, indicating the strong desire for a new charging solution.
So what precisely is this highly desirable Magfast? Described as an alternative to messy, wire-laden charging systems, this family of chargers relies on the power of magnets to link together, much like Legos, providing a charging solution that is efficient and easy on the eyes.
The Magfast Family comes with six chargers, covering every charging situation, and promises easy and quick charging for all your mobile devices. All of Magfast’s power banks come with a self-storing and replaceable built-in cable, traditional USB-A and new USB-C outlets, as well as wireless charging.
More: 17 great wireless chargers to free yourself from cables
While each individual Mgafast charger can work on its own, the system’s modular design allows you to connect multiple units together for “easy and rapid charging without wires.” There’s the LifeCharger, a portable powerbank that is easy to charge and can easily charge any device, all while fitting in the palm of your hand. Then, there’s the LifeCharger Extreme, which boasts the maximum power allowed by FAA law — that’s enough to jump start your car.
Then, you have the RoadCharger, which when plugged into your 12v outlet gives you 4 USB outlets for you and your carmates to charge your devices with. As for AirCharger, this device supports wireless charging, and promises to be “perfect for the kitchen or office.” The WallCharger claims to provide a station for wireless charging not only for your mobile devices, but for the whole family of Magfast chargers as well. And finally, if you have an Apple Watch, the TimeCharger is for you.
“There’s two problems with most chargers today,” said Seymour Segnit, Magfast founder and CEO. “They’re ugly with all those messy wires, which is no good in your environment — and most are so cheaply made they quickly go to landfill, which is really bad for everyone’s environment.”
“Magfast is changing charging for good with world-class design and the best manufacturing, so these products will really last,” Segnit continued. And best of all, Magfast says it will plant a tree for every product sold during its launch.
You can pre-order the whole Magfast Family now at Magfast.com, from $49 for individual components and $297 for the whole set.
Goodbye odors! This smart gym bag freshens its contents for you
Why it matters to you
Want your gym clothes to smell as clean as the air after a rainstorm? This self-cleaning bag promises to deliver on that promise.
Virtually everyone has had the experience of opening their gym bag to be greeted by a malodorous gust of sweaty workout clothes and smelly sneakers.
The folks behind new Kickstarter Paqsule think they’ve come up with a crowd-pleasing solution — and, no, it’s not ditching exercise to stay at home.
“Paqsule is a bag that cleans itself and anything you put inside it,” creator Ravid Yosef told Digital Trends. “Using UV-c and O3 (read: ozone) technology, it sanitizes, deodorizes and kills bacteria with the touch of a button to keep your bag and everything inside smelling fresh.”
More: Humble duffel bag gets reinvented for modern, tech-savvy business travelers
A chemical-free, FDA approved process, Yosef says that everything that occurs inside the Paqsule gym bag occurs naturally. It works by first trapping bacteria inside. The owner can then activate the unit, which causes ozone to fill the bag, killing odor and bacteria on contact. UV-C light acts as an additional layer, sterilizing against viruses and pathogens. Each cycle takes 35 minutes to complete, after which the ozone converts back to oxygen, leaving the bag and its contents smelling fresh.
Thanks to an iOS and Android app you can even control the bag’s technology from a distance, and get an alert when the fresh cycle is complete. In essence, it’s the same principle that causes air to smell the way it does after a rainstorm — only with an added dose of tech thrown in for good measure.
The bag itself is stylish, and boasts a range of other smart features.
“We really wanted Paqsule to be the only duffel bag you would ever need,” Yosef continued. “Rather than having multiple bags for different uses, our cleaning system allows you to use one bag to crossover from the gym to work to travel. We also have a USB charging station and over twenty premium features with lots of pockets to help organize just about anything.”
You can currently pre-order Paqsule on Kickstarter, with prices starting at $229. Shipping is set to take place this summer. Let’s hope the concept is still “fresh” by then.
AIVAnet 