OK guys I have an issue
I now own a tf101 the issue I'm having is a connection issue
I recently purchased my tf101 used as a bargain price as our families 2nd tablet
The lady reset to factory before I purchased
After a couple days I began looking into rooting as an option to restore some functionality to this older tablet when connecting to my computer, I wasn't receiving any notification it was plugged in .... no new device detected ... no sounds..... nothing in device manager
It charges fine... and its an official Asus cord ( least it says Asus on it)
I also got the 40 pin to USB converter and it transfers data from a flash drive to the tablet fine movies pics etc...
I tried the cord on 3 different PC's, and 2 Macs nothing
Tried downloading and installing Asus sync and naked drivers neither helped
(Gonna get my friends cord this weekend see if it does anything)
I also tried most of all of this stuff in USB debugging mode , and toggling sync tool, as well in and not in apex mode
I tried a j5 wormhole USB to USB cord from the 40 pin converter still nothing...
I've read post after post about this topic however NONE have solutions
I had a friend suggest that it may have been rooted before she factory reset it and something got corrupted...
Some other info I'm sure I'll get asked about
Firmware version IML74K.US_epad-9.2.1.27-20120615
Kernel version 2.6.39.4 [email protected]#1
Android version 4.0.3
Whenever I try to boot into any kind of recovery it shows a belly up android with red exclamation mark
Any help would be appreciated
Anyone know if I can root from usb
Same USB Connection Problem
I recently reset my tablet to "factory" and had the exact same issue. Probably searched all the same sites and found the same results you have already seen. "Buy a new cable." "Buy a new tablet."
I used Baiduroot to get temporary root and install TWRP. Unfortunately, I had to download it from a Chinese server and the app is in Chinese, so you are really guessing as to the use of the tool. I poked around till I got it.
So now I can boot into recovery, but have not yet attempted flashing a ROM such as KatKiss.
Rooted, Bootloader, and Flashed
I took courage and flashed. I now have a TF101 with Katkiss 4.4.2 and Gapps running. All done without the cable. In fact, I just plugged it into my computer and it still doesn't recognize it. This is a weird problem.
Bradley Norris said:
I recently reset my tablet to "factory" and had the exact same issue. Probably searched all the same sites and found the same results you have already seen. "Buy a new cable." "Buy a new tablet."
I used Baiduroot to get temporary root and install TWRP. Unfortunately, I had to download it from a Chinese server and the app is in Chinese, so you are really guessing as to the use of the tool. I poked around till I got it.
So now I can boot into recovery, but have not yet attempted flashing a ROM such as KatKiss.
Click to expand...
Click to collapse
My tablet got stuck on the boot screen (a 'bootloop') and so I downloaded the Swedish instructions, tools and firmware image files from the manufacturer's website. I installed the driver on my laptop, connected the tablet, flashed the latest firmware and got it working. Annoyingly, the Chrome browser would not work whatever I did, and eventually I tried to flash an older firmware image onto the tablet. This killed it completely. The screen shows nothing at all; you can just about tell that the backlight has come on due to a dim glow, but the screen is still blank.
The worst thing is that the laptop no longer detects that the tablet is connected to it. It does not even report it as an unknown device. This is what really worries me.
I've read other threads on this forum where Flashtools is advised for bricked phones, but will this work with a tablet where the computer cannot even detect the device is attached?
Any help will be much appreciated many thanks.
Go to a repair shop is the only solution
i can do any thing except damaging your device. GOD DOES NOT DO THAT
Pay1 said:
My tablet got stuck on the boot screen (a 'bootloop') and so I downloaded the Swedish instructions, tools and firmware image files from the manufacturer's website. I installed the driver on my laptop, connected the tablet, flashed the latest firmware and got it working. Annoyingly, the Chrome browser would not work whatever I did, and eventually I tried to flash an older firmware image onto the tablet. This killed it completely. The screen shows nothing at all; you can just about tell that the backlight has come on due to a dim glow, but the screen is still blank.
The worst thing is that the laptop no longer detects that the tablet is connected to it. It does not even report it as an unknown device. This is what really worries me.
I've read other threads on this forum where Flashtools is advised for bricked phones, but will this work with a tablet where the computer cannot even detect the device is attached?
Any help will be much appreciated many thanks.
Click to expand...
Click to collapse
Yes, as @droid_god said the only way is a repair shop because they use those jtag devices to fix your phone.
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 all, i'm trying to get Magisk to install, but seem to have a problem i can't find anything on.
I have read all the guides, read the whole tread on Magisk for our phone, without finding any solution.
I have tried 3 different cables, the one that came with the phone, a cable from my LG v30 and a third party really thick one.
All these cables have been tried on 3 different PCs, a HP G3 probook, a Surface Pro 3 and some kind of Dell desktop, all running updated versions of W10 home, pro and enterprise.
I have tried with samsungs usb drivers, all versions 1.5.51.0 and 1.5.63.0 on all PCs with all cables.
The obious fault here is Odin, 3.12.3, 3.13.1 and 3.13.1_patched (for S10). It's stuck on File Analysis.
So when i checked how its connected, while booted up and not in download mode, it says its using USB for transferring files, which works just fine, and shows up the correct way. Samsung SmartSwitch also works fine.
the problem seems to be the "USB controlled by" with the setting "Connected Device". all i get is the error: "Couldn't switch". I have reinstalled and wiped numerous times. Always the same result. OEM unlocking is on, dev tools are on etc etc.
Do anyone have anything other than what the guides tell you to try?
I had the same problem so it turns out that i didnt have windows media feature pack, because i installed N version of windows. it's free on microsoft website.
I'm in the same situation. Some time ago I needed this function to install a new rom from Samsung, the global one (mine was a carrier locked rom which tooked ages for update). So, now I need it again in order to use an app that needs an adb command via PC and I just can't make it work. I remember that time it worked after the permission showed up on screen, but now I'm not lucky. Hope U find it if still in need of it.
odin stuck [quit]
Echuz said:
Hi all, i'm trying to get Magisk to install, but seem to have a problem i can't find anything on.
I have read all the guides, read the whole tread on Magisk for our phone, without finding any solution.
Do anyone have anything other than what the guides tell you to try?
Click to expand...
Click to collapse
Likevise :crying:
Same happened to me couple of times.
Messed with odin ... Odin has sometimes quit at the end ...
Messed up big times ... bootlops ...
Have finaly bring it back from dead & bootloops ... It's almost 17th time ..., but this time it was harder ...
Always the same result. OEM unlocking is on, dev tools are on etc etc.
Same.
But last stuck bring back dev tools locked, only OEM unlocking on.
Check almost everything, boot only AP (modified tar).
Have messed big time with md5 reconstuction as in the original tar regarding md5.
Hava also tried reflash PIT ...
After 5 hours back on line ...
Are you on latest ASIG ?