connecting my rooted NC to my laptop crashes it? - Nook Color General

the second I connect my rooked NC to my laptop, it shows a blue kernel panic error and instantly restarts...
is this a bad ADB driver or something?
its only done this since I rooted my NC using auto-nooter 3.0

Related

PC cannot detect Captivate after using SuperOneClick v1.4

I used SuperOneClick v1.4 to root and to "Enable Non Market Apps" on my Captivate (running Froyo). I first clicked on "root" and everything went without a problem. I rebooted my phone. After this, I tried to "Enable Non Market Apps", but it did not do anything. It gets stuck at "Waiting for Device". I noticed that my computer does not detect my Captivate as well. I tried re-installing the USB drivers for samsung and nothing. Now I cannot use the three button combo to go into "Download mode". It was working perfectly prior to using the SuperOneClick v1.4.
I also noticed that before I used the SuperOneClick v1.4, when I connect my USB cable into my phone, there will be a notification on my Captivate saying that an USB cable is connected. It gives me an option to mount my SD cards onto my computer. But after I used SuperOneClick v1.4, I do not see the Notifications on my captivate whever I plugged in my USB cable.
Does anyone have any suggestions on how I can get my computer to recognize my Captivate and enable "Download Mode"?
Only problems I had getting it to recognize my phone was when I put on launcher pro. I have to use home switcher to get to touch wiz and it worked fine. Didn't find anything in your post about it but that's the only problem I had.
Sent from my SAMSUNG-SGH-I897 using XDA App

[Q] Windows No Longer Recognizes Captivate

Hello all, I am turning to the Forums since I have spent 5 hours trying to resolve my problem.
Earlier today I installed Kies Mini on my computer in anticipation of the official AT&T Froyo. However, now my computer no longer recognizes my phone at all. It does not show up in the Device Manager, or anywhere.
I tried Uninstalling Kies Mini, Uninstalling the Drivers, Rebooting my phone. etc, etc. But Windows still will not recognize the phone as attached. It worked in the past and I would like for it to work again.
I am currently running Windows 7 64 bit. My Captivate is running Cog 3.4.
Try this:
Uninstall Kies Mini and all Drivers
Reinstall Kies Mini
Once installed turn on USB debugging on your phone and then plug it in, let it install all of the drivers.
Unplug your phone and shut it down
Once shut down activate download mode (hold up and down volume and plug in the USB) again it will install more drivers.
Once this is done unplug your phone, remove the battery and turn it back on, then restart your computer.
Uninstalled Kies Mini, and Samsung Drivers. Reboot
Installed Kies Mini.
Attached Phone to Computer. Nothing.
Also, Tried to Just boot my phone into Recovery Mode. But only boots into Clockwork Recovery. Can't Log into Stock Recovery
Update: Tried hooking up the phone to my XP machine. No Joy. XP did not recognize the device or try to install drivers.
Did you enable debugging?
Sent from my SAMSUNG-SGH-I897 using XDA App
Yes, I placed it in Debug mode. When I plug in my Phone my Title Bar Shows the USB Debugging Android indicating that USB Debugging connected, the USB icon that says Copy files to From Computer. If I click on USB, it gives me the Green Connect Android, then the Orange One. But none of my computers recognize a USB device as connected.
I have tried it with Three different cables. I'm thinking that somehow the phone is not sending some message to Windows saying "Hey, I'm connected"
Did you use the correct drivers for the phone? Can't recall of the top of my head if I can use the standard captivate drivers for windows if your on cognition..
Sent from my SAMSUNG-SGH-I897 using XDA App
I am having this exact same issue - only I updated from JH7 to Official 2.2 (for ****s n giggles) and now pc no longer recognizes phone. Went through the uninstall and reinstall and reboot.... no luck. I've never had this issue before...... ever.
I have tried almost everything i can think of. Anyone have any suggestions?
Sent from my SAMSUNG-SGH-I897 using XDA App
Not in device manager
I have what appears to be a soft brick. I was running the i9000 drivers. I was trying to install the i897. At first Odin recognized my phone and I began to download. The Odin bootloader flash failed. No my computer (Win 7 64 bit) does not even see my phone. Nothing in device manager, not even an unrecognized device.
I can get my phone into download mode. Does anyone have an idea how I can get windows to see me again?
From my experience as long as you are in download mode and have odin opened up it when you connect it, odin should find the phone no problem for you to be able to flash something new to it.
davncari said:
I have what appears to be a soft brick. I was running the i9000 drivers. I was trying to install the i897. At first Odin recognized my phone and I began to download. The Odin bootloader flash failed. No my computer (Win 7 64 bit) does not even see my phone. Nothing in device manager, not even an unrecognized device.
I can get my phone into download mode. Does anyone have an idea how I can get windows to see me again?
Click to expand...
Click to collapse
Have you rebooted the PC? Try to reinstall the drivers again. I had to reinstall the nexus s drivers but I have read some need to reinstall kies to get the drivers to work. Just keep at it. Try other USB ports. My phone wouldn't be recognized for about two weeks with trying everything. I tried new USB cables, drivers and all. Then finally it kind of worked and I went from download mode with a jig to phone!PC and then it took another reboot of the laptop and phone was able to get flashed again via the phone!PC screen. Just keep trying is all I can say.
Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted

[Q] Milestone on CM7 - issue with using as modem

This weekend I was away from home and needed to book some plane tickets. So I connected my milestone (running CM7 Nightly) to a laptop(Windows 7 32 bit) via USB.
But when I plugged in the USB cable into the laptop, when the drivers were being installed there was an error (there was a red x next to 1 of the options, can't remember the exact option but I think it had something to do with Motorola networking?).
Anyway, I downloaded the latest Motorola drivers (same 1 I used when rooting) via my phone and installed it on the laptop, but I was still unable to connect using the dial up connection I created. Everytime I tried to connect I received error 632 (I think it means modem not detected)
I had to flash the phone back to stock Froyo and then it installed properly and I was able to use the phone as a modem on the laptop.
Has anyone else experienced this and is there a solution?
There's a thread for USB tethering using CM7: http://forum.xda-developers.com/showthread.php?t=1257115
I haven't tried it yet though

[Q] Galaxy S soft brick(?) + USB failure(?) problem

Hi,
I was using F1 V6 ROM on JVK for some time (flashed it with no problems using Odin and Clockwork). After some time, it started to crash more often. I triend V7 but it was even worse so I got back to V6. The only problem was often restarts and sometimes slow operation.
Yesterday I decided to switch to Cyanogen to give it a try. I did it without flashing from scratch. I just used Cyanogen 7.1 installation through Clockwork. It seemed OK untill I tried to connect my phone to PC via USB. I couldn't get any response from PC (not even a sound indicating that something was connected to USB) or Phone (no mount USB screen).
So I was able to charge my phone through USB but not to connect it to PC (tried 2 PCs, different cables, different ports). It doesn't seem like driver problem (no sign of connecting phone to PC, nothing).
I thought that it might be some problem with Cyanogen ROM. So I tried to go back to F1 V6 (wipe) through Clockwork. After doing it, I got boot loop but still showing the logo of Cyanogen (not SGSII from F1). Having no USB connection and being unable to start the phone, I tried to do recovery (I had a backup of F1 V6 from the moment before installing Cyanogen. That didn't go well either. The process stopped and left me with Samsung Galaxy S logo (no boot loop - just hanging there). I cant get into recovery mode anymore. I can only get to download mode.
So the status right now is:
Download mode - OK
USB - can't get phone to connect with PC (no signs of connection so probably not a driver problem but maybe? I tried reinstalling kies, drivers, running Odin, no sign of connected phone, USBDeview shows no Samsung or Kies or Android drivers in my system right now).
Hanging on the Samsung Galaxy S screen.
Did anyone had similar situation?
What do you advice? Any idea on a atest checking if USB hardware is fine?
Was it possible to break USB hardware or driver in phone by installing Cyanogen 7.1 on F1 V6 SGS2?
Any help would be appreciated.
Thanks
kaminkac said:
Hi,
I was using F1 V6 ROM on JVK for some time (flashed it with no problems using Odin and Clockwork). After some time, it started to crash more often. I triend V7 but it was even worse so I got back to V6. The only problem was often restarts and sometimes slow operation.
Yesterday I decided to switch to Cyanogen to give it a try. I did it without flashing from scratch. I just used Cyanogen 7.1 installation through Clockwork. It seemed OK untill I tried to connect my phone to PC via USB. I couldn't get any response from PC (not even a sound indicating that something was connected to USB) or Phone (no mount USB screen).
So I was able to charge my phone through USB but not to connect it to PC (tried 2 PCs, different cables, different ports). It doesn't seem like driver problem (no sign of connecting phone to PC, nothing).
I thought that it might be some problem with Cyanogen ROM. So I tried to go back to F1 V6 (wipe) through Clockwork. After doing it, I got boot loop but still showing the logo of Cyanogen (not SGSII from F1). Having no USB connection and being unable to start the phone, I tried to do recovery (I had a backup of F1 V6 from the moment before installing Cyanogen. That didn't go well either. The process stopped and left me with Samsung Galaxy S logo (no boot loop - just hanging there). I cant get into recovery mode anymore. I can only get to download mode.
So the status right now is:
Download mode - OK
USB - can't get phone to connect with PC (no signs of connection so probably not a driver problem but maybe? I tried reinstalling kies, drivers, running Odin, no sign of connected phone, USBDeview shows no Samsung or Kies or Android drivers in my system right now).
Hanging on the Samsung Galaxy S screen.
Did anyone had similar situation?
What do you advice? Any idea on a atest checking if USB hardware is fine?
Was it possible to break USB hardware or driver in phone by installing Cyanogen 7.1 on F1 V6 SGS2?
Any help would be appreciated.
Thanks
Click to expand...
Click to collapse
Cyanogen uses a different file system, so to get it back to a Sammy ROM you need to flash it with Odin. and cyanogen doesn't use the Sammy driver for connecting to the PC. download nexus s drivers from the Android SDK and install it.
Sent from my GT-I9000 using xda premium
OK, so how do I install these drivers when my PC can't see that I have my phone connected to USB port? There is no driver error. After connection nothing happens.
Is there a way to install these drivers on Windows 7 without actually having sgs listed on device list?
any help with that?
kaminkac said:
OK, so how do I install these drivers when my PC can't see that I have my phone connected to USB port? There is no driver error. After connection nothing happens.
Is there a way to install these drivers on Windows 7 without actually having sgs listed on device list?
any help with that?
Click to expand...
Click to collapse
Get your phone into download mode (volume down + home + power) and see if windows lists it then.
Sent from my GT-I9000 using xda premium
Thanks but it does not.
No sign of connecting phone to PC.
any ideas?
kaminkac said:
Thanks but it does not.
No sign of connecting phone to PC.
any ideas?
Click to expand...
Click to collapse
Reflash the CM7 Rom, and see if it shows up in device manager. Do you get an option on CM to share disc drives with usb plugged to the computer?
Oh, and if you have KIES installed, try remove it and remove the driver pack too (i know it affects ODIN's ability to see the phone).
Solved
Thanks for help.
I got different cable (third) and different (third) PC and somehow it worked - PC noticed connection of SGS in download mode and than it was easy.
I installed clean JVT, than CF-Root and CM 7.1 + google apps.
It seems to work fine for now.
Please close this thread.
Cheers

[Q] Samsung S2 not recognized - USB Device Not Recognized Error

I believe the source of the problem to be a faulty install of ICS plus a later rooting, as the phone would intermittently go from Android Phone to Unable to Recognize USB Device, to just not being able to recognize the phone. I've uninstalled KIES along with the drivers and installed them back again to no avail. Can anyone help? Is it possible to flash the phone with a working Android version without using the computer - through the SD card?
I'm having a similar problem seems to be very intermittent and random.
Try plugging it into a friends laptop, mine got recognised that way.
Then either download a rom and chuck it on the card that way or we shall see.
I got it fully working, absolutely perfectly an hour or so ago. Came back to it now and tried to plug it in and no response...

Categories

Resources