I am literally having the worst time. I have to go to work in 30 minutes and my phone is now broken. All I wanted to do was update it so I found a rom for my Infuse but now that I installed it, my phone seems to be broken.
Now I am trying to get it back to its normal state, but the only way to do that is put it in download mode(which works fine) and plug it into Odin. But Odin will not detect it no matter what I do. I have tried everything and I am literally pulling out my hair because this is frustrating me so much.
I hear my pc detecting it. I download drivers. I tried installing drivers through kies, but it just sits at 0%. Then I downloaded the galaxy s drivers, which does nothing when I click the setup file(or at least I can't tell that it is doing something), and then I tried finding the download specifically for my device on the samsung website, but when I run that setup file it says Samsung Android USB Modem Software not installed succesfully (9).
I just want to fix my damn phone and this software will not detect it for the life of me.
Related
I have a s 2 i flashed a Lightening rom XWEK7 and it worked fine all day until a hour ago when my phone froze and restarted it self and now it wont recognize being plugged in it will go into download mode on the phone but still wont come up on the computer end. And is currently not going past the screen that says " Samsung Galaxy S 2 GT - 19100 and the yellow triangle at the bottom.
Need help ASAP as is my work phone.
The main thing is you can get into download mode. Get stock firmware from here if your carrier is listed, if not get country specific firmware here and flash that in Odin.
Edit - I just re-read your post & realised your PC won't recognise your phone. Uninstall/reinstall Kies so you have the drivers in place for Odin to recognise the phone (drivers might be corrupt ?). Make sure you kill off Kies in task manager before you attempt to flash stock firmware in Odin. If you find the PC still won't recognise your phone try a different USB cable/different USB ports (I know there's only one port on my laptop Odin works on), failing that try a different PC/different version of Windoze. And if all that doesn't work, you might want to try Heimdall. Search the forum, plenty of posts on how to use it (never used it myself so I can't guide you in the use of same).
http://forum.xda-developers.com/showthread.php?t=1449771
Follow this, and the phone will live again
Hello all, I have a GS3 international GT-I9300
I'll try to go through the story as fast as I can and give as much detail so you guys can understand how I got here.
Bought the phone unlocked, I was stock, I rooted and then I decided to install a new ROM. I went with Resurrection Remix, it was working great. I did this on a desktop back home. They released a new update to RR so I did a OTA update with "Update Me" apparently the thing flashed but it didn't, the phone still worked but NFC wasn't working as well as having lost root access and some other stuff wasn't working correctly, but I lived with it.
I moved to Florida (home is in NY) and I have a laptop with me, for some reason my laptop used to be able to transfer files to my S3, but it wasn't doing it any more after a while. So it would just charge it. I was in a hotel room last week trying to tether via USB but the PC wasnt having it, it could not locate the phone. This week I moved to a different hotel with internet and decided I would flash stock on my S3 to get rid of all these bugs and get root again, I tried flashing stock through recovery and it wasn't going, so I tried flashing RR again (this time downloaded from the site RR site) and it worked. Still no USB connection but I had root back. I looked around my PC and apparently the Samsung drives are not installing or something on my PC. I installed Kies, but nothing, I tried a stand alone driver install and nothing, so I just gave up and bought Mobile Odin pro from Gplay to try to flash again.
Mobile Odin for some reason (I blame it on myself) wasn't finding/flashing stock so again I decided to try and flash RR and see what would happen. It flashed RR and turned on fine. Then I just decided to look for an NFC fix on XDA. Once I found my NFC fix (http://forum.xda-developers.com/showpost.php?p=32029713&postcount=8367) I decided to just copy the files to the system folder, NFC still not working, rebooted and NFC still no working, so I figured I would try to flash the fix through mobile odin seeing as how I can't get my PC to pick up on the USB. I tried flashing but MO just kept bouncing it back and re-booting into RR. Tried again and no flash. So I decided to again try and flash stock. I tried going into Recovery, the phone shut off like it always does, came back on but stayed in the Galaxy S3 GT-I9300 logo and would not move. I shut it off again, tried turning it on again and still stuck on the galaxy logo. Now, if I leave the phone off and plug in the USB, it won't show the battery charging image, it will actually turn straight onto the galaxy logo again and stay there. I can get the phone into download mode, but like I said my pc won't recognize the drivers.
Now, here are my questions:
What happened?
Can this be fixed?
Am I an idiot?
If I can get the drivers installed on another PC as well as Odin (1.85), will the new PC "see" the S3 or are the drivers on the phone deleted as well? (if that sort of thing can happen, idk.)
I'm going to see if I can borrow a buddy's PC and download the drivers as well as odin to try and bring my S3 back to life, I just want to know, what happens if I can't get the other PC to pick it up ether because the drivers on the phone are deleted (if that's a thing) or what I can expect if it is connected.
What are the steps or guides to follow here? I just got it into Download mode and it says on the top of the screen:
ODIN MODE
Product name: GT-I9300
Custom Binary Download: Yes (2 counts)
Current Binary: Custom
System Status: Custom
sorry , i am sometime getting headache reading long english text so i just briefly look over.
your PC doesn't recognize your S3 ? is that correct ? hmmm , is it possible that your PC (Microsoft Windows I assume?) system is damaged due to something like virus or some reasons ? i have encountered that kinda problem before and be OK after i reinstalled the system.
If it's a soft brick, then it can defiantly be fixed. You might, however, lose your data along the process.
Be glad it's not hard bricked
It happened to me many times, USB error "unknown device" connected. Only fix for it was reinstalling Windows so better if you can use different PC or laptop. Install Kies and other USB drivers. Restart computer, download and run Odin v 3.0x. Flash your phone.
If this doesn't work then maybe your phone have a problem with USB port?
Sent from my GT-I9305 using xda app-developers app
djembey said:
It happened to me many times, USB error "unknown device" connected. Only fix for it was reinstalling Windows so better if you can use different PC or laptop. Install Kies and other USB drivers. Restart computer, download and run Odin v 3.0x. Flash your phone.
If this doesn't work then maybe your phone have a problem with USB port?
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Don't forget to delete kies as you only need the drivers
Sent from my GT-I9300 using Tapatalk 2
Thanks for the replies guys. I'll try to fix tit today, I didn't get a chance to do it last night. If anything I'll update you guys with what's going on.
Like I was saying, I'll try using a different PC to fix it. Now, if I can't get Odin to recognize the phone, what would be the next step?
Hi all. So I just picked up a Verizon Note 2 today and happily looked forward to rooting it. I'm on 4.1.2 Jellybean VRAMC3, model number SCH-I605. I'm afraid I may have messed something up.
I had downloaded Odin and installed the Samsung USB drivers and all that good stuff. Odin picked up the phone and all that, but a bit more looking around seemed to indicate that the usual Odin method of rooting wouldn't work on the latest version that I had.
So I downloaded the CASUAL installer and got that to run. It ran through the install, rebooted the phone, and then said it was waiting for Windows to recognize the device again so that it could continue with the install.
At that point, Windows informed me that a driver install had failed and the CASUAL install did not proceed any further, despite waiting a good 5-10 minutes.
Since doing this, the phone has had bizarre USB connection issues. Odin and Kies do not read the phone at all. Plugging the phone in brings up an additional drive for about two minutes with a Verizon Assistant Manager EXE, a USB Drivers EXE, and a couple other things, then it disappears.
The phone will often display a message informing me "Unable to find software on your PC that can recognize your device." This happens regardless of being in USB Debugging mode or not.
I've tried uninstalling and reinstalling several versions of Samsung's drivers as well as Kies. I also tried a factory reset on the phone itself, but these connectivity issues (and accompanying warning messages) persist.
Not sure how to proceed from here and would love a bit of help. Thanks!
Additional notes: All normal functions of the phone are working fine, and the computer DOES detect the phone as a "Samsung Android Device", but as stated Odin and Kies are not able to detect/connect with it.
Update: Messed with drivers a bit more and Odin will now pick up the phone again. When the phone disappears as a "drive" with install helper stuff, it reappears as a portable device, and I can browse the innards of the phone to put music and other stuff on it. CASUAL however still does not pick up the phone.
Hi everyone, i hope to find a solution writing there, since i'm kinda desperate about my situation.
So, i got this telephone, a s2 I9100g, but only the day after i noticed the browser was in chinese. Looked up a bit better inside and i found it is a chinese version of the telephone (original one, but made for chinese market).
So i tryed to pull in an original rom, but it failed; i found a guide to how to fix this problem, and become able to flash the italian rom on it.
Basically, i followed this guide http://forum.xda-developers.com/showthread.php?t=1702479%22 I did all the steps using the CHN version of the bootloader and.. i know, i was so stupid there, but since it got stuck at NAND writing (i did not see the progress bar after 15 minutes), i simply unplugged the cable.
Well, after that the phone didn't enter reset/download mode, but it started showing the yellow phone---!---pc screen, with wrote above "software update fail", and something else in chinese.
There is what i tryed to do:
-Flash another rom (tryed 2) with different versions of odin, 1.3,1.6 and 3.07.
odin does recognize the telephone with the drivers installed, but if i start it, it gets stuck at setup connecting phase and failing after. Same with all versions.
-use OneClickUnbrick, i tryed to start it normally and from CMD.
with the drivers which odin and windows use to recognize the telephone (last ones available on samsung website), it says "usb drivers are not properly installed attempting to install drivers". So, it starts Zadig. I follow the steps there, and the installation completes succesfully. But at this point, when i plug in the telephone windows recognizes it but fails installing the device with drivers, and odin doesn't recognize it at all, while oneclick keeps showing the "usb drivers are not properly installed" window, time after time even if i keep reinstalling with success the drivers using Zadig.
-delete everything and install Kies.
none of the programs above does see the telephone now, neither windows.
Tryed to follow the steps i did before after having it installed, nothing changed.
Every of this tryes, i did the following "changes":
-removing and inserting the battery
-changing usb port
-changing cable
-changing computer
-trying to enter reset/download mode by holding vol up/down+mid button+power
Would be enough to make odin go over the setup connecting phase, or kies to recognize it, or OneClick to stop showing the window about drivers.
I read that seems i'm in a hard brick case, but since the phone is seen by odin and windows and the battery does recharge, i got still a bit of hope.
Thanks
Click the link in my signature, there's more troubleshooting steps to try. You've done a few but not all of them.
I would usually say that pulling out the cable leaves you with no hope, but you seem to have gotten a little lucky. Don't hold your breath though.
Sent from a galaxy far, far away
Hopper8 said:
Click the link in my signature, there's more troubleshooting steps to try. You've done a few but not all of them.
I would usually say that pulling out the cable leaves you with no hope, but you seem to have gotten a little lucky. Don't hold your breath though.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Tryed all the steps.
Nothing changed.
You can either keep trying or take to a service centre & pay to have it fixed *shrugs*
Hopefully somebody can help me this this. I was attempting to flash back to the original firmware to get back to the unrooted ROM and it seems like during the process the phone or cable disconnected and now it's stuck on the Firmware Update screen and the little console box on the bottom reads "VUSER B99". The computer seems to recognize the phone in device manager as LGE Androidnet for VZW, however nothing seems to change when I try to run the LG flash program. I've used the program twice before and both times it worked perfectly.
I've tried booting into TWRP recovery, entering download mode, and battery pulls, but nothing changes once it boots. I'm using the LGFlash tool and VS98510B_03.tot. I had the JasmineROM v5.0 on it before I was trying to revert back. Has anybody seen this before? I tried searching and found a few similar problems, but no conclusive solutions and none for the G3.
Update --> solved
In case this happens to anyone else, I found the solution was to use a different computer. For whatever reason, I was no longer able to use the computer that I had previously used for flashing the stock firmware. Apparently, the stock cable that I have, and was using, is slightly worn out and the computer lost the connection during the process, which soft bricked the phone on the update firmware screen.
I downloaded all programs and drivers on a new windows 8 laptop and it worked on the first try. Hopefully this helps if this happens to anyone else.