[Upgrading, Modifying and Unlocking] ProdiJay:
Hi Jorandobnl, thanks for your reply.

I am using windows 7 & already have the android sdk bundle which I grabbed online when unlocking & attempting to root my device. It would of been great if I had the link you provided at the time as it was such a large download for the purpose of 4 files (fastboot, adb, adbwinapi & adbwinusbapi). Please let me know if I'm missing any other adb required files and I will download them.

So here's where im at...

I followed your instructions step 1 - 3 & my fastboot folder now contains root, fastboot, AdbWinApi.dll, AdbWinUsbApi.dll, adb & crDroid.zip

When typing 'C:\fastboot>adb devices' the cmd prompt returns with:

C:\fastboot>adb devices

List of devices attached

Even though the cmd prompt didn't list any adb devices I continued to the next step anyway & here's what was returned:

C:\fastboot>adb push crDroid-4.4.4-20141106-OFFICIAL-endeavoru.zip/sdcard/
Android Debug Bridge version 1.0.26

-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.

If -p is not specified, the ANDROID_PRODUCT_OUT

environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this ocmmand with no additional arguments

will disconnect from all connected TCP/IP devic
es.

device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport

adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.

adb help - show this help message
adb version - show version num

DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition

scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns

adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:

- If <directory> is not specified, both /system and /data partitions will be u
pdated.

- If it is "system" or "data", only the corresponding partition
is updated.

environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.

C:\fastboot>

'crDroid-4.4.4-20141106-OFFICIAL-endeavoru.zip' is the name of the ROM file which you kindly provided

When my handset is attached to my PC via USB I receive a different command prompt:

C:\fastboot>adb devices
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:

C:\fastboot>

When I use the cmd code 'C:\fastboot>fastboot devices' It returns:

C:\fastboot>fastboot devices

HT244W103055 fastboot

I'm not sure whether this has any relevance but I would like to give you as much detail as possible.

To quickly summarise the steps which I took so you can check if I am doing anything wrong (which is more than likely) :eek:

Firstly I downloaded the ROM (crDroid) & placed it in my fastboot folder along with the adb files I already have. I connected my phone to my computer and started bootloader mode, then I clicked 'recovery' which loaded CWM. I proceeded to check for adb devices which unfortunately returned with nothing. I attempted 'step 4' regardless which returned the cmd code I copy and pasted for you above (for obvious reasons I could not complete step 5).

Your alternative method I have not tried yet because I neither know what nandroid nor sideload means (I must sound like im either 90, amish or stupid :rolleyes: )

Any further help you could give me would be very much appreciated & hopefully I can find a way to fix this soon :fingers-crossed:

Once again I apologise on behalf of my technologically illiterate brain!