Develop Bugs

[Q] Need Assistance, I brick my Galaxy Nexus

Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!

So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?

cbs2002 said:
Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!
Click to expand...
Click to collapse
The key piece of information for your symptom is in this line:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
The other lines do help provide background as to the other modes such as recovery and download working properly, which indicates the issue is not *serious*.
The symptom you state, where the device does not boot past the boot logo, usually means the device is not able to boot the kernel or boot past the kernel. The boot logo appears while the kernel is being loaded on the device. Generally, after the boot logo and kernel finish loading a boot animation appears which indicates the kernel has usually handed off to the Android OS to continue booting.
My approach would be to load a completely stock ROM in order to restore a working kernel and ROM to the device. I generally perform this step as a baseline to get everything back in working order.
In many instances the ROM is dependent on the kernel. Your situation requires at least a kernel to be loaded and in order to prevent any further issues, it would be best to load a ROM dependent on the kernel being loaded.
A simple way would be to grab the stock factory images from Google's site and load those back onto the device.
Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode.
Hope that helps!

Since you're rooted I'm going to assume you have ADB and the necessary drivers installed.
1.) Download a ROM. It doesn't have to be stock, you can choose any of the ROMs from the development section for your device. Most of the ROMs are packaged with a kernel already.
2.) Save this ROM file to the same folder where you have ADB installed.
3.) Boot your phone into CWM recovery and plug it into your computer.
4.) Use ADB to push the ROM zip file to your phone (/data/media). For example:
Code:
c:\gnex\>adb push rom.zip /data/media/rom.zip
5.) Use CWM to wipe data, cache, and davlik-cache
6.) Install zip from sdcard and flash the rom.zip.

RMarkwald said:
So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?
Click to expand...
Click to collapse
1. I am using GSM
2. Whenever I turn on my mobile, the 'Google' and 'Unlock' logo appears and then freeze, with no more respond at all
* I definitely mess up some system files, but don't know how to restore it because my PC do not recognize my mobile.
Thanks

I am seeing more and more of these threads about "bricked" nexus's is this an issue with how new the phone is or people not following instructions properly as they are too eager to root their phones?
All else fails flash back to stock and count yourself lucky.

To silow,
Thanks for your advice, but fail
1. I put adb.exe, adbwinapi.dll and fastboot.exe (3 files) under my PC C drive (i.e. C
2. I also put a stock Rom (rename as rom.zip) under C drive (i.e. C
3. Boot phone into CWM recovery and plug it into computer.
4. Use cmd command and type c:\gnex\>adb push rom.zip /data/media/rom.zip
5. It fails , It say "Access Denied" (in Chinese, but I translate it into English here)
6. How do I use ADB (it is a ADB.exe file, When I double click it, it only flash up a few page very fast and nothing happen)
Please assist!

To Joeykrim,
I agree that
"Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode."
But how? (according to my symptoms)

The command I gave you was just an example. I didn't spell out the exact details because I thought that you would know how to do it considering you rooted the phone.
If you put the adb.exe and AdbWinApi.dll file in your C: drive, make sure you copy the ROM file to your C: drive too. In the follow example I'm going to use "ROM.zip" but use the name of the ROM file that you downloaded. Also I am assuming you are on Windows XP.
1.) Boot your phone into CWM recovery and then plug it in.
2.) Go to your Start Menu and choose Run. Then type in "cmd" without quotes and hit enter to open a command prompt.
3.) Enter:
Code:
cd c:\
4.) Enter the following to make sure ADB can see your phone:
Code:
adb devices
You should see something similiar to this to confirm ADB can see your device:
List of devices attached
019B756F0C018012 device
5.) Enter the following command to copy the ROM file to your phone. Remember to replace ROM.zip with whatever the name of the ROM file is:
Code:
adb push ROM.zip /data/media/ROM.zip
6.) Use CWM to wipe data, cache, and davlik-cache
7.) Install zip from sdcard and flash the rom.zip.

To Silow,
You have been very helpful, but I fail.
"You should see something similiar to this to confirm ADB can see your device:
List of devices attached"
There is NO device number shown after the phrase 'List of devices attached'
To recap:
a) Phone is already plugged in my PC, under the Clockworkmod Recovery 5.5.0.2
b) adb.exe and AdbWinApi.dll file are under C: drive directly
c) Also type cmd in 'Run', a black Dos window shown C:\windows\system32\cmd.exe
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Pls don't give up on me!
: )

you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot (edit: wrong!)

Sounds like your ADB USB drivers are not correctly installed. While the phone is under CWM, when you plug it in is your computer attempting to install drivers for a new device?
Download these bare ADB Interface drivers.ADB USB Drivers
Go into Device Manager on your computer and check the device list for any unknown devices or "?" devices. If you need to update those drivers by pointing them to the drivers you downloaded and extracted from that link above.
When the ADB Interface drivers are correctly installed you should see Android Phone listed under under your Device Manager when it's plugged in with CWM recovery loaded.
---------- Post added at 02:36 PM ---------- Previous post was at 02:35 PM ----------
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.

silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
edit: i did appear to have one missing driver, my mistake. it was listed in device manager as "unknown - full"
its funny cause i never had to use adb from cwm before, never noticed

cbs2002 said:
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Click to expand...
Click to collapse
This symptom generally occurs from not having loaded the drivers for the hardware. As with the majority of hardware devices when being connected to a Windows machine, the drivers need to be loaded. Sometimes these are automatically loaded and other times they have to be manual loaded.
As an alternative and for future reference, the android-sdk package contains general USB drives which usually work for Google Nexus devices.
Generally, as this providers a *cleaner* install, best practice as recommended by Google is to download the whole android-sdk .zip and then from the installer download/install the pieces needed, such as platform-tools (containing adb) and USB drivers as opposed to extracting out the adb.exe and .dll file and installing manually.
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
Agreed. To add greater clarification so there is no confusion: adb can't be used from the bootloader.
The /sbin/adbd daemon on the device is only loaded while in normal android boot mode or in recovery mode as called by the init.rc (or on some older devices, recovery.rc) file in the boot process.
Bootloader mode will only work with fastboot while it is in fastboot usb mode.
On some devices, the bootloader has a separate menu for fastboot and on other devices, the fastboot mode is directly entered when entering the bootloader.
Hope that helps clarify!

To silow (and all other helpers)
1. I fail
2. The ADB USB drivers in my PC should be fine as in Device Manager , I can see Android Phone with Android Composite ADB Interface. (No exclamation mark)
3. On the other hand, whenever I plug my mobile into PC, I can see "Unknown-Full"
4. In DOS, when I first type "adb devices" it shows
* daemon not running. starting it now on port 5037*
*daemon started successfully *
List of devices attached
(but NO device number shown!)
5. When I enter adb devices second time, it shows
List of devices attached (No device number shown)
Thank you so much , but it is Hong Kong time (my place) at 0511 am , I didn't sleep all night and I am very tired.
If you don't mind (especially big helper Silow), please give me email so that I capture screen picture and show you in detail (hope it may help)
my email is
[email protected]
I need to sleep now, I will check my email and see you guys or come back this Forum later (several hours later, as I really need some sleep right now)
Pls don't give up on me as this is an expensive mobile. I think the hardware is fine, just need to figure out a way to unbrick it.
Thanks, and see you!

What you need to do is right click on "Unknown-Full" and click on "Update Driver...". Then choose "Install from a list or specific location". Make sure "Search for the best driver in these locations." is checked and "Include this location in the search:" is check. Click on the Browse button and browse to where you extracted the driver files from the link I posted above. Click Next and this should install the correct drivers for you. Afterwards try "adb devices" again to see if ADB now reconizes your device.

To Silow,
Fail.
1. Already installed the drivers you gave me (and there is no 'Exclamation' Mark) in Device manager
2. Situation is the same , Cannot recognize my mobile (i.e. no Device No. after entering adb devices)
3. "List of devices attached" shown in DOS video but without any number.
No other method?
My mobile is really 'bricked' to death?

To Silow and all,
Something important
1. When choose 'install zip from sd card' under CWM, a list of old folder names remains
(e..g gameloft, DCIM, Pictures, etc). That means almost all old files, folders are STILL in my mobile!
2. I have already use the funcion 'Wipe data/factory reset', 'wipe cache partition', ' Wipe Dalvik Cache'
Perhaps my CWM has problem?

What happens when you update drivers for Unknown-Full?
Boot into fastboot and see if your computer recognizes the phone by checking device manager. The key here is to get your computer to see the phone either in fastboot or CWM.
Perhaps try another cable, USB port, or new computer.
The goal is to get Android Phone ADB Composite Interface to show up in device manager either in Fastboot or CWM. Without that done you cannot use Fastboot to flash nor ADB to push a zip file to the phone.
Sent from my Galaxy Nexus using XDA App

[Q] ADB recognizes device but not in recovery

Hi! I want to update my girlfriend's GNex by pushing update via recovery. I have adb working and recognizing device when it's turned on (with debugging mode). But when I go to recovery (adb reboot recovery), I can't get my device recognized again - "adb devices" shows nothing. I figured it can't be problem with drivers (since the device is recognized when turned on?), I must be doing something else wrong? But I have no idea where to look.
Sorry for the (probably) common question, but all I've found (using search) is adb not recognizing devices at all. I've been only using "fastboot" commands so far, and I never had problems with recognizing.

Joplisan said:
Hi! I want to update my girlfriend's GNex by pushing update via recovery. I have adb working and recognizing device when it's turned on (with debugging mode). But when I go to recovery (adb reboot recovery), I can't get my device recognized again - "adb devices" shows nothing. I figured it can't be problem with drivers (since the device is recognized when turned on?), I must be doing something else wrong? But I have no idea where to look.
Sorry for the (probably) common question, but all I've found (using search) is adb not recognizing devices at all. I've been only using "fastboot" commands so far, and I never had problems with recognizing.
Click to expand...
Click to collapse
what recovery are you using? in twrp, in advanced menu, theres a adb sideload option.

The problem is that her phone is locked, everything is stock. The only option is adb sideload (as far as I know). Any suggestions? I really don't have a clue.
Sent from my Galaxy Nexus using my thumbs.

Stock recovery does not offer the ADB interface, so adb commands will not work. You need to flash a custom recovery such as CWM or TWRP.

Ahhh, I didn't know that. I guess I have to wait for the ota, then, since I can't flash or use custom recovery. Thank you for your help!
Sent from my Galaxy Nexus using my thumbs.

Actually you can use adb commands in stock recovery - this works on build number JRN84D and newer only (JRN84D corresponds to 4.1, the first Jelly Bean build).
1) Reboot your device into the stock recovery (i.e., the screen with the Android on its back with the "!");
2) Access the stock recovery menu by pressing power and volume up;
3) Select "Apply update from ADB";
4) Download the correct update for your build and place it in the same directory as your ADB binary;
5) Open a command prompt in the same directory as your ADB binary;
6) Type adb devices to make sure that your device is recognized;
7) Type adb sideload name-of-file.zip
8) Reboot. Done.
Click to expand...
Click to collapse
This is from Method 4 in http://forum.xda-developers.com/showthread.php?t=1419170
Hope this helped

[Q] adb/fastboot can't find device in bootloader, but they can do it when booted

Dear all,
I have worked on building Android from source code for few weeks. It used to be fine to me with my galaxy nexus, I can connect to my device via adb and fastboot and flash either the factory ROM or ROM built by me into my device. However, when updating the phone into 4.3, I forgot to extract drivers into the built directory and flash the built image into my device. Is surely can't work, and the screen turn off once "Google" is shown, so I would like to reflash it back to other image. However, my laptop can't recognize my Nexus S anymore in the bootloader. I can use "adb shell" once the device is normally booted (even without screen), but once I type "adb reboot bootloader", the connection is lost! Both "adb and fastboot devices" show nothing....
I have searched the forum and stackoverflow all day but can't find helpful information. There are many threads talking about unable to connect devices but 70% of them are driver-related issue and 30% of them, ex: sudo adb, just don't work for me. I think I am not facing the driver issue because I still can use "adb shell" once the device is normally booted (not in bootloader mode). Moreover, I also tried few debrick tools contributed by xda community but with no luck.
I am wondering if there is any way that I can reflash image to my device without accessing it in bootloader mode? (ex: push image in to device via adb shell when device is normally booted?). I am also wondering if there is any way to fix this problem. Any suggestion is very appreciated!: crying:
Thanks
Yu-Chih
ps. the most closed thread I found is called "ADB can discover devices but not fastboot" in stackexchange (I am not allowed to post the link)
but it seems there is no answer in this thread

I'm not a expert, but do you know how is the DD command ?,
I wonder, is you can DD the boot loader into the nexus partition?

chongns said:
I'm not a expert, but do you know how is the DD command ?,
I wonder, is you can DD the boot loader into the nexus partition?
Click to expand...
Click to collapse
Thanks for the reply. I am not sure what I should do with dd command? Could I use it to reinstall the drivers into device?
by the way, I found there is a error showing up in the bottom of screen in fastboot mode, "Fastboot Command Read Error -2147483647", and many closed threads (sorry that I am not allowed to post url because I am new). Some suggests are to reinstall drivers (even thought I don't get if they mean reinstall the usb driver for laptop or for android), but it seems not solved yet.
Yu-Chih

Dear all, I think I have tried all potential solution about "fastboot command read error -2147483647" that I can find at internet......
Here is what solution I have tried:
1. sudo the command of adb and fastboot
2. update drivers
3. update sdk
4. use another cable
5. install other drivers (win7), ex: naked driver
6. Wug's root kit
What I can't try:
1. enable USB debug mode at phone (because I don't have screen of it but only adb shell)
2. remove(uninstall) other software such as PDA net...etc (I don't try this because my system is clean-installed win7/MAC/ubuntu)
I think this problem is kind of common but my situation seems slightly different from others, that I can find the device when my device is normally booted but I can't recognize it when it is rebooted into bootloader (showing "fastboot command read error -2147483647" at bottom). I am starting to believe it either be the problem that I don't activate the USB debugging in my new flashed image (but I can connect it with adb when the device is normalled booted) or the usb driver in my device is broken.
Anyone has any idea.....:crying:
eddyxdxda said:
Thanks for the reply. I am not sure what I should do with dd command? Could I use it to reinstall the drivers into device?
by the way, I found there is a error showing up in the bottom of screen in fastboot mode, "Fastboot Command Read Error -2147483647", and many closed threads (sorry that I am not allowed to post url because I am new). Some suggests are to reinstall drivers (even thought I don't get if they mean reinstall the usb driver for laptop or for android), but it seems not solved yet.
Yu-Chih
Click to expand...
Click to collapse

Dear all,
This is my latest update. I wipe out the whole system of Ubuntu and Win7 and restart everything from the first step. Magically, the new Win7 + Wug's root kit can successfully flash new image into my phone. But also magically, the ubuntu system faces the same issue as I described (no connection in bootloader with the error code but connection is fine after the device is booted). The bright side of this is that I am finally able to try other solutions, e.g., enabling debugging mode, but the sad part is that I still get no luck at Ubuntu and MAC.........can't believe it works at Win7 but not at Ubuntu and MAC.....
Yu-Chih
eddyxdxda said:
Dear all, I think I have tried all potential solution about "fastboot command read error -2147483647" that I can find at internet......
Here is what solution I have tried:
1. sudo the command of adb and fastboot
2. update drivers
3. update sdk
4. use another cable
5. install other drivers (win7), ex: naked driver
6. Wug's root kit
What I can't try:
1. enable USB debug mode at phone (because I don't have screen of it but only adb shell)
2. remove(uninstall) other software such as PDA net...etc (I don't try this because my system is clean-installed win7/MAC/ubuntu)
I think this problem is kind of common but my situation seems slightly different from others, that I can find the device when my device is normally booted but I can't recognize it when it is rebooted into bootloader (showing "fastboot command read error -2147483647" at bottom). I am starting to believe it either be the problem that I don't activate the USB debugging in my new flashed image (but I can connect it with adb when the device is normalled booted) or the usb driver in my device is broken.
Anyone has any idea.....:crying:
Click to expand...
Click to collapse

[Q] MTP USB Device: ADB lists no devices

Hi guys.
The phone is Xperia S.
I have installed CWM and wiped all partitions (except for sdcard) in order to prepare the phone for CM12.1 install.
Now I understand that my CWM version is outdated (5.5.0.4) and I need to install TWRP (which I had had installed before).
The problem is that when I plug in the phone, Windows registers it as MTP USB Device and I cannot uninstall/change drivers. adb devices lists no devices and I cannot do anything with the phone now.
Also, I have twrp.img on sdcard, but I'm not sure how to install it from CWM. When I was running TWRP before, adb was working fine.
So, I guess my problem can be fixed in two ways:
Install TWRP from CWM. I have twrp.img on sdcard, but CWM won't let me install it, I can't see it listed in file list.
Uninstall/change drivers for "MTP USB Device" so that adb works again.
Any help would be appreciated, as I cannot install anything on my phone now, and all I have is a CWM recovery on it.

Witchunter said:
Hi guys.
The phone is Xperia S.
I have installed CWM and wiped all partitions (except for sdcard) in order to prepare the phone for CM12.1 install.
Now I understand that my CWM version is outdated (5.5.0.4) and I need to install TWRP (which I had had installed before).
The problem is that when I plug in the phone, Windows registers it as MTP USB Device and I cannot uninstall/change drivers. adb devices lists no devices and I cannot do anything with the phone now.
Also, I have twrp.img on sdcard, but I'm not sure how to install it from CWM. When I was running TWRP before, adb was working fine.
So, I guess my problem can be fixed in two ways:
Install TWRP from CWM. I have twrp.img on sdcard, but CWM won't let me install it, I can't see it listed in file list.
Uninstall/change drivers for "MTP USB Device" so that adb works again.
Any help would be appreciated, as I cannot install anything on my phone now, and all I have is a CWM recovery on it.
Click to expand...
Click to collapse
The MTP is fine, You don't need to uninstall it. Try following the method from here to flash the ROM.

Mirhawk said:
The MTP is fine, You don't need to uninstall it. Try following the method from here to flash the ROM.
Click to expand...
Click to collapse
Thanks for the suggestion.
When I turn off the phone, press and hold UP button and then connect the phone to PC, the blue light lights up as it should. However, after ~10 seconds, blue light goes away and the phone goes to CWM recovery.
Therefore, I'm unable to execute adb commands during this short time period.
How to prevent CWM from starting up while in fastboot mode?

Witchunter said:
Thanks for the suggestion.
When I turn off the phone, press and hold UP button and then connect the phone to PC, the blue light lights up as it should. However, after ~10 seconds, blue light goes away and the phone goes to CWM recovery.
Therefore, I'm unable to execute adb commands during this short time period.
How to prevent CWM from starting up while in fastboot mode?
Click to expand...
Click to collapse
Then Your fastboot drivers are not installed.
Disconnect Your phone from PC.
Open command prompt and run this command:
Code:
SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
and then open device manager, Choose View, Show Hidden Devices. Then uninstall any device with Xperia S and/or android in it. Then install the flashtool, fastboot, and every Xperia S related drivers from drivers pack in flashtool. I see that You use Windows 8/8.1, hence You need to follow a different method to install drivers. You can find that method here. Then follow the method I mentioned before.

Mirhawk said:
Then Your fastboot drivers are not installed.
Disconnect Your phone from PC.
Open command prompt and run this command:
Code:
SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
and then open device manager, Choose View, Show Hidden Devices. Then uninstall any device with Xperia S and/or android in it. Then install the flashtool, fastboot, and every Xperia S related drivers from drivers pack in flashtool. I see that You use Windows 8/8.1, hence You need to follow a different method to install drivers. You can find that method here. Then follow the method I mentioned before.
Click to expand...
Click to collapse
While waiting for your answer, I found the video detailing instructions to install drivers on Windows 8.1 x64:
Nonetheless, thank you for your answer, now I can continue to try to install CM12.1.

Fastboot interface is missing. Help!

On Device Manager (Window 10). Were updating the driver, I can only see ADB interface but no Fastboot interface. I'm on the latest version SDK from Google and have OnePlus driver installed. I can command ADB but not fastboot. What am I missing? My device is OnePlus 7T TMobile is sim unlocked and I can toggle OEM unlocking and is on.

Not sure what mean, but fastboot only works when you're booted in bootloader. (Adb reboot bootloader)
Sent from my OnePlus7TPro using XDA Labs

That's correct but when I fastboot cmd it get stuck on "waiting for device". So I read around on XDA on how to fix it and I tried to follow the instruction on PC - device manager, still no go.

PesTicide. said:
That's correct but when I fastboot cmd it get stuck on "waiting for device". So I read around on XDA on how to fix it and I tried to follow the instruction on PC - device manager, still no go.
Click to expand...
Click to collapse
I myself have never had this problem, I can only suggestion reinstalling OnePlus drivers.
Hopefully you figure this out
Sent from my OnePlus7TPro using XDA Labs

I reinstalled couple of times. Still no go! This is the first time that this happening. Never had problem since day one on Nexus devices. I'm going to try again and search more around.

You can also use the universal drivers by clockworkmod https://adb.clockworkmod.com/
Here's what I did.
1) Extract the android sdk platform tools and put on your c:// drive
2) Install the universal usb drivers
3) Enable usb debugging on your one plus and connect to computer. Switch to usb debugging mode and accept the popup on your one plus to allow the connection.
4) Open cmd and run "cd C:\platform-tools", then run "adb devices" to ensure that your devices is connected properly
5) Run "reboot bootloader" and device will restart into bootloader mode and fastboot will now work
*This is all assuming that you've already oem unlocked your devices as well already*

It work till fastboot. Still stuck at "waiting for device".

PesTicide. said:
It work till fastboot. Still stuck at "waiting for device".
Click to expand...
Click to collapse
Are you trying to open? Command shell? In windows 10 right? So for your information in windows 10 it's not supported , you have to open that platform tool folder which you installed already named as adb, platform tools , sdk may go into that folder and you will see a folders directory above there .. just click on that and type cmd and hit enter and cmd will pop up now you can use all your commands it's not your fault it's windows 10 fault ..maybe hope it may work for you

That how I done it. Fastboot Command appear on my Google Pixel 2 and 3 but I can't do it on my 7T. I don't get it
Thanks for the help! I tried working on Device Manager on PC yet doesn't work. Adb shell command work but no Fastboot command.

I found the solution! This is what I did and it worked for me! Here's the link for anyone who has the same issue I went through. Here you go and follow the instruction. http://www.wtfandroid.com/fix-fastboot-device-not-recognised-problem/
Mod you can close this thread. Thanks again for everyone who tried to help me. :highfive: