Related
I have a TF101 that's seemingly dead after being dropped. Currently, it does not power on. When plugged in with the ac charger, it shows no sign of charging, i.e., no light of any kind - amber, green or otherwise. I assume the mainboard has gone south.
When I connect it to my laptop, however, Windows 7 gives a chime and recognizes it as an MTP device, and even lists it as a TF101 in device manager. Linux also acknowledges that much. I can pretty much browse and access the content of the internal SD card like an external HD. Holding the power button long enough will unmount the device in either OS, which suggests that the device has turned itself off, and thus still responding to physical commands, or functioning on some level.
So it appears dead but not really. Being totally unfamiliar with this model, I'm not sure what possibilities the current state of affairs might indicate insofar as the device's vitality. Any input as to what this means is greatly appreciated.
If is it determined that the mainboard is done for, can anyone point me to a source for a replacement? If this kind of info solicitation is proscribed by regulation, my apology. Thank you.
My guess is, if the board was dead, you wouldn't be able to mount the device at all. It would suggest that it's actually alive and well, but the graphic/monitor part is dead, so you have no display at all. Mine also shows no signs of life (assuming I don't check the display) while it's charging and not on the dock. Only the dock has charging status lights as far as I can tell.
Sadly I can't help you further than that. I know they sell replacement parts on ebay and such, but I never even opened mine up, so I have no idea how easy it would be to replace any part. I know there's repair videos on youtube for the tf101, it might give you a clue if you open it up and run some tests.
Also check this out.
Lethe6 said:
My guess is, if the board was dead, you wouldn't be able to mount the device at all. It would suggest that it's actually alive and well, but the graphic/monitor part is dead, so you have no display at all. Mine also shows no signs of life (assuming I don't check the display) while it's charging and not on the dock. Only the dock has charging status lights as far as I can tell.
Sadly I can't help you further than that. I know they sell replacement parts on ebay and such, but I never even opened mine up, so I have no idea how easy it would be to replace any part. I know there's repair videos on youtube for the tf101, it might give you a clue if you open it up and run some tests.
Also check this out.
Click to expand...
Click to collapse
On second thought, I'm not too keen on replacing the MB just yet. Cracking the thing open is no big deal. I am dexterous enough. However, I am more intrigued by what is possibly going on.
If you guessed right, and transferring PC knowledge to this, the board would have a video chip integrated, with the other part consisting of an inverter and the LCD. If the integrated video circuit is dead, then connecting the device via HDMI to a TV would show nothing. If the device shows up, for instance, it's just the display part from the inverter on and so forth.
But I'm hesitant to go down that route. If it's the video part, then I should be able to do everything else like putting it in APX Mode, or flashing as with a normal device. Unfortunately, my computer never registered such activities; the tablet does not respond beyond the symptoms I described above.
As a matter of fact, I'd entertain any mad proposal on what should be tried on the thing at this point, just for the fun of it. I stand to lose little. So you can use your imagination and shoot some crazy ideas my way, and we'll see what.
So you tried with HDMI and it didn't work? You're right about APX though unless you're missing the drivers.. so maybe there really is some damage to the board. Sadly I don't have any crazy/mad suggestions at this point
My normal approach to possums (and the only legal thing I can do with them once captured) is to kill them or get someone else to kill them for me. :good:
As for your TF101, I seem to remember reading on another forum that when these devices are dropped and show the symptoms you describe, it can be caused by a ribbon cable that connects the display to the motherboard being jolted loose. It might be worth opening it up and check both ends of the appropriate cable for secure fit.
Mike_NZ said:
My normal approach to possums (and the only legal thing I can do with them once captured) is to kill them or get someone else to kill them for me. :good:
As for your TF101, I seem to remember reading on another forum that when these devices are dropped and show the symptoms you describe, it can be caused by a ribbon cable that connects the display to the motherboard being jolted loose. It might be worth opening it up and check both ends of the appropriate cable for secure fit.
Click to expand...
Click to collapse
Hey I totally agree that killing it may be the only option right now. And I don't mind that, just that I'd prefer the scalpel to the cleaver, and doing it in such a way that I would learn something about it that may be of benefit to me and incidentally, to others. I did open the thing, and you're again right, people have run into this problem of the LCD cable being jarred loose on impact from Asia to the Western Hemisphere to Eastern Europe. But it's not that, as I did unseat and reseat the cable on both ends, for naught.
As to the APX drivers, I did try both Easy Flasher and PERI 0.4. They act as if they finish the job. However, the tablet remains consistently inert. Lethe6, am I missing something here? How do you tell if the APX drivers are missing? Normally Windows would show the USB device as in APX mode right? Mine did not do that. When I tried to update the driver in Device Manager, Windows refused to do it claiming it was not necessary. Is there a way to force-install the drivers just to see?
Oh well, I'd just let the issue hang at this point and see what else comes this way.
Yeah if you connect your device in APX mode it should pop up in the device manager, just right-click uninstall then re-install the drivers. I don't remember what's the exact device name but iirc it's something generic. Sorry I can't check I'm on a Mac at work and my TF101 is at home.
What about HDMI? Did you ever get a signal through there? Tried having it connected when assuming to do a full boot?
Lethe6 said:
Yeah if you connect your device in APX mode it should pop up in the device manager, just right-click uninstall then re-install the drivers. I don't remember what's the exact device name but iirc it's something generic. Sorry I can't check I'm on a Mac at work and my TF101 is at home.
What about HDMI? Did you ever get a signal through there? Tried having it connected when assuming to do a full boot?
Click to expand...
Click to collapse
I never had the chance to try the HDMI output. Still waiting for the adapter to arrive. Ebay can be a pain during holiday season. But I'd sure to report the result. When I plugged the thing in, Win recognized it as an MTP device and proceeded to install drivers automatically. After which it showed in Device Manager as TF-101. So apparently the drivers are correct, though they dated back to 2006!!?? However, with other devices like the Acer A500, the USB device symbol normally would appear at the right bottom bar with the designation "APX device." With this thing, nothing - not even the icon. What's your thought on this?
I don't have any other devices that I can boot into APX (HTC won't tell anyone and my other tablet is a craplet, have to ADB on the live FS, which is awesome lol) so I can't compare here, but have you tried these drivers for APX? It's been a while but I seem to remember needing special drivers for APX. The device had a weird name.. like a bunch of numbers and letters... haven't used it since easyflasher though.
When I plug it in APX the device is called "NVIDIA USB Boot-recovery driver for mobile devices" and it's dated 1/31/2011.
When I plug it in Rogue Recovery the device is called "Asus Android MTP Device" dated 7/17/2012.
When I plug it in booted to 4.0.3 the device is called "Transformer TF101" dated 7/17/2012.
So I'm guessing yours never enters APX or has the wrong drivers? Maybe try installing the ASUS Sync software? Not sure but it may bring newer drivers...
I assume you're doing all this undocked as well?
I have a quick question. It seems that my tablet has lost its ability to connect through USB recently. I was unable to send pictures to the pc one day and have bought numerous cables to no avail. Looks as if, somehow, it just wont connect through usb. The original cable was acting up during charging anyway. My main question is, how do I root without the ability to connect to a pc? Is this at all possible? I was rooted before but since installing the newest update, 10.6.1.27.5-20130902, i noticed it wasn't rooted anymore.Am I pretty much SOL? BTW, nowadays the tablet wakes up and beeps like every other minute while charging. Dont know if its related. I wish I didnt do the update altogether.
Updating to the latest firmware (at last check) hides the developer options from the settings. Your problem might be that USB debugging was disabled or never was enabled.
To add developer settings back into the settings, you need to go into the "about tablet" in settings and tap the build number 5 or so times and then developer options should show up.
tayden812 said:
I have a quick question. It seems that my tablet has lost its ability to connect through USB recently. I was unable to send pictures to the pc one day and have bought numerous cables to no avail. Looks as if, somehow, it just wont connect through usb. The original cable was acting up during charging anyway. My main question is, how do I root without the ability to connect to a pc? Is this at all possible? I was rooted before but since installing the newest update, 10.6.1.27.5-20130902, i noticed it wasn't rooted anymore.Am I pretty much SOL? BTW, nowadays the tablet wakes up and beeps like every other minute while charging. Dont know if its related. I wish I didnt do the update altogether.
Click to expand...
Click to collapse
If its a cable problem, the cable only costs 5$ on amazon.
I'm on my third replacement cable already. Also, developer options are turned on. USB debugging is on as well. They charge fine but connecting them directly to any computer i have does nothing, almost like not plugging it in at all. Have tried on three different setups that worked before, Win 7 X64, Win 8 X64, Win XP X86.
tayden812 said:
I'm on my third replacement cable already. Also, developer options are turned on. USB debugging is on as well. They charge fine but connecting them directly to any computer i have does nothing, almost like not plugging it in at all. Have tried on three different setups that worked before, Win 7 X64, Win 8 X64, Win XP X86.
Click to expand...
Click to collapse
Disable the developer options and USB debugging. Windows may be trying to recognize the ADB instead of trying to mount partitions.
cmendonc2 said:
Disable the developer options and USB debugging. Windows may be trying to recognize the ADB instead of trying to mount partitions.
Click to expand...
Click to collapse
Tried that too. Doesn't seem to work either way.
Which worries me severely.
If you haven't already, install the google sdk adb drivers and see if that works, though from what it sounds like that's not the problem.
I'm thinking bad usb port on computer... try wireless adb if you can...
Sent from my TF300T
might be that the plug at your tablet got damage some how? maybe not fully damaged but partialy, do u have a dock? if you have you have any problem with it?
sorry for my bad english
Greetings!
Don't have the dock. Went to the Best Buy out here and they don't got it. Worst case scenario, my port is jacked up, can I still root without it? If so what steps can I take to do so?
depends on if you have a custom recovery like twrp if you do, then you should ok flashing supersu package, otherwise you are in the worst case scenario...
Sent from my TF300T using Tapatalk
Drahric said:
depends on if you have a custom recovery like twrp if you do, then you should ok flashing supersu package, otherwise you are in the worst case scenario...
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
THought so. The update completely killed my recovery as well. Doh! Thanks for the help guys.
If your still under warranty then you could get it fixed but from what sound like that wont help...
Take care.
Sent from my TF300T using Tapatalk
Hello all!
I'm just guna say, this might get long winded so, TLDR, Nexus 7 has no OS, I can get into the boot loader, the only thing I can actually do is get into TWRP v2.8.01, computer doesn't recognize it, can't get it to even see a flash drive that I've formatted to Fat32, now what?
For those who want some background. I got my N7 refurbished from ebay, if that matters at all. First thing I did was update it to Kitkat and root it. Installed some apps and was happy with it for a few months. About a month or so ago it stopped connecting to the Google Play Store. I wasn't bothered by it too much. But as time goes on, I find new apps and would like to use them. But obviously can not.
So, just to be safe, I wrote down all the apps I still had on it just in case they didn't want to load back up. Did a factory reset, still couldn't connect. Looked online and cleared caches and stopped services. Still didn't work. When I went onto the GPS, heh, on my computer it said that I had no devices so that was a clue of some sort. I could still go onto Youtube and log in and use it just fine. Just nothing in the store. So I decided to try something else.
What that was was to clear all my data with TWRP. Went to put in my email and password, couldn't connect, tried another wifi connection, still no go. I was able to use it, but the Play Store still didn't want to play nice. So in a bit of, "rage" we'll call it. I formatted it and now I'm where I am now. With a tablet that won't boot, just sit at the Google logo for up to 5 mins, as long as I've let it sit there for anyway. I have downloaded the Nexus Root Kit and tried to use that, but my computer won't even see my N7 now. In the bootloader or TWRP. So I can't even get anything onto it now.
So, what now? Do I have a bricked tablet that won't do anything or is there something an Android Guru out there can help me with? I'd like to keep it. I mainly used it to read and for various videos.
I have posted on forums.androidcentral but after a week and almost 300 views, no one has made any comments. I'm sorry for my ignorance if I'm missing something.
Thanks! I shall be hoping for good news.
So, does ADB recognize your tablet or not when you type "fastboot devices"?
I take it you mean shift+right clicking in the platform tools folder, open command window here, and typing that into the command prompt? If so, then no, it doesn't show up.
Waslow said:
I take it you mean shift+right clicking in the platform tools folder, open command window here, and typing that into the command prompt? If so, then no, it doesn't show up.
Click to expand...
Click to collapse
Can you go into the bootloader? Did you install the right drivers?
I can get into the boot loader just fine. Recovery sends me to TWRP 2.8.01. I've got the drivers from the Android SDK Manager, Rev. 11 apparently. Would that be any different from the standard drivers that get installed when you hook up the N7? Well, when it works?
Waslow said:
I can get into the boot loader just fine. Recovery sends me to TWRP 2.8.01. I've got the drivers from the Android SDK Manager, Rev. 11 apparently. Would that be any different from the standard drivers that get installed when you hook up the N7? Well, when it works?
Click to expand...
Click to collapse
That is correct. Use this: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
And if doesn't work check in device manager.
If it works flash the latest factory image and then you will be good to go
I've already had that installed and set up and nothing pops up in the device manager. I've also tried all the usb ports on my computer to no avail.
Waslow said:
I've already had that installed and set up and nothing pops up in the device manager. I've also tried all the usb ports on my computer to no avail.
Click to expand...
Click to collapse
Then try the driver manual in nexus root toolkit
I can follow the instructions, but that doesn't resolve the fact that my computer can't see the Nexus .
go into device manager and delete every single entry that suggests anything to do with a phone, tablet, google device, nexus device, ETC. if you dont do that first, this will probably not work.
once you delete every single entry in there, go to the top command bar and somewhere in those menus is an option to show disconnected devices. delete everything again as above.
now, does your tablet still charge on the AC plugged into the wall? does it still charge when plugged into the computer usb? drivers are NOT required for usb to supply power. if so, the usb connector is probably OK. if not, your usb connector may be toast.
next, connect to the computer. does windows show any device connected? if not, try a different usb cable. report your findings back.
Sorry for the late reply.
There is nothing in the device manager related to my Nexus, which is odd, it had entries for flash drives, a camera, and my phone. All of which were in the disconnected devices. I got rid of just for the sake of it. Nexus charges just fine, either from the wall or any of my usb ports. If there is no way to make ANY computer see my Nexus, is it safe to say it's bricked?
I do have a cousin who's fluent in Linux if that means anything. I know that Android is a flavor of it. Might work better if both devices speak the same language. Grasping for straws I know.
Again, thanks for the help fwayfarer, GtrCraft, and Fobos531!
If I am reading right, you did NOT try a new USB CABLE yet, did you?
Try a known good USB cable, what I mean by that is try a cable you KNOW works for data transfer on another device and report back.
Connecting it to a Linux machine isn't going to make any difference in my opinion.
I have 2 cables and they transfer things just fine with my phone and my Kindle. I just downloaded everything off of both things, and transferred them back. No issue with the cables. I just popped open my Nexus and it looks like the usb connector and ribbon are fine. I did wiggle them a little but to no avail.
Pull the battery cable, smash the power button for a few minutes, reconnect and try again. It won't recognize a USB thumb drive in bootloader or recovery to my knowledge, BTW. I noticed you mentioned it not seeing one.
I unplugged the battery, hit the power switch for a while, plugged the battery back in, plugged the usb back in, nothing. Still nothing. I had read before that you can put the version of android you wanted on a flash drive. With an otg cable you could use that to update/install what you wanted.
You're probably right, I haven't tried using one in recovery for a long time. You didn't change the battery or anything recently did you?
Nope, haven't replaced anything in the Nexus. The only thing that I could think of that could be wrong is the usb connector. But for it to "fail" at the same time I formatted everything, too much of a coincidence.
Over a week bump
I ran into a similar problem about a year ago. Unless your tablet is connected to the computer you will not see it show up it the windows device manager. You should be able to connect your N7 to a work computer & it should go out for the drivers. If not, then you are Sol. You might have a blown main board.
The only thing my N7 does when I plug it in, is that it charges. That's the only thing I can get it to do. Well, this sucks. If I really have a bricked, or worse, tablet, it's still good for its screen and other bits.
I have read every single thread that exists on the internet about this problem, the bootloops, the faulty bootloaders, the wrong rooting and image installations, every single posible way to brick this piece of device that everyone seems to have problems with. Yet none of them has gave me a solution. First of all, it's my girlfrinds tablet, she told me that one day, she tried to upgrade the android software and while it was installing it, the tablet bricked. She was able to go to fastload mode (power + volume up) we've tried recovery mode, factory reset, every option there, nothing. She gave me the tablet, I plugged it on my pc and used Nexus Root Kit to install a new android software to the device. After a painful search of how to make the Kit recognize the tablet because usb debugging was not on, I was able to start the process of installing the new software. Yet, in the middle of the installation, the micro-usb moved a little bit and the tablet got disconected. The process was cancelled and the tablet screen froze. I turned the tablet off and that was when it just bricked and never wanted to turn back on. Neither with any combination of the buttons, nor while leaving it charging a long time, nor any possible solution the internet may have about this. Just fully totally and simply bricked. Yet, when I connect it to my pc (windows 7 ultimate 64 bits) sometimes, it reads it as an unknown device, sometimes it reads it as a random APX device, and when I install any kind of drivers that already exist on every thread that there is about it, it reads it as an ASUS Transforme Prime APX Interface, yet the tablet never displays anything, and I'm not able to access it in any way nor make any changes to it whatsoever. I live in a country were there is no google or asus techical support, and third-party technical supporters are dumb as f***. My girlfrind took the tablet to 2 other places before giving it to me and they said to her that "it didn't have any software installed" (which was wrong) and that "it was beyond repair" (which was also wrong). The only thing I want to know is: is there any way to fix it now? or do I just have a very nice and fancy paperweight in my hands.
Makatown said:
I have read every single thread that exists on the internet about this problem, the bootloops, the faulty bootloaders, the wrong rooting and image installations, every single posible way to brick this piece of device that everyone seems to have problems with. Yet none of them has gave me a solution. First of all, it's my girlfrinds tablet, she told me that one day, she tried to upgrade the android software and while it was installing it, the tablet bricked. She was able to go to fastload mode (power + volume up) we've tried recovery mode, factory reset, every option there, nothing. She gave me the tablet, I plugged it on my pc and used Nexus Root Kit to install a new android software to the device. After a painful search of how to make the Kit recognize the tablet because usb debugging was not on, I was able to start the process of installing the new software. Yet, in the middle of the installation, the micro-usb moved a little bit and the tablet got disconected. The process was cancelled and the tablet screen froze. I turned the tablet off and that was when it just bricked and never wanted to turn back on. Neither with any combination of the buttons, nor while leaving it charging a long time, nor any possible solution the internet may have about this. Just fully totally and simply bricked. Yet, when I connect it to my pc (windows 7 ultimate 64 bits) sometimes, it reads it as an unknown device, sometimes it reads it as a random APX device, and when I install any kind of drivers that already exist on every thread that there is about it, it reads it as an ASUS Transforme Prime APX Interface, yet the tablet never displays anything, and I'm not able to access it in any way nor make any changes to it whatsoever. I live in a country were there is no google or asus techical support, and third-party technical supporters are dumb as f***. My girlfrind took the tablet to 2 other places before giving it to me and they said to her that "it didn't have any software installed" (which was wrong) and that "it was beyond repair" (which was also wrong). The only thing I want to know is: is there any way to fix it now? or do I just have a very nice and fancy paperweight in my hands.
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
Your thread will be moved to Nexus 7 Q&A,Help and Troubleshooting.Experts there may be able to help you
___
v7
XDA Assist
Ha, yes...same boat and similar situation happened where USB became disconnected during bootloader flash. Surprised there haven't been any snarky comments made on your (and now my) situation. I have a totally non-responsive device now and Windows is also not recognizing the USB device (because it does not respond back when attempting to connect/mount). Looks like the only magic at this point would be cracking open and trying a completely different path to restoring, otherwise it is time to find a nice door needing a doorstop!
~Dubhead
Hello people,
so a few days ago I dropped my Galaxy S5 and the screen is now black, I can't use it. I want to try to save the data, but it's not as easy as plug in and transfer, since I have a password that I can't unlock. Using a screen mirroring program is also out of question, because I had USB Debugging disabled before I dropped it.
My next thought was to enable USB debugging with the help of adb, but that didn't work, since adb sees my device as "unauthorized". It still shows up as "Samsung Android ADB Interface" up in the Windows Device Manager.
So my next thought was to flash a custom recovery such as CWM via Odin (my phone doesn't have to be rooted for that, right?). That way I could use the volume keys to navigate through recovery mode once I enter it. All I would have to do is look at screenshots online and count how many times I press the volume buttons to know when to hit enter since the sceen doesn't work.
Would that even be helpful? I really hope that someone can help me or at least tell me there is no possible way to recover the files so I can sleep in peace. I've been trying so much, but all I find is more problems. I even had to use the Samsung 300K tool to enter Download mode, since that didn't work at one point. And I did that to use Dr. Fone's Android Lock Screen Remover which didn't remove my password. So that was 50 dollars well spent.
Looking forward to any kind of help, really desperate right now!
i dont think you can enable usb debugging from outside of the GUI. Can you use one of those MHL devices to get the display output to something? Perhaps the digitizer will still recognize touch input and let you turn it on from there.
youdoofus said:
i dont think you can enable usb debugging from outside of the GUI. Can you use one of those MHL devices to get the display output to something? Perhaps the digitizer will still recognize touch input and let you turn it on from there.
Click to expand...
Click to collapse
That's a pretty good idea! Looks like I haven't tried everything after all. I'll take a look if I the local electric market has some sort of adapter or is there anything I have to take into consideration? I am not familiar with the term MHL...
zakuani said:
That's a pretty good idea! Looks like I haven't tried everything after all. I'll take a look if I the local electric market has some sort of adapter or is there anything I have to take into consideration? I am not familiar with the term MHL...
Click to expand...
Click to collapse
nothing else really to take into consideration, just hope it works for ya
https://images-na.ssl-images-amazon.com/images/I/413PWcLXQHL._SY300_.jpg