Develop Bugs

Anyone from N.Ireland offer rooting service

I've noticed a few posters on here are from N.Ireland and was wondering if any of you would root my phone? For a fee of course?
I'm a complete noob at this, I've spent the last four days reading guides and I just can't get it to work. Can get the tinycore linux working on my macbook but can never get past entering this in the terminal:
sudo mkdir /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom
cd /mnt/cdrom/desire After I press return here I get an error.
So I've now thrown in the towel and was hoping a local Android geek could help me out lol
Cheers
Joe

Are you using the TinyCore Live-CD from the MoDaCo guide or the r4 one posted by craigcrawford? the latter had an edited TinyCore build made which was slightly different to the normal one originally posted...
Have a read of this guide, by craigcrawford, never fails to work (so long as you download the right Live-CD - check your HBOOT and download accordingly):
http://android.modaco.com/content/h...sire-easy-rooting-guide-with-tiny-core-linux/

Thanks for the reply, yeah thats the one I'm using. Could it be my tinycore setup? I can't get it to boot from CD so setup a virtual machine on my macbook and ran tinycore through that.
Sorry if that doesn't make sense, I'm a complete noob at all this

Not being an Apple man I don't know if you can boot a Live-CD using a Mac but shouldn't see why not!
Also don't see why a VM wouldn't work but again I've always used a PC and it boots fine so might wanna see if you can borrow a Windows laptop and use that (or, if you're ever in Liverpool, come see me and I'll do it)

Ok going to try it again, I had already installed Linux VM before I downloaded the r4 and didn't know there was Tinycore ISO included with it.
So I've setup a new VM with the ISO from craigcrawford and I'm going to try it one last time. Just want to check something before I start, my phone is unbranded so I'm not using a goldcard do I need to put the rootedupdate.zip on the SD card before i start?

joe_998 said:
Ok going to try it again, I had already installed Linux VM before I downloaded the r4 and didn't know there was Tinycore ISO included with it.
So I've setup a new VM with the ISO from craigcrawford and I'm going to try it one last time. Just want to check something before I start, my phone is unbranded so I'm not using a goldcard do I need to put the rootedupdate.zip on the SD card before i start?
Click to expand...
Click to collapse
Correct, no Goldcard required. Should take about 10 mins all in (did for me on a W7 x4 Ultimate-based machine). Good luck!!

Cheers Eddy, here goes! I'll post how it goes!

Ok getting a bit further into it. Says rebooting into bootloader... FAILED
but then says Step 1 complete and gives instructions on how to continue.
I'm confused
Uploaded with ImageShack.us

Forgot to add, my phone didn't do reboot nor did the screen change at all

Yeah thats not working correctly...something's not right, be it running through a VM or otherwise...
I'd say it might be worth asking advice on (or taking a look at) the rooting guide on MoDaCo as more people there can help (and it works from within a Mac natively)
http://android.modaco.com/content/h...e-now-with-hboot-0-80-and-os-to-1-21-support/

Ok Eddy thanks for your help mate.
Going to phone round a few repair shops in belfast and see if they can do it! It's really started to p*ss me off now!

Would they want to do it, though? I doubt they'd want to potentially brick your phone and have to buy you a new one
What HBOOT are you running on btw?

Well I know of one shop that jailbroke a friends iphone so I'm going to try them to see if they'll give it a go!
I'm running HBOOT 0.80

Right, here's a little guide for a Mac:
- First, download THIS and extract it on to the Mac equivalent of the Desktop
- Copy the 'update.zip' to your SD card - do NOT rename it
- Now open a Terminal window (go to Applications>Utilities, double click 'Terminal' icon) and change directory to the extracted folder. Turn your phone on holding down the back button and you should be in the FASTBOOT screen. Plug your phone into the Mac and it should then read FASTBOOT USB
- In the terminal window type './step1-mac.sh' (without ') and when it finishes it will take you back to the FASTBOOT screen. Press the power button and it will change from FASTBOOT to HBOOT USB
- Select 'Recovery' and when at the screen with the red ! hold vol up and press the power key.
- Select 'wipe data/factory reset' and once complete select 'apply:update.zip' and once this is done reboot the device and you should be rooted

"Now open a Terminal window and cd to the extracted folder"
Eddy I haven't a clue how to open a terminal window and cd to the extracted folder, thats why I was trying the Tinycore guide.
Sorry for being such a noob

*Updated guide above
Don't know what else to put as I'm a Windows man, never used a Mac

Ok think I understand that. Just waiting on the r6 to finish downloading then I'm going to have another crack at it!
Thanks for putting that together Eddy, much appreciated.

Joe, if you are still stuck I should be able to help you out tomorrow free of charge. I think your bootloader is the same version as mine (can't remember off hand) so I still have the files on my netbook to do it, or at least should have.

Still can't get it to work.
Kerso, I'll take you up on that mate, Where abouts are you?
Eddy, thanks very much for your help mate

I am a Mac user but rooting is loads easier on a Windows machine, had mine rooted in no time using a XP based PC.
To open a Terminal window, just click on the magnifying glass search icon type in Terminal and it will appear in the list of matches, just double click it.
CD = change directory in the terminal, that's all. ie CD to the directory where you downloaded the folder it to.
Trouble I had was that OSX was unzipping the downloaded file on completion, I'm not sure how to stop it doing that.

[GUIDE] [HOW-TO] Root Your Droid Incredible 2 VIA HTC Bootloader Unlock

My other thread got screwed up. So, I just thought it would be easier to re-write it all over.
Some warnings:
-This is not a FULL unlock (S-OFF or to unlock your SIM card slot.)
-This WILL VOID your warranty.
-This will work with ANY version of HBOOT. Unless something has changed and I never update.........
-This is a how to for WINDOWS ONLY. Sorry Mac, Linux, and Unix. If someone knows how to do it VIA those ways, I'll add it in here.
-If you are logged out of HTC Dev at any time during the identifier period (1 - 5), just sign back in and don't click anything. It will automatically redirect you to the last page you were on.
-I am not responsible if you didn't follow a step correctly and your phone lights on fire, cracks into two, wants to destroy you, etc...
If you like to learn visually (like me) and would rather not go through my jumble of steps, check out this YouTube video. [link]
What you are going to need:
-A computer
-Fastboot and ADB [API] - [link] <-- These are applications I use to flash ROM's. They are in a .zip from me.
-HTC Drivers - [link] <-- Drivers HTC gives, couldn't find them on HTC's site.
-Android SDK - [link]
-microUSB cable, phone, and some time
STEPS TO ROOT: finally...
1.) You are going to want to head over to the HTC Dev[eloper] site ([link]) and make an account or sign in. Once you have done one of the two, you are going to want to click 'Unlock Bootloader,' then 'Get Started.' It will next ask you what device you are trying to unlock, click 'Droid Incredible 2 (Verizon)' then 'Begin Unlock Bootloader.' Then a pop up window will ask you if you are sure, just click 'Yes.' Then, another pop up window will appear, just tick the two boxes and press 'Proceed to Unlock Instructions.'
2.) Go to your phone. Take off the [back] battery door and remove the battery (don't hold the power button and make it a proper shut off, just rip the battery out. Then, put the battery back in. Once you have replaced the battery, hold the volume down button and the power button at the same time until a white screen shows up. You can use the volume rocker to highlight your selection, and the power button to select the highlighted selection. Right now, we want to highlight 'BOOTLOADER' and use the power button to select it. Next, grab your miniUSB cable and plug it into your computer to your phone.
3.) Next, make a folder on your computer in the C:\ Drive. In Windows Vista & 7, you can just go to Computer from the Start Menu and it will be labeled Local Disk (C:\). You can name the folder whatever you want, I am just going to name it Android. Next, you are going to want to download my ADB, Fastboot, and ADBAPI .zip file and place all three files into the Android folder. After you unzip the ADB/Fastboot folder, you are going to want to (if you have not already) download and install the Android SDK manager. You will need to install SDK tools [and I believe a version of Android?] After you have installed everything, you can go to the Start Menu again and type in 'cmd' in the search bar and press enter. Then type in the following: (Or you could take the easy way of going to your C:\ drive and shift-clicking the folder and press 'Open Command Window Here...)
Code:
cd C:\Android
4.) After you have got into Command Prompt and are in the \Android folder, type in the following:
Code:
fastboot oem get_identifier_token
You will then see a great big brick of random characters. Right click in the bottom right-hand corner of '<<<<< Identifier Token End >>>>>' and click 'Mark...' Hold down the left-mouse-button and select the great brick of text up until '<<<< Identifier Token Start >>>>' (don't highlight any of the 'INFO' things.) Then, right-click again and you will have the identifier token copied to your clipboard. Back on the HTC Dev site, it will ask you for your identifier; just paste the identifier in the box and it will send you an email with a .bin file (Unlock_code.bin) and just throw that into the folder with ADB and Fastboot.
5.) You are going to want to click the continue link that HTC Dev sent you as well to downloading the file. After you have finished downloading and put it in the folder, type in the following:
Code:
fastboot flash unlocktoken Unlock_code.bin
Once you have done that and pressed Enter, your phone will change screens. It will ask you if you are SURE you want to do this. Just press the volume rocker up and press the power button. Your phone will reboot and take you back to Android. It's normal and it doesn't mean it failed... Your phone is fine and it should have went OK if you followed the steps. We are done with HTC Dev now, so you can close it.
6.) Next thing we are going to want to do is flash ClockWorkMod (CWM) Recovery onto your phone. You are going to want to download the .iso for CWMR and flash it to your phone (download link [link].) After you are done downloading the .iso, place it into your ADB and Fastboot folder. Once your phone has finished starting up, take the battery out again and put it back into HBOOT mode (step 2.) You are going to want to go back into FASTBOOT (step 2, again) and flash the recovery by doing the following:
Code:
fastboot flash recovery recovery(press TAB)
Once you press enter and fastboot says it has completed, it will just have the Fastboot screen. Just highlight 'Bootloader' and press the power button. Next, to make sure it worked... Scroll down to 'Recovery' (which is right under Fastboot) and select it. The HTC screen should show and then CWMR should come to life.
7.) This is where the real magic happens. We are going to install SuperUser on to your phone now. Reboot your phone into regular Android. Now, you can plug it into the computer and make it a disk drive or pop out the miniSD card and put it into a converter. Now, you are going to want to download SuperUser ([link] - make sure your scroll down to the .zip dowload) and put it onto the miniSD (I recommend not putting it in any folders so it is easy to find.) Now, put your phone back into CWMR (step 6.) Now, use the volume rocker to scroll down to 'install .zip from sd card' and press the power button. Now, find the SuperUser.zip (or whatever it is named) and press the power button. The 'yes' to install it is in the middle of all the 'no' options, use the volume rocker to select 'yes' and press the power button. Wait for CWMR to finish, and in the meantime... Just stare at your phone. After you have finished installing SuperUser, restart your handset into Android. Once it has finished restarting, go into the app drawer and find the SuperUser app. Press the 'menu' button and tap 'Settings.' Scroll down to 'Su Binary x.x.xx' and tap it. On the bottom it will say 'Update Binary,' just tap that and it will do its 'magic.' Once SU has finished updating Binary, you have a rooted DINC2.
If you need any help, please let me know here, or on Twatter (@Rumor0922)

Updated post. Finished the guide. Hope you guys enjoy.

thanks for your guide - I'm needing to get something fresh on my wife's DI2...and I'm not as savvy with the HTCs as I am with my GNex.
The problem I have initially run into is the JDK - I have it installed....but whenever I try to install the Android SDK, the installer tells me that it does not recognize an installed JDK...
Also, I did notice that your Fastbook & ADB link is not active - is it obsolete now?
Thanks again, hopefully I can get this puppy running smoothly soon

jegawhat said:
thanks for your guide - I'm needing to get something fresh on my wife's DI2...and I'm not as savvy with the HTCs as I am with my GNex.
The problem I have initially run into is the JDK - I have it installed....but whenever I try to install the Android SDK, the installer tells me that it does not recognize an installed JDK...
Also, I did notice that your Fastbook & ADB link is not active - is it obsolete now?
Thanks again, hopefully I can get this puppy running smoothly soon
Click to expand...
Click to collapse
Android SDK includes fastboot and adb, so it isn't necessary. Are you sure you have the JDK installed? What version? I know OpenJDK was giving me trouble so I had to switch to the official JDK.
Sent from my Transformer Pad TF300T using Tapatalk 2

prototype7 said:
Android SDK includes fastboot and adb, so it isn't necessary. Are you sure you have the JDK installed? What version? I know OpenJDK was giving me trouble so I had to switch to the official JDK.
Sent from my Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Yep, just tried to reinstall 7u7 from the oracle site....no dice with SDK. Weird. I'll try with another PC to see if my laptop just licks

I added the ADB and Fastboot link, I thought it was already added... So, that is my fault. And like prototype said, Android SDK also includes ADB and Fastboot. Hope the best to your wife and the phone.

getting error!
EVoorhees said:
I added the ADB and Fastboot link, I thought it was already added... So, that is my fault. And like prototype said, Android SDK also includes ADB and Fastb7Aoot. Hope the best to your wife and the phone.
Click to expand...
Click to collapse
Hey guys im trying to root this phone with your instructions so I can use it for straight talk. Any who this error is popping up in cmd
<bootloader> [err] comand error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
any help would be great and much appreciated!

how to de odex a rom
is there an easy way
thanks.

casseer15 said:
how to de odex a rom
is there an easy way
thanks.
Click to expand...
Click to collapse
www.google.com
Sent from my Incredible 2 using Tapatalk 2

Take it to the house said:
Hey guys im trying to root this phone with your instructions so I can use it for straight talk. Any who this error is popping up in cmd
<bootloader> [err] comand error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
any help would be great and much appreciated!
Click to expand...
Click to collapse
This isn't for a SIM CARD tray unlock. It's just to root you phone and get ROMS and SU apps on it. Look around for a SIM unlock.
Sent from my HTC Incredible 2 using xda premium

6.) Next thing we are going to want to do is flash ClockWorkMod (CWM) Recovery onto yoour phone. You are going to want to download the .iso for CWMR and flash it to your phone (download link [link].) After you are done downloading the .iso place it into your ADB and Fastboot folder. Once your phone has finished starting up, take the battery out again and put it back into HBOOT mode (step 2.) You are going to want to go back into FASTBOOT (step 2, again) and flash the recovery by doing
Click to expand...
Click to collapse
the following:
In my download folder this shows up as an image file, is this right?
Does this mean that C: Android folder I created in the beginning of the guide? If not, where am I supposed to place it?
Does flashing it to my phone mean simply copy/pasting this cwm image file into the adb and fastboot folder?
Sorry guys I've been lurking for weeks. Successfully rooted my galaxy nexus and that was a breeze compared to this!

JimHTP said:
the following:
1.) In my download folder this shows up as an image file, is this right?
2.) Does this mean that C: Android folder I created in the beginning of the guide? If not, where am I supposed to place it?
3.) Does flashing it to my phone mean simply copy/pasting this cwm image file into the adb and fastboot folder?
Sorry guys I've been lurking for weeks. Successfully rooted my galaxy nexus and that was a breeze compared to this!
Click to expand...
Click to collapse
1.) Yes, an .iso file is a disk image.
2.) I personally like to place it in the C:\ Drive, but people put it where ever they want to.
3.) Yes, just put that in the folder with Fastboot and ADB[API.]

Please fadtboot install as administrator in pc?
Sent from my E15a using xda premium

It shouldn't have to install. You have to use Fastboot VIA Command Prompt.
Sent from my Incredible 2 using xda premium

Ok i try thanks
Sent from my E15a using xda premium

Here this message its in spanish sorry
Sent from my E15a using xda premium

kdrumwork said:
Here this message its in spanish sorry
Click to expand...
Click to collapse
English equivalent: "fastboot" is not recognized as an internal or external command, operable program or batch file.
That's happening since you're still in the Administrator's directory - C:\Documents and Settings\Administrador\.
You need to use the "cd" command to change to the directory where you downloaded fastboot. Then you'll be able to use that command.

Ok thanks i try this bro :thumbup:
Sent from my E15a using xda premium

anyone have any trouble with the new twrp 2.3.1.0 on here?

The Dropbox link for the drivers is empty. Can you put a new one up?

[GUIDE] [T-Mobile] Unlock Bootloader, Install Custom Recovery, Root, S-Off

This guide is for the T-Mobile HTC One M8. Bootloader Version: 3.16.0.0000
Disclaimer: I am not responsible for your device. You are performing the steps detailed in this post at your own risk. Support for any phone unlocked through this method falls upon you. Assume that this method voids any warranty that may have come with your phone. Also, currently there is no known way to restore the T-Mobile variant to complete stock settings after using HTC Dev Unlock and/or achieving S-Off. Maybe at a later date this could be possible, but not yet.
*Please do not quote this post. It's so long.*
Support for recoveries, firewater, or other tools used herein should be asked in their respective thread or forum.
Firewater does not work on every T-Mobile M8. If, when running firewater, you see "Whelp, this sucks..." firewater will not work on your phone. Right now firewater is the only method to achieve S-Off on our M8 variant.
There was speculation that the phone's build date might be a reference for who's phone was compatible with firewater. This is not the case. There is no correlation between build date and compatibility. A further explanation is given under the S-Off instructions.
This thread is for people that understand what this whole post means. If you are unsure of the terms, please search. The terminology is readily available and nothing should be difficult to find.
I work and go to graduate school, so this thread will be updated periodically, but I will not be able to provide a lot of support. This guide reflects my steps to achieve root and S-Off, and is just intended to give someone new to the phone an easy to read step-by-step guide of what the process will be.
I also hope we can condense the large amount of information floating around about achieving S-Off on our variant into one thread.
Required Files:
HTC Dev Unlock Process:
Google Android SDK zip:
http://developer.android.com/sdk/index.html
Java Runtime Environment:
http://java.com
HTC Sync (Windows Only):
http://www.htc.com/www/help/
Recovery (choose one):
Team Win Recovery Project (TWRP) 2.7.x for GSM Phones
http://teamw.in/project/twrp2/225
PhilZ Touch ClockworkMod (CWM) Recovery
http://forum.xda-developers.com/showthread.php?t=2703223
S-Off:
Firewater
http://firewater-soff.com/instructions/
Firewater M8 Original Thread
http://forum.xda-developers.com/showthread.php?p=51698035
Useful Commands:
adb devices
(after installing adb, this will tell you if your phone is detected by the computer)
expected output:
Code:
C:\sdk\platform-tools>adb devices
List of devices attached
FAXXXXXXXXXXdevice
fastboot devices
(after copying the fastboot utility downloaded during the HTC Dev Unlock process to your sdk\platform-tools\ directory, this will tell you if your phone is detected by the computer)
expected output:
Code:
C:\sdk\platform-tools>fastboot devices
List of devices attached
FAXXXXXXXXXXfastboot
1. Unlock bootloader via HTC Dev Unlock (http://www.htcdev.com/bootloader)
a. At the top of the page, either register for a new account or log in with an existing one
b. Under "Supported Devices" choose "All Other Supported Models"
c. Click "Begin Unlock Bootloader"
d. A prompt will ask you to continue. Read this. If this prompt scares you, stop immediately. Otherwise, press "Yes" to continue
e. Accept the legal terms and conditions.
f. Follow the on-screen steps provided.
Step 1
After powering down, press Volume Down and while pressing Volume Down, press Power holding both buttons to start the device into Bootloader mode. If you have difficulty, power up normally, go to Settings->Battery and deselect Fast boot. Power down and try again.
Step 2
Use the Volume buttons to select up or down. Highlight Fastboot and press the Power button.
Step 3
Connect the device to the computer via a usb cable
Step 4
Download the fastboot binary for your OS using the provided links​g. Follow the on-screen steps provided
Step 5
Open a command Prompt: Windows: Start->"cmd" Mac: Applications->Utilities->Terminal.app Linux: Terminal
Type in Command Prompt: fastboot oem get_identifier_token.
Step 6
You will see a long block of text. Copy and paste this text into the the token field below (in the Windows command prompt: Right Click > Mark > highlight the block of text > Right click to copy. Mac users can use cmd-option to mark and select text.).
When copying the token, start with this line:
>
And end with this line:
>
(Note: Do not copy the INFO or (bootloader) prefix)
Step 7
Paste this string of text into the token field and hit Submit in order to receive your unlock code binary file. You will receive this information in your email.​h. After hitting submit, HTC will send you an email. Sender is HTC-Unlockbootloader. Subject is "The key to unlocking your HTC Device."
Email Message:
Hi Recipient
Attached in this mail is your unlock bootloader key file. To use this file to unlock your device, simply follow the remaining instructions on the website to complete the process and successfully unlock your bootloader.
Please remember that unlocking your bootloader may void all or parts of your warranty and your device may not function as intended by HTC. Unlocking the bootloader is for development purposes only.
* Click here to continue the bootloader unlocking process.
The bootloader unlock key file can only be applied to the device with which you generated the token.
Please do not reply to this email which is auto-sent by server.
If you need to contact us with questions please click here.
Sincerly,
HTC
Click to expand...
Click to collapse
Attached to the email is Unlock_code.bin. This is the file you will need to download in order to unlock your bootloader. This file is device specific. You cannot use this file to unlock any other HTC phone. Please do not try as this will probably result in a brick.
Click the link provided in the email to continue the steps to unlock your bootloader​i. Follow the on-screen steps provided
Step 8
You will receive an email with the attachment: Unlock_code.bin. Save this file in the same folder as your fastboot files (For Example: C:\Android).
If, after a short period of time, you have not yet received the mail, or you have received an email from HTC, but does not contain an attached file, it is possible that more stringent spam filters and anti-virus programs will block this mail or attachment.
In order to ensure that you receive the email with the attachment, we suggest you consider using a non-corporate email server as corporate servers tend to have more stringent attachment policies. If you have not received the email at all, please check your spam folder in your email client to check if the email was filtered out.
Step 9
In the command prompt type: fastboot flash unlocktoken Unlock_code.bin. In the command prompt you will see the following message:
Code:
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' ...
OKAY [ 0.151s]
writing 'unlocktoken'...
unlock token check successfully
OKAY [0.006s]
finished. total time: 0.158s
Step 10
On your phone you will now see the disclaimer. Please read this carefully as this action may void your warranty. Use the Volume buttons to highlight your choice, and the Power button to make your selection. If you select Yes, your phone will be reset to its’ factory default settings, and your bootloader will be unlocked. If you select No, your phone will reboot and no modifications will have been made.
Step 11
To re-lock your bootloader, in the command prompt, type: fastboot oem lock.
Note: This will not restore the factory default lock, but will simply re-lock the bootloader so no further changes can be made. Furthermore, if you want to unlock your bootloader again, simply repeat step 9 with your original unlock key file to unlock your phone again.​j. Congratulations, your phone now has an unlocked bootloader! If your phone hasn't done so already, reboot it and let it sit at the welcome screen for the requisite 5-10 minutes to settle. Turn off your phone, and reboot to HBOOT with volume down + power button. Select fastboot.​
​
2. Install a custom recovery
As far as I know, there are two recoveries that are fully functional with our M8 variant:
TWRP
PhilZ Touch CWM​a. Download your chosen recovery from the above links.
b. Rename it recovery.img
c. Drop it in the same folder as your adb and fastboot binaries.
d. After booting to fastboot mode, make sure your device is still plugged in and run the following command in your command window:
fastboot devices
Your computer shouldn't have any troubles recognizing your phone since we just went through the bootloader unlock, but it's always best to be safe.​e. Now run the command:
fastboot flash recovery recovery.img
Expected output:
Code:
C:\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' ...
OKAY [ 0.871s]
writing 'recovery'...
OKAY [ 1.501s]
finished. total time: 2.543s
f. Congratulations! You now have a custom recovery installed.
g. I recommend immediately making a backup of your fresh operating system (pre-root) by selecting HBOOT from the fastboot menu, then selecting and booting into recovery
h. After booting into your new custom recovery select backup from your list of options and proceed to select your backup location (internal or micro sd) and continue to the backup. It will be quite large, but this will provide you a good starting point should you ever need to restore to factory settings for any reason.
i. I use TWRP, because it will automatically prompt you to install root and SuperSU upon rebooting from recovery.
I am unsure how to achieve root after flashing PhilZ Touch. If anyone provides the info I will add it to this guide.​
​
3. Achieve S-Off (Hopefully!)
The instructions to attaining S-Off are listed on the firewater s-off page linked above. They are really comprehensive and you should follow them to the letter. Make sure that you read through their prerequisites as well.
Note: On prerequisite number four, it states that you must be "HTCDEV unlocked/rooted." Please read this as you must be HTCDEV unlocked AND rooted.​
I didn't want to post the firewater team's instructions here (I didn't ask permission yet), so this section will be more for information regarding the S-Off process that I have gathered from other threads and this one going forward.
Issues seen with Firewater:
Firewater does not work on every T-Mobile M8. If, when running firewater, you see "Whelp, this sucks..." firewater will not work on your phone.
There was speculation that the build date was an indicator of compatibility with firewater's S-Off method. As several people expected, there is no correlation. There are batches of components that HTC purchased from various manufacturers that vary in compatibility with the firewater exploit. At this point there is no known method to determine if your phone will be compatible with firewater. Unfortunately, it's just a shot in the dark. So, if you're comfortable, give it a shot and hopefully you're compatible.
Issue: Firewater hangs but does not give the "Whelp this sucks..." message:
Possible Solutions: Your device is likely compatible. You must be persistent. Keep trying.
Hit Ctrl+C to exit the exploit and try again starting from "adb reboot" (from @Fenny)
Unplug your USB cable, reboot your phone manually. Once it boots up, plug in your USB cable (from @epsix)
Plug in your USB cable, adb reboot. Once it boots, go to Developer Options and uncheck and recheck USB Debugging (from @epsix)
Install BusyBox (from @renn9420)​Issue: After running adb reboot command and pushing firewater phone shows up as "offline"
Possible Solutions: Make sure that you granted su permissions to your adb shell through SuperSU
I had this happen to me. I would go to run the command and suddenly, the phone is disconnected. I ran through the adb reboot steps a couple of times and finally when executing firewater it ran. Went through the steps 3 times before it ran.​
​
4: Other
a. @Fenny noticed that /data/preload/ gets emptied after HTC Dev Unlock. If you're hanging onto your stock ROM and don't plan to change to a custom OS you'll want to replace these files. Go here to replace them: http://forum.xda-developers.com/showthread.php?t=2714522​
Thanks go to:
@beaups - firewater
@Dees_Troy - TWRP
@Phil3759 - PhilZ Touch
@Fenny - Stock + ROM, Hacked HBOOT, Preload data & more
@Turge - ViperOneM8
@Chainfire - SuperSU
@jcase - for looking into getting weaksauce working on our phones

FYI I didn't develop firewater, just weaksauce. That is @beaups baby
Sent from my HTC One_M8 using XDA Premium 4 mobile app

jcase said:
FYI I didn't develop firewater, just weaksauce. That is @beaups baby
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the info! Changed in OP.

Your posting title is slightly misleading since a good portion of T-mobiles m8s are not compatible with firewater.

Where do you find the build date
Sent from my HTC One_M8 using XDA Premium 4 mobile app

fryingpan0613 said:
Where do you find the build date
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's on the bottom edge of the box on the same sticker as IMEI.
Sent from my HTC One M8
egcthree said:
Your posting title is slightly misleading since a good portion of T-mobiles m8s are not compatible with firewater.
Click to expand...
Click to collapse
Updated OP to show that firewater may not work without having to show the contents of the S-Off info. Thanks for the comment.

I get the whelp yada yada and my build date is 4/10/14 do I need to have busy box installed?
Sent from my HTC One M8

OctoberNexus said:
I get the whelp yada yada and my build date is 4/10/14 do I need to have busy box installed?
Sent from my HTC One M8
Click to expand...
Click to collapse
Nope. That means that firewater won't work for you and S-Off isn't yet achievable for your phone.
OP updated with your build date.
Sent from my HTC One M8

Hopefully there will be another way in the future until then running GPE ROM which is a lot better than nothing still not what I had in mind when purchasing this thing.
Sent from my HTC One M8

Glad someone condensed everything down into an instructional guide. This should be stickied (if it's not already).
Thanks bro! :good::good:

thanks for writing this up!! got the dang Whelp message tho build date of 04/05/2014 if you want to add that to the list

VolcanicSkunk said:
This guide is for the T-Mobile HTC One M8. Bootloader Version: 3.16.0.0000
Disclaimer: I am not responsible for your device. You are performing the steps detailed in this post at your own risk. Support for any phone unlocked through this method falls upon you. Assume that this method voids any warranty that may have come with your phone. Also, currently there is no known way to restore the T-Mobile variant to complete stock settings after using HTC Dev Unlock and/or achieving S-Off. Maybe at a later date this could be possible, but not yet.
*Please do not quote this post. It's so long.*
Support for recoveries, firewater, or other tools used herein should be asked in their respective thread or forum.
Firewater does not work on every T-Mobile M8. If, when running firewater, you see "Whelp, this sucks..." firewater will not work on your phone. Right now firewater is the only method to achieve S-Off on our M8 variant.
This thread is for people that understand what this whole post means. If you are unsure of the terms, please search. The terminology is readily available and nothing should be difficult to find.
I work and go to graduate school, so this thread will be updated periodically, but I will not be able to provide a lot of support. This guide reflects my steps to achieve root and S-Off, and is just intended to give someone new to the phone an easy to read step-by-step guide of what the process will be.
I also hope we can condense the large amount of information floating around about achieving S-Off on our variant into one thread.
Required Files:
HTC Dev Unlock Process:
Google Android SDK zip:
http://developer.android.com/sdk/index.html
Java Runtime Environment:
http://java.com
HTC Sync (Windows Only):
http://www.htc.com/www/help/
Recovery (choose one):
Team Win Recovery Project (TWRP) 2.7.x for GSM Phones
http://teamw.in/project/twrp2/225
PhilZ Touch ClockworkMod (CWM) Recovery
http://forum.xda-developers.com/showthread.php?t=2703223
S-Off:
Firewater
http://firewater-soff.com/instructions/
Firewater M8 Original Thread
http://forum.xda-developers.com/showthread.php?p=51698035
Useful Commands:
adb devices
(after installing adb, this will tell you if your phone is detected by the computer)
expected output:
Code:
C:\sdk\platform-tools>adb devices
List of devices attached
FAXXXXXXXXXX device
fastboot devices
(after copying the fastboot utility downloaded during the HTC Dev Unlock process to your sdk\platform-tools\ directory, this will tell you if your phone is detected by the computer)
expected output:
Code:
C:\sdk\platform-tools>fastboot devices
List of devices attached
FAXXXXXXXXXX fastboot
1. Unlock bootloader via HTC Dev Unlock (http://www.htcdev.com/bootloader)
a. At the top of the page, either register for a new account or log in with an existing one
b. Under "Supported Devices" choose "All Other Supported Models"
c. Click "Begin Unlock Bootloader"
d. A prompt will ask you to continue. Read this. If this prompt scares you, stop immediately. Otherwise, press "Yes" to continue
e. Accept the legal terms and conditions.
f. Follow the on-screen steps provided.
Step 1
After powering down, press Volume Down and while pressing Volume Down, press Power holding both buttons to start the device into Bootloader mode. If you have difficulty, power up normally, go to Settings->Battery and deselect Fast boot. Power down and try again.
Step 2
Use the Volume buttons to select up or down. Highlight Fastboot and press the Power button.
Step 3
Connect the device to the computer via a usb cable
Step 4
Download the fastboot binary for your OS using the provided links​ g. Follow the on-screen steps provided
Step 5
Open a command Prompt: Windows: Start->"cmd" Mac: Applications->Utilities->Terminal.app Linux: Terminal
Type in Command Prompt: fastboot oem get_identifier_token.
Step 6
You will see a long block of text. Copy and paste this text into the the token field below (in the Windows command prompt: Right Click > Mark > highlight the block of text > Right click to copy. Mac users can use cmd-option to mark and select text.).
When copying the token, start with this line:
<<<< Identifier Token Start >>>>
And end with this line:
<<<<< Identifier Token End >>>>>
(Note: Do not copy the INFO or (bootloader) prefix)
Step 7
Paste this string of text into the token field and hit Submit in order to receive your unlock code binary file. You will receive this information in your email.​ h. After hitting submit, HTC will send you an email. Sender is HTC-Unlockbootloader. Subject is "The key to unlocking your HTC Device."
Email Message:
Attached to the email is Unlock_code.bin. This is the file you will need to download in order to unlock your bootloader. This file is device specific. You cannot use this file to unlock any other HTC phone. Please do not try as this will probably result in a brick.
Click the link provided in the email to continue the steps to unlock your bootloader​ i. Follow the on-screen steps provided
Step 8
You will receive an email with the attachment: Unlock_code.bin. Save this file in the same folder as your fastboot files (For Example: C:\Android).
If, after a short period of time, you have not yet received the mail, or you have received an email from HTC, but does not contain an attached file, it is possible that more stringent spam filters and anti-virus programs will block this mail or attachment.
In order to ensure that you receive the email with the attachment, we suggest you consider using a non-corporate email server as corporate servers tend to have more stringent attachment policies. If you have not received the email at all, please check your spam folder in your email client to check if the email was filtered out.
Step 9
In the command prompt type: fastboot flash unlocktoken Unlock_code.bin. In the command prompt you will see the following message:
Code:
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' <0KB>...
OKAY [ 0.151s]
writing 'unlocktoken'...
<bootloader> unlock token check successfully
OKAY [0.006s]
finished. total time: 0.158s
Step 10
On your phone you will now see the disclaimer. Please read this carefully as this action may void your warranty. Use the Volume buttons to highlight your choice, and the Power button to make your selection. If you select Yes, your phone will be reset to its’ factory default settings, and your bootloader will be unlocked. If you select No, your phone will reboot and no modifications will have been made.
Step 11
To re-lock your bootloader, in the command prompt, type: fastboot oem lock.
Note: This will not restore the factory default lock, but will simply re-lock the bootloader so no further changes can be made. Furthermore, if you want to unlock your bootloader again, simply repeat step 9 with your original unlock key file to unlock your phone again.​ j. Congratulations, your phone now has an unlocked bootloader! If your phone hasn't done so already, reboot it and let it sit at the welcome screen for the requisite 5-10 minutes to settle. Turn off your phone, and reboot to HBOOT with volume down + power button. Select fastboot.​
​
2. Install a custom recovery
As far as I know, there are two recoveries that are fully functional with our M8 variant:
TWRP
PhilZ Touch CWM​ a. Download your chosen recovery from the above links.
b. Rename it recovery.img
c. Drop it in the same folder as your adb and fastboot binaries.
d. After booting to fastboot mode, make sure your device is still plugged in and run the following command in your command window:
fastboot devices
Your computer shouldn't have any troubles recognizing your phone since we just went through the bootloader unlock, but it's always best to be safe.​ e. Now run the command:
fastboot flash recovery recovery.img
Expected output:
Code:
C:\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' <14,818KB>...
OKAY [ 0.871s]
writing 'recovery'...
OKAY [ 1.501s]
finished. total time: 2.543s
f. Congratulations! You now have a custom recovery installed.
g. I recommend immediately making a backup of your fresh operating system (pre-root) by selecting HBOOT from the fastboot menu, then selecting and booting into recovery
h. After booting into your new custom recovery select backup from your list of options and proceed to select your backup location (internal or micro sd) and continue to the backup. It will be quite large, but this will provide you a good starting point should you ever need to restore to factory settings for any reason.
i. I use TWRP, because it will automatically prompt you to install root and SuperSU upon rebooting from recovery.
I am unsure how to achieve root after flashing PhilZ Touch. If anyone provides the info I will add it to this guide.​
​
3. Achieve S-Off (Hopefully!)
The instructions to attaining S-Off are listed on the firewater s-off page linked above. They are really comprehensive and you should follow them to the letter. Make sure that you read through their prerequisites as well.
Note: On prerequisite number four, it states that you must be "HTCDEV unlocked/rooted." Please read this as you must be HTCDEV unlocked AND rooted.​
I didn't want to post the firewater team's instructions here (I didn't ask permission yet), so this section will be more for information regarding the S-Off process that I have gathered from other threads and this one going forward.
Issues seen with Firewater:
Firewater does not work on every T-Mobile M8. If, when running firewater, you see "Whelp, this sucks..." firewater will not work on your phone.
The speculation is, there are different components used during the builds due to sourcing those components from different companies. It seems that some people believe that the phone build date may indicate the devices that have components that are compatible with the exploit. So we'll document this to try to see who achieved S-Off on which build dates.
Issue: Firewater hangs but does not give the "Whelp this sucks..." message:
Possible Solutions: Your device is likely compatible. You must be persistent. Keep trying.
Hit Ctrl+C to exit the exploit and try again starting from "adb reboot" (from @Fenny)
Unplug your USB cable, reboot your phone manually. Once it boots up, plug in your USB cable (from @epsix)
Plug in your USB cable, adb reboot. Once it boots, go to Developer Options and uncheck and recheck USB Debugging (from @epsix)
Install BusyBox (from @renn9420)​ Issue: After running adb reboot command and pushing firewater phone shows up as "offline"
Possible Solutions: Make sure that you granted su permissions to your adb shell through SuperSU
I had this happen to me. I would go to run the command and suddenly, the phone is disconnected. I ran through the adb reboot steps a couple of times and finally when executing firewater it ran. Went through the steps 3 times before it ran.​
Build Dates S-Off Achieved On:
04/01/2014
04/04/2014
04/07/2014
04/12/2014​
Build Dates S-Off Not Achieved On:
04/03/2014 x2
04/08/2014
04/09/2014
04/10/2014
04/11/2014​
​
4: Other
a. @Fenny noticed that /data/preload/ gets emptied after HTC Dev Unlock. If you're hanging onto your stock ROM and don't plan to change to a custom OS you'll want to replace these files. Go here to replace them: http://forum.xda-developers.com/showthread.php?t=2714522​
Thanks go to:
@beaups - firewater
@Dees_Troy - TWRP
@Phil3759 - PhilZ Touch
@Fenny - Stock + ROM, Hacked HBOOT, Preload data & more
@Turge - ViperOneM8
@Chainfire - SuperSU
@jcase - for looking into getting weaksauce working on our phones
Click to expand...
Click to collapse
tks

tnez said:
thanks for writing this up!! got the dang Whelp message tho build date of 04/05/2014 if you want to add that to the list
Click to expand...
Click to collapse
Thanks for posting your results. OP updated with your build date.
abutran said:
tks
Click to expand...
Click to collapse
You're welcome. If you don't mind, please edit your post to remove the quote of the OP. It keeps the thread much shorter for people on mobile devices. Thanks.
Sent from my HTC One M8

uoY_redruM said:
Glad someone condensed everything down into an instructional guide. This should be stickied (if it's not already).
Thanks bro! :good::good:
Click to expand...
Click to collapse
Saw your post in the other thread and agreed with you! It was way too many pages to sift through.
Sent from my HTC One M8

Anyone good to go with a build date of 04/01/2014?

donciclon said:
Anyone good to go with a build date of 04/01/2014?
Click to expand...
Click to collapse
My build date is 04/01/2014 and I was able to achieve S-Off. If you try it, let us know the results. We haven't pinned down if the build date is the indicator. I'm hoping like hell it is though.
Sent from my HTC One M8

04/07/2014 build date no go... Got the whelp message as well.
Sent from my HTC One_M8 using Tapatalk

irrelephant said:
04/07/2014 build date no go... Got the whelp message as well.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
As I've said in the other thread it is the luck of the draw. Assembly date and location have little to do with it. It's a matter of what components were put into your device and that is a matter of what components were available at the time of assembly.
Just because one device was produced with exploitable components on one day doesn't mean another device wasn't produced with unexploitable components on the same day. A run of a particular component can run out at any time. When it does the next available run of components will be used.

Behold_this said:
As I've said in the other thread it is the luck of the draw. Assembly date and location have little to do with it. It's a matter of what components were put into your device and that is a matter of what components were available at the time of assembly.
Just because one device was produced with exploitable components on one day doesn't mean another device wasn't produced with unexploitable components on the same day.
Click to expand...
Click to collapse
That's what I was thinking too. Multiple runs happen on any given day.
I was hoping it would be as simple as the build date. Of course we're not that lucky though. Lol. Whelp.... Back to the drawing board.
Sent from my HTC One M8

Behold_this said:
As I've said in the other thread it is the luck of the draw. Assembly date and location have little to do with it. It's a matter of what components were put into your device and that is a matter of what components were available at the time of assembly.
Just because one device was produced with exploitable components on one day doesn't mean another device wasn't produced with unexploitable components on the same day. A run of a particular component can run out at any time. When it does the next available run of components will be used.
Click to expand...
Click to collapse
Well what information might be of assistance and I will gladly provide it. I'm pretty good with adb, and willing.
Sent from my HTC One_M8 using Tapatalk

RUU Flash ADB stuck during 'sending ZIP'

Hi Folks
Let me preface by saying I've flashed RUU before, and flashed many recoveries and ROMs over the years, not a total novice, but certainly no expert either. But I've never seen anything quite like this one, and not sure what to do at this point.
first, I downloaded the GPE non-rooted RUU and copied the zip into my ADB folder (Windows 10 PC)
then, I connected phone, shift+rclick open cmd window in ADB folder
renamed the file "ruu2.zip" (which was a mistake, it should have just been "ruu2")
adb devices - device recognized
adb reboot bootloader
fastboot oem readcid - it's GOOGL001, no problem
fastboot oem rebootRUU - no problem, HTC logo displayed on device
fastboot flash zip <drag and drop file into cmd window> - (note, I haven't actually done that before, I've always just typed it, and drag+drop showed whole file path - "C:\user\me\adb\ruu2.zip.zip" - but shouldnt make a difference, as far as I know, so I hit enter)
it ran through everything, checked zip, etc then failed. This is expected and normal, no problem.
so I hit up arrow, reloaded the command and hit enter...
and now my cmd window is stuck. It says "sending zip", displays file size, and the cursor is flashing...and nothing is happening. It's been an hr or more. Nothing is going to happen.
Now what?
If I pull the phone am I going to be bricked? I just alt-tabbed and googled for a solution, but didn't find anything. So I figured I better post here. This is not a good place to be stuck.
Thanks in advance.
(I have a screenshot of my cmd window but I don't have enough posts to link it.)
EDIT: Figured worst case = new phone. Pulled cord. CMD window reset itself, phone stayed in RUU mode. Would not power down or respond to any button combo. Reconnected cable, entered command again, and it went. Worked fine. No idea why that happened, but all is well.
Thanks anyway.
Mods, please close thread. Thanks.

Sir_Cusfreak said:
renamed the file "ruu2.zip" (which was a mistake, it should have just been "ruu2")
Click to expand...
Click to collapse
Highly recommend you disable the Windows option to hide file extensions, to avoid any future file name confusion.
Sir_Cusfreak said:
Mods, please close thread. Thanks.
Click to expand...
Click to collapse
Threads typically stay open, in case there are other members with a similar issue, subsequent comments, etc.
Mods usually only close threads, if you start a thread about something you shouldn't have!

Hi, just wanted to say that the same thing happened to me, i got stuck on sending zip .. and i did like the OP, disconnected the cable and reconnected again, the cmd reset just like the OP said and after i put the command again it worked for me too. Cheers.

i had to do the trick a few times before it worked. thanks

Noob Bootloader Unlock Guide: Answers to several questions and solutions to problems.

***Warning: I am not responsible for bricked or broken devices, warranties, computers, etc. This is your phone and your free will to follow the below steps and you bare the full burden of any consequences.***
A note for the Moderators: I am aware that the information I am about to provide exists outside of this thread. The purpose of this is not for redundancy or to clutter the forum. I am making this thread because I had to go to SEVERAL different sources to find these solutions and pull pieces from each. Hopefully, this is comprehensive enough to help someone who may have been in the same boat I was in. This is truly Noob friendly and intended for someone just beginning in the Android community, because of this it is painfully detailed. Hopefully, you will allow it to stay up.
The purpose of this thread is to address several issues I ran into while attempting to unlock my bootloader as well as address questions I personally had that I couldn't find answers to by using myself as the test dummy. Those items are as follow:
1) ADB was not functioning properly with Windows 10.
2) My Windows 10 laptop could recognize my OneTouch 7t in ADB devices but could not recognize it in Fastboot. Windows 10 wouldn't let me install the drivers that come pre-loaded on the OnePlus 7t.
3) After Unlocking the bootloader I hit a "checking info" loop with Google.
4) Does unlocking a bootloader on the OnePlus 7t cause any Safety Net Issues?
5) What does a SafetyNet failure result in?
6) Will every app work with an unlocked bootloader?
Solutions and answers:
1) This is going to be a detailed process but in the end, you'll have universal ADB and fix your windows issues:
If you decide to unlock the bootloader IT WILL WIPE EVERYTHING. This includes photos, apps, music, etc. So start by doing a backup:
-Settings>search "switch">OnePlus Switch>Backup & Restore> New Backup
-Copy that backup folder to your computer by plugging the phone into the computer> settings>search "USB">USB preferences>select file transfer>On your computer open up HD1905>internal shared storage>copy the "opbackup" folder to your computer (this will take a while)
Now to get Developer options:
-On your phone>settings>about phone>Tap build number until it says you are a developer
-Settings>system>developer options>turn on USB debugging
Getting ADB set up on your computer:
-Download and install SDK Platform-Tools for Windows: https://developer.android.com/studio/releases/platform-tools
-on Windows>Open up Command Prompt (run>cmd>enter)>Type sysdm.cpl> hit enter
-Go to the advanced tab in the window that pops up> environment variables>path>new>browse.
-Now find where you installed the SDK platform-tools and select the folder that says "platform-tools"
click ok>ok>ok
Testing ADB:
-Open a new Comand Prompt in Admin mode. To do this Open run type "cmd" and then hit Ctl+Shift+Enter and click ok to the pop-up
-Plug your phone into the computer
-In Command Prompt type "adb devices" and hit enter
-You should now see your phone ID
-Type "adb reboot bootloader" and hit enter
-Your phone will reboot into bootloader
-Type "fastboot devices" and hit enter
-If your ID does not show up go to step 2 without changing anything (ie. stay in Command Prompt with the phone plugged in at the bootloader menu)
2)-This step fixes the driver issue that likely causes problem #1.
Get the newest Android drivers:
-Download and install Android Studio: https://developer.android.com/studio
-Launch Android Studio
-Configure>SDK Manager>SDK Tools>Google USB Driver>Apply>Ok
-At the top, it will say SDK path I highly suggest you copy that or write it down you will need it soon.
-Click Finish and close Android Studio
Installed drivers for fastboot:
-Open any folder and then select "view" at the top of the window and check the box that says hidden files then close the window.
-windows key+x>device manager>right click on the phone with the orange exclamation point>update drivers>browse my computer>browse>go to the folder location>next>finish
If that doesn't work and you get "Windows was unable to install driver" error do the following:
-click search for updated drivers on windows update>a new window will come up> Update and restart your computer
-Once back on and updated>windows key+x>device manager>right click on the phone with the orange exclamation point>update drivers>browse my computer>let me pick from a list>Android Bootloader interface>next>once finished, close the window.
To Test if this fixed the issue:
open an Admin Command Prompt and type "fastboot devices" and hit enter, you should now see your phone's ID.
WARNING: IF YOU DO THE NEXT STEP YOUR PHONE WILL BE FULLY WIPED. ENSURE YOU MADE A BACKUP!!!
Now to unlock the bootloader:
-In Admin Command prompt type "fastboot oem unlock" and hit enter
-On your phone use the volume keys to select "unlock the bootloader" then use the power key to select it.
Congrats your bootloader is now unlocked. Now for the problems you may face once it's back on
3) If you hit the "checking info" Google loop follow these steps:
-Go to Settings> Battery> Battery Saver>Turn off when fully charged>Select OFF,
-Go Settings> Apps&notifications>See All ## Apps>3 Dot menu>Reset app preferences> reset Apps,
-Go Settings> Apps&notifications>See All ## Apps>3 Dot menu>Show System
-----Select Google play store >Storage & cache>Clear Storage
-----Press Back
-----Select Download manager> Storage & cache>Clear Storage
-----Press Back
-----Select Google play services> Storage & cache>Clear Storage>Clear All Data
-Go to Settings >Accounts> Google Account name/ Names> 3 Dot Menu> Remove ALL Accounts
-Restart device
-Connect to Wifi
-Go to Settings >Accounts>Add Account>Google
4) Yes, unlocking your bootloader on the OnePlus 7t results in a "CTS Profile Match=false" failure in SafetyNet
5)From what I can tell this SafetyNet failure doesn't really cause too many issues but time will tell and I will update this accordingly.
6) I tested the known problem children ie. Google pay, PokemonGo, and Snapchat. All were good. The only exception I ran into was Netflix. It will not work with an unlocked bootloader. There may be ways to resolve this but I haven't tried them yet as this is all without Root. I will update this post when I find solutions.
Again I know that most of this can be found but it took me a decent amount of digging. More importantly, a lot of the stuff was implied knowledge that many of us already have but a newcomer wouldn't. Hopefully, this is useful to the new and old alike feel free to ask questions below as I will be continuing to test stuff further.

Saved
Update:
How to fix SafetyNet failure:
Get Root
-Follow this link: https://forum.xda-developers.com/oneplus-7t/how-to/magisk-auto-root-tool-oneplus-7t-pro-t4079355#post82221323
This is hands down the easiest root method I have ever seen for any device. HUGE shoutout to @daxiaamu and @mauronofrio for this!
Install Magisk Manager
On Your phone go to https://github.com/topjohnwu/Magisk/releases/
and download the latest version of Magisk Manager.
Allow unknown sources> install
Update Magisk
Once in Magisk Manager it will prompt you to install some updates for our phone. Install them and let it reboot.
Install Magisk Hide
Open Magisk>Three lines in top left corner>Downloads>MagiskHide Prop Config>download>install
Test
Once your phone has rebooted open Magisk>SafetyNet Check Status>Prosper!
Thank you to the Magisk team for making this hands down the easiest experience I have ever seen on Android and to @daxiaamu for making a truly one-click install that works flawlessly!

This should be pinned, but I have ctsProfile: false.
Is that expected?

lucfig said:
This should be pinned, but I have ctsProfile: false.
Is that expected?
Click to expand...
Click to collapse
If you have the bootloader unlocked, yes. Magisk won't be able to hide the lock/root status from SafetyNet once Google fully rolls out their updates to SafetyNet/Play Services.
https://twitter.com/topjohnwu/status/1251712525843918853
Signing ROMs with custom keys and relocking may be a possibility, but I haven't tested anything on the 7T, and I'm staying locked until official support ends since the days of passing SafetyNet with root/unlocked bootloaders appears to be over.

lucfig said:
This should be pinned, but I have ctsProfile: false.
Is that expected?
Click to expand...
Click to collapse
Thank you, it took a while to write was a little discouraged with the lack of response lol. To fix cts error:
Open Magisk>settings>turn off magisk hide
Magisk>Downloads>MagiskHide Props Config> Download and reboot
Magisk>Settings>Turn on MagiskHide
Test again should be good

C4sp3R911 said:
Thank you, it took a while to write was a little discouraged with the lack of response lol. To fix cts error:
Open Magisk>settings>turn off magisk hide
Magisk>Downloads>MagiskHide Props Config> Download and reboot
Magisk>Settings>Turn on MagiskHide
Test again should be good
Click to expand...
Click to collapse
Hope it gets more visibility, is the most detailed and easy to follow instructions.
I figured that out. Without riru or edxposed the Magisk hide works great.

otto888 said:
If you have the bootloader unlocked, yes. Magisk won't be able to hide the lock/root status from SafetyNet once Google fully rolls out their updates to SafetyNet/Play Services.
https://twitter.com/topjohnwu/status/1251712525843918853
Signing ROMs with custom keys and relocking may be a possibility, but I haven't tested anything on the 7T, and I'm staying locked until official support ends since the days of passing SafetyNet with root/unlocked bootloaders appears to be over.
Click to expand...
Click to collapse
We were able to fix it through MagiskHide. Both methods above worked.

Hey guys, I just received my OP7T today (upgrading from the 5T), and I see that there's no official TWRP yet. I've been looking around to see if it's worth it to root the phone already.
Is the rooting already stable enough, or should I wait a couple more months for full modded roms to come out? 'cause I really enjoy having the root features that some apps offer, but I also definitely need MagiskHide to work so my bank app won't have any issues with the unlocked bootloader.
If the guide above is up to date and working like C4sp3R911 posted, I'd be down to try it today.

Could I still use the the following command if OEM Unlocking is grayed out in Settings? Thanks.
"fastboot flashing unlock"
or
"fastboot OEM unlock"

What?... You need to learn a bit more before messing with bootloader unlocking, fastboot flashing unlock is not a command and will do nothing... Check yourself before you wreck yourself as the saying goes,
If it's greyed out doesn't that mean the BL is already unlocked?

C4sp3R911 said:
***Warning: I am not responsible for bricked or broken devices, warranties, computers, etc. This is your phone and your free will to follow the below steps and you bare the full burden of any consequences.***
A note for the Moderators: I am aware that the information I am about to provide exists outside of this thread. The purpose of this is not for redundancy or to clutter the forum. I am making this thread because I had to go to SEVERAL different sources to find these solutions and pull pieces from each. Hopefully, this is comprehensive enough to help someone who may have been in the same boat I was in. This is truly Noob friendly and intended for someone just beginning in the Android community, because of this it is painfully detailed. Hopefully, you will allow it to stay up.
The purpose of this thread is to address several issues I ran into while attempting to unlock my bootloader as well as address questions I personally had that I couldn't find answers to by using myself as the test dummy. Those items are as follow:
1) ADB was not functioning properly with Windows 10.
2) My Windows 10 laptop could recognize my OneTouch 7t in ADB devices but could not recognize it in Fastboot. Windows 10 wouldn't let me install the drivers that come pre-loaded on the OnePlus 7t.
3) After Unlocking the bootloader I hit a "checking info" loop with Google.
4) Does unlocking a bootloader on the OnePlus 7t cause any Safety Net Issues?
5) What does a SafetyNet failure result in?
6) Will every app work with an unlocked bootloader?
Solutions and answers:
1) This is going to be a detailed process but in the end, you'll have universal ADB and fix your windows issues:
If you decide to unlock the bootloader IT WILL WIPE EVERYTHING. This includes photos, apps, music, etc. So start by doing a backup:
-Settings>search "switch">OnePlus Switch>Backup & Restore> New Backup
-Copy that backup folder to your computer by plugging the phone into the computer> settings>search "USB">USB preferences>select file transfer>On your computer open up HD1905>internal shared storage>copy the "opbackup" folder to your computer (this will take a while)
Now to get Developer options:
-On your phone>settings>about phone>Tap build number until it says you are a developer
-Settings>system>developer options>turn on USB debugging
Getting ADB set up on your computer:
-Download and install SDK Platform-Tools for Windows: https://developer.android.com/studio/releases/platform-tools
-on Windows>Open up Command Prompt (run>cmd>enter)>Type sysdm.cpl> hit enter
-Go to the advanced tab in the window that pops up> environment variables>path>new>browse.
-Now find where you installed the SDK platform-tools and select the folder that says "platform-tools"
click ok>ok>ok
Testing ADB:
-Open a new Comand Prompt in Admin mode. To do this Open run type "cmd" and then hit Ctl+Shift+Enter and click ok to the pop-up
-Plug your phone into the computer
-In Command Prompt type "adb devices" and hit enter
-You should now see your phone ID
-Type "adb reboot bootloader" and hit enter
-Your phone will reboot into bootloader
-Type "fastboot devices" and hit enter
-If your ID does not show up go to step 2 without changing anything (ie. stay in Command Prompt with the phone plugged in at the bootloader menu)
2)-This step fixes the driver issue that likely causes problem #1.
Get the newest Android drivers:
-Download and install Android Studio: https://developer.android.com/studio
-Launch Android Studio
-Configure>SDK Manager>SDK Tools>Google USB Driver>Apply>Ok
-At the top, it will say SDK path I highly suggest you copy that or write it down you will need it soon.
-Click Finish and close Android Studio
Installed drivers for fastboot:
-Open any folder and then select "view" at the top of the window and check the box that says hidden files then close the window.
-windows key+x>device manager>right click on the phone with the orange exclamation point>update drivers>browse my computer>browse>go to the folder location>next>finish
If that doesn't work and you get "Windows was unable to install driver" error do the following:
-click search for updated drivers on windows update>a new window will come up> Update and restart your computer
-Once back on and updated>windows key+x>device manager>right click on the phone with the orange exclamation point>update drivers>browse my computer>let me pick from a list>Android Bootloader interface>next>once finished, close the window.
To Test if this fixed the issue:
open an Admin Command Prompt and type "fastboot devices" and hit enter, you should now see your phone's ID.
WARNING: IF YOU DO THE NEXT STEP YOUR PHONE WILL BE FULLY WIPED. ENSURE YOU MADE A BACKUP!!!
Now to unlock the bootloader:
-In Admin Command prompt type "fastboot oem unlock" and hit enter
-On your phone use the volume keys to select "unlock the bootloader" then use the power key to select it.
Congrats your bootloader is now unlocked. Now for the problems you may face once it's back on
3) If you hit the "checking info" Google loop follow these steps:
-Go to Settings> Battery> Battery Saver>Turn off when fully charged>Select OFF,
-Go Settings> Apps&notifications>See All ## Apps>3 Dot menu>Reset app preferences> reset Apps,
-Go Settings> Apps&notifications>See All ## Apps>3 Dot menu>Show System
-----Select Google play store >Storage & cache>Clear Storage
-----Press Back
-----Select Download manager> Storage & cache>Clear Storage
-----Press Back
-----Select Google play services> Storage & cache>Clear Storage>Clear All Data
-Go to Settings >Accounts> Google Account name/ Names> 3 Dot Menu> Remove ALL Accounts
-Restart device
-Connect to Wifi
-Go to Settings >Accounts>Add Account>Google
4) Yes, unlocking your bootloader on the OnePlus 7t results in a "CTS Profile Match=false" failure in SafetyNet
5)From what I can tell this SafetyNet failure doesn't really cause too many issues but time will tell and I will update this accordingly.
6) I tested the known problem children ie. Google pay, PokemonGo, and Snapchat. All were good. The only exception I ran into was Netflix. It will not work with an unlocked bootloader. There may be ways to resolve this but I haven't tried them yet as this is all without Root. I will update this post when I find solutions.
Again I know that most of this can be found but it took me a decent amount of digging. More importantly, a lot of the stuff was implied knowledge that many of us already have but a newcomer wouldn't. Hopefully, this is useful to the new and old alike feel free to ask questions below as I will be continuing to test stuff further.
Click to expand...
Click to collapse
Just bought the op7t pro and followed your guide step by step, but still fastboot devices does not show nothing to me
Tried in 2 different windows pc with same results, don't know how to do now

Having trouble getting adb setup on my computer. Specifically here:
-Now find where you installed the SDK platform-tools and select the folder that says "platform-tools"
click ok>ok>ok-
In "Environment Variables" popup, I select "path" in the top field, then click "new". The next popup is "New User Variable". Here, I've clicked "Browse Directory", as well as "Browse File", but each time I click platform-tools and click OK, the OK in the "New User Variable" popup is greyed out. I've tried even clicking on a subfolder to platform-tools, just to see if that 2nd OK would be active, but it isn't. Any help is much appreciated.

doncheadlesdriveway said:
Having trouble getting adb setup on my computer. Specifically here:
-Now find where you installed the SDK platform-tools and select the folder that says "platform-tools"
click ok>ok>ok-
In "Environment Variables" popup, I select "path" in the top field, then click "new". The next popup is "New User Variable". Here, I've clicked "Browse Directory", as well as "Browse File", but each time I click platform-tools and click OK, the OK in the "New User Variable" popup is greyed out. I've tried even clicking on a subfolder to platform-tools, just to see if that 2nd OK would be active, but it isn't. Any help is much appreciated.
Click to expand...
Click to collapse
Great. Thanks for the help.