Related
I'm quite confused with this one. Here's what's happened so far.
I was on AOKP Build 31 with CWM touch 5.8.2.1 and decided I want to go back to stock and start fresh. I found a mostly stock 9.2.1.17 from a thread in XDA titled "[ROM] TF101 Rooted Stock 9.2.1.17 + bootloader + modded recovery US and WW" (sorry, can't post links). I downloaded, checked the MD5, made a nandroid, wiped data/cache/Dalvik and installed the ROM. After doing that, I have been unable to get my device to connect to any computer via USB. I tried restoring my backup and also re-flashing a fresh copy of AOKP Build 31. I am able, however, to connect via ADB using TCP/IP. When I plug the device into my Windows 7 Pro, 64-bit I don't get any sort of notification or sound. When I plug the device into my Ubuntu 11.10, 64 bit I also don't have a connection showing up using the 'sudo lsusb' command. The strangest thing is that when I plug the device in the screen turns on, so clearly the USB cable is not the cause. I've tried two different Win. 7 computers, my Ubuntu box and a Fedora box (and multiple USB ports on each computer). Any suggestions?
Try this, Settings> Storage> hit the 3 dots sign at top right corner, hit USB computer connection,
Un check the MTP box and check it again. If that don't work try turning off USB debugging
Try this, Settings> Storage> hit the 3 dots sign at top right corner, hit USB computer connection,
Un check the MTP box and check it again. If that don't work try turning off USB debugging
Click to expand...
Click to collapse
Tried that on one of the Win. 7 boxes and the Ubuntu box, no success.
Have you tried reinstalling the drivers? I had to do that when I went from stock to custom rom.
This happens a lot. Something to do with the bootloader not getting flashed properly or something.
Get the full ICS ROM from Asus website and flash it.
horndroid said:
This happens a lot. Something to do with the bootloader not getting flashed properly or something.
Get the full ICS ROM from Asus website and flash it.
Click to expand...
Click to collapse
Just did that... lost root -.- stock and no usb >:/
Does anyone have any ide how i can root it now?
Get the full ICS ROM from Asus website and flash it.
Click to expand...
Click to collapse
I also tried doing this, without success. I'll try a few other things, thanks for the help though all!
You can root it (rather painfully and obscurely) by using an update.zip with the version of the firmware Razorclaw needs to work, and root in tablet and then flash in tablet. Downgrading to the required honeycomb might fix the usb too. I've never had to use ADB to do anything on my tf, aside from developing
Thing O Doom said:
You can root it (rather painfully and obscurely) by using an update.zip with the version of the firmware Razorclaw needs to work, and root in tablet and then flash in tablet. Downgrading to the required honeycomb might fix the usb too. I've never had to use ADB to do anything on my tf, aside from developing
Click to expand...
Click to collapse
How can i downgrade to honeycomb? without recovery?? and where can i find the ww version of it?
baseballfanz said:
Try this, Settings> Storage> hit the 3 dots sign at top right corner, hit USB computer connection,
Un check the MTP box and check it again. If that don't work try turning off USB debugging
Click to expand...
Click to collapse
Ive rooted a bajillion devioces and never thought to look there when my tf101 stopped connecting, ive rebooted my pc and it a hundred times
Thanks for the DOH! moment !!
Hello,
I have a strange issue - one that I've had for a while now - where neither my PC or laptop will 'discover' my TF700 as a storage device and allow me to copy/paste/delete files from it. This is incredibly annoying as it means I cannot now copy on any new roms.
Strangely - I have managed to flash new recoveries onto the device, but again this hasn't change anything as far as being able to copy/paste files in Windows.. Instead I am stuck with the current (very old) custom ROM I installed a few months ago.
Could this be something to do with the USB drivers I have on my PC/Laptop? I'll be honest - I have tried several.
Could it be something to do with the cable? My official cable is a complete mess and almost in pieces, the replacement I bought (cheaply) doesn't charge properly, but again both work when flashing stuff across...
I am at a bit of a loss... Hopefully someone can guide me in the right direction.
Many thanks in advance for any help
I had the same issue, almost, when flashing TWRP.
All I did was reboot the tablet while plugged into the PC and it was recognized again.
Not sure if it will help you but it is worth a try.
Thanks for the reply.
That was not the issue, I had tried a laptop, my main PC, a couple of cables, reboots, erasing partitions etc. etc.
I finally fixed it today by flashing the latest firmware blob via fastboot, albeit after flashing a jellybean bootloader, as it would not flash properly previously.
Straight after flash of blob it rebooted, took around five minutes finalising configuration and hey presto, Windows found it and everything was well with the world again.
Cheers
OK. First of all, although I'm using the TF101 for the first time, I'd like to say that I've done a fair bit of rooting, troubleshooting and customizing various Android devices (HD2, Desire, SE x10, SGS2, SGSN, SGSN2...). So I ensure you, any lack of knowledge regarding the TF101 is not caused by ignorance. I'm trying to find out the cause for my problem for few days now, but can't find something to catch on. There are many similar problems with TF101 not being recognized by PC, but they all offer solutions which don't work, I don't understand them, or which make no sense.
Let's start at the beginning.
I have gotten my hands on Asus EEE Pad Transformer TF101. It was really cheap. I was told it came form USA.
It's obviously rooted, has a custom rom and recovery (ClockworkMod Recovery v3.2.0.1. roach2010-tf101-r1)
This is waht it says in Settings>About:
Model Number:
Transformer TF101G (although I think it is actually just a Wi-Fi model - TF101, it has no SIM slot)
Android version:
3.2.1
Baseband version:
Unknown
GPS version:
V5.5.8
Wi-Fi version:
V5.2.65
Bluetooth version
v6.24
Kernel version:
2.6.36.4-g6aa10ba
[email protected] #20111023
Build number
HTK75.prime_epad-2.1.0-20111105
Mobile Dock version:
Not available
It seems to be working fine, except for being totally filled up with apps, bloatware and data. Natural instinct was to install a clean ROM. I wanted to go with CM, and a newer Recovery, but I got stuck on the first step. I can't get it recognized on any of my computers. Both Windows 7 and 8.
However I plug it in, I get; USB device not recognized. One of the USB devices attached to you computer has malfunctioned... This happens when I connect the USB cable when Android is booted up, when in recovery and also in APX mode, providing I have entered it (I'm not really sure because the display is always black).
In Device Manager, I can see only one exclamation icon (I did enable show hidden devices) in Universal Serious Bus Controllers called Unknown Device, which seems to be from the TF101. I tried uninstalling it. Restarting both the tablet and the computers. I tried to manually override those Unknown Device drivers with ASUS Android USB drivers for Windows and Universal_Naked_Driver_0.72 and ventana apx driver, but it wouldn't take any of them. I also tried installing them manually by right clicking on the INF files, and still nothing.
Then I thought I could mount the sdcard or USB mode in recovery, but that wouldn't work either.
Any solutions?
Do you have the stock USB cable? Are you plugging in to a usb3 slot?
Does the rom have fast charge enabled? I think that's what it's called but it allows USB charge rather than seeing your files and such.
Do you have mtp mode or mass storage mode options on the tablet?
Sent from my SGH-T999 using Tapatalk 2
Yes, I have stock USB cable. At least I think so. I'm not the first owner. How can I be sure? It seems to be charging fine on the wall charger. It doesn't charge thru PC though.
If you are asking me if I tried it on USB 3.0; yes I did. Both 2.0 and 3.0. Not recognized.
I don't know if the ROM has "fast charge". I'm new to the TF101, and Honeycomb in general, and I didn't notice such an option. Where can I look?
I also didn't see any MTP/Mass storage modes in settings. Where would they be?
estugarda said:
Yes, I have stock USB cable. At least I think so. I'm not the first owner. How can I be sure? It seems to be charging fine on the wall charger. It doesn't charge thru PC though.
If you are asking me if I tried it on USB 3.0; yes I did. Both 2.0 and 3.0. Not recognized.
I don't know if the ROM has "fast charge". I'm new to the TF101, and Honeycomb in general, and I didn't notice such an option. Where can I look?
I also didn't see any MTP/Mass storage modes in settings. Where would they be?
Click to expand...
Click to collapse
Lol I don't know on honeycomb. It's been a long time but these threads are filled with fast charge and the other issue as well. Do some more searches it's bound to give you something.
Sent from my SGH-T999 using Tapatalk 2
TomTcom said:
Lol I don't know on honeycomb. It's been a long time but these threads are filled with fast charge and the other issue as well. Do some more searches it's bound to give you something.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I did look around. I read a ton of posts here and elsewhere. There is nothing to the point. People at transformer forums are actually advising to just forget about the usb and use wireless transfer instead, since there are so many people with this problem who can't solve it. That would be fine with me, but I'm especially stuck because I can't flash anything since my USB connection is not working, and current CWM recovery doesn't seem to support flashing from internal memory/sd card.
Before you do anything else, install TWRP recovery before you brick your TF with CWM
Install Goo Manager here
https://play.google.com/store/apps/details?id=com.s0up.goomanager
Tap the menu dots at the top right of the app and choose "Install OpenRecoveryScript"
That should flash the latest TWRP recovery for you
estugarda said:
OK. First of all, although I'm using the TF101 for the first time, I'd like to say that I've done a fair bit of rooting, troubleshooting and customizing various Android devices (HD2, Desire, SE x10, SGS2, SGSN, SGSN2...). So I ensure you, any lack of knowledge regarding the TF101 is not caused by ignorance. I'm trying to find out the cause for my problem for few days now, but can't find something to catch on. There are many similar problems with TF101 not being recognized by PC, but they all offer solutions which don't work, I don't understand them, or which make no sense.
Let's start at the beginning.
I have gotten my hands on Asus EEE Pad Transformer TF101. It was really cheap. I was told it came form USA.
It's obviously rooted, has a custom rom and recovery (ClockworkMod Recovery v3.2.0.1. roach2010-tf101-r1)
This is waht it says in Settings>About:
Model Number:
Transformer TF101G (although I think it is actually just a Wi-Fi model - TF101, it has no SIM slot)
Android version:
3.2.1
Baseband version:
Unknown
GPS version:
V5.5.8
Wi-Fi version:
V5.2.65
Bluetooth version
v6.24
Kernel version:
2.6.36.4-g6aa10ba
[email protected] #20111023
Build number
HTK75.prime_epad-2.1.0-20111105
Mobile Dock version:
Not available
It seems to be working fine, except for being totally filled up with apps, bloatware and data. Natural instinct was to install a clean ROM. I wanted to go with CM, and a newer Recovery, but I got stuck on the first step. I can't get it recognized on any of my computers. Both Windows 7 and 8.
However I plug it in, I get; USB device not recognized. One of the USB devices attached to you computer has malfunctioned... This happens when I connect the USB cable when Android is booted up, when in recovery and also in APX mode, providing I have entered it (I'm not really sure because the display is always black).
In Device Manager, I can see only one exclamation icon (I did enable show hidden devices) in Universal Serious Bus Controllers called Unknown Device, which seems to be from the TF101. I tried uninstalling it. Restarting both the tablet and the computers. I tried to manually override those Unknown Device drivers with ASUS Android USB drivers for Windows and Universal_Naked_Driver_0.72 and ventana apx driver, but it wouldn't take any of them. I also tried installing them manually by right clicking on the INF files, and still nothing.
Then I thought I could mount the sdcard or USB mode in recovery, but that wouldn't work either.
Any solutions?
Click to expand...
Click to collapse
Are those drivers signed? I know 7 will reject an unsigned driver for security reasons.
Nexus 4 CyanogenMod 10.1.0RC2
---------- Post added at 02:04 PM ---------- Previous post was at 02:01 PM ----------
estugarda said:
Yes, I have stock USB cable. At least I think so. I'm not the first owner. How can I be sure? It seems to be charging fine on the wall charger. It doesn't charge thru PC though.
If you are asking me if I tried it on USB 3.0; yes I did. Both 2.0 and 3.0. Not recognized.
I don't know if the ROM has "fast charge". I'm new to the TF101, and Honeycomb in general, and I didn't notice such an option. Where can I look?
I also didn't see any MTP/Mass storage modes in settings. Where would they be?
Click to expand...
Click to collapse
It should be somewhere in "storage" in settings.
Nexus 4 CyanogenMod 10.1.0RC2
Here you go hope it helps
Nexus 4 CyanogenMod 10.1.0RC2
*Detection* said:
Before you do anything else, install TWRP recovery before you brick your TF with CWM
Install Goo Manager here
https://play.google.com/store/apps/details?id=com.s0up.goomanager
Tap the menu dots at the top right of the app and choose "Install OpenRecoveryScript"
That should flash the latest TWRP recovery for you
Click to expand...
Click to collapse
Unfortunately, GO Manager wouldn't install OpenRecoveryScript. It says something along the lines of "No Recoveries were found for your device..."
ryaniskira said:
Are those drivers signed? I know 7 will reject an unsigned driver for security reasons.
Those from Asus websites are signed 100%.
Nexus 4 CyanogenMod 10.1.0RC2
Click to expand...
Click to collapse
estugarda said:
Unfortunately, GO Manager wouldn't install OpenRecoveryScript. It says something along the lines of "No Recoveries were found for your device..."
Click to expand...
Click to collapse
You might need to update to ICS first then, maybe Honeycomb is too old
CWM has a habit of boot looping devices, I would try updating to an ICS ROM and then trying Goo again before going for a Jellybean ROM
EDIT - You might have more luck getting TWRP installed using Easyflasher
http://forum.xda-developers.com/showthread.php?t=1688012
In the same boat
estugarda said:
OK. First of all, although I'm using the TF101 for the first time, I'd like to say that I've done a fair bit of rooting, troubleshooting and customizing various Android devices (HD2, Desire, SE x10, SGS2, SGSN, SGSN2...). So I ensure you, any lack of knowledge regarding the TF101 is not caused by ignorance. I'm trying to find out the cause for my problem for few days now, but can't find something to catch on. There are many similar problems with TF101 not being recognized by PC, but they all offer solutions which don't work, I don't understand them, or which make no sense.
Let's start at the beginning.
I have gotten my hands on Asus EEE Pad Transformer TF101. It was really cheap. I was told it came form USA.
It's obviously rooted, has a custom rom and recovery (ClockworkMod Recovery v3.2.0.1. roach2010-tf101-r1)
This is waht it says in Settings>About:
Model Number:
Transformer TF101G (although I think it is actually just a Wi-Fi model - TF101, it has no SIM slot)
Android version:
3.2.1
Baseband version:
Unknown
GPS version:
V5.5.8
Wi-Fi version:
V5.2.65
Bluetooth version
v6.24
Kernel version:
2.6.36.4-g6aa10ba
[email protected] #20111023
Build number
HTK75.prime_epad-2.1.0-20111105
Mobile Dock version:
Not available
It seems to be working fine, except for being totally filled up with apps, bloatware and data. Natural instinct was to install a clean ROM. I wanted to go with CM, and a newer Recovery, but I got stuck on the first step. I can't get it recognized on any of my computers. Both Windows 7 and 8.
However I plug it in, I get; USB device not recognized. One of the USB devices attached to you computer has malfunctioned... This happens when I connect the USB cable when Android is booted up, when in recovery and also in APX mode, providing I have entered it (I'm not really sure because the display is always black).
In Device Manager, I can see only one exclamation icon (I did enable show hidden devices) in Universal Serious Bus Controllers called Unknown Device, which seems to be from the TF101. I tried uninstalling it. Restarting both the tablet and the computers. I tried to manually override those Unknown Device drivers with ASUS Android USB drivers for Windows and Universal_Naked_Driver_0.72 and ventana apx driver, but it wouldn't take any of them. I also tried installing them manually by right clicking on the INF files, and still nothing.
Then I thought I could mount the sdcard or USB mode in recovery, but that wouldn't work either.
Any solutions?
Click to expand...
Click to collapse
Have exhausted all resources all so if you find out anything please pm me. In the mean time I am still looking and I will keep you posted if I find out anything.
philseven said:
Have exhausted all resources all so if you find out anything please pm me. In the mean time I am still looking and I will keep you posted if I find out anything.
Click to expand...
Click to collapse
My guess is a bad USB cable. I had my USB cable stop working for ADB/APX/MTP/PTP but it still works with the Asus wall wart for charging. New USB cable fixed it straight away.
Solution
hi. if you cannot enter apx mode. try flashing a new rom of the tf101 or reflashing your current recovery
Soft brick Asus transformer tf101,None boot stuck\no USB
Hello I'm having the same problem with my tf101 but I can't get windows 7 64bit too load a driver for it, tried them all? Mine is soft bricked and there's no recovery file to restore. getting file not found.
Only shows CMW Based recovery v 5.5.0.4 roach-tf101-r2, also won't see SD card to re flash a rom or recovery.img, seems everywhere I turn I hit a wall on getting it back to working again, just hangs on Asus Logo?
please help? do I need to use a terminal program? is there a way to force a driver to load and see it long enough to reimage?
Thanks tons for any help.:crying:
rmontgo3Denver said:
Hello I'm having the same problem with my tf101 but I can't get windows 7 64bit too load a driver for it, tried them all? Mine is soft bricked and there's no recovery file to restore. getting file not found.
Only shows CMW Based recovery v 5.5.0.4 roach-tf101-r2, also won't see SD card to re flash a rom or recovery.img, seems everywhere I turn I hit a wall on getting it back to working again, just hangs on Asus Logo?
please help? do I need to use a terminal program? is there a way to force a driver to load and see it long enough to reimage?
Thanks tons for any help.:crying:
Click to expand...
Click to collapse
Same problem here... Tried Naked Driver and still got nothing. The Tablet just won't get recognized by the computer (Windows 8.1).
Did you have any luck unbricking it?
I've been through soft bricks before but this time, it seems to me that I've hit the bottom... I just can't think of anything else... any help??
had this problem for 2 years now. started off off like that, now it doesnt recognize at all. if it's rooted, flash a recovery using a terminal emulator. (there are instructions on team win's website on how to flash it to the appropriate block). then, just install a ROM with twrp. mine is in a permaloop. wiping data, rebooting, doing it again. if you get it to work, don't tinker with it any more. that's from my experience.
Sent from my LG-LG870 using Xparent Blue Tapatalk 2
tf101
hi, my asus tf101 has a same issue,my laptop don't recognized my asus,i dont know if the problem is in the cable or what,.i tried already what i saw in youtube but nothing happen.,the sdcard slot is not working,i used cwm v5.8.1.8 touch ,.but i want to change it into original stock version..now ,im working on how my device will recognize...is there a solution to bringback the original recovery base without using computer?..thank you..
---------- Post added at 03:08 PM ---------- Previous post was at 03:04 PM ----------
fabioporto said:
Same problem here... Tried Naked Driver and still got nothing. The Tablet just won't get recognized by the computer (Windows 8.1).
Did you have any luck unbricking it?
I've been through soft bricks before but this time, it seems to me that I've hit the bottom... I just can't think of anything else... any help??
Click to expand...
Click to collapse
got a same issue here,with my asus tf101,i regret to changed my recovery base into cwm touch v5.8.1.8.. it didn't show my ext sdcard file to change it again..i want to bring back the old one..but i don't know how..please please please..need help..
---------- Post added at 03:13 PM ---------- Previous post was at 03:08 PM ----------
James130201 said:
hi. if you cannot enter apx mode. try flashing a new rom of the tf101 or reflashing your current recovery
Click to expand...
Click to collapse
hi sir,..i have the same problem above,.my data cable doesn't work ..the cwm i used now doesn't show my ext sd card,.only clockworkmod file,.is it possible to flash the old rom without computer?..how..please reply ,..thanks,
Don't wanna be the bearer of bad news but, I gave up trying to recover that thing a long time ago buddy. My advise to you would be: let go of it. The way I see it, the only way you could do it would be if you could replace the connection port and regain access to you tablet through you computer - considering the problem is being caused by that port.
Another way of doing that would be if you could actually have access to the tablet's internal storage and then place a ROM there so you could flash that using CWM.
Those are the only two options I didn't try, and now I can't, since I gave mine away to someone I thought could try one of those things, but not even an eager 17 year old boy could do it.
So, good luck with that.
Hi
TF300T JB 4.2.1
Bought new in the US in 2013 so has US SKU. Originally for my wife, but she now has an iPad Pro so I've got the hand-me-down!
Wiped it and unlocked the device successfully using the Asus V8 utility. Tried to flash TWRP from Win7 computer but something went wrong. The interface was still there, it would boot up okay but there was no sign of TWRP. Eventually, I went into fastboot and selected RCK. Nothing happened except the icon turned brown and just sat there. Then I tried a factory reset but it wouldn't have any, nor a cold boot. In desperation I turned the device off and tried to reboot. The initial "Asus" screen came up ("This device is unlocked" in top left-hand corner and the 'Nividia Tegra' logo in bottom right. No spinning circle of dots). It won't boot into fastboot, in fact the volume keys are totally unresponsive. On/off will turn off the device, but it immediately boots back to the same Asus screen. It's not recognised by the Win7 computer so I can't flash anything to it. I think I've tried everything this forum (and a few lesser ones!) could suggest, to no avail.
I believe I now have the proverbial 'bricked' tablet.
Nothing daunted, and not prepared to involve Asus support, I'm considering swapping the motherboard (I've done a couple on Windows computers) but will this bring my TF300T back to life, or is there more I need to do?
I'm no expert on the Android OS so any help from you experts would be much appreciated.
Thanks in advance.
Anyone?
I know the TF300 is a bit long in the tooth now, but all I want to know is whether a bricked one can be recovered by replacing the motherboard. There must be someone out there who has done the replacement and can advise me? Also, I apologise if this in in the wrong section, I guess it should have been in the 'Help' section, but I didn't realise until I'd posted it.
capelyddol said:
Hi
TF300T JB 4.2.1
I'm considering swapping the motherboard (I've done a couple on Windows computers) but will this bring my TF300T back to life, or is there more I need to do?
Click to expand...
Click to collapse
Of course, exchange the MB will bring back your device to life. But it is really the last option.
Firstly you have to check patiently if you can get access into your device. Therefore read mindfully this thread:
https://forum.xda-developers.com/showthread.php?t=2396072
"The solution by @Buster99 is for those who:
- flashed the wrong recovery, and wiped data
- are able to boot into recovery, but cannot flash anything
- no adb access (although, if you DO have adb access, this will still work for you...)"
Hopefully my advise will help you! Don't forget to thank @Buster99
ebonit said:
Of course, exchange the MB will bring back your device to life. But it is really the last option.
Firstly you have to check patiently if you can get access into your device. Therefore read mindfully this thread:
https://forum.xda-developers.com/showthread.php?t=2396072
"The solution by @Buster99 is for those who:
- flashed the wrong recovery, and wiped data
- are able to boot into recovery, but cannot flash anything
- no adb access (although, if you DO have adb access, this will still work for you...)"
Hopefully my advise will help you! Don't forget to thank @Buster99
Click to expand...
Click to collapse
ebonit ~ many thanks for your response. Unfortunately, I really don't think there's any way I can get access. The initial boot-up screen is all I get, in perpetual loop. The only way to shut it down is reset with vol-up., though it's possible it may be in some sort of variation of apx mode at this point as the screen is blank. I've no way of knowing as my win 7 computer only acknowledges an 'unknown device' at that point, and nothing when the initial boot screen is there. Vol-down doesn't seem to have any effect at all. Windows has already installed the drivers so won't re-install, or uninstall them as it's 'unknown'. I did once manage to get it recognised as an 'apx device' but with an '!' (not sure how I did it as I haven't been able to replicate it since!) but I don't think that helps me even if I could replicate it without the '!', Nvflash requires I have the necessary back-up files, which of course I don't. I don't know where to go from here except to replace the motherboard. Once I get the device apart I may try disconnecting the battery, vol-down, and reconnect, to try booting to recovery, but I'm not optimistic of that working.
I'll certainly be very happy to consider any other suggestions you, or anyone else, may have.
I tried Buster99's method, but as my TF300T isn't recognised by Windows that was a non-starter.
Once again, many thanks for your input.
capelyddol
(John)
capelyddol said:
ebonit ~ many thanks for your response. Unfortunately, I really don't think there's any way I can get access.
Click to expand...
Click to collapse
I'm sorry, but if you are really sure that you cannot boot into either fastboot or recovery the tablet is bricked for good!
In this case to replace the mainboard will be the last option to get the tablet back to life. There is a very good instruction with pictures by @huebinger that shows you what to do exactly: https://forum.xda-developers.com/showthread.php?t=2368372 (BTW, that's what I did many years ago!!!)
On ebay.com you may find a used one:
https://www.ebay.com/itm/GENUINE-AS...863174?hash=item54321ab206:g:lrcAAOSwjXRXcHSB
ebonit said:
I'm sorry, but if you are really sure that you cannot boot into either fastboot or recovery the tablet is bricked for good!
In this case to replace the mainboard will be the last option to get the tablet back to life. There is a very good instruction with pictures by @huebinger that shows you what to do exactly: https://forum.xda-developers.com/showthread.php?t=2368372 (BTW, that's what I did many years ago!!!)
On ebay.com you may find a used one:
https://www.ebay.com/itm/GENUINE-AS...863174?hash=item54321ab206:g:lrcAAOSwjXRXcHSB
Click to expand...
Click to collapse
ebonit ~ Thanks for the links. I checked out huebinger's and pulled my motherboard out, then bought the one you linked to on eBay. Hopefully, I didn't do any damage getting the MB out. I'm more used to the tough old internal wiring of desktop computers!
I'd already backed up the data and done a factory reset before I began my abortive attempts at rooting so hopefully I'll be starting with a clean slate once I get the new board installed. It's going to take a while to cross the pond to France, but I'll report on how it goes once it arrives.
Thanks again for your help, it's much appreciated.
John.
(capelyddol)
Hello,
My tf300t got bricked while upgrading twrp.
nothing helped, i put away the tablet, after a year i found her ... so i said to myself "why not" ?! so i ordered from ebay a motherboard, and it's work like a charm, but the tablet is old now ;0
now i want to setup a lite rom ....
mitomon said:
Hello, now i want to setup a lite rom ....
Click to expand...
Click to collapse
What do you mean?
What do you mean?
Click to expand...
Click to collapse
I was wondering that, too!
It's good to know the s/h motherboard cured his tablet's ills, though.
My replacement motherboard arrived yesterday and is installed, up, and running.
Android Ver: 4.2.1
Build No: US_epad - 10.6.1.27.5
I downloaded the v8 unlock device app and unlocked the tab.
I've downloaded:
1) djibe Transformer Pad TF300T pack v3
2)KatKiss -7.1_TF300T_029
3) open-gapps-arm-7.1-pico-20180517
I have a 32g microSD formated to FAT32 installed in the tablet.
All as per djibe89's tutorial here: https://forum.xda-developers.com/transformer-tf300t/general/guide-asus-transformer-pad-tf300t-stock-t3554744
My 'versions' are identical with djibe89's except for the BT version which is 11.38, not 10.38. Hopefully that'll not affect anything!
At this point I run into problems:
1) My USB link between the win 7 (32-bit) computer and the tablet is iffy. Sometimes it works for a while, but I frequently get the "USB device Not Recognized" with a useless MS message not worth clicking on. I'm wondering if there's a more reliable way to transfer files? Airdroid, possibly? Losing connection during file transference doesn't bear thinking about.
2)
Go to folder /Universal Naked Drivers 0.72 you unziped at start on your Desktop.
Select file android_apxusb.inf, then right click -> Install.
Force driver install and wait until a success message prompts.
Repeat operation with android_winusb.inf .
Click to expand...
Click to collapse
I tried installing these drivers by both right-click-> Install and also CMD. -to no avail. I get a Windows message saying the best drivers for the device are already installed, but the tab still isn't recognized. Oh, yes it is! Ooops, now it isn't! ad infinitum, I'm guessing.
Can anyone advise how to overcome this or I can see myself keeping the used motherboard salesmen in Mercedes for the next decade! :crying:
3) Assuming I can overcome the iffy USB problem: should I use TWRP Kang 2.8.7.2 or TWRP 3.2?
I guess that's enough problems for now. I hope ebonit or some other expert can assist with this as I really want to get this tab rooted.
Thanks
John.
(capelyddol)
capelyddol said:
My replacement motherboard arrived yesterday and is installed, up, and running.
Android Ver: 4.2.1
Build No: US_epad - 10.6.1.27.5
Click to expand...
Click to collapse
Congratulations! You did a good job. Thanks for your report.
First of all, to avoid any issues to get your device on N 7.1 Nougatella please follow exactly Tim's install instruction step by step in post #1. https://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702
You need Kang TWRP as advised by Tim. Don't forget to format data through Kang TWRP before. It takes up to one hour. Then change file system to F2FS for data only no cache and system. Successfully done your device is now ready to install Rom, pico Gapps and SuperSU fresh downloaded via Tim's links there.
PS: About your USB issue take another USB port on your PC not via hub!
Good luck!
Three days with nothing from me, you'd be excused for thinking either I was dead, or my tab was! Thankfully, neither. In fact - SUCCESS!!! We're both alive and well, and for the tablet at least, performing better than ever.
TWRP installation took me two days. First, the computer (Win 7 32-bit) refused to recognize the TF300T and 'fastboot' could have been renamed 'nerverboot'. Strangely, the whole business seemed to evolve over time. Persistence was the name of the game - trying different USB ports, booting and rebooting (both tab and desktop). Eventually I found Snoop05's '15 seconds ADB Installer v1.4.3' https://forum.xda-developers.com/showthread.php?t=2588979 and with that I began to make progress...slowly!
Code:
fastboot devices
returned '???????????????' over and over again. By uplugging/plugging the cable into the tablet a few times I suddenly got a nice long string of letters and numbers. It came and went a few times but after a while seemed to stabilize till I felt ready for the big push of TWRP. I got so many error messages: 'can't find twrp.img' (I'd renamed it); 'can't open twrp.img'; 'insufficient memory', etc, etc.. Suddenly, it worked. It took just over eight seconds to download the 6.95MB. Booting into recovery was rather heart-stopping, but it came up a treat.
After that it was relatively simple to set up the TWRP (I found Djibe89's guide https://forum.xda-developers.com/transformer-tf300t/general/guide-asus-transformer-pad-tf300t-stock-t3554744 especially useful and there's a copy in the -djibe Transformer Pad TF300T pack v3' http://bit.ly/djibe-tf300t-v3.
Flashing KatKiss 7.1_TF300T_029, open_gapps-arm7.1-pico, and SuperSU-v2.82 from the microSD I'd copied them to went like a dream and before I knew it the old tab was humming with life once more. I'm a very happy chappy!
I have just two queries (so far ) 1. djibe89 mentions the file 'deviceID.apk' but Tim doesn't. Is it still necessary? I believe it's to keep Google happy, but I've no problems downloading from the Play Store, so I've not installed it as yet.
2) While installing the 'Battery Calibration' app it briefly stated that the tab wasn't rooted. I assume if I've achieved all the above, then it must be?
Now I'm going to play. No doubt I'll be back with a few more queries before too long!
Special thanks to ebonit for his help and support.
capelyddol said:
My replacement motherboard arrived yesterday and is installed, up, and running.
Android Ver: 4.2.1
Build No: US_epad - 10.6.1.27.5
I downloaded the v8 unlock device app and unlocked the tab.
I've downloaded:
1) djibe Transformer Pad TF300T pack v3
2)KatKiss -7.1_TF300T_029
3) open-gapps-arm-7.1-pico-20180517
I have a 32g microSD formated to FAT32 installed in the tablet.
All as per djibe89's tutorial here: https://forum.xda-developers.com/transformer-tf300t/general/guide-asus-transformer-pad-tf300t-stock-t3554744
My 'versions' are identical with djibe89's except for the BT version which is 11.38, not 10.38. Hopefully that'll not affect anything!
At this point I run into problems:
1) My USB link between the win 7 (32-bit) computer and the tablet is iffy. Sometimes it works for a while, but I frequently get the "USB device Not Recognized" with a useless MS message not worth clicking on. I'm wondering if there's a more reliable way to transfer files? Airdroid, possibly? Losing connection during file transference doesn't bear thinking about.
2)
I tried installing these drivers by both right-click-> Install and also CMD. -to no avail. I get a Windows message saying the best drivers for the device are already installed, but the tab still isn't recognized. Oh, yes it is! Ooops, now it isn't! ad infinitum, I'm guessing.
Can anyone advise how to overcome this or I can see myself keeping the used motherboard salesmen in Mercedes for the next decade! :crying:
3) Assuming I can overcome the iffy USB problem: should I use TWRP Kang 2.8.7.2 or TWRP 3.2?
I guess that's enough problems for now. I hope ebonit or some other expert can assist with this as I really want to get this tab rooted.
Thanks
John.
(capelyddol)
Click to expand...
Click to collapse
hi ,
you said that you succeeded to unlock the tablet ?
how ?!
i tried with unlocker v7 and 8 , i got the network error.
my tf330t is on 4.2.1.
i try hard reset, nothing helped.
i changed the mb, succeeded to root with motochopper.
please , i need help.
thanks
mitomon said:
I tried with unlocker v7 and 8 , i got the network error. My tf330t is on 4.2.1.
Click to expand...
Click to collapse
To avoid any issues please reinstall your system by doing a Buster99 https://forum.xda-developers.com/showpost.php?p=44244313&postcount=12. Be sure you have the latest firmware "WW_epad-user-10.6.1.27.5"
After that delete your Google account. Then you may unlock your device with V7.
capelyddol said:
TWRP installation took me two days. Eventually I found Snoop05's '15 seconds ADB Installer v1.4.3' https://forum.xda-developers.com/showthread.php?t=2588979 and with that I began to make progress...slowly!
Click to expand...
Click to collapse
Hope you have Kang TWRP now as required by Tim in post #1!
I'm sorry, but you never mentioned that you cannot access your Tablet via ADB. Therefore please note, the best ADB tool, every Android user may have on his PC, is "Minimal ADB & Fastboot" https://forum.xda-developers.com/showthread.php?t=2317790.
BTW, the answer to your first question is nope, you don't need it. The answer to your second one is yes the device is rooted. However check the update status of your SuperSU. Hope you did fresh download Rom, Apps and SuperSU via Tim's links in post #1 of the Nougatella thread?
I have installed Kang TWRP 2.8.7.2 as per Timduru's link. My tab was wiped before installation so all apps were fresh downloads. SuperSU was 'UPDATE-SuperSU-v2.82-20170528234214.zip' again, as per Timduru's link, as was the ROM ' KatKiss-7.1_TF300T_030.zip'. Many thanks for pointing me to 'Minimal ADB & Fastboot' which I've now installed for future use. And many thanks for all your other help. No doubt I'll be back for more!
capelyddol said:
My tab was wiped before installation so all apps were fresh downloads. Many thanks for pointing me to 'Minimal ADB & Fastboot' which I've now installed for future use. And many thanks for all your other help. No doubt I'll be back for more!
Click to expand...
Click to collapse
You are welcome! It's good to hear that you did such a good job. Using the thanks button is always greatly appreciated.
Please note, if you have any issues or you are changing the Android system, Format /data through Kang TWRP is always required. Format /data is more than wipe (you did wipe!) or factory reset. It takes up to 1 hour to be successfully. After that your system is really clean.
"Warning: formatting will remove what is stored in your internal storage, so store the rom /gapps/supersu zips onto an external storage (microSD, SD card..) or make sure you know how to push them back through adb." advised by Tim in post #1.
Hi,
Yes, I know, there's a million topics about this and I'm pretty sure I tried them all!
Long story short: been running Lineage OS on my Tab 2 for a while but it's been sitting in a drawer. Saw a video about using old tablets for emulating retro consoles and the Tab works a dream for that. So I bought a Bluetooth controller for better gameplay but it just wouldn't work under Lineage so thought I'd flash the original ROM back onto it to see if that would work. I'm not a n00b, but haven't done it for a while so thought to be safe I'd follow a guide. All seemed to be working well when Odin crashed and left me with the Firmware Upgrade Failed error.
I've been trying for about four hours to get it back, but having no luck. I've tried the latest version of Odin, as well as the old 1.7 version I was using; tried Kies, tried uninstalling Kies; tried uninstalling the stock drivers MS installed when connected, no go. Interestingly Odin doesn't seem to see the Tab at all now, so I tried the UniversalADB installer, tried installing ADB drivers as well as Samsung drivers manually, but nothing works, it just sits at "connecting" but never actually does. Also tried different stock ROMs to no avail. I think my issue is with the ADB drivers, just don't know how to fix it.
I don't know what to try now. Any advice?
Using MS Surface Pro (2017) running Win10.
Not allowed to post screenshots, but do have some.
Thanks.
How is the tab behaving after this crash?
Can you use the tab as usual? But you are still in LineageOS? If Yes, what version of LineageOS?
Can you still get into Recovery Mode? If Yes, what Recovery and version do you have?
Download Mode seems Ok, but not Odin at the PC end. Correct?
The more info you can give the better. Also if you prepared the tab in any way other than just entering download mode.
Did you enable USB Debugging for example? (but I'm not sure how important that is)
Or wiped anything in recovery?
I'm not sure if I can help, but surely there must exist someone here that can. I'm new to the android world, but used to work in IT Support and Network Administration.
And 100 years ago I blogged with Blogger, but sat and amended the xml-file to get the design I wanted more than creating blog entries
Anyway, I hope it gets sorted.
Tab_Triggerhappy said:
How is the tab behaving after this crash?
Can you use the tab as usual? But you are still in LineageOS? If Yes, what version of LineageOS?
Can you still get into Recovery Mode? If Yes, what Recovery and version do you have?
Download Mode seems Ok, but not Odin at the PC end. Correct?
The more info you can give the better. Also if you prepared the tab in any way other than just entering download mode.
Did you enable USB Debugging for example? (but I'm not sure how important that is)
Or wiped anything in recovery?
I'm not sure if I can help, but surely there must exist someone here that can. I'm new to the android world, but used to work in IT Support and Network Administration.
And 100 years ago I blogged with Blogger, but sat and amended the xml-file to get the design I wanted more than creating blog entries
Anyway, I hope it gets sorted.
Click to expand...
Click to collapse
Hi,
Thanks for your reply and sorry it's taken me so long to respond; I've got several health issues I have to work around!
I can't get into the OS at all, it's just stuck at the "Firmware upgrade..." screen and there's nothing else I can do with it.
It was rooted and I was running TWRP recovery, but can't access it at all now. I did a wipe in TWRP but was still able to boot into it before I ran Odin. Odin worked fine, then it just stopped for reasons unknown and now there's nothing I can do with the Tab at all.
I see this in Device Manager: samsung mobile usb cdc composite device. Have tried manually installing driver but nothing seems to work.
Have tried it on my Mum's Win7 machine, but to no avail. I really need ADB drivers but I can't install them without turning on debugging on the Tab and I can't do that because I can't get out of this blasted error screen!
There's literally nothing else I can say about it as this is all that's happening.
Annnnd, now it doesn't seem to want to hold a charge. :crying:
Thanks again.
I've tried following a few tutorials, but I can't get past the ADB issue. Does anyone know of, or can link to, a solution to this please? I really want my Tab back!
Thanks!
Tabby22020 said:
I've tried following a few tutorials, but I can't get past the ADB issue. Does anyone know of, or can link to, a solution to this please? I really want my Tab back!
Thanks!
Click to expand...
Click to collapse
Maybe a longshot, but you can test if this free version can access the tab:
https://www.tenorshare.com/products/reiboot-for-android.html
No use buying if it can't.
But since Device Manager sees something it's worth a shot.
Do you have to longpress power button to turn it off?
If so... when the screen goes off, have you tried to quickly let go of the power button and immediately press it again together with Volume Up?
Or down, for download instead of Recovery.
With my P3100 it was much easier with no charger plugged in...
Edit:
Tried the software and my tab is OK, but no connection established anyway. Only result was that I couldn't access tab in File Explorer and MTP state... only PTP.
In Device Manager I got a new Android Device: Something like Google Nexus ADB... sorry but I uninstalled it directly without noting exact name.
Replugged USB cable and MTP working again.