Database Develop

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.

[Q] ADB Sideload isn't working for me!

Hello there
I am stuck without a ROM and without a ROM zip file anywhere on the internal device that I can use TWRP to install. The only option I have at the moment is to use adb sideload, and this is my first time doing so.
I downloaded this:
adt-bundle-windows-x86_64-20130522
Anyway, I am trying to follow this tutorial but it's not working out for me:
http://forum.xda-developers.com/showthread.php?t=2317986
It looks simple and easy, but this is the problem I am facing:
"I changed directories to where the adb.exe is (inside platform-tools) and ADB Sideload is already started in TWRP. However, whenever I type "adb devices" it only says "List of attached devices" and nothing under it. Whenever I try flashing the ROM, it says error: device not found. What am I doing wrong here? I even changed the name of the ROM to rom.zip to make it shorter as per a suggestion in the first page of the thread, but that didn't work either."
Can someone please help me and tell me how to make it work? I have been without a ROM for hours waiting for the SDK to download this my internet is pretty slow. Thanks a lot!

Okay now I realize my device isn't actually recognized, although it works fine with fastboot usb.
What do I do? I tried having windows automatically search for drivers but it didn't find anything.

Okay after doing some more reading I realized I never actually opened SDK Manager, and when I try, it just opens a black command prompt window and then shuts down. I then came across this article and realized I need Java JDK drivers before I can actually run SDK Manager and then follow the rest of the tutorial. Maybe that is the problem??

You need HTC drivers , if you didn't install HTC SYNC, open "virtual CD", that appears at connection of phone with PC and you will see folders with drivers for different OS.

Thanks, mate. I already fixed the problem but I forgot to update this thread. You are right, I did not have the proper drivers, so I downloaded and installed HTC Sync Manager and then everything went great.

I had the same problem last night trying to flash my first rom ever, but thankfully i had a usb otg cable that I used to put the rom zip in my flash drive and flash it into the phone

TarekElsakka said:
Hello there
I am stuck without a ROM and without a ROM zip file anywhere on the internal device that I can use TWRP to install. The only option I have at the moment is to use adb sideload, and this is my first time doing so.
I downloaded this:
adt-bundle-windows-x86_64-20130522
Anyway, I am trying to follow this tutorial but it's not working out for me:
http://forum.xda-developers.com/showthread.php?t=2317986
It looks simple and easy, but this is the problem I am facing:
"I changed directories to where the adb.exe is (inside platform-tools) and ADB Sideload is already started in TWRP. However, whenever I type "adb devices" it only says "List of attached devices" and nothing under it. Whenever I try flashing the ROM, it says error: device not found. What am I doing wrong here? I even changed the name of the ROM to rom.zip to make it shorter as per a suggestion in the first page of the thread, but that didn't work either."
Can someone please help me and tell me how to make it work? I have been without a ROM for hours waiting for the SDK to download this my internet is pretty slow. Thanks a lot!
Click to expand...
Click to collapse
Just get the all in one tool, ins;tall the relevant drivers and then go to recovery and select sideload a rom, go to the all in one toolkit and select sideload a rom, then choose the rom, simples
Sent from my Transformer Prime TF201 using xda premium

Thanks, guys. I ordered an OTG USB cable this morning just to avoid any future problems.

Can you flash...

Hey all. I was reading about the stock Google edition RUU 4.4 that's posted here. However, the directions say to manually install via fastboot. I tried with TWRP instead because I am having trouble with the command prompt but when I try to install the RUU via twrp it immediately says failed. Is there a way to do it via twrp? Thank you all

Just follow the instructions. If there was an easier way it would have been posted.
Sent from my HTC O'ne-xus

Take a hint and don't do it.

I know it can be frustrated, but that's one of those things where you REALLY need fastboot setup and working before installing the Rom. If something weird happens where you're in a bootloop or something, you need access to working fastboot. If you can't get it working I'll help you get it figured out.
But tell us exactly what's not working and we can probably help.
One tip is if you're using Windows 7, open the command prompt by holding shift while right clicking in the blank white folder space where your fastboot.exe file is located on the computer.
Shift + Right Click will pop up a menu where you choose "Open Command Window Here"
That puts you right to the step of typing the command, because cd (change directory to path of fastboot file) isn't needed since you started in the correct folder.
When you run the command, like "fastboot devices" as a test, take a screenshot of the cmd window after you run it so we can see exactly what it's doing and advise from there.
If you're own Windows 8 you'll need to disable driver signing, which I find the steps for by googling "Windows 8 how to disable driver signing"
Also if there's USB 2.0 ports on your computer use them instead of 3.0. And the main USB port usually works best, such as on the back of a motherboard instead of the front case in a desktop tower.
Sent from my HTC One using Tapatalk

[Q] Unlocking Bootloader issue

I'm trying to install CyanogenMod, unless you can advise me a better ROM?
Doing so, I need to unlock my Bootloader, right? However, after I connect my Sony Xperia T with my laptop via USB-cable while holding the 'Volume up' button, and I attempt to type:
Code:
fastboot devices
into Command Prompt, command prompt says:
Code:
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
So I Google'd it and bumped into this thread.
I'm glad someone found a solution, however I'm stuck.
I unzipped the ADB drivers and tried to install the USB driver windows says:
Windows 8 said:
This program might not have installed correctly
SAMSUNG USB Driver for Mobile Phones.
SAMSUNG Electronics Co., Ltd.
If this program didn't install correctly, you can try installing the
program using compatibulity settings.
-> Install using compatibility settings
-> This program installed correctly
Click to expand...
Click to collapse
When I choose "-> Install using compatibility settings", nothing happens.
When I choose "-> This program installed correctly", well... Nothing happens...
What am I missing? Do I need a Sony equivalent?
Edit: After posting the thread, my PC started installing the SAMSUNG USB Driver for Mobile Phones software. However there is still no progress when i attempt to type in "fastboot device" in CMD...

Bounkass said:
I'm trying to install CyanogenMod, unless you can advise me a better ROM?
Doing so, I need to unlock my Bootloader, right? However, after I connect my Sony Xperia T with my laptop via USB-cable while holding the 'Volume up' button, and I attempt to type:
Code:
fastboot devices
into Command Prompt, command prompt says:
Code:
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Instead of doing it manually, since it doesn't seem to be your thing, why don't you use Flashtool and let it take care of everything for you.
If you want to do it manually, if you're not in the same folder with the fastboot executable then you'll get that error, either change directory into the folder where you have the fastboot executable or add said folder path to your Windows system environment variables.

Antiga Prime said:
Instead of doing it manually, since it doesn't seem to be your thing, why don't you use Flashtool and let it take care of everything for you.
If you want to do it manually, if you're not in the same folder with the fastboot executable then you'll get that error, either change directory into the folder where you have the fastboot executable or add said folder path to your Windows system environment variables.
Click to expand...
Click to collapse
Oh, I didn't know there was some tool that can do it for me. I just Google'd how to install CyanogenMod on my Xperia T, or something like that and their website said do this. So I did.
Say I would do it manually (I'm not, just asking out of curiosity), what do you mean by "if you're not in the same folder with the fastboot executable then you'll get that error". The folder was open everytime I did it? So I don't understand.
Edit: Next problem, I installed Sony Mobile Flasher by Androxyde, it doesn't recognize my phone so I have to install drivers. This thread instructs me to a certain folder withing the Flashtool directory to install the drivers needed (Xperia TX), however, once again, it's not working. This is what Device Driver Installation Wizard says:
Device Driver Installation Wizard said:
X Sony (WinUSB) sa0105AdbDeviceClass (03/07/2012 2.0.0010.30011) -- Install Failed
X Sony Net (02/29/2012 6.0.6000.16493) ------------------------------------------- Install Failed
Click to expand...
Click to collapse

Bounkass said:
Oh, I didn't know there was some tool that can do it for me. I just Google'd how to install CyanogenMod on my Xperia T, or something like that and their website said do this. So I did.
Say I would do it manually (I'm not, just asking out of curiosity), what do you mean by "if you're not in the same folder with the fastboot executable then you'll get that error". The folder was open everytime I did it? So I don't understand.
Edit: Next problem, I installed Sony Mobile Flasher by Androxyde, it doesn't recognize my phone so I have to install drivers. This thread instructs me to a certain folder withing the Flashtool directory to install the drivers needed (Xperia TX), however, once again, it's not working. This is what Device Driver Installation Wizard says:
Click to expand...
Click to collapse
What I mean is that when you type "fastboot" in the command prompt, it's actually looking for a program named "fastboot.exe/bat/cmd, etc.". If you would have been in the same folder you most likely wouldn't have gotten that error message.
Regarding drivers not installing, I'm assuming you're on Windows 8, and you're following a guide for a Samsung phone, which it seems it even directed you to install drivers for a Samsung phone in your first post.
First of all, you need to disable Windows Driver Signature Enforcement before it allows you to install the drivers. You have to do that first, then install drivers, then use Flashtool/or do it manually, by opening the command prompt and changing directories to the folder where the fastboot executable is.
Not trying to sound harsh, but if I were you I'd be a bit careful when following guides and/or dabbling with unlocking your phone, etc.; I think you should either read up very carefully before doing anything, ask questions, or leave it for later when you're a bit more knowledgeable on these types of things, because if you're having problems running a program from a command prompt or are even installing drivers for a different phone and expecting things to work smoothly, chances are you'll mess up while tinkering with your phone, especially considering you're following the CM guide and installing a CM ROM when chances are most people with custom Roms and a T would probably be using a different ROM found here on XDA, though I could be wrong.

Antiga Prime said:
What I mean is that when you type "fastboot" in the command prompt, it's actually looking for a program named "fastboot.exe/bat/cmd, etc.". If you would have been in the same folder you most likely wouldn't have gotten that error message.
Regarding drivers not installing, I'm assuming you're on Windows 8, and you're following a guide for a Samsung phone, which it seems it even directed you to install drivers for a Samsung phone in your first post.
First of all, you need to disable Windows Driver Signature Enforcement before it allows you to install the drivers. You have to do that first, then install drivers, then use Flashtool/or do it manually, by opening the command prompt and changing directories to the folder where the fastboot executable is.
Not trying to sound harsh, but if I were you I'd be a bit careful when following guides and/or dabbling with unlocking your phone, etc.; I think you should either read up very carefully before doing anything, ask questions, or leave it for later when you're a bit more knowledgeable on these types of things, because if you're having problems running a program from a command prompt or are even installing drivers for a different phone and expecting things to work smoothly, chances are you'll mess up while tinkering with your phone, especially considering you're following the CM guide and installing a CM ROM when chances are most people with custom Roms and a T would probably be using a different ROM found here on XDA, though I could be wrong.
Click to expand...
Click to collapse
Thanks for your reply.
I decided to re-install Windows 7. I was planning that anyway.
Now I'm going to start from scratch and see what happens.

ADB/Fastboot problems with Open Beta 5 (7.1.1)

I have had a very eventful few hours and I'll do my best to explain. Earlier this morning I was rooted, twrp installed and running FreedomOS. I had this bright idea of flashing a file I had downloaded from the OP3T website. It was a firmware file (either the first option, the option before OB5). Everything was running smoothly until I got home and tried using fastboot at which point it just sticks on waiting for device. All normal options are checked (adb files installed, debugging selected, the works), but now I can not use fastboot what so ever. I did at one point sideload an OTA using adb sideload (filename.zip). I have tried just about every adb option I can think of to include: 15 second ADB and minimal adb and fastboot. I even deleted the OP3T drivers from my computer, reinstalled those drivers. I followed an article through technobuzz: http://www.technobuzz.net/download-oneplus-3-usb-drivers/
http://www.technobuzz.net/setup-adb-fastboot-drivers-for-nexus-oneplus-samsung-or-any-android/
I have been using adb and fastboot with no issues up til Open Beta 5 and now my PC and another PC is giving me crap and it's iritating the %%%k out of me.
adb reboot recovery works, adb devices work - showing that the device is connected. I checked the device manager and only found the portable devices. It's like my computer somehow magically deleted the adb driver and will not allow me to install an adb driver. I have no logs to check out....15 second adb was suppose to place a log file on the desktop, but it doesnt....it wont install
Here's what Im on:
OB5 (7.1.1) with stock recovery. I can not use fastboot commands. Here are some pics
http://imgur.com/a/y7iFE
http://imgur.com/a/SVVMg You should see something that says, "Android Device or ADB", but nothing - just MTP
http://imgur.com/a/62msw
I'm using windows 10, device signature is off
Essentially I just want to be able to fastboot flash TWRP and gain root.
Has anyone else experienced any kind of issues with OB5 and adb/fastboot
Btw I had the entire Android SDK installed on another computer and that did not work either....Any assistance would be greatly appreciated. I'm talking about you @redpoint73, lol

Oh boy, I've been summoned! I have to say, I'm not anywhere near knowledgeable yet with the 3T as I was with my past devices. But I'll try.
I assume you are properly trying fastboot commands while in fastboot mode (not in OS or recovery)? I assume so, since you already said it worked fine before the update. But it never hurts to ask the obvious, as a lot of folks forget that adb and fastboot work a bit differently (fastboot only in fastboot mode, adb only in OS or recovery - debugging only needed for adb, not fastboot).
Do you have the OP3T drivers installed? These are the files that Windows always opens whenever I connect the phone (while booted into phone OS), select File Transfer, and it gives the option to open the folder. Although I don't think you even need the drivers for fastboot to work. I unlocked the bootloader and flashed TWRP before I ever installed the OnePlus drivers. The generic fastboot drivers worked fine. But it's worth a try, to install the OP drivers.

I don't even know where to begin or how to reply to what you just said @redpoint73. I haven't attempted to use adb/fastboot commands since yesterday, so i have no idea as to rather it will work or not. If you have teamviewer, I can give your access to a backdoor to show you as it's easier to show then explain. Have you ever noticed when you download a zip from here: http://downloads.oneplus.net/devices/oneplus-3t/#title-section
it never saves the file as Open Beta 3, 4, or etc. It saves the file as this long-named file.zip rather than being something easy to understand. Im able to understand it now, but a few moments ago I wasnt. I "have" downloaded the OP3T drivers on multiple occasions with no success to to fastboot only adb. My computer recognizes the device though. When I go into device manager checking things out. I will have an option that says, "portable devices". when you select that option you'll go across through some contextual menus where you wind up seeing MTP. You should see MTP if you successfully installed the OP3T devices, but at the same time you should be able to see an option that says something along the lines of ADB or Android Debug Bridge, vice versa. My computer does not say that and I have no idea where to go from here. I have no logs or anything helping me out, so it's like finding a needle in the haystack. I do know that I have all of the prereq's such as debugging selected from developers options within the phone, device signature turned off through Windows, adb/fastboot installed, OP3T drivers installed - you know the works you usually need in order to get everything working right. What I might end up doing is just reformatting my entire laptop, installing a fresh copy of windows, fresh copy of adb/fastboot and going from there. My bootloader is unlocked and has been since I've owned the device. As of right now I'm on OB5 with stock recovery. Yesterday I tried three times to sideload one of the downloads from this site: http://downloads.oneplus.net/devices/oneplus-3t/#title-section
. However, my phone would end up saying, "installation failed" when Im in sideload mode. I'm thinking that might have something to do with a botched download from the OP3T server.

Looks like you found your solution here: https://forum.xda-developers.com/showpost.php?p=72046709&postcount=20
Fastboot/adb is usually as simple as reinstalling drivers, etc. as opposed to reformat the PC as you were considering. Reinstalling adb/fastboot was a good idea also, as I don't think I would have thought of that (although it makes perfect sense). So good job working it out!