I recently acquired a damaged Kindle Fire. (I'll refer to it below as the 'new' one, even though it is, like my others, used.) The obvious damage is to the screen: it has a fan of cracks on it. However, touch fully works, so that is not my problem.
The problem is that, although the USB port works for charging, I have not been able to establish any USB connection with my Mac. I have other KF's which work with the same connection methods that I have tried without success on this new one. This includes using both regular and factory cables. Nothing works to get the computer to see this and when I start with the factory cable this Kindle just boots normally rather than stopping at the bootloader screen.
This new one has the stock ROM, version 6.3.1, and I have not dealt with any stock ROM since last winter, so I might as well be a noob in that regard. There appears to be no way of turning on ADB debugging, but I doubt that would help anyway, since the Mac's System Profiler doesn't see the KF at all, regardless of what I do.
I do notice that the USB port seems a bit loose and that the cable plug end can move from side to side a bit more than it does on other KF's, but holding it steady in various positions doesn't help.
So, I'm wondering if there's anything I can do with the software that might solve the problem or at least let me get fuller use of the KF, including rooting it and loading apps, without opening the device and repairing the USB port.
Suggestions appreciated.
Related
Hi all. Long time lurker, first time poster here.
I have had my Galaxy Nexus for around a year now and have never had any problems - I've flashed countless ROMs and kernels, etc. However, just recently my phone has stopped being recognized by my computer(s). I've searched and searched and read every thread remotely related to the problem and still the problem persists.
At first I thought it was the new Macbook I was using, or OSX, but I've tried everything I can think of in Windows, OSX, and Linux.
When plugged in, I get nothing in OSX - finder won't find it, android file transfer won't find it, adb won't find it. In Windows, I get an unknown device in device manager, and a popup on the toolbar saying the device has malfunctioned. I've tried all three driver installs with Wug's toolkit, switching from MTP to PTP, turning Debugging on and off, flashing new roms and kernels, installing drivers manually, installing drivers through the Android SDK, even different computers - but every time I get "The USB Device has malfunctioned," or nothing at all in OSX's case. I've even tried a laptop running Ubuntu - still a no go. All the while the phone shows it is charging fine, but no indication of being connected to a PC like it used to do.
I've even tried bending the USB port a little as I've read in some guides and cleaning out the port - no luck. I have yet to try a different cable - one is on the way - but my next step is to replace the USB port board myself, unless anyone has ANY ideas.
It charges fine and never has any problems, it's just I cannot get it to be recognized by anything I plug it into.
I don't have an option to enable/disable fast charge in this ROM (currently on CM10) but I have disabled it in one of the ROMs I flashed to and still no luck.
Is there anything I've yet to try, besides using a different cable? Maybe fast charge was enabled in another kernel and it's screwed up some stuff? Although that seems impossible because I've factory reset/wiped everything and flashed different ROMs and kernels and still nothing. I just don't know at this point.
Any input at all would be great, but I understand if there's nothing else I can do besides trying a new cable and then replacing the board. I finally get going in Android development and this brick wall stops me in my tracks.
Thanks guys.
Try to clean the port (by blowing all the dust out of the usb-port)
For now, just use 'Wifi-explorer'. I use it ALOT just to save my USB-port
The two options you came up with yourself sounds most plausible. I've been through a ton of MiniUSB cables that have gone bad out of nowhere (just lying in my briefcase). So test that one first before buying a new USB port.
Well what do you know, it was the USB cable. I cannot fathom how a USB cable just stops working on the data side of things but still charges after just sitting around. I found another cable in a drawer, plugged it in, and voila, everything's working. Glad I don't have to replace anything, though. Woo!
Good thing is though I now know my way around the drivers and the SDK and am pretty sure I could write a guide on everything you could do to fix a USB issue. The more you know!
tuk1maar said:
Try to clean the port (by blowing all the dust out of the usb-port)
For now, just use 'Wifi-explorer'. I use it ALOT just to save my USB-port
Click to expand...
Click to collapse
I had been using AirDroid before and loved it. And even though it was a cable problem, I know know my USB port is squeaky clean, ha.
I am having multiple issues. The big one is that sometimes when I plug in the phone to my Macbook Pro, it decides to hang the OS. But it's really weird. It's like only the mouse and keyboard hang. Music will keep playing normally, the clock in the menubar runs with no problems, and if I press the power button the "What do you want to do?" window still pops up, I just can't tell it anything. It forces me to hold down the power button for a hard restart. Here's the weird part: I can't narrow it down to what is causing it. I can't tell if it is the phone in Disk Mode or what. And it doesn't always do it. Heck, sometimes the phone won't even act like it's plugged into a computer so it won't even try to connect.
When I first got the phone it didn't do this, but a few weeks after installing DoubleTwist (the only thing I have installed for this phone) it started happening. Uninstalled DoubleTwist and it still does it.
Any help is super appreciated. I searched around and there are similar problems on other phones, but nothing as odd as this.
Thanks!
HTC One X 2.20 unrooted
Macbook Pro running Lion 10.7.5
this happens to me on my macbook air when I plug in any kind of usb device. it starts working fine after a few seconds though. It doesnt bug me enough that i feel the need to find a solution right now but test if it happens with other usb devices.
shahravi94 said:
this happens to me on my macbook air when I plug in any kind of usb device. it starts working fine after a few seconds though. It doesnt bug me enough that i feel the need to find a solution right now but test if it happens with other usb devices.
Click to expand...
Click to collapse
I have had no other problems with any other devices. And for me, this doesn't go away if I wait for 30 seconds or so. I did find out a few minutes ago that if I unplug my phone, within 30 seconds my mouse begins to work again, but my keyboard still won't work. It seems as though if I press a few keys on my keyboard sometimes the mouse will lock up for another 30 seconds. Only a restart will make it all work normally.
gotcha. well in that case sorry I don't know
Ha it's cool. Hopefully somebody will know though!
have you written to apple to make sure it's ok to plug in an android phone to a mac?
are you on ICS or JB? if it's the later it could be the MTP connection that's been introduced
you have to let your mac and hox know that the lawsuit is over...
waz000000 said:
have you written to apple to make sure it's ok to plug in an android phone to a mac?
are you on ICS or JB? if it's the later it could be the MTP connection that's been introduced
Click to expand...
Click to collapse
Hahahahaha, for some reason I don't know if that was ever an issue lol
I'm running 4.0.4 which from what I understand is still ICS. So it's probably good that I haven't attempted to upgrade just yet?
The main reason I even care right now is because I'm trying to jailbreak, but I'm having all sorts of issues. I figured I'd start with this one haha.
hahaah
I bet if you had an iPhone ,you wouldn't run into this kind of problem ,htc
Sent from my HTC One X using xda premium
I have no issues with my mac...running OS10.8.2...i plugged my HOX, transferred data and even flashed boot.img via mac...no issues whatsoever..seems like you may have to do a SMB reset..try googling ur issue, probably there's a solution somewhere..
atrako1973 said:
I bet if you had an iPhone ,you wouldn't run into this kind of problem ,htc
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
When I plug in my iPhone I don't have this kind of problem
However, my iPhone also can't record audio anymore, and it's two years old. My HOX can and isn't :highfive:
amirage said:
I have no issues with my mac...running OS10.8.2...i plugged my HOX, transferred data and even flashed boot.img via mac...no issues whatsoever..seems like you may have to do a SMB reset..try googling ur issue, probably there's a solution somewhere..
Click to expand...
Click to collapse
I'll look up an SMB reset. Haven't heard of it. Still new to Android lol
However, I googled for a while and even went nuts on here looking for it, no one has this exact issue. The other similar issues only involve programs freezing. For me it seems like my keyboard and mouse freezing, while the computer keeps going. Sometimes I can't even get the two to talk to each other. And when I CAN get my HOX to connect without freezing up the keyboard and mouse, when I run the root through terminal it can't find the phone, in charging mode or in disk mode.
Your Mac is jealous
Sent from my HTC One X using xda app-developers app
So, did an SMC reset (when I googled SMB reset, SMC came up instead). I thought it worked, but it didn't. My mouse would unfreeze, but my keyboard would still be jacked until I restarted. And if I pressed too many keys on the keyboard the mouse would freeze back up for another 30 seconds. I am too tired to think of what I could do right now haha. Throw suggestions (LOGICAL ONES!) and I'll try it out haha. I just want this dang thing to work so I can root! :silly:
This is clearly a Mac issue. Absolutely nothing to do with the hox whatsoever.
You said that you used to be able to plug the phone in without any issues, and the only reason you want to plug the phone in now is to root it (You said Jailbreak but I presume you meant root).
Why don't you try a factory reset on the HOX and see if it resolves the issue. If it does then you can root your phone and will be installing a new ROM anyway so it won't matter that you've done the factory reset. If it doesn't then it means something has changed on you MAC and I can't help you unless you install Windows
Have you tried another usb charge cable with your phone and macbook it could be the cable is damaged internally causing a short circuit and making the usb devices play up even internal like keyboard/trackpad? Just a guess as Ive experienced a broken cable disabling usb which then works fine after reboot.
jo3yp said:
You said that you used to be able to plug the phone in without any issues, and the only reason you want to plug the phone in now is to root it (You said Jailbreak but I presume you meant root).
Why don't you try a factory reset on the HOX and see if it resolves the issue. If it does then you can root your phone and will be installing a new ROM anyway so it won't matter that you've done the factory reset. If it doesn't then it means something has changed on you MAC and I can't help you unless you install Windows
Click to expand...
Click to collapse
factory reset of HOX won't solve an issue with computer. It seems that you USB port is screwing up or is screwed up. See if you can connect another android device the computer and repeat the issue again...if so your USB port is jacked...BTW, u are not using an external keyboard/ mouse, are u?
I'd take the computer back to the service centre and shown them the issue...
me too...seems like MTP is not going well on mac(
jo3yp said:
You said that you used to be able to plug the phone in without any issues, and the only reason you want to plug the phone in now is to root it (You said Jailbreak but I presume you meant root).
Why don't you try a factory reset on the HOX and see if it resolves the issue. If it does then you can root your phone and will be installing a new ROM anyway so it won't matter that you've done the factory reset. If it doesn't then it means something has changed on you MAC and I can't help you unless you install Windows
Click to expand...
Click to collapse
I did mean root haha my bad. If a different USB cable doesn't work then I'll try resetting the phone
gffmac said:
Have you tried another usb charge cable with your phone and macbook it could be the cable is damaged internally causing a short circuit and making the usb devices play up even internal like keyboard/trackpad? Just a guess as Ive experienced a broken cable disabling usb which then works fine after reboot.
Click to expand...
Click to collapse
^^^^ Now THIS I haven't really thought of! And, actually I think it makes more sense than a software issue. I was having problems sometimes even getting the two to talk to each other unless I moved the cord a bit. I've dropped the phone from my nightstand a few times and it has landed on the cord, so I wouldn't be too surprised if either the cord is messed up or (God forbid) the port inside of the phone is messed up. Sometimes if I had the HOX in disk mode and moved the cord just a bit then it would suddenly eject and often freeze. I have another cable back home, so I'll grab it when I'm there tonight or tomorrow and see if I have the same issue!
Hi everyone,
first off, I've spend days now trying to find a fix. If I've missed anything, I'm sorry, it wasn't for lack of trying.
Here's the situation: I have acquired an HTC One X earlier this year which has worked quite flawlessly. I went ahead and unlocked the bootloader and installed a custom recovery. However, since I handed the phone off to my not-so-techy sister I did not use a custom ROM, and after the HTC update failed with the custom recovery I reversed that as well. The device should now be stock everything with unlocked bootloader.
After a few months my sister encountered heavy problems, though. She described them as battery related (wouldn't turn on correctly) and eventually she moved to a new phone. Now I have gotten the device back and I am trying to fix it. After charging it I managed to have it boot once. However, I but it to the side and wanted it to load some more. Ever since then the screen doesn't come on. The charging LED seems to work fine (eventually switched from red to green, too, indicating that the device is fully charged) and the button backlight still works, too. Most significantly though, the device is recognized as MTP device in Windows: I can access all the data in the storage without problems.
I have read that there is an issue with the HTC One X and the display connector so eventually I went ahead and took the device apart. It's lying in front of me now in pieces, but I still couldn't get the screen to come alive. The obvious conclusion would be to buy a new screen but the device doesn't feel like it's worth the investment. Besides, I would like to know for sure that it's the screen before I do anything.
So I turn to you guys and ask if you have any idea how I could access the phone via my computer. I tried to boot it up in bootloader mode but due to the strange standby methods HTC is using and not seeing anything on the screen I haven't been able to do that yet: Whenever I connect my USB cable it's recognized as MTP device, not ADB. Debugging seems to be deactivated so that doesn't seem to be an option. Does anyone have any idea how I could get the phone to talk to my computer (i.e. get into the bootloader or ADB screencast for sure)? With my Galaxy S I could simply plug in this dummy micro USB and would be sure to end up in download mode.
Any help is appreciated!
tl;dr: HTC One X screen is dead but LEDs work, is recognized as MTP device. How to make it talk to the computer?
Thanks,
rien
Alright, sometimes just posting stuff like this helps already. I was now finally able to get the phone into fastboot (apparently) and it's reacting to the fastboot commands. I suppose the next step is to load CWM and connect via adb. This way I can at least do a factory reset.
Does anyone have any ideas regarding the original issue with the screen? Especially since it does seem to work occasionally. And doesn't show any fragments...
Can I enable USB debug mode from within the recovery to work in the system?
Video of the issue: https://www.youtube.com/watch?v=XzIx9SHj6MQ&feature=youtu.be
According to my sister it has always had the screen "artifacts"as shown in the video where certain pixels are the wrong colours (which apparently never set off any alarm bells in her head... ). But apparently the screen and device stopped responding correctly a while back which i have been able to find out can be fixed by taking the back off the device. I can not use the recovery on the device since it just displays multicolored static on the screen, same thing happens when the device is plugged in to charge while powered off. I told her to get all important data off the device and factory reset it so the device is all at factory defaults to rule out software issues. After that didn't work i took the back off the device to check to see if the screen was connected correctly and to see if there were any obvious issues such as the cable being visibly damaged or disconnected etc.
Image of the issue when charging: http://i.imgur.com/Kat1RoC.jpg
So everything is stock on the device. It has never ran anything but official updates directly from Google.
The device is out of warranty and considering the cracks on the corners of the case i doubt Google/Asus would be happy to fix the device out of warranty without it getting expensive. It would be nice to fix it if it is possible or financially viable.
Any ideas and suggestions appreciated!
Have you tried a factory reset? If not, have you tried reflashing a stock rom, wiping everything?
dikidera said:
Have you tried a factory reset? If not, have you tried reflashing a stock rom, wiping everything?
Click to expand...
Click to collapse
It has been factory reset. I have not flashed a new ROM to it.
I have actually fixed that issue by putting some padding in to prevent the cable from flexing so much inside the case. So the device now functions as an e-reader and web browser. But it still cannot play video or cope with scrolling through images and so on due to the tearing. It gets worse the more that is updated on the screen. This may still be a cable issue.
I would flash a new kernel and ROM to the device but download mode doesn't work since no computer can recognize the device. In download mode and recovery the screen shows the static as shown in the image meaning i cant really use it easily. Since it is still running stock recovery i cant just flash a zip file, since download mode doesn't work it may be difficult to do the above.
But i only have experience with my own Galaxy S2 which runs custom everything. So my experience is with Odin and CWM, so i am not familiar with download mode for other manufacturers.
The second image, I know this. I was fiddling with the ribbon cables one day and I also got that distorted screen.
If it appears when charging, sounds like...the cable is not grounded or something and the signal(to/from the ribbon cable) is being distorted. But that is just a guess, it could be anything.
dikidera said:
The second image, I know this. I was fiddling with the ribbon cables one day and I also got that distorted screen.
If it appears when charging, sounds like...the cable is not grounded or something and the signal(to/from the ribbon cable) is being distorted. But that is just a guess, it could be anything.
Click to expand...
Click to collapse
Its not exclusive to charging though therefore i dont think it is power related. It happens every single time the system displays something on screen outside of Android. So the charging screen, recovery and download mode are all displayed as that.
Have you tried fiddling with said cable when you get the distorted image, in an attempt to perhaps fix it? it's odd that it appears with system messages. This sounds more and more like a true hardware issue(a defective unit) than software or a "simple" ribbon cable problem.
dikidera said:
Have you tried fiddling with said cable when you get the distorted image, in an attempt to perhaps fix it? it's odd that it appears with system messages. This sounds more and more like a true hardware issue(a defective unit) than software or a "simple" ribbon cable problem.
Click to expand...
Click to collapse
Not while it displays that image. But i have unplugged it and plugged it back in and nothing has helped.
My theory at the moment is that the cable is damaged meaning when the device tries to completely update the screen data goes missing and it struggles. Since videos dont work at all while the android flappy bird clone works flawlessly since it doesn't need to send as much data to update the screen due to the solid background colours and so on. But there are still holes in that theory, for example the issues become many many times worse when the device is in landscape mode.
So as far as i can tell it could be anything from heavily corrupted software to broken vram and anything in between including broken cable (since fiddling with that has fixed a different issue, perhaps its related) to the displays RAM for storing the previous screen update being broken. I can't tell.
Defective VRAM is also a possibility.
But I am not aware of any tool(for Android) that would allow for direct memory scanning of the VRAM. If you end up deciding the tablet is a goner, and want to buy a new one. I'd advise against another N7, it's already old, and the bugs are not worth the hassle.
dikidera said:
Defective VRAM is also a possibility.
But I am not aware of any tool(for Android) that would allow for direct memory scanning of the VRAM. If you end up deciding the tablet is a goner, and want to buy a new one. I'd advise against another N7, it's already old, and the bugs are not worth the hassle.
Click to expand...
Click to collapse
Yeah, im not aware of any either. I have also been through all the relevant debugging tools. Telling the screen to flash on update actually made the device function much better (where it flashes pink on each update) it stopped the issues from being serious. But lets face it, no one is going to want to use a device with that debugging option left enabled.
The touchscreen on my 2013N7 fizzled out earlier. Responsiveness has been on and off for the day - for a few hours it would improve after I press on a certain spot on the back of the device, but after that it has gone entirely. I've rebooted several times and there is no response.
I'm trying to use android control (http://forum.xda-developers.com/showthread.php?t=2786395) to just access it and get my data off of it, but when I plug it into a PC, the PC doesn't recognize that there is a device plugged in at all, even though it'll still charge the N7. It's completely missing from the device management list; adb shell can't find devices plugged in. I've looked around for possible fixes, but all of the ones mentioned require being able to access the tablet.
I'm at a bit of a loss here - is there a way to get the N7 to show up on the device list, or an alternate way to pull data off of it?
session030213 said:
it would improve after I press on a certain spot on the back of the device
Click to expand...
Click to collapse
The spot corresponds to the plug (att) and now it is time to unlock, reseat the cable and relock it as all of the problems relate to poor contact of the cable.
Same issue here,I am inserting a usb otg and connecting mouse there and then rebooting. This is really a bad issue
Sent from my Nexus 7 using Tapatalk