Related
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
Hey guys I have recently tried flashing the biohazard ics kernel thru clockwork but now that I've done that the phone won't boot but mow when i try to restore my previous rom it says there's an md5 mismatch and when i try to install a rom from the internal card I get a can't mount emmc message. Also since i installed the standard ice rom odin only read my phone when it was turned on. Have I bricked my phone???
If you can still get into download mode, you have not bricked your phone. Just flash an original firmware, root it and try again with the restoration.
I have the firmware but if odin won't detect my phone do i need to reinstall the drivers or get a new cable.
kn1v3z said:
I have the firmware but if odin won't detect my phone do i need to reinstall the drivers or get a new cable.
Click to expand...
Click to collapse
what do you mean if?? pls explain your situation more clearer
try reinstalling drivers. and before opening odin, kill all kies related tasks in task manager. then open odin. then connect phone while in download mode
whenever i was running the previous rom, odin would only detect my phone when it was booted normally but not when i would go into download mode and since i can't pull roms off my sd card because i get a can't mount /emms/ i've never gotten that error message before.
Don't connect your phone to odin, since you have no proper kernel installed Odin won't detect any drivers.
Go to recovery mode and reflash stock kernel stored on your phone(assuming you have stored a kernel).
If you haven't then use Heimdall Suite to flash recovery mode again, use link below for reference:
http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_II:_Full_Update_Guide
i reinstalled the samsung drivers and heimdall doesn't detect my phone either :/
What is the "biohazard ics kernel" ?
Try a different cable, different usb port and different computer.
it's an ice cream sandwich kernel created by biohazard and ever since i cant't boot up and clockwork can't detect my removable sd which is where all my backup files and other roms are. I've already tried about 3 different cables and all ports the only other thing is to find a desktop and see if that works...I have a feeling i might have to buy another phone since my phone so far can't be detected in download mode anymore.
So what exactly happens when you put your phone into download mode (power off phone, then hold volume down and home button while booting it) then plug it into the computer?
Does the computer detect it, does it try to install drivers?
the computer detects it but odin won't detect it unless you've installed kies on your computer
kn1v3z said:
the computer detects it but odin won't detect it unless you've installed kies on your computer
Click to expand...
Click to collapse
Uninstall kies, download the samsung phone drivers from my 4shared (the 4icon in my sig), install them, put phone into download mode, plug into computer.
still no luck...
When simply powered on, Odin will recognize my tab (10.1 WiFi Only 7510). But will not recognize in DL mode... grrrrr. Any suggestions?
Have you tried to uninstall and reinstall the drivers on the PC?
Yes, I did. Reinstalling the drivers did not work. I tested with USB debug off, this did nothing in Odin either.
kamgrn said:
I tested with USB debug off, this did nothing in Odin either.
Click to expand...
Click to collapse
Of course it wouldn't; toggling a USB debug setting on the device while booted into it's operating system will have no affect on how the device is going to work in download mode as download mode is completely independent from the operating system itself. It's like comparing a PC's BIOS to an installation of Windows or Linux on the PC.
Your issues with Odin and download mode are most likely on the PC side and NOT on the tablet side. The Samsung drivers are very temperamental. Sometimes they don't play well with other devices and sometimes they don't work well with certain chipsets or USB controllers. My suggestion is try different USB ports, avoid using USB HUBs and try reinstalling drivers as well as disabling antivirus on the PC temporarily.
It may even be advantageous to have device manager open while you connect the tab in download mode to see how the PC is recognizing it. The tab should never be connected while you're attempting to get into download mode, leave it disconnected and have Odin fired up and prepped until you get the tab in download mode. Seeing how device manager picks it up might help diagnose driver issues.
same problem, varios computers
Hello everyone! I also have this issue whereas my gt-p7500 dont even exists to the system in download mode. I tryed 3 computers so far, even on linux in download mode heimdall wont recognize the tablet. what I have done so far:
(on 1st pc win7)
- installed kies, and updated to latest version. On normal mode the tablet gets recognized, all drivers install throught the end, kies works fine, managing folders and files as storage device also works fine.
- turned on usb debugging, and connected to pc again. A new driver MPC is installed, kies still works, pc communication also.
- rebooted the device in download mode, and after this conected again to the pc. Nothing new is detected.
-- Odin can see the device on normal mode, and if its turned off (charge mode) but on download mode nothing happens.
(on 2nd pc, win 7)
- didnt install kies, only samsung drivers
- inserted the tablet in 3 ways on the cpter, normal node, normal mode with debugging on, and download mode to all new devices and drivers to be detected.
- odin dont work on download mode, but can see the tablet as the example above, normal mode, normal mode with debug on and turned off (charge mode)
(3rd pc, debian 64)
- installed heimdall via git, latest package. Also wont detect the device on download mode, whereas it can see the tablet on normal mode.
on 3 pcs, tryed ALL usb ports, tryied openning odin first, and then connecting the device, tryed conecting the device first and then openning odin... nothing works while in download mode.
also Iv reseted the device to factory defaults to test, nothing changed.
On the first pc iv also tryed downloading older drivers versions from samsung, spreaded all over xda foruns on other threads. the oldest version Iv tryed was 1.4.x,
Please helpe me on this, cant figure out how to get the device detected in download mode on the pc... getting very annoyed on this already, and tryed all the possibilities I could imagine so far.
Are you using a laptop? Bcz pc can iddntify. I also had same problem with my laptop. It was recognizinging it as media device but not in download mode. So try to cknnect it to the CPU of the Pc
HIT THANKS WHENEVER POSSIBLE OR IF I HELPED YOU...
Not necessarily computer related, past experience for me has shown that not all versions of Odin work with this tab......the newer versions are NOT so good
Try this version uploaded and these drivers - try odin first if you are sure of your drivers, otherwise install the drivers first
Let us know how you go....
stinky73 said:
Not necessarily computer related, past experience for me has shown that not all versions of Odin work with this tab......the newer versions are NOT so good
Try this version uploaded and these drivers - try odin first if you are sure of your drivers, otherwise install the drivers first
Let us know how you go....
Click to expand...
Click to collapse
Hi
I had the same issue and those files solved it
Thank you
Samsung Galaxy TAB P1000(Ordin detection in DOWNLOAD MODE)
Initially google SAMSUNG_USB_Driver_for_Mobile_Phones_x86 . Download the file in your pc or laptop and install it. Then switch-off the tab and Press power and Volume down button simultaneously to get into the download mode. This time Samsung tab would be detected in the Ordin.
Hi I have galaxy tab 10.1 GT P7510, Odin don't recognize
Hello..
I have a Galaxy S plus (GT I9001), I installed TIGER-JELLY BEAN v8 recently, which was working fine. But phone was lagging a lot so I decided to install the stock rom again. I installed Kies(latest version) with drivers and connected my phone to my PC, but it was not detected by Odin. Every time I got Samsung Composite USB Device driver installation failed. So I searched and installed drivers from Here and Here. But they didn't worked either. I tried again after changing USB Cable but still no luck. Then I installed Kies in my Laptop and tried to connect the phone. Still it wasn't recognized.
Things were not working with downloading mode and Stock rom tar file cannot be flashed with recovery mode. So I searched a converter for .tar to flash able .zip file and found THIS . I installed this tool and tried to convert the tar file to zip. Didn't noticed that it require knowing "Mount Point", so I converted the tar file to zip without changing the mount point and copied the file to internal storage of phone and flashed the zip file. After that phone restarted , and stuck at Samsung Logo.
New I can't even to recovery Mode, nothing happens when I keep Pressing Vol Up + Power. Phone starts and stuck at samsung logo. Odin was already not detecting the phone so I tried connecting the phone on Ramdump Mode and some how drivers were installed and odin detected it correctly. But odin can't flash phone in ramdump mode so it didn't worked.
So now the problems I am facing are:
1- Phone is stuck at samsung logo, can't go in recovery mode.
2- Odin not detecting phone in downloading mode.
Is there something what I can do to fix this?
Please help!
Thank you.
This latest tool also allows you to boot your Samsung Smartphone and tablets into the download mode without pressing the physical keys. If in case your Samsung device physical keys are not working, then this latest Samsung tool is useful for all of you. The best thing about this tool is that it is not necessary to have the USB debugging active. The tool only detects your device and restarts it in download mode to do the flashing by ODIN.
How to use Samsung 300K Tool
This latest tool is useful for those users who have Samsung devices that do not enter download mode with the failure of keys.
After download file is complete simply Run for install.
Make sure that the Samsung drivers are installed
Before connecting the device open the program and the following screen instructions.
Now connect your device to the computer and make sure that the cable is properly or correctly connected, and the screen will change.
In this last step click on the figure of the image where the strain point and your cell phone connected or not enter the download mode quickly in 2 seconds, but I recommend doing the operation with the phone is connected.
Done.
Admin Edit: Attachment has been removed as it was flagged by Google as "uncommon download". Also locking thread.
speechless said:
This latest tool also allows you to boot your Samsung Smartphone and tablets into the download mode without pressing the physical keys. If in case your Samsung device physical keys are not working, then this latest Samsung tool is useful for all of you. The best thing about this tool is that it is not necessary to have the USB debugging active. The tool only detects your device and restarts it in download mode to do the flashing by ODIN.
How to use Samsung 300K Tool
This latest tool is useful for those users who have Samsung devices that do not enter download mode with the failure of keys.
After download file is complete simply Run for install.
Make sure that the Samsung drivers are installed
Before connecting the device open the program and the following screen instructions.
Now connect your device to the computer and make sure that the cable is properly or correctly connected, and the screen will change.
In this last step click on the figure of the image where the strain point and your cell phone connected or not enter the download mode quickly in 2 seconds, but I recommend doing the operation with the phone is connected.
Done.
Click to expand...
Click to collapse
The attached Samsung 300k file gives a CRC error when extracted. also its an exe and doesnt run on Windows 10. Is there an equivalent file that will allow my samsung galaxy T4 (sm-231 v4.4.2 Kitkat) to enter download mode? Its home key is not working right now. Using ADB i am able to enter Manual mode, but not Download mode! So ODIN does not recognize it ( ID:COM is not highlighted). I have installed the latest Samsung USB drivers.
any help will be most appreciated.
sifar786 said:
The attached Samsung 300k file gives a CRC error when extracted. also its an exe and doesnt run on Windows 10. Is there an equivalent file that will allow my samsung galaxy T4 (sm-231 v4.4.2 Kitkat) to enter download mode? Its home key is not working right now. Using ADB i am able to enter Manual mode, but not Download mode! So ODIN does not recognize it ( ID:COM is not highlighted). I have installed the latest Samsung USB drivers.
any help will be most appreciated.
Click to expand...
Click to collapse
When the phone is booted up normally and the way you would normally use it, when you connect your phone and open ODIN, does it still not pick up the phone on the COM port?
And (I'm sure you do), do you have USB debugging turned on and all the other usual things (like you mentioned, having installed the latest drivers)?
Samsung galaxy tab 4 (sm-t231) kitkat v4.4.2
Max_Terrible said:
When the phone is booted up normally and the way you would normally use it, when you connect your phone and open ODIN, does it still not pick up the phone on the COM port?
And (I'm sure you do), do you have USB debugging turned on and all the other usual things (like you mentioned, having installed the latest drivers)?
Click to expand...
Click to collapse
yes, i finally used "adb reboot download" to boot into download mode. Now when i am using ODIN and trying to root my cell by installing TWRP 3.2.1-0-degas.img.tar, it says PASS (success 1/fail 0), but my mobile still shows "DOWNLOADING..." with a horizontal blue line. I can also reboot and load normally, but it seems TWRP has not got installed and still ROOTCHECKER says my mobile is not rooted. Am i using the wrong versions of TWRP recovery or ODIN etc? Can you advice next steps?
sifar786 said:
yes, i finally used "adb reboot download" to boot into download mode. Now when i am using ODIN and trying to root my cell by installing TWRP 3.2.1-0-degas.img.tar, it says PASS (success 1/fail 0), but my mobile still shows "DOWNLOADING..." with a horizontal blue line. I can also reboot and load normally, but it seems TWRP has not got installed and still ROOTCHECKER says my mobile is not rooted. Am i using the wrong versions of TWRP recovery or ODIN etc? Can you advice next steps?
Click to expand...
Click to collapse
When you've flashed TWRP, the phone will stay in download mode. Nothing will change on screen, that is normal. You have to reboot the device manually, using the button combination it says, then immediately as the device restarts, you change the combination to boot into TWRP. All of these steps are explained in whichever thread or wherever you found TWRP.
As far as rooting is concerned; TWRP doesn't inherently root the device. It just replaces the bootloader to allow you to flash custom packages, like the one needed to root the device.
If you're struggling to get the device rooted and there isn't a very specific reason why you need root, then my best recommendation would be to rather just leave it stock.
As far as I know, flashing TWRP won't trigger Knox, so you'll still have that functionality. Recently, it's become less and less necessary to have root and fewer apps require it, as well.
Like I said, unless there is a very specific reason, you'll likely be better off just leaving it the way it is.
EDIT: I'm realising now the original problem was that your home button wasn't working. In that case, it'll be difficult to get into TWRP, anyway. I also made some assumptions about Knox, because this is on the Note8 sub forum. I don't know if your device has Knox. And You're on a rather old version of Android also, so I understand why you may want to root, but without your home button working, it could become difficult to get into the places where you need to be to make that possible.