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.
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
Uh hi.
I'm a herp.
So I may have accidently tried to root and flash my friend's Samsung Vibrant. It was going smoohtly but now, I'm all sorts of messed up.
The problem: I may have used the wrong kernel (zImage) when using heimdall-frontend (which I downloaded from xda). This is causing the phone to power on; it shows the Samsung Galaxy S 4g load screen, then Overstock, then the T-Mo logo sign (with the music), and then a longer Galaxy S load screen. After the load screen, the screen goes completely black, but all the touch buttons light up. Once like this, I can turn it off, and make it go back into recovery mode and also download mode.
Please help. I've been trying to solve this with my friend for about.. 4 hours.
P.S. I've looked up all the guides for using ODIN to get back to JFS, none works due to the reason that when I put it back into download mode, the computer does not recognize it. But it does at the same time. (it shows the "safetly remove hardware" and says that is an "USB mass storage device" ((but does not appear in "My Computer" when in the unresponsive screen-- but when in the download screen, it shows the same thing, only labeled "SAMSUNG USB Composite Device", which also cannot be accessed through "My Computer")
P.P.S. I'm sure it is a Samsung Galaxy S Vibrant, exclusive from T-Mobile. My computer is Windows Vista 32-bit, and I have as many Samsung drivers as humanly possible when it comes to the Vibrant.
Can anyone help a poor fool?
Try this, get in to download mode, open Odin, then disconnect the usb cable, then reconnect the usb cable and Odin should recognize it then. Good luck!
Using XDA premium, you should be too!
johnny12times said:
Try this, get in to download mode, open Odin, then disconnect the usb cable, then reconnect the usb cable and Odin should recognize it then. Good luck!
Using XDA premium, you should be too!
Click to expand...
Click to collapse
Sorry. That did not work. It just doesn't recognize it in ODIN when in download mode. My computer doesn't even see it. But it does say "Safely Remove Hardware" -- "SAMSUNG USB Composite Device"
Sounds really odd. Do you have any roms you can try reflashing from recovery?
Using XDA premium, you should be too!
depaer said:
Uh hi.
I'm a herp.
So I may have accidently tried to root and flash my friend's Samsung Vibrant. It was going smoohtly but now, I'm all sorts of messed up.
The problem: I may have used the wrong kernel (zImage) when using heimdall-frontend (which I downloaded from xda). This is causing the phone to power on; it shows the Samsung Galaxy S 4g load screen, then Overstock, then the T-Mo logo sign (with the music), and then a longer Galaxy S load screen. After the load screen, the screen goes completely black, but all the touch buttons light up. Once like this, I can turn it off, and make it go back into recovery mode and also download mode.
Please help. I've been trying to solve this with my friend for about.. 4 hours.
P.S. I've looked up all the guides for using ODIN to get back to JFS, none works due to the reason that when I put it back into download mode, the computer does not recognize it. But it does at the same time. (it shows the "safetly remove hardware" and says that is an "USB mass storage device" ((but does not appear in "My Computer" when in the unresponsive screen-- but when in the download screen, it shows the same thing, only labeled "SAMSUNG USB Composite Device", which also cannot be accessed through "My Computer")
P.P.S. I'm sure it is a Samsung Galaxy S Vibrant, exclusive from T-Mobile. My computer is Windows Vista 32-bit, and I have as many Samsung drivers as humanly possible when it comes to the Vibrant.
Can anyone help a poor fool?
Click to expand...
Click to collapse
Sounds like you used the wrong odin files. if your screen is showing a galaxy s 4g logo then you must have mistakenly flashed a galaxy s 4g odin/heimdall package. on the back of your phone what is the model number. What on earth is JFS? ive heard of JFD which is the stock firmware that the phone shipped with.
If you flashed the wrong bootloader you are more or less stuck between a rock and a hardplace and will require a jtag. now the fact that teh screen does turn on is a good thing.
You need to keep trying to get it into download mode maybe try using a jig. Once youve gotten it into download mode try every single usb port you can find on your pc. When i need to odin i need to use one of my usb ports on the rear io panel none of the others will work. Once you get odin running and recognizing your device use the files posted in my sig as the odin files. any others and i cant help you cuz i dont know what your source is. Odin should be able to recover your device if it is still booting to the splash screen.
If for whatever reason you cant boot into download mode but can get into recovery here is what you do: make sure you have the android SDK installed (dont know what that is go here: http://developer.android.com/sdk/index.html and follow their directions) then open up command prompt while in recovery type the following command: adb reboot bootloader this should put you into download mode. If nothing ive mentioned works you may require a JTAG there is a company called MOBILETECHVIDEOS (http://mobiletechvideos.mybigcommerce.com/) that has a JTAG service.
Good luck
-Cheers
Help mee.
I have bought a s3 that is locked to Orange, need to unlock, but odin does not see the phone in recovery/dl mode.
Odin see the phone in normal mode , but each time i put into start/+vol/home odin see nothing.
I have kies updated.
Thanks
crazydiamond1970 said:
Help mee.
I have bought a s3 that is locked to Orange, need to unlock, but odin does not see the phone in recovery/dl mode.
Odin see the phone in normal mode , but each time i put into start/+vol/home odin see nothing.
I have kies updated.
Thanks
Click to expand...
Click to collapse
I had a similar thing when i was plugged into a usb hub
Was ok when i plugged directly into the pc
Install Samsung Kies to be able your PC to detect your phone via Odin
also check the debugging mode in the developer options
bordikun said:
Install Samsung Kies to be able your PC to detect your phone via Odin
also check the debugging mode in the developer options
Click to expand...
Click to collapse
I have Kies, also tried debugging, i need root to unlock phone
Try to use the latest Odin
Odin v3.04
bordikun said:
Try to use the latest Odin
Odin v3.04
Click to expand...
Click to collapse
I have uninstalled the older Kies, re installed the latest.
I have installed the lastest odin.
Have tried to link up with and without debugging, odin still does not see phone when in recovery mode.
Only time odin see the phone when phone is in normal mode.
Starting to get annoyed now lol, i cant cut my sim to fit phone, untill this is done
I cant see my s2 on odin either, what am i doing wrong ????
1. Reboot PC
2. Ensure KIES is not running and kill any KIES processes in PC task manager.
3. Download mode
4. Connect USB directly to PC port (no hub)
5. Wait for any drivers to instal or load on PC
6. Start Odin in administrator mode
If still no good;
a) Different USB cable
b) Different PC USB port and wait for drivers
Sent from my GT-I9300 using xda premium
Thanks . Seems that I had been pressing volume up not down.
I have another question . I used chainfire Rom to debrand the phone but keis does not recognize . How can I solve this . Could it be because the phone is rooted ?
i am having this problem at the mo, I have tried all of the above, apart from a different pc.
oden worked fine with my galaxy s2
is there any more updates on how to sort this out please?
thanks
ian
I know this is a 7 day old thread, but I feel for you having been in the same situation. Firstly, have you installed the Android SDK? If not then I advise you to do so. Do a search on how to install the SDK. There maybe smaller downloads available with a package of the binaries you need to do some testing i.e. adb. The instructions will elaborate about how to set up your Environment settings in Windows. Essentially ADB needs to be called from within any part of your Windows system....or else you will have to cd to its location each and every time you want to do something like this. So once you have done that, open command prompt and type adb and see what comes up? If it says bad command or file name it means your environment settings for the ASK are incorrect, if it displays the adb help text in command prompt you are ready to proceed.
When you plug your device in (not in DL or recovery modes) is it detected by the PC? If so then your drivers are probably fine. If not then it maybe 1 of 2 things? 1 the device is detected but the MTP drivers have not been loaded or 2. No detection what so ever and all drivers need to be installed.
To determine how to proceed you will need to do a bit of investigating.
Note the USB drivers are included as part of the Android SDK.
Check in Device manager inside of Windows to see if anything is detected when you plug it in. If so but it has a yellow exclamation ! then it would indicate you need to update your drivers (but not always?). From here you can test to see if the phone is detected and you only need MTP drivers.
If not then I would suggest uninstalling Keis all together and downloading and installing the Samsung USB drivers separately. Install the drivers. Plug in the phone. If it is not detected straight away, then reboot the PC then plug the phone into a different USB port. From here you can determine how to proceed by using adb.
plug your phone in via USB and open command prompt and type this: adb devices
You should see 1 of 2 things.
1) The words "list of devices attached" followed by a 16 digit long ID number a gap and the word "device"
2) just the words "list of devices attached" and then blank and nothing else?
If a device ID is returned then you can proceed with the following. Otherwise you need to do some additional trouble shooting
Proceed here:
Once it is detected by Windows and shows up in Explorer then unplug the phone and go into settings and developer options and check enable USB debugging. Once you have done this it should allow your device to be seen in DL and recovery modes.
Troubleshoot: If not detected try the following:
1) Reboot the PC and plug into a new USB port that you have not previously plugged into.
2) Try disabling USB debugging plugging the device in and then unplugging it and reenabling USB debugging
3) From the status bar try switching modes between MTP and PTP modes. Wait a good minute or so between to allow Windows to detect the driver change. Tip a good indication is your notification tray Icon with green USB disk with a magnifying glass swirling around....Note if you cannot see this at all you probably should drag it into the notification panel so that you CAN!
4) Open up device manager again and ensure no yellow exclamation marks !
Once all this is right and you can get List of devices attached followed by an ID number then you can for sure be able to detect your device from Odin. Make sure you are running Odin 3.04, run it as admin (not necessary but have heard that it helps?)
Good luck
James
I have an S4 Active that NO MATTER WHAT I DO, Odin will NOT see phone in Download mode, it will with the phone on, and my PC will see the phone, but not Odin. I am stumped. I have tried 3 PC's, I have ALL the drivers and then some. I am Stumped.
rekamyenom said:
I have an S4 Active that NO MATTER WHAT I DO, Odin will NOT see phone in Download mode, it will with the phone on, and my PC will see the phone, but not Odin. I am stumped. I have tried 3 PC's, I have ALL the drivers and then some. I am Stumped.
Click to expand...
Click to collapse
have you tried factory resetting the phone?
afasayan said:
have you tried factory resetting the phone?
Click to expand...
Click to collapse
Several times
rekamyenom said:
Several times
Click to expand...
Click to collapse
You can try with minimal/no drivers i.e. uninstall kies if you have it and delete the drivers you might have installed on your own-it sounds counter productive but it has worked for me a few times.
You can also try to either install kies or the drivers separately.
Try the forum for your own phone, the people there might know better about this problem.
Also what OS are you on?
afasayan said:
You can try with minimal/no drivers i.e. uninstall kies if you have it and delete the drivers you might have installed on your own-it sounds counter productive but it has worked for me a few times.
You can also try to either install kies or the drivers separately.
Try the forum for your own phone, the people there might know better about this problem.
Also what OS are you on?
Click to expand...
Click to collapse
I will give all that a try. I'm on 4.4.2 build NH3. That's why I need Odin, to get back to build NE3
rekamyenom said:
I will give all that a try. I'm on 4.4.2 build NH3. That's why I need Odin, to get back to build NE3
Click to expand...
Click to collapse
By OS I meant the computer's OS.
afasayan said:
By OS I meant the computer's OS.
Click to expand...
Click to collapse
I have tried several computers using Windows 7 and Windows XP both 32 and 64
I have a Samsung Galaxy S3 from T-Mobile and I tried rooting the phone using the procedure below obtained form an external link as I was running Android 4.3:
**********************************************************************************
Requirements:
T-Mobile Samsung Galaxy S3 SGH-T999 with USB data cable
CF-Root zip package (Download HERE)
Also download Odin3 v3.09 Flashing Utility
Make sure that you’ve installed USB drivers on your PC.
Go to Phone Settings>Developers Options and Enable USB debugging.
Before you start rooting your phone, make sure that you’ve got good enough battery charge.
Last but not the least, Proceed at your own risk.
How to Root T-Mobile Samsung Galaxy S3 (SGH-T999) on Android 4.3 Jelly Bean Firmware
1. First of all, extract the CF-Auto-Root-d2tmo-d2tmo-sght999.zip and Odin v3.09 files to a new folder on your desktop.
2. Now from the extracted folder run Odin3-v3.o9 application on your PC.
3. Next Reboot your T-Mobile Galaxy S3 into Download Mode:
Turn Off Galaxy S3.
Press and Hold down the Volume Down+Home+Power buttons at the same time till you see a warning on your screen.
Further hit the Volume Up button to continue.
4. While in download mode connect your GS3 to PC via the USB data cable. Just make sure that Odin3 detects your device.
5. Also make sure that only Auto Reboot and F. Reset Times options are checked and rest leave the default Odin settings.
6. Finally click the PDA button and from the extracted folder select the CF-Rooted kernel file and hit the START to flash the kernel.
7. Wait for Odin3, When completed, Odin will notify you via the PASS!! message in Odin and at this stage your phone will automatically reboots.
**********************************************************************************
I used Odin3 v3.09 and got a "Pass" message at the end and the phone rebooted as stated in the instructions.
However, it seems that my phone starts up but doesn't load completely. I have device encryption on my phone (as required by work to access work e-mails) and have to enter a password before I can get to my lock screen and though I can enter my password to get past the first lever of encryption, it doesn't load past the Android screen. The snapshots below show both the password entry screen and the android screen on which my phone freezes and doesn't load past.
My question is, is the website above lacking in some directions and did I mess anything up? I'm assuming the phone is not bricked as it still is able to turn on and I'm able to still enter passwords. Is the only way to correct this through a hard factory reset perhaps?
Any assistance on getting the phone up and running would be appreciated!
You might want to ask in correct forum, this is i9300 (int'l s3) forum.
Hopefully this is the right place to post this.
I have a Samsung Galaxy S4 (completely stock as it is my work phone), however I have some personal data on it (photos etc.).
The screen and digitiser are completely broken, however the phone still boots; I'm just unable to see what is occurring, or interact with the device.
The device broke without USB debugging enabled, so I am unable to use adb to access the device. I have tried booting into both recovery and download modes (but I have been unable to access using adb regardless of mode). The device is also not set to act as USB mass storage, so it only displays as a media device within Windows.
I have also tried using Kies to access the data, however I receive a message saying that the phone needs to be unlocked. Obviously I am unable to do this, as neither the screen nor adb commands work. Using the Samsung website to unlock the device is out of the question too, as I do not have a Samsung account.
In addition, I have tried booting into download mode and using ODIN to flash ClockworkMod to the device, but ODIN was unable to connect.
I do not have another S4, so swapping the screens temporarily isn't possible, and obviously using an OTG mouse wouldn't work, as I cannot see the screen.
I am really at a loss here, is there any way I can get the data off of this device?
Any help is greatly appreciated.
Only way without replacing the screen is going to be a custom recovery and adb at this point. I'm hard pressed to understand why Kies recognizes your phone but Odin doesn't. Only thing I can think of is that once you boot to Download Mode via Power + Home + Volume Down is that starts the caution message about installing custom stuff and you need to hit Volume Up at that point to continue to actually be able to use the mode. Either that or check your Device Manager for driver issues as the driver loaded for that is a little different than like for MTP.
es0tericcha0s said:
Only way without replacing the screen is going to be a custom recovery and adb at this point. I'm hard pressed to understand why Kies recognizes your phone but Odin doesn't. Only thing I can think of is that once you boot to Download Mode via Power + Home + Volume Down is that starts the caution message about installing custom stuff and you need to hit Volume Up at that point to continue to actually be able to use the mode. Either that or check your Device Manager for driver issues as the driver loaded for that is a little different than like for MTP.
Click to expand...
Click to collapse
The only way I can tell it is in any mode other than normal boot is due to the red LED. After the first vibrate I repeatedly pressed Volume Up to ensure I'd got past the disclaimer, but obviously I'll never know for sure.
I found a tutorial for flashing CWM, however it was for an older version of ODIN (3.07). It mentions to put the CWM tar file in the "PDA" field, however this field is not present in the newer version (3.10 I think?).
As such, I was unsure how to proceed.
PDA is now the AP slot in newer versions of Odin.
Thank you, I'm going to give it another go today.
Does the device need to be rooted in order to use ODIN? I've used it once before but it was a long time ago, so I don't fully remember.
I also don't want to void the warranty on the device, as it's technically not mine.
Root is not necessary to use Odin, however, if you are able to install a custom recovery, and your phone has Knox, it will be tripped, thus voiding the warranty. There are plenty of people who have returned phones with it tripped without issue, but no way to guarantee they won't care. Most likely since it's obviously a physical issue, and not from any attempt at modding, they shouldn't care. However, they do reserve the right to refuse warranty claims if they so chose.
Just in case anyone comes across this via Google, I managed to get my files using the following method:
First, I loaded up Samsung Kies on my PC, and plugged in a standard USB male to microUSB male cable.
Then I used an OTG adapter (USB female to microUSB Male) and plugged a USB keyboard into the phone. After a few attempts, I felt the phone vibrate when I typed my PIN in and pressed return.
I then quickly unplugged the OTG cable from the phone, and plugged in the PC USB cable. This allowed Kies to connect to the phone, and I was able to pull my files.
Hopefully this helps someone if they are having the same issue.
Good work! Glad you were able to find a solution.