So I installed cm7 and then realised that my galaxy s was no longer getting recognised by odin, meaning i cant flash other roms. So i tried flashing the cwm version of jvr but it just doesnt work. When i reboot the phone im still on cm7. Ive tried factory resetting but after the reboot im still on cm7! What do i do to flash another rom?
Try to look for nexus s usb drivers, that should do, i think...?
As cm7 uses nexus s drivers.
Sent from my GT-I9000 using xda premium
Ive tried downloading the nexus s drivers aswell and the same things happening. It device drivers were not installed because there is no ethernet controller.
Install Android sdk then install google USB driver package thats solves my problem
Related
Well.. it seems to me that there has been an unusually high amount of people who are now getting the USB device not recognized error when plugging their phone into their computer. Myself included. I'm stuck on dj05 because of it.
Can everyone that's having this problem post what they've flashed and how? Or any other problems their having? Make sure to post what OS you are using, x64 or x86, stock cord or not, Samsung drivers version, etc. Maybe we can find a common theme between everyone having the problem, and figure out a way to fix it. Thanks!
Sent from my SCH-I500 using XDA App
I will asap when I get home to my computer. Thanks for the thread as I have asked myself, but still no luck.
Sent from my SCH-I500 using XDA App
Same problem. I was running DL30 with the Blackhole Rom. Just stopped working yesterday. Tried flashing stock, then DL05. Can't root, ADB doesn't see it, nothing. Can't mount either. Win7 64 keeps saying its a CD drive and tries to install the verizon drivers. Did that, still tries.
I thought considering I started the thread, I should probably post my configuration as well. I had no problems with USB until I flashed kaosinate. I'm sure this didn't have anything's to do with it but oh well. I also flashed the lasted kaosinate kernal. After that, I installed superclean with adryn.'s test kernal. Still nothing. If you look around, there are definitely quite a few reports of the phone being recognized as a CD drive. Adrynalyne reccomends flashing one of his new test kernals which has been reported by some to fix the problem. He says that he still has to reboot with the phone plugged in to have it recognized, however.
I an running windows 7 pro x64 with the lastest Samsung drivers. I only get the USB error when plugging the phone in while its In downlaod mode. Otherwise it is recognized as a CD drive. I guess this is what we get for flashing non stock firmware, Roms, etc. If anyone has any suggestions, feel free to post them.
Sent from my SCH-I500 using XDA App
Randomly came back...flashed stock DI01, then DI05, then DI09, then back to DI05. Working now...it must have finally wiped some bad code or something...
OK, so I went to root the thing...when the root rebooted, it didn't work. I had to disconnect and reconnect the USB cable to get it to recognize again.
Did you use Odin? Where did you get the files from?
Sent from my SCH-I500
Running Windows 7 64bit
running super clean 3.2nv
I finally got it to recognize. But it will not recognize when i boot into download so i can flash with odin...
My USB drivers were working correctly on the stock image. Then I flashed to Cyanogenmod 7. My Windows XP machine is looking for drivers for "Fascinate" but it won't find any. I tried reinstalling the drivers, rebooting the machine, tried to find the drivers manually. What's next?
I've read other places and they all say to load nexus drivers
Sent from my SCH-I500 using XDA App
yeah nexus s drivers, install the android sdk and it should come with it.
Sent from my MIUI SCH-i500
Yeah, just this morning I ended up using the drivers in the "extras" folder. Everything is working now!
I am in a bit of a pickle. I rooted my brand new Nexus S, but in the excitement, I accidentally flashed a kernel for Cyanogenmod first instead og the ROM first, THEN the CM7. Now it won't go pass the unlocked bootscreen. I have searched for solutions, but can't find any. If only the Nexus S had a SD card, I would know what to do, but how do I get a stock kernel transferred to the phone when I can only get it into Clockwork mod? I tried factiory reset and all, but it is not the problem, it is the kernel. I can get into CWM but nothing happens when I try to mout USB storage to transfer files and/or new kernel..... Help, anyone? Please?
Benny. Denmark
You can mount your sdcard from recovery, there is an option for mounts in the first menu. Then transfer whatever file you want to flash.
Sent from my Nexus S using xda premium
It doesn't work. Ther phone shows up for a split second in Windows file explorer and then closes again.
Please post the exact model of your phone and the exact file you flashed, and the exact CWM recovery file you flashed.
Also, if you can get to recovery you haven't bricked your phone
If you haven't done it already I'd also flash superuser. If you are after a stable ROM based on CM7, I'm using NSCollab 1.0.39 and works very well.
Sent from my Nexus S using xda premium
mcdanish said:
It doesn't work. Ther phone shows up for a split second in Windows file explorer and then closes again.
Click to expand...
Click to collapse
Which drivers do you have installed, just the ones from the Android SDK? what Windows do you have?
Sent from my Nexus S using xda premium
mcdanish said:
I am in a bit of a pickle. I rooted my brand new Nexus S, but in the excitement, I accidentally flashed a kernel for Cyanogenmod first instead og the ROM first, THEN the CM7. Now it won't go pass the unlocked bootscreen. I have searched for solutions, but can't find any. If only the Nexus S had a SD card, I would know what to do, but how do I get a stock kernel transferred to the phone when I can only get it into Clockwork mod? I tried factiory reset and all, but it is not the problem, it is the kernel. I can get into CWM but nothing happens when I try to mout USB storage to transfer files and/or new kernel..... Help, anyone? Please?
Benny. Denmark
Click to expand...
Click to collapse
when you flashed cyanogenmod after flashing the kernel, cyanogenmod automagically overwrote the kernel that you flashed first, so thats not the issue. try wiping data, then reflash cyanogenmod and the gapps.
simms22, the issue occurred because after flashing the kernel, I could not flash anything because it just halted on the Google screen with the open padlock. I have now uninstalled and reinstalled the Samsung drivers, and it helped, I then could see the phone in Windows Explorer and was able to transfer a new kernel and a new ROM, which actually was the NSCollab which I like because of the speed. Thanks all for helping me out. Have a nice one.
mcdanish said:
simms22, the issue occurred because after flashing the kernel, I could not flash anything because it just halted on the Google screen with the open padlock. I have now uninstalled and reinstalled the Samsung drivers, and it helped, I then could see the phone in Windows Explorer and was able to transfer a new kernel and a new ROM, which actually was the NSCollab which I like because of the speed. Thanks all for helping me out. Have a nice one.
Click to expand...
Click to collapse
ahh, i misread what you wrote. im glad that it got straightened out anyways
Good to hear
NSCollab 1.0.39 is pretty stable with the Matr1x 5.5 kernel it comes with and you'll notice a better battery life too.
Sent from my Nexus S using xda premium
hello. i used LCD density monitor to try to fix the market after switching the DPI settings, and my device is unusable. as sooon as i boot, everything force closes, nothing runs. ADB cannot connect to the device. it says theres no device connected.
i used toolkit to reflash stock rom, but i cant reset to factrory, so it keeps booting into this terrible set up with nothing working. stock recovery is just the android with the open chest and eclamation.
going through the toolkit, i cannot get the ADB drivers to install and correctly see my tablet.
can anyone offer some help?
much appreciated!
Not sure if this will work for you but when ADB couldn't see my N7, it was because it was in MTP mode.
Settings > Storage > Menu (top right) > USB computer connection > select Camera (PTP)
If that works, you can push all the stock images and recovery via fastboot.
managed to finally get adb to work, flashed stock, and starting over wiuth a restore, but theres no MTP drivers installed. anyone have any idea how to install them or where to get them?
joshtb86 said:
managed to finally get adb to work, flashed stock, and starting over wiuth a restore, but theres no MTP drivers installed. anyone have any idea how to install them or where to get them?
Click to expand...
Click to collapse
Can you roll us a little how you managed to revive your device?
Sent from my Galaxy Nexus using xda premium
kind3rgarten said:
Can you roll us a little how you managed to revive your device?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
to get ADB to work, i went through the manual driver install several times before i got it to work. i had the USB plugged into a usb 3.0 port, and for some reason, ADB does not recognize through 3.0 ports. plugged into a 2.0 port and had no problem getting ADB to finally recognize it.
I flashed stock, but rebooted to the same problem. i managed to get into the menu and factory reset. after factory resetting, it was fine.
no more LCD density until they fix that.
Make sure you have android SDK installed.
Sent from my Nexus 7 using Tapatalk 2
joshtb86 said:
to get ADB to work, i went through the manual driver install several times before i got it to work. i had the USB plugged into a usb 3.0 port, and for some reason, ADB does not recognize through 3.0 ports. plugged into a 2.0 port and had no problem getting ADB to finally recognize it.
I flashed stock, but rebooted to the same problem. i managed to get into the menu and factory reset. after factory resetting, it was fine.
no more LCD density until they fix that.
Click to expand...
Click to collapse
The easiest way to change your DPI is to either download ROM Toolbox or edit it yourself. ROM Toolbox is good for whole slew of things, not just DPI modding. I would recommend it for anyone with a rooted Android Device.
And thanks for telling us that information, nice to know that ADB doesn't support USB 3.0. :/
Sent from my Nexus 7 using xda premium
I've looked everywhere on the forums and tried every known combination on trying to install my Nexus S 4G drivers. I've uninstalled all the drivers on my computer, shutdown my computer for 5 mins and powered it back on, downloaded the SDK Tool Manager, tried installing Google Drivers, tried using the Galaxy Nexus Toolkit for the drivers...EVERYTHING. All I'm trying to do is get my computer to read my Nexus so I can re-root my phone. If someone knows something that will get my pc to read new drivers PLEASE HALP!!!
I get the same problem when i use my original usb cable. I solved my problem by using my nokia usb cable which also have micro usb plug.
HTC Sensation z710e
ICS 4.0.3
Sense version 4.0
Software Sense-o-maniac v1.4
Kernel. 3.0.30 Bricked v1.4
Radio 11.68.3504
Hey bud
Go here http://www.youtube.com/watch?feature=player_embedded&v=EA6DlAqYUeo#at=189
There's a video "how to... .," and in the description is a link to a zip that has the correct drivers.
Let me know how it goes
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
i had exact same problem, i solved it by enabling usb debugging under developer settings. and i am on the factory usb line. and if youre on jellybean, make sure you enable the dev options on the top right corner as well. hope this helps.
I've seen that video several times and I have installed the drivers but even after installing them my pc still reads my Nexus as and Unknown Device. USB debugging is on and I'm currently running ICS 4.0.3. I haven't tried a different cable which is going to be my next step. I just have to find the one of the many I have. I will post an update here very shortly
doktabl4ck said:
I've seen that video several times and I have installed the drivers but even after installing them my pc still reads my Nexus as and Unknown Device. USB debugging is on and I'm currently running ICS 4.0.3. I haven't tried a different cable which is going to be my next step. I just have to find the one of the many I have. I will post an update here very shortly
Click to expand...
Click to collapse
You have exactly same problem as me. Another non factory usb cable will surely fix your problem.
HTC Sensation z710e
ICS 4.0.3
Sense version 4.0
Software Sense-o-maniac v1.4
Kernel. 3.0.30 Bricked v1.4
Radio 11.68.3504
...no prob
Did you try this?
https://www.youtube.com/watch?v=GSD92Qjt5Og&feature=youtube_gdata_player
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Try a new cable and reinstall the sdk
Sent from my Galaxy Nexus using xda premium
snowman77 said:
Try a new cable and reinstall the sdk
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Sorry for the delayed reply, being sick isn't fun.....I tried another cable and it didn't work either. I was at work last night with another cable and on my work computer and the computer still shows up as Unknown device. Could it be my root that's making my phone read like that?
doktabl4ck said:
I've looked everywhere on the forums and tried every known combination on trying to install my Nexus S 4G drivers. I've uninstalled all the drivers on my computer, shutdown my computer for 5 mins and powered it back on, downloaded the SDK Tool Manager, tried installing Google Drivers, tried using the Galaxy Nexus Toolkit for the drivers...EVERYTHING. All I'm trying to do is get my computer to read my Nexus so I can re-root my phone. If someone knows something that will get my pc to read new drivers PLEASE HALP!!!
Click to expand...
Click to collapse
I followed this and it worked the first time for my Nexus S and Windows 7, not sure if it works for a 4G:
Install-nexus-s-windows-usb-drivers/