Database Users

adb when fully booted in 2.1

Quick and possibly stupid question but is adb accessible in 2.1 when fully booted? I know in 1.5 it was but I can't seem to do it in 2.1 unless i'm in recovery.

cali310 said:
Quick and possibly stupid question but is adb accessible in 2.1 when fully booted? I know in 1.5 it was but I can't seem to do it in 2.1 unless i'm in recovery.
Click to expand...
Click to collapse
I'm far from an expert, but with USB debugging enabled I can adb to my phone with it fully booted...in fact, that's how I rooted it, lol.
I might be missing something though...like I said, I'm pretty much a newb.

cali310 said:
Quick and possibly stupid question but is adb accessible in 2.1 when fully booted? I know in 1.5 it was but I can't seem to do it in 2.1 unless i'm in recovery.
Click to expand...
Click to collapse
No problems here doing it.

You have to be connected using the choice HTC Sync when you plug the phone in. Then you have to wait a few seconds and then you should be able to use ADB

Leukay said:
You have to be connected using the choice HTC Sync when you plug the phone in. Then you have to wait a few seconds and then you should be able to use ADB
Click to expand...
Click to collapse
Actually the trick is NOT using htc sync. HTC sync also uses adb and you can't have multiple adb connections. So if you have htc sync running on your computer (even if you aren't currently connected to it) it's holding a connection to your phone and will prevent command line adb from working properly.

I tried all 4 settings when USB is connected and no luck w/ any of them.

cali310 said:
I tried all 4 settings when USB is connected and no luck w/ any of them.
Click to expand...
Click to collapse
Can you tell us what adb is telling you? To answer your original post... adb works perfectly fine in all flavors of 2.1. So there is something else going on.

That's the thing. It's not showing the device. If I do an adb devices it's not showing up unless i'm in recovery. Same thing when using fresh kitchen. I tried using it the other day to wipe the lock screen cache to install the invis one and that's when I discovered the prob.

That's the thing. The device isn't showing up. If I do an "adb devices" I get nothing unless i'm in recovery. Same thing w/ fresh kitchen. I went to use it the other day to wipe my lock screen cache and that's when I discovered the prob. It worked in recovery too.

Sounds like you are missing drivers. Are you running Win 7 by any chance?
Anyways, try this, it should help. Download PDAnet (google it for link) and install it. This will install correct drivers for you . Then it should work.

ccapasso said:
Sounds like you are missing drivers. Are you running Win 7 by any chance?
Anyways, try this, it should help. Download PDAnet (google it for link) and install it. This will install correct drivers for you . Then it should work.
Click to expand...
Click to collapse
I already have PDANet installed. It is the 1.12 version if that makes a difference. And yes, i'm running Win 7 64 bit. It was working fine w/ 1.5 so I don't think it's a driver issue.

This worked for me as well.....
jackal424 said:
I had a similar problem. I use Windows 7 Pro 64bit.
Here is what helped fix the issue:
http://www.mydigitallife.info/2009/08/24/workaround-for-htc-hero-sync-problem-in-windows-7/
Click to expand...
Click to collapse

I'm using linux, and I used linux to root both of our Heros. Now, in linux I can't communicate with the phone through adb. It just doesn't see the phone. On the same computer I boot into windows and adb works fine.
What could be causing this?

One time, I had a bad USB cable. Only charged, and made no USB connection whatsoever (ADB, sdcard mount, etc.)

Before I mess w/ htcsync does one of the hero gurus around here think it is worth trying? As I said before I have no probs with adb in 1.5 when fully booted nor do I have a prob w/ it when in recovery (both 1.5 and 2.1) so I wouldn't think it's a driver issue. If i'm wrong let me know.
Also, which of the 4 USB settings do you select when the phone is plugged into the pc?

I had the exact same issue. I blogged about it here so I could show screenshots in context
http://sprintherotips.blogspot.com/2010/03/pc-connection-issue-windows-7-ultimate.html

cali310 said:
Before I mess w/ htcsync does one of the hero gurus around here think it is worth trying? As I said before I have no probs with adb in 1.5 when fully booted nor do I have a prob w/ it when in recovery (both 1.5 and 2.1) so I wouldn't think it's a driver issue. If i'm wrong let me know.
Also, which of the 4 USB settings do you select when the phone is plugged into the pc?
Click to expand...
Click to collapse
charge only.

Updated the drivers and the sdk and now I can adb in. Thanks a lot ro_bro and everyone else. It only works for me in htcsync mode. It searches for htcsync for like 30 secs then lets me cancel. Charge only doesn't work. I assume something else is screwed up.

I need help restoring my phone - odin wont flash it

Background is, I was flashing JAC's latest kernel onto my phone, which I had done twice before. Unfortunately, ODIN was getting stuck at zimage. After trying a few times, I decided to go back to the version of the kernel I was running previously, which I knew worked. I tried to flash the kernel but odin kept getting stuck on zimage again.
I tried restarting the computer, battery pulls on the phone, different usb ports and nothing has worked.
In desperation I tried to flash the stock firmware back, but ODIN gets stuck at cache.rfs.
Did I brick my phone?

Which version of windows are you using? Try from a different computer.

the3dman13 said:
Which version of windows are you using? Try from a different computer.
Click to expand...
Click to collapse
Windows 7 32bit. I've also tried a computer running xp home.
My main pc runs windows 7 64 bit, but odin doesn't work on it, even in compatibility mode.
The phone is f'ed. Im going into the tmo store this morning, I hope they dont give me a hard time.

ArbitrageMan said:
My main pc runs windows 7 64 bit, but odin doesn't work on it, even in compatibility mode.
Click to expand...
Click to collapse
BS! Heh, I restored my phone using ODIN flasher. I have windows 7 64 bit. I don't have to do anything special, just followed directions and it worked. Make sure you have 64 bit Samsung Drivers.

zaduma said:
BS! Heh, I restored my phone using ODIN flasher. I have windows 7 64 bit. I don't have to do anything special, just followed directions and it worked. Make sure you have 64 bit Samsung Drivers.
Click to expand...
Click to collapse
Done. The phone is detected by odin in 7 - 64, but when I try to flash, odin throws up a couple of messages in chinese and then sits there doing nothing. It never starts the flashing process.

hey did you fix your phone...im having the same issue

You guys try flashing anything via clockwork recently? There are recovery images for stock inside the odin thread from jac and stock I images for a kernel in his kernel thread... That's if you can even get into recovery now.....
Pooped from my Samsung Vibrant using XDA app... Dont mind the skidmarks...

on the same boat any other solutions

have you guys tried the toolbox?
http://forum.xda-developers.com/showthread.php?t=954509
Here is another good thread to check out.
http://forum.xda-developers.com/showthread.php?t=1013967

Flag eugenes froyo that doesn't brick. Look it up it will fix it
Sent from my SCH-I500 using XDA App

No idea if this will help, but make sure you are using a later version of Odin (1.7 or above).
Also might try flashing with Heimdall. Works very well in my experience.

RSD LITE not detecting phone

Ok so i was planning to flash my defy with the leaked 2.3.4 gingerbread but when it came time to connect it to the rsdlite, it wasn't detected. The drivers installed fine.
I followed this tutorial:
http://forum.xda-developers.com/showthread.php?p=14976942#post14976942
Things checked:
Bootloader was on when connected
Battery full
I tried multiple methods:
Running RSDLITE with safemode
running rsdlite admin access
installing rsdlite 4.9
installing rsdlite 5.3.1
installing motorola drivers 5.1
installing motorola drivers 5.2
So now i can't flash the shadow4.5.1-134fixed.sbf.
Doing this step:
4. Select “shadow4.5.1-134nandroid” and choose “System Only”
I can't load into my phone to access ClockworkMod Recovery to revert that.
So now when i boot up my phone it is stuck at the motorola symbol.
What i can do:
access bootloader
access recovery module

Pull out battery.
Reinsert battery while holding volume up key.
Phone should say ok to program.
Sent from my MB525 using XDA App

Red should detect then
Sent from my MB525 using XDA App

Tried that and RSDLITE still doesn't detect. I tried installing RSDLITE on a different laptop but same issue.

i have a feeling its because of the 64bit windows 7. Has anyone got it to work on other flavours of windows?

I'm having the same issue.. tried the pulling battery out and back in with volume up with no luck..

any solution?
i'm having the same problem
thanks

Any solution?
I have the same problem. Any help is appreciated. Thanks!

arulshoponline said:
Any solution?
I have the same problem. Any help is appreciated. Thanks!
Click to expand...
Click to collapse
just go to boot loader then connect phone to PC... RSd will detect it...
Sent from my MB526 using xda premium

nogoodusername said:
just go to boot loader then connect phone to PC... RSd will detect it...
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Thanks for your reply. I was also trying to connect USB when phone is on boot loader. Even computer itself does not recognize the phone.

try using another version of rsd
Sent from my MB526 using xda premium

Yeah my solution was that i installed windows XP on the same laptop, installed the same version of rsd lite and it was detected. I don't think you have to do something that strenuous but you could try installing a different version of rsd lite. I think the latest one is 5.6 and it works in detecting my phone on windows 7 x64.

munky88 said:
Yeah my solution was that i installed windows XP on the same laptop, installed the same version of rsd lite and it was detected. I don't think you have to do something that strenuous but you could try installing a different version of rsd lite. I think the latest one is 5.6 and it works in detecting my phone on windows 7 x64.
Click to expand...
Click to collapse
Thanks for replies. I tried RSD lite 5.6
4.9
4.8
4.6
on windows7 x64. But no luck.
Not only RSD lite, even computer also does not detect the phone. I tried in my laptop also which is running windows7 x64. I will try it in XP also tomorrow.
---------- Post added at 10:17 PM ---------- Previous post was at 10:12 PM ----------
I tried re-installing driver 5.5.0 also.

Check if you have any belkin router software installed. I remember reading on some topic that, the USB monitor of that software was interfering with rsd lite
Sent from my MB526 using XDA

shadenight said:
Check if you have any belkin router software installed. I remember reading on some topic that, the USB monitor of that software was interfering with rsd lite
Sent from my MB526 using XDA
Click to expand...
Click to collapse
Yes, I also read that thread and checked for it. I do not have belkin router software installed.

Sorry to missed this post.
I have the very same problem.
I tried each and every probe googled.
No luck.
Finally I have to install a brand new x86 Windows 7 Ultimate (I think not particularly ultimate, any would do e.g. home, home premium...etc).
To me it is the x86 that hinders me from recognizing the phone.
Sorry, it should be rsdlite not working along with x64 but seemless with x86.
Hope this helps !

kneepain said:
Sorry to missed this post.
I have the very same problem.
I tried each and every probe googled.
No luck.
Finally I have to install a brand new x86 Windows 7 Ultimate (I think not particularly ultimate, any would do e.g. home, home premium...etc).
To me it is the x86 that hinders me from recognizing the phone.
Sorry, it should be rsdlite not working along with x64 but seemless with x86.
Hope this helps !
Click to expand...
Click to collapse
Thanks for the reply. I found this is due to hardware issue. I sent it to service they replaced the board (with Defy+ board). Now it is working good with 2.3.6 defy+ stock ROM. Upgraded to Defy+!

arulshoponline said:
Thanks for the reply. I found this is due to hardware issue. I sent it to service they replaced the board (with Defy+ board). Now it is working good with 2.3.6 defy+ stock ROM. Upgraded to Defy+!
Click to expand...
Click to collapse
arulshoponline, I am suffering with this prob for soo long.. all the forums have been of very little help to me.
First, I rooted my phone and then installed the cyanogen 7.2 mod instead of 7.1 by mistake. Everything was going as instructed by various tutorials.. Then when the device rebooted, it was stuck on the screen showing android & cyanogen mod logo with an arrow going round and round(in blue). It kept repeating itself. Thinking my phone froze, I removed the battery. Upon reboot, it Got stuck at the "Google" image which replaced the original Motorola symbol after the update. Ever since I cannot get RSD Lite to recognize the device even after installing Motorola Helper drivers as well as the phone drivers. I am frustrated and seriously thinking of just getting a professionals help.
Any suggestions anyone?? The SBF file i used is JRDNEM_U3_3.4.3-11_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB03A.0R_PDS03C_USAJRDNFRYORTGB_P010_A007_HWp3_Service1FF.sbf
is this the wrong one?
arulshoponline - Where did you give your phone for service? Did you give it to Moto itself? or some local repair store?
P.S I was initiallly running Froyo 2.2.1 and wanted to upgrade to Gingerbread 2.3.4 when all this happened I am running on Win XP, currently with RSD 5.3. I have tried 4.9 and 5.0 so far.

akira.nev said:
arulshoponline, I am suffering with this prob for soo long.. all the forums have been of very little help to me.
First, I rooted my phone and then installed the cyanogen 7.2 mod instead of 7.1 by mistake. Everything was going as instructed by various tutorials.. Then when the device rebooted, it was stuck on the screen showing android & cyanogen mod logo with an arrow going round and round(in blue). It kept repeating itself. Thinking my phone froze, I removed the battery. Upon reboot, it Got stuck at the "Google" image which replaced the original Motorola symbol after the update. Ever since I cannot get RSD Lite to recognize the device even after installing Motorola Helper drivers as well as the phone drivers. I am frustrated and seriously thinking of just getting a professionals help.
Any suggestions anyone?? The SBF file i used is JRDNEM_U3_3.4.3-11_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB03A.0R_PDS03C_USAJRDNFRYORTGB_P010_A007_HWp3_Service1FF.sbf
is this the wrong one?
arulshoponline - Where did you give your phone for service? Did you give it to Moto itself? or some local repair store?
P.S I was initiallly running Froyo 2.2.1 and wanted to upgrade to Gingerbread 2.3.4 when all this happened I am running on Win XP, currently with RSD 5.3. I have tried 4.9 and 5.0 so far.
Click to expand...
Click to collapse
Sorry for you akira.nev. I also really felt bad when mine went wrong. I gave it to Moto service they also said RSD & computer do not detect the phone and advised to change the board. It cost me 2000INR.
Did your phone get connected with the computer thru USB before flashing cm7?Did you try to flash with RSD from another computer? Do you hear any sound when you plug in your device?
P.S Use the latest RSD. It works seamless in my laptop with Windows7 x64 home basic.

McGuver. Hack works
Sent from my MB525 using Xparent Cyan Tapatalk 2

[Q] usb came unplugged durring sbf flash

My friends purchased a Droid Pro with CM9 already loaded onto it. He asked for my help because he was experiencing bugs and wanted to go back to a stock ROM.
I installed the Motorola drivers.
I put the phone into clockwordmod recovery and cleared all the caches and battery stats.
I then restarted into the Bootloader and started up a current version of RSD lite on my Win7x64 installation.
Next I got the SBF file loaded up in RSD lite and started flashing.
As it was nearing completion I picked up the phone to "catch the boot" and in the process bumped the USB cable just enough to terminate the connection and the process failed.
Now I can't get passed the Bootloader which says Code Corrupt.
I have spent hours upon hours scouring the internet trying different fixes to fix this problem.
Now when I try to flash it again with RSD lite it gets stuck when switching the phone to PB pass through and FAILS with the error 0x70be because it can't find the driver for MDM6600 and my system labels it as an unknown device.
I have since installed WinXPx84 on my system and tried the SBF process over and over in different ways hoping that it will take.
Any insight is greatly appreciated.
Thank you,
PEZ

PEZ Dispenser said:
My friends purchased a Droid Pro with CM9 already loaded onto it. He asked for my help because he was experiencing bugs and wanted to go back to a stock ROM.
I installed the Motorola drivers.
I put the phone into clockwordmod recovery and cleared all the caches and battery stats.
I then restarted into the Bootloader and started up a current version of RSD lite on my Win7x64 installation.
Next I got the SBF file loaded up in RSD lite and started flashing.
As it was nearing completion I picked up the phone to "catch the boot" and in the process bumped the USB cable just enough to terminate the connection and the process failed.
Now I can't get passed the Bootloader which says Code Corrupt.
I have spent hours upon hours scouring the internet trying different fixes to fix this problem.
Now when I try to flash it again with RSD lite it gets stuck when switching the phone to PB pass through and FAILS with the error 0x70be because it can't find the driver for MDM6600 and my system labels it as an unknown device.
I have since installed WinXPx84 on my system and tried the SBF process over and over in different ways hoping that it will take.
Any insight is greatly appreciated.
Thank you,
PEZ
Click to expand...
Click to collapse
Woah woah woah. Windows x84?
Sent from my Nexus 7 using xda app-developers app

BlackFire27 said:
Woah woah woah. Windows x84?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
x84 is just another way of saying 32 bit

I think it is x86. Back on topic. So, try downloading another sbf that is from before 4.7.8 Try sbfing that
Sent from my Amazon Kindle Fire using Tapatalk HD

Vlasp said:
I think it is x86. Back on topic. So, try downloading another sbf that is from before 4.7.8 Try sbfing that
Sent from my Amazon Kindle Fire using Tapatalk HD
Click to expand...
Click to collapse
Ah, my bad, yes x86. Like I said I've spent hours and hours on this and missed some sleep.
I will look into and try other SBFs however I have been having trouble locating good links considering the age of the device. Know of any resources?
What do you mean by 4.7.8? I can't find any information on that. The SBF files that I have tried flashing are 2.26.20 and another one I found for the Droid Pro that is just labeled 3087.sbf

PEZ Dispenser said:
Ah, my bad, yes x86. Like I said I've spent hours and hours on this and missed some sleep.
I will look into and try other SBFs however I have been having trouble locating good links considering the age of the device. Know of any resources?
What do you mean by 4.7.8? I can't find any information on that. The SBF files that I have tried flashing are 2.26.20 and another one I found for the Droid Pro that is just labeled 3087.sbf
Click to expand...
Click to collapse
my bad 4.7.3. Try that one by searching on google.
Sent from my Amazon Kindle Fire using Tapatalk HD

Vlasp said:
I think it is x86. Back on topic. So, try downloading another sbf that is from before 4.7.8 Try sbfing that
Sent from my Amazon Kindle Fire using Tapatalk HD
Click to expand...
Click to collapse
ah, I see, 4.7.8 is the blur version. Downloading 4.6.8 now. Hopefully that works.

Have I permanently bricked a phone for the first time?
Ok, so now I have tried 4.6.8, 4.7.3, 4.7.8 and probably also a couple others by now with no luck.
All of them get error switching phone to PB pass through mode (0x07BE). My system cannot find the driver for MDM 6600 and my systems will only see it as an unknown device after RSD light trys to do the PB mode switch. I have tried installing the driver pack after the PB switch, which doesn't work. Extracting the drivers to a location that I then direct device manager to and that doesn't work.
Any other ideas on how to get this good hardware back and going again?
I will try the process on a completely different computer tomorrow, maybe the OS switch wasn't enough and there is a conflict with my machine. I doubt it though because I have used this machine to work on my D3.

PEZ Dispenser said:
Ok, so now I have tried 4.6.8, 4.7.3, 4.7.8 and probably also a couple others by now with no luck.
All of them get error switching phone to PB pass through mode (0x07BE). My system cannot find the driver for MDM 6600 and my systems will only see it as an unknown device after RSD light trys to do the PB mode switch. I have tried installing the driver pack after the PB switch, which doesn't work. Extracting the drivers to a location that I then direct device manager to and that doesn't work.
Any other ideas on how to get this good hardware back and going again?
I will try the process on a completely different computer tomorrow, maybe the OS switch wasn't enough and there is a conflict with my machine. I doubt it though because I have used this machine to work on my D3.
Click to expand...
Click to collapse
now lets go 1 step back on rsd lite and downgrade to the second latest version. and install the Motorola bootloader drivers or normal drivers with that. quick question. can you boot past the error screen into the recovery? It is R and Q and Power button. when the M screen is present.
Sent from my Amazon Kindle Fire using Tapatalk HD

Vlasp said:
now lets go 1 step back on rsd lite and downgrade to the second latest version. and install the Motorola bootloader drivers or normal drivers with that. quick question. can you boot past the error screen into the recovery? It is R and Q and Power button. when the M screen is present.
Sent from my Amazon Kindle Fire using Tapatalk HD
Click to expand...
Click to collapse
I'm using RSD lite 6.1.5, so you say I should try 6.1.4 or another older version?
What is the difference between Motorola bootloader drivers and normal drivers?
I thought it was R and M and the Power button to get into recovery. Anyway, I tried R and Q which does not work either. Doesn't look like I can get into recovery. Can I flash a recovery system onto it with RSD lite and then fix it from there?
Thank you Vlasp for taking the time to help me out with this.

PEZ Dispenser said:
I'm using RSD lite 6.1.5, so you say I should try 6.1.4 or another older version?
What is the difference between Motorola bootloader drivers and normal drivers?
I thought it was R and M and the Power button to get into recovery. Anyway, I tried R and Q which does not work either. Doesn't look like I can get into recovery. Can I flash a recovery system onto it with RSD lite and then fix it from there?
Thank you Vlasp for taking the time to help me out with this.
Click to expand...
Click to collapse
I am getting all of my facts mixed up. It is R and M, and there are no bootloader drivers. and regarding the rsdlite, try the 6.1.4 or something.
Sent from my Amazon Kindle Fire using Tapatalk HD

You can flash the bootloader update, and then try flashing again... 4.04 or something like that... I cant check as my phone got stolen last week, but I think it may solve your problem

donlloreda said:
You can flash the bootloader update, and then try flashing again... 4.04 or something like that... I cant check as my phone got stolen last week, but I think it may solve your problem
Click to expand...
Click to collapse
I haven't been able to find any information on this or any other bootloader update. Can you maybe point me in the right direction?

try turning off firewall and flash it again
Sent from my Motorola MB612 using xda app-developers app

Hot-dog007 said:
try turning off firewall and flash it again
Sent from my Motorola MB612 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure how that is supposed to help and the firewall was already disabled anyway.
When RSD lite finishes flashing and wants to switch the phone to PB pass through mode the system sees my phone as an unknown device and won't install the correct driver correctly. I do have the option to select which driver to install and can find Motorola from the menu but then I am faced with about 10 different options on what specific device driver to install. One of them is Motorola PB interface, one of them is Motorola Flash interface, etc etc. I've tried the PB interface driver and it seems like it installs but it still shows up as an unknown device on my system and the flashing fails.

try sbf_flash using linux

Soft brick but with no adb connection on bootloader

Ok, tired of waiting for the OTA KitKat update for my Nexus 7 2012 tablet, I downloaded the OTA update and sideloaded it with adb. Got a status 7 error and now it's stuck on a bootloop. Thing is, my Windows 8 laptop won't recognize the device anymore (code 43 error on device manager) when on recovery or bootloader. There's even no way to instal google's usb drivers or anything because it says the device malfunctioned. I downloaded the factory image but, obviously, can't sideload it or do anything with it.
Please give me a hand with this, I'm really desperate.

More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app

nobody_nowhere said:
More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Sorry, wasn't sure what you needed. The bootloop esentially goes from recovery to off and then to recovery again. I am able to go to fastboot normally (power and volume down when off).
Wanting to root the device a while ago, I unlocked it and rooted it whitout issues. Since the 4.3 update though, it was a little more difficult to root so having no time to research I just left it at that. That's all that was done to the Nexus 7. No Custom Recovery, no ROM, no nothing. Now, waiting for 3 weeks for KitKat, decided to sideload the OTA update (I did check the version was my device's version) the status 7 error appeared and all hell broke loose with the computer not recognizing the device.

Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app

Duplicate post. Please erase.

nobody_nowhere said:
Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Yeah, that's what relaxes me a bit, but I can't seem to fix it for 20 hours straight. I use this for studying.

Well, I suggest using another computer (a friend's or relatives') or installing a Linux distro like ubuntu. Oses other than Windows usually don't have such problems. I suggest you download something called adb gui which as I recall did a pretty fine job of 're installing the drivers for me.
But then, please do correct me if I'm wrong... I think that you must first use the device on adb and get the drivers installed and then only can you use it by the fastboot interface.
Sent from my GT-S5570 using xda app-developers app

I used Wug nexus root toolkit to install drivers (windows 8.1) there are clear instructions (if you click manual or something similar) how to get drivers to work.

Yeah, actually I did use the toolkit when I was trying to update to KitKat. Thing is, it doesn't work since the bricking occurred.
Yeah, I'll try on another pc, and I'll keep you posted.
Thanks
Sent from my Nexus 4 using xda app-developers app

I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.

Johnson90512 said:
I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.
Click to expand...
Click to collapse
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app

nobody_nowhere said:
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?

Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
It pretty much cancels out any problems with drivers.
It is easy to do.
It takes 5 minutes to boot up and test? Try it for yourself
Sent from my Nexus 5

Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app

nobody_nowhere said:
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
I appreciate the advice, I will give it a shot this evening, and let you know if this works. I'm sure that it will.

Alright, so I got SDK up and running on Linux! It was a little bit of a pain, but it installed just fine. Once I got it all installed I was able to see the nexus 7 through fastboot! From there I was able to reinstall the bootloader. Then was able to get to recovery to do an adb push to get a rom of 4.4 on to it. 4.4 installed just fine. All problems are fixed Good suggestions guys!