restore to stock problems - Verizon Samsung Galaxy Note II

I bought this Note 2 about a month ago and got unlocked and rooted pretty easy... So I'm Currently on liquid smooth v2.3 4.2.2 vrall4. I was attempting to flash back to stock but each time I connect phone to computer in download I get no "ID:COM" number showing connectivity with the device. My first smartphone was original Samsung Galaxy so I'm slightly familiar with this flash back to stock, too bad there is no one click recovery restore tool but anyways. I'm not sure what I did but I believe I have accidentally deleted a wrong folder. Phone still works perfectly except that it doesn't seem to want to flash ROMs from the Original Android Dev section of this phone's forum... such as Paranoid's 3.5x.
also it will not connect to computer as media device...only as camera. phone notifies me it is connecting as media device, but it does not appear in my computer. it won't even allow me to put zips on the internal storage.

bunnsguy said:
I bought this Note 2 about a month ago and got unlocked and rooted pretty easy... So I'm Currently on liquid smooth v2.3 4.2.2 vrall4. I was attempting to flash back to stock but each time I connect phone to computer in download I get no "ID:COM" number showing connectivity with the device. My first smartphone was original Samsung Galaxy so I'm slightly familiar with this flash back to stock, too bad there is no one click recovery restore tool but anyways. I'm not sure what I did but I believe I have accidentally deleted a wrong folder. Phone still works perfectly except that it doesn't seem to want to flash ROMs from the Original Android Dev section of this phone's forum... such as Paranoid's 3.5x.
also it will not connect to computer as media device...only as camera. phone notifies me it is connecting as media device, but it does not appear in my computer. it won't even allow me to put zips on the internal storage.
Click to expand...
Click to collapse
I've noticed this problem also after the update. C3 seems to be the culprit. Flash back to a stock rooted 4.1.1 rom and set radios back. Install Kies (again) and then you can keep or uinstall kies. This worked for me. The 4.1.2 update for some reason will not play nice with the drivers. Will only let me connect as camera on both windows and Ubuntu 13.04. Thats what led me to down grade and try again.
Also, it seemed that my phone got "stuck" in PTP for some reason after all that. Once i got it to work again. I was able to connect back to Ubuntu 13.04 in MTP mode using a new 4.1.2 rom. (this for those trying to figure out how to get MTP to work on Linux boxes after update. Use a computer to set phone back to MTP, and Linux will recognize it again.) If windows jogs the phone to PTP, for some reason it will not go back until you fix that on windows. Not a science, just what i've experienced in the last 2 weeks.

each time I connect phone to computer using odin in download I get no "ID:COM" number showing connectivity with the device

Sounds to me that your drivers arent installed. Youll need to update your drivers on your computer. That is what I do if odin is not seeing my device.
Sent from my SCH-I605 using xda premium

joeriv5692 said:
Sounds to me that your drivers arent installed. Youll need to update your drivers on your computer. That is what I do if odin is not seeing my device.
Click to expand...
Click to collapse
ive only tried this 10 times so far and no worky

Related

[Q] Hardware USB issue troubleshooting

Hey guys, well my note got thrown into a puddle last may. Everything has been working fine up until now. Two weeks ago my computer was recognizing my note just fine. In the last couple of days I've been trying to figure out why my computer isn't recognizing my phone.
So far I have:
-Uninstalled/reinstalled USB drivers
-Troubleshooted kies to see if that would recognize my phone
-Started up droid explorer to see if that would recognize it either.
-Have disabled/enabled usb debugging to see if that made a difference.
Is there anything left I can do to determine if it's a hardware issue or not? The phone charges just fine.
I've been paying warranty monthly.
If it's indeed a hardware issue, how am I supposed to revert from my custom rom back to stock and remove personal files without usb?
Thanks for the input everyone.
tonomon said:
Hey guys, well my note got thrown into a puddle last may. Everything has been working fine up until now. Two weeks ago my computer was recognizing my note just fine. In the last couple of days I've been trying to figure out why my computer isn't recognizing my phone.
So far I have:
-Uninstalled/reinstalled USB drivers
-Troubleshooted kies to see if that would recognize my phone
-Started up droid explorer to see if that would recognize it either.
-Have disabled/enabled usb debugging to see if that made a difference.
Is there anything left I can do to determine if it's a hardware issue or not? The phone charges just fine.
I've been paying warranty monthly.
If it's indeed a hardware issue, how am I supposed to revert from my custom rom back to stock and remove personal files without usb?
Thanks for the input everyone.
Click to expand...
Click to collapse
Have you tried a new "factory" cable ??
That is the next place to look..IMHO...g
tonomon said:
Hey guys, well my note got thrown into a puddle last may. Everything has been working fine up until now. Two weeks ago my computer was recognizing my note just fine. In the last couple of days I've been trying to figure out why my computer isn't recognizing my phone.
So far I have:
-Uninstalled/reinstalled USB drivers
-Troubleshooted kies to see if that would recognize my phone
-Started up droid explorer to see if that would recognize it either.
-Have disabled/enabled usb debugging to see if that made a difference.
Is there anything left I can do to determine if it's a hardware issue or not? The phone charges just fine.
I've been paying warranty monthly.
If it's indeed a hardware issue, how am I supposed to revert from my custom rom back to stock and remove personal files without usb?
Thanks for the input everyone.
Click to expand...
Click to collapse
Have you tried Kies whilst your Note is in recovery and download mode?
If not...
If I recall correctly, the stock recovery has an OTA firmware install option.
If I am right, you can use a WiFi FTP connection, Dropbox, Google Drive, Skydrive, Box, etc to get the CWM/TWRP installable stock recovery package onto your phone, flash that, then restore to stock firmware via the OTA option.

S3 Bricked [Soft?]

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?

I have tried everything please help

Computer wont recognize my device anymore. I have downloaded every set of drivers from this forum, from the samsung website, I even tried downloading kies but it wouldnt recognize it either.
It worked before I did the following and now it doesnt.
First I rooted my phone with route 66 everything was going fine until I made the huge mistake (not knowing) and downloaded rom manager so that I could do a nandroid backup. Well as we all know now, you cant do that. So I got the deadly uellow verizon triangle saying unauthorized software bring it to the store. So I went through the xda forums and found the one that told me how to fix it. I used odin with the alternate restore and got it back up and running. So I wanted to go back and use adams one click unlock and root. I got everything downloaded and ready. I put my phone in developer mode and plugged it in. It starts trying to find the drivers and then it flips from debugger mode to media mode everytime. It starts seeing it as everything but a samsung phone. It says found camera and even cd rom but not the phone. I have read through everything and tried everything I could think of but I am at a loss. PLEASE HELP
Sent from my SCH-I605 using xda app-developers app
brandi1693 said:
Computer wont recognize my device anymore. I have downloaded every set of drivers from this forum, from the samsung website, I even tried downloading kies but it wouldnt recognize it either.
It worked before I did the following and now it doesnt.
First I rooted my phone with route 66 everything was going fine until I made the huge mistake (not knowing) and downloaded rom manager so that I could do a nandroid backup. Well as we all know now, you cant do that. So I got the deadly uellow verizon triangle saying unauthorized software bring it to the store. So I went through the xda forums and found the one that told me how to fix it. I used odin with the alternate restore and got it back up and running. So I wanted to go back and use adams one click unlock and root. I got everything downloaded and ready. I put my phone in developer mode and plugged it in. It starts trying to find the drivers and then it flips from debugger mode to media mode everytime. It starts seeing it as everything but a samsung phone. It says found camera and even cd rom but not the phone. I have read through everything and tried everything I could think of but I am at a loss. PLEASE HELP
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Turn off your phone, connect to your computer with the USB cord and turn back on your phone. It should start the drivers and connect to your device.
smalk said:
Turn off your phone, connect to your computer with the USB cord and turn back on your phone. It should start the drivers and connect to your device.
Click to expand...
Click to collapse
I tried that, it is still not seeing it like it is supposed to. I was able to get Odin to recognize it so that I could flash the rooted stock again but I can't get Casual Jailbreak to work. I'm not sure if it is because the drivers or not but I am guessing it has something to do with it. Every time I plug it in, it starts searching for drivers and then always switches from usb debugging mode to media mode. The checkmark is still in usb debugging but I don't think it actually is. You can watch it go from device as installer to media.
Are you using the driver install app (zadig i think its called) to install the heimdall driver on top of "gadget serial". Looking at your other post it seems like a driver issue. One thing ive noticed is, if odin can see the device then heimdalll cant and vice/versa. So if odin can see it you have the wrong driver, if you are infact installing the heimdall driver my second question is, does windows xp x64 use driver sig enforcement like win7 x64 does? if so you probably need to disable it. Just throwing my $0.02 out there.
Are you using the official USB cable? I had an aftermarket cable that had worked for months, then decided to quit working. It works with other devices just not the Note2. Changed to my original cable and all is well.
nunyazz said:
Are you using the official USB cable?
Click to expand...
Click to collapse
Also try plugging it in to the PC and not through a hub/keyboard/monitor port
Sent from my SCH-I605 using xda app-developers app
If it sees the device in the dumb verizon cd mode thing and ptp than it can see adb. Its not the cable. however i would try setting the usb debugging first than set it to camera mode. adb should still be able to pick it up
Thank you everyone for your help, I finally got the drivers working and the bootloader unlocked
brandi1693 said:
Thank you everyone for your help, I finally got the drivers working and the bootloader unlocked
Click to expand...
Click to collapse
How? Fixing to unlock my spanking new note also. I had the drivers issues late last night. When installing drivers through the Z app I never could get it to install Samsung usb drivers nor did I see serial gadget option. Running Windows Vista 64bit. I know I have Java.
Sent from my SCH-I605 using xda premium

No data/odin won't recognize and can't connect to computer

I flashed up to 4.2.2 the newest 2,2 Liquidsmooth rom, didn't like it, so I wen't to flash back to 4.1 jellybeans build 13. I wiped everything, from, factory, cache/dalvik 3 times and then flashed. I loaded it up and it was buggy, so I wiped and reflashed again, and like the last time I have no signal and my phone no longer connects to my computer. Everytime I plug it in it says installing drivers but it will never connect. I get a message saying there is nothing on my computer to detect my phone even though it could 20 minutes ago. I have an odin stock file I wan't to flash but can't as odin won't recognize it. It makes a sound upon being plugged into my computer and shows up under device manager saying drivers are all up to date but I still get nothing. I can still use twrp though etc. What do I do?
Good luck dude I can't even root my new note because of this issue
The computer note finding the note
Sent from my SCH-I605 using Tapatalk 2
I got signal back now, stupid problem wasn't even related to it at all, but It still won't recognize the phone. the computer recognizes my dads note 2 so I don't get it, but his is for t-mobile.
milesmarrero said:
I got signal back now, stupid problem wasn't even related to it at all, but It still won't recognize the phone. the computer recognizes my dads note 2 so I don't get it, but his is for t-mobile.
Click to expand...
Click to collapse
Yup verizon screwed us.
Sent from my SCH-I605 using Tapatalk 2
I feel lucky that I rooted my phone as soon as i got it and everything went successful. Because like 3 days later my phone stops communicating with the computer...
Thankfully I have a micro sd card so i can do flashable zips... But if I ever have to Odin back to stock or use Odin for anything I'm screwed.
From what I've read it isn't a phone issue is a Windows issue? But I don't know if that's true because i have yet to find a fix...
Sent from my Samsung Galaxy Note ²
dfuse06 said:
Yup verizon screwed us.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I agree with this statement.
touchthecaleb said:
I feel lucky that I rooted my phone as soon as i got it and everything went successful. Because like 3 days later my phone stops communicating with the computer...
Thankfully I have a micro sd card so i can do flashable zips... But if I ever have to Odin back to stock or use Odin for anything I'm screwed.
From what I've read it isn't a phone issue is a Windows issue? But I don't know if that's true because i have yet to find a fix...
Sent from my Samsung Galaxy Note ²
Click to expand...
Click to collapse
Yep thats the same thing that happened to my first phone ( rooted it within 30 mins. Of having it) but I was having other issues and had to send my phone back3 days later and usb debugging just stopped working so i had to use mobile odin to go back factory.
Sent from my SCH-I605 using Tapatalk 2
When Odin wouldn't recognize my phone, I went into device manager (on windows 7) and then clicked update driver under usb on "android device" then I chose choose from list. There were 3 options and I tried the second one and as soon as it installed Odin recognized immediately.
Sent from my SCH-I605 using xda app-developers app
constomy said:
When Odin wouldn't recognize my phone, I went into device manager (on windows 7) and then clicked update driver under usb on "android device" then I chose choose from list. There were 3 options and I tried the second one and as soon as it installed Odin recognized immediately.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Thanks! Simple, but it worked for me, too. Took about 2 seconds to find it and install it.
Windows did need to update a driver first on its own so that it would have something to update. Otherwise you may not get the Update driver option when you right click the driver in Device Manager.
Something like this:
1. Connect the phone in the mode (phone on, or phone in download mode) that isn't working
2. Start/Right click Computer/Properties/Device Manager
3. Right click on Android or Samsung drivers that appear
4. Choose Update Driver, Browse computer for drivers, Pick from a list on my computer
5. Click on the most promising looking drivers that come up until one works
Robtao said:
Thanks! Simple, but it worked for me, too. Took about 2 seconds to find it and install it.
Windows did need to update a driver first on its own so that it would have something to update. Otherwise you may not get the Update driver option when you right click the driver in Device Manager.
Something like this:
1. Connect the phone in the mode (phone on, or phone in download mode) that isn't working
2. Start/Right click Computer/Properties/Device Manager
3. Right click on Android or Samsung drivers that appear
4. Choose Update Driver, Browse computer for drivers, Pick from a list on my computer
5. Click on the most promising looking drivers that come up until one works
Click to expand...
Click to collapse
THANK YOU I HAVE BEEN TRYING FOR 2 DAYS to get my computer to see my phone in oden this fixed it!!!! Now if i can oden my way back to stock to fix my soft brick bootloop
Robtao said:
Thanks! Simple, but it worked for me, too. Took about 2 seconds to find it and install it.
Windows did need to update a driver first on its own so that it would have something to update. Otherwise you may not get the Update driver option when you right click the driver in Device Manager.
Something like this:
1. Connect the phone in the mode (phone on, or phone in download mode) that isn't working
2. Start/Right click Computer/Properties/Device Manager
3. Right click on Android or Samsung drivers that appear
4. Choose Update Driver, Browse computer for drivers, Pick from a list on my computer
5. Click on the most promising looking drivers that come up until one works
Click to expand...
Click to collapse
Where exactly will the drivers be on the computer?
Sent from my SCH-I605 using XDA Premium HD app
constomy said:
When Odin wouldn't recognize my phone, I went into device manager (on windows 7) and then clicked update driver under usb on "android device" then I chose choose from list. There were 3 options and I tried the second one and as soon as it installed Odin recognized immediately.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Dude thanks!!!! This finally worked!
Odin won't work
I can't get Odin to recognize my galaxy note 2. Trying to reinstall stock rom. I have uninstalled and reinstalled the samsung drivers over and over. I have the verizon note 2. All I wanted to do was root and remove some of the bloatware that came with the phone. I followed directions exactly but have wound up with a brick. Someone please help. I tried to update the Samsung drivers through device manager but it says I have the latest drivers .
constomy said:
When Odin wouldn't recognize my phone, I went into device manager (on windows 7) and then clicked update driver under usb on "android device" then I chose choose from list. There were 3 options and I tried the second one and as soon as it installed Odin recognized immediately.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
You just saved my butt! I couldn't get anything to work trying to re-flash with 4.3 OTA...chose the 2nd driver...Odin finally connected. Thanks for your cleverness!
Robtao said:
Thanks! Simple, but it worked for me, too. Took about 2 seconds to find it and install it.
Windows did need to update a driver first on its own so that it would have something to update. Otherwise you may not get the Update driver option when you right click the driver in Device Manager.
Something like this:
1. Connect the phone in the mode (phone on, or phone in download mode) that isn't working
2. Start/Right click Computer/Properties/Device Manager
3. Right click on Android or Samsung drivers that appear
4. Choose Update Driver, Browse computer for drivers, Pick from a list on my computer
5. Click on the most promising looking drivers that come up until one works
Click to expand...
Click to collapse
This did it for me as well. Specifically, the driver in my list that worked was: SAMSUNG Mobile USB CDC Composite Device Version: 2.11.5.0 [10/14/2013]
Image of driver select page attached.
VRoot
I have read and read....googled and youtube just about everything to get my note 3 AT&T rerooted! AT&T had an update on Friday 2-28-14 over the air. i noticed it was updating while i was at work. when it was done it removed my root by Kingo. I have tried like most of you numerous times with no success. I took the advise from this thread and used Vroot it took about 96 seconds and Bam....rooted! then i followed the instructions on this link ( http://forum.xda-developers.com/showthread.php?t=2532818 ) and now I'm done! THANKS!!!!!!!! hope this helps. I did this on my mac through parallels 9 my device is note 3 SM-N900A 4.3 build N900AUCBNB4
I had the same problem as everyone else. Odin would not recognize my note 2 (Windows 7) or acknowledge that it was connected. I got the correct drivers to load by going to USB options on the phone and checking Connect as: Media Device (MTP) while connected to the PC. Windows automatically installed the drivers. I then shutdown my device, put it in download mode, and Odin recognized it and I was able to flash.
neoixii said:
This did it for me as well. Specifically, the driver in my list that worked was: SAMSUNG Mobile USB CDC Composite Device Version: 2.11.5.0 [10/14/2013]
Image of driver select page attached.
Click to expand...
Click to collapse
where did you get the new driver?? My computer sees my phone, and i can access all my files on the phone...but odin STILL doesnt se my phone :-/... its driving me absolutely crazy . i dont get a list of drivers on my computer when i do everything you suggested. HELP lol
Make Odin Recognize Note 2
1. Open Odin
2. Get Samsung Note into Odin Mode (on off state, hold down volume down, home, and then power button)
3. Plug in to USB
4. If it doesn't recognize your device, take out battery (keep it plugged in!), wait a few seconds and put battery back in
5. Odin should now see your phone under ID:COM

gt-i9300 does not detect via odin

Guys I have already rooted my sgs3 and used many other roms. but few months earlier i put 4.3 stock rom to my device.
even now my phone is getting detected via odin(when it is turned on) and kies. But when i put it into the download mode phone isnt getting detected by odin. what i actually need to do it install custom recovery and root this device.
but now framaroot is not working and i have tried many other apks. please help me out
SLDarKprince said:
Guys I have already rooted my sgs3 and used many other roms. but few months earlier i put 4.3 stock rom to my device.
even now my phone is getting detected via odin(when it is turned on) and kies. But when i put it into the download mode phone isnt getting detected by odin. what i actually need to do it install custom recovery and root this device.
but now framaroot is not working and i have tried many other apks. please help me out
Click to expand...
Click to collapse
Aren't you just missing some drivers? Maybe try to reinstall them: http://forum.xda-developers.com/showthread.php?t=961956
Also make sure to allow drivers to interact with your device if anything prompts while in Odin.
Android Debugging activated?
blint6 said:
Aren't you just missing some drivers? Maybe try to reinstall them: http://forum.xda-developers.com/showthread.php?t=961956
Also make sure to allow drivers to interact with your device if anything prompts while in Odin.
Click to expand...
Click to collapse
Have you tried installing Sammy's USB driver?
And I'm presuming the device IS on download mode already (I don't believe it appears on Odin while on normal mode)
1. yes i have already installed drivers and phone is detecting via KIES and ODIN when it is turned on.. it suddenly disconnect whenever i put into download mode.
2. yep usb debugging is activated...
3. Im using 4.3 stock rom.. arent there any other way to root this device without pc .. coz i checked lot of forums but none helped me..
4. my pc - windows 10. but i dont think that it will be a issue coz it's detected when it's turned on (means not using download mode).
SLDarKprince said:
1. yes i have already installed drivers and phone is detecting via KIES and ODIN when it is turned on.. it suddenly disconnect whenever i put into download mode.
2. yep usb debugging is activated...
3. Im using 4.3 stock rom.. arent there any other way to root this device without pc .. coz i checked lot of forums but none helped me..
4. my pc - windows 10. but i dont think that it will be a issue coz it's detected when it's turned on (means not using download mode).
Click to expand...
Click to collapse
Bumping Up this thread since i have really same issue, as in literally the same.
Anyone can help me/us?
xaiury said:
Bumping Up this thread since i have really same issue, as in literally the same.
Anyone can help me/us?
Click to expand...
Click to collapse
mate you have to try a different PC or a port. I have fixed my issue using another PC
Download vroot PC Latest Version VRoot 1.7.8
http://www.vrootdownload.com
Downloading mode only..
I have tried 10000000000000000000000000000 tips tricks and almost everything in this and other websites.. but there is no solution for this:
I have GT-I9300 Pathetic galaxy SIII and since I tried flashing recovery to this it goes into download mode... and its been there ever since.. i have downloaded 32 different kind of drivers claiming Samsung drivers.., buying and trying 8 different USB Cables, formatted my laptop 3 time in order to get it detected by ODIN 3.04 to 3.12... or kies or Smart switch.. working on this piece of crap since 3 weeks day and night but getting nowhere,... If any one knows a way to get it fixed... EVEN IF IT NOT DETECTED BY ODIN OR KIES.
PLZ HELP....
Gr8mobiPro said:
I have tried 10000000000000000000000000000 tips tricks and almost everything in this and other websites.. but there is no solution for this:
I have GT-I9300 Pathetic galaxy SIII and since I tried flashing recovery to this it goes into download mode... and its been there ever since.. i have downloaded 32 different kind of drivers claiming Samsung drivers.., buying and trying 8 different USB Cables, formatted my laptop 3 time in order to get it detected by ODIN 3.04 to 3.12... or kies or Smart switch.. working on this piece of crap since 3 weeks day and night but getting nowhere,... If any one knows a way to get it fixed... EVEN IF IT NOT DETECTED BY ODIN OR KIES.
PLZ HELP....
Click to expand...
Click to collapse
Relax.. I understand how frustrating it can be.
I need a detail explanation of what you did to get it into that state and what you've tried. A bullet point list will suffice. I just need to know so I can work out how buggered it is and where to go from here.
I need to know which PC operating system you're using, which variant of s3 you have including its region (this can be determined by the sticker in the battery compartment unless you already know.
There is a possibility it is your os not detecting the device because of drivers but if you've tried formatting and starting over then it shouldn't have any issues. The only other option is to manually edit the drivers ".cat" file with the s3's actual physical address before installing the drivers, but this is in extreme circumstances when the os is not "playing ball".
Also remove kies or at least stop all of its running processes when using odin.
My advice at this stage is to manually remove all drivers from the pc OS regarding the s3 and wait until we figure out where the s3 is at. I have a gdrive with some useful stuff that I know works on Windows XP flawlessly. https://drive.google.com/folderview?id=0B4vTiHTBB629ZW5vQndpbjFnblk
One question though.. When you pull the battery out and reinsert it. Does the phone automatically boot to download mode, is it stuck there permanently or does it boot loop?.
Beamed in by telepathy.
shivadow said:
Relax.. I understand how frustrating it can be.
I need a detail explanation of what you did to get it into that state and what you've tried. A bullet point list will suffice. I just need to know so I can work out how buggered it is and where to go from here.
I need to know which PC operating system you're using, which variant of s3 you have including its region (this can be determined by the sticker in the battery compartment unless you already know.
There is a possibility it is your os not detecting the device because of drivers but if you've tried formatting and starting over then it shouldn't have any issues. The only other option is to manually edit the drivers ".cat" file with the s3's actual physical address before installing the drivers, but this is in extreme circumstances when the os is not "playing ball".
Also remove kies or at least stop all of its running processes when using odin.
My advice at this stage is to manually remove all drivers from the pc OS regarding the s3 and wait until we figure out where the s3 is at. I have a gdrive with some useful stuff that I know works on Windows XP flawlessly. https://drive.google.com/folderview?id=0B4vTiHTBB629ZW5vQndpbjFnblk
One question though.. When you pull the battery out and reinsert it. Does the phone automatically boot to download mode, is it stuck there permanently or does it boot loop?.
Beamed in by telepathy.
Click to expand...
Click to collapse
1st of all I want to thank you bro for reply...
Now..
I am using Windows 10 64bit, using Samsung galaxy sIII GT-I9300 Indian single sim varient.
I rooted it using KingoRoot successfully but I found I wasn't able to get SuperSU and without that I was not able to use root fun properly so I tried to flash the same with flashFire.. it failed as it require SuperSU. So I tried installing TWRP recovery from playstore and it started flashing and after reboot, It stuck on the Downloading mode.. No matter how many buttons I tried pushing combined it stuck on downloading mode...
I tried almost all method on YouTube and websites but it still don't work. Worst thing .. I tried fixing the same by Kies as well as ODIN but .. I never detect my phone.. when i connect my phone after uninstalling and Or installing the samsung driver and Kies as well.. windows didn't recognise it.
I am about to give up n this and almost ready to smash the phone with wall hammer and throw it under my car tyres but I committed myself not to do that before 14th May.
The problem is most likely Windows 10 64bit. I'm quite sure the drivers don't agree with them.
You're going to have to find an older OS and try it. Either use a virtual machine or dual boot and load up a real OS like XP. Then we can begin the proper problem solving. I hate putting percentages on things but I'm 90% confident that windows 10 is an issue here, mainly for the fact it is 64bit and the drivers aren't made for that.
As for button combo's if they don't work while booting and it goes straight to download mode then there is a big problem and it could be bricked. You can try holding just the power button for about 15 seconds while in download mode and it "should" attempt to reboot. If not then as I said, big issue ahead.
No matter what you need to get it seen by odin so get yourself xp somehow and use the stuff on my gdrive. You need to get yourself a copy of the latest firmware for your phone, ready to flash via odin should you get it to see the phone.
Beamed in by telepathy.
Windows 10 to win7
shivadow said:
The problem is most likely Windows 10 64bit. I'm quite sure the drivers don't agree with them.
You're going to have to find an older OS and try it. Either use a virtual machine or dual boot and load up a real OS like XP. Then we can begin the proper problem solving. I hate putting percentages on things but I'm 90% confident that windows 10 is an issue here, mainly for the fact it is 64bit and the drivers aren't made for that.
As for button combo's if they don't work while booting and it goes straight to download mode then there is a big problem and it could be bricked. You can try holding just the power button for about 15 seconds while in download mode and it "should" attempt to reboot. If not then as I said, big issue ahead.
No matter what you need to get it seen by odin so get yourself xp somehow and use the stuff on my gdrive. You need to get yourself a copy of the latest firmware for your phone, ready to flash via odin should you get it to see the phone.
Beamed in by telepathy.
Click to expand...
Click to collapse
I have moved to windows 10 to win7.. and tried all over again (in the process to downgrade the same i formatted by all drive.. thanks to my idiot brother)..
i tried all the same thing again but still no luck..
now trying windows XP 32 bit in virtual machine.
i will let you know..
and i am thinking to hand it over to samsung service center.. lets see what they can do?
Gr8mobiPro said:
I have moved to windows 10 to win7.. and tried all over again (in the process to downgrade the same i formatted by all drive.. thanks to my idiot brother)..
i tried all the same thing again but still no luck..
now trying windows XP 32 bit in virtual machine.
i will let you know..
and i am thinking to hand it over to samsung service center.. lets see what they can do?
Click to expand...
Click to collapse
If you can afford to have them look at it then it's up to you but you will be billed for it as the s3 is out of warranty. They haven't made the s3 for about 3 years now.
Beamed in by telepathy.
shivadow said:
If you can afford to have them look at it then it's up to you but you will be billed for it as the s3 is out of warranty. They haven't made the s3 for about 3 years now.
Beamed in by telepathy.
Click to expand...
Click to collapse
I know.. hopefully it will be done under my expectation.. or last thing I know to donate the same to hammer and trash bin :cyclops:

Categories

Resources