Long story short, I accidentally flashed an unrooted ROM and ran the one click unlocker thing. The phone still works fine and connects to the PC (and is recognized), but Odin won't recognize it. I've got my TWRP backup files but no way to spply them. I need to either make odin recognize it again or find an alternate way to do it.
I have uninstalled and reinstalled all drivers. I have tried multiple computers, one if which won't recognize the device in download mode, the other recognizes it as a "Samsung Android Device". Again, when not in download mode, both computers recognize it fine, and I can manage files.
Figured it out
For some reason, removing my SD card worked. I'll leave this up in case anyone encounters a similar problem.
Related
I have already installed the Samsung drivers but I cant get Odin to recognize my phone while in download mode. I even installed Kies but no luck. Does anyone have anysuggestions? I can mount my card and copy files but just no luck with Odin.
EDIT: NVM I've resolved my issue. I thought that my SGS1 setup was enough but I guess not. I had to reinstall Kies, reboot, restart Kies and went to Tools, then Install Drivers, reboot, then reconnect phone and it worked.
Hi,
So I just purchased a Samsung Galaxy S II, and I've been trying a few different ROM's found on this site. The last thing I did was actually revert back to a stock Samsung Kernel and firmware. This worked fine, but it unrooted my device, which I knew would happen, but now I'm not able to root it again because when I put the device into download mode, ODIN, or better yet, my computer won't detect the device.
I have all the drivers installed, and I also deleted them all, and Kies, and started from scratch again after searching XDA for similar issues.
I don't believe this to be a driver issue, since I was able to root my device, and swap roms before I went back to the official kernel and firmware. I'm with Bell in Canada, so the versions I went back to were not the official Bell versions, since Samsung has not made them available.
I have a Mac, but I've been using Windows 7 and Odin under VMWare. I can connect my device to either OSX, or Windows 7 when the device is not in download mode, and everything works fine, and Odin detects the device (Not that that does any good of course)
When I connect the device under download mode, the Mac detects the device and asks me if I want to connect it to my Mac, or to Windows (As it should) but no matter which one I select, neither OS acknowledges the device after that point, where as when I'm not in Download mode, both OS's detect the device fine.
After all my troubleshooting with my computer based off of what I found online here, The only conclusion I have left is that there is something missing on the device that allows it to be found under download mode, but that aspect of all this is beyond my current skill level.
Anyone have any ideas?
Are you pressing the Volume Up button to continue in Download mode? Besides, Virtual machine isn't recommended I think.
Yes, Once the Custom ROM warning comes up, I press the Volume up button to continue.
That wasn't even necessary on the Stock Bell ROM. The warning didn't come up at all.
VM has been working fine up until now, so I don't think that's the problem, but I have been thinking of trying this on my old laptop that runs on windows if nothing else pans out.
Scott56 said:
Yes, Once the Custom ROM warning comes up, I press the Volume up button to continue.
That wasn't even necessary on the Stock Bell ROM. The warning didn't come up at all.
VM has been working fine up until now, so I don't think that's the problem, but I have been thinking of trying this on my old laptop that runs on windows if nothing else pans out.
Click to expand...
Click to collapse
Have you found anyway to Make Odin recognize to phone in download mode?? Im still struggling with that. my phone is on stock kernel and not rooted yet, ODIN finds it fine when the phone is on and USB Debugging is on, but once I put the phone on download mode it wont recognize it, I dont know why..
Could it be because of the ''SAMSUNG Mobile MTP Device'' driver failed to install correctly??
all other drivers are installed correctly.. I have tried to get the driver mentioned above to install correctly but it fails every time, with USB debugging on and off, i have wiped the phone and installed Kies and the drivers several times, Im clueless right.. anyone have any idea please help??
I myself am also suffering from this problem. However, USB seems to function fine while the phone is booted up or in recovery (For ADB). I'm wondering if necessary files may have become corrupted or deleted in reference to USB drivers (phone side mind you) that are used in download mode.
edit: It's also recognized in recovery mode.
Even if it can't be fixed I'd still like to understand why.
-Simply D
was looking for help on this and saw this thread, same problem too..
Connects to Odin and Kies fine when switched on "normally", can use USB mass storage mode Etc.
comes up with a USB device has malfunctioned message on PC when I connect USB cable when switched on and in download mode
EDIT:- just to add, if I try upgrading firmware via Kies it gets to the point where it switches the phone to download mode to upgrade it and has the same issue even with an official upgrade
Figuring download mode is outside the normal boot procedure, I hoped on an off chance that pulling my battery and sim for a few minutes would reset it. It did indeed. Download mode is now functional again, just to be certain I tested it right before pulling the battery to make sure it was still broken. And multiple flashes and reboots afterwards seem to confirm that it has returned to normal.
Anyone else who solves it with this method, please report back.
-Simply D
SimplyD said:
Figuring download mode is outside the normal boot procedure, I hoped on an off chance that pulling my battery and sim for a few minutes would reset it. It did indeed. Download mode is now functional again, just to be certain I tested it right before pulling the battery to make sure it was still broken. And multiple flashes and reboots afterwards seem to confirm that it has returned to normal.
Anyone else who solves it with this method, please report back.
-Simply D
Click to expand...
Click to collapse
Tried this and it didn't work for me :/ going to give it another try later, thanks for the suggestion either way
I have read through every thread here on brick recover, and none addresses my specific problem.
I have a Verizon LTE Tab.
I installed Rom Manager and flashed Clockwork recovery. As everyone now knows, this bricked the tab.
I have found instructions in various places for flashing a new recovery through Odin3. However, I cannot get my tablet to connect to my PC. I put it in Downloading mode and connect it to my computer. At that point, the computer starts automatically installing drivers because it thinks the tablet is a Samsung CMDA modem. I cannot force it to install the correct drivers, I cannot update the drivers, and I cannot manually add the hardware.
Thus, although Odin3 recognizes a connection, it gets stuck at SetupConnection every time I try to flash a new recovery to it.
Any suggestions? Please help!
I had the same problem with my laptop + my home desktop. I cannot get either of them to recognize my tab. Fortunately for me, my work PC does. I have no idea what the difference is. They are all running Windows 7 Pro 64bit.
Hello all. I have been racking my brain for days and reading a billion posts and guides to no avail. I have flashed many a phone and have never had an issue until now. I have an SGH-I717 from AT&T unlocked and being used on T-Mobile. I was attempting to either go to a stripped Rom or Stock Rom to get rid of AT&T software. Well I noticed a couple of 4.3 Roms I had not tried before, I was currently on 4.0.4 stock rooted. So I started up CWM touch and started firing away, first Rom started acting strange with the screen coming on out of standby, so I decided to try the next one. Seemed awesome at first. Then I rebooted the phone after a couple of app installs. Boom, would not turn on. Blank screen, not responding to power button. Would go to CWM and Download mode. Hmm. Started fiddling, couldn't get Kies firmware recovery to get past 0%, tried Odin 1.83, 1.85 3.07 3.09, it kept crashing at getting pit for mapping. Windows 7 X64 pro, Was able to load a backup with cwm after copying through adb to internal sd. Didn't want that, attempted to flash again. Same thing. Got to adb with CWM up. Manually wrote 3e recovery to phone, bad idea. Now i can't do anything. Can't access the external sd to try and update.zip, can't get to adb no matter what, either drivers fail to install, hardware id missing, or some other nonsense. I tried an ubuntu 12 machine, windows xp (physical and virtual) several cables, and several windows 7 machines. All with similar results, linux won't recognize the phone through adb but will with lsusb and udev. I can get windows to recognize in factory mode, not odin mode, and odin will read the com port, but crashes on every machine at the pit phase. I tried heimdall and it complains that I don't have a matchine pit and I tried one that i found online and it is unable to write the pit file and just reboots the phone. I have been unable to manually flash anything from any point. Is there anything any of you can think of that I can try? I have heard of JTag and don't know much about it but read somewhere someone using and Arduino to do that, I have an arduino but its sound difficult due to size of the interface plug. Please help, phoneless and scared!!!
Since a Windows pc recognizes a lil bit, I would try using kies software and perform an emergency recovery.
Thanks for the reply
I entered the model SGH-I717 and then the S/N, tried this about 10 times with different cables and different Windows versions. Sticks at 0% after unpacking binary files. Stays there for a long time before failing and saying that it couldn't recognize the phone.
440bro said:
Since a Windows pc recognizes a lil bit, I would try using kies software and perform an emergency recovery.
Click to expand...
Click to collapse
Try ATT-I717
I will try that this evening thanks.
rangercaptain said:
Try ATT-I717
Click to expand...
Click to collapse
Updated Question
I have an arduino, is there any way without building a jtag interface or using a riff box to send some data to the phone through some of the pins directly and force it to accept adb commands or to push a file or some such? One thing to note on the 3e recovery I can see the filesystem and of course i did a factory reset so there is nothing there of use to me, however why won't the microsd card mount in stock recovery is that normal? Dummy me I had TWRP on it, then flashed CWM, and then manually used dd to write the stock back to it thereby making it difficult to do anything because 3e sucks. When I get home I'm going to try the OneClickUnbrick jar and see what that does. I have never tried it. There has to be a way to send data or arbitrary commands to the phone through the usb to force it to do what I want, isn't there a be my ***** adapter or something I can hook up to this paperweight?
One0f4K1nd said:
Hello all. I have been racking my brain for days and reading a billion posts and guides to no avail. I have flashed many a phone and have never had an issue until now. I have an SGH-I717 from AT&T unlocked and being used on T-Mobile. I was attempting to either go to a stripped Rom or Stock Rom to get rid of AT&T software. Well I noticed a couple of 4.3 Roms I had not tried before, I was currently on 4.0.4 stock rooted. So I started up CWM touch and started firing away, first Rom started acting strange with the screen coming on out of standby, so I decided to try the next one. Seemed awesome at first. Then I rebooted the phone after a couple of app installs. Boom, would not turn on. Blank screen, not responding to power button. Would go to CWM and Download mode. Hmm. Started fiddling, couldn't get Kies firmware recovery to get past 0%, tried Odin 1.83, 1.85 3.07 3.09, it kept crashing at getting pit for mapping. Windows 7 X64 pro, Was able to load a backup with cwm after copying through adb to internal sd. Didn't want that, attempted to flash again. Same thing. Got to adb with CWM up. Manually wrote 3e recovery to phone, bad idea. Now i can't do anything. Can't access the external sd to try and update.zip, can't get to adb no matter what, either drivers fail to install, hardware id missing, or some other nonsense. I tried an ubuntu 12 machine, windows xp (physical and virtual) several cables, and several windows 7 machines. All with similar results, linux won't recognize the phone through adb but will with lsusb and udev. I can get windows to recognize in factory mode, not odin mode, and odin will read the com port, but crashes on every machine at the pit phase. I tried heimdall and it complains that I don't have a matchine pit and I tried one that i found online and it is unable to write the pit file and just reboots the phone. I have been unable to manually flash anything from any point. Is there anything any of you can think of that I can try? I have heard of JTag and don't know much about it but read somewhere someone using and Arduino to do that, I have an arduino but its sound difficult due to size of the interface plug. Please help, phoneless and scared!!!
Click to expand...
Click to collapse
adb.exe works when the phone is in download mode. If you can get into 3e recovery you can factory reset. That usually clears up some issues.
I would try the reset, then go to a virgin pc running win 7 - the drivers are already in that os.
Connect with phone in download mode, run odin3 1.85 as administrator, flash a stock rom.
Hello.
I have a GT-i9100. It gets stuck in a bootloop, won't let me access recovery mode but it does go into download mode. I have the usb that came with it which I've used for file xfer a lot without any issues. When I try to flash it with odin, odin won't recognise my phone. I have samsung drivers installed and I'm running windows 7. I tried to connect it to 2 different PCs. Is there anything at all that I can do to save my phone? I wanted to flash it so I can try recover some of old photos I have on it. I don't particularly care to make the phone itself usable again as long as I can recover my files.
Thanks for your help.