I tried flashing CWM recovery onto my AT&T Galaxy S4 and because my phone does not connect to my computer via USB for some reason (the phone charges and my computer recognizes that there's a device in, but I cannot actually do anything with it) I flashed it with Flashify. I rebooted into recovery mode, and I got slapped with the "Unauthorized software has been detected on your phone!" message. So I tried rebooting, and I got stuck in a recovery mode bootloop with the same message. Eventually, I realized if I just go into download mode and reboot by pressing the volume down key, it doesn't try to go into recovery mode. I have already endlessly researched my USB problem, and yes, I DO have USB debugging on. ODIN recognizes that I have an external device in as well, but I haven't tried flashing anything onto my phone with it because I don't want to brick my phone because the connection to my PC is faulty. I'm using the charger that came with the device as my USB drive, so that's not faulty either. I know rooting my phone did this, and I'm pretty sure it's because I missed a step. I used this tutorial to root my phone:
[droid views dot com] /root-att-galaxy-s4-sgh-i337-android-4-4-4-kitkat-firmware-i337ucufnj4/ (I'm not allowed to post links yet, so fix the URL if you're gonna have a look)
When I flashed the I337_NC1_Stock_Kernel, my phone refused to go into download mode and I couldn't flash the I337_NJ4_Stock_Kernel as a result. I'm pretty sure that's what caused it, but I have no idea how to fix it. I'm not an expert with my phone and, despite almost soft-bricking my phone via a corrupt CWM .zip, I'm not a newbie at this either. If I could figure out how to fix this problem, I wouldn't have to worry about throwing myself into a bootloop because I can just use ODIN. I was a sitting duck before download mode rescued me, so I'd like some help as to how I can accomplish this. Any and all help is appreciated. I am 100% certain my device is the right version for that tutorial, I wouldn't try to root my phone without checking all of the simple things first.
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
Hi All,
I am having an issue with my S4 that when I plug them into my computer I get USB device not recognized. I have searched the forum for the past 2 days trying all kinds of different solutions the major one was changing my USB/charging port board on my phone.
I need to ODIN my device to an MJ7 image. At first I got the error and did a factory reset through safestrap recover. Still got the error so I did an advance wipe of every option. (Looking back shouldnt have done that) That took away my recovery, but I can get to download mode, but its not detected by my computer to use ODIN with. So I am stuck without a custom recovery without the ability to boot into anything.
Here is what I have tried so far:
1. Reinstall/uninstall drivers, reinstall/uninstall kies.
2. Changed USB ports on computer.
3. Changed USB cables
4. Changed computers from Win 8 x64 to Win 7 x64.
5. Changed computer to my MACbook using Heimdall.
6. Changed USB charging port board on my phone.
7. Tried everything again. *Still doesnt detect it*
Any ideas that I havent done already, or how to fix? I do have nandroid backup of my ROM, but dont have a custom recovery to flash it.
Cant ODIN back cause its not detected by my computer. Thanks in advance for your help.
Is USB debugging still checked on phone? You must use the USB cable provided with phone...
safestrap enabled, Hyperdrive driven
Thanks for the reply. I cant select USB debug on my phone because my phone does not boot into the main OS, it is stuck at the samsung custom padlock screen. The USB debug option was on when the OS was installed though. My phone will only boot into stock recovery and into download mode. I tried to use the original USB cable provided with the phone as I read this could be the problem, but I tried 4 other ones too and phone still gets detected as "Unknown Device" in device manager, so ODIN cant even see phone in download mode to restore. I have tried to install KIES and the Samsung Mobile phone drivers 1.5.x.x drivers. Just read somewhere where someone had this issue and installed Samsung mobile phone driver v1-4-6-0 so I am trying that now.
odlay75 said:
Thanks for the reply. I cant select USB debug on my phone because my phone does not boot into the main OS, it is stuck at the samsung custom padlock screen. The USB debug option was on when the OS was installed though. My phone will only boot into stock recovery and into download mode. I tried to use the original USB cable provided with the phone as I read this could be the problem, but I tried 4 other ones too and phone still gets detected as "Unknown Device" in device manager, so ODIN cant even see phone in download mode to restore. I have tried to install KIES and the Samsung Mobile phone drivers 1.5.x.x drivers. Just read somewhere where someone had this issue and installed Samsung mobile phone driver v1-4-6-0 so I am trying that now.
Click to expand...
Click to collapse
Tried Samsung Mobile phone drivers version 1.4.6.0 and still the same outcome "USB device not recognized". I went down to a local electronics store and bought two different brand microUSB data cables. Tried them both along with my original one from samsung, and still the same result. Any other ideas??
Anyone else have any ideas? Thinking of sending it in and having it JTAG'ed back to stock. Can anyone recommend any services? Heard mobiletechvideos is good.
odlay75 said:
Anyone else have any ideas? Thinking of sending it in and having it JTAG'ed back to stock. Can anyone recommend any services? Heard mobiletechvideos is good.
Click to expand...
Click to collapse
Go to Saferoot thread in dev forum...your answer may be there
safestrap enabled, Hyperdrive driven
Hello All,
I've been reading posts from here for a long time but this is my first post.
I'm coming here as a last resort to save my Galaxy s2 (SGH-T989) which has a stock ROM.
Here's what happened.
I dropped my phone and then it got stuck in bootloop (it only boots until I see the "SAMSUNG" word animation and stops there).
At that point, ODIN 'sees' that there's a connected device; KIES keeps "connecting...." but can't actually connect; ADB does not show any connected device.
So, what I wanted to do was to factory "reset" the phone. The problem is I can't get the phone into Recovery mode. I believe it's because my volume down button was acting up when the phone was working. However, I can get to "Download Mode" using a USB Jig.
So, the next thing to do is to flash a new stock ROM. However, whenever I connect my phone when it's in "Download Mode", ODIN does not see it.
Yes, I've installed, re-installed, removed, re-installed all drivers and Kies and I've done that so many times you can't even believe it.
The problem is that the device driver "SAMSUNG Mobile USB CDC Composite Device" gives the following error "This device cannot start. (Code 10)", and I don't know why or how I can get rid of that. As mentioned above, I've tried all the device driver installation fixes but none has worked.
I mean, when the phone is not in Download Mode and I connect it to my PC, all device drivers are working fine with no error, but when it's in Download Mode, I get the error mentioned above "This Device cannot start.".
So, my questions:
1) Is there a way to get to Recovery Mode without using the button combinations? (The phone is in bootloop)
2) How can I fix the device driver error mentioned above to get ODIN to see my device?
3) Is there anything else I need to be doing?
This problem is really frustrating and I've been on it for more than 2 weeks and nothing has worked so far. Any help is greatly appreciated.
1. I think you have flashed an bad kernel if you cant get into recovery mode and i dont get it why your volume down acts like up?.
2. http://support.microsoft.com/kb/943104 try to maybe also disable kies and try again.
3. Kies is on, adb doesnt work at samsung/download screen, try to reinstall samsung usb drivers again :/ yes I know but to be sure, disable driver signature or something like that if you are on windows 8.x, try another usb cable.
2weeks dont sound good. I hope these tips could help a bit but I still wonder why your phone got in bootloop when you dropped it !?!? What were you doing at that time and did the battery go out?
wulsic said:
1. I think you have flashed an bad kernel if you cant get into recovery mode and i dont get it why your volume down acts like up?.
2. try to maybe also disable kies and try again.
3. Kies is on, adb doesnt work at samsung/download screen, try to reinstall samsung usb drivers again :/ yes I know but to be sure, disable driver signature or something like that if you are on windows 8.x, try another usb cable.
2weeks dont sound good. I hope these tips could help a bit but I still wonder why your phone got in bootloop when you dropped it !?!? What were you doing at that time and did the battery go out?
Click to expand...
Click to collapse
Thanks for the quick reply, wulsic.
1. No, I did not flash any kernel on this phone, everything on it is stock and was working just fine before it was dropped. I meant that the volume down was not working properly, not that it was acting like up.
2. I tried that but did not work
3. The drivers are working fine when the phone is not in Download Mode, it's only when it's in Download Mode that I get the error and I've tried re-installing drivers and everything, I think the problem is with the device itself not a driver problem.
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.