Related
I am rooting my friends phone using the proper thread, following all the directions, did this on my previous Fascinate, however I get into download mode, but Odin does not recognize it and does nothing....?
make sure you have the samsung drivers installed...
Everything is installed including the drivers, its saying the device is not being recognized even though the drivers are on my computer..
are u using the stock usb cable? Maybe try a different one. Also might want to try a different computer. Another thing go into device manager and make sure the drivers are indeed installed for your device.
droidstyle said:
are u using the stock usb cable? Maybe try a different one. Also might want to try a different computer. Another thing go into device manager and make sure the drivers are indeed installed for your device.
Click to expand...
Click to collapse
Yes I am using the stock cable, and I have tried it on 3 different computers each one isn't working and a pop up comes up stating the usb device cannot be recognized or something close to that. Under disk drives on device manager it does show SAMSUNG HM500JJ but I dunno...this is weird maybe I just can't get this thing rooted..
CC268 said:
Yes I am using the stock cable, and I have tried it on 3 different computers each one isn't working and a pop up comes up stating the usb device cannot be recognized or something close to that. Under disk drives on device manager it does show SAMSUNG HM500JJ but I dunno...this is weird maybe I just can't get this thing rooted..
Click to expand...
Click to collapse
I would try redownloading and installing the samsung drivers...try the drivers from section 1 of my guide in general section. If that still dont work then try another usb cable. The cables can be touchy with odin, especially if you coil it up all the time. Don;t ask me why, all I know is in the past 6mo this issue has been posted 50times or better. Usually its one of the things I mentioned causing the problem.
droidstyle said:
I would try redownloading and installing the samsung drivers...try the drivers from section 1 of my guide in general section. If that still dont work then try another usb cable. The cables can be touchy with odin, especially if you coil it up all the time. Don;t ask me why, all I know is in the past 6mo this issue has been posted 50times or better. Usually its one of the things I mentioned causing the problem.
Click to expand...
Click to collapse
Yea that is the driver I have been using and I have uninstalled it and installed it probably a good 5 times. I just dont understand why it would be the cable if I plug it in and its giving the message "The USB Device cannot be detected" or something along the lines of that. I will try the cable for my HTC Thunderbolt tomorrow and see if it works. If that doesn't work then it looks like the phone won't be getting rooted because I don't have anymore cables to try and I am running out of patience
It has to be the driver...my htc thunderbolt works perfect and is always recognized and adb works too and recognizes my device
CC268 said:
Yea that is the driver I have been using and I have uninstalled it and installed it probably a good 5 times. I just dont understand why it would be the cable if I plug it in and its giving the message "The USB Device cannot be detected" or something along the lines of that. I will try the cable for my HTC Thunderbolt tomorrow and see if it works. If that doesn't work then it looks like the phone won't be getting rooted because I don't have anymore cables to try and I am running out of patience
It has to be the driver...my htc thunderbolt works perfect and is always recognized and adb works too and recognizes my device
Click to expand...
Click to collapse
try installing the google nexus driver and see if that works.
http://developer.android.com/sdk/win-usb.html
droidstyle said:
try installing the google nexus driver and see if that works.
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
I will try this tonight when I get over to my buddies apartment, thanks
I couldn't get it installed...the directions on actually getting the driver installed are not good...there are a lot of steps that I can't do on my computer such as go to manage in computer and then devices tab...there is no devices tab?!?!
CC268 said:
I couldn't get it installed. It just said windows has already found the appropriate driver. I dont understand how it could be so hard to find a dang driver for this phone...
Click to expand...
Click to collapse
it wont automatically install...you have to click on the device in device manager and go to update driver, then manually push the google driver. After successful install it should say android device in DM.
I couldn't find the device in device manager...I mean the computer isn't going to recognize it anyways if there isn't any drivers installed?
CC268 said:
I couldn't find the device in device manager...I mean the computer isn't going to recognize it anyways if there isn't any drivers installed?
Click to expand...
Click to collapse
If you have usb debugging turned on, usb cable plugged in, installed either the samsung driver or nexus driver and still get a "cant recognize device error" then either the usb port is bad on the phone or the cable is jacked. The problem is not the drivers...Lots of people use the drivers I suggested with no problems. I thinks its the usb cable personally because from what you describe, windows can tell something is plugged into the usb port, but cant tell what it is. Windows has to be able to recognize the device before you can install the drivers for it.
droidstyle said:
If you have usb debugging turned on, usb cable plugged in, installed either the samsung driver or nexus driver and still get a "cant recognize device error" then either the usb port is bad on the phone or the cable is jacked. The problem is not the drivers...Lots of people use the drivers I suggested with no problems. I thinks its the usb cable personally because from what you describe, windows can tell something is plugged into the usb port, but cant tell what it is. Windows has to be able to recognize the device before you can install the drivers for it.
Click to expand...
Click to collapse
Yea...hmm well I know its not the computers and certainly not my laptop as I never have any trouble with it...I have used several different cables though so it could be the phone...
CC268 said:
Yea...hmm well I know its not the computers and certainly not my laptop as I never have any trouble with it...I have used several different cables though so it could be the phone...
Click to expand...
Click to collapse
That could be...try cleaning the usb port on the phone...power of device, pull battery, then put some contact cleaner on a q-tip. If still nothing, then a replacement might be in order.
droidstyle said:
That could be...try cleaning the usb port on the phone...power of device, pull battery, then put some contact cleaner on a q-tip. If still nothing, then a replacement might be in order.
Click to expand...
Click to collapse
I will try these steps...I mean windows is recognizing that something is plugged into the computer so I dont know if its really a phone issue still seems like its more of a driver issue...but I dunno I wish I could find the old adb way of rooting the fascinate...it was way more problem free...anyways I dont know when I will have time to try this on my friends phone again it may not be for another month but I will try again at some point
CC268 said:
I will try these steps...I mean windows is recognizing that something is plugged into the computer so I dont know if its really a phone issue still seems like its more of a driver issue...but I dunno I wish I could find the old adb way of rooting the fascinate...it was way more problem free...anyways I dont know when I will have time to try this on my friends phone again it may not be for another month but I will try again at some point
Click to expand...
Click to collapse
here is adb root method if it helps:
To Root
(credit p3droid/Mines_01 from ec09)
***Requires ADB***
1. Download this: http://www.multiupload.com/HXKQY717LY
md5: 113a9158535ddefa802eb2dc187f236d
2. unpack to wherever adb folder is
(if adb is universal unpack wherever)
3. cd folder with unpackaged files
4. adb push su /data/local
5. adb push Superuser.apk /data/local
6. adb shell
7. mount -o remount,rw -t rfs /dev/block/stl19/system
8. cat /data/local/su > /system/xbin/su
9. chmod 6755 /system/xbin/su
10. cat /data/local/Superuser.apk > /system/app/Superuser.apk
11. chmod 755 /system/app/Superuser.apk
12. reboot
Please take the time to read this:I flashed and installed SkyRaider a couple days ago and I noticed when I connected to my PC that my PC started recognizing it as HTC Phone (or something of the like). This apparently really screwed up my drivers on my computer because I installed iKReaM and now I can't even get into disk drive mode...it doesn't ask what connection type I want anymore and my computer just says "USB Device Not Recognized". I tried uninstalling the HTC Driver Installer but that didn't do anything either. This is not good as I ran into the same problem when trying to root my friends Samsung Fascinate and never go the problem fixed. Anyways...my phone worked perfect before and SkyRaider evidently messed it up pretty good...to say I am pissed is an understatement. If you need any more info please let me know.
Please link me to the newest HTC Drivers as well, it would be much appreciated.
If no one can help I will have to do a clean install of windows 7, which is not an enjoyable experience
https://market.android.com/details?id=com.dooblou.WiFiFileExplorer&hl=en
You will have to buy the pro version to push files. That would be your easy solution.
You can always use recovery to get into usb mode as well.
Stratejaket said:
https://market.android.com/details?id=com.dooblou.WiFiFileExplorer&hl=en
You will have to buy the pro version to push files. That would be your easy solution.
You can always use recovery to get into usb mode as well.
Click to expand...
Click to collapse
I can't get into recovery anymore using usb mode, computer doesn't recognize the device so no way to use it...and I would use the Wifi app instead of using a usb cable? I see what you mean by easy but I don't wanna avoid the problem...I have a brand new $1600 Alienware so I would like to have it fixed lol...if need be I may just have to do a clean install
I know this isn't your actual problem but just for the record, AirDroid lets you control your phone and push files to it with a web browser and wifi for free.
(I tried linking it but I guess I haven't made enough posts to include links yet, easy to find by searching the Market tho)
You might check under Settings/ Connect to PC to make sure the Ask Me option is turned on.
Sent from my ADR6400L using Tapatalk
When you plug your phone into your computer does the phone start to charge?
If so restart the computer and plug the phone into a different usb port. Check device manager and see if you have it listed in your usb devices, or you have an ! over a usb. Most of the time this ends up being an issue with the computer it is being hooked to, not the phone. The computer isn't launching the driver correctly to show the phone that it is connected to a computer, and not just a wall outlet.
Even when I've had this issue, which is random I have still been able to use recovery usb to manage it. Make sure when your in recovery you mount the sdcard before enabling the usb.
Hey guys.
My girlfriends Galaxy S 2 won't even recognize it's plugged into my laptop, yet it will charge.
Now it's no deal at all as she never plugs it into a PC anyway, I just transfer stuff bluetooth.
But I want to put a custom ROM on it to get rid of all the carrier bull****, but being un-able to connect to a PC, how can I root it and install one using just the handset itself?
Please help me?
aussiesausage said:
Hey guys.
My girlfriends Galaxy S 2 won't even recognize it's plugged into my laptop, yet it will charge.
Now it's no deal at all as she never plugs it into a PC anyway, I just transfer stuff bluetooth.
But I want to put a custom ROM on it to get rid of all the carrier bull****, but being un-able to connect to a PC, how can I root it and install one using just the handset itself?
Please help me?
Click to expand...
Click to collapse
Not possible imho without pc, uninstall and reinstall Kies or the usb drivers for connection. Disable usb debugging.
Oh ok, bugger. And I've tried doing that, doesn't seem to work.
The phone doesn't even come up that it's plugged in. Nothing.
search in the development section
there was a method to root ics without flashing anything from pc
I have but can't find anything.
aussiesausage said:
I have but can't find anything.
Click to expand...
Click to collapse
Yoy usb drivers are not working, reinstall them again in Kies and reboot the pc. than connect again.
aussiesausage said:
Hey guys.
My girlfriends Galaxy S 2 won't even recognize it's plugged into my laptop, yet it will charge.
Now it's no deal at all as she never plugs it into a PC anyway, I just transfer stuff bluetooth.
But I want to put a custom ROM on it to get rid of all the carrier bull****, but being un-able to connect to a PC, how can I root it and install one using just the handset itself?
Please help me?
Click to expand...
Click to collapse
Is the S2 already running ICS firmware? If so you can easily root using the method here: http://forum.xda-developers.com/showthread.php?t=1501719
Just put the two linked files on your internal sd (either transfer then via bluetooth or directly download from your phone through the browser) and follow the instructions, literally a 2 minute job.
Yeah seen that, but it's not ICS
gee2012 said:
Yoy usb drivers are not working, reinstall them again in Kies and reboot the pc. than connect again.
Click to expand...
Click to collapse
Nope no go, just did that. KIES just says please connect a device
My galaxy Nexus connects up fine, just not her Galaxy S 2 yet it will charge fine. Dunno why.
EDIT: I take that back, left it plugged in and now it's making weird noises and sayings installing device driver software.
Sorry somebody else had posted my way of doing it
Just to eliminate another option have you tried cleaning the USB port on the phone, I have seen quite a few posts here and there saying that it has helped
dj_sploits said:
If you are on a stock ICS ROM then you could always get the files for CF-Root. You pop them on your SD card and then you root your device from the phone itself. After that you could send the custom roms over to the SD card and install them that way? No PC needed
I'm sure this way works but if not hopefully somebody will correct me
Click to expand...
Click to collapse
Not possible, you have no cwm to flash it with, sammy`s 3rd recovery doesn`t allow flashing custom software. You need to have cwm.
---------- Post added at 09:17 AM ---------- Previous post was at 09:16 AM ----------
You could try another usb port
Now WTF.
I rooted it, used Rom Manager to flash CWM and it's still the stock one.
Why isn't my phone this ***** hard.
aussiesausage said:
Now WTF.
I rooted it, used Rom Manager to flash CWM and it's still the stock one.
Why isn't my phone this ***** hard.
Click to expand...
Click to collapse
Why are u using rom manager, it causes problems with sammy based roms. Turn off the phone, press volume up + menu +power buttom at the same time, you should get in cwm. Don`t use rom manager!
Did you try to connect on another pc? Or at least on another usb port? Windows should at least recognise that a new hardware has been plugged in
Hi guys,
I'm new to this forum. I've got a Samsung i777 on android 2.3.6 kernel 2.6.35.7 build number gingerbread.uckk6
I've recently bought this phone off ebay
My phone does not get detected by windows 7 or Macbook. I've tried changing the USB flex cable with I9100 v2.3 but still no luck.
When I connect USB port it beeps and shows mtp-initialization/mtp-connected on the phone but it is not shown on windows. It says USB cannot recognise the device. I've got a s3 and ideos x3 both of them are detected.
I've installed kies 3 on my laptop.
I had to swtich off the wifi on the phone because it consumes a lot of battery, I think it is because of the android version I'm using!
I want to root the phone and unlock it!!
Any help is appreciated!
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
I'm guessing the problem is the Samsung drivers you have installed for the s3. Try uninstalling those and installing the correct drivers for s2.
Sent from my GT-p511x
you can check this thread for driver
http://forum.xda-developers.com/showthread.php?t=961956
You most likely need a new cable. Happened to me once! Could be the drivers but I HIGHLY recommend just trying a new USB cable.
Thank you guys for all your help really appreciate it!
I have tried all the steps mentioned above tried to uninstall all the previous drivers I had and installed the new driver as mentioned in the above link but no luck
I tried it on a friends computer with a different cable still it shows the USB device is not recognised!!
kshah1606 said:
Thank you guys for all your help really appreciate it!
I have tried all the steps mentioned above tried to uninstall all the previous drivers I had and installed the new driver as mentioned in the above link but no luck
I tried it on a friends computer with a different cable still it shows the USB device is not recognised!!
Click to expand...
Click to collapse
Did you install another ROM? It might help to Wipe system, Data, ETC! it appears to be a software problem. Or at least my guess is the ROM your using.
The Galaxy phones all use the same USB drivers whether it's an S2, S3, S4, etc., so if the installed drivers were working for your S3, it's unlikely to be a driver issue.
Can you boot it into download mode? If you happen to have a USB jig, that's the easiest. Otherwise, power off the phone, unplug the USB cable, hold Vol +/Vol-, then plug in the USB cable. It should go into ODIN download mode. See if Windows detects the phone that way. If so, it very well could be something weird with the OS installed (although it appears to be stock).
If you can get into download mode, you can flash a stock kernel to make sure you are starting fresh. A good file repository is found here. I recommend the stock UCKH7 image I777_UCKH7_OCD_No_BL.7z (you'll also get root).
And yes, the UCKK6 release had a serious bug related to the wifi that could drain your battery. Best to go with UCKH7.
You could also download an app that allows you to enter download mode.
SighIsAnonymous said:
Did you install another ROM? It might help to Wipe system, Data, ETC! it appears to be a software problem. Or at least my guess is the ROM your using.
Click to expand...
Click to collapse
How would I be able to change the ROM if the phone is not detected
jpasher said:
The Galaxy phones all use the same USB drivers whether it's an S2, S3, S4, etc., so if the installed drivers were working for your S3, it's unlikely to be a driver issue.
Can you boot it into download mode? If you happen to have a USB jig, that's the easiest. Otherwise, power off the phone, unplug the USB cable, hold Vol +/Vol-, then plug in the USB cable. It should go into ODIN download mode. See if Windows detects the phone that way. If so, it very well could be something weird with the OS installed (although it appears to be stock).
If you can get into download mode, you can flash a stock kernel to make sure you are starting fresh. A good file repository is found here. I recommend the stock UCKH7 image I777_UCKH7_OCD_No_BL.7z (you'll also get root).
And yes, the UCKK6 release had a serious bug related to the wifi that could drain your battery. Best to go with UCKH7.
Click to expand...
Click to collapse
I was able to boot to download mode by holding the vol +/- key and then plugging in the USB cable but there is no movement from the computer it doesn't make a sound nor does it detect. I tried restarting the phone then I get a notification on windows that USB device not recognised!
Yes I guess this rom is useless, if the wifi is switched on then battery would not even last 6 hrs!
kshah1606 said:
I was able to boot to download mode by holding the vol +/- key and then plugging in the USB cable but there is no movement from the computer it doesn't make a sound nor does it detect. I tried restarting the phone then I get a notification on windows that USB device not recognised!
Click to expand...
Click to collapse
Are you saying to get a balloon notification in the tray that says the USB device is not recognized? A possible reason for that is a faulty USB cable or USB port (funny enough, I actually got that message last night when I was playing around with my Captivate, and switching USB ports made it work). I know you said you've tried other computers an another USB cable, but that's about my only idea. Maybe there's some debris inside the connector that's messing up the connection.
When you say you changed the "USB flex cable", are you talking about the internal connector and board inside the phone? If so, perhaps the I777 connector board is actually a little different than the I9100 board and causing a compatibility issue.
The bug in UCKK6 related to wifi didn't affect everybody, but it definitely affected a lot of people (based upon reports here).
kshah1606 said:
How would I be able to change the ROM if the phone is not detected
Click to expand...
Click to collapse
If you have an SD card, you can download another ROM on that SD card from your computer and then you can install custom recovery (CWM) and then install the ROM from SD card.
kshah1606 said:
How would I be able to change the ROM if the phone is not detected
Click to expand...
Click to collapse
First ill run you through the problem I had. Just for reference did you use Mr. Cooks script before flashing Cyanogenmod 11? One of his scripts for cleaning before flashing, actually deletes a certain file, not to keen on which one. What it results in though is not being able to flash OF ROMS and some certain custom ROMS! So id recommend alliance's ROM! As for the "Getting the ROM on your device, you could put the ROM on your SD though recovery "Mount and storage/Mount mass storage/" or just use a micro sd card adapter and move it on there that way.
Thanks for your reply. Would you mind sending me the link on how to do that step by step as mentioned I'm new to Samsung phones and also this forum.
Your help is appreciated
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
kshah1606 said:
Thanks for your reply. Would you mind sending me the link on how to do that step by step as mentioned I'm new to Samsung phones and also this forum.
Click to expand...
Click to collapse
What state is your phone currently in? Is it still not detected by the computer? You are still on 2.3.6, correct?
If it's still not being detected by your computer, I'm not sure if you can flash anything needed using the stock recovery. I know that when I flashed stock JB, I was able to boot into stock recovery and directly apply the standard CWM update file here. It will give boot into a temporary CWM that should allow you to flash other ZIP files (like a ROM), although I had trouble doing that (so I ended up flashing the AJK_v4.9_NoSwap.zip kernel using the MobileOdin android app, which gave a permanent CWM recovery).
I'm not sure if this same process works with the 2.3.6 recovery. However, in order to get the stock recovery to see the internal SD card, I had to run adb shell commands to mount the partition (meaning I had to have a working connection from the computer).
Solved!!!
HI Guys,
Many many thanks for all your responses!
I have changed the USB flex cable again to an older version v2.2 and my phone is currently being detected by kies! So relieved thanks a lot for all your help..now the rooting begins!!:laugh:
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...