After upgrading my phone (T-Mobile Galaxy S Vibrant SGH-T959) to vibrantmtd #30, my laptop (HP EliteBook 8540p - Running Windows 7 Enterprise 64-Bit) no longer recognizes my phone as a USB device. There is literally no indication of Windows trying to load the phone as a USB device. I have tried everything I can think of to get the device to load as a USB drive on my laptop.
1. Rebooted the Laptop, several times
2. Uninstalled and reinstalled Samsung and Nexus USB drivers
3. Made sure my laptop was up-to-date on all patched
4. Tried with USB Debugging was checked/uncheck
5. Tried with multiple cables
6. Tried multiple USB ports (1.1, 2.0, and 3.0)
7. Used USBdeview to uninstall all USB devices on my laptop (also tried this on my home PC) and then let window reload the devices after a reboot.
8. Tried with multiple systems (both Windows 7 and XP 32/64 Bit) – including friends who have Galaxy S and Nexus Phones.
a. The only system that will try to load a USB driver is my home PC [Windows 7 Ultimate 64 Bit] and no matter what drivers I install the phone always comes up as an Unknown Device.
9. Tried going into download mode to use Odin to revert back to a 2.2 mod. I can only get into download mode using a physical jig and even then Odin will not connect to the device.
10. I can’t even load a different build of Cyanogenmod. I tried loading build #31. It downloads, prompts me with the three questions about backup, clear data, and cache. I have selected every possible combination of those selections and it will download the build and reboot try opening rom manager (too quick to see what it says) and then loads back into build #30.
I am at a loss as to why I cannot get the phone to be recognized as a USB device or be capable of further MODing. Any help would be appreciated
Thanks,
Michael
MikeTheTechGeek said:
After upgrading my phone (T-Mobile Galaxy S Vibrant SGH-T959) to vibrantmtd #30, my laptop (HP EliteBook 8540p - Running Windows 7 Enterprise 64-Bit) no longer recognizes my phone as a USB device. There is literally no indication of Windows trying to load the phone as a USB device. I have tried everything I can think of to get the device to load as a USB drive on my laptop.
1. Rebooted the Laptop, several times
2. Uninstalled and reinstalled Samsung and Nexus USB drivers
3. Made sure my laptop was up-to-date on all patched
4. Tried with USB Debugging was checked/uncheck
5. Tried with multiple cables
6. Tried multiple USB ports (1.1, 2.0, and 3.0)
7. Used USBdeview to uninstall all USB devices on my laptop (also tried this on my home PC) and then let window reload the devices after a reboot.
8. Tried with multiple systems (both Windows 7 and XP 32/64 Bit) – including friends who have Galaxy S and Nexus Phones.
a. The only system that will try to load a USB driver is my home PC [Windows 7 Ultimate 64 Bit] and no matter what drivers I install the phone always comes up as an Unknown Device.
9. Tried going into download mode to use Odin to revert back to a 2.2 mod. I can only get into download mode using a physical jig and even then Odin will not connect to the device.
10. I can’t even load a different build of Cyanogenmod. I tried loading build #31. It downloads, prompts me with the three questions about backup, clear data, and cache. I have selected every possible combination of those selections and it will download the build and reboot try opening rom manager (too quick to see what it says) and then loads back into build #30.
I am at a loss as to why I cannot get the phone to be recognized as a USB device or be capable of further MODing. Any help would be appreciated
Thanks,
Michael
Click to expand...
Click to collapse
Do you have skype? It would make it easier for me to help you. If you're not comfortable with it, I'll just type everything
Try this, turn phone off completely, turn it on by holding these three.... vol up, vol down, power....let go of all three at the same time as soon as you see the Vibrant logo.
Edit.....do not have it plugged in at all while doing this.
Is this a bug with the nightly? Try an OLDER version.
Sorry, don't have skype.
I did your above steps and that puts me into ClockworkMod Recovery.. Was there something I need to do in here?
s15274n said:
Is this a bug with the nightly? Try an OLDER version.
Click to expand...
Click to collapse
Nope, it's a driver and human error. Rom manager cannot go into recovery mode, you have to use three button combo.
It's stated by the cm7 team.
No, I checked. I was just able to go to build #31 by rebooting into clockworkmod and installing the build #31 zip from there. I did have to wipe data, install, and clear cache to get it take though.
Removed.. Agh, been awhile since cm7, not what I remembered.
MikeTheTechGeek said:
Sorry, don't have skype.
I did your above steps and that puts me into ClockworkMod Recovery.. Was there something I need to do in here?
Click to expand...
Click to collapse
Yes, now if you have downloaded a cm7 nightly on your sd card, do this.
Wipe data, factory reset
Wipe cache
Go to advanced, format system, cache, and data.m.
Go to install zip, choose zip from sdcard, select the downloaded cm7 nightly, select yes.
Then reboot phone, not reboot recovery. Leave it for 15 minutes, reboot, now use it.
After it's up and running, please please go into recovery mode the same way I posted, do this after you finish all the steps above!
Go into backup and storage and make a backup!! This will save your phone if future problems occur.....this is a nand backup.
Ok, I did all those steps, I have a backup now.
MikeTheTechGeek said:
Ok, I did all those steps, I have a backup now.
Click to expand...
Click to collapse
Awesome, this will save you from bricks or anything unfortunate.
Is your computer still not recognizing it?
Correct, still not recognized.
Open device manager, find device installation settings and make sure it's on find drivers automatically.
Open Windows Update, settings, check give me recommended/additional updates.
Use the usb software to uninstall the drivers, uninstall kies, or any samsung software.
Reboot......install this driver, turn off your compute, don't restart.
On your phone, settings, applications, development, make sure debugging is on.
Plug the phone into the usb and plug it into a new usb slot. Now turn on your computer with it plugged in.
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
Well for whatever reason, those steps seem to bring to life my USB port.
I performed all the above steps and when I powered on my PC after perform the steps, the phone was not recognized as a USB device until I unplugged the USB cable and plugged it back in. Now it is recognized on every port on my laptop.
Interesting other issue was that after I used Odin to revert to stock, if I powered off my phone it would not load anything (not even the splash screen) when I tried to power it on and I know it was at 90-100% battery power. The only way to get it to boot was to go back into download mode and use odin to reflash the OS. I did this 4 times with the same results, with different copies of Odin and the stock rom and I got the same result.
I decided I was too tired to figure it out, left it on after a flash (not plugged into anything) and now it will reboot fine.
I don't know what strange voodoo possesses my phone, but thanks for your help.
That's good to hear and no problem. By the way, I highly recommend using Heimdall to flash roms....I've had no problems with it. I don't use odin anymore.
Thanks, I have heard of Heimdall but never tried it. I will give it a try next time.
Related
Hi all
I have a problem with my hero not being recognized by my PC. This happened after a weekend trip and i charged the phone with iphone USB adapter as i lost my one and now after returning from my trip i connect my hero to my PC to be greeted with the "USB Device Not Recognized" message.
Also my Amon_Ra recovery i used has been wiped and i cant get into recovery or install any rom at all.
I am thinking this might be the same USB brick that affected some Desire owners but i am not sure.
So please if anyone can help me, please do.
Thanks in advance.
fizzle101 said:
Hi all
I have a problem with my hero not being recognized by my PC. This happened after a weekend trip and i charged the phone with iphone USB adapter as i lost my one and now after returning from my trip i connect my hero to my PC to be greeted with the "USB Device Not Recognized" message.
Also my Amon_Ra recovery i used has been wiped and i cant get into recovery or install any rom at all.
I am thinking this might be the same USB brick that affected some Desire owners but i am not sure.
So please if anyone can help me, please do.
Thanks in advance.
Click to expand...
Click to collapse
this happen to me. What i did was switch my phone off, plug in the usb and switched it back on. then wait for windows to say it not recognised. then go to to device and printers and uninstall the drivers for the phone. Disconnect and reconnect the usb back to the phone and it it will pick it up.
Can you try booting in fastboot and tell me if that is recognized?
it still doesnt recognize it in fastboot
fc_Kuro said:
this happen to me. What i did was switch my phone off, plug in the usb and switched it back on. then wait for windows to say it not recognised. then go to to device and printers and uninstall the drivers for the phone. Disconnect and reconnect the usb back to the phone and it it will pick it up.
Click to expand...
Click to collapse
i have tried that and it doesnt help
fizzle101 said:
i connect my hero to my PC to be greeted with the "USB Device Not Recognized" message
Click to expand...
Click to collapse
Sounds like its just a driver issue. Have you tried plugging it in, when you get that message open DEVICE MANAGER,... Find the yellow "!", right click it, uninstall, unplug phone, reboot PC.
.... Then use BTDAG's [Guide] How to Setup Correct Hero Drivers (for x86 & x64 users)
I hav the same problem. In recover mode it works but then turn on the phone, there is no popup options as before. Tried around with drivers but didnt work either. But found a solution which is very convenient. I dont know if it works on other ROM versions but I'm on 2.1 (Villain10).
- Install extended control widget (dont remember where I got it but you can google, it seems I cannot find it on the market)
- Add this widget to the home screen: Menu/Add to Home/Widget/ Extended Control bar (you can choose the size from 1x1 to 1x4) then select "Mass storage" at the bottom, apply.
Now you have a widget to turn on/off USB storage. When you connect Hero to the PC, just click on this widget then the PC will connect to the SD card, and click one more to turn it off.
ok i will give that a try
crk23 said:
I hav the same problem. In recover mode it works but then turn on the phone, there is no popup options as before. Tried around with drivers but didnt work either. But found a solution which is very convenient. I dont know if it works on other ROM versions but I'm on 2.1 (Villain10).
- Install extended control widget (dont remember where I got it but you can google, it seems I cannot find it on the market)
- Add this widget to the home screen: Menu/Add to Home/Widget/ Extended Control bar (you can choose the size from 1x1 to 1x4) then select "Mass storage" at the bottom, apply.
Now you have a widget to turn on/off USB storage. When you connect Hero to the PC, just click on this widget then the PC will connect to the SD card, and click one more to turn it off.
Click to expand...
Click to collapse
that didnt work. o well i guess i am stock with the rom i have there.
fizzle101 said:
that didnt work. o well i guess i am stock with the rom i have there.
Click to expand...
Click to collapse
i've got this problem once and it was as simple as the cable was damaged...
i changed the cable and since then, everything works try that.
robocik said:
i've got this problem once and it was as simple as the cable was damaged...
i changed the cable and since then, everything works try that.
Click to expand...
Click to collapse
i have tried everything. changed the cable, used different pc but nothing works. i think is a hardware problem, something might be broken inside or something like that
Did you ever got this solved? I have the same problem only i use stock rom 2.1 Hero.. driving me nuts ...
baklap said:
Did you ever got this solved? I have the same problem only i use stock rom 2.1 Hero.. driving me nuts ...
Click to expand...
Click to collapse
No i havent and i gave up trying because i dnt think there is a fix for it. if yours is unrooted and the warranty is still valid you should consider returning it to HTC maybe they might replace it
got the same problem. Any solution so far ??
ddotpatel said:
Sounds like its just a driver issue. Have you tried plugging it in, when you get that message open DEVICE MANAGER,... Find the yellow "!", right click it, uninstall, unplug phone, reboot PC.
.... Then use BTDAG's [Guide] How to Setup Correct Hero Drivers (for x86 & x64 users)
Click to expand...
Click to collapse
Did you try that?..... You need to do the reboot PC/Laptop after uninstalling ALL HTC drivers! Then when you reboot PC, plug phone back in, should say "not recognised" again,... then follow BTDAG's guide. T'is definitely a driver issue!
tried flashing 3 roms, modaco, radug and now kimera... none working.
can connect in fastboot, it shows up in device manager as android 1.0
ive tried 3 different usb cables and 4 differet pcs, still there is no response on my phone !!!
using villian rom 10.0 rite now.
okay it boots up into fastboot and fastboot usb shows up on the screen in red,
BUT when i use the "adb devices" command in adb it doesnt show the device,
it is showing as android 1.0 in devices and printers (windows 7)
You need to use....
fastboot devices
....when your are in fastboot.
What happens when you go into your recovery, select "Toggle MS/USB" with USB connected to PC?
okay
fastboot devices command shows some serial number.
then i tried adb remount, it gave an error....
enabling usb-ms with cable attached gives no response
ok i think it might be USB driver like ddotpatel said but i am not sure.
i reinstalled my whole windows 7 to 32bit now instead of the 64bit version i was using before and today i just connected my hero to my PC and windows 7 did its thing and installed the drivers and finally my hero can mount the SD card in my PC again although i kept getting this can perform faster in USB 2.0 port or something like that i didn’t care as long as i can mount my SD card again.
now went into fastboot and used the fastboot device command and i could see my hero serial no. but when i try to flash the amonra recovery i got the permission error (i cant really remember). i tried flashing using the adb method but still no luck.
so i went to market and downloaded rom manager and used it to flash clockwork recovery and now i could boot to clockwork recovery.
from this recovery i can now flash any rom i want and although there are still a few more problems i am glad now that i can flash custom roms again.
the problem i can see so far but i can deal with is
1. i don’t think fastboot commands work even if the phone is detected.
2. SD card mounts at USB 1.1 speed. (i have tried different ports and cable but still the same thing and this is the ports i use for my N1, Desire and my other android phones with USB 2.0 speed)
PS: adb commands for pushing and removing apps is working.
Hope this can be helpful to those experiencing the same problem.
Instead of re-installing your entire OS just use usbdeview to remove the failing drivers.
Also remove any old HTC Sync installs and install the latest version.
Hi guys and gals !
So a few days ago i rooted/flashed my friends s5830 regular way and uploaded VillainRom, yesterday he came by my house for he has tried to upload LucaRomv2 by using Rom Manager.
As a result the phone stays dead at "Samsung" logo on regular boot, altough if we plug it in the pc it will detect the modem, sd card(not acessing it for it must have usb debugging enabled) and all, just the screen that doesnt pass "Samsung" logo.
So the logical next step is if we have communication is to press the magic buttons VOL- + Home + power ON, and it does work for it goes to download mode, the only problem is has soon has i plug it on my VM (VBox 4.0) it just spits out usb error on VBox and does not connect.
I have tried all combinations Volume+ (flash mode) all enters, its just that when i plug it to VM it spits out an error.
I can even enter recovery mode by HOME+POWER (and for the looks of the register that show when i enter it it complains it cant find /data, /cache .... so my guess is Bootloader is still ok has it enters all these modes and just need to re-upload rom(basically the os)
So leading to usb error in VM i prompted to fully test my VMUSB everything works ok connecting it (storage drive, my vodafone smart, usb cam) and even the s5830 itself while on regular usb connection. This has worked ok before for this is the computer/vm i used it to flash it originally.
Just to relief up i will try the following today:
Clean format a physical computer with winxp and try do the process without VM in the middle
Should i make the usb jig with 301K ? Has anyone actually tried usb jig on ace ? Whats different from this mode to regular vol- + home + power ? From what it seems its factory download mode i guess, an alternative bloader.
In case of JTAG needed does anyone have flash specs ? I mean offsets and such ... i have access to JTAG tools here at work, just a matter of pinout and see if cpu/flash supported.
What is your general opinion about this ?
I have launched this thread for i have not found any info on this kind of situation, people usually have fully bricked (black screen) or can still access download mode and communicate with pc, i have not found similar characteristics.
Thank you !!
Did your friend a wipe after flashing the rom? If not then go to recovery and wipe Dalvik cache - cache and Data/factory reset.
If this doesn't work put the phone in Download Mode and flash with Odin and after this make a wipe.
Sent from my Transformer TF101 using Tapatalk
http://forum.xda-developers.com/showthread.php?p=16699494
steini81: I dont know exactly what he did, i have tried to wipe it via recovery manager but still no go, it still complains on missing mounts /data /cache .... as for flashing with odin i can start download mode on the phone but has soon has i connect it on the usb port of the computer it just gives out an error and does not go online.
Lovetz: I already read that post, the difference is i still can go to download mode, my problem is when i plug on pc it doesn´t go thats why i opened another thread.
--------------------------------
Maybe it´s just Virtualbox playing it´s pranks with async usb, can only eliminate this chance later on for i dont have the sga with me.
how about using a different machine? a machine with the drivers from Kies..
Try it on a Windows PC with Odin and Kies Drivers installed.
Sent from my Transformer TF101 using Tapatalk
Mundix: I´m already using skeys drivers, tried killing processes and not killing them, but this subject goes further then that because i think i have usb connectivity issues, now, it worked ok when i first flashed this device maybe something corrupted my usb1/2 modules for virtualbox (btw running debain squeeze-> virtualbox -> xpsp3, with full usb 2.0 extension loaded (already tried only usb 1.0 only has it has helped before on the first flash). Plus all usb devices work ok, including the samsung itself on "normal" boot so i dont know, maybe has its a raw dump vbox doesnt like it Later on i will format a computer with xpsp3, load skeys, odin and start from there,so basically you agree with my point
Steini81: yeps thats what im gonna do, but i do not use any windows machines all obsd/debian at home and work so ... only virtual, i´ll grab an old borrowed laptop and format it just for this.
-------------------------
Once again i just opened the thread because i havent found anyone with same situation, either its fully bricked or they can usb plugin. No post until now for usb download mode crash. I will follow up here maybe it might help someone in the future, or will confirm brick altough bloader boots and phone detected on "normal" mode.
Mizaiko said:
Mundix: I´m already using skeys drivers, tried killing processes and not killing them, but this subject goes further then that because i think i have usb connectivity issues, now, it worked ok when i first flashed this device maybe something corrupted my usb1/2 modules for virtualbox (btw running debain squeeze-> virtualbox -> xpsp3, with full usb 2.0 extension loaded (already tried only usb 1.0 only has it has helped before on the first flash). Plus all usb devices work ok, including the samsung itself on "normal" boot so i dont know, maybe has its a raw dump vbox doesnt like it Later on i will format a computer with xpsp3, load skeys, odin and start from there,so basically you agree with my point
Steini81: yeps thats what im gonna do, but i do not use any windows machines all obsd/debian at home and work so ... only virtual, i´ll grab an old borrowed laptop and format it just for this.
-------------------------
Once again i just opened the thread because i havent found anyone with same situation, either its fully bricked or they can usb plugin. No post until now for usb download mode crash. I will follow up here maybe it might help someone in the future, or will confirm brick altough bloader boots and phone detected on "normal" mode.
Click to expand...
Click to collapse
My sister's Backflip had a similar issue . All I did was to wipe EVERYTHING then reflash .
Sent from my Awesome Ace with fla.sh ROM and TAPATALK
SOLVED !
1 st Run:
Clean XPSP3 *Laptop* - "Unrecognized USB device ...", exactly has ocurring in VM.
No go.
2 nd Run:
USB JIG (tried 299K, 300K, 301K and 302K accurate resistors 1% tolerance) followed by above method.
No go.
3 rd Run:
Load WIN7PRO on a desktop for s-kies was giving problems with framework4 on XPSP3.
No go. "Unrecognized usb ..." just like on the laptop with XPSP3
Thats when it hit me, "some" devices(MODEM, STORAGE) load ok, odin driver does not, so it does have partial usb communication, this made me go way back in time when i had a USB MSI WIFI that would only work stable under USB 1.0 and was buggy under 2.0, so ...
Step 1 - Take the dust out that powered USB 1.0 Hub from drawer;
Step 2 - Make pigtail from internal desktop 12Vcc to power usb hub for Vcc stability
for power supply been lost like 4 house moves ago(yes i could go external powerless but ... just in case);
Step 3 - Cook a good home meal and mix it with some fine red wine;
Step 4 - Hook up usb hub, let win7 install, hook up SGA while on DOWNLOAD MODE (Vol- + Home + Power) and you can have the batery installed, no need to hot plug it, connect to usb hub.
Step 5 - Be amazed has it detects "Odin" has a new device and Odin square turns yellow just waiting for you to press start ...
*Personal Note : Do not stand up quickly after step 3 !
Now, the funny thing is if i move the USB 1.0 HUB to the XP SP3 Laptop its also a go, same results for in my Virtualbox install. Notice i tried it on 2 physical/1 virtual computer under VBOX4.
In conclusion:
If your SGA still boots to "samsung" and lets you get in Download/Flash/Recovery but gives out an USB communication errors, but still installs some devices like MODEM/Storage, all of this after a run from ROM MANAGER, please *DO* try to put an usb 1.0 hub between your computer and your SGA.
At this moment it works like a charm and i´ve just uploaded coderom.v2x-02, altough if i remove the USB HUB its back on the same problem, trough the hub it works ok aside i have 1.0 transfer speeds ...
Now, some help on debugging, arent there any logs on the system i could analyse? Should i dump trough JTAG ? What could of happened so that it has this symptom now ?
Anyways thanks for those who tried to help, just hope this helps someone in the future !
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.
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
Hi all,
I have a Rooted, WanamLite v6.3 ZSEMC1 ROM with AdamKernel 2.2.1+. i9300.
I updated recently from another previous version of the same ROM because I had noticed that my USB functionality has not been working. Specifically, the MTP application. Soon further found that my computer does not recognise ADB commands at all, as I used to install .apks from my computer quickly with adb install.
Odin does not even recognise my phone, even when in download mode. The only thing I havent tried yet is ADB in CWM Recovery, but im 99% sure that wont work still.
When I plug the micro-usb plug in it charges fine, but no data connection seems to occur. No windows detection, No USB device connected in the notifications bar.
I have tried:
-Backing up
-Installing vanilla ROM
-Installing stock ROM
-Using different computer with drivers
-Reinstalling Samsung Drivers
-Tried using Kies for the drivers
-Changing SD cards
-Power Cycling phone removing sim and micro-sd cards. Turning on after some time.
-Cleaning the micro-usb port on the phone with dental picks.
Im pretty much out of ideas apart from trying to organise to send it for repairs, after un-rooting.
If I was to re-root do you think this would solve the problem?
Any help is much appreciated.
Thanks :good:
UPDATE: I fixed this by using Mr. Despairs suggestion.
Power off, pull battery, SIM, SD card. Power cycled the power button with no battery in it.
Waited about 1-2 minutes.
Battery in boot straight to Download Mode.
Only got it to recognise once in about 15 tries.
Thanks again Mr Despair!
You could also try another cable. Or what I read in another german forum: Shut down your phone, take the battery out and in and reboot. Then reboot into download mode and plug in your phone. Then your PC should search for drivers.
Do this as a colleague says Mr. Despair replace the cable. Often dirt in the connector. Clean the connector on the phone.
Also check ...
Also check on a different computer/port - it could be a problem with the USB drivers on your computer.
Probably the safest test would be to cross-test combinations of 2-3 computers vs 2-3 phones.
xclub_101 said:
Also check on a different computer/port - it could be a problem with the USB drivers on your computer.
Probably the safest test would be to cross-test combinations of 2-3 computers vs 2-3 phones.
Click to expand...
Click to collapse
He already wrote that he tried more PCs. He would have very bad luck if it is on both. But trying doesn't cost. He shoule then also try to plug it direct into the USB ports and not through a hub.
I have also tried two other cables which both previously worked.
Ill give the hard reboot into download mode a try.
No PC recognises it at all at the moment.
I have tried all USB ports, directly not through a hub or whatnot. This includes other computers too.
Im open to any other suggestions.
Thanks for the help so far
Have you installed KIES?
KIES and ODIN cannot co-exist.
Install ONLY Samsung USB drivers then run ODIN.
As for installing apks, you shouldn't need to install via adb. You can just copy to sdcard and run from there.
Sent from my GT-I9300 using XDA Premium
IRPnet said:
Have you installed KIES?
KIES and ODIN cannot co-exist.
Install ONLY Samsung USB drivers then run ODIN.
As for installing apks, you shouldn't need to install via adb. You can just copy to sdcard and run from there.
Sent from my GT-I9300 using XDA Premium
Click to expand...
Click to collapse
I had used ODIN without KIES existing on my system.
I installed KIES to try and get it to read my phone for once.
I used ADB to install .apks when I had ADB running. I have the problem now that I cant use it, because my phone MTP, ADB or even Download Mode wont read my phone. All from different computers etc.
:crying:
Sounds more and more like a hardware failure. What about reboot to CWM then in mounts and storage to mount the USB drive? Can your PC recognize it this way?
Mr. Despair said:
Sounds more and more like a hardware failure. What about reboot to CWM then in mounts and storage to mount the USB drive? Can your PC recognize it this way?
Click to expand...
Click to collapse
Yeah im thinking hardware too. If I throw it into CWM and try to mount /sdcard, it doesnt to anything. Nothing changes it just stays permanently on mount /sdcard. (Its not mounting).
Mounting external_sd works but its not helping me.
Anyone ever returned a SGS3 to factory or phone provider?
Mr. Despair said:
You could also try another cable. Or what I read in another german forum: Shut down your phone, take the battery out and in and reboot. Then reboot into download mode and plug in your phone. Then your PC should search for drivers.
Click to expand...
Click to collapse
I initially tried this with no success, however after about 15 tries I got it to work once!
Thanks heaps for this!
Pull Battery, SIM and SD. Press Power buttons a few times and let it sit for about 1 minute.
Battery in and boot straight to Download mode. Worked once in about 15 tries. Reflashed everything and it works now!
Thanks Despair!!:laugh::laugh::laugh::laugh::laugh::laugh::laugh::laugh: