[Verizon HTC 10 Guides, News, & Discussion] Zoandroid:
I HAVE SOLVED THE ISSUES BELOW but I'll leave the post here for others meeting the same obstacles.

Hurdle # 1 for me right off the blocks........the htcdev website's pages for unlocking the bootloader refused to display for me using my default Waterfox (64 bit Firefox) browser. I had to switch over to using the Chrome Browser on the Windows 7 Home Premium SP1 PC I am using for this conversion process. Mozilla products seem to have tons of issues with Flash, which despite the railings of the anti-Flash movement, EVERYONE is still using on their websites. I figure that is why I had the problems. Continuing on with Chrome.

---------- Post added at 03:20 PM ---------- Previous post was at 02:21 PM ----------

Wow. I've rooted several devices, and used ADB before (albeit years ago). But I wasn't prepared for things like the HTCdev.com website having cryptic instructions now that they've upgraded to Marshmallow, nor their complete lack of explaining the the Android SDK you download from their link and "install", is actually just an installer itself. You have to RUN that program at least ONCE, as it downloads and installs a ton of essential files in doing so. :) Slogging along........ :) (Google search is our friend when we encounter those WTF moments. ) ;)

---------- Post added at 03:23 PM ---------- Previous post was at 03:20 PM ----------

So at the end of the lengthy run of Android Studio, I get this message. Is this something I need to be concerned about for what we are doing here? I get the feeling it only applies to developers.

"Unable to install Intel HAXM

Your CPU does not support required features (VT-x or SVM).

Unfortunately, your computer does not support hardware accelerated virtualization.

Here are some of your options:

1) Use a physical device for testing

2) Develop on a Windows/OSX computer with an Intel processor that supports VT-x and NX

3) Develop on a Linux computer that supports VT-x or SVM

4) Use an Android Virtual Device based on an ARM system image

(This is 10x slower than hardware accelerated virtualization)"

---------- Post added at 04:04 PM ---------- Previous post was at 03:23 PM ----------

HELP! :eek:

I am stuck. I am trying to follow the HTCdev.com instructions to unlock the bootloader. In step 5 it says to open a command window and "Type in Command Prompt: fastboot oem get_identifier_token."

What they do not tell you is that you have to be in whatever folder the fastboot.exe file is residing. At least I think so. I've tried both that folder's newer version of fastboot, installed in Windows 7's ridiculously long path name to get to the Android SDK, and then I tried replacing that version of fastboot with the much older version HTC is telling us to download. In both instances, there does not seem to be any kind of command structure that could run "fastboot oem get_identifier_token". So the command fails.

In the newer version of Fastboot.exe, when it fails I see the following list of acceptable commands (see below). Note that none of them look even close to the command above.

I am remembering from years ago when I used ADB on an different computer I had to gather a bunch of file together and put them on a short path folder on the C drive. I've never used ADB on this rig, (is THIS the problem?? -- where do I download the current version of ADB??) and I'm guessing I need to do that here, but apparently whatever files I need are missing, as there is no fastboot command with "oem" in it. Can someone tell me the collection of files needed to get going on this process, so I can hunt them all down and collect them to a convenient place?

usage: fastboot [ <option> ] <command>

commands:
update <filename> Reflash device from update.zip.
flashall Flash boot, system, vendor, and --
if found -- recovery.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request
.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
erase <partition> Erase a flash partition.
format[:[<fs type>][:[<size>]] <partition>
Format a flash partition. Can
override the fs type and/or size
the bootloader reports.
getvar <variable> Display a bootloader variable.
set_active <suffix> Sets the active slot. If slots are
not supported, this does nothing.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader] Reboot device [into bootloader].
reboot-bootloader Reboot device into bootloader.
help Show this help message.

options:
-w Erase userdata and cache (and format
if supported by partition type).
-u Do not erase partition before
formatting.
-s <specific device> Specify a device. For USB, provide ei
ther
a serial number or path to device por
t.
For ethernet, provide an address in t
he form <protocol>:<hostname>[:port] w
here <protocol> is either tcp or udp.
-p <product> Specify product name.
-c <cmdline> Override kernel commandline.
-i <vendor id> Specify a custom USB vendor id.
-b, --base <base_addr> Specify a custom kernel base
address (default: 0x10000000).
--kernel-offset Specify a custom kernel offset.
(default: 0x00008000)
--ramdisk-offset Specify a custom ramdisk offset.
(default: 0x01000000)
--tags-offset Specify a custom tags offset.
(default: 0x00000100)
-n, --page-size <page size> Specify the nand page size
(default: 2048).
-S <size>[K|M|G] Automatically sparse files greater
than 'size'. 0 to disable.
--slot <suffix> Specify slot suffix to be used if the

device supports slots. This will be
added to all partition names that use

slots. 'all' can be given to refer
to all slots. 'other' can be given to

refer to a non-current slot. If this
flag is not used, slotted partitions
will default to the current active sl
ot.
-a, --set-active[=<suffix>] Sets the active slot. If no suffix is

provided, this will default to the va
lue
given by --slot. If slots are not
supported, this does nothing. This wi
ll
run after all non-reboot commands.
--unbuffered Do not buffer input or output.
--version Display version.
-h, --help show this message.

---------- Post added at 04:28 PM ---------- Previous post was at 04:04 PM ----------

OK, I found a way around this problem! :D

Google search led me to Minimal ADB and Fastboot here on XDA

http://xdaforums.com/showthread.php?t=2317790

I've got the identifier code now. Onward and upward! :)

---------- Post added at 05:10 PM ---------- Previous post was at 04:28 PM ----------

Finally got the bootloader unlocked. Anyone doing this, I recommend using the above mentioned MinimalADB and Fastboot tool. It is hands down better than the package of files HTCdev's website tells you to install.