Database Info

fastboot questions

I come from the world of Windows Mobile and have just recetly delved into hacking my G1. While I've had no problems installing jesusfreke's images or themes...I'm struggling with how to get fastboot to work.
Perhaps someone can give me some guidance. Anyone willing to give me some simple step by step instructions. I've searched for this and i think I have everything i need, but I'm unable to get to a point where I can type in commands. when i try to run adb, it open very briefly and closes.
What am i doing wrong?
Thanks,
Jason

Go to start -> run -> type in CMD
Navigate to the folder where adb is located.
Then type in adb devices to see if it finds ur device.
If not then make sure you have it plugged in and USB debugging is turned on in the phones settings under Development.
Also download the usb drivers/or the whole SDK if you havent yet.

nosaj13 said:
when i try to run adb, it open very briefly and closes.
Click to expand...
Click to collapse
If you try to execute a text mode executable in windows, it will close the terminal window as soon as the program finishes. If you run adb without any arguments, it will print the arguments out terminate. I could say the solution is to open run as and type cmd, but the true answer is to install Linux

nosaj13 said:
I come from the world of Windows Mobile and have just recetly delved into hacking my G1. While I've had no problems installing jesusfreke's images or themes...I'm struggling with how to get fastboot to work.
Perhaps someone can give me some guidance. Anyone willing to give me some simple step by step instructions. I've searched for this and i think I have everything i need, but I'm unable to get to a point where I can type in commands. when i try to run adb, it open very briefly and closes.
What am i doing wrong?
Thanks,
Jason
Click to expand...
Click to collapse
1. Download this
2. Extract the contents of the fastboot directory to the root of your C drive.
3. Go Start -> Run -> type 'cmd' (no quotes) and hit enter
4. Type 'c:' (no quotes) and hit enter
5. With your phone plugged in, you should be able to type 'adb devices' and it should return your phones serial number, which is usually in HTXXXXXXXX format. If it does not, make sure debugging is enabled on your phone and you have the adb drivers installed.
6. type 'adb shell reboot bootloader' and hit enter. The screen on your phone will go blank for a second and then you should be in the SPL with the skating androids. Make sure you see "FASTBOOT" at the bottom of the screen.
7. type 'fastboot devices' and hit enter. If you see your phone's serial number again, you have successfully established a fastboot connection with the phone and can run commands such as:
fastboot erase <partition> (erases the given partition)
fastboot flash <partition> <file.img> (overwrites and flashes given partition with given file. This is how one would restore from a nandroid backup)
fastboot reboot (reboots the device into user mode)
Hope that helps. Have fun

when i type adp devices i get an error that says "adp is not recognized as an internal or external command, operable program, or batch file"
what am i doing wrong?

nosaj13 said:
when i type adp devices i get an error that says "adp is not recognized as an internal or external command, operable program, or batch file"
what am i doing wrong?
Click to expand...
Click to collapse
First, the command is adb devices not adp. Second, make sure you copied the contents of the fastboot directory to the C drive. Third, make sure you that when you type 'c:' into the command line, the command prompt actually changes to "C:\>"

Datruesurfer said:
1. Download this
2. Extract the contents of the fastboot directory to the root of your C drive.
3. Go Start -> Run -> type 'cmd' (no quotes) and hit enter
4. Type 'c:' (no quotes) and hit enter
5. With your phone plugged in, you should be able to type 'adb devices' and it should return your phones serial number, which is usually in HTXXXXXXXX format. If it does not, make sure debugging is enabled on your phone and you have the adb drivers installed.
6. type 'adb shell reboot bootloader' and hit enter. The screen on your phone will go blank for a second and then you should be in the SPL with the skating androids. Make sure you see "FASTBOOT" at the bottom of the screen.
7. type 'fastboot devices' and hit enter. If you see your phone's serial number again, you have successfully established a fastboot connection with the phone and can run commands such as:
fastboot erase <partition> (erases the given partition)
fastboot flash <partition> <file.img> (overwrites and flashes given partition with given file. This is how one would restore from a nandroid backup)
fastboot reboot (reboots the device into user mode)
Hope that helps. Have fun
Click to expand...
Click to collapse
i did all the above steps with no problem at all till i got to number 7. when i typed in fastboot devices it just goes to the next prompt without my phone showing up.
If i plug in my g1 in normal mode i see it at the top under adb and in the usb section as a mass storage device.
In bootloader mode with fastboot on the screen it doesnt show up anywhere in the device manager.
Also when i follow the above quoted steps and type in the "adb shell reboot bootloader" and hit enter i hear the ding you hear when you unplug a usb device, and all instances of the phone then leave the device manager.
i have also uninstalled and reinstalled all drivers for the phone and all drivers that have to do with the usb ports on my win xp machine.
Anyone have any ideas i could try?

I think you need this program. I put it on my desktop, then just ran cmd, directed to it, and type in fastboot.

I7oobie said:
I think you need this program. I put it on my desktop, then just ran cmd, directed to it, and type in fastboot.
Click to expand...
Click to collapse
thats not it. i have that in the sys 32 folder and also on desktop

Fastboot mode not recognized
I'm having the same problem. I've installed all the correct drivers and in normal mode, I see the Android Composite Device (or something similar) in Device Manager.
As soon as I go into SPL mode (the 3 skateboarding androids screen), the device does not show up.
Anyone have any ideas? Thanks!

Datruesurfer said:
First, the command is adb devices not adp. Second, make sure you copied the contents of the fastboot directory to the C drive. Third, make sure you that when you type 'c:' into the command line, the command prompt actually changes to "C:\>"
Click to expand...
Click to collapse
When I'm in the Command Prompt and I type C:, the directory still reads C:\Documents and Setting\Reids. It won't change to only C:

Hi,
You have to do this to get back to c:
cd\
press enter
That should do it.

bestwebs said:
Hi,
You have to do this to get back to c:
cd\
press enter
That should do it.
Click to expand...
Click to collapse
Ok, thanks a lot. Got it working now.

I need help trying to flash my cupcake images that I have stored in my fastboot folder. I attached the pictures below. I will accept any help I can get.

EDIT: Doh, I thought I was in another topic.
My bad.

Are adb & adb's dll files located inside the same folder as fastboot??? They are suppose too be.
Is your usb cord directly plugged into your system or thru a hub??
Your phone, i bet is under usb mass....to check, expand your device manager window.
Expand your USB-Mass storage list.
With your phone in fastboot mode, click on the camera key and the back key. With enough time inbetween for your system to recognize that there might be a device hooked up.
Notice any change in the list??

Anyone wanting good instructions
http://androidcommunity.com/forums/f28/nandroid-v2-0-full-nand-backup-and-restore-tool-9336/
Read post 2 and go!

this seems like the most easiest thing to do but i still cant get it to work
i have downloaded everything needed and see ADB Interface on my device manager with a yellow mark on it when i try to update the dirver it fails and i got the drivers and point them to it but seems not to work
my phone is on the fastboot screen with the android skateboards guys
i dont know whats going on if someone know what am also doing wrong can tell me please...
This is what i get

sensation stuck on bootloop

i rooted my phone and followed the guide in
http://www.androidauthority.com/how-to-root-htc-sensation-21697/
which worked great and had my phone rooted with S-OFF and full control
then i went to this page and wanted to install a rom and chose
http://forum.xda-developers.com/showthread.php?t=1468683
which i downloaded, after trying to follow the instructions the firmware would install and gave installation aborted so i installed the rom anyways
now the phone boots into the rom but freezes before the loading the phone and restarts.
i am stuck in boot-loop and when trying to recover using the backup it still boot-loops
i think the boot files are corrupt, and i have also tried super-wipe, (super-wipe V2 would load)
even after this i tried installing the custom rom and the backup version and still not working
the firmware still does work and i have tried loading the backup 6 times now using as many different methods such as clearing cache..etc
i even found programs uses to 4EXT_Recovery_Touch_v1.0.0.4_RC3_flashing_tool
and ADB_Fastboot_Windows
but those wont work unless the phone is started and in htc sync/usb mode.
any help would be grateful, i am really getting stressed out for not being able to use my phone

1)You know how to boot into HBOOT, or the bootloader? Do just that.
2) Connect your phone to your computer. You must have all the ADB and SDK drivers installed.
3)Navigate to "Fastboot" using your phones Volume UP and DOWN keys until you reach fastboot. Select using the power button.
4) Go into cmd in Windows.
5)Type the following:
cd C:\Program Files\Android\android-sdk\platform-tools
6)Type the following:
adb getvar cid
7) Remember what the previous command just told you. It could be HTC_001 for example.
8)Thanks to this dev, go to this thread. Find this in the first post:
Firmware from 3.32.401.x & 3.32.401.10x RUU
9)See if your CID is listed. If it is not, DO NOT TRY FLASHING THIS. If it is, download the file and flash in HBOOT using the PG58IMG.zip method. Make sure it isn't called PG58IMG.zip.zip.
10) If it isn't listed, use STEP 4 in this post, then flash it.
RE-POST THIS!!! Save devs time to building ROMs and save hassle.

i have followed your steps to number 3, now it says "fastboot ac" on phone
with step 5 i found the folder in this directory
C:\Program Files (x86)\Android\android-sdk
after typing in the command after navigating there i get this
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Owner>cd C:\Program Files (x86)\Android\android-sdk\platform-tools
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb getvar cid
Android Debug Bridge version 1.0.29
-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 command 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 backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
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:\Program Files (x86)\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
and now im stuck as to where to find htc_001
sorry for sounding noobish as im new to this but can you please tell me what i have done wrong to where to go from here ??

Once in that directory type fastboot getvar cid
Then write down the CID that shows up.
If it doesn't match one in the list of compatible firmware then you'll have to super CID to 11111111.
Edited because I wasn't thinking.

You have to use fastboot, not adb
Sent from my HTC Sensation with Beats Audio using xda premium

ok i have tried that now it is saying "waiting for device"
the phone is still not being picked up by the computer either by htc sync or by the program through command prompt.
fastboot changes to fastboot ac, not sure if that means its just on charge only and not any other mode

Unplug the phone and pull the battery. Then boot the phone back into the initial recovery screen (vol down + power on)
Connect phone to computer. In a cmd prompt navigate to cd C:\Program Files\Android\android-sdk\platform-tools
Type adb devices (Should come back with serial number)
Type fastboot getvar cid
Hopefully that pulls the CID. Let us know.

i have tried this over several times , it still does not pick up the device.
any other ways to get this to work ??

Have you just installed the SDK? Open the SDK, and a pop-up should come up. Select Android USB drivers or something similar to it. Check it and install. Try again after this.
Sent from my Wildfire using Tapatalk 2 Beta-5

You also need to have your fast boot drivers in the directory that you cd to to issue your fastboot commands.
sent from HTC Pyramid using Tapatalk

usaff22 said:
Have you just installed the SDK? Open the SDK, and a pop-up should come up. Select Android USB drivers or something similar to it. Check it and install. Try again after this.
Sent from my Wildfire using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
stringer7 said:
You also need to have your fast boot drivers in the directory that you cd to to issue your fastboot commands.
sent from HTC Pyramid using Tapatalk
Click to expand...
Click to collapse
i have made sure that the usb drivers have been installed infact i uninstalled htc sync and android sdk and reinstalled them both and made sure the drivers are installed.
on there is doesnt say anything like android usb drivers but Google usb drivers is the closest, basically the default settings installed.
for the drivers htc sync has been installed it is also failing to detect my phone.
stringer7, i have made sure i am in the directory and it checks for devices, but it fails to find my htc sensation.
Ive had this phone for 2 months now of a 24 month contract.
now i just want to reformat it all and install the stock version over, and see if i can get my backup back as it has all my contacts and messages on it which i thought were on the sim.

wbb1 said:
i have made sure that the usb drivers have been installed infact i uninstalled htc sync and android sdk and reinstalled them both and made sure the drivers are installed.
on there is doesnt say anything like android usb drivers but Google usb drivers is the closest, basically the default settings installed.
for the drivers htc sync has been installed it is also failing to detect my phone.
stringer7, i have made sure i am in the directory and it checks for devices, but it fails to find my htc sensation.
Ive had this phone for 2 months now of a 24 month contract.
now i just want to reformat it all and install the stock version over, and see if i can get my backup back as it has all my contacts and messages on it which i thought were on the sim.
Click to expand...
Click to collapse
u mean that you boot into bootloader, u see written HBOOT on the screen, then u connect the usb cable coming from a computer on which both htc sync and ADK/SDK installed (not running, but installed) and HBOOT turns into FASTBOOT USB on the screen but u cant send fastboot commands?

dowanrac said:
u mean that you boot into bootloader, u see written HBOOT on the screen, then u connect the usb cable coming from a computer on which both htc sync and ADK/SDK installed (not running, but installed) and HBOOT turns into FASTBOOT USB on the screen but u cant send fastboot commands?
Click to expand...
Click to collapse
when i connect the phone to my computer i manually go to fastboot option using the power key then from there it will say fastboot ac
or if i connect after in fastboot it will change to "fastboot ac"
now im gonna try reinstall the whole setup on another machine or try dualboot with ubuntu and try the drivers through that,

wbb1 said:
when i connect the phone to my computer i manually go to fastboot option using the power key then from there it will say fastboot ac
or if i connect after in fastboot it will change to "fastboot ac"
now im gonna try reinstall the whole setup on another machine or try dualboot with ubuntu and try the drivers through that,
Click to expand...
Click to collapse
grab a photo of the screen - bootloader screen when u connect. lets see what u got there.
i think its only a communication problem with pc. message on screen should be fastboot USB. not fastboot AC. so it means u simply dont have the proper drivers. if u get a different computer, just install htc sync, reboot computer after that and make sure htc sync program aint running. then connect phone in bootloader. if it says fastboot usb, go to ADK step. if not... weird...

dowanrac said:
grab a photo of the screen - bootloader screen when u connect. lets see what u got there.
i think its only a communication problem with pc. message on screen should be fastboot USB. not fastboot AC. so it means u simply dont have the proper drivers. if u get a different computer, just install htc sync, reboot computer after that and make sure htc sync program aint running. then connect phone in bootloader. if it says fastboot usb, go to ADK step. if not... weird...
Click to expand...
Click to collapse
heres the photo of the bootloader that shows when connecting to pc
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i also tried this on another computer and it still shows the same message. i would try on linux ubuntu but cant seem to find htc sync for it.
any more ideas ??

Try Google USB Drivers. Install that.
And please DO try and make your pictures a bit smaller

ok i found out my usb cable was the reason and now after getting a new one i get "fastboot usb"
after typing the code on first page i get this, the device is not listed but it shows htc_001 with getvar cid
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar cid
cid: HTC__001
finished. total time: 0.002s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
i am now going to try supercid to see if i can move forward in finally getting my phone working.
EDIT:
it is working now, after 3 long days of no phone,
after installing the rom i used my backup to "advanced backup" to get my data back which gave my old apps and messages along with contacts

Not able to download firmware from link provided.
usaff22 said:
1)You know how to boot into HBOOT, or the bootloader? Do just that.
2) Connect your phone to your computer. You must have all the ADB and SDK drivers installed.
3)Navigate to "Fastboot" using your phones Volume UP and DOWN keys until you reach fastboot. Select using the power button.
4) Go into cmd in Windows.
5)Type the following:
cd C:\Program Files\Android\android-sdk\platform-tools
6)Type the following:
adb getvar cid
7) Remember what the previous command just told you. It could be HTC_001 for example.
8)Thanks to this dev, go to this thread. Find this in the first post:
Firmware from 3.32.401.x & 3.32.401.10x RUU
9)See if your CID is listed. If it is not, DO NOT TRY FLASHING THIS. If it is, download the file and flash in HBOOT using the PG58IMG.zip method. Make sure it isn't called PG58IMG.zip.zip.
10) If it isn't listed, use STEP 4 in this post, then flash it.
RE-POST THIS!!! Save devs time to building ROMs and save hassle.
Click to expand...
Click to collapse
Hello,
Im in the same situation and I know how to boot load the firmware. My problem is that when I go to the link provided to download Firmware 3.32.401.x & 3.32.401.10x RUU, it sends me to another website that is down. is there somewhere ales I can find this file? I have been trying for days and I always get the following message.
Not Found
The requested URL /db_mirror/ROMs/HTC Sensation/Firmware/3.32.401.x/PG58IMG.zip was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Apache/2 Server at xda3.androidrevolution.nl Port 80

[Q] Root Xoom with linux ?

i ditched windows ages ago and i will never look back i am sick and tierd of waiting on moto uk to push ics. i use to have the dell streak and i rooted that but i was on windows then how do i root my xoom with linux mint is it possible and can any point me in the right direction please

Stand by, I will give you all the tools and options you need to do so, I could draft something tomorrow morning.
Sent from my PG86100 using Tapatalk

Thank you megabiteg Still learning linux but i Love it
megabiteg said:
Stand by, I will give you all the tools and options you need to do so, I could draft something tomorrow morning.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse

well, it isn't that hard since everything you really need on your computer ist fastboot and a way to push a file to an sdcard (fat formatted)...
Just go here, download and install the android sdk from there. Make sure the commands adb and fastboot are in your path. (test by issuing adb devices, shold return a list of attached android devices with usb debugging turned on)
After that, just follow these instructions. I am not sure if you need to run fastboot as root, but you'll see

Cheers for the info just by any chance do you know the commands still learning Linux
llama-power said:
well, it isn't that hard since everything you really need on your computer ist fastboot and a way to push a file to an sdcard (fat formatted)...
Just go here, download and install the android sdk from there. Make sure the commands adb and fastboot are in your path. (test by issuing adb devices, shold return a list of attached android devices with usb debugging turned on)
After that, just follow these instructions. I am not sure if you need to run fastboot as root, but you'll see
Click to expand...
Click to collapse

elsworth1983 said:
Cheers for the info just by any chance do you know the commands still learning Linux
Click to expand...
Click to collapse
thought you ditched windows ages ago?
anyhow... don't have linux set up atm, so this will from memory and might contain some errors... Also, never tried mint, I always stuck to debian or debian-derivates...
anyhow, lets try this:
first, use your package management-system to install a jre (java runtime environment.
If that is set up, install the android sdk:
Code:
$ cd ~
$ wget http://dl.google.com/android/android-sdk_r17-linux.tgz
$ sudo su
[enter your su-password]
# cd /usr/local
# tar xfzv ~[yourusername]/android-sdk_r17-linux.tgz
# ./android-sdk-linux/tools/android
a window should open up and list some files available for download. Just select "Android SDK Platform-tools" and hit "Install 1 package...".
once that's finished (might take a while), close the Android SDK Manager and you should get back to your shell.
Code:
# ln -s /usr/local/android-sdk-linux/platform-tools/adb /usr/local/bin/adb
# ln -s /usr/local/android-sdk-linux/platform-tools/fastboot /usr/local/bin/fastboot
# exit
$ rm android-sdk_r17-linux.tgz
now, connect your xoom to your computer and enable usb debugging in the settings of your xoom. If you issue adb devices, you should get something like
Code:
List of devices attached
043c12343456476547 device
if you receive something like bash: adb: command not found, something went wrong somewhere. Try the same using sudo: sudo adb devices if that doesn't fix it please write another post.
Also, if you encounter an error after entering any of the comments above, please do not continue until you resolved that error. (For example ask for a solution here)
And, since you are still learning to use linux: whenever instructions contain a $ or # at the beginning of a line, DO NOT ENTER THESE. They are just there to tell you to issue that command as normal user ($) or superuser (#)
/EDIT: btw: there may be an easier way to do this if you just want to use adb/fastboot this once: you could try to simply download the adb and fastboot- binaries and put these into the folder with your recovery.img-file. Might work, not sure about that, though. Also, since I don't have linux installed on my machine atm, I can't provide you with a link to these binaries.

cheers for all your help will give this a go "Dont want to back to windows

Android SDK manger log
Error Stopping ADB server failed (code-1)
Connected the xoom and did adb devices and it listed the xoom with no errors in the terminal Thank you again ? Were do i go from here now

glad to read it's working
just follow the instructions in this thread That will help you to install a custom recovery and root your xoom. It will not, however, install a custom rom. To do that, you'd also need to download a custom rom (usually comes in a flashable .zip-file), place that on an acutal sd-card which you're gonna put into your xoom, and install that file from within the custom recovery. Just make sure you grab a rom that works with your xoom (for example, you shouldn't put a us-4g-rom onto a wifi-only-xoom and vice versa)

have i done something wrong
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot oem unlock
fastboot: command not found
The problem i seem to be having is when the xoom is on i type <adb reboot bootloader> The xoom reboots to the fastboot screen after that no commands work and when i do ADB devices in the terminal the device list is empty ?

elsworth1983 said:
have i done something wrong
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot oem unlock
fastboot: command not found
Click to expand...
Click to collapse
have you done the # ln -s /usr/local/android-sdk-linux/platform-tools/fastboot /usr/local/bin/fastboot? The error you're getting seems to suggest that it can't find the fastboot application? What happens if you type /usr/local/android-sdk-linux/platform-tools/fastboot oem unlock?
elsworth1983 said:
The problem i seem to be having is when the xoom is on i type <adb reboot bootloader> The xoom reboots to the fastboot screen after that no commands work and when i do ADB devices in the terminal the device list is empty ?
Click to expand...
Click to collapse
that is expected. adb is only available while android is booted up, fastboot is the protocol to use while in bootloader mode. As indicated before, I suspect that your computer can't find the fastboot application (on the computer).

Cheers for all the info i went back and started all from the top again only thing i am struggling with is Flashing the recovery now lol i get
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot flash recovery recovery-solarnz-100611-1150.img
error: cannot load 'recovery-solarnz-100611-1150.img'
I have it on a memory card which i checked which was working

elsworth1983 said:
Cheers for all the info i went back and started all from the top again only thing i am struggling with is Flashing the recovery now lol i get
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot flash recovery recovery-solarnz-100611-1150.img
error: cannot load 'recovery-solarnz-100611-1150.img'
I have it on a memory card which i checked which was working
Click to expand...
Click to collapse
The recovery image needs to be on your pc. It doesn't matter where on your pc as long as you can access it and know where it is.
Fastboot works by sending the image over the usb cable. Once you start flashing roms, those will need to be on your sd card within the xoom.

all i can say is thank you for all the information every 1 is giving me my head is mashed lol so if i put recovery-Tiamat-R4c-100611-1150-cwm.img on the desktop what would the terminal code be
kofrad said:
The recovery image needs to be on your pc. It doesn't matter where on your pc as long as you can access it and know where it is.
Fastboot works by sending the image over the usb cable. Once you start flashing roms, those will need to be on your sd card within the xoom.
Click to expand...
Click to collapse

depends on where your desktop is If it is in ~/Desktop/, then the correct command should be
Code:
fastboot flash recovery ~/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img

error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)

What am doing so wrong its lucky am not bold yet been trying this all day

elsworth1983 said:
error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)
Click to expand...
Click to collapse
if the graphical interface, where do you see the file located?

elsworth1983 said:
error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)
Click to expand...
Click to collapse
Sounds to me like you are running the commands as root. You likely have also downloaded the recovery image as a normal user. This means the '~' shortcut for the home directory is pointing you to someplace where the file is not.
Try using "fastboot flash /home/Your username/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img"

I have put the file on the desktop ? is that what u mean

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

READ THIIS!
*this thread is for E8. it will NOT work on m7,or any older device. please check the general forum for your particular device for a similar thread.
this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or locked back to stock.
advantages
-no hassle with htcdev,tokens,or unlock codes
-no submitting your phones personal info to htc
-the ability to get back to 100% stock without any visual traces or records of having been s off or unlocking your bootloader.
you do NOT need to downgrade your hboot. this simple adb command works without any scary hboot downgrades.
*you must be s off.
*you must have superuser installed
read this:
this will not work if your s on. its not a way to magically unlock
the usual disclaimers:
use this info at your own risk. if it melts your phone into a little pile of aluminum goo,its not my fault.
credits
-beaups for schooling me on echo comand protocol
-strace for originally discovering the location of the lock status flag(check out this thread for more info)
-ian.anindya and a couple others have provided dumps. let me know and ill add you to the credits. if someone wants to provide screen shots,i can add those as well.
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb(windows 7 and older)
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "lock status flag"
to LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now locked
_____________________________________________________________________________________________
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now unlocked
(yes this is m7. i dont have an E8. if someone wants to provide correct screenshots,ill add them)
other useful threads:
remove tampered banner: http://forum.xda-developers.com/one-e8/general/how-to-remove-tampered-banner-t3019164
change mid without an eng bootloader: http://forum.xda-developers.com/one-e8/general/how-to-change-mid-eng-bootloader-t3019148

sorry for the delay,guys. hope you find it useful

This way doesn't wipe out all the data, right?

buggerman said:
This way doesn't wipe out all the data, right?
Click to expand...
Click to collapse
Correct. It will not wipe any data
Sent from my HTC One max

Good job.
Any way to do S-OFF to S-ON ??
greg

gregferns said:
Good job.
Any way to do S-OFF to S-ON ??
greg
Click to expand...
Click to collapse
Sunshine again..

windows 8 and above
am using windows 10 but it seems the required tool does not support the operating system
any other option for me?

cant get # prompt
hi, when i enter the Su command it says su not found and the prompt still remains $ instead of #. Is it something am not getting right or something. Thanks

Unlocking Bootloader [Incomplete]

Note: It would be great to keep this page open while following through on your PC instead of your phone as you'll be rebooting and resetting your phone by following this procedure.
Click to expand...
Click to collapse
Prerequisites:
ADB (Android Debugging Bridge) tools for your OS (Windows/Linux/Mac)
Windows
Mac
Linux
Custom Recovery Image (TWRP or some other that you prefer):
(Official TWRP web hosted version) Nokia 6.1 (2018)
Download from American Mirrors
Download from EU Mirrors
USB Cable to Connect the phone to the computer
The Phone: Nokia 6.1 (2018) (preferably Fully Charged)
The device drivers (for Windows and Mac)
A good and active Internet Connection
An active Email address and client to quickly view it.
In this tutorial I'll be referring to Linux terminal, Mac Terminal & Windows Command prompt/Powershell simply as terminal.
Click to expand...
Click to collapse
Installing adb and fastboot
Google hosts zips including only adb and fastboot. You can set these up for use with the instructions below.
On Windows
Download the (Windows.zip) from Google.
Extract it somewhere - for example, %USERPROFILE%\adb-fastboot
• On Windows 7/8:
1. From the desktop, right-click My Computer and select Properties
2. In the System Properties window, click on the Advanced tab
3. In the Advanced section, click the Environment Variables button
4. In the Environment Variables window, highlight the Path variable in the Systems Variable section and click the Edit button
5. Append ";%USERPROFILE%\adb-fastboot\platform-tools" to the end of the existing Path definition (the semi-colon separates each path entry)
• On Windows 10:
1. Open the Start menu, and type “advanced system settings”
2. Select “View advanced system settings”
3. Click on the Advanced tab
4. Open the “Environment Variables” window
5. Select the Path variable under “System Variables” and click the “Edit” button
6. Click the “Edit Text” button
7. Append ";%USERPROFILE%\adb-fastboot\platform-tools" to the end of the existing Path definition (the semi-colon separates each path entry)
• Install the device drivers linked in prerequisites (or from Nokia support site), and reboot.
On MacOS
Download the MacOS (Darwin.zip) from Google.
Extract it somewhere - for example, ~/adb-fastboot.
Add the following to ~/.bash_profile:
Code:
if [ -d "$HOME/adb-fastboot/platform-tools" ] ; then
export PATH="$HOME/adb-fastboot/platform-tools:$PATH"
fi
Log out and back in.
On Linux
Download the (Linux.zip) from Google.
Extract it somewhere - for example, ~/adb-fastboot.
Add the following to ~/.profile:
Code:
if [ -d "$HOME/adb-fastboot/platform-tools" ] ; then
export PATH="$HOME/adb-fastboot/platform-tools:$PATH"
fi
Log out and back in.
You may also need to set up udev rules: see (this repository) for more info.
Setting up adb
To use adb with your device, you’ll need to enable developer options and USB debugging:
1. Open Settings, and select “About”.
2. Tap on “Build number” seven times.
3. Go back, and select “Developer options”.
4. Scroll down, and check the “Android debugging” entry under “Debugging”.
5. Plug your device into your computer.
6. On the computer, open up a terminal/command prompt and type adb devices.
7. A dialog should show on your device, asking you to allow usb debugging. Check “always allow”, and choose “OK”.
Congratulations! adb is now ready to use with your device.
Unlocking the bootloader
Note: The steps below only need to be run once per device.
Code:
Warning: Unlocking the bootloader will erase all data on your device! Before
proceeding, ensure the data you would like to retain is backed up to your PC and/or
your Google account, or equivalent.
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging & OEM unlocking on your device under Settings->Developer Options. Incase you don't see Developer Options, then you need to unlock it by tapping Build Number 7 times in Settings->About Phone.
3. Get the current status of your bootloader:
Open a terminal on the PC and boot the device to fastboot mode by typing:
Code:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC finds it by typing:
Code:
fastboot devices
If you see "no permissions fastboot" or "<waiting for device>", try running
Code:
fastboot
as root/Administrator.
From the same terminal, type the following command to get the bootloader status:
Code:
fastboot oem device-info
4. Follow the instructions at (Nokia Support) to unlock your bootloader, you will need to register at this site with a working/active email to proceed. They'll verify your device using an app to issue a validation code.
Note: If your device is not supported by the Nokia Bootloader Unlock
website, you will need to use an alternative bootloader unlock method.
Installing a custom recovery using fastboot
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging & OEM unlocking on your device under Settings->Developer Options. In case you don't see Developer Options, then you need to unlock it by tapping Build Number 7 times in Settings->About Phone. This needs to be done again due to resetting of your phone.
3. Download recovery - visit twrp.me to obtain the latest version of Team Win
Recovery Project for your device. Nokia 6.1 (2018) does have an official TWRP recovery that you can find here: Nokia 6.1 (2018) [PL2] respectively.
4. Connect your device to your PC via USB.
5. Open a terminal on the PC and boot the device to fastboot mode by typing:
Code:
adb reboot bootloader
6. Once the device is in fastboot mode, verify your PC finds it by typing:
Code:
fastboot devices
If you see "no permissions fastboot" or "<waiting for device>" , try running
Code:
fastboot
as root/Administrator.
7. Boot into TWRP temporarily:
Code:
fastboot boot twrp.img
8. Use adb to push the zip onto your device:
Code:
adb push twrp.zip /
9. Go to `Install` option on the TWRP menu and browse to the zip (Scrolling to the bottom should have the zip) and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
If you accidentally flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
Click to expand...
Click to collapse
This command assumes the recovery image is present in your current working directory (Check using `DIR` on command prompt or `ls` command on terminal)
If it isn't you can change your current directory to the directory containing the recovery image or copy/move the recovery image to your current working directory.
10. Now reboot into recovery to verify the installation:
That's all folks. You may now root your phone, or even flash a custom ROM. I suggest getting openGapps for the custom ROM if you wish to use Google play services on the custom ROM.
Popular adb commands
Code:
adb shell
Launches a shell on the device accessed through the terminal on your computer.
Code:
adb push <local> <remote>
Pushes the file <local> to <remote>
Code:
adb pull <remote> [<local>]
Pulls the file <remote> to <local>. If <local> isn’t specified, it will pull to the current folder.
Code:
adb logcat
Allows you to view the device log in real-time. You can use adb logcat -b radio to view radio logs, and adb logcat -C to view logs in colour
Code:
adb install <file>
Installs the given .apk file to your device
<local> refers to location on your computer (like c:\\Users\%USERPROFILE%\adb-fastboot on windows or ~/adb-fastboot on unix based OS), while <remote> refers to location on your android device (like "/sdcard/", without quotes)

Reserved

What do you do if oem unlocking in developer is greyed out? TA-1045

@toxicmender The official bootloader unlock was only released to the Nokia 8. So, what is the point posting it here?
Or have they silently added the 6.1?

singhnsk said:
@toxicmender The official bootloader unlock was only released to the Nokia 8. So, what is the point posting it here?
Or have they silently added the 6.1?
Click to expand...
Click to collapse
Unfortunately no, they haven't, removed the [incomplete] tag prematurely after reading it somewhere.
Currently only known way to unlock Nokia 6.1 seems to be to flash signature file.bin from these guys for fee.
at Step 4:
Code:
fastboot flash signature signature_file.bin
Also it has follow up instructions for flashing TWRP for anyone who has successfully unlocked their bootloader, since flashing TWRP is a bit different from most other phones

toxicmender said:
Unfortunately no, they haven't, removed the [incomplete] tag prematurely after reading it somewhere.
Currently only known way to unlock Nokia 6.1 seems to be to flash signature file.bin from these guys for fee.
at Step 4:
Code:
fastboot flash signature signature_file.bin
Also it has follow up instructions for flashing TWRP for anyone who has successfully unlocked their bootloader, since flashing TWRP is a bit different from most other phones
Click to expand...
Click to collapse
Why would you make start this thread then? It is completely pointless and misleading.
It is like making a post saying that there are flying cars and marking it [Incomplete]. It is just ****ing stupid.
I hope you drop your 6.1 and break it so you make **** posts in other phone forums instead of this one.

cmaxwe said:
.
I hope you drop your 6.1 and break it so you make **** posts in other phone forums instead of this one.
Click to expand...
Click to collapse
Hey now, there is really no need for that level of hostility. He knew they were doing unlocks for at least one Nokia phone, and me may not have known that they didn't have it for the 6.1.
Please don't talk to peope like that if they make a simple mistake when trying to provide info and help out the community. We're all human.

toxicmender said:
Unfortunately no, they haven't, removed the [incomplete] tag prematurely after reading it somewhere.
Currently only known way to unlock Nokia 6.1 seems to be to flash signature file.bin from these guys for fee.
at Step 4:
Code:
fastboot flash signature signature_file.bin
Also it has follow up instructions for flashing TWRP for anyone who has successfully unlocked their bootloader, since flashing TWRP is a bit different from most other phones
Click to expand...
Click to collapse
Honestly if there was a good amount of roms available for this phone I would gladly pay the $5 to unlock bootloader, although that method leaves me with questions. does that method survive ota? Does it actually work? Can it relock and unlock without paying again?
Is there really not that many people on here willing to try unlocking and flashing the many gsi roms available?

cmaxwe said:
Unfortunately no, they haven't, removed the [incomplete] tag prematurely after reading it somewhere.
Currently only known way to unlock Nokia 6.1 seems to be to flash signature file.bin from these guys for fee.
at Step 4:
Why would you make start this thread then? It is completely pointless and misleading.
It is like making a post saying that there are flying cars and marking it [Incomplete]. It is just ****ing stupid.
I hope you drop your 6.1 and break it so you make **** posts in other phone forums instead of this one.
Click to expand...
Click to collapse
It's not like there isn't a way, there is, just not a transparent method. Somehow those (refer to link in reply) are able to generate and send the signature file allowing you to unlock the phone, how it works or if your bootloader be locked again after updating is unknown to me ATM

mymeatb18 said:
Unfortunately no, they haven't, removed the [incomplete] tag prematurely after reading it somewhere.
Currently only known way to unlock Nokia 6.1 seems to be to flash signature file.bin from these guys for fee.
at Step 4:
Honestly if there was a good amount of roms available for this phone I would gladly pay the $5 to unlock bootloader, although that method leaves me with questions. does that method survive ota? Does it actually work? Can it relock and unlock without paying again?
Is there really not that many people on here willing to try unlocking and flashing the many gsi roms available?
Click to expand...
Click to collapse
Well the ROM development begins after an Official TWRP recovery, so the chances are there might be some. I'm not clear on the the OTA being able to relock the bootloader either since I was running Pie update when I got to know about it.

thread closed as per OP request