Database Users

Unable to see phone when in download mode

I'm trying to revert back to stock on my Epic. I previously flashed using Clockwork and wanted to try Odin this time around but when I put the phone into Download mode my computer doesn't recognize the device. I've tried multiple cables and USB ports including one on the board itself. I am using Windows 7x64 and have the 64 bit samsung drivers installed properly. If I do a battery pull and boot the phone normally the computer recognizes the phone no problem.
Any ideas?

ghsthntr said:
I'm trying to revert back to stock on my Epic. I previously flashed using Clockwork and wanted to try Odin this time around but when I put the phone into Download mode my computer doesn't recognize the device. I've tried multiple cables and USB ports including one on the board itself. I am using Windows 7x64 and have the 64 bit samsung drivers installed properly. If I do a battery pull and boot the phone normally the computer recognizes the phone no problem.
Any ideas?
Click to expand...
Click to collapse
I was having a similar issue with my MBpro, nothing would recognize my phone. Tried it on another comp and bingo. I think stuff is just finicky with USB ports. Lame-o.

ghsthntr said:
I'm trying to revert back to stock on my Epic. I previously flashed using Clockwork and wanted to try Odin this time around but when I put the phone into Download mode my computer doesn't recognize the device. I've tried multiple cables and USB ports including one on the board itself. I am using Windows 7x64 and have the 64 bit samsung drivers installed properly. If I do a battery pull and boot the phone normally the computer recognizes the phone no problem.
Any ideas?
Click to expand...
Click to collapse
when did u plugg ur phone in dowload mode?
try this ... load odin ... turn ur phone off!!! plugg it to the computure so when u see its charging for 30 sec. Then put the cellphone into download mode... and that should work

maldito.boss said:
when did u plugg ur phone in dowload mode?
try this ... load odin ... turn ur phone off!!! plugg it to the computure let it charge for 30 sec and the put it into load mode... that should work
Click to expand...
Click to collapse
Yea...this post made my brain hurt...and of course didn't change anything...but..thanks?

Here's another piece of info that may help nail down the problem...
Odin is able to see the phone if I boot into Clockwork recovery mode but because clockwork is up the phone can't receive a flash but Odin does see the phone with no problem. It just still won't see the phone when booted into download mode.

ghsthntr said:
I'm trying to revert back to stock on my Epic. I previously flashed using Clockwork and wanted to try Odin this time around but when I put the phone into Download mode my computer doesn't recognize the device. I've tried multiple cables and USB ports including one on the board itself. I am using Windows 7x64 and have the 64 bit samsung drivers installed properly. If I do a battery pull and boot the phone normally the computer recognizes the phone no problem.
Any ideas?
Click to expand...
Click to collapse
I use windows7 64 too. I encountered tons of problems when trying to flash my epic. first my computer doesn't recognize my phone in download mode. after i wipe out all the drivers and reinstall them. finally i get my computer recognize it under download mode, but Odin froze every time during the flash.
Finally, i tried on another desktop computer with windows XP. Everything went perfectly. So maybe you should try that too.

I cannot connect to my Epic in download mode on mac os x either.
I was trying to install a lag fix, and now all my phone will do when powering on is show switch between the normal Samsung screen, and another reading "Samgung GT I9000".
I can still boot into Clockwork Recovery. But OS X will not recognize my phone.
Either that, or Heimdall isn't recognizing it and won't let me flash.
Help! Any ideas?

Pirate-M.Lifnen said:
I cannot connect to my Epic in download mode on mac os x either.
I was trying to install a lag fix, and now all my phone will do when powering on is show switch between the normal Samsung screen, and another reading "Samgung GT I9000".
I can still boot into Clockwork Recovery. But OS X will not recognize my phone.
Either that, or Heimdall isn't recognizing it and won't let me flash.
Help! Any ideas?
Click to expand...
Click to collapse
Really!?! No one has any idea? Please guys, I'm just sitting here with a broken phone, there must be a way for me to fix this.

Pirate-M.Lifnen said:
Really!?! No one has any idea? Please guys, I'm just sitting here with a broken phone, there must be a way for me to fix this.
Click to expand...
Click to collapse
I had the same problem, I couldn't connect it to 3 of my pc's. 2 xp's and one windows 7. Turned out the port on the phone it self was broken, had to take it sprint and get it replaced.

Pirate-M.Lifnen said:
Really!?! No one has any idea? Please guys, I'm just sitting here with a broken phone, there must be a way for me to fix this.
Click to expand...
Click to collapse
If OS X isn't recognising your phone it's likely your phone has the buggy secondary bootloader. Samsung corrected the bootloader for at least the GT-I9000 JPA firmware but I'm unsure if they have done so for other devices or firmware releases.
Unfortunately the only solution then is to use Windows or Linux. If you don't have access to a system running either of these OS then I recommend downloading a 64-bit release (assuming your PC has a 64-bit CPU) of Ubuntu, then you can download the Heimdall binaries from my website and use it to recover your phone.

i had an extremely similar issue as to what you are having. I have 3 win 7 machines and 1 xp, none worked. I went to a friends house he has 2 win 7s and an xp also didnt work. I did a general search and found all kinds of crap. One dude something about using his chicks blackberry usb cord and suddenly it worked on any and all of the machines it had previously not worked. so at the time im reading this on my chicks laptop which has a damn blackberry cord attached to it chargin her evo(go figure) ... anyway u didnt need the whole story but i have nothing to do right now.
Point is everyone says try different cords, i say try the damn blackberry cord if you happen to have one or a friend that has one.

Benjamin Dobell said:
If OS X isn't recognising your phone it's likely your phone has the buggy secondary bootloader. Samsung corrected the bootloader for at least the GT-I9000 JPA firmware but I'm unsure if they have done so for other devices or firmware releases.
Unfortunately the only solution then is to use Windows or Linux. If you don't have access to a system running either of these OS then I recommend downloading a 64-bit release (assuming your PC has a 64-bit CPU) of Ubuntu, then you can download the Heimdall binaries from my website and use it to recover your phone.
Click to expand...
Click to collapse
Is it the hardware on the Macbook pro itself? or just the OS? in other words, If I were to partition my macbook with ubuntu would that work with heimdall? would it be able to recognize my phone while it's in download mode as opposed to OSX, which couldn't...?

ldartez said:
Is it the hardware on the Macbook pro itself? or just the OS? in other words, If I were to partition my macbook with ubuntu would that work with heimdall? would it be able to recognize my phone while it's in download mode as opposed to OSX, which couldn't...?
Click to expand...
Click to collapse
In this particular instance Apple haven't done anything wrong at all, both their hardware and software is fine. The issue is that Samsung are distributing secondary bootloaders that aren't complaint with the USB specifications.
Whilst that is annoying, the good news for you is that you can simply install Linux (Ubuntu etc.) or Windows on your Macbook and you'll be able to flash just fine.

[Q]Bricked Nexus 7 not recognized on windows Please Help

Hi My nexus 7 was working fine I had a custom rom (paranoidandroid ) tried to upgrade to the latest release and now stays stuck at jelly bean splash screen
ive tried
installing frivers through wugz 1.5
nexus root kit uninstalled reinstalled tried to connect in fastboot mode nothing
I used a windows 7 box and an xp box updated usb drivers on both pcs nothing its like the port on the nexcus 7 was broken or something please help!
The only way I see out is if maybe I can connect through linux but not sure how to I do have a laptop running backtrack I could use

Wrong forum for this but:
Sounds like you tried to install on top of the existing ROM without wiping.
Can you get into fastboot? if so open a command prompt from the folder you have fastboot.exe installed and type "fastboot devices". do you see your serial number? If so you're fine! Flash a custom recovery you can easily wipe/reset and wipe dalvik cache and install a new ROM.

asawoszc said:
Wrong forum for this but:
Sounds like you tried to install on top of the existing ROM without wiping.
Can you get into fastboot? if so open a command prompt from the folder you have fastboot.exe installed and type "fastboot devices". do you see your serial number? If so you're fine! Flash a custom recovery you can easily wipe/reset and wipe dalvik cache and install a new ROM.
Click to expand...
Click to collapse
I can get into fastboot and it doesnt recognize it ive tried everything different cables etc
also i was upgrading from 1.9.2 to 1.9.5 so a full wipe was not required
My main problem is i cant connect cant list devices

so if you're in fastboot mode and you type "fastboot reboot-bootloader" nothing happens?
I don't see how installing a ROM would cause these problems.

asawoszc said:
so if you're in fastboot mode and you type "fastboot reboot-bootloader" nothing happens?
I don't see how installing a ROM would cause these problems.
Click to expand...
Click to collapse
Nothing at all it doesnt recognize it at all
I dont see either I dont get it and I cant get into recovery if i try that it gets stuck at google screen
if i try to boot then I just get stuck at splash
tried different systems no dice

Put your device in fastboot mode. Do not connect it yet.
Run wugz 1.5.2 (that's the latest I think) and press the "Full Driver Installation guide".
Check the instructions to remove your current drivers. Remove them.
connect your device
Reinstall the drivers manually (not via the toolkit). Use the naked drivers from here.
Download the factory image from here and flash it via the toolkit.
root it, flash cwm do whatever you want to do :silly:
profit

Wont respond or recognize it

snipestech said:
Wont respond or recognize it
Click to expand...
Click to collapse
You need to install the drivers. Do you know how to get into your device manager in windows and install drivers for devices connected? You need to dl th wugz that regunus told you about above. After installing you can tell your computer to search in that folder to install drivers. When you open your device manager do you see anything yellow with a question mark. Once you have the drivers installed correctly then follow this http://forum.xda-developers.com/showthread.php?t=1781250 and you will be golden. Been through this a couple times already

Also when you try to manually install drivers for the devices that are not recognized in the device manager make sure to guide the driver install wizzard in the folder Universal_Naked_Driver_0.7 (or wherever you unzipped your drivers) and NOT in a specific directory like "amd64" or "i386".
If all drivers are succesfully installed, your computer will see the device in fastboot mode and your problems are gone ^_^

snipestech said:
Wont respond or recognize it
Click to expand...
Click to collapse
You can install the toolkit from here http://forum.xda-developers.com/showthread.php?t=1809195 then use it to install the drivers, then install temp cwm, then reboot into recovery, do a full wipe and try to install 1.95 again. You can use the toolkit to install a rom as well if you download it to your computer. Hope it helps.You always have to wipe cache and dalvic cache when flashing any rom. No wipe means you don't need to do a data/factory reset.

Vocalshock said:
You need to install the drivers. Do you know how to get into your device manager in windows and install drivers for devices connected? You need to dl th wugz that regunus told you about above. After installing you can tell your computer to search in that folder to install drivers. When you open your device manager do you see anything yellow with a question mark. Once you have the drivers installed correctly then follow this http://forum.xda-developers.com/showthread.php?t=1781250 and you will be golden. Been through this a couple times already
Click to expand...
Click to collapse
Its not connecting at all Ive done this before ive had many Android phones when i connect nothing happens. I tried different cables computers etc nothing no connection at all
Would like to try to connect on linux if not Its going on ebay as is

snipestech said:
Its not connecting at all Ive done this before ive had many Android phones when i connect nothing happens. I tried different cables computers etc nothing no connection at all
Would like to try to connect on linux if not Its going on ebay as is
Click to expand...
Click to collapse
dude, forget the ebay! Your device is ok!
Check the Device Manager in the control panel to make sure all the drivers have been installed correctly. After that we'll see

I did dalvic and that's it also I already tried that tool kit regunus is connect via teamviewer see if he can help
Sent from my Galaxy Nexus using xda premium

snipestech said:
I did dalvic and that's it also I already tried that tool kit regunus is connect via teamviewer see if he can help
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I think he should be able to help. If not let me have a go at it..I have Team Viewer.

He would need dubugging mode on wouldnt he
Sent from my SGH-I777 using Tapatalk 2

Regunus tried no avail.
I reformatted my laptop dual boot windows 7 32 bit.
Tried all previous suggestions its not recognized, me and Regunus came to the conclusion that the port can't be bad Cuz it charges yet it does not recognize it.
I just finished installing adb fastboot on ubuntu if I go to terminal and list devices nothing if I connect my Galaxy sIII it shows up so again not being recognized while other devices do.
Current state :
Fastboot start goes to paranoid android jelly bean splash
And hangs
Fastboot recovery stays stuck at Google screen
I have reciept and all to bad I can't return may just post on ebay

Same Issue
I'm having the same problem, was this ever resolved?
Edit: I was having the same problem. Downloaded 'Nexus 7 Toolkit' and ran the 'install driver' option again (option 1). Device was recognized again.

No such thing as no way out. Keep find a way to connect and you're all set. Have you tried force reboot to fastboot and then enter recovery? I have similar problem once with my nexus s and i finally find a way after 10 hours of constant googling

I've tried nexus 7 toolkit
I reboot into fastboot mode and select recovery and it goes to Google and hangs I've tried on different post nothing at all
Sent from my SPH-L710 using Tapatalk 2

When it was recognized what state was it in?
fastboot mode?
Sent from my SPH-L710 using Tapatalk 2

[Q] Google Nexus 4 bricked?

I have a Google Nexus 4, bought direct from Google, I rooted it and it was working well for a while. Then the battery started draining super fast. A friend recommended resetting, so I did and it seemed to fix it for a while. Then the battery issue came up again, so I reset again, expecting the same outcome....however, I wiped the phone completely. It turns on and displays Google, and that's it.. My computer does not recognize the phone when I plug it in, and I cannot get the USB Debugging to even be an option. Every resolution I have found for this situation needs me to enable the USB Debugging mode. Is there any other way to get all the OS files back on this phone or is it bricked?
When I plug it into the PC it tells me to look up drivers, and this is how it sees my phone: Unidentified Device USB\VID_0CF3&PID_3000&REV_0200.
It isn't recognized as a phone at all. It tells me to download Atheros Drivers.
I have searched for days trying to find the solution to this. Any help would be so very appreciated by this noob

Did you try to manually delete drivers from the device manager? Ticking the option that permanently delete the driver from PC.
And after doing this...trying Windows Update for driver installation?
PS: also try to manually flash with Fastboot all the latest Factory Image from Google....
Sent from my Nexus 4 using Tapatalk 4 Beta

thesebastian said:
Did you try to manually delete drivers from the device manager? Ticking the option that permanently delete the driver from PC.
And after doing this...trying Windows Update for driver installation?
PS: also try to manually flash with Fastboot all the latest Factory Image from Google....
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, I've done that, there are currently no drivers on my PC. When the phone is plugged into the PC, it tells me to find drivers because it is an unrecognized device.

MrsWhitey said:
I have a Google Nexus 4, bought direct from Google, I rooted it and it was working well for a while. Then the battery started draining super fast. A friend recommended resetting, so I did and it seemed to fix it for a while. Then the battery issue came up again, so I reset again, expecting the same outcome....however, I wiped the phone completely. It turns on and displays Google, and that's it.. My computer does not recognize the phone when I plug it in, and I cannot get the USB Debugging to even be an option. Every resolution I have found for this situation needs me to enable the USB Debugging mode. Is there any other way to get all the OS files back on this phone or is it bricked?
I have searched for days trying to find the solution to this. Any help would be so very appreciated by this noob
Click to expand...
Click to collapse
Hold volume up/down and power until it reboots into boot loader mode. Download the factory images from the Google website (search nexus stock images on Google) and plug your phone into the computer and use fastboot to flash the OS back.
Rember, as long as you can get the phone to turn on you can fix whatever other issue your having providing its software related.
To fastboot flash,
You need the android SDK, use Google to figure out how to install it but its not hard.
Run the flash-all bat found in the archive file you downloaded, or manullay flash each partition like this.
fastboot flash [partition] [.IMG name]
Sent from my Nexus 4 @1.944 GHz on Stock 4.2.2

IRX120 said:
Hold volume up/down and power until it reboots into boot loader mode. Download the factory images from the Google website (search nexus stock images on Google) and plug your phone into the computer and use fastboot to flash the OS back.
Rember, as long as you can get the phone to turn on you can fix whatever other issue your having providing its software related.
To fastboot flash,
You need the android SDK, use Google to figure out how to install it but its not hard.
Run the flash-all bat found in the archive file you downloaded, or manullay flash each partition like this.
fastboot flash [partition] [.IMG name]
Sent from my Nexus 4 @1.944 GHz on Stock 4.2.2
Click to expand...
Click to collapse
I am having trouble getting the phone to accept anything from the PC...

MrsWhitey said:
I am having trouble getting the phone to accept anything from the PC...
Click to expand...
Click to collapse
Download the toolkit and install the drivers
Sent from my Nexus 4 @1.944 GHz on Stock 4.2.2

yea download Google Nexus 4 ToolKit install drivers then you can factory restore using the toolkit to restore
i think i chose option 9 and it downloaded the need restore image

Tried it all
I have tried all those ideas and all have failed. I can never get the computer to see my device. All it says is unknown device. When I click update drivers and direct it to the sdk driver I download it still gives me no connection through fastboot or adb. I have tried selecting various general Android drivers through the update drivers screen, Found some from Google Inc. that specify Nexus 4 bootloader interface and adb interface. Nothing is working. I think I need to have a working Nexus 4 to install to correct drivers first and then I might be able to piggy back off those and use my phone to flash through fastboot or push adb. I have worked with both command lines with reasonable success before rooting samsung tablets and phones and htc's. I am familiar with the process and have read numerous ideas none of which seem to work in this case. Made it all the way to Google search page 12. Anyone know a way to force install the Nexus 4 drivers without having a working phone present? I am thinking I just need to go buy a new one and return it after I plug it in to install drivers. Don't want to have to pay the re-stock fee though. Any other ideas are very welcome.
And I have tried to use the toolkit as well and it does nothing either. I have the stock rom ready to go just need a way to get it onto the phone.

[Q] Bricked Updating to CM11

Hey guys any help or suggestions will be greatly appreciated on this matter. I will try to be as detailed as possible but I'm trying to fix this phone for a friend and he isn't very phone savvy. From what I understand, he was previously on CM10 and tried updating to CM11 using the cmupdater. For some reason it failed and he was stuck in TWRP. When he tried to reboot it kept kicking him back to recovery. He took his phone to a phone repair shop who then wiped his device. At this point he gave me the phone to try to fix.
First of all I have working fastboot and adb drivers for my Nexus 5 so I don't think this is a driver issue but I'm no expert on the Nexus 4 so I could be wrong. I'm also running Windows 8.1 if this is any relevance.
I can still access the devices bootloader (ver MAKOZ20i)
I can still access TWRP (ver 2.6.0.0)
When plugging the device into my USB 2.0 ports, nothing shows up in my device manager in bootloader, TWRP, or TWRP ADB sideload.
When plugging the device into my USB 3.0 ports, I see 'Unknown USB Device (Device Descriptor Request Failed)' and the Device Instance Path is 'USB\VID_0000&PID_0002\7&20F39B9B&0&2' in bootloader, TWRP, or TWRP ADB sideload.
I've never heard of a device not being seen at all in by USB 2.0 ports but showing using USB 3.0 ports so I attempted to give extra juice to the phone using a powered USB OTG cable. Still nothing shows up.
I've tried running 'fastboot device' and 'adb devices' with no luck.
I think I've covered all the bases... can anyone think of anything that could help me re-install a new rom or factory reset or his he out of luck?

I think it may be a Win8 problem. You have access to another machine with Win7 or WinXP?

Install "universal driver.exe" in win7, than connect phone while power off, I think it'll install driver...than push any custom ROM to phone via adb or just flash any official IMG..

Well I can tell you WHY it didn't work. That version of TWRP is not able to install 4.4 (CM11). if you manage to successfully push via adb and get it started again, make sure to flash the newest version of TWRP before trying that again.

Thanks for the reply guys. I kind of guessed that the version of TWRP was not compatible as I installed CM11 on my old Nook Tablet and had to update my recovery before installing it. Unfortunately the guys who wiped the phone prevented me from installing an old version of CM10 that my friend probably had from the cmupdater.
As for Windows 8 being the issue.. I attempted to try to use my laptop which runs Windows 7 but was unable to get anything to happen. Since the laptop only had USB 2.0 ports, plugging in the device to any of the ports did the exact same thing as what it did on my desktop (Windows doesn't even recognize anything is connected). I still get the charge animation on the phone but yea... nothing in device manager. I'm thinking of running Linux from a live installation to see if anything different happens, unfortunately its been ages since I've touched Linux so this is kind of a last ditch effort here.
Any other thoughts?

mrlazyone said:
Thanks for the reply guys. I kind of guessed that the version of TWRP was not compatible as I installed CM11 on my old Nook Tablet and had to update my recovery before installing it. Unfortunately the guys who wiped the phone prevented me from installing an old version of CM10 that my friend probably had from the cmupdater.
As for Windows 8 being the issue.. I attempted to try to use my laptop which runs Windows 7 but was unable to get anything to happen. Since the laptop only had USB 2.0 ports, plugging in the device to any of the ports did the exact same thing as what it did on my desktop (Windows doesn't even recognize anything is connected). I still get the charge animation on the phone but yea... nothing in device manager. I'm thinking of running Linux from a live installation to see if anything different happens, unfortunately its been ages since I've touched Linux so this is kind of a last ditch effort here.
Any other thoughts?
Click to expand...
Click to collapse
One more, when you plug into usb 3.0 you can see unknown device Right ??
If yes, download driver files from here Here.
It's a zip contains .inf files, Now click on unknown device and select update drivers then give the path to these drivers manually.
Hope this will help you out.

I'm pretty convinced at this point that the phone can't be fixed by me. Running it through Ubuntu I can't see the device at all (USB 2 & 3) when running the lsusb command but it sees my nexus 5 just fine. I even tried modifying drivers to match vendor id product id and class id as reported by windows. Thanks for the suggestions. Does anyone know of a reputable service to get this phone repaired? How much does a JTAG repair usually cost?
Sent from my Nexus 5 using XDA Premium 4 mobile app

mrlazyone said:
I'm pretty convinced at this point that the phone can't be fixed by me. Running it through Ubuntu I can't see the device at all (USB 2 & 3) when running the lsusb command but it sees my nexus 5 just fine. I even tried modifying drivers to match vendor id product id and class id as reported by windows. Thanks for the suggestions. Does anyone know of a reputable service to get this phone repaired? How much does a JTAG repair usually cost?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The following method may still help
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060

DrFredPhD said:
The following method may still help
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Click to expand...
Click to collapse
Awesome! Didn't realize this was an option. It didn't work using the USB 3.0 ports but the USB 2.0 actually worked for this method. Thank you!

Bricked & Unseen...

Ok, here goes my story.
Just a week ago from the date this was posted, I decided to update my recovery (TWRP) through ROM Installer. Surprisingly, I didn't see TWRP at all in the "Recoveries" section of the application. Stock, ClockworkMod Touch, regular Clockworkmod (no touch), and unofficial Clockworkmod were available - from what I can remember. I decided to use Clockworkmod (no touch) to install Paranoid Android. Coming from OmniROM, I factory reset and flashed the .zip.
Flashing ended in error with Status 7. A while before I had used ClockworkMod Touch to try another ROM and had no such issue. I ignored the error and restarted my tablet hoping that it would still boot fine. It rebooted, gave me the Google logo for about 5-10 seconds and automatically rebooted into recovery.
I saw a bypass for Status 7. Removing some lines from the updater-script was the solution. Having no access to my Nexus 7 storage, this bypass is unusable
I tried flashing a new recovery using flashboot fastboot. After verifying that I had my drivers installed (Universal ADB by Koush), I opened up adb in the command line (Windows) as an administrator. I could not see my device. I tried the drivers from Asus, multiple USB 2.0 ports, and a different USB cord, but same results. I tried on a different computer. Still no detection.
Systems used: Windows 8.1, Windows 7 (x64), Windows 7 (x86)
I tried using Wug's Toolkit and used Flash Stock + Unroot, since it didn't need USB Debugging enabled. Same results...
I also tried plugging in another Android phone (LG Optimus Dynamic II) to see if Windows would recognize it. Windows recognized it, installed drivers automatically, and was recognized in ADB immediately. This practically unknown phone (XDA doesn't have a section for it yet) could be recognized, but my world famous Nexus 7 2012 can't be seen.
I have absolutely no idea of what to do now...

Are you on the bootloader screen when trying to use fastboot?

PrizmaticSmoke said:
Are you on the bootloader screen when trying to use fastboot?
Click to expand...
Click to collapse
Yes. Every time I use fastboot, I am in the bootloader.
I'm not new to this at all, so say whatever you need to ^^
The main problem is my PC not recognizing my Nexus 7 through adb. Again, I have used multiple cables with no success.
The computer I am using for this runs Windows 7 x64. I have only tried using USB 2.0 ports to connect my tablet.
Thank you!

Might try deleting the drivers and starting over. I had some issues with adb drivers for both the N7 and the kindle fire on windows 7 as well, but eventually got both working by doing this several times.
I'm assuming you ticked the option for softbricked when trying the flash stock option? If not try again and check that option.
This thread http://forum.xda-developers.com/showthread.php?t=1907796 has a section on driver installation with good info and links too.
Hope that helps. Best of luck man, getting the adb drivers working properly seems to be finicky sometimes in my experience, and i'm no stranger to PC and software troubleshooting either.

PrizmaticSmoke said:
Might try deleting the drivers and starting over. I had some issues with adb drivers for both the N7 and the kindle fire on windows 7 as well, but eventually got both working by doing this several times.
I'm assuming you ticked the option for softbricked when trying the flash stock option? If not try again and check that option.
This thread http://forum.xda-developers.com/showthread.php?t=1907796 has a section on driver installation with good info and links too.
Hope that helps. Best of luck man, getting the adb drivers working properly seems to be finicky sometimes in my experience, and i'm no stranger to PC and software troubleshooting either.
Click to expand...
Click to collapse
Thank you so much for all of this! I'll need all the luck I can get...
By the way, I checked that softbrick option ^^!