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
Hi guys, was having a few problems with my phone and decided that I'd flash the stock ROM again.
Went into ODIN as you do, and as I was flashing the stock ROM, for some reason or another I heard the disconnect/reconnect noise that Windows makes when you remove a device then FAIL came up in ODIN.
Now my phone's stuck with a phone connecting to a computer on the charge screen, it can't go into recovery mode but it can go into download mode.
Tried connecting it to my PC in download mode, and even though I've got the Samsung USB Drivers installed I get the 'USB Device Not Recognized' message, which means I can't flash the stock ROM in ODIN anymore.
Does anyone have any advice? Thank you.
JoshS2 said:
Hi guys, was having a few problems with my phone and decided that I'd flash the stock ROM again.
Went into ODIN as you do, and as I was flashing the stock ROM, for some reason or another I heard the disconnect/reconnect noise that Windows makes when you remove a device then FAIL came up in ODIN.
Now my phone's stuck with a phone connecting to a computer on the charge screen, it can't go into recovery mode but it can go into download mode.
Tried connecting it to my PC in download mode, and even though I've got the Samsung USB Drivers installed I get the 'USB Device Not Recognized' message, which means I can't flash the stock ROM in ODIN anymore.
Does anyone have any advice? Thank you.
Click to expand...
Click to collapse
Try installing samsung kies. The usb drivers are included.
princeownt said:
Try installing samsung kies. The usb drivers are included.
Click to expand...
Click to collapse
I have it installed, and I installed the USB drivers from the soft bricked sticky in this section. Neither have helped.
Hi!
Hi, you guys install ADB on your system? And also USB debugging mode on the phone?
Should be turned on which can be done by going to Settings>Applications>Development and select USB debugging.
Try this, for me its works
MafiaDroid said:
Hi, you guys install ADB on your system? And also USB debugging mode on the phone?
Should be turned on which can be done by going to Settings>Applications>Development and select USB debugging.
Try this, for me its works
Click to expand...
Click to collapse
I can't even turn the phone on at the moment. Only thing I can do is go into Download mode.
Help
Try this, take out the battery, then press and hold the ON button for 7-10 seconds (the longer the better). Reinsert the battery, then press ON button to start it. This is a soft reset, and wipes the temporary memory and empties all remaining power in the circuits. This helps on many phones and even laptops that won't start properly or show anything on screen.
If this does not work, try the next step. Again, do as above. But after inserting the battery, do not turn the phone on, but press and hold the ON button and the HOME button at the same time for 7-10 seconds. This is a hard reset, and works best if done after a soft reset. Just be sure the battery has at least some juice in it and isn't empty. If possible, try with another battery if this does not work.
Hope this helps!
Try going to device manager, you will probably find your device as an unrecognized device, uninstall the drivers, unplug and then plug it again and see.
if the prblm is hard then do a fresh installation of kies,device etec etc.....but if u have ur device in the device list on pc then first uninstall it...if possible try recovery mode and reset...
I tried everything you guys have suggested and none of that worked. Anyone else got any ideas?
Try everything (and I mean everything) on the following list. Given the problems you've had & that you've already tried some of these things, I'd try another PC. And if it doesn't work first go on another PC, then go thru the list & try everything on the 2nd PC.
*Ensure Kies & it's processes aren't running in Windoze task manager. Kill them if they are.
*Try different USB ports; you must be using a 'powered' or mainboard port.
*Try different USB cables (particularly the cable that came with the phone if you're not using it now)
*Try different versions of Odin (search on here/Google)
*Uninstall Kies, reboot, redownload & reinstall it, reboot, try the flash again. Also run Windoze Update.
*And if all this fails, try a different PC.
Tried all the above and a different PC.
It didn't work. I could fix the phone if the computer would pick up that the phone's connected - it just doesn't.
Total Removal of KIES including registry entries .
Reboot PC install a new copy of Kies .
Phone backup data and factory reset .
Set phone to USB storage mode using the Samsung cable connect to PC and wait for Windows to find USB drivers .Remove cable reboot phone .
Start Kies connect with cable wait for Kies to find the phone .
Note USB Debugging OFF and cable connects to a direct motherboard port only .
Nothing then only further suggestion would be to Format the PC and start over with a clean Windows install .
jje
I can't turn the phone on, it's stuck on the phone, triangle, PC screen.
I've tried fresh installs on three different PC's.
JoshS2 said:
I can't turn the phone on, it's stuck on the phone, triangle, PC screen.
I've tried fresh installs on three different PC's.
Click to expand...
Click to collapse
That's a forced download mode.
Try a blind flash to a stock firmware from Odin while connected to your computer with the phone on this screen. Even if Odin doesn't seem to register that it's connected. I've heard of at least one person this worked for.
At this point, you really have nothing to lose by trying this.
Bit of an update, I plugged it in again and it installed some drivers and ODIN picked it up. Only for it to disconnect a few moments later, now it keeps disconnecting and reconnecting over and over but ODIN's not picking it up.
JoshS2 said:
Bit of an update, I plugged it in again and it installed some drivers and ODIN picked it up. Only for it to disconnect a few moments later, now it keeps disconnecting and reconnecting over and over but ODIN's not picking it up.
Click to expand...
Click to collapse
I know you said you tried a different cable, but that sounds suspiciously like a bad cable.
It's not the cable, thanks any way.
Update 2: I managed to get it to connect long enough to flash the stock Kernel. Still didn't reboot. Then I connected it again and flashed the stock ROM, which bricked it again. Then I flashed the stock kernel and it works!
However, there is a problem:
When the phone gets turned off, it constantly shows the charging battery icon with warning triangle and a thermostat next to it. I can't turn the phone on because of this unless I go into Recovery mode and reboot system.
Any ideas? Thanks.
JoshS2 said:
It's not the cable, thanks any way.
Update 2: I managed to get it to connect long enough to flash the stock Kernel. Still didn't reboot. Then I connected it again and flashed the stock ROM, which bricked it again. Then I flashed the stock kernel and it works!
However, there is a problem:
When the phone gets turned off, it constantly shows the charging battery icon with warning triangle and a thermostat next to it. I can't turn the phone on because of this unless I go into Recovery mode and reboot system.
Any ideas? Thanks.
Click to expand...
Click to collapse
Now this sounds like a faulty/dirty/bad usb port.
ctomgee said:
Now this sounds like a faulty/dirty/bad usb port.
Click to expand...
Click to collapse
This was my original thought and my reasoning for flashing a stock ROM in the first place!
JoshS2 said:
This was my original thought and my reasoning for flashing a stock ROM in the first place!
Click to expand...
Click to collapse
I in no way recommend this, and not sure I would do it if I ever started having this issue...
BUT - I have heard that some people faced with this condition have fixed it by physically moving the small wafer board inside the USB port with a precision screwdriver (gently!) to a more "centered" position.
If that doesn't work, look at replacing that part. Either via warranty service if you still have it, or a service center.
So I tried the S off and I failed a couple of times with the wire trick. My timing was more than likely off. I re-ran the program and tried again. After it rebooted to check my alcohol level like it had the time before it could not find the device. It just kept counting to 45 secs over and over and kept asking me to check device drivers and adb and fastboot. And it worked fine before. Before I even started I checked adb devices.
Now the phone boots to the juopunutbear screen and it when I try to run the program it says that the device is not detected. So I rebooted in hboot and tried to run some adb or fastboot commands and the phone is not detected at all. I tried my mac too and no luck. I tried a different usb cable and no luck either.
So no I cant push anything to my phone and its just reboots to the juopunutbear screen. I think I bricked it. I dont know what to do. I cant push files to the phone. Any help?
DeviceSettings said:
So I tried the S off and I failed a couple of times with the wire trick. My timing was more than likely off. I re-ran the program and tried again. After it rebooted to check my alcohol level like it had the time before it could not find the device. It just kept counting to 45 secs over and over and kept asking me to check device drivers and adb and fastboot. And it worked fine before. Before I even started I checked adb devices.
Now the phone boots to the juopunutbear screen and it when I try to run the program it says that the device is not detected. So I rebooted in hboot and tried to run some adb or fastboot commands and the phone is not detected at all. I tried my mac too and no luck. I tried a different usb cable and no luck either.
So no I cant push anything to my phone and its just reboots to the juopunutbear screen. I think I bricked it. I dont know what to do. I cant push files to the phone. Any help?
Click to expand...
Click to collapse
I'm not sure what's happening with your computer not seeing the phone, but if you have a microsd adaptor you could get a stock RUU onto your card and flash back to stock.
Edit: or just your boot.img. If you can get into hboot you're not bricked.
Part fix
As previous poster said, put a PH...IMG with boot on it and you'll be able to boot up again. Yours is third phone reported here with USB problem after failed S-0ff.
I can boot my rom, but no radio or wifi, No charging, and no computer can see it for fastboot. Hoping for cure soon.
Thanks guys. I am downloading an RUU now. Hopefully it works. I hope the usb connection is not fubar'd ...but i took the risk so its on me.
Same thing happened to me. I just finished uninstalling HTC Sync and Android SDk, then reinstalled both. Now the drivers are working properly, and computer sees my phone again. This should help.
***edit: this process helped with my computer finding software drivers to connect phone to computer. Before- "Windows could not find drivers for Android device" (device manager in windows)
I could never get it to work in the first place. Cleanflash finds and flashes to it just fine but the s off just can't see my phone once it reboots.
Sent from my ADR6425LVW using XDA
DeviceSettings said:
Thanks guys. I am downloading an RUU now. Hopefully it works. I hope the usb connection is not fubar'd ...but i took the risk so its on me.
Click to expand...
Click to collapse
If the phone is rebooting to the screen with the arrow when you press power to enter fastboot then try going to recovery, your regular recovery will probably not show up but another stock hboot menu will. Then try selecting fastboot there and see if you can run fastboot commands without rebooting to arrow screen.
Sent from my HTC Vigor
Success getting it to reboot with the boot.img from the rom I was running....But unfortunately the usb is fried. Can not charge the phone or connect to a computer. So I guess that is another potential risk with using this method.
Ouuuuch :/
Sent from my ADR6425LVW using xda premium
Yeah sucks. I'm trying everthing I can, but its looking more and more bleak
DeviceSettings said:
Yeah sucks. I'm trying everthing I can, but its looking more and more bleak
Click to expand...
Click to collapse
Warranty!
(edit: kidding, no need for a ****storm)
my phone will not be recognized by the computer no matter what i do. It recognizes my friends i777 just fine in odin and as a storage device so it isnt my drivers. With mine it only makes the connection sound and says device drivers failed to install. I am running shostock 3, philz kernel and windows 7. I have tried everything and i am out of ideas, please help. thanks
Install Kies fresh, install android sdk and update it, reboot, try different usb ports.
Also u have to disable usb debugging and let it install those drivers, enable it and let it install those drivers and boot into download mode and do a regular reboot and let it install those. Always worked for me after following those steps.
If he's friends phones works. Then I think it's the phone usb. My own phone has the same issues but my usb on phone is messed up. Says charging while its not chargin and that happens I get the whole Device not recognize and fail to install. Try cleaning your usb with 99% Isopropyl of the instructions above this post don't work out.
chibixzero said:
If he's friends phones works. Then I think it's the phone usb. My own phone has the same issues but my usb on phone is messed up. Says charging while its not chargin and that happens I get the whole Device not recognize and fail to install. Try cleaning your usb with 99% Isopropyl of the instructions above this post don't work out.
Click to expand...
Click to collapse
I will try this. I appreciate the help
I tried the suggestions.....
I downloaded the samsung drivers correctly because my pc recognizes any other samsung but no matter what i've tried it says usb device not recognized for my galaxy. Im stuck in a boot loop and the only thing i can access is download mode when i plug it in the computer. I can't access anything with the battery in, it just flashes the galaxy logo over and over. Thank you for you time in advance
I've been having two problems with my OG.
The first is when my OG is connected to my computer, the computer recognizes it and I am able to view everything on my phone. The problem is when I open command prompt and enter adb devices to check to see if it sees the phone, it returns "List of devices attached" with nothing underneath. Clearly it is not recognizing the phone.
The second problem I am having is that when I enter download mode neither LGNPST nor my computer recognize the phone. Its as if nothing was plugged into the usb port.
Any help or advice to either problem would be greatly appreciated.
Not sure if download mode needs drivers. Do you have usb debugging enabled for the phone to be recognized in adb? Under development settings.
Make sure you're not plugged into a USB 3.0 port
It isnt plugged into a USB 3.0 port.
What are the necessary drivers? I might've deleted them after I rooted and flashed to The Base 0.73 and didn't think I would need them again.
I feel like I should mention that actually. I rooted and flashed to the Base, then flashed Slick Rom, then went back to the Base. So orginally my computer recognized my phone in download mode but after rooting and flashing it didn't. I think it might be the drivers. I'll check when I get home.
Ok so I downloaded the drivers from LG's website and installed them. I ran adb and it was recognized so that was the problem I had. Apparently after flashing I uninstalled and deleted everything off of my computer and just forgot to download everything back. Thanks for helping.