Related
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.
I've searched all over the posts and google and have yet to find a solution. I am a MAC user and trying to restore fascinate. I am stuck at Samsung screen. I can get into Clockwork Mod Voodoo.
When i did my last backup I never enabled USB Debugging. I can not ./adb into device, nor can I use ODIN on friends PC. (No Device) Same result with Heimdal "Failed to detect Device" I would just like to get back to stock. Is there a step by step guide to recover similar to ODIN get you back to stock but for a MAC. Or since i never enabled Debug mode I should just use my warranty?
When you tried Odin, did you have the battery out and put the phone in download mode?
Kevin Gossett said:
When you tried Odin, did you have the battery out and put the phone in download mode?
Click to expand...
Click to collapse
Yes, I did see the Yellow triangle Droid character w/ shovel
So, battery out and in download mode, Odin doesn't recognize? Hm
Kevin Gossett said:
So, battery out and in download mode, Odin doesn't recognize? Hm
Click to expand...
Click to collapse
I feel because I never enabled debug mode originally.
Does it recognize the phone at all? Maybe the drivers need to be updated
Sent from my SCH-I500 using XDA App
Morning, I'm attempting to resolve the same issue. I have the "Yellow Shovel" Andy but I can't get Odin to recognize the device.
The device was fine and Odin was working last night, however I do believe I did something ridiculous last night. I tried flashing my phone with a Nexus S rom and succeeded. HOWEVER, the only buttons that are recognized are the "Home" and "Menu" soft keys.
I can boot into the 2.3 Nexus S rom but I can't get the hardware to recognize anymore.
UPDATE: I managed to get the USB to recognize. I'm not completely sure how, it just started recognizing it after fidgeting with the cable. I'm not flashing it back to stock using ODIN and the following post.
http://forum.xda-developers.com/showthread.php?t=867648
UPDATE: The link above worked. I recommend using the stock USB cable that comes with the phone. Now that it's back.. I'm curious to know what I would have to change for 2.3 to work.. hm..
Kevin Gossett said:
Does it recognize the phone at all? Maybe the drivers need to be updated
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Come to think of it I did update the drivers on my friends PC but there was an error installing drivers. He had a Windows XP 32bit device (Did install the 32bit drivers X86) Im going to try my other buddies PC he has Vista should that make a difference?
Soft Brick fixed
rolo12010 said:
Come to think of it I did update the drivers on my friends PC but there was an error installing drivers. He had a Windows XP 32bit device (Did install the 32bit drivers X86) Im going to try my other buddies PC he has Vista should that make a difference?
Click to expand...
Click to collapse
UPDATE: My buddy brought over his PC and got it restored! looking good now. We just updated the samsung drivers. restarted the machine. And it worked. Will update w/ the file he used. Thanks for the help and feedback.
Ok, I'm having a problem here. I'm buzy on a ROM, and I have made something that I want to test. But when I try to access my phone via adb, it doesn't show up in adb devices. Just nothing. I reïnstalled adb, the drivers, rebooted the phone and computer, put on debugging mode, everything. The phone is showing in (windows) devices, but adb just don't recognize him. I'm on Windows 7 Home Premium. And on my phone Swiftdroid M5 (with ClockworkMod Recovery 3.2.0.1, which is working properly). Anyone knows what to do?
Anyone?
Sent from my GT540 using Tapatalk
Heres my solution ^^ adb worked for me some weeks ago but now i had your problem too lol:
first uninstall all the adb drivers from:
Start>devicemanager
then get this :
http://www.junefabrics.com/bin2/LGDriver.exe
original LG drivers
and install
then plug your phone(debugging on of course)
then it will show 7 (i think) installations
5 of them will be done fast but 2 won't finish installation
so just go to devices and printer
rightclick on android sooner single adb interface and select troubleshooting( marked with a yellow triangle)
then just let is solve the error
the last of the 7 drivers wont install but thats not a problem
EDIT: make sure u know on which port u were doing this
Oh of course you should reinstall the adb drivers. Btw i'm in linux you can use linux for building rom. What are you using?
Sadronis said:
Oh of course you should reinstall the adb drivers. Btw i'm in linux you can use linux for building rom. What are you using?
Click to expand...
Click to collapse
Windows 7 + Ubuntu 11.10
Sent from my GT540 using Tapatalk
is fastboot working now ?. and installed properly in device manager.
regisol said:
is fastboot working now ?. and installed properly in device manager.
Click to expand...
Click to collapse
Wrong topic
Sent from my GT540 using Tapatalk
Hello, I tried all of the above but my device still doesn't get recognized. Is there any other way to fix this? Thanks.
I've been in the same situation like this before. My phone wasn't recognized by adb. I though it was a driver problem so I reinstall the driver million times but it doesn't help. I tried on many other computer with various OS as well but adb still can't recoginized it. At last I flash another ROM and adb can recognized my phone again. so the problem is the SDSL ROM
I see. Thanks for the info ^_^
First some background:
Playing around with some ROMs, I loaded up MIUI. I wanted to see what all the fuss was about. While installing from ROM Manager, the subsequent boot into CWM started my backup and installed the ROM. During the process CWM notified me the install was attempting to overwrite the recovery partition. I inadvertently said yes, one of the bad things about touch recovery...fat fingers.
Result:
CWM was blown away. MIUI failed to install Google Apps.
I connect the N7 up to my PC. It is not detected. No ADB available, however I can use wireless ADB so I installed ROM manager and reflashed CWM. This was were the fun began. Everything on my internal storage got nuked during the install and attempted recovery. I had to format internal storage.
No biggie, I have backups on my laptop through WUGFresh Root Kit. I will restore back to stock and start over.
Problem:
No computer I connect the N7 to detects it, regardless of USB connection method nor OS on the PC (Ubuntu, Win 7, Mint). I still have wireless ADB but that doesn't help with fastboot.
Current Status:
Currently I am running AOKP, after flashing multiple ROMs and Recovery between TWRP (current) and CWM. Also I have done many factory resets, cache cleaning, etc.
My diagnosis:
I think my boot, recovery or bootloader partition is borked due to the fat finger in CWM while installing MIUI. The added bonus...without being able to connect the N7 to any PC, I can't get into recovery unless I get lucky (1 out of 10 tries I get lucky and can get into recovery). I can get into recovery as long as I can boot into a ROM and do any common method to reboot recovery.
Question:
Now my question, does anyone have any ideas what I can do to get the USB connection working again to allow ADB/Fastboot connections?
Additional info/Review:
I have a GNex that I can ADB/Fastboot into without issue.
I have tried multiple different cables to connect to PC/Laptops.
As mentioned, I have tried multiple PCs to attempt a connection running everything from Windows 7 to variations of Linux (Mint and Ubuntu)
All the cables work fine with GNex, excluding one cable I deemed trashworthy.
I am fairly certain that the micro-USB port is fine, I can charge without issue even connected to a PC. OTG cable works perfectly fine.
I did something saying a port was open from the N7 that cause USB connection to fail. I forget what I did to find that message or what program I was using. I think I was trying to do a adb usb command from the command line on the N7.
USB Debugging is enabled.
More info:
No errors in logcat when connecting N7 to PC.
Try to do complete wipe & flash stock . My desktop has never detected the n7 but the fastboot works. I was able to flash stock using wugs toolkit.
Sent from my GT-I9300 using Tapatalk 2
That is the problem, I can't get any PC to recognize the n7 is connected. therefore, wugs root tool kit wont work. it uses fastboot and adb. without the drivers loaded and the device detected, I can't use wugs. this happens even on machines I have never plugged the n7 into.
If I could find a flashable zip of stock, that might do the trick.
I am wondering if I can use the otg cable and connect from my phone with adb? I don't think I can run fastboot commands from the phone though.
Sent from my Nexus 7 using Tapatalk 2
Doubt you could. Have you tried booting into bootloader then changing the usb port on the and also try reinstalling the drivers. When in bootloader try locating your device in device manager.
Good luck
Sent from my GT-I9300 using Tapatalk 2
panjaby said:
Doubt you could. Have you tried booting into bootloader then changing the usb port on the and also try reinstalling the drivers. When in bootloader try locating your device in device manager.
Good luck
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
even in boot manager, the device does not show in device manager on windows and it can't be seen on Linux either when looking for attached devices.
With my old viewsonic gtab I use to verify there was a device connected from command line, that doesn't work either. I'll post that command later today, just for reference.
Sent from my Nexus 7 using Tapatalk 2
OK, I have verified the problem is on the tablet side. I can connect my OTG cable to the tablet and mount my GNex allowing me to perform adb commands sent to the phone. I can not mount my tablet to the phone reversing the cable.
N7 ---> OTG ---> USB ---> GNex (works)
GNex ---> OTG ---> USB ---> N7 (fails, phone does not recognize the tablet being connected. I verified I could connect to a USB stick without issue.)
I think this narrows it down to MTP/PTP being disabled somewhere. Since it affects fastboot as well, I am assuming something in boot or bootloader. I ruled out recovery due to recovery working correctly when I can get to it.
Any ideas?
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 ^^!