Database Develop

[Q] Unlock Bootloader Problem

Hi guys, I have a problem.
I want to flash my N1 with the Cyanogenmod, but I have a problem with Bootloader unlocking. I do exactly what here is written (in the N1 guide from wiki.cyanogenmod), but when I open CMD (win XP) and write "fastboot oem unlock", it just doesn't works, but "adb devices" works and shows my phone. What can I do ? Any ideas ?

You need to boot into bootloader to work with fastboot. And if "adb devices" shows your phone - you obviously didn't boot.
adb reboot bootloader
Click to expand...
Click to collapse
Also, for a more comprehensive guide, please read the Wiki.

Code:
C:\fastboot>fastboot oem unlock
'fastboot' is not recognized as a
operable program or batch file.
This is what it shows in bootloader mode.
P.S. I have already re-installed my drivers. I have to notice that when I try to reinstall the drivers (in fastboot mode), they always auto-install themselves and when I try to update them, they say that there isn't newer version.

Fastboot executable isn't in the same directory as ADB executable, and isn't in the path you're executing it from (which is C:\fastboot).
Check, what is the actual executable you're trying to run, and if you have one. It might be called fastboot-windows.exe, if you didn't get it from downloading the Android SDK.

There is a executable file named "fastboot-windows.exe", but when I try to run it, it just open and close for 1 second. Any ideas ?

I thought the message would be clear by now... Oh well.
Open command prompt.
Run:
fastboot-windows oem unlock
Click to expand...
Click to collapse

I think It's done but my computer shows this message (see attached) 5 mins and I don't know it's ready or not ? Could I turn on the phone ? (Sry for the easy questions but I'm a real noob, because that's my 1st Android phone.)

The "too many links" message doesn't look good.
Reboot your computer.
Reboot the phone.
Use different USB port in your computer.

Ok well if you want my input try "fastboot devices" this should return your S/N (starting with "HT") if it gives you the same error then I would reinstall the SDK.

Some Honeycomb 514 Tips.

Edit: this is about Streak 7 Honeycomb 514 installation tips, I fixed the tile
I have installed ROMs on my Viewsonic gPad. Piece of cake, the process is straightforward and there were no wild goose chases looking for drivers. I never appreciated how easy the gTab was until I dealt with this nightmarish Streak 7.
I started at 6 pm last night, gave up at 2:30am, woke up at 7:30 this morning, and now (at 8:15) it is HOPEFULLY going to reboot into Gingerbread. And it looks successfull!
Some tips:
The general process
I followed the general instructions on the 506 update thread, but I used a 514 ROM.
You can add the update.img file to your external SD card using windows explorer, but you can't use windows explorer to add the recovery file to the recovery partition. One way to do that, is with Fastboot. The whole fastboot process includes:
-placing the tablet in fastboot mode
-connecting the tablet to the computer via USB
-installing drivers (hopefully, first time only)
-running fastboot.exe
-using a command prompt to move the recovery.img file onto the tablet's recovery partition
Fastboot and the recovery file are where I had my problems, so I added a few tips here.
ROM and Recovery
Get the 514 ROM and recovery files from here: here
NOTE: I could not get the 514 US 4G recovery to work, so I used the US Stock Froyo recovery.img from the 506 update thread.
Fastboot Guide
Use this page as a general guide for installing Fastboot and Flashing/Updating, but it is by no means comprehensive.
Finding Fastboot Drivers
Drivers for fastboot were a big sticking point for me. To get Streak 7 drivers: I connected my Streak 7 to my computer, enabled USB sharing on my tablet, and then in Windows file explorer find the streak and do a search for 'drivers'. It will found the folder (using a search for 'drivers') on the Streak that contains the drivers I need. There are drivers included in the fastboot download but the fastboot drivers did not work for me.
My approach for setting up/using fastboot
Download fastboot (it's actually fastboot and adb)
Extract the zip (I put it in c:\android)
Enter fastboot mode on device
Connect phone pc with usb cable.
Install approporate driver extracted from your streak (or try the ones from fastboot, they didn't work for me but maybe they will work for you)
Note: I installed drivers in fastboot mode AND in regular android mode, but I spent a long time working on drivers so that might not be necessary
Note 2: I installed the free 'Nero' software from Dell because someone else with similar problems also installed that software, IDK if it helped either one of us but who knows. I recommend not installing Nero just for this task, because most people don't seem to need it.
Note 3: After driver is installed, the streak will still say what it always says in fastboot mode: some red text followed by some white text. The fact that you have installed fastboot on your PC will not cause a change on the screen of your Streak 7 when it is connected to the PC.
run 'fastboot.exe'
a black window will appear and disappear very quickly.
open a command prompt type c:\android>fastboot devices
the command prompt should return something like '? fastboot'
This step lets you know you have fastboot working properly.
Now that you know fastboot is working, it's time to move your new recovery file to the Streak's recovery partition. Type C:\android>fastboot flash recovery recovery.img
If you forgot how to use a command line: you will need to use the 'cd' command to navigate to the folder your recovery.img file is in. It will be easy enough to find on the internet, and I am too tired to explain now. If you happened to place your files in C:\android, you can get there by typing 'cd\' (no quotes) and hitting enter, then typing 'cd android' and hitting enter.
in the above text, 'C:\android>' is the prompt you will see after using the 'cd' command. If you have your recovery file somewhere else, you must alter this prompt with the CD command so it reflects the recovery file's location.
in the above text, 'fastboot' tells your computer to use fastboot commands. Make sure you ran fastboot.exe. There is also a way to change environmental settings/path so that it will work whenever you have an android device plugged in, but I couldn't find the thread that discussed it.
in the above text, 'flash' is a command to write a file to a particular partition.
in the above text, 'recovery' is the partition being written to is the recovery partition.
in the above text, 'recovery.img' is the name of the file being copied to the tablet.
in the above text, 'C:\android' is the location of the file being copied.
I know I'm overtired and I need to go back to sleep because I'm doing an anal-retentive job of explaining how to use functions that you can read by typing in 'fastboot help'. But I've lost a bit of rational thinking and I am compelled to work on formatting and adding bullets so it looks pretty.
The command prompt will give you a couple of lines saying how long it took to move the file.
Finished!
Make sure you have a new update.pkg file on your external SD card, boot into recovery, and install your update.

Are you sure you are in the right section? This is Streak7 not Streak5

giveen said:
Are you sure you are in the right section? This is Streak7 not Streak5
Click to expand...
Click to collapse
Lol I changed the title. Yup, I was talking about the Streak 7.

Now you are making some sense, lol.

mike_ekim said:
Edit: this is about Streak 7 Honeycomb 514 installation tips, I fixed the tile
I have installed ROMs on my Viewsonic gPad. Piece of cake, the process is straightforward and there were no wild goose chases looking for drivers. I never appreciated how easy the gTab was until I dealt with this nightmarish Streak 7.
I started at 6 pm last night, gave up at 2:30am, woke up at 7:30 this morning, and now (at 8:15) it is HOPEFULLY going to reboot into Gingerbread. And it looks successfull!
Some tips:
The general process
I followed the general instructions on the 506 update thread, but I used a 514 ROM.
You can add the update.img file to your external SD card using windows explorer, but you can't use windows explorer to add the recovery file to the recovery partition. One way to do that, is with Fastboot. The whole fastboot process includes:
-placing the tablet in fastboot mode
-connecting the tablet to the computer via USB
-installing drivers (hopefully, first time only)
-running fastboot.exe
-using a command prompt to move the recovery.img file onto the tablet's recovery partition
Fastboot and the recovery file are where I had my problems, so I added a few tips here.
ROM and Recovery
Get the 514 ROM and recovery files from here: here
NOTE: I could not get the 514 US 4G recovery to work, so I used the US Stock Froyo recovery.img from the 506 update thread.
Fastboot Guide
Use this page as a general guide for installing Fastboot and Flashing/Updating, but it is by no means comprehensive.
Finding Fastboot Drivers
Drivers for fastboot were a big sticking point for me. To get Streak 7 drivers: I connected my Streak 7 to my computer, enabled USB sharing on my tablet, and then in Windows file explorer find the streak and do a search for 'drivers'. It will found the folder (using a search for 'drivers') on the Streak that contains the drivers I need. There are drivers included in the fastboot download but the fastboot drivers did not work for me.
My approach for setting up/using fastboot
Download fastboot (it's actually fastboot and adb)
Extract the zip (I put it in c:\android)
Enter fastboot mode on device
Connect phone pc with usb cable.
Install approporate driver extracted from your streak (or try the ones from fastboot, they didn't work for me but maybe they will work for you)
Note: I installed drivers in fastboot mode AND in regular android mode, but I spent a long time working on drivers so that might not be necessary
Note 2: I installed the free 'Nero' software from Dell because someone else with similar problems also installed that software, IDK if it helped either one of us but who knows. I recommend not installing Nero just for this task, because most people don't seem to need it.
Note 3: After driver is installed, the streak will still say what it always says in fastboot mode: some red text followed by some white text. The fact that you have installed fastboot on your PC will not cause a change on the screen of your Streak 7 when it is connected to the PC.
run 'fastboot.exe'
a black window will appear and disappear very quickly.
open a command prompt type c:\android>fastboot devices
the command prompt should return something like '? fastboot'
This step lets you know you have fastboot working properly.
Now that you know fastboot is working, it's time to move your new recovery file to the Streak's recovery partition. Type C:\android>fastboot flash recovery recovery.img
If you forgot how to use a command line: you will need to use the 'cd' command to navigate to the folder your recovery.img file is in. It will be easy enough to find on the internet, and I am too tired to explain now. If you happened to place your files in C:\android, you can get there by typing 'cd\' (no quotes) and hitting enter, then typing 'cd android' and hitting enter.
in the above text, 'C:\android>' is the prompt you will see after using the 'cd' command. If you have your recovery file somewhere else, you must alter this prompt with the CD command so it reflects the recovery file's location.
in the above text, 'fastboot' tells your computer to use fastboot commands. Make sure you ran fastboot.exe. There is also a way to change environmental settings/path so that it will work whenever you have an android device plugged in, but I couldn't find the thread that discussed it.
in the above text, 'flash' is a command to write a file to a particular partition.
in the above text, 'recovery' is the partition being written to is the recovery partition.
in the above text, 'recovery.img' is the name of the file being copied to the tablet.
in the above text, 'C:\android' is the location of the file being copied.
I know I'm overtired and I need to go back to sleep because I'm doing an anal-retentive job of explaining how to use functions that you can read by typing in 'fastboot help'. But I've lost a bit of rational thinking and I am compelled to work on formatting and adding bullets so it looks pretty.
The command prompt will give you a couple of lines saying how long it took to move the file.
Finished!
Make sure you have a new update.pkg file on your external SD card, boot into recovery, and install your update.
Click to expand...
Click to collapse
i would just like to add that you can go to the folder with fastboot.exe and the recovery.img and in my win7 64bit i just hold shift + right click and choose open cmd windows here note* not sure if this is a special feature of my win7 or not tho so other user who dont see it dont panic use above steps thought it may help tho
and i read a post baout using the 506 recovery img but theres a post saying it was updated idk cant find link now to it but if it works then good i myself am in the process of charging my 7 before i can see if it will accept the update.pkg now cause i tryed without changing the img im on stock 2.2.2 4g tmobile one

colorsharpkid said:
and i read a post baout using the 506 recovery img but theres a post saying it was updated idk cant find link now to it but if it works then good i myself am in the process of charging my 7 before i can see if it will accept the update.pkg now cause i tryed without changing the img im on stock 2.2.2 4g tmobile one
Click to expand...
Click to collapse
Yup, I read that posty too and I tried several times with the 514 recovery with no success. I then tried with the 506 recovery, no other changes, and it worked. I would have preferred a 514 revocery from a warm-and-fuzzy standpoint but I don't really care now that it's done.

I'm stuck! Is a factory cable required?

I spent about 6 hours yesterday trying to root my Kindle Fire HD 7" tablet using various methods. I've searched numerous posts and tried several ways with no success.
I believe my ADB drivers are working properly because I am able to reboot the tablet from adb successfully. And in the Windows Device Manager it shows the "Android Composite ADB Interface" as my driver. But the command "adb reboot bootloader" just reboots back into the standard Home screen. And any fastboot command just gives me the "waiting for device" response.
I am on Version 7.4.8 of the firmware so I am trying to find a way to downgrade. I purchased it in November 2012 so it is the 2012 tablet. But every method I try just fails for one reason or another. So my question is, do I need a factory cable in order to get anywhere with this? Is it even doable with this version firmware?
Thank you in advance.

It is doable without a factory cable, the known rooting utilities people typically use are kindle fire first aid or binary's root. If you still can't get it to root, you can technically use a fastboot cable and kffa to restore it to a earlier is that os pre-rooted.
Sent from my Amazon Kindle Fire HD using Tapatalk

pastorbob62 said:
I spent about 6 hours yesterday trying to root my Kindle Fire HD 7" tablet using various methods. I've searched numerous posts and tried several ways with no success.
I believe my ADB drivers are working properly because I am able to reboot the tablet from adb successfully. And in the Windows Device Manager it shows the "Android Composite ADB Interface" as my driver. But the command "adb reboot bootloader" just reboots back into the standard Home screen. And any fastboot command just gives me the "waiting for device" response.
I am on Version 7.4.8 of the firmware so I am trying to find a way to downgrade. I purchased it in November 2012 so it is the 2012 tablet. But every method I try just fails for one reason or another. So my question is, do I need a factory cable in order to get anywhere with this? Is it even doable with this version firmware?
Thank you in advance.
Click to expand...
Click to collapse
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct. The fact you see it in your device manager is a pretty good sign though.
The command you are looking for is (must be rooted to use this command otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.

LinearEquation said:
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct. The fact you see it in your device manager is a pretty good sign though.
The command you are looking for is (must be rooted to use this command otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.
Click to expand...
Click to collapse
I appreciate your reply and information very much. However, I downloaded the SDK package and installed it over a year ago and have used Fastboot for three other devices numerous times. I used Fastboot with my Asus TF300T to flash recoveries, and return to Asus Stock on more occasions than I can count. I am currently running CROMBi-kk 20140323 on that same tablet. Just to be certain, I connected it just now as I am typing this and verified several Fastboot commands. I also have a Huawei U8800-51 and a Samsung S4 Mini Duo GT-I9192 and have used Fastboot commands with them as well.
So I don't think it is an issue with the driver not being installed correctly, or the SDK not being present unless it is a version specific issue. But the Samsung phone is much newer than the Kindle so I don't think it is that either.
So I guess that puts me at an impasse until I get a factory cable. Or I can just forget customizing the Kindle.

pastorbob62 said:
I appreciate your reply and information very much. However, I downloaded the SDK package and installed it over a year ago and have used Fastboot for three other devices numerous times. I used Fastboot with my Asus TF300T to flash recoveries, and return to Asus Stock on more occasions than I can count. I am currently running CROMBi-kk 20140323 on that same tablet. Just to be certain, I connected it just now as I am typing this and verified several Fastboot commands. I also have a Huawei U8800-51 and a Samsung S4 Mini Duo GT-I9192 and have used Fastboot commands with them as well.
So I don't think it is an issue with the driver not being installed correctly, or the SDK not being present unless it is a version specific issue. But the Samsung phone is much newer than the Kindle so I don't think it is that either.
So I guess that puts me at an impasse until I get a factory cable. Or I can just forget customizing the Kindle.
Click to expand...
Click to collapse
You said you were using simply adb reboot bootloader right? Did you try the command I suggested? "adb shell su -c reboot bootloader" because if everything is set up right then this should work. CD from the tools folder.

LinearEquation said:
You said you were using simply adb reboot bootloader right? Did you try the command I suggested? "adb shell su -c reboot bootloader" because if everything is set up right then this should work. CD from the tools folder.
Click to expand...
Click to collapse
Okay, got it working. Not sure what the problem was but I reinstalled SDK-Tools and Platform-Tools using the latest version of SDK. I was then able to use KFFA to root the Kindle and do a full backup. Not sure why it didn't work before the reinstall since I used ADB and Fastboot with my TF300T as recently as a week and a half ago while testing CROMBi-kk. Also verified they still worked with that tablet yesterday. Whatever the problem, it was specific to the Kindle.
One more question. Is it necessary to downgrade from 7.4.8 before installing a second bootloader and custom ROM? Or is that just a precautionary step because some people have had issues.

pastorbob62 said:
Okay, got it working. Not sure what the problem was but I reinstalled SDK-Tools and Platform-Tools using the latest version of SDK. I was then able to use KFFA to root the Kindle and do a full backup. Not sure why it didn't work before the reinstall since I used ADB and Fastboot with my TF300T as recently as a week and a half ago while testing CROMBi-kk. Also verified they still worked with that tablet yesterday. Whatever the problem, it was specific to the Kindle.
One more question. Is it necessary to downgrade from 7.4.8 before installing a second bootloader and custom ROM? Or is that just a precautionary step because some people have had issues.
Click to expand...
Click to collapse
Its kinda just a precautionary measure, to put it plainly, your kindle will bootloop into recovery if you do the process on 7.4.8, so unless you know how to use "Adb push" its suggested to put the rom and gapps onto the kindle ahead of time so it will be there when you start to bootloop into recovery. On another note, you do need to downgrade the bootloader though, if you use hashcodes method, please check the md5sum on the bootloader file before flashing it to avoid a hardbrick. If you used the fireflash method i wouldnt worry about it, just make sure you check off the downgrade bootloader button above or beside the red warning text.

I had these same issues. The device wouldn't boot into fastboot while it was <waiting for device>.
I did this.
1. Used Many Root Tool to gain root. http://forum.xda-developers.com/showthread.php?t=1886460
2. Placed the Rom and Gapps file on my sd card to be safe.
3. Used Anonymous.123's Tool up until the fastboot <waiting for device> malfunction. http://forum.xda-developers.com/showthread.php?t=2685414
4. Opened the Batch File for the Flasher Tool and copied and pasted the fastboot commands into a terminal with the Kindle in Fastboot. The only way I could get it in fastboot was "adb shell su -c reboot bootloader"
This will install the 4.2 bootloader so you don't have to flash back.
5. Profit 2nd Bootloader and TWRP
Good luck. You'll get it.
Sorry I Keep using the quote reply wrong. Havn't been on XDA in a while.

Okay, following Hashcode's procedure, I have successfully completed all steps up to flashing CM 10.2. TWRP works great and I made a backup from it. Not really necessary since I had backed up my Kindle three different ways and also copied all of my data to my PC as well.
But when I went to copy the TWRP backup to my PC for safekeeping I discovered that now I no longer have access to my Kindle from my PC's file explorer when I am booted into my Kindle. Prior to doing any of the steps here I could swap files back and forth without any problem. So how do I get that feature back??
I am running WIndows 8.1. This worked before I followed the procedures here. Also, when I pull files in adb where do they get stored??? Can't seem to find them.

Check the storage settings in CM you have to turn MTP storage in.
Sent from my Galaxy Nexus using xda app-developers app

[Q] Htc one M7 softbricked and can't connect to a computer

FYI: I am not tech savy at all so bare with me if I sound like a noob/idiot.
I basically formatted my phone from TWRP and I'm thinking there isn't any ROM/UI/kernel?..ect. so it cannot start up (basically stuck on the htc loading screen). My computer detects it but not as a storage device and I can't seem to find a way to access it. I believe I have what i need on my computer but my issue is that i dont know how to get into the internal storage of my htc one because it cannot detect it as a storage device on my computer.
The only trace of it at all i seem to be able to find is in
Control Panel\Hardware and Sound\Devices and Printers
Its called "android 1.0" and when i click on it, it takes me to its properties from device manager.
It says Location: Port_#0001.Hub_#0008
I dont know if any of this info i gave is relevant, if not, let me know what ups.

ray408 said:
FYI: I am not tech savy at all so bare with me if I sound like a noob/idiot.
I basically formatted my phone from TWRP and I'm thinking there isn't any ROM/UI/kernel?..ect. so it cannot start up (basically stuck on the htc loading screen). My computer detects it but not as a storage device and I can't seem to find a way to access it. I believe I have what i need on my computer but my issue is that i dont know how to get into the internal storage of my htc one because it cannot detect it as a storage device on my computer.
The only trace of it at all i seem to be able to find is in
Control Panel\Hardware and Sound\Devices and Printers
Its called "android 1.0" and when i click on it, it takes me to its properties from device manager.
It says Location: Port_#0001.Hub_#0008
I dont know if any of this info i gave is relevant, if not, let me know what ups.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2318497
Here is some reading material for you

Bro..I completely understand your predicament..
Just do this step by step
1. Download minimal adb from the internet and install it on your PC.
2. Download twrp image from the internet.this is a recovery loader.
3.copy the image file into the install directory of minimal adb.
4.execute the minimal adb shortcut from your PC.it should open a command prompt.
5.connect your device to the PC via usb.
6. Type this command to check if your device is recognized. "Fastboot devices"
It should show you a device ID..if your device is connected and recognized
7.flash tarp image with this command "fastboot flash recovery <twrp.img>"
8.reboot your device..press and hold volume down at the sametime to get into bootloader.
9.enter recovery.
10.Download any custom rom from htconeroot.com.it will be a zip file.
11. Copy the zip into minimal adb install directory and run this command to push the zip onto your device. "adb push <image file>.zip any name.zip"
12. After this completes you should be able to see this image in the filemanager in twrp.
13.move the zip file into sdcard directory.
14.make sure all options are checked in the mount in twrp
15.install the custom rom from install option in tarp.
This is 3 frantic days of research on the internet bro..
I had a brick in my hand too..got it up and running VIPERONE ROM
Hope you get through this fine

Thank you, i really appreciate the effort! but im stuck on step 6/7. When i typed in fastboot devices, it didn't show any new id. and when i typed fastboot flash recovery twrp.img it says "waiting on device" so im guessing it still didnt detect it. any idea on why this might be happening? thanks
gowda-the-grear said:
Bro..I completely understand your predicament..
Just do this step by step
1. Download minimal adb from the internet and install it on your PC.
2. Download twrp image from the internet.this is a recovery loader.
3.copy the image file into the install directory of minimal adb.
4.execute the minimal adb shortcut from your PC.it should open a command prompt.
5.connect your device to the PC via usb.
6. Type this command to check if your device is recognized. "Fastboot devices"
It should show you a device ID..if your device is connected and recognized
7.flash tarp image with this command "fastboot flash recovery <twrp.img>"
8.reboot your device..press and hold volume down at the sametime to get into bootloader.
9.enter recovery.
10.Download any custom rom from htconeroot.com.it will be a zip file.
11. Copy the zip into minimal adb install directory and run this command to push the zip onto your device. "adb push <image file>.zip any name.zip"
12. After this completes you should be able to see this image in the filemanager in twrp.
13.move the zip file into sdcard directory.
14.make sure all options are checked in the mount in twrp
15.install the custom rom from install option in tarp.
This is 3 frantic days of research on the internet bro..
I had a brick in my hand too..got it up and running VIPERONE ROM
Hope you get through this fine
Click to expand...
Click to collapse

ray408 said:
Thank you, i really appreciate the effort! but im stuck on step 6/7. When i typed in fastboot devices, it didn't show any new id. and when i typed fastboot flash recovery twrp.img it says "waiting on device" so im guessing it still didnt detect it. any idea on why this might be happening? thanks
Click to expand...
Click to collapse
Ok..try this..
Press down on the power and volume down button to enter the default boot loader.
If you hv rooted your phone..it should be showing tampered at the top.
select the fast boot option..
Now connect your phone via usb..
The display name should change to "fastboot usb"
Then again open minimal adb and continue from step 6.
Make sure you have all the htc drivers for Windows installed on your PC.
Windows can automatically download these drivers for you if you don't have them..
All the best

Are you using Windows 8.1?

everything works now, thank you guys. You are all awesome!

OnePlus3t bricked can only boot into fastboot, however my ADB driver no longer works

I have ran into a bit of an odd problem due to me messing up a root and then messing my phone up even more while trying to fix it.
my phone is fully bricked and only boots into fastboot mode. i tried to fix it with the one-plus fixer (idk its official name) but i got an error 7. I now need to re flash an older version of TWRP and try a diffrent method but i cant as my phone no longer is recognized in fastboot using the ADB tool. I have the USB driver installed on Windows. On Linux i ran the .sh script as root and it still doesn't work.
I have both Ubuntu and Windows installed on my PC so i can do whatever you suggest me to do regardless of the os.
Thank you to anyone that can help in advanced
Malte

This is not a hardbrick; a hard one wouldn't boot at all and give no sign of life (except when plugged to PC).
Try an unbrick tool to revert to official OOS. On Windows 7+ remember to disable signed driver enforcement.

You mention fastboot and adb. Which one are you using?
Just to make sure: While in the bootloader (fastboot mode), adb does not work. You have to use the fastboot commands. Installing TWRP would be:
Code:
fastboot flash recovery <name-of-img-file>
If that's what you're already trying, just ignore this post.

I want to be able to do that but if i do adb devices it no longer finds my phone
Didgeridoohan said:
You mention fastboot and adb. Which one are you using?
Just to make sure: While in the bootloader (fastboot mode), adb does not work. You have to use the fastboot commands. Installing TWRP would be:
Code:
fastboot flash recovery <name-of-img-file>
If that's what you're already trying, just ignore this post.
Click to expand...
Click to collapse
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command

Ive done this but it didnt fix my phone.
przemcio510 said:
This is not a hardbrick; a hard one wouldn't boot at all and give no sign of life (except when plugged to PC).
Try an unbrick tool to revert to official OOS. On Windows 7+ remember to disable signed driver enforcement.
Click to expand...
Click to collapse
I did this last night but it never fixed my phone. it boots and then says "md5 checksum error" so im needing to try a diffrent approach but i cant because i cant flash anything onto it due to adb not finding my device now

Bandella said:
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command
Click to expand...
Click to collapse
Like I said, the adb commands won't work while in the booloader (that's why it's called fastboot mode). You need to use fastboot commands... The equivalent command would be:
Code:
fastboot devices

Bandella said:
I did this last night but it never fixed my phone. it boots and then says "md5 checksum error" so im needing to try a diffrent approach but i cant because i cant flash anything onto it due to adb not finding my device now
Click to expand...
Click to collapse
I had the same issues with md5, all you have to do is try a different USB port. I suggest the ones on your motherboard if you're on a PC. Then run the tool as administrator. I hope this helps, good luck!
P.S if it still doesn't work, try a different PC, I'm 100% sure it'll work

Bandella said:
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command
Click to expand...
Click to collapse
As Didgeridoohan touched upon, adb and fastboot (while related) are different. They have different requirements and applications.
adb won't work while the device is in fastboot mode. Conversely, when the device is able to use adb, fastboot commands won't work.
adb: only works booted to OS or alternately in TWRP. Debugging must be enabled
fastboot: only works in bootloader-fastboot mode. Debugging is not required to be enabled.
For flashing TWRP, it's fastboot that you need. Well, there is a way to do it with adb, but fastboot is by far the more common way.
When in fastboot mode, adb command won't work, and there fore it is completely expected that "adb devices" yields not response. Try "fastboot devices" (no quotes) and if you get the phone's ID in response, you are in business.

Bandella said:
...
my phone ... only boots into fastboot mode...
Click to expand...
Click to collapse
I've had this happen to me when I've triggered dm-verity. Instead of getting the dm-verity warning display the phone would simply boot straight back to fastboot.
My solution was to:
- flash the latest TWRP using
Code:
fastboot flash recovery <recovery file. img>
- reboot into recovery (use the volume keys on the phone to select recovery and then press the power key)
-flash the full stock image I was using before the problem started
This would clean up any changes made to the boot and system images and allow me to boot the system normally.
Note: because this leaves you with a stock kernel you'll end up with the stock recovery after you boot the system.
Sent from my OnePlus3T using XDA Labs

boot your PC into Ubuntu and install adb/fastboot (tons of guides available off the 'net). then boot your 3t to dl mode and connect it to your PC. as mentioned already "fastboot devices" should list your 3t and you should now be able to flash to your heart's content. no need for drivers, unlike under Windows. i have a bootable linux usb drive primarily for this reason. curious what script you're trying to run though..