So... after spending 2 hours searching and asking around in various android irc channels i come to you XDA...
I have an ATT SGS3 that i used odin to install CWM and subsequently root, etc etc.
I went to do another today on the same machine but when going into recovery [cwm] windows tells me no device drivers were found. Ive tried the original device as well and it throws the same error. If i boot into android it uses the drivers.
I've re installed the drivers at least 10 times using various methods. ive tried updating the driver via device manager also with no joy. Any help would be appreciated.
krstnsn said:
So... after spending 2 hours searching and asking around in various android irc channels i come to you XDA...
I have an ATT SGS3 that i used odin to install CWM and subsequently root, etc etc.
I went to do another today on the same machine but when going into recovery [cwm] windows tells me no device drivers were found. Ive tried the original device as well and it throws the same error. If i boot into android it uses the drivers.
I've re installed the drivers at least 10 times using various methods. ive tried updating the driver via device manager also with no joy. Any help would be appreciated.
Click to expand...
Click to collapse
Bump.
Same here.
id like to update.
Adb works on windows and linux with 2 ATT SGS3s... in stock recovery and android [CM10] but not CWM. Ive tried 3 versions of CWM to no joy.
In linux when i LSUSB it shows nothing when in CWM.
I cant believe no one else is having this issue.
Try installing the Universal Naked Drivers from here:
http://forum.xda-developers.com/showthread.php?t=1766220.
I suggest unpacking the drivers, booting your phone to recovery, and then connecting it to your computer. When Windows tries to install the drivers, cancel out of any search it's doing and point it to the location you unpacked the drivers. If you do it this way, you will use the official Samsung drivers when booted into your ROM and the Universal Naked Drivers when in recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
drothenberger said:
Try installing the Universal Naked Drivers from here:
http://forum.xda-developers.com/showthread.php?t=1766220.
I suggest unpacking the drivers, booting your phone to recovery, and then connecting it to your computer. When Windows tries to install the drivers, cancel out of any search it's doing and point it to the location you unpacked the drivers. If you do it this way, you will use the official Samsung drivers when booted into your ROM and the Universal Naked Drivers when in recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
ill try this.
PS we live in the same city.
EDIT: This worked. thanks a ton.
Related
I was preparing to flash the stock EC05 rom with odin and did a full wipe of everything. But it seems I can't get odin to recognize the phone is plugged in (I can get to download mode, but it never shows up in Odin).
Not I'm stuck in recovery with no backup, and can't do anything.
I also can't get windows7 or adb to recognize the device.
I have the drivers I used when rooting the phone, and they don't seem to work.
Windows says "usb device not reconized... the device has malfunctioned" etc.
I have tried many cables and many computers, and nothing seems to work.
My last resort is to buy yet another cable, one recommended in another thread, but I have already bought a few cables designed for this phone, blackberry, and one just for data.
Is there anything I could flash from recovery to at least allow me to boot?
Souzhi said:
I was preparing to flash the stock EC05 rom with odin and did a full wipe of everything. But it seems I can't get odin to recognize the phone is plugged in (I can get to download mode, but it never shows up in Odin).
Not I'm stuck in recovery with no backup, and can't do anything.
I also can't get windows7 or adb to recognize the device.
I have the drivers I used when rooting the phone, and they don't seem to work.
Windows says "usb device not reconized... the device has malfunctioned" etc.
I have tried many cables and many computers, and nothing seems to work.
My last resort is to buy yet another cable, one recommended in another thread, but I have already bought a few cables designed for this phone, blackberry, and one just for data.
Is there anything I could flash from recovery to at least allow me to boot?
Click to expand...
Click to collapse
Have you tried downloading the drivers fresh from Samsung? How about different USB ports? Sounds like bad drivers though. The first time I used Odin, Windows used the drivers I installed plus got some others from Windows update. Took about 10 minutes for it to find my phone.
Which version of Clockwork are you on? If not stock you can go here and flash the EC05 stock ROMS:
http://forum.xda-developers.com/showthread.php?t=1027904
Classic sign of bad drivers or a bad cable. Don't waste your time on the stock cable - get another, and plug it into a different port. Reinstall the drivers if you need to.
I'm kind of stuck here. I'm not big into flashing roms and stuff.....but had issues with the one ROM I flashed 2 years agao so I thought I'd upgrade to CM10 finally. I flashed it properly using CWM and had a working rom....but forgot todarkside super wipe and to install the gapps.zip. So I thought I'd just do it over again. Everything seemed fine in the reinstallations of all 3.....but when I started the phone up it got stuck on a boot loop on the Cyanogen animation. No big deal....I'll just flash it again. Go into recovery mode.....wipe the data/cache.....it freezes on the cache. Try to flash the rom, cWM , the old rom, anything.......it gets stuck on the first "Installing....." . Not good. Can't do anything in CWM.
So I read a million webpages trying to figure out what to do next......someone else had to have had this problem. Seems like my only option is to go through Odin and flash it there. I make sure I get the USB drivers from Samsung and install those first. The installation goes through no problem......I reboot....and then try to plug in my phone via Download Mode. I make sure I use the USB cable that came with my phone and use a powered port on the back of my computer (XP btw). Windows recognizes it with its usual bull**** fanfare of 3 different notifications......"Found New Hardware!" then it says Found! "MSM8x60" then it says Windows failed to fully install new hardware. In the Device Manager its shown as the "Samsung Mobile USB CDC Composite Device" with the dreaded yellow exclamation mark on it. I tried uninstalling the drivers....rebooting.....and then reinstalling. No luck. Tried an older driver package.....no luck. I've spent hours trying every combination with no luck. I can't get Windows to recognize it....or more importantly.....Odin to recognize it. Any thoughts? Thanks.
Sorry for my English.
A lot of different things can happen if you are not using the correct version of recovery. The latest recovery doesn't always mean it will flash properly. For example I had to use TWRP 2.6 for 4.3 based ROM and had to roll back to TWRP 2.5 for some other versions of a rom. I don't know which version of CM you are using but maybe try TWRP or another version of CM.
Sent from my SGH-T989D using Tapatalk
Yeah....that makes sense. But how do I flash a different version of CWM? I can't get the phone detected by Odin.
Resolved.....tried a couple of other PCs....found one that worked
Ok, so my problem is the next one:
I have rooted my phone now 6 months, from then I haven't used ODIN. Now I want to install android 4.2.2 so I want to unroot my device, when it's turned on, it is recognized by computer and I can share files, photos etc.
Short version to the problem: ODIN doesn't recognize my Samsung Galaxy Note II when it's in download mode, even if I followed all the steps correctly.
I tried:
- Using another USB cable
- Using another USB port
- Followed the instructions - 1. Turn off the device 2. Enter download mode 3. Connect it 4. Open ODIN
None of above helped me. It's not from the drivers or kies, because my phone is recognized by computer.
I really try from a week to solve the problem from tutorials or internet, but I couldn't find any solution so I hope someone could help me.
Try to uninstall Kies. It really messes things up. Leave only the drivers, or uninstall everything Kies related and put these drivers. Then try again.
Experienced much the same symptoms today, not having updated recently, phone would be recognized by Kies, by the PC, but not in download mode by Odin. Tried removing Kies, Kies Air, previous drivers, reinstalling drivers mentioned above. Nothing. And then I happened to click on an older version of Odin accidently and it recognized my Note 2 SGH-i317m almost immediately. Odin3 ver 1.82. Have no idea why but for your information in case it helps you.
Makes sure kies is not running in background. End the process from Teal manager and try again.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Note note not recognosed by Note 2
I rooted My note 2 about a month ago and now i want to install the stock ROM back. but then i connect my Note 2 to my PC and run Odin, its not recognised. i have removed kies from my PC and installed the drivers as mentioned.
i restarted m PC and disable the antivirus as well. Still then, no change.
Can some one please help me out with this issue
Hi,
I have similar problem with my Note II. When I had rooted phone, computer didnt recognize my phone. I tried to reinstall drivers, using Toolkit or manually, but nothing works. Samsung Kies I havent installed on my computer, I tried to install Kies too, but Kies doesnt recognize phone too. So I installed mobileOdin into my phone and unrooted it, but "force root" was checked. So now I have "unrooted" phone with no working superuser because some binaries are missing, I have stock recovery, my computer still doesnt recognize my phone. So I cant install mobileOdin because I havent root permissions, and I cant do anything else. So what I have to do if I want to make my Note II working well with computer? I have no ideas.
Btw, another usb cabel I tried too...
Thanks for reply
Hi forum,
I'm actually in hospital for about 6 weeks and after flashing a custom Rom I want to go back to the previius issue but go back
my samsung n7100 is'nt recognized by windows 8.1 update 1 and doesn't go to recovery mode. I tried to deinstall USB-drivers and did a new Installation of the drivers, but nothing Helms.
I cannnot install any cwm-Rom.
Please help because my smarty is the only connection to my wife and children.
P.s.: sorry for my Bad English. and i wrote this thread in my sickbed.
Thanks a Lot for your patience..
Hubs135 said:
Hi forum,
I'm actually in hospital for about 6 weeks and after flashing a custom Rom I want to go back to the previius issue but go back
my samsung n7100 is'nt recognized by windows 8.1 update 1 and doesn't go to recovery mode. I tried to deinstall USB-drivers and did a new Installation of the drivers, but nothing Helms.
I cannnot install any cwm-Rom.
Please help because my smarty is the only connection to my wife and children.
P.s.: sorry for my Bad English. and i wrote this thread in my sickbed.
Thanks a Lot for your patience..
Click to expand...
Click to collapse
Uninstall the drivers again, then Try using USBDeview and delete all the devices related to android and samsung... this will remove the possibility of any device driver not being reinstalled properly by windows...
USBDeview 32-bit
USBDeview 64-bit
After this restart the pc and try installing drivers and connect the phone to see if it works...
U can try reinstalling samsung kies.
Sent from Samsung Note 2 on Phantom Kitkat Rom via Tapatalk
Windows 8.1 update 1 also can't flash anything to my phone because of drivers. I had tried every driver mtp, Sammy etc.
Here are the latest Sammy if you want to try.
http://forum.xda-developers.com/showthread.php?t=961956
Sent from my GT-N7100 using Tapatalk 2
Hubs135 said:
Please help because my smarty is the only connection to my wife and children.
Click to expand...
Click to collapse
What's the issue with your current rom? If it's working fine don't play with it, if it's not then maybe we can fix the issue.
im using windows 8.1. working & able to flash 4.4.2 with Odin 3.0.9
try install PdaNet & KIES 3
I tried all things you wrote but without any success. At least I did a new installstion of windows 8.1 but also without success. I think if its ossible for me to come into recovery mode I can Flash cwm Version of rom from my sd Card. It seems the onlyest Way to Repair my smarty.
Any tricks to get recovery mode.
Hubs135 said:
I tried all things you wrote but without any success. At least I did a new installstion of windows 8.1 but also without success. I think if its ossible for me to come into recovery mode I can Flash cwm Version of rom from my sd Card. It seems the onlyest Way to Repair my smarty.
Any tricks to get recovery mode.
Click to expand...
Click to collapse
http://stackoverflow.com/questions/21246905/cant-connect-android-device-to-pc-on-windows-8
you might need google help
Sorry, but tried all things you wrote, but without success. I googled too, but all threads say to do it. via Odin or similar but my opiniion the onlyest Way to rescue my smarty is getting in the recovery mode again.
Is there any tricky to do.this?
Bricked???
No tricks. It seems i've bricked my smarty
Nobody any Idea?
Really Nobody any Idea to recscue my smarty.
Then I've lost 336,00€,
**** ....
Hubs135 said:
Really Nobody any Idea to recscue my smarty.
Then I've lost 336,00€,
**** ....
Click to expand...
Click to collapse
Well, what's actually wrong with it, other than Win 8.1.1 not seeing it? You haven't told anyone what problems you're having other than that. It could be just something simple that someone here can help you with; that doesn't mean you have to reflash it...
Bricked - yes or no? - briefing my problem
Briefing my problem for better understanding my problem:
1. i wanted to do clean installation of sammobile rom 4.4.2 by preparing my n7100 before flashing new costum rom by deleting previous rom via a script.
2. after doing this my smartphone isn't recognized by windows 8.1 Update 1 - 64 bit
3. I tried also windows 8.1, 8 and 7 without any success.
4. i'm not be able to flash new custom rom via odin
5. on sd-card i had a cwm of rom and a backup of previous rom version, too
6. i tried to get into recovery mode by pushing sound+, on-switch and home by pushing at the same time
7. i got always immediately into download mode or in bootloop since boot sound starts (it's difficult to reconstruct the exactly way, but i had the problem not to go into recovery mode mot time before. therefore i do it always by "rom manager" appfrom chainfire).
8. i'm not be able to flash new custom rom via recovery mode
9. then i tried all tricks by searching the prroblem by google but all methods didn' work
10.. i'm be able to load my smartphone and the led lights, too.
this is why i think about my n7100 is bricked.
please, please help me!
thanks a lot
So you're bootlooping?
Your best bet is to try to access it from an older version of Windows. Probably you have a bad driver somewhere and it's causing conflicts. I have similar issues from W8, but it's fine on older OS's.
If an older version of Windows can access the device, then you should be able to reflash it. I suggest trying to drop Dr Ketan a PM, he's very knowledgeable and helpful.
see item 3, please.
im on windows 8.1
just download the lastest Samsung Kies (Samsung Kies 3) and install it.
try this
Hubs135 said:
Briefing my problem for better understanding my problem:
1. i wanted to do clean installation of sammobile rom 4.4.2 by preparing my n7100 before flashing new costum rom by deleting previous rom via a script.
2. after doing this my smartphone isn't recognized by windows 8.1 Update 1 - 64 bit
3. I tried also windows 8.1, 8 and 7 without any success.
4. i'm not be able to flash new custom rom via odin
5. on sd-card i had a cwm of rom and a backup of previous rom version, too
6. i tried to get into recovery mode by pushing sound+, on-switch and home by pushing at the same time
7. i got always immediately into download mode or in bootloop since boot sound starts (it's difficult to reconstruct the exactly way, but i had the problem not to go into recovery mode mot time before. therefore i do it always by "rom manager" appfrom chainfire).
8. i'm not be able to flash new custom rom via recovery mode
9. then i tried all tricks by searching the prroblem by google but all methods didn' work
10.. i'm be able to load my smartphone and the led lights, too.
this is why i think about my n7100 is bricked.
please, please help me!
thanks a lot
Click to expand...
Click to collapse
may be your phone has lost root access,try connecting it to kies and use the phone recovery guide if connecting your phone to pc is problem try other usb cables try the thicker shorter ones..
SOLVED !!!
:laugh::good: dr.Kretan was right.. After coming home from hospital i was able to connect my smarty to my home pc and flash kitkat 4.4.2 (france edition by sammobile) via odin.
1000 thanks to all of you for helping to solve my problem :good::good::good:
but one question is open: it's still impossible for me to get into recovery mode i don't understand tihs.any idea?
Hello...
First, the environment: P600 32GB US version. Running Windows 8.1 on my laptop, SDK installed fine. ADB drivers working with no problem.
Here's the problem: I was running the stock ROM with root for a very long time, but I decided to try the unofficial port of Cyanogenmod 12. It installed just fine, but in the process it whacked my TWRP installation on the tablet. When I rooted the tablet I had been running Windows 7 and the Samsung drivers worked without any issues, both ADB and Fastboot.
No matter what I try now, I can't get the Fastboot driver to load - the tablet is recognized as a Samsung USB composite device, but Fastboot does not see it and whenever I try to change to most any other driver, the install succeeds but the device can't start (the dreaded Code 10).
Of course, the stock recovery won't let me load anything that isn't signed by Samsung, and I can't find a stock signed image anywhere, so I can't even get back to the stock ROM. And Windows 8.1 on multiple machines seems to be working the same way, so unless I can get the right driver installed and working I can't flash anything from my laptop. Mobile ODIN doesn't support the tablet, Goo.IM Manager installed, but it apparently does not recognize the tablet either, so I can't flash anything on the tablet side, either.
Does anyone have any ideas on how I can get this to work short of throwing up a Windows 7 VM and trying that?
-Dave
Have you tried installing Kies and using the drivers it provides? Or if you already had Kies installed, going to Tools > Reinstall device driver?
Different USB cable?
blindmanpb said:
Have you tried installing Kies and using the drivers it provides? Or if you already had Kies installed, going to Tools > Reinstall device driver?
Different USB cable?
Click to expand...
Click to collapse
Thanks. I tried Kies and three different cables as well. Nothing doing. I think because the Knox counter was tripped Kies connects to the tablet and then says it is unsupported and disconnects. ADB driver works fine independently, but when running Kies it does the same thing - connects, recognizes the tablet as a P600 but then disconnects because it is unsupported.
Because of the Knox thing I am pretty sure Samsung will charge me an unspeakable amount to reflash this thing, so I would love to find my own solution.
-Dave
da_ferreira said:
I think because the Knox counter was tripped Kies connects to the tablet and then says it is unsupported and disconnects.
Click to expand...
Click to collapse
I doubt this is the issue, the Knox counter has been tripped on my P600 since a week after I got it, and I've taken every firmware update via Kies.
Does it give you this message only when the device is in download mode, or do you get it with the tablet powered up normally?
AFAIK Kies won't recognize your tablet unless it's been started normally with Android running, and if it's still got anything other than a stock ROM on it, that message isn't surprising.
I'm also running Windows 8.1 on both my laptop and desktop and have never had any connection issues
If all you want is TWRP back, have you tried Flashify?
https://play.google.com/store/apps/details?id=com.cgollner.flashify
blindmanpb said:
I doubt this is the issue, the Knox counter has been tripped on my P600 since a week after I got it, and I've taken every firmware update via Kies.
Does it give you this message only when the device is in download mode, or do you get it with the tablet powered up normally?
AFAIK Kies won't recognize your tablet unless it's been started normally with Android running, and if it's still got anything other than a stock ROM on it, that message isn't surprising.
I'm also running Windows 8.1 on both my laptop and desktop and have never had any connection issues
If all you want is TWRP back, have you tried Flashify?
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Click to expand...
Click to collapse
I've been pretty much throwing anything at the problem - I did try Flashify, and it tells me that it does not recognize the device. The tablet boots, it runs fine (no weirdness), I have root but no ability to flash anything.
As far as Kies goes, even when running normally (meaning not in download) Kies tells me the device is unsupported.
My goal is to be able to get to something so I can flash stock in case I decide to sell the tablet. I love it, but it already feels like an orphan and not because of my screwing things up. Kinda feels like Samsung abandoned it not long after release in favor of the Tab Pro line. Just my opinion, I could be wrong.
-Dave