[One (M7) Q&A, Help & Troubleshooting] nkk71:
Frequently Asked Questions

FAQ:

1) Q: I'm using Windows 8.1 what should I worry about

A: when you downgrade to hboot 1.44, or it get's downgraded during an ruu, fastboot commands will no longer work and you will be stuck, so you need to use Win7 or Linux (continue reading FAQ)

EDIT: or you could try this [GUIDE] Fix Fastboot on Windows 8.1 (thanks [MENTION=2895182]clsA[/MENTION])​

2) Q: I'm using Windows 7 what should I worry about

A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install

follow the below instructions to fix

Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that

just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to [MENTION=4258433]mdmower[/MENTION])

though you should already have them since you have been using your phone anyways

​

for those who like a visual guide:

okay so I did a fastboot boot command, and as you can see it didnt install correct driver

Open "Device Manager"

there's the culprit

right click and Update Driver Software

select Browse my computer for driver software

select Let me pick from a list of device drivers on my computer

select Android USB Devices

select My HTC ... (if you have more than one version, choose the latest)

warning, select Yes

successful installation

now it looks better :)

and can confirm:

C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery

-------------------------------------------------------------------------------------------------------------------------------------------

3) Q: I'm using a Mac what should I worry about

A: not much, you just can't run a Windows RUU.EXE (executable), and you probably need to use "./":

--> you'll need to use RUU.ZIP method instead

--> CWM guide also updated

----> depending on your setup, you may need to run adb and fastboot commands, with "./" as in "./adb ..." and "./fastboot ..."​

4) Q: I'm using Linux what should I worry about

A: not much, you just can't run a Windows RUU.EXE (executable), and some commands might require "sudo":

--> you'll need to use RUU.ZIP method instead

--> CWM guide also updated

----> adb seems to work just fine in any mode, but

----> fastboot may need su privileges, so you'll need to issue fastboot commands with "sudo fastboot ..."​

5) Q: How do I create a Linux Live USB

Windows users: http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows

Mac users: http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-mac-osx

Ubuntu 12.04 LTS 32bit ISO from here: http://www.ubuntu.com/download/desktop

in case you're having problems setting up adb/fastboot on newer versions, use 12.04 http://releases.ubuntu.com/12.04/

Once the Ubuntu Live USB is ready, shutdown your computer and

restart from the USB

No need to install, just use the "Try Ubuntu" option

open a terminal

and install adb & fastboot using (copy/paste 1 line at a time into terminal):

sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot

you can then check version, by typing "adb version"

and check connection using "adb devices" in custom recovery or booted phone

and "sudo fastboot devices" in bootloader

in case you're having issues, please check [MENTION=5116541]Danny201281[/MENTION]'s MiniGuide here for more information

you can also check [MENTION=5098011]tobesedated[/MENTION] guide for more info: [Guide]Suggestion For S-off On 1.55 HBoot Using Ubuntu---Step by step with pictures

-------------------------------------------------------------------------------------------------------------------------------------------​

6) Q: fastboot is giving me "cannot load"

A: the filename is wrong​

7) Q: flashing 1.44 hboot gives me "FAILED (remote: 42 custom id check fail)"

A: your CID is missing in android-info.txt; the updated zip on my mega account should work, if it doesn't edit android-info.txt to include your CID using Notepad++, or temporarily change CID "fastboot oem writecid 11111111" <- 8 ones, flash hboot, and restore your original CID.​

8) Q: Guru Bootloader Reset just keeps freezing

A: Use alternate method:

credits to [MENTION=3437245]scotty1223[/MENTION]

[how to] remove your "tampered" banner

[how to] lock/unlock your bootloader without htcdev(s-off required)

I recommend you copy/paste the "echo | dd" commands!! (If you write to the wrong partition/offset you could have a brick)

C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I]<- you need to be in CWM recovery to
ensure [B]root[/B] privileges
i.e. an adb shell with [B]#[/B] as opposed to [B]$[/B][/I]

C:\ADB3>[B][COLOR="Blue"]adb shell[/COLOR][/B]

[I][SIZE="1"]Resetting TAMPERED[/SIZE][/I]
~ # [B][COLOR="Blue"]echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988[/COLOR][/B]
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
1+0 records in
1+0 records out
1 bytes (1B) copied, 0.009370 seconds, 106B/s

[I][SIZE="1"]Setting LOCKED[/SIZE][/I]
~ # [B][COLOR="Blue"]echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796[/COLOR][/B]
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
4+0 records in
4+0 records out
4 bytes (4B) copied, 0.007691 seconds, 520B/s

~ # [B][COLOR="Blue"]exit[/COLOR][/B]
exit

C:\ADB3>[B][COLOR="Blue"]adb reboot bootloader[/COLOR][/B]

--> confirm that bootloader is untampered and LOCKED

9) Q: I "adb push" the backup files, but it doesn't show up in restore

A: on a few rare occasions, CWM recovery doesn't mount the data partition automatically, do "adb shell mount /data" and then try pushing the files again.​

10) Q: When I run the Windows RUU.EXE it just exits when I click next

The RUU executable needs the MS Visual C++ 2008 Redistributable Package (x86) package installed.​

-------------------------------------------------------------------------------------------------------------------------------------------

Not so FAQ (maybe):

1) Q: What is this MD5 people keep talking about

A: https://www.google.com/#q=MD5 ; Basically (in our context), MD5 checksums are to verify that the file you downloaded isn't corrupt

on Mac, Linux, and Android terminals it's already built in:

Mac: in terminal, just type md5 <name of file>

----> MD5 (<name of file>) = 12345678901234567890123456789012

Linux: in terminal, just type md5sum <name of file>

----> 12345678901234567890123456789012 <name of file>

Android: in "adb shell", just type md5sum <name of file>

----> 12345678901234567890123456789012 <name of file>

Windows (seems not built-in!?!?): you can use programs such as http://winmd5.com/ or http://implbits.com/hashtab.aspx (available for Windows and Mac, credits to [MENTION=287971]Lizard[/MENTION] for that one ;))

-------------------------------------------------------------------------------------------------------------------------------------------

2) Q: What can I flash (or not) with S-On/S-Off and a (re)locked/unlocked bootloader

A: This may help