Database Users

Computer recognition help!

Have done done searching, but still can't get my phone to connect to my computer. I've tried everything that I've found posted. Doesn't mean I found then all.
I get "usb device not recognized" when I plug on my phone. I'm trying to flash the modem to get my text messaging to work. Windows 7 64bit
DL30 black hole 4.1
Any help would be appreciated.
Sent from my SCH-I500 using XDA App

As most people would say, wrong place. This is a question that belongs in the general section.
Did you install the samsung driver onto your computer?

Kaze105 said:
As most people would say, wrong place. This is a question that belongs in the general section.
Did you install the samsung driver onto your computer?
Click to expand...
Click to collapse
Sorry about that.
Yes divers have been installed a long time. I used to be able to connect. Then about a month ago it decided to stop. I even tried it on a XP system, same thing.
Sent from my SCH-I500 using XDA App

Have you tried using a different USB cable?

mob87 said:
Have you tried using a different USB cable?
Click to expand...
Click to collapse
Yes. Tried my wifes. Tried one from my BB. Tried de-bugging mode. Tried rebooting while connected. Lol
Sent from my SCH-I500 using XDA App

Did you try a different USB port?
Also I would suggest updating to EB01 since DL30 isn't supported by devs and is a less stable Froyo build. Uninstall the Samsung drivers, reboot, reinstall and try it again.

Mine quit working today....i disabled usb debug then did a battery pull. Rebooted..enabled usb all is well...
Sent from my Froyo Fascinate.

I've had this issue and have tracked it down to my BT dongle. Every time I use it on my win 7 64bit box I have to uninstall the Samsung drivers, then reinstall without the phone or the BT dongle plugged in.

Thanks for all the input. It finally started working. I installed another rom and kernel. But now I can't get odin to recognize the phone in download mode. Weird stuff....
Sent from my SCH-I500 using XDA App

ragarm said:
Thanks for all the input. It finally started working. I installed another rom and kernel. But now I can't get odin to recognize the phone in download mode. Weird stuff....
Click to expand...
Click to collapse
I just ran into this myslef, and I believe the Fascinate has a bit of a multiple personality disorder. When I went through the Windows registry, I found entries listing the phone as a phone, as removable storage, as a SD card reader and as a CD drive. Nothing worked - no matter what I did, Windows wouldn't recognize it as anything.
To solve it, I had to uninstall the Samsung drivers and then search through the registry, removing anything that said Samsung. A bunch of keys gave me permission errors, but after finally removing them all, I connected the phone and it was immediately recognized as an Android Device. I reloaded the Samsung drivers and everything is back to normal.
A major PITA, but I'm just glad there was a solution.
If you want to try to do the same, uninstall the Samsung drivers, open regedit and search for Samsung. Delete any key that says Samsung (assuming you don't have any other Samsung peripherals). Hopefully you won't run into the permissions problems, but if you do, let me know and I'll walk you through how to get past them.

ChrisDDD, thank you. I will try that asap. That is some great information. I will report back my findings after I'm finished.
Sent from my SCH-I500 using XDA App

Well finally got around do working on this. And YES it worked. At least on my XP machine. Got some permission problems on my win 7 machine.
Chris, thanks for that bit of info. Only thing I had to do different than most was to reboot my phone in download from the menu that is installed with my kernel. I couldn't get it to work by pulling the batt and hooking up to pc. Funny stuff trying to get this stuff to work.

Kindke fire hd 7" not recognised in windows or Linux

Well.... no effing clue whats happened.... it must've updated recently as no longer rooted or using golauncher... getting rather annoyed at the inability to access the internal storage via usb...
Windows brings up a massive message that when i googled it the fix was to apparently unplug the pc.... which resolved a few issues but still get the same issues with the kindle... which sucks.... managed to connect briefly with Linux but now it just seem to not acknowledge it at all....
I had what i thought were the latest drivers as i only installed them a couple of days ago.. (rediscovered scummvm!!!)
Any ideas what I can do? I want to re root and flash a totally new rom as the amazon one is truely awful
And which is the best root method for 7.4.6? If there is one....
Thanks again peeps!
Sent from my KFTT using Tapatalk now Free

shugs81 said:
Well.... no effing clue whats happened.... it must've updated recently as no longer rooted or using golauncher... getting rather annoyed at the inability to access the internal storage via usb...
Windows brings up a massive message that when i googled it the fix was to apparently unplug the pc.... which resolved a few issues but still get the same issues with the kindle... which sucks.... managed to connect briefly with Linux but now it just seem to not acknowledge it at all....
I had what i thought were the latest drivers as i only installed them a couple of days ago.. (rediscovered scummvm!!!)
Any ideas what I can do? I want to re root and flash a totally new rom as the amazon one is truely awful
And which is the best root method for 7.4.6? If there is one....
Thanks again peeps!
Sent from my KFTT using Tapatalk now Free
Click to expand...
Click to collapse
You would probably benefit most by using KFFA to return to 7.2.3 then root, remove OTA updates and install GApps. This way when you go to install a custom ROM, you have a matching boot loader. In order to put a custom ROM on, you need to flash a 2nd boot loader and TWRP. All this is covered in great detail on here. If you have questions do ask.
Sent from my Kindle Fire HD 7 running 4.3 Paranoid Android using xda app-developers app

I recommend Paranoid Android indeed!

Soft brick but with no adb connection on bootloader

Ok, tired of waiting for the OTA KitKat update for my Nexus 7 2012 tablet, I downloaded the OTA update and sideloaded it with adb. Got a status 7 error and now it's stuck on a bootloop. Thing is, my Windows 8 laptop won't recognize the device anymore (code 43 error on device manager) when on recovery or bootloader. There's even no way to instal google's usb drivers or anything because it says the device malfunctioned. I downloaded the factory image but, obviously, can't sideload it or do anything with it.
Please give me a hand with this, I'm really desperate.

More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app

nobody_nowhere said:
More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Sorry, wasn't sure what you needed. The bootloop esentially goes from recovery to off and then to recovery again. I am able to go to fastboot normally (power and volume down when off).
Wanting to root the device a while ago, I unlocked it and rooted it whitout issues. Since the 4.3 update though, it was a little more difficult to root so having no time to research I just left it at that. That's all that was done to the Nexus 7. No Custom Recovery, no ROM, no nothing. Now, waiting for 3 weeks for KitKat, decided to sideload the OTA update (I did check the version was my device's version) the status 7 error appeared and all hell broke loose with the computer not recognizing the device.

Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app

Duplicate post. Please erase.

nobody_nowhere said:
Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Yeah, that's what relaxes me a bit, but I can't seem to fix it for 20 hours straight. I use this for studying.

Well, I suggest using another computer (a friend's or relatives') or installing a Linux distro like ubuntu. Oses other than Windows usually don't have such problems. I suggest you download something called adb gui which as I recall did a pretty fine job of 're installing the drivers for me.
But then, please do correct me if I'm wrong... I think that you must first use the device on adb and get the drivers installed and then only can you use it by the fastboot interface.
Sent from my GT-S5570 using xda app-developers app

I used Wug nexus root toolkit to install drivers (windows 8.1) there are clear instructions (if you click manual or something similar) how to get drivers to work.

Yeah, actually I did use the toolkit when I was trying to update to KitKat. Thing is, it doesn't work since the bricking occurred.
Yeah, I'll try on another pc, and I'll keep you posted.
Thanks
Sent from my Nexus 4 using xda app-developers app

I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.

Johnson90512 said:
I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.
Click to expand...
Click to collapse
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app

nobody_nowhere said:
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?

Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
It pretty much cancels out any problems with drivers.
It is easy to do.
It takes 5 minutes to boot up and test? Try it for yourself
Sent from my Nexus 5

Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app

nobody_nowhere said:
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
I appreciate the advice, I will give it a shot this evening, and let you know if this works. I'm sure that it will.

Alright, so I got SDK up and running on Linux! It was a little bit of a pain, but it installed just fine. Once I got it all installed I was able to see the nexus 7 through fastboot! From there I was able to reinstall the bootloader. Then was able to get to recovery to do an adb push to get a rom of 4.4 on to it. 4.4 installed just fine. All problems are fixed Good suggestions guys!

[Q] Boot Loop of sorrow

I need Major help with my phone. So here's the run down.
Starting on a Tuesday my phone started acting funny, it would get to the AT&T logo and stop, but then if I removed the battery and hold down the power button for roughly 20 seconds and start it up it would come on without any problems that I could see. Through the week it got worse, and by that I mean that it would restart on it's own, randomly. By that Sunday pulling the battery and holding the power button no longer did anything and from what I understand it is stuck in a boot loop.
I should have started by asking all of you, but unfortunately for me I tried fixing it myself by searching for the answers.
This is where my phone sits. It was rooted, but there is no back up. I can get to the Android system recovery. I foolishly did a reset and cleared my phone (I have all of my info and pics backed up so I'm not worried about that). My computer does not recognize my phone unless I go into the ADB setting in recovery mode and as far as I can tell the computer just knows that something is connected through USB but can't quite tell what it is. Kies has been installed on said computer recently so I have the newest Samsung drivers. I have a 32 gb sd card for my phone if that helps any. I forgot to mention that my phone is running Version 4.3 of the S4 software.
I am a total noob when it comes to these types of problems so please help me.

Do you know what firmware version you're on? Did you do a factory reset in recovery? Kies is junk you're probably going to have to use Odin. But even that may not work based on your description of the problems.
Sent from my Nexus 5 using XDA Free mobile app

Re:
jd1639 said:
Do you know what firmware version you're on? Did you do a factory reset in recovery? Kies is junk you're probably going to have to use Odin. But even that may not work based on your description of the problems.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I am running Version 4.3. I only installed Kies to make sure I had the right driver, but you're right, Odin doesn't see my phone. I did do a factory reset in recovery, hopefully I didn't completely screw myself.

Bulk like Hulk said:
I am running Version 4.3. I only installed Kies to make sure I had the right driver, but you're right, Odin doesn't see my phone. I did do a factory reset in recovery, hopefully I didn't completely screw myself.
Click to expand...
Click to collapse
If Odin the mk2 tar file, see the all in one from here
http://forum.xda-developers.com/showthread.php?p=49687770
What Windows os version are you using? Google 15 second adb install xda and try those drivers.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
If Odin the mk2 tar file, see the all in one from here
http://forum.xda-developers.com/showthread.php?p=49687770
What Windows os version are you using? Google 15 second adb install xda and try those drivers.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm running Windows 7. I'll try that when I get home. I'll let you know what happens.

jd1639 said:
If Odin the mk2 tar file, see the all in one from here
http://forum.xda-developers.com/showthread.php?p=49687770
What Windows os version are you using? Google 15 second adb install xda and try those drivers.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry I haven't logged in for a while. This worked very well, thank you.:good:

[Q] Help stuck on "System Software not authrized by AT&T has been found on your phone

[Q] Help stuck on "System Software not authrized by AT&T has been found on your phone
Well as the title says thats exactly what happened. It happened when I booted to recovery on Rashr recovery tools. Mistake on my part. I also know that there are similar threads, but I've already tried them out but they don't work for me. So I thought this would be the best way. The situation is well... its stuck on that error message. I tried to factory reset with ODIN but ODIN never detects my phone when I plug it in. I already tried taking the battery out and putting it back in. Then i tried Kies, but no luck there either since I can't find the serial number on the back of the phone sticker nor on the box of the phone. Does this mean my phone is dead?

Odin will work. You just need to get it to recognize your device. You have a usb driver issue. You need to install the court drivers. Kies should have done that but it can get in the way of Odin. Uninstall kies but keep the drivers and try Odin again.
Sent from my Nexus 5 using XDA Free mobile app

Okay I uninstalled kies, and updated my drivers to 1.5.45 on the Samsung website, but Odin still doesn't detect it. I feel like I'm missing something.

Psysora said:
Okay I uninstalled kies, and updated my drivers to 1.5.45 on the Samsung website, but Odin still doesn't detect it. I feel like I'm missing something.
Click to expand...
Click to collapse
Are you using Windows 8? You need to allow it to use unsigned drivers. Google how to do that if you do
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Are you using Windows 8? You need to allow it to use unsigned drivers. Google how to do that if you do
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
No, I'm on Windows 7 Home Premium.

Psysora said:
No, I'm on Windows 7 Home Premium.
Click to expand...
Click to collapse
With your device plugged into the pc, go to device manager. There's probably an exclamation mark on one of the usbs. That's the one having the issues. Right click on it and up date the driver. Go to where it say let me pick from a list on the computer. Pick the Samsung adb android interface, or something along those lines.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
With your device plugged into the pc, go to device manager. There's probably an exclamation mark on one of the usbs. That's the one having the issues. Right click on it and up date the driver. Go to where it say let me pick from a list on the computer. Pick the Samsung adb android interface, or something along those lines.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks a lot for the help, but oddly enough when I was about to try your idea i entered download mode to install a custom os. Of course
I didn't need to not I restarted my phone, and VIOLIA it works. Seriously what a turn of events. It now works perfectly. But, seriously thanks man, if that didn't happen just now I know for sure you would've helped me out and my phone would work. This was really just a shortcut if you think about it. Either way thanks a lot you were a great help.

Psysora said:
Thanks a lot for the help, but oddly enough when I was about to try your idea i entered download mode to install a custom os. Of course
I didn't need to not I restarted my phone, and VIOLIA it works. Seriously what a turn of events. It now works perfectly. But, seriously thanks man, if that didn't happen just now I know for sure you would've helped me out and my phone would work. This was really just a shortcut if you think about it. Either way thanks a lot you were a great help.
Click to expand...
Click to collapse
No problem, just glad it's working for you
Sent from my Nexus 5 using XDA Free mobile app