Database Develop

[GUIDE] Changing your Bluetooth/Wi-Fi MAC Address

Hi guys
Well, I had an Atrix for a few days, but had some issues with AT&T and had to return it and deal with some customer service issues before I can re-purchase the device. I didn't let that slow me down though
While I had it, I made a few dumps of the NAND, and have been working on disassembling things. Thanks to the help from a number of great people on IRC (#xda-devs irc.freenode.net) I have been able to successfully change the Bluetooth and Wi-Fi MAC addresses, and discovered a way to write to the flash, bypassing the bootloader security.
The full writeup can be found at pocketnow.com
I will be posting more info about the bootloader bypass as soon as I get it 100% working, right now we are able to write data directly to the NAND, bypassing bootloader security, and also provide a false signature, allowing the device to boot. However there are some remaining issues (a custom kernel that was flashed to the device failed to boot properly) - stay tuned

You the man, thanks for the efforts !

Sweeeet!
Wonderful work!

Excellent, can't wait to see the end result. Hopefully custom kernels and ROMs will be coming soon.

Devs you guys are amazing! Thank you for the hard work that is put into all this! I know the challange is fun for you all, but it really helps us non dev ppl out a lot!
Sent from my MB860 using XDA App

nicely done Da-G.... great work as always glad to see you again and i hope to continue using your work as i did back in old winmo cooking !!!
quick question, is there really a reason why to change the bluetooth/wifi MAC drivers??? are there any benefits or basically just the same exact reasons when you do it on pc's

Main reason to change MAC address is to be able to join Wi-Fi networks that have whitelisting.
You could also use it to simplify device administration on your network.
Beyond that I can also imagine a few black-hat reasons to do it
Atrix is one of the few smartphones that can pull it off easily though, others I am aware of are the LG Optimus One and the SGS series (although it's not so easy on SGS)
There are plenty of other interesting datas in /pds, it is the device provisioning partition (NVRAM) and is equivalent to /efs on the i9000/Captivate (which is the last device I used, so easy for me to compare with)
Careful messing with it though, on the Captivate changing the wrong bit would kill your cellular radio until you restored an EFS backup, I suspect the same danger is here with the Atrix too! And we don't have a quick way to restore a PDS backup yet like with odin on SGS (although I am hot on the heels of a method to do so)

Omfg I'm excited! If this device gets real ROMs an even custom kernels, its going to be an even more amazing device
Sent from my MB860 using XDA Premium App

i'm exited about the bootloader bypass, i thought the firmware would do a complete checksum of it, so if it's partial then we should be able to find out exactly what gets checked.
i'm curious to see if you have been able to find something regarding sim unlock, just like the sgs was holding the lock very easily changeable with a simple hex editor. i bought the code already but maybe other people will get lucky

I've asked for a backup of /pds prior to and after locking over in the general forum, hopefully a few people can send those my way. I suspect a good hard look at that will reveal the location and provide an easy unlock method (I think I located it already, but as /pds is not restored via flashing the leaked SBF, i'm loathe to have someone else try it in fear of brickage)
I'll hammer it out once I get my device back in hand, whenever AT&T decides to allow me to purcahse

Da_G said:
I've asked for a backup of /pds prior and after locking over in the general forum, hopefully a few people can send those my way. I suspect a good hard look at that will reveal the location and provide an easy unlock method (I think I located it already, but as /pds is not restored via flashing the leaked SBF, i'm loathe to have someone else try it in fear of brickage)
I'll hammer it out once I get my device back in hand, whenever AT&T decides to allow me to purcahse
Click to expand...
Click to collapse
i will do it, but i am getting a permission denied.
Code:
C:\Users\fjleon\Desktop\android-sdk-windows\platform-tools>adb shell tar zcvpf /
sdcard-ext/pds-backup.tar.gz /pds/
tar: can't open '/sdcard-ext/pds-backup.tar.gz': Permission denied
i tried adb shell su and accepted super user on the phone, but i still cannot do it

wow bypass= custom roms...... this would be ingenious hope u get it working....
how does rsd lite 5 flashing work??? it seems to create an image and then re sign it.... would backtracking and try to use the same method work?

@franciscojavierleon:
Make sure you don't have usb internal/sd storage mounted when you issue the command, or the sd card will be unaccessible from device
@ahjdmarchi:
I didn't study the program too much yet. I'll look to that if the current method i'm working on proves to be a failure

Da_G said:
@franciscojavierleon:
Make sure you don't have usb internal/sd storage mounted when you issue the command, or the sd card will be unaccessible from device
@ahjdmarchi:
I didn't study the program too much yet. I'll look to that if the current method i'm working on proves to be a failure
Click to expand...
Click to collapse
heres a tattoo that i have on my chest
"failure is not an option" good luck brudda hope all turns well

Da_G said:
@franciscojavierleon:
Make sure you don't have usb internal/sd storage mounted when you issue the command, or the sd card will be unaccessible from device
Click to expand...
Click to collapse
i unmounted it and tried again and still get the same error. i killed root explorer first since i had it open and no dice

@franciscojavierleon:
Try this instead.
Code:
adb shell tar zcvpf /data/local/tmp/pds-backup.tar.gz /pds/
adb pull /data/local/tmp/pds-backup.tar.gz
adb shell rm /data/local/tmp/pds-backup.tar.gz

RadioComm
You really need to take a look at RadioComm if you haven't yet.
The BT MAC address can be edited directly in the NVM on all Motorola devices.
On CDMA chipset devices it is located in seem 01bf record 0001 bytes 0006 and there is also a module and special set of TCI commands for managing this called HOB restore.
There are also flags set in the firmware for whether the HOB is verified during the flash cycle or not.
just an FYI!

@cellzealot:
Checked out RadioComm already, but none of the commands work for Atrix. Have you tried it? Perhaps you have a more updated version?

Edited. Nevermind just saw you needed it before unlock as well. I've got my PDS folder from my unlocked phone if you need it (not sure)

i should get my unlock between today and tomorrow, so with my locked pds backup i will do a diff to see if anything gets changed at all.

Lenovo Ideapad K1 One-Click Root (Mostly)

First, please forgive me if this is posted in the wrong section. It seemed most appropriate.
Second, I take no credit for anything here except for writing the .bat file here used to do the work, as well as assembling the files as per the original post.
All credit goes to djmwj and his article found here:
http://rootzwiki.com/topic/8722-lenovo-ideapad-k1-rooting-guide-messy/
As the title states, it was very messy. The OP figured out how to make it go, but it was a bit fuzzy to follow. So, I thought I'd help folks out a bit and clean things up.
So, I took the instructions presented in the OP, and condensed them into one download with one .bat that does everything from start to finish, minus installing the respective drivers for ADB and NVFlash. However, the drivers are included in the download.
Instructions:
1. Extract K1Root.rar to the directory of your choosing.
2. Connect your tablet to your PC with the USB cable.
3. With your tablet off, press POWER+VOL_UP+VOL_DOWN until the screen turns on, but displays only black.
4. Windows should detect the device, but not install drivers.
5. Go into device manager, select the APX device, choose update drivers, and install the drivers from the aptly named NVFlash_Drivers folder.
6. Open up the NVFLASH_HOME folder and run the file K1Flash.bat
7. Make your desired choices when prompted, and enjoy.
Notes (PLEASE READ BEFORE USING):
THERE MAY BE BUGS! I used it on my own stuff before releasing, and all of the essential components work as they should, however, there may possibly be a minor hiccup somewhere in the script. This should not damage anything. If you have doubts, you're welcome to examine the .bat and check it for yourself.
Please be gentle. I am not a full-time developer. I just wrote this to help make the process simpler for people.
The OP suggests you download and read the partition table, and then name the backup files based on that. This script names the backup files based on the flash.cfg script referenced in the OP, which is what controls the flashes used anyway. So, there shouldn't be any irregularities, however, I can't speak for every device on the planet.
This does NOT use the latest OTA updates. The rooted files being flashed are the default ones from the original download. You can easily adapt this to any files generated from the latest OTA files by simply dropping them in the NVFLASH_HOME file.
To install the SU properly, you have to install ADB drivers midway through the script. There's probably a way around this, but I didn't find it to be too inconvenient.
The ADB drivers are also located in the NVFLASH_HOME folder. Just do like you did when installing drivers in step #5, but instead point to NVFLASH_HOME.
Um...um...
That should be it. Obviously, use at your own risk. Let me know if there are problems with the script, and I will fix them.
Oh, and party on, Wayne.
http://www.megaupload.com/?d=AG10XE25
EDIT:
Attached is an updated .bat file which fixes a few errors in the original script, plus adds more userability. Just extract to the NVFLASH_HOME folder and run.

digitalhigh said:
First, please forgive me if this is posted in the wrong section. It seemed most appropriate.
Click to expand...
Click to collapse
You may want to change the title to Ideapad K1, I don't know if this will work for the Thinkpad tablet.
Thanks for this, I just picked up this tablet ($250 at staples) and was worrying about having to tackle linux and "compiling" just to be able to get hulu.com working. You're a lifesaver.

gallahad2000 said:
You may want to change the title to Ideapad K1, I don't know if this will work for the Thinkpad tablet.
Thanks for this, I just picked up this tablet ($250 at staples) and was worrying about having to tackle linux and "compiling" just to be able to get hulu.com working. You're a lifesaver.
Click to expand...
Click to collapse
Wow. Yeah, I'm pretty sure the key used is just for the Ideapad. Thanks for pointing that out. My dumb a$$ must've blanked out and just used the group name when posting.
And just to be fair, the original poster does include everything needed to do stuff in windows as well - it's just very hard to discern from the post.

question
Is anyone working on a custom ROM for this tablet? I am hopeing that there will be at least a few custom roms available at some point in the near future.

jfkerekes said:
Is anyone working on a custom ROM for this tablet? I am hopeing that there will be at least a few custom roms available at some point in the near future.
Click to expand...
Click to collapse
We need to be able to root and unlock the bootloader first.

Does the root method work on the 121211 update?
Or is there a way to flash back to the older firmware?

the OTA update 12 12 11.... seems to be update.zip style with no .img files inside. just loose files like normal rom updates. doesnt seeem like you can drop the files in as suggested. or i have the wrong OTA....
oh and is this for LINUX as the OP or work in windows too??

Hi, I was wondering, is this procedure works for the Lenovo ThinkPad 1838-25U? I'm thinking to buy it to give a test ride, i sold my Transformer 101 to buy the Prime but it seems like Asus is taking vacations on the delivery shipments. Is this a good tablet? or is better to wait for another version?

READ THE POST
IDEApad not THINKpad. no it wont work.

First of all- thank you so much for creating this script! I have been putting off rooting this device due to the "messy" nature of the original post.
I was hoping you could help me troubleshoot, I have tried both the new K1 root application and the original .bat file. I know the drivers are working because the script makes it as far as creating and formatting partitions and successfully pushes the bootlooder.bin but then:
bootloader.bin sent successfully
file not found: recovery.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
I've tried everything I can think of... any ideas?
Thanks again.

I found problem.
after root done follow step. I cannot factory reset and update any ota.
anyone can help me ?

taiz said:
I found problem.
after root done follow step. I cannot factory reset and update any ota.
anyone can help me ?
Click to expand...
Click to collapse
Yes you have to roll-back to 04 stock and then apply the OTA's

Backup of the stock lenovo .apks!
File 1:http://www.mediafire.com/?r7iskr3wrfx4u01
File 2:http://www.mediafire.com/?fymdv9e9kmj332s
File 3:http://www.mediafire.com/?w33k205ej4fpbcl
A big thanks to Khanning who was nice enough to walk me through the adb commands and bear with me when I couldn't get adb over usb to work.

This may fix your issues http://forum.xda-developers.com/showpost.php?p=21309379&postcount=50

Can someone help I used this and I installed drivers from the drivers folder fine ....I ran option 1 fine and it said completed but said something about nvflash error make sure drivers are installed ....but on my tablet it said phone update success ....when I try option three to flash image it just stays at nvflash started and goes no further and when I try to install Su it won't connect adb , probably cause adb drivers wouldnt install ....any advice ....device is booting and seems stock ....it did not wipe my files either
Sent from my HTC EVO 3D X515a using XDA App

maek_it_happen said:
Can someone help I used this and I installed drivers from the drivers folder fine ....I ran option 1 fine and it said completed but said something about nvflash error make sure drivers are installed ....but on my tablet it said phone update success ....when I try option three to flash image it just stays at nvflash started and goes no further and when I try to install Su it won't connect adb , probably cause adb drivers wouldnt install ....any advice ....device is booting and seems stock ....it did not wipe my files either
Sent from my HTC EVO 3D X515a using XDA App
Click to expand...
Click to collapse
It means you are not in APX mode. Read the PDF and follow the instructions for installing the APX drivers. This should fix your issues.http://forum.xda-developers.com/show...9&postcount=50

I just completed step 3 flashing the image went fine up to bootloader .bin sent successfully ...then it says
File not found recovery.img
Failed executing command 2147473647 Nverror 0x4
Command failure : create failed
Edit the link u posted is not working and the drivers are installed
Edit 2 I just downloaded ur v2 root tool in ur other thread ....for some reason ur flash me Command actualy went past the recovery img error I was having with this tool .... But yours is flawless
Sent from my HTC EVO 3D X515a using XDA App

maek_it_happen said:
Edit 2 I just downloaded ur v2 root tool in ur other thread ....for some reason ur flash me Command actualy went past the recovery img error I was having with this tool .... But yours is flawless
Click to expand...
Click to collapse
Glad to hear it worked for you.
TD

I recently got this device and looking for a way to root this device without having to roll back to the factory default rom and then having to update again using OTA.
Question, am I in luck, is that at all possible or do I have to really rollback and reinstall everything again?
Thanks!
Sent from my K1 using Tapatalk

Anyone have the root? Megaupload is down forever.

[Q] Rooting Error - Edited mount_ext3.sh

I've been reading all day and I'm confused and looking for some direction.
I have a mostly stock Droid Bionic that had been rooted using the motofail method. All was fine, and then I attempted to make the edit to my mount_ext3.sh file, but must have done something wrong.
At reboot, phone is stuck at the red Moto splash screen.
I thought I could use adb to pull / push the mount_ext3.sh script to edit out my error and put the file back. For some reason I am not able to do this. I believe I have the correct drivers installed, and I am able to see the adb device in my device manager. RSD lite also sees the device when in fastboot mode. But adb devices shows no device.
Can someone tell me if it's possible to use adb to restore this mount_ext3.sh file? I'd prefer to not factory wipe if possible.
Also, I notice that a lot of links and files referenced in rsd restore methods are gone or invalid. Although I have found them elsewhere (such as bionic_minimal_fxz.tar.gz) .. but I'm not sure my best course from here. Seems like the small edit should be easier to un-do. Can I boot from an SD card or mount the /system/ partition some other way?
Thanks, and if this belongs elsewhere, please let me know and I'll move it.
Thanks,
Chris

Are you using the factory cable from Motorola? Also are you using the latest drivers from Motorola? Make sure you using the correct drivers for 32 or 64 bit OSs.

Gosh .. factory cable. I'm not sure .. I have so many cables laying around.
The cable has several sticky labels that say:
Model: DICMUSB / DC1012 ..
Hmm .. this might be from my old Incredible - It has the following model numbers on the cable:
adr6300vw
adr6225vw
adr6226vw
mwp6985
Jimmeny Crickets. Now I can't seem to be able to get the phone to do much of anything. Sheesh .. indicator light on the front is steady white when usb connected. Did I read somewhere that you basically need a full battery for a lot of this stuff? Swell. Guess I'll home and get the wife's battery.

Majority of people's problem's i've noticed was people not using the factory cable. Motorola's cable are different from other manufacture cables as I've found out recently. I've had issues in the past using other cables and usually using the factory cable resolves my issue.
Link to post about motorola cable:
http://forum.xda-developers.com/showthread.php?t=1077414&highlight=motorola+factory+cable

adb
So I am using the correct cable, I believe I have the correct drivers. I've installed the SDK and am using the ADB from the Android platform_tools.
RSD Lite 5.6 recognizes the device as:
Fastboot CDMA_TARGA S
Does that confirm anything (like that I have the correct ADB driver installed) ..
I've tried all the usual adb commands like adb shell, wait-for-device, kill-server/start-server, etc.
I always get
error: device not found
or in the case of adb devices:
I just get an empty set. ARGG! Really frustrated. I can't believe I started all this with a fatfinger on a forever root script edit. I really thought I would be able to adb pull/push the /system/bin/mount_ext3.sh file in a case like this.
Thanks,
Chris

bionic minimal
Does anyone have any recent experience with this bionic_minimal fxz file:
http://forum.xda-developers.com/showthread.php?p=17560174
I wonder if I can flash that and get back?
Thanks,
Chris

I am going to assume you were previously on 902 or 905. You could do SamuraiHL's no dataloss fxz script to 902. Should prevent any data from your internal memory from being wiped: http://www.droidforums.net/forum/mot...ml#post2173723. I believe there used to be a link in there to the original fxz 902 file that prevented your memory from being wiped. Since you can see your phone via RSDLite and not adb.
Btw...i never mentioned to ask but are you booting into AP Fastboot or staying at the splash screen when trying to adb?

Alternate root method for Nexus 6? CF-Auto-Root gives nothing but issues.

I could never get CF-Auto-Root to properly work with my Nexus 5. I could get the script to launch but I always get this error:
downloading 'boot.img'... ERROR: usb_write failed with status e00002ed
FAILED (command write failed (No such file or directory))
I'm now experiencing the same issue with my Nexus 6. I'm convinced it's an issue with my computer, at this point.
With the Nexus 5 on Lollipop the alternate method is simply to flash a modified boot image, flash TWRP, then install the SuperSU zip. I'm looking to see if there is a similar method for the Nexus 6.

Did you unzip the file and make sure you copied the image over to your platform tools with the best file before you run it.

The phone has been in consumers hands for like 2-3 days, why don't you just wait a bit until some early kinks are worked out. I'd say in like 1-2 weeks all these root, etc issues will be much more seemless.

Pilz said:
Did you unzip the file and make sure you copied the image over to your platform tools with the best file before you run it.
Click to expand...
Click to collapse
Yeah. I moved it to the folder where I put all the factory images when I flash those without issue. I just tried throwing it into the platform tools folder under sdk and get the following error:
... INFODevice already unlocked!
FAILED (remote failure)
cannot load 'image/CF-Auto-Root-shamu-shamu-nexus6.img'
I've been using fastboot commands forever but am beyond frustrated that I cannot figure this out.
eep2378 said:
The phone has been in consumers hands for like 2-3 days, why don't you just wait a bit until some early kinks are worked out. I'd say in like 1-2 weeks all these root, etc issues will be much more seemless.
Click to expand...
Click to collapse
Very true. I'll just enjoy the phone for now and wait it out.

That's weird I had no issues with the bat file. You could flash the image and then su from what I remember and that should work

Pilz said:
That's weird I had no issues with the bat file. You could flash the image and then su from what I remember and that should work
Click to expand...
Click to collapse
think that's essentially what I did on the Nexus 5. I'll give that a try.
EDIT: is SuperSU 2.16 the latest that is in the Auto Root for the Nexus 6?

sn0warmy said:
think that's essentially what I did on the Nexus 5. I'll give that a try.
EDIT: is SuperSU 2.16 the latest that is in the Auto Root for the Nexus 6?
Click to expand...
Click to collapse
2.27 is the latest beta and is a significant change since it doesn't patch the kernel. However it is a BETA and not 100% stable...but I think Chainfire will release it fairly soon (next few days).

Try the toolkit. ??

nexus6R3plicant said:
Try the toolkit. ??
Click to expand...
Click to collapse
The toolkit doesn't work on a Mac. I'm just gonna hold off a bit longer. The only real reasons I want to root is to adjust DPI and adjust gamma settings. Aside from that I'm loving the phone so I'm not in a huge hurry.

sn0warmy said:
The toolkit doesn't work on a Mac. I'm just gonna hold off a bit longer. The only real reasons I want to root is to adjust DPI and adjust gamma settings. Aside from that I'm loving the phone so I'm not in a huge hurry.
Click to expand...
Click to collapse
Download a mint or ubuntu Linux and put it on a usb stick and boot into it but don't install unless you want it ....install adb and fastboot etc and you're good to go

nexus6R3plicant said:
Download a mint or ubuntu Linux and put it on a usb stick and boot into it but don't install unless you want it ....install adb and fastboot etc and you're good to go
Click to expand...
Click to collapse
WAY to much work to simply root the phone. :laugh:
When I get some more time I'll just flash the modified boot image, flash TWRP recovery and install SuperSU (once it's out of beta). That should do the trick.

sn0warmy said:
WAY to much work to simply root the phone. :laugh:
When I get some more time I'll just flash the modified boot image, flash TWRP recovery and install SuperSU (once it's out of beta). That should do the trick.
Click to expand...
Click to collapse
Why not just pull the image file and fastboot-mac binary from the zip and run this in the terminal.
Code:
fastboot-mac boot <image>.img
Where <image> is the name of the image file.
Should work as long as they are in the same directory.

Wugs nexus root toolkit is updated and works fine

I gave in and installed Parallels back on my Mac and used Wug's toolkit, which worked perfectly. I typically hate using toolkits because I think it's best to always know ADB and Fastboot commands. But in this case, it did the job for me.
Thanks guys!

sn0warmy said:
Yeah. I moved it to the folder where I put all the factory images when I flash those without issue. I just tried throwing it into the platform tools folder under sdk and get the following error:
... INFODevice already unlocked!
FAILED (remote failure)
cannot load 'image/CF-Auto-Root-shamu-shamu-nexus6.img'
I've been using fastboot commands forever but am beyond frustrated that I cannot figure this out.
Very true. I'll just enjoy the phone for now and wait it out.
Click to expand...
Click to collapse
Did you get a fix for this issue?
I'm getting the same error.
I unlocked my bootloader by running a separate command. do i need to relock the bootloader and run the script again.
I hate to lose all of my info

I found the issue to the error:
... INFODevice already unlocked!
FAILED (remote failure)
cannot load 'image/CF-Auto-Root-shamu-shamu-nexus6.img'
Looking at the errors and in the script, the script is looking for the a specific folder structure.
After extracting the chainfire package as instructed, I created two folders that I needed (your folder may differ).
I'm using Ubuntu should work for any other linux.
May work for window, but i don't know.
Folder structure is such, my folders are on my desktop ubuntu.
~/Desktop/Nexus6/tools
here should be the fastboot-linux file that is part of the package
~/Desktop/Nexus6/image
here put the CF-Auto-Root-shamu-shamu-nexus6.img file for rooting
~/Desktop/Nexus6
here should be the script root-linux.sh
I ran the script and now have root no issues with any errors.

Fixing CF-Auto-Root for the Nexus 6

tl;dr Use the fastboot executable that comes with adb-tools instead of the one that comes with CF-Auto-Root
I decided to upgrade the N6 to Marshmallow today, and everything was going smoothly until I tried to regain root with CF-Auto-Root. Every time I ran the .bat file I got he error:
Code:
...
We will now attempt to boot CF-Auto-Root. You should see a red Android on the
screen of your device in a minute, with scrolling white text on top of it.
downloading 'boot.img'...
FAILED (command write failed (Unknown error))
finished. total time: 5.004s
...
I hunted around google for a bit but couldn't find any real answer. I opened the .bat file to see what it was doing and maybe try to pinpoint the command that was failing. I saw that it was calling the fastboot that came in the CF-AutoRoot zip (tools\fastboot-windows.exe) On a hunch I copied in the fastboot.exe I had from adb-tools into the CF-AutoRoot directory, and changed all references of 'tools\fastboot-windows.exe' to 'fastboot.exe' in the .bat file.
I ran the .bat file again, and everything worked as it should. Booted into the OS and had root again.
Hopefully this can help someone in the future!

even better.. don't use toolkits to root, especially when you are not knowing much about the processes. learn to do it properly. its easier than using the toolkit for sure, and faster. if you know what you are doing already, then its fine to use a toolkit. but if you are clueless(like most that use toolkits), then learn the right way first, because toolkits mess up, and often.

I have run into the same error while attempting CF Auto Root on my 3 day old Nexus 6. I dont know exactly how to move my fastboot.exe into the windows bat file but I am pretty sure I can figure it out with some reading and research. I agree with simms22 as well. I dont like using toolkits because I dont know what the toolkit is doing when it executes. I would rather perform the steps myself so I have a better understanding of what is happening during the process. I have a good understanding of adb and fastboot even though I am new to the Nexus 6. I am not new to Android though. @CleanSanchez, if there is any information you wouldnt mind passing on about how you modified the bat file I would appreciate it. Thanks for the quick little guide. I will get it figured out for sure. It may just take some time and some research. Thats all I have been doing for the first 3 days I have owned the device. I have read post after post and forum after forum here on XDA. I dont mind being a noob when it comes to a new device but Ill be damned if Im gonna make noob mistakes by getting in a hurry.
Edit:
I followed @CleanSanchez quick guide in the OP and wouldnt ya know, it worked for me too. I read a short Microsoft guide about editing Windows batch files and gave it a shot and it worked like a charm. Thanks for the guide.

Rename the fastboot.exe is a bit easier than editing the bat. Thanks for the guide

Some clarification for anyone needing more details.
Copy the fastboot.exe. file in the tools folder, into the zip CF-Auto-Root-shamu-shamu-nexus6.
Right click on the root-windows file and then click edit.
Change all 'tools\fastboot-windows.exe' to 'fastboot.exe' should be 6 lines of changes needed to be made
Make sure your Nexus 6 is in the bootloader
Click on fastboot.exe to root your phone
I must thank you @CleanSanchez because I got this phone a couple of days ago and this is only guide that actually worked. Hours spent got me continuously failing the fastboot windows. Even though it is years after the fact, you have my thanks.:good: