Computer wont recognize my device anymore. I have downloaded every set of drivers from this forum, from the samsung website, I even tried downloading kies but it wouldnt recognize it either.
It worked before I did the following and now it doesnt.
First I rooted my phone with route 66 everything was going fine until I made the huge mistake (not knowing) and downloaded rom manager so that I could do a nandroid backup. Well as we all know now, you cant do that. So I got the deadly uellow verizon triangle saying unauthorized software bring it to the store. So I went through the xda forums and found the one that told me how to fix it. I used odin with the alternate restore and got it back up and running. So I wanted to go back and use adams one click unlock and root. I got everything downloaded and ready. I put my phone in developer mode and plugged it in. It starts trying to find the drivers and then it flips from debugger mode to media mode everytime. It starts seeing it as everything but a samsung phone. It says found camera and even cd rom but not the phone. I have read through everything and tried everything I could think of but I am at a loss. PLEASE HELP
Sent from my SCH-I605 using xda app-developers app
brandi1693 said:
Computer wont recognize my device anymore. I have downloaded every set of drivers from this forum, from the samsung website, I even tried downloading kies but it wouldnt recognize it either.
It worked before I did the following and now it doesnt.
First I rooted my phone with route 66 everything was going fine until I made the huge mistake (not knowing) and downloaded rom manager so that I could do a nandroid backup. Well as we all know now, you cant do that. So I got the deadly uellow verizon triangle saying unauthorized software bring it to the store. So I went through the xda forums and found the one that told me how to fix it. I used odin with the alternate restore and got it back up and running. So I wanted to go back and use adams one click unlock and root. I got everything downloaded and ready. I put my phone in developer mode and plugged it in. It starts trying to find the drivers and then it flips from debugger mode to media mode everytime. It starts seeing it as everything but a samsung phone. It says found camera and even cd rom but not the phone. I have read through everything and tried everything I could think of but I am at a loss. PLEASE HELP
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Turn off your phone, connect to your computer with the USB cord and turn back on your phone. It should start the drivers and connect to your device.
smalk said:
Turn off your phone, connect to your computer with the USB cord and turn back on your phone. It should start the drivers and connect to your device.
Click to expand...
Click to collapse
I tried that, it is still not seeing it like it is supposed to. I was able to get Odin to recognize it so that I could flash the rooted stock again but I can't get Casual Jailbreak to work. I'm not sure if it is because the drivers or not but I am guessing it has something to do with it. Every time I plug it in, it starts searching for drivers and then always switches from usb debugging mode to media mode. The checkmark is still in usb debugging but I don't think it actually is. You can watch it go from device as installer to media.
Are you using the driver install app (zadig i think its called) to install the heimdall driver on top of "gadget serial". Looking at your other post it seems like a driver issue. One thing ive noticed is, if odin can see the device then heimdalll cant and vice/versa. So if odin can see it you have the wrong driver, if you are infact installing the heimdall driver my second question is, does windows xp x64 use driver sig enforcement like win7 x64 does? if so you probably need to disable it. Just throwing my $0.02 out there.
Are you using the official USB cable? I had an aftermarket cable that had worked for months, then decided to quit working. It works with other devices just not the Note2. Changed to my original cable and all is well.
nunyazz said:
Are you using the official USB cable?
Click to expand...
Click to collapse
Also try plugging it in to the PC and not through a hub/keyboard/monitor port
Sent from my SCH-I605 using xda app-developers app
If it sees the device in the dumb verizon cd mode thing and ptp than it can see adb. Its not the cable. however i would try setting the usb debugging first than set it to camera mode. adb should still be able to pick it up
Thank you everyone for your help, I finally got the drivers working and the bootloader unlocked
brandi1693 said:
Thank you everyone for your help, I finally got the drivers working and the bootloader unlocked
Click to expand...
Click to collapse
How? Fixing to unlock my spanking new note also. I had the drivers issues late last night. When installing drivers through the Z app I never could get it to install Samsung usb drivers nor did I see serial gadget option. Running Windows Vista 64bit. I know I have Java.
Sent from my SCH-I605 using xda premium
Hello to all since this is my first post on these forums! And to just say thank you to everyone who will respond to me if I don't say it.
I rooted and installed CWM 6.0.1.8 on my phone about a year ago. I did not unlock the boot loader, because I didn't want to have any custom ROMs on my phone. Now just recently I was looking at android 4.4 and thought that this is a good update for any phone. So, I started to do my research for what to do to flash a ROM. I downloaded CWM 6.0.4.5 on my micro SD card and used "[ROOT]Recovery Tools - Flasher". Now this is where everything goes south...
I went through the app, found the CWM file to flash, and then I got the security error... After researching why this happened it was because of not unlocking the boot loader which was a huge mistake that I forgot to do.
I have searched on here a lot. I found a lot of great and useful information, but I can't try any of the suggestions yet. Not until my computer can recognize my phone. I know before this all happened, I had debugging enabled on my phone. I do not have fastboot installed on my computer anymore (reformatted a long time ago). I do have B2CApp.exe installed so I could try to do a factory reset on my phone. I have installed the driver for the phone from the LG program and from their website.
But like I said before, when I plug in my phone to my computer, the computer does nothing. It doesn't recognize that there is even a device there, but there is power getting to it. How I know is because I took out the battery and "S/W Upgrading" could be enabled.
If I can get past this, I'm 100% positive I can fix it then. If anyone has some sort of useful information about my computer not recognizing my phone, please share it! Also, for context, my computer is a windows 7 x64.
Thank you for your time and your responses!
Paul
Well I haven't heard from anyone yet and I've been still digging around. I might know why my computer doesn't discover my phone. I think it has to do with the charging port. It makes sense since that is where the connection lies. And I already know that my cords are all good as well as my computers. But anyways, I have bought a replacement part and hopefully that fixes the issue.
I'll post my results as soon as I replace the part. Wish me luck!!
Paul
My nexus 4 has no OS in it, while connecting to PC it was showing "USB device not recognized" I've actually tried to google but couldn't find anything. I'm hoping someone come up with a solution.
akhil1289 said:
My nexus 4 has no OS in it, while connecting to PC it was showing "USB device not recognized" I've actually tried to google but couldn't find anything. I'm hoping someone come up with a solution.
Click to expand...
Click to collapse
i have a similar problem with my nexus 10.
while trying to unlock/root it i think i may have bricked it.
i was able to unlock it then tried to root it and got stuck in a loop where the google dots keep going around.
tried to reboot several times. tried everything i could find.
was able to get into twrp v2.6.3.1 andd found that it has no os.
now when i try to unlock it goes thru the motions but returns to fastboot screen, showing that it is still locked.
im guessing that is because it doesnt have or cant see any os.
tried to mount the system partition but that failed as well.
anyone have any advice. at this point i dont have much to lose
tia,
thouston
akhil1289 said:
My nexus 4 has no OS in it, while connecting to PC it was showing "USB device not recognized" I've actually tried to google but couldn't find anything. I'm hoping someone come up with a solution.
Click to expand...
Click to collapse
You should be able to use adb whilst booted into recovery.
akhil1289 said:
My nexus 4 has no OS in it, while connecting to PC it was showing "USB device not recognized" I've actually tried to google but couldn't find anything. I'm hoping someone come up with a solution.
Click to expand...
Click to collapse
Try this http://adbdriver.com/
i had to get the usb jig replaced and it started working for few days now i have the same problem again but i'm using stock android now and with a custom recovery rooted i would be happy if u would explain the cause of this kinda problem and the solution considering my current situation!
I factory reset my kindle fire and I went through the setup and it started updating and when it was finished it went black. After I realized it was bricked I tried the unbrick tool but I couldn't get my kindle to stay connected to my computer for long enough to use it. Can anyone help me out?
Seanballer94 said:
I factory reset my kindle fire and I went through the setup and it started updating and when it was finished it went black. After I realized it was bricked I tried the unbrick tool but I couldn't get my kindle to stay connected to my computer for long enough to use it. Can anyone help me out?
Click to expand...
Click to collapse
This is how you unbrick ;
http://forum.xda-developers.com/fire-hd/development/unbrick-fire-hd-6-7-flashing-lollipop-t3405797
Don't rush it, take your time !
/reader.sh not working .. its just hang there .............
aamszia said:
/reader.sh not working .. its just hang there .............
Click to expand...
Click to collapse
I am running into the same issue. I had rooted the Fire 6 (4th gen) and it has SuperSU Installer on it still after I thought I had restored back to factory and this is preventing me from doing any updates. I also no longer have the recovery option (VolUp+Power), it just blinks and reboots so I don't even have TWRP. I tried following the restore process above using a Boot USB but the READER.SH does nothing. I read it was maybe the USB hardware in the computer so I've tried 5 different computers all with the same result, both with a regular USB cord and fastboot cord. READER.SH just does nothing and I have to CTRL+C out. I'd say try other computers to see if that works. Anyone have any idea why mine isn't working?
ccbst10 said:
I am running into the same issue. I had rooted the Fire 6 (4th gen) and it has SuperSU Installer on it still after I thought I had restored back to factory and this is preventing me from doing any updates. I also no longer have the recovery option (VolUp+Power), it just blinks and reboots so I don't even have TWRP. I tried following the restore process above using a Boot USB but the READER.SH does nothing. I read it was maybe the USB hardware in the computer so I've tried 5 different computers all with the same result, both with a regular USB cord and fastboot cord. READER.SH just does nothing and I have to CTRL+C out. I'd say try other computers to see if that works. Anyone have any idea why mine isn't working?
Click to expand...
Click to collapse
I know this is old, but so you have the all the drivers installed and showing up in your computer's device manager?
The unbrick process and iso posted do not work with the newer FireOS versions starting with FireOS 5.3.1. Ask me how I know besides that it is posted a the top of this thread: https://forum.xda-developers.com/fire-hd/development/unbrick-fire-hd-6-7-flashing-lollipop-t3405797
I have two bricked devices in my closet. Do not think there has been any movement on finding a way around it.
So... now that I think with hindsight, I did something pretty stupid, and I'm going to need some help, since I have no idea what to do.
I have a Nexus 9 tablet, and I never liked it. The OS is just so slow and laggy, and it overheats, and it has many other problems. Quite a couple of times, I installed custom ROM's and so on, and I never had a problem. Let me explain what I did now.
Around a month ago, while looking on the internet, I heard this thing that if I install the original software, but with no encryption, it would work better. It sounded cool at the time, so I downloaded the Nexus Root Toolkit, and did it.
Everything went well. But then I heard about a custom ROM that was apparently working even better, Dirty Unicorns, so using the same toolkit, I installed it. For the first time, my Nexus 9 actually worked the way it is supposed to work, but the custom ROM still had its problems, it crashed from time to time. I was thinking about possibly returning or selling the tablet, so that's why using the Toolkit, I reinstalled the original software. But, if I went all the steps, and also locked the OEM, my device then showed a flag saying that it was a development device, while booting up. So, after messing around with the settings of the Toolkit a little, I decided to reinstall the software, but leave the bootloader unlocked.
But after some time, I reinstalled my Windows, and I also reinstalled the Toolkit. But that's when I started to have problems. My tablet wouldn't connect to my laptop anymore. I used the toolkit and uninstalled drivers, reinstalling others quite a couple of times, and that's where I think that I messed something up. I managed to eventually connect my tablet, and I rooted it, after rooting it, I connected it again. But adb wasn't working for some reason. A little annoyed, I simply copy pasted the zip file of CM13 into my tablet's internal storage, and I rebooted it to the recovery, TWRP. But the recovery failed to flash it, saying something about an Error 7.
Now that I think about it, I was stupid, since after that, I performed a complete factory reset, resetting my TWRP backup too. I tried to connect it again, nothing. It didn't connect at all. I plug it in, my computer doesn't even recognize that something is plugged in. No Nexus 9, no Android Device, no anything. I booted it in fastboot mode, and it worked, my computer recognized it, and after I downloaded a ROM zip file again, I tried to connect the tablet back and flash it manually, but nothing. It didn't recognize anything anymore.
I tried to reinstall the drivers countless times. I deleted what I had, reinstalled it, nothing. I uninstalled and reinstalled the Toolkit. But strangely, now, even if I know that I installed the Google USB drivers, and the ADB drivers, as I even installed Android SDK, if I use USB Deview, it doesn't show me any of them. I can't see any Google or ADB drivers, although I tried installing them multiple times. So now, I'm stuck with a tablet with TWRP and no OS, which I can't connect to my PC, and I can't use ADB or fastboot.
Is it something from my laptop? I can't check to see if it will connect to another PC right now, so I don't know for sure. Is there any way to delete all the traces from my (failed) attempts at reinstalling the drivers, and to install them again properly? Or is it something from the tablet itself? I don't have an OS, so I can't enable USB debugging.
So, shortly, I have no idea what's happening. And I'm quite obviously a noob in all of these. Can anyone help me? Please?
If you boot into the bootloader and from a command prompt type fastboot devices you don't get anything?
Sent from my Nexus 9 using XDA-Developers mobile app
I still couldn't get ADB to work, but I managed to work out fastboot. It may be something from my USB cable, it works perfectly.
I flashed the original software back, and I'll go to check my cable, although I feel kinda stupid that I didn't think about that in the first place.
Thanks for the help anyway.
If fastboot is working and bootloader is unlocked, you can still install a factory image.
Depending of your device download for wifi Version:
https://dl.google.com/dl/android/aosp/volantis-mob30p-factory-2cb57a1b.tgz
If you habe the LTE variant:
https://dl.google.com/dl/android/aosp/volantisg-mob30p-factory-ae9ce05a.tgz
Extract the files and put them into the same directory link fastboot and execute the flash-all.bat
WARNING: Any data will be erased!!! Also TWRP
Now it should boot up with stock firmware.
If you want your device decrypted install twrp. format the internal storage and flash the pure nexus rom which i can highly recommend and is decrypted by default. Dont forget do flash gapps
my issue is same
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
rohanzakie said:
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
Click to expand...
Click to collapse
Use fastboot, not adb.
what if fastboot isn't working, either?
uberSkeptic said:
what if fastboot isn't working, either?
Click to expand...
Click to collapse
Is the tablet in fastboot mode?
madbat99 said:
Is the tablet in fastboot mode?
Click to expand...
Click to collapse
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
uberSkeptic said:
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Hi, uberSkeptic...
Just a quick thought... Have you tried a different USB cable?
Rgrds,
Ged.
Edit & Additional...
The command is not fastboot list devices... it's fastboot devices
One last point... Ensure your Nexus 9 is definitely booted into fastboot mode and not just HBOOT (the bootloader). Take a look at the two screenshots below - your Nexus 9 should look like the screenshot on the right, the one with my green explanatory text.
Apologies for the poor image quality; there's no way of taking a screenshot in the bootloader, so I had to take photographs instead.
Hope this helps and good luck.
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
uberSkeptic said:
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
Click to expand...
Click to collapse
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
GedBlake said:
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
Click to expand...
Click to collapse
Sadly, me too. I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Too bad, too - the tablet is otherwise in great condition and even has a custom-painted backplate (long story).
Thanks for trying to help, though!
uberSkeptic said:
...The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Mmm...
uberSkeptic said:
...I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Click to expand...
Click to collapse
Mmm... (scratches head, raises eyebrow quizzically)...
If I was Hercule Poirot and this was a murder case, and with all the suspects gathered in one room, prior to revealing a brilliant deduction... I'd be casting very dark glances in the direction of your Nexus 9's USB port right now as the likely culprit here.
Think about it. Different computers. Different USB cables. An OTG cable... And none of them work. What's the one thing they all have in common?
Answer: The USB port on the Nexus 9 itself, and where you've replaced the USB daughter-board.
Maybe, possibly, that replacement don't go so well. Maybe there's some unknown problem with it. I can't comment too much on this, 'cos it outside the scope of my knowledge - I'm a software guy; circuit boards and dismantling devices to fix 'em isn't something I'm comfortable with. I always think I'm going to damage something or rip a wire out somewhere, so I bow to your superior knowledge in this area, as I may be talking complete cobblers here. It certainly wouldn't be the first time.
Anyway... Sorry I wasn't able to help find a working solution for you. If anything occurs to me that might help, I'll be sure to let you know.
Rgrds,
Ged.
I would be suspect if the replacement as well if it weren't for the fact that I did it only AFTER the other symptoms/problems appeared. Hence the replacement (which is known good because the battery charges no problem). There cables and everything inside the tablet tests just fine... It feels like the firmware for USB is somehow corrupt or something.
Thanks for all the advice, though. ?
So I can't believe I didn't think of this before, but when I run "dmesg" from the terminal app included w/ TWRP, I see that there a TON of errors, mostly referencing problems accessing the recovery image. I could screenshot it, if anyone at all might be able to tell me a little more specifically what the dmesg log is trying to tell me...