Related
I know there are various threads like this one but my situation is a bit different. I tried using odin to clean install 2.2 to then use the custom rom epic experience. I attempted to install 2.2 using odin but it would get stuck in "setup connection" and I would have to quit and try again. Last time I tried my phone got the "phone connection caution computer" icon and to get into recovery I would have to hold the power and camera button, not the volume down button. When I go to try and install things straight from my SD card I would get an error like "status 7" cus I didn't have the sprint apps to install 2.2. I believe I get these errors installing straight from the card cus I rooted my phone, modifying the kernal cus I read somewhere because when trying to update, it tries to verify but can't cus things are missing or edited cus of the root. I can't try to use odin again because my computer can't recognize the phone anymore regardless reinstalling the samsung drivers. SOOOO, I'm basically ****ing stuck for sure I think. The way I access the SD card is by using an adapter. The only way I see this working is if I find a fix using the SD card, but it's looking slim cus of the stupid root.
I don't know much about this yet, as I'm still learning myself. Did you try using another usb port and are you putting the phone in download mode?. Restart the computer and the phone. Make sure odin is running before you plug in the phone as well. And try another usb port. Are you using the cable that came with the phone? That one trends to have problems for some people.
Edit: I don't believe your phone is bricked either, people tend to throw the word around to much because that arnt quite sure about the definition. Just hang in there and the community will help you get back up and running. Good luck
Sent from my shoe, I mean....Epic shoe... I mean Samsung Epic!
mxcoldhit said:
I don't know much about this yet, as I'm still learning myself. Did you try using another usb port and are you putting the phone in download mode?. Restart the computer and the phone. Make sure odin is running before you plug in the phone as well. And try another usb port. Are you using the cable that came with the phone? That one trends to have problems for some people.
Edit: I don't believe your phone is bricked either, people tend to throw the word around to much because that arnt quite sure about the definition. Just hang in there and the community will help you get back up and running. Good luck
Sent from my shoe, I mean....Epic shoe... I mean Samsung Epic!
Click to expand...
Click to collapse
You see, I'm out of options. Last thing I thought of was installing a custom rom 2.1 rom cus 2.2 roms need odin, but I try to install and I get a signature error or whatever. I'm about to throw the phone against the wall, crack the screen, and use my warranty and get a new phone cus I literally tried EVERYTHING. I spent my ****ing 8 hours of my saturday trying to fix this.
Try a different computer my new Dell XPS 9100 will never reconize my Epic, however, my wifes laptop will always reconize it. I know that sounds weird, I always thought I had a poblem with my phone but it ended up being my computer.
Sent from my SPH-D700 using XDA App
cbpagent72 said:
Try a different computer my new Dell XPS 9100 will never reconize my Epic, however, my wifes laptop will always reconize it. I know that sounds weird, I always thought I had a poblem with my phone but it ended up being my computer.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
omfg, I used my mom's lappy and the drivers worked. Meaning I can try and use an odin fix.
Odin can be tricky to use because of a few factors other than itself. 1) if you can, use a deskto pc and attach to a usb port literally on the motherboard, no front or pci, this may work, but this I what I found (reading countless threads) to be the most failsafe for everyone. 2) your sammy usb cable is for charging or non critical data transfer ONLY, as it is garbage... repeatedly proven in the threads. 3) reboot pc and phone, boot phone into download mode, (hold down 1. On physical keyboard and press power... DO NOT CONNECT YET! Start up odin, place files where needed (.pit, etc...) uncheck all but what you're told in the flashing instructions with the file you're flashing, most have awesome detals, but sometimes your little issue is resolved on page 50 of the thread... not in the OP. Ok so now plug in the usb connection, odin should find it. If it doesn't, search for drivers, uninstall, reinstall start over, OR you have a bad connection, refer back to usb port and cable. I have 1 out of 4 mobo usb ports that the drivers will maintain a connection to, so try another. Then, once odin has a connection, make sure you're following the guides to the T (and read all the posts)... after that, odin is your best friend. The problem lies elsewhere... odin is the goods. If you have run into problems maintaining connection, and plan to re-root, read all the one click posts and if it drops connection a lot, enter the commands in one by one, repeat if one fails till it sticks. There are way better guides, but you seem to have run into the same issues I did, and after hours and hours, I got that scary ass reconnect me now screen. Just read the whole threads, and if your problem hasn't already been resolved, post in the appropriate thread, so others may learn from your discoveries!
Don't give up, once you figure out the quirks of the relationship between your pc and phone, and of course meticulously follow instructions, your elation when successful will make you forget that pesky 'bricked' screen... trust me I got it too, and no matter how much everyone says you can't brick these following instructions on here... its still scary till it all works. If things are wonky, wipe, go back to DI18 and start over... or just sit tight for froyo roms... good luck!
Oh, and sorry for no links, but it would seem you've probly already read em all... not sure I can do links...
Maybe its just my eeepc that doesn't like the drivers, good luck! Sounds like you're on the way... oh don't forget with the drivers to let em install on connect, leave it plugged in for like 10 mins, unplug, it will then complain it wasn't done, reconnect, then after that finishes, reboot. Crazy drivers...
At least I got a computer recognizing my phone, so I can try and use odin. I've been trying to use this fix
http://forum.xda-developers.com/showthread.php?p=9755894#post9755894
and so far odin has been stuck at this one step "file analysis..."
Yeah I used that method to no avail, but it was about 3 pasts old at the time, so I figured id try
something more stable. Tried a couple dk17 roms, then went back to 2.1 and am now using syndicate xtreme. Id suggest going back to DI18, then go from there. Let me check for another post of mine, theres a dialer code I had to do too at one point...
Ok when doing one click root, someone suggested ##8778# in the dialer, then keyboard enter, then set UART to pda not modem. This and removing comodo firewall, all the sudden my intermittent connection was solid. Not responsible for what this does, but it worked for me. Never found out what it does..... still curious. So this may help you even in odin, try to flash di18 after doing this, then the all in one rom you're looking at...
Oddly enough, I managed to semi-brick my phone several hours ago - my wireless adapter was on the same USB header, and both the wireless adapter and the phone crapped out while trying to flash with Odin.
Thankfully I was still able to get into download mode, and plugging the phone into a different USB port worked fine.
After some more research, about 10 hours of it, odin finally cooperated with me after I downloaded about every kind of file that could make my phone work and finally got it into 2.1
I first flashed the stock kernal to get it working, then flashed stock 2.1
Now I'm that my phone isn't rooted anymore I tried installing 2.2 through the recovery menu and I still get error status 7. Any ideas?
Probly best to post in the thread for the package/rom you are trying to install... others using it should be able to help... or you can do a 2.1 rom and wait for a final froyo based rom... glad to hear you're not bricked... the only way I've heard you can absolutely do that with these is installing a GSM rom or something crazy like that... but non-functional phone is scary regardless...
ungovernable1977 said:
Probly best to post in the thread for the package/rom you are trying to install... others using it should be able to help... or you can do a 2.1 rom and wait for a final froyo based rom... glad to hear you're not bricked... the only way I've heard you can absolutely do that with these is installing a GSM rom or something crazy like that... but non-functional phone is scary regardless...
Click to expand...
Click to collapse
Alright I completely fixed my phone. After I rooted my phone on 2.1, I then used odin v1.6 to install the froyo .tar file into pda and it worked. I then rooted it again so now I'm back to normal. Honestly, I did so many things I forgot what I did but I now have my phone functional. Thanks for help everyone, I greatly appreciate it!
So I want to root my phone, but I cannot get ANY computer to recognize the phone when it is in either download mode, or debug mode.
I'm running Sprints stock EB13 right now.
I've downloaded the samsung drivers and installed them.
I've tried 3 computers -- A XP 32bit, a vista 64bit, and a 7 64bit system. I've also tried 3 different cables. Nothing works.
The phone is recognized fine in mass storage mode.
Tried restarting the phone many times, removing the battery, etc.. same with the computer side of things.
I'm out of ideas to try and can't find a good post with a fix.
Thanks for any input!
syntax_erorr said:
So I want to root my phone, but I cannot get ANY computer to recognize the phone when it is in either download mode, or debug mode.
I'm running Sprints stock EB13 right now.
I've downloaded the samsung drivers and installed them.
I've tried 3 computers -- A XP 32bit, a vista 64bit, and a 7 64bit system. I've also tried 3 different cables. Nothing works.
The phone is recognized fine in mass storage mode.
Tried restarting the phone many times, removing the battery, etc.. same with the computer side of things.
I'm out of ideas to try and can't find a good post with a fix.
Thanks for any input!
Click to expand...
Click to collapse
what are you running on your PC that you want to connect to the phone with?
Odin (in download mode?)
ADB in debugging mode?
What exactly are you trying to run ??
jdelano said:
what are you running on your PC that you want to connect to the phone with?
Odin (in download mode?)
ADB in debugging mode?
What exactly are you trying to run ??
Click to expand...
Click to collapse
I wanted to use Odin to go back to DI18 at first. After that didn't work I tried ADB in debug mode, and that no longer works!
I know ADB in debug mode used to work when I was on DI18 because I used it before when I first got my phone. Now I've upgraded to EB13 from the file samsung provided on their website. I've also tried a hard re-set of the phone and that didn't help either.
I had a similar issue. I was able to resolve it by creating a fresh user in windows and then running it from there.
Sent from my SPH-D700 using XDA Premium App
iil said:
I had a similar issue. I was able to resolve it by creating a fresh user in windows and then running it from there.
Click to expand...
Click to collapse
umm..yeah three complete different computers?...I don't think thats the case.
syntax_erorr said:
So I want to root my phone, but I cannot get ANY computer to recognize the phone when it is in either download mode, or debug mode.
Click to expand...
Click to collapse
I had this exact problem with my Epic also. I tried rooting my fone too, for like 2 months straight, with no luck... Tried every technique, software, and trick in the book and nothing worked...
2 days ago though, I finally rooted it using this solution:
Forget about trying to "root" it.
Instead, flash the "Stock EB13 Deodexed EXT4 + CW 3.0.0.6" to your fone (search the forum, you'll find it and the thread that explains how to do it).
It's pre-rooted too!
It worked fabulous for me. I am now rooted and well on my way to fully customizing my fone.
Odin is finicky though... I had to switch the usb cord around to several different ports before it recognized my fone. Also, it kept locking up at a certain point in the flashing process, but after moving the image from "Phone" to "PDA" (you'll know what these are once you open up Odin), it worked brilliantly.
Try it, it works!
P.S. Just in case this helps anyone; I should note that originally I upgraded from Eclair to the official unrooted straight from Samsung (before they pulled it) stock Froyo. I loved it, but wanted it rooted.
I read somewhere that it was easier to root it if you reverted back to Eclair first. So I did (search forum for uninstalling Froyo).
And from Eclair, I flashed to the above mentioned rooted and deodexed version of Froyo (EB13).
Hope it helps!
syntax_erorr said:
I wanted to use Odin to go back to DI18 at first. After that didn't work I tried ADB in debug mode, and that no longer works!
I know ADB in debug mode used to work when I was on DI18 because I used it before when I first got my phone. Now I've upgraded to EB13 from the file samsung provided on their website. I've also tried a hard re-set of the phone and that didn't help either.
Click to expand...
Click to collapse
Might try looking at the usb on the phone to check for something preventing a good connection; I've read where people have found bent connectors and were able to fix it.
Good luck; that has to be extremely frustrating.
I tried everything like you, multiple cables, multiple computers, EVERYTHING!!!
I finally broke down and took it to sprint and they couldnt even get it to connect or fix the problem so i got a new epic. You might just want to take it back and get another one. Im on my 3rd epic now so that should tell you something about these ****TY phones...
Ok,a few months ago I rooted my vibrant, deleted the bloatware, last week I dropped my cell and the camera stopped working,i have warranty on it, so I went to unroot my cell but now it won't connect to my pc.....
Is there anything I can do too fix my problem?
Sent from my SGH-T959 using XDA App
TatuGrim said:
Ok,a few months ago I rooted my vibrant, deleted the bloatware, last week I dropped my cell and the camera stopped working,i have warranty on it, so I went to unroot my cell but now it won't connect to my pc.....
Is there anything I can do too fix my problem?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
What do you mean by "it won't connect to my pc."
Does the phone boot into any mode? normal, recovery, download?
Does the pc recognize the phone at all?
I am assuming you have drivers installed on your pc.
Need more information on what problem you are experiencing. If you are able to get the phone to boot up and the pc won't recognize the phone, ie recognizes it as an unknown device in device manager, then you probably have the wrong drivers installed or have remnants of old drivers on your machine, which need to be cleaned out via regedit.
Anyway, this gets lengthy, however, if you can provide more information on the exact problem you are having I am sure someone can help.
Just as an example, I have an XP machine with proper drivers and the phone is always recognized after a normal boot. I have sdk on the machine at can utilize it with no problem. Until I need Odin and Download mode. Odin has nothing to do with it, the computer just drops the phone like a brick when you enter download. I walk across the office plug it into my laptop with Windows 7 flash up Odin and boom YELLOW. Back to stock. You will hear it both ways XP fails try Win 7 and viceversa.
But need more information to start.
go to this. http://forum.xda-developers.com/showthread.php?t=849028
thank him not me
flipnotiq said:
go to this. http://forum.xda-developers.com/showthread.php?t=849028
thank him not me
Click to expand...
Click to collapse
Yes read through this it will answer your questions
So, my neighbor bought an Acer A500 a few months back. He ended up not liking it so I bought it off of him. My tablet and I got really close and I fell in love. I started neglecting my girlfriend and all that. We had a beautiful relationship; my tablet and me. But, a couple days ago I was playing N.O.V.A 3 and it froze. I thought nothing of it and just powered it down. To my dismay, it froze at the Acer screen. I restarted it again and got the same thing. My life was over. My heart felt like it was ripped from my chest... I shed a manly tear.
I've tried vol- and power, vol+ and power, the reset button, D/Ling several different update.zip files and copying them to my SD. I've spent the last couple days reading and trying everything. All I get is the Droid guy with the blue thing swirling in his chest and then him laying on the ground with a red triangle and an exclamation point.
I'm told it's most likely not a hardware issue as things things are almost bullet-proof. But, I am pretty good at breaking things
Am I screwed or does someone have a miracle they can share. My gaming life depends on it.
-Dennis.
DennisPimps said:
So, my neighbor bought an Acer A500 a few months back. He ended up not liking it so I bought it off of him. My tablet and I got really close and I fell in love. I started neglecting my girlfriend and all that. We had a beautiful relationship; my tablet and me. But, a couple days ago I was playing N.O.V.A 3 and it froze. I thought nothing of it and just powered it down. To my dismay, it froze at the Acer screen. I restarted it again and got the same thing. My life was over. My heart felt like it was ripped from my chest... I shed a manly tear.
I've tried vol- and power, vol+ and power, the reset button, D/Ling several different update.zip files and copying them to my SD. I've spent the last couple days reading and trying everything. All I get is the Droid guy with the blue thing swirling in his chest and then him laying on the ground with a red triangle and an exclamation point.
I'm told it's most likely not a hardware issue as things things are almost bullet-proof. But, I am pretty good at breaking things
Am I screwed or does someone have a miracle they can share. My gaming life depends on it.
-Dennis.
Click to expand...
Click to collapse
Do you know what you were running on this thing? Was it stock Honeycomb, scock ICS, or was it running a custom ROM? (If so which one?)
Was it ever hooked up to your PC? (This would help with retrieving CPUID, if it was.) Do you know your CPUID? (Or SBK?)
You should at the least know the answers to these questions before you attempt any type of repair, as it is almost certainly salvageable, but you will almost certainly need your CPUID.
Danny2 said:
Do you know what you were running on this thing? Was it stock Honeycomb, scock ICS, or was it running a custom ROM? (If so which one?)
Was it ever hooked up to your PC? (This would help with retrieving CPUID, if it was.) Do you know your CPUID? (Or SBK?)
You should at the least know the answers to these questions before you attempt any type of repair, as it is almost certainly salvageable, but you will almost certainly need your CPUID.
Click to expand...
Click to collapse
I was running 4.0.1 ICS. I do have my cpuid and SBK. I tried flashing a new rom using blackthund3rs flash tool but it got to about 25% and stopped. I keep losing sync with my PCs, though.
DennisPimps said:
I was running 4.0.1 ICS. I do have my cpuid and SBK. I tried flashing a new rom using blackthund3rs flash tool but it got to about 25% and stopped. I keep losing sync with my PCs, though.
Click to expand...
Click to collapse
So, do you want to go back to stock, or to a custom ROM? If you wanna go stock, the easiest way would be load a 3.01 EUU, & upgrade on the play market to 4.03. That will prove it isn't a hardware issue. Alternatively, you could root, load a recovery, a bootloader, & flash a new ROM.
Danny2 said:
So, do you want to go back to stock, or to a custom ROM? If you wanna go stock, the easiest way would be load a 3.01 EUU, & upgrade on the play market to 4.03. That will prove it isn't a hardware issue. Alternatively, you could root, load a recovery, a bootloader, & flash a new ROM.
Click to expand...
Click to collapse
To be honest, I really don't care as long as I can getting it working again. But I would rather root it.
I think I can get it to work but neither one of my computers will recognize it. It shows up in APX and says something about recovery driver mode when I plug it into the laptop with Vista automatically downloads a driver and installs it again. I've tried turning off automatic driver install but that doesn't work for some reason. The one with XP Pro just shows up APX device but the APX Flash Tool by blackthund3r says it can't find it. I've downloaded the Acer Iconia 500 drivers and installed them but that doesn't work either. I'm at a loss.
Any tips would be great. I think I have a better chance using my laptop with XP, though. I also need to let you know that I truly do appreciate you trying to help. If you're ever in Columbus Ohio, let me know and I'll buy you a beer. lol
DennisPimps said:
To be honest, I really don't care as long as I can getting it working again. But I would rather root it.
I think I can get it to work but neither one of my computers will recognize it. It shows up in APX and says something about recovery driver mode when I plug it into the laptop with Vista automatically downloads a driver and installs it again. I've tried turning off automatic driver install but that doesn't work for some reason. The one with XP Pro just shows up APX device but the APX Flash Tool by blackthund3r says it can't find it. I've downloaded the Acer Iconia 500 drivers and installed them but that doesn't work either. I'm at a loss.
Any tips would be great. I think I have a better chance using my laptop with XP, though. I also need to let you know that I truly do appreciate you trying to help. If you're ever in Columbus Ohio, let me know and I'll buy you a beer. lol
Click to expand...
Click to collapse
Sorry,I thought I responded to this yesterday, but just now noticed I didn't.
Fire it up in APX mode, and install the 3.01 EUU from the development section, (Stock ROM listing) then simply follow the upgrade path to 4.03, then root. If you drivers are installed correctly, everything will work fine, if not, nothing will happen. If it does start to load the stock ROM, then fails with a write error after it attempts to write the bootsector, you may need to run Badsector, or babsector, depending where you look. Search the recent posts on this, you will find lots of stuff.
Danny2 said:
Sorry,I thought I responded to this yesterday, but just now noticed I didn't.
Fire it up in APX mode, and install the 3.01 EUU from the development section, (Stock ROM listing) then simply follow the upgrade path to 4.03, then root. If you drivers are installed correctly, everything will work fine, if not, nothing will happen. If it does start to load the stock ROM, then fails with a write error after it attempts to write the bootsector, you may need to run Badsector, or babsector, depending where you look. Search the recent posts on this, you will find lots of stuff.
Click to expand...
Click to collapse
How would I go about installing the EUU? I have nvflash and blackthund3r's flashing tools. But I can't seem to get my PC and tablet to connect. When I plug it into my PC without being in APX mode, it just says MTP Device. When I plug it in while in APX mode it does say something about Picasso Recovery Driver.
If you could explain things to me like I'm aN idiot, I'd really appreciate it.
Thanks,
Dennis
DennisPimps said:
How would I go about installing the EUU? I have nvflash and blackthund3r's flashing tools. But I can't seem to get my PC and tablet to connect. When I plug it into my PC without being in APX mode, it just says MTP Device. When I plug it in while in APX mode it does say something about Picasso Recovery Driver.
If you could explain things to me like I'm aN idiot, I'd really appreciate it.
Thanks,
Dennis
Click to expand...
Click to collapse
Sorry for late response, I watched for reply from yourself, but you didn't answer for 10 days, I lost track. Still need help?
Danny2 said:
Sorry for late response, I watched for reply from yourself, but you didn't answer for 10 days, I lost track. Still need help?
Click to expand...
Click to collapse
Yea, it's still bricked. I did finally get the flash tool to recognize it but it kept hanging up. I also tried Timmy Dean's EUU tool and that hangs up too. I did a little more research and found that I may have a faulty emmc. I ran babsector and got 'fatal error code 9 cannot format partition BCT.' I found a thread here that discusses how to write around the bad sectors using Linux. I'm going to give that a go... I've always wanted to learn Linux. Hey, I can't screw it up anymore than it already is, right? Again, thanks for your time and effort in trying to help.
Cheers,
Dennis
Hey, before you try that, try different USB cables and ports (if u haven't already)
I had a similar problem with my phone not maintaining stable USB link to PC... after 4 days I tried a diff USB cable and boom, snap, working.
Just a thought.....
Sent from my A500 using xda app-developers app
ericpeacock79 said:
Hey, before you try that, try different USB cables and ports (if u haven't already)
I had a similar problem with my phone not maintaining stable USB link to PC... after 4 days I tried a diff USB cable and boom, snap, working.
Just a thought.....
Sent from my A500 using xda app-developers app
Click to expand...
Click to collapse
I'll give that a go, m8.
Thanks!
-Dennis
DennisPimps said:
I'll give that a go, m8.
Thanks!
-Dennis
Click to expand...
Click to collapse
Just wondering if you ever figured out the errors you were getting during flashing? Currently having the same issues when using babsector.
Hello!
I think I somehow deleted a crucial file...
Okay, so my phone won't connect to my computer anymore. I am using Windows 8 so aside from Windows 8 automatically downloading the drivers on its own, I took additional steps and downloaded the drivers directly from samsungs site. I've tried using different ports, different usb cables and different computers. All that happens is a lightning bolt telling me my phone is charging.
My phone used to be rooted. When I noticed the problem, I unrooted the phone and tried restoring the phone. (I tried booting in recovery and doing it that way as well as restoring it through settings).
I've downloaded just about every app that has the word 'mount' in it to see if it will help and nothing happens.
Every time I restore my phone, the first thing that pops up is a notification saying that samsung link has stopped working. I'm on android 4.2.2
Whenever I've restored my phone in the past, I've always been successful but that was also because I was able to flash a factory ROM through odin on my computer.
When I put the phone in developer mode, it shows in the corner:
CURRENT BINARY: CUSTOM
CURRENT STATUS: CUSTOM
Root checker says I am not rooted so I'm guessing that the BINARY and STATUS is coming up as custom because I am not fully unrooted (however, I had the problem of not being able to connect via usb when I was rooted).
If you have any ideas, I will definitely try them!
Oh, one more thing. Before my phone stopped connecting to my computer, I purchased additional batteries for my phone. I say this because It had been a fairly long time before I realized that my phone wouldn't connect to my computer because I no longer used my computer to charge my phone. And I say that because when I was rooted, I used titanium backup as well as CMW and neither was able to restore my phone back to a time that the usb worked again.
Okay, I think that's it. It's a lot of details but I didn't want to waste anyone's time coming up with ideas if I had already tried one.
Thank you!
swagganation said:
Hello!
I think I somehow deleted a crucial file...
Okay, so my phone won't connect to my computer anymore. I am using Windows 8 so aside from Windows 8 automatically downloading the drivers on its own, I took additional steps and downloaded the drivers directly from samsungs site. I've tried using different ports, different usb cables and different computers. All that happens is a lightning bolt telling me my phone is charging.
My phone used to be rooted. When I noticed the problem, I unrooted the phone and tried restoring the phone. (I tried booting in recovery and doing it that way as well as restoring it through settings).
I've downloaded just about every app that has the word 'mount' in it to see if it will help and nothing happens.
Every time I restore my phone, the first thing that pops up is a notification saying that samsung link has stopped working. I'm on android 4.2.2
Whenever I've restored my phone in the past, I've always been successful but that was also because I was able to flash a factory ROM through odin on my computer.
When I put the phone in developer mode, it shows in the corner:
CURRENT BINARY: CUSTOM
CURRENT STATUS: CUSTOM
Root checker says I am not rooted so I'm guessing that the BINARY and STATUS is coming up as custom because I am not fully unrooted (however, I had the problem of not being able to connect via usb when I was rooted).
If you have any ideas, I will definitely try them!
Oh, one more thing. Before my phone stopped connecting to my computer, I purchased additional batteries for my phone. I say this because It had been a fairly long time before I realized that my phone wouldn't connect to my computer because I no longer used my computer to charge my phone. And I say that because when I was rooted, I used titanium backup as well as CMW and neither was able to restore my phone back to a time that the usb worked again.
Okay, I think that's it. It's a lot of details but I didn't want to waste anyone's time coming up with ideas if I had already tried one.
Thank you!
Click to expand...
Click to collapse
Not sure if this will work, but there's a mobile odin you can try to use.
And you can get stock ROM there.
Salil999 said:
Not sure if this will work, but there's a mobile odin you can try to use.
And you can get stock ROM there.
Click to expand...
Click to collapse
Ii'm not rooted anymore so mobile odin doesn't work
swagganation said:
Ii'm not rooted anymore so mobile odin doesn't work
Click to expand...
Click to collapse
Try and download a ROM that is pre-rooted. Maybe that will work!
Salil999 said:
Try and download a ROM that is pre-rooted. Maybe that will work!
Click to expand...
Click to collapse
Do you know how I would install a rom that's prerooted without my phone being rooted or being able to connect to a computer via usb?
swagganation said:
Do you know how I would install a rom that's prerooted without my phone being rooted or being able to connect to a computer via usb?
Click to expand...
Click to collapse
You're should have a custom recovery installed... At least that way you wouldn't need your computer. Otherwise you'd have to do it through Odin, but like you said in the OP, you can't connect to USB. Is your device rooted?
swagganation said:
Hello!
I think I somehow deleted a crucial file...
Okay, so my phone won't connect to my computer anymore. I am using Windows 8 so aside from Windows 8 automatically downloading the drivers on its own, I took additional steps and downloaded the drivers directly from samsungs site. I've tried using different ports, different usb cables and different computers. All that happens is a lightning bolt telling me my phone is charging.
My phone used to be rooted. When I noticed the problem, I unrooted the phone and tried restoring the phone. (I tried booting in recovery and doing it that way as well as restoring it through settings).
I've downloaded just about every app that has the word 'mount' in it to see if it will help and nothing happens.
Every time I restore my phone, the first thing that pops up is a notification saying that samsung link has stopped working. I'm on android 4.2.2
Whenever I've restored my phone in the past, I've always been successful but that was also because I was able to flash a factory ROM through odin on my computer.
When I put the phone in developer mode, it shows in the corner:
CURRENT BINARY: CUSTOM
CURRENT STATUS: CUSTOM
Root checker says I am not rooted so I'm guessing that the BINARY and STATUS is coming up as custom because I am not fully unrooted (however, I had the problem of not being able to connect via usb when I was rooted).
If you have any ideas, I will definitely try them!
Oh, one more thing. Before my phone stopped connecting to my computer, I purchased additional batteries for my phone. I say this because It had been a fairly long time before I realized that my phone wouldn't connect to my computer because I no longer used my computer to charge my phone. And I say that because when I was rooted, I used titanium backup as well as CMW and neither was able to restore my phone back to a time that the usb worked again.
Okay, I think that's it. It's a lot of details but I didn't want to waste anyone's time coming up with ideas if I had already tried one.
Thank you!
Click to expand...
Click to collapse
IF you can get to download mode Then jump over to this thread. Download the zipped file (from first or second post), extract the file - just to the .tar.md5 file.
While waiting for the download charger your phone to at least 50%
Also download Odin 3.x. get that here. unzip one of the Odins - I've been using 3.07
To launch Odin make sure you right-click and choose run as administrator!
Once Odin is launched go to the PDA box and select the .tar.md5 file you downloaded.
Make sure you have NOT selected re-partition. you can leave auto reboot and f.reset time checked though.
Now get into download mode - Power button + Home key + Volume down. Hold until you are asked to confirm going into download mode by selecting up volume.
Plug your phone into your computer and a com port should show in Odin3.
If it does then select start and wait till it finishes completely - it will say pass; your phone will actually reboot too.
Go through setup and there you go. new phone.
Then to root just use CF-Autoroot
My computer stopped recognizing my S4 recently, too. Odin wouldn't see it, couldn't connect it as a drive, etc. It had not been very long between when it worked and when it didn't, and I had installed a bunch of new Java stuff for (JDK7, Netbeans, Eclipse, etc). Tried the wife's S3 and same deal. So I uninstalled my Samsung drivers and Kies and booted my Win7 laptop. Reinstalled drivers, no joy. Reinstalled Kies and let it do all it's updates and that fixed the issue. Rooted, MDL, stock rom.
jejb said:
My computer stopped recognizing my S4 recently, too. Odin wouldn't see it, couldn't connect it as a drive, etc. It had not been very long between when it worked and when it didn't, and I had installed a bunch of new Java stuff for (JDK7, Netbeans, Eclipse, etc). Tried the wife's S3 and same deal. So I uninstalled my Samsung drivers and Kies and booted my Win7 laptop. Reinstalled drivers, no joy. Reinstalled Kies and let it do all it's updates and that fixed the issue. Rooted, MDL, stock rom.
Click to expand...
Click to collapse
When uninstalling old drivers make sure you go to Device manager and go to View >Sho Hidden devices and remove them too! Remove everything - all left over devices, all software and even directories for said software; Revo uninstaller works well.
Also try a brand new USB cable. Though that may not be it, I've seen that alone solve all kinds of problems! Really just a brand new cable.
If you haven't tried this already, try and make sure USB debugging is enabled?