Related
Hi Community-
I'm having USB connection issues & was hoping for a little guidance.
Although I've read through multiple USB problem threads, I thought I'd start my own rather than hijack another member's thread.
In an effort to best help, I'll try to be thorough.
When I connect my Vibrant to PC, I get the "USB Device Not Recognized" and "Error Code 43" notifications & "Unknown Device" designation in Device Manager. Also, when I set updates to automatic, I get an "Drivers failed to install" notification (paraphrased).
I am running EDT's Project V with one of the Bullet 1.2/1.42 kernels. While I DO NOT believe the ROM or Kernel are causing issue, I will likely change both soon to confirm.
To solve the issue, I have attempted the following in USB Debugging and Mass Storage modes:
1. Plugged into 3 different PCs (2 running XP, 1 running W7).
a. Multiple usb ports in each.
2. Used 4 different micro USB cables (two are original Samsung cables).
3. Allowed windows to autdetect & install drivers (fails).
4. Installed 32 bit drivers & 64 bit drivers from multiple sources using the included setup files (uninstalled between).
5. Manually directed Windows to 32 bit and 64 bit drivers using Device Manager.
6. Attempted to connect to Kies Mini in Kies mode (uninstalled program after failure).
*As a side note, I successfully connected a Captivate & Fascinate (neither mine) to one of the PCs using one of the same Samsung cables I have tried.
*And another: I have not tried to connect the Vibrant recently, but have successfully connected the phone to multiple PCs in the past.
To this point, I have not tried:
1. Manually installing I9000 drivers.
2. Installing a new Froyo kernel and/or ROM.
3. Reverting to a previous Froyo nandroid that connected in the past.
4. Flashing an Eclair kernel then reverting to a stock Eclair nandroid.
Those will likely be the next steps, but if any users have had success using additional methods, any advice would be greatly appreciated.
Thanks!
Try this from Unlockr.com (was for HTC drivers but you can clear remaining Samsung drivers if any)
1. Download USBDeview
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
2. While the phone is still plugged in, open USBDeview and sort by manufacturer. Find all the Samsung drivers and delete them all.
3. Once all have been deleted, unplug the phone from the USB cable and plug it back in.
4. The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
suchavibrantthang said:
4. The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
Click to expand...
Click to collapse
Downloaded USBDeview from the provided link. Program confirmed that I have already deleted all Samsung drivers.
When I left program running and plugged Vibrant back in, I got:
1. Same error notification (device has malfunctioned).
2. Windows did not try to download drivers (despite permission in Windows Update).
3. USBDeview did not recognize that a USB device had been plugged in (checked "Display devices without drivers" under Options & refreshed).
Thanks for the reply & a new method to attempt though! Something's gotta work eventually.
"device has malfunctioned"
"Drivers failed to install" notification"
edit: just letting you know my experiences with those failure notices. for me it had nothing to do with drivers and such. it was faulty hardware.
Ive had this problem with one of my MS Bluetrak mouses. The USB dongle fried and burned and messed up one of my usb2.0 ports on my laptop, leaving me with only one. Might be your usb port in your phone that's malfunctioned. My two vibrants have loose connections now because of the way it pulled left or right while charging. so it's either your usb port on pc or the phone has a bent chip or massive dust...idk
sorry i cant help. another alternative is to replace your usb part on your phone.
suchavibrantthang said:
"device has malfunctioned"
"Drivers failed to install" notification"
phone has a bent chip or massive dust...idk
another alternative is to replace your usb part on your phone.
Click to expand...
Click to collapse
Yeah, looking that way, huh?
Anyway, thanks again.
I had a similar situation. I had 4 micro usb cables, two samsung stock ones (captivate/vibrant), 1 blackberry, 1 which I forgot where I got it from. Long story short, the blackberry one which coincidentally was the thickest cable of the bunch was the only one that consistently detected my phone. Hope that helps...
mrlazyone said:
the thickest cable of the bunch was the only one that consistently detected my phone. Hope that helps...
Click to expand...
Click to collapse
Haha, tried my thickest cable for 15 min again just to see.
Unfortunately, I'm getting close to giving up.
So:
1. No smartphone for a while ... Boo!
2. Or no Odin ever ... Double boo!!
Sent from my SGH-T959 using XDA App
mrlazyone said:
I had a similar situation. I had 4 micro usb cables, two samsung stock ones (captivate/vibrant), 1 blackberry, 1 which I forgot where I got it from. Long story short, the blackberry one which coincidentally was the thickest cable of the bunch was the only one that consistently detected my phone. Hope that helps...
Click to expand...
Click to collapse
THANK YOU!!!! I tried using my wife's cable and it did the trick! It sucks because I saw your comment a few days ago but it didn't register but this morning I am sleepless so decided to give it a shot again and voila!!! Thank you boss.
I have been working through this for a while as well. As far as I can tell, the problem is isolated to only my machine, even though there are a couple of different USB controllers within. Both cables I have and the CM7.1-nightly (various attempted) Vibrant I am using will connect to my laptop and my other desktop, but not to my Asus P8Z68-V Pro (either directly or through a hub, through the USB3 controller and USB3 + hub). I have also tried a separate stock Vibrant, same results. All I get on my uber-rig is charging
one thing that HAS worked (in a limited fashion) is using the hub built in to my Razer Tarantula keyboard, however its USB 1.1 and cant supply the proper voltage. So code 43 becomes code 10 (This Device Cannot Start [USB Hub Power Exceeded]), still no functionality.
fortunately my mobo has a built in bluetooth module and I can just push things around with that. slowly... Will be keeping an eye out for bios and chipset updates to see if they resolve, and in the future may try an add-in USB2 card
Hello Everybody i just got my viewpad 7 2.2 froyo i want to root it ... when i open superoneclick and click root it stucks and doesn't respond
According to this thread "If there is no activity for more than 30 seconds and the terminal display is stuck at 'Running rageagainstthecage....' remove the USB plug momentarily and plug back in." Hope that helps. Good Luck!
hanmin said:
As mentioned above, the AGPS uses server information (via cellular network) to locate the GPS satellite for a quicker fix and hash conditions. For a 4KM tunnel, I'm sure that your phone would have lost both GPS and network signal.
Click to expand...
Click to collapse
hi
try ginger break it worked for me i have gvn apk im my olivepad thread take it try it
Sent from my CSL-MI410 using xda premium
i got the same problem...
It stucks at waiting for device... I've tried pluging it off and back in...
you guy`s try a different usb port i had a simuliar problem with sut restoring the stock rom and i switch port and it worked youy can always try
haree said:
hi
try ginger break it worked for me i have gvn apk im my olivepad thread take it try it
Click to expand...
Click to collapse
Could never get Super One Click 1.7 to work, it just hangs on "Waiting for device" each and every time, no matter what usb port I use or known good cable out of my desk.
Gingerbreak appears to work, I have SuperUser installed, but I cant connect to the device with ADB Shell. lakehousetech's guide basically comes to a halt at the stock backup phase. I cannot get ADB Shell to find any devices period.
elister said:
Could never get Super One Click 1.7 to work, it just hangs on "Waiting for device" each and every time, no matter what usb port I use or known good cable out of my desk.
Gingerbreak appears to work, I have SuperUser installed, but I cant connect to the device with ADB Shell. lakehousetech's guide basically comes to a halt at the stock backup phase. I cannot get ADB Shell to find any devices period.
Click to expand...
Click to collapse
first run setup when connect device then leave the syng prog runninggo to dos shell
enter viewpads cdrom letter here it is g:\ you have to check youre`s
the type adb shell
dont forget superuser on youre viewpad ask for permission grant it hope this wil work
Its also worth noting that I cannot actually boot into a recovery mode. On my HTC phone, I press down volume and power at the same time and it will boot into a BIOS/Recovery screen. Ive read that I need to do something similar with my Viewpad, which is to press volume down, volume up and power on in order to boot into this menu, but nothing ever happens. I get the birds splash screen for a few seconds, then the screen goes black.
elister said:
Its also worth noting that I cannot actually boot into a recovery mode. On my HTC phone, I press down volume and power at the same time and it will boot into a BIOS/Recovery screen. Ive read that I need to do something similar with my Viewpad, which is to press volume down, volume up and power on in order to boot into this menu, but nothing ever happens. I get the birds splash screen for a few seconds, then the screen goes black.
Click to expand...
Click to collapse
yes and keep pressing them all the time until it say`s left upper screen enter recovery screen if that does not work are youre buttons ok do they work?
Alleycatzero said:
yes and keep pressing them all the time until it say`s left upper screen enter recovery screen if that does not work are youre buttons ok do they work?
Click to expand...
Click to collapse
Yes the buttons do work (this is brand new, not even 24 hours has passed), in a normal operation mode, volume goes up and down. On my HTC phone, it was very easy to boot into this recovery mode, so this process of getting clockworkrecovery mod installed isnt totally new to me. Seems like its going to be hit or miss on this tablet.
elister said:
Yes the buttons do work (this is brand new, not even 24 hours has passed), in a normal operation mode, volume goes up and down. On my HTC phone, it was very easy to boot into this recovery mode, so this process of getting clockworkrecovery mod installed isnt totally new to me. Seems like its going to be hit or miss on this tablet.
Click to expand...
Click to collapse
it supposed to be easy with youre pad to don`t know what els then sorry
so, the only way to root is via gingerbreak? SuperOneClick doesn't work right?
armando101 said:
so, the only way to root is via gingerbreak? SuperOneClick doesn't work right?
Click to expand...
Click to collapse
Ive made several dozen attempts to get Super One Click to work (wasted a few hours) and its just a big bowl of fail. Gingerbreak 1.2 is flawless, takes minutes and installs Superuser.
elister said:
Ive made several dozen attempts to get Super One Click to work (wasted a few hours) and its just a big bowl of fail. Gingerbreak 1.2 is flawless, takes minutes and installs Superuser.
Click to expand...
Click to collapse
never had any problems with super one click. make sure the right drivers are installed, open sync (syncusb.exe) and disable your firewall
kwbr said:
never had any problems with super one click. make sure the right drivers are installed, open sync (syncusb.exe) and disable your firewall
Click to expand...
Click to collapse
Are you sure? Lakehousetech's guide to using Super One Click 1.7 does not mention syncusb.exe. Because of this, Im wondering if the rest fo the guide is correct, because even with my device rooted with Gingerbreak, the rest of the guide does not work.
http://forum.xda-developers.com/showthread.php?t=1015005
Hello guys, I'm new here. I'm also facing the same problem in rooting my VP7. Tried different versions of SOC, stuck up on "waiting for device" and SOC stops responding. Tried also GingerBreak, installed and click Root Device and waited for ages and nothing happens. Almost followed all the guides posted here in XDA.
What am I missing? I'm about to give up. Thanks in advance.
same problems....
I am actually in Germany, have a european Viewpad7 and spent hours and days to try to root it. To no avail.
I first read the postings in forums and websites, downloaded the newest (and then the successively older) versions of SuperOneClick 2.2.3. and tried - nothing, its stuck every time before connecting to the device.
Tried different USB-ports, enabled always USB-debugging, tried it with SD-card in or out - nothing. Same result with older versions of SuperOneClick (even using the alternate ADB-parser in "Advanced") - always stuck at the same place before connecting to the device. But - Windows sees the tablet and the card, because the usual window opens (for deciding what to do with the data on the card). Copying pics or music to the card is no problem.
Then - I left the SOC-Road for Gingerbreak. Installed, SD-card removed, runnig forever (25 minutes was the longest I let it run) - nothing. No reboot, no stopping of that little wheel proving that the program is not stuck and runs.
Now, before downloading another potential program for rooting, I became member here at XDA, looking for help.
I run Froyo 2.2.2, last viewsonic update is installed on the Viewpad (bought end of december last year).
I would be glad if someone of the "gurus" here could help me, because I spent three days now and I still don't see the light at the end of the tunnel....
Gerd
boriflash1 said:
... in Germany, have a european Viewpad7 and spent hours and days to try to root it. To no avail ... run Froyo 2.2.2, last viewsonic update is installed on the Viewpad (bought end of december last year) ... and I still don't see the light at the end of the tunnel....
Gerd
Click to expand...
Click to collapse
Okay, let's try a fresh approach to rooting the Vpad7 (does your specs. looked similar to mine under my signature below ?) What computer OS are you running - Vista, Win7 or XP Pro/SP3 like one of my older system?
Might I suggest, if you have access to/borrow one - start with a clean PC (I keep an older Dell laptop, XP Pro/SP3 with OEM drivers and basics installed and running, plus Antivirus & Firewall running (easily turned off/shut down as needed) - and easy enough to reformat or restore (if necessary) -
Setup a subfolder on the drive(s) with all the Vpad7 apps, drivers, devices, patches, etc. so that it's easily accessible; and, do the same for ADB & shell/busybox, etc. so that you can run command lines directly from the c:\ prompt (arrrh ...... the good old DOS days)
You might want to have an extra mini-usb cable (OEM or generic) available that is tested to work with similar devices - to play with "trying" out different USB 2.0 ports as needed.
It's possible that one of the self-configured/auto-installed usb drivers from the Vpad7 might be conflicting or competing as you run SuperOneClick (I sticked with v1.7x as newer ones tend to be more problematic per various posts I've read over the past 6+ months.) Turn off pc's anti-virus & firewall, etc. and do a reboot to clear the pc of any background running programs - and pay attention to any prompts, messages, beeps and alerts that pop-up as you proceed (as they often provide important clues to the likely sources of problem)
Follow the posted directions, step-by-step and do it carefully - upon initial connection, does it see a usb connection, recognize the device, attempt to use/run usb driver installation, etc. If it seemed to stalled while connecting or looking for device/drivers - try quickly removing & reconnecting the Vpad7 to the mini-usb cable, sometimes - this trick it into the "mode" to work (one of our HTC DI2 easily gained root but the 2nd. & newer one would "install" for over 3 hours, then a "clean/stock" fresh pc with the connection trick did it - rooted)
If this is still "no good" or you continue to run into problems - please post with any specific error messages or pop-up during the failed attempt, and let's see what can be done then.
Letitride said:
Okay, let's try a fresh approach to rooting the Vpad7 (does your specs. looked similar to mine under my signature below ?) What computer OS are you running - Vista, Win7 or XP Pro/SP3 like one of my older system?
Click to expand...
Click to collapse
Dear Letitride, first of all thank you very much for trying to help. Let me answer your questions one by one.
My computer runs on Vista home, its a laptop and has all the official windows updates. Four USB-ports, all of them working (checked with my external hard drive). When plugging-in the Viewpad, the window with the options how to open the data on the SD-card immediately opens.
I do not know how to access the data on the Viewpad like you did, but I definitely have Froyo 2.2.2. and the last official update, official rom.
Letitride said:
Might I suggest, if you have access to/borrow one - start with a clean PC (I keep an older Dell laptop, XP Pro/SP3 with OEM drivers and basics installed and running, plus Antivirus & Firewall running (easily turned off/shut down as needed) - and easy enough to reformat or restore (if necessary) -
Click to expand...
Click to collapse
Sorry, I don't know anyone at the moment (as I am travelling) with another computer I could use. So I guess I have to stick with mine. But when I do a restart, all applications running before should be terminated anyway. I could also move all the data without any problem to and from the Viewpad's SD-card.
Letitride said:
Setup a subfolder on the drive(s) with all the Vpad7 apps, drivers, devices, patches, etc. so that it's easily accessible; and, do the same for ADB & shell/busybox, etc. so that you can run command lines directly from the c:\ prompt (arrrh ...... the good old DOS days)
Click to expand...
Click to collapse
Now you lost me. Which drive? Laptop drive? Where do I get the VPad7 apps, drivers, etc? I have to have them before copying them in any subfolder (subfolder of which folder by the way?). Same question for ADB, shell, busybox. Sorry for my stupidity, I am into Windows, but not into Android....And even in Windows I must confess that I almost did not run anything from command lines. Never needed to....
Letitride said:
You might want to have an extra mini-usb cable (OEM or generic) available that is tested to work with similar devices - to play with "trying" out different USB 2.0 ports as needed.
Click to expand...
Click to collapse
I even have three cables and 4 ports and I interchanged already all of them.
Letitride said:
It's possible that one of the self-configured/auto-installed usb drivers from the Vpad7 might be conflicting or competing as you run SuperOneClick (I sticked with v1.7x as newer ones tend to be more problematic per various posts I've read over the past 6+ months.)
Click to expand...
Click to collapse
Already did. I tried them from 1.6 on upwards... No success.
Letitride said:
Turn off pc's anti-virus & firewall, etc. and do a reboot to clear the pc of any background running programs - and pay attention to any prompts, messages, beeps and alerts that pop-up as you proceed (as they often provide important clues to the likely sources of problem)
Click to expand...
Click to collapse
I turned of windows firewall, Avira and the Viewpads antivirus. No success
Letitride said:
Follow the posted directions, step-by-step and do it carefully - upon initial connection, does it see a usb connection
Click to expand...
Click to collapse
YES
Letitride said:
recognize the device,
Click to expand...
Click to collapse
Hmmm.,... it recognizes the SD-card, but not the device. That is also the problem when using SOC....it is stuck at ...looking for device....
Letitride said:
attempt to use/run usb driver installation, etc. If it seemed to stalled while connecting or looking for device/drivers - try quickly removing & reconnecting the Vpad7 to the mini-usb cable,
Click to expand...
Click to collapse
DID, but it did not move of change anything when SOC is stuck.
Letitride said:
sometimes - this trick it into the "mode" to work (one of our HTC DI2 easily gained root but the 2nd. & newer one would "install" for over 3 hours, then a "clean/stock" fresh pc with the connection trick did it - rooted) - If this is still "no good" or you continue to run into problems - please post with any specific error messages or pop-up during the failed attempt, and let's see what can be done then.
Click to expand...
Click to collapse
I do not get any error messages - neither from the Viewpad, nor from Windows. SOC simply stops working, the window gets white and then when I try to close it, it simply states that SOC has a problem in closing. On the second click, it closes.
I hope I was a specific as possible, excuse once again my ignorance concerning android. It definitely seems that my laptop sees the storage device, but not the Viewpad itself. Changing cable or changing USB-ports did not fix that.
Thanks again. I really appreciate your help.
Gerd
boriflash1 said:
I do not get any error messages - neither from the Viewpad, nor from Windows. SOC simply stops ... gets white and ... simply states that SOC has a problem in closing. On the second click, it closes ... ignorance concerning android ... my laptop sees the storage device, but not the Viewpad itself. Changing cable or changing USB-ports did not fix that.
Gerd
Click to expand...
Click to collapse
Edited your details to try to keep it short - it read like there some of the device drivers might be missing or need to be installed.
My laptop was reformatted last month running Vista Business & from my notes, when the Vpad was 1st. connected, it recognized the new hardware (Qualcomm USB device) and proceed to install 3 drivers, enabled a virtual CD-ROM drive with additional setup files, and when it was done including a reboot, the laptop has 6 new hardware/device drivers - and both the new virtual CD-ROM and USB removable device available & working, with USB debugging enabled and once the USB drive was turned on (default is off)
Have you tried to go to Control Panel, click & uninstall all the related USB drivers, including a PC Tools apps auto-configured by the Vpad7 ?
Then, shutdown & reboot the laptop - reconnect the Vpad and let it re-install everything from the beginning. (also, do you have a spare mSD card, an older 8GB or even 4GB mSD would be useful ?)
As for the sub/folder - I was referring to creating to making a subfolder on your laptop's drive, and saving/moving all of the vpad7 related donwloads, SOC and custom Roms, etc. to this folder (and subfolders as necessary to keep it organized.) I put the adB and busybox files, etc. here too as downloaded - in order to run adB using the command prompt per instructions - this Android & linux based "stuff" is new to many of us, but to have fun is to allocate some time to learn them. There are links here on XDA on the basics & it's worthwhile reading.
Also, did the Vpad7 install PC Tools, which is used to sync. files between the laptop & the V?
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...
Hi,
I wanted get a more vanilla Android to run on the Kindle Fire so I read everything I think I would need to know to proceed (I know it's a bit more difficult than on other devices, but that is not the problem here).
I have already rooted and flashed multiple other androids, so I'm not a total beginner.
My Amzon Kindle Fire HDX 7 is running Fire OS 4.5.5.2 without any modifications like a new device:
Not rooted
Stock Recovery
Locked Bootloader
Stock Rom
But before I could even start to try and flash TWRP, the tablet wasn't recognized by my Windows 10 Desktop-PC. So I tried to install the official Amazon Fire Driver.
It was already pretty weird, because Windows didn't do that "device connected"-sound or showed a popup that it is installing drivers.
I checked the Device Manager and it showed nothing. There was no "unknown device" or "Kindle Fire".
I tried other cables, other phones, other PCs
The only Popup I get is on the Tablet that says that its connected to a slow charger.
ADB is enabled. I have tried to do a factory reset, but that didn't help.
I have read other threads, but they either already have flashed something or they are suggested to install drivers via the device manager (which is not listing the tablet, in my case)
I have thought about rooting with kingroot and then flashing TWRP with a terminal app, but I'm afraid that that may brick the device and I woudn't have the backup possibility to reflash with a PC.
I hope someone knows what to do. Maybe amazon has some special drivers that I haven't found?
I would be very happy for any response
Thanks
Hischem said:
Hi,
I wanted get a more vanilla Android to run on the Kindle Fire so I read everything I think I would need to know to proceed (I know it's a bit more difficult than on other devices, but that is not the problem here).
I have already rooted and flashed multiple other androids, so I'm not a total beginner.
My Amzon Kindle Fire HDX 7 is running Fire OS 4.5.5.2 without any modifications like a new device:
Not rooted
Stock Recovery
Locked Bootloader
Stock Rom
But before I could even start to try and flash TWRP, the tablet wasn't recognized by my Windows 10 Desktop-PC. So I tried to install the official Amazon Fire Driver.
It was already pretty weird, because Windows didn't do that "device connected"-sound or showed a popup that it is installing drivers.
I checked the Device Manager and it showed nothing. There was no "unknown device" or "Kindle Fire".
I tried other cables, other phones, other PCs
The only Popup I get is on the Tablet that says that its connected to a slow charger.
ADB is enabled. I have tried to do a factory reset, but that didn't help.
I have read other threads, but they either already have flashed something or they are suggested to install drivers via the device manager (which is not listing the tablet, in my case)
I have thought about rooting with kingroot and then flashing TWRP with a terminal app, but I'm afraid that that may brick the device and I woudn't have the backup possibility to reflash with a PC.
I hope someone knows what to do. Maybe amazon has some special drivers that I haven't found?
I would be very happy for any response
Thanks
Click to expand...
Click to collapse
First, you can't just install TWRP on this device. Some prep work is involved including rooting and installing a vulnerable bootloader.
It is possible the USB connection (one or both middle pins) are damaged on the HDX given you have tried different hosts, USB cables and ports with no response. If the pins look OK the connector may have partially dislodged from the mainboard. Not much can be done about that unless you are handy with a soldering iron.
Davey126 said:
First, you can't just install TWRP on this device. Some prep work is involved including rooting and installing a vulnerable bootloader.
It is possible the USB connection (one or both middle pins) are damaged on the HDX given you have tried different hosts, USB cables and ports with no response. If the pins look OK the connector may have partially dislodged from the mainboard. Not much can be done about that unless you are handy with a soldering iron.
Click to expand...
Click to collapse
Thanks for your response,
Rooting would be pretty easy, as it is rootable with Kingroot. I wanted to follow this guide https://forum.xda-developers.com/kindle-fire-hdx/general/thor-4-5-5-2-easy-to-root-unlock-t3571240
I wonder if it would be possible to do this without a pc. I know it is possible to flash a custom recovery with the rooted device alone, but I'm not sure if I could unlock the bootloader like that.
If I had to solder I would either give it to a repair shop or just leave it.
Hischem said:
Thanks for your response,
Rooting would be pretty easy, as it is rootable with Kingroot. I wanted to follow this guide https://forum.xda-developers.com/kindle-fire-hdx/general/thor-4-5-5-2-easy-to-root-unlock-t3571240
I wonder if it would be possible to do this without a pc. I know it is possible to flash a custom recovery with the rooted device alone, but I'm not sure if I could unlock the bootloader like that.
If I had to solder I would either give it to a repair shop or just leave it.
Click to expand...
Click to collapse
You can root and therotically flash a vulnerable bootloader w/o the benefit of a tether. Unlocking must be done via fastboot which requires a hardwire host.
Servicing a HDX 7 would be cost prohibitive. Can snag a used one in perfect condition (aside from battery age) on many auction sites for 60-75 USD.
I just replaced the USB port/ribbon cable on my HDX7. Took about 20 minutes and $15. No soldering required. Just be sure to peel the back off by hand (don't use pry tools or you'll crack your screen). After completion I was able to unlock bootloader and install TWRP and Lineage OS.
robnhl said:
I just replaced the USB port/ribbon cable on my HDX7. Took about 20 minutes and $15. No soldering required. Just be sure to peel the back off by hand (don't use pry tools or you'll crack your screen). After completion I was able to unlock bootloader and install TWRP and Lineage OS.
Click to expand...
Click to collapse
Wow, so you just pulled the HDX open and popped in the replacement port? No soldering? Does it just hook in? I'm hesitant to do this, it's a nice piece of hardware and I'd hate to bust it if there was another option (like paying a professional to do it...).
Any way to root and get a working google play store without a tether/USB/ADB?
You have to peel the black strip off to access the screws to take the body apart. If I could do it then I'm sure you'll be able to make it work.
Ok, I need to load an OS back to the device ( wiped data/system because girlfriend enabled encryption.....) anyway I've tried the same computer I rooted the thing 2 years ago, installed new drivers and also am in test mode, however
the hdx (when booted into TWRP) never shows up in device manager, and "adb devices" is always empty. I've tried several USB cables, and even a mac computer, anyone lose access to their device and got it back? Any hints?
cq_ said:
Ok, I need to load an OS back to the device ( wiped data/system because girlfriend enabled encryption.....) anyway I've tried the same computer I rooted the thing 2 years ago, installed new drivers and also am in test mode, however
the hdx (when booted into TWRP) never shows up in device manager, and "adb devices" is always empty. I've tried several USB cables, and even a mac computer, anyone lose access to their device and got it back? Any hints?
Click to expand...
Click to collapse
First verify drivers are working. For whatever reason legacy composite drivers from Motorola seem to work best with this device regardless of platform or host OS. Install the Motorola Device Manager from this page and then switch drivers. No need to launch the utility.
TWRP must be at v2.7 or above for ADB support. If below 2.8.6.0 you should consider updating via fastboot assuming bootloader has been unlocked. See: https://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-3-0-0-0-t3322547
If still no joy you will have to erase/replace aboot and rebuild the device from scratch. Data loss is likely.
hmm yeah, the main problem seems to be the tablet never shows up in device manager as any device... thanks for the hints though, will try the motorola device manager drivers...
cq_ said:
Ok, I need to load an OS back to the device ( wiped data/system because girlfriend enabled encryption.....) anyway I've tried the same computer I rooted the thing 2 years ago, installed new drivers and also am in test mode, however
the hdx (when booted into TWRP) never shows up in device manager, and "adb devices" is always empty. I've tried several USB cables, and even a mac computer, anyone lose access to their device and got it back? Any hints?
Click to expand...
Click to collapse
Where'd you get the drivers from? Can you share a link to the ones you installed on your PC? In control panel devices have you tried enabling show hidden devices to see if the tablet is detected but not enabled? What version of Windows?
I haven't tried this yet personally yet but I'm wondering if a live Linux (e.g. Mint) booted on USB thumb drive might be an option. I don't know enough about using a Mac to access the Kindle to offer much in detail there. Have you tried different USB ports on each of these computers? Do other USB devices show up okay?
fufu508 said:
Where'd you get the drivers from? Can you share a link to the ones you installed on your PC? In control panel devices have you tried enabling show hidden devices to see if the tablet is detected but not enabled? What version of Windows?
I haven't tried this yet personally yet but I'm wondering if a live Linux (e.g. Mint) booted on USB thumb drive might be an option. I don't know enough about using a Mac to access the Kindle to offer much in detail there. Have you tried different USB ports on each of these computers? Do other USB devices show up okay?
Click to expand...
Click to collapse
Read here literally two posts above yours. Where was Linux/Mac ever mentioned? Connectivity on Windows almost always boils down to procedures, drivers and/or USB cable integrity. Assuming the device itself is not toast.
fufu508 said:
In control panel devices have you tried enabling show hidden devices to see if the tablet is detected but not enabled?
Click to expand...
Click to collapse
Oh snap, this is a good idea - will try when I get home.
TWRP 3.1.1-1, Win 10 64bit - yeah tested several usb ports on my computer - I originally rooted the HDX with this computer and windows 10 install about 2 years ago [side note do you guys remember reformatting every 6 months because windows was such a pos, I'm really glad those days are long gone!]
LOL yep Windows 10 nowadays does seem a lot more stable than the earlier stuff.
---------- Post added at 06:14 PM ---------- Previous post was at 05:50 PM ----------
Davey126 said:
Read here literally two posts above yours. Where was Linux/Mac ever mentioned? Connectivity on Windows almost always boils down to procedures, drivers and/or USB cable integrity. Assuming the device itself is not toast.
Click to expand...
Click to collapse
Hi Davey oops somehow I missed that you had already replied a few days ago . cq_ did mention a Mac computer. I suggested testing with a live Linux thumb drive boot in case they have an extra thumb drive kicking around to find out what that OS sees as compared to the Windows and Mac already tried. When reviving my Thor, part of the process I tried was draxie's 1-click, which required Linux and access to the device to do its work, so it seemed like a good to me to try to boot the PC that cq_ is using into Linux. In my case I have Linux Mint installed on a separate SATA hard drive but not everybody has that type of rig, hence the live Linux USB thumb drive boot suggestion.
fufu508 said:
Hi Davey oops somehow I missed that you had already replied a few days ago . cq_ did mention a Mac computer. I suggested testing with a live Linux thumb drive boot in case they have an extra thumb drive kicking around to find out what that OS sees as compared to the Windows and Mac already tried. When reviving my Thor, part of the process I tried was draxie's 1-click, which required Linux and access to the device to do its work, so it seemed like a good to me to try to boot the PC that cq_ is using into Linux. In my case I have Linux Mint installed on a separate SATA hard drive but not everybody has that type of rig, hence the live Linux USB thumb drive boot suggestion.
Click to expand...
Click to collapse
Fair enough; I may have been a bit harsh in my response. I now see the passing reference to an Apple rig and appreciate the unfiltered perspective often obtained via Linux. That said, there is new info on the table that suggests the OP has access to a Win10x64 box which should connect effortlessly/reliably with Moto drivers and a quality USB cable. Mucking with drivers can be a PiTA on Windows; the Moto variants remove much of the pain - although you still have to select the proper driver after tethering in the target mode (adb or fastboot) as Windows will typically default to Microsoft/stock variants which rarely work with HDX devices.