Welcome to the Frequently Asked Questions for your Asus Transformer TF300T
Click to expand...
Click to collapse
This thread is here to help our community out as best as it can.
Why is this thread here?
There's 2 main reasons really. The first reason is to stop the development threads getting filled with questions which have nothing to do with the thread they're posted in. That then makes the thread go off-topic which is not what a development thread is there for.
The second reason is because there are too many repetitive questions being asked. The main problem with that is the fact that other users will sometimes attack the OP and 'flaming' them.
The main way which this thread will help to stop that happening is by helping you out as much as possible, while being in a friendly environment.
Below you will find the Thread Rules which I expect you all to follow and not to break them.
Thread Rules
1. Remember that while posting in this thread and across the whole site, you must not break the Forum Rules.
2. Even though this thread is for everyone to use, there'll be a lot if new members in here so no flaming or insulting anyone else.
3. As this is a help thread, remember that there is no such thing as a stupid question.
4. Even if you get your question answered by reading the 2nd post, be sure to come back here and read some more. It will help you to learn even more.
Click to expand...
Click to collapse
Hall Of Fame
As I'll be keeping an eye on this thread quite a lot, I'll be adding the people to this list who have been the most helpful and are contributing the most, and we need your help for a good FAQs
Code:
[B][CENTER]
[B]1.[URL="http://forum.xda-developers.com/member.php?u=4518416"][B][COLOR="Blue"] - QuantumFoam[/COLOR][/B][/URL] who is the chief editor of the FAQ
2. - [URL="http://forum.xda-developers.com/member.php?u=2559267"][B][COLOR="Green"]tobdaryl[/COLOR][/B][/URL] - Help provider
3.
4.
5.[/B][/SIZE][/CENTER][/B]
Asus TF300 Moderators
Click to expand...
Click to collapse
If you report any posts, the report will go to our SM (Senior Moderator) and FSMs (Forum Specific Moderators). They are our SM - zelendel and our FSMs - babijoee, chrisd1a1, Divine_Madcat, GODZSON, Moscow Desire, zacthespack . If you have any questions about this forum in particular then feel free to drop them a PM or you can use the button report
XDA In General
Click to expand...
Click to collapse
First of all, I'm linking to some general XDA threads which can help you become more familiar with this site and how things run. I feel this is one thing which new users don't realize because they think it's okay to come to this site and post anywhere.
If you don't feel this applies to you, please move onto the Asus TF300T links further down this post.
The first of all is the Forum Rules, which is the first thread that you must read and implement for taking good time here
The XDA Tour and Report Posts
XDA New User Guide - I can't stress enough how important that thread is. If you follow what that guide says, you'll be well on your way to becoming an asset to the XDA forums.
[HOW TO] Make A Substantial Thread, Post, Question & Poll - This is also a must read thread. Why, you ask? Well it's simple. Reading this will show you the best way to post your thread to ensure that people will respond and be able to help you. Rather than just giving no information or a thread title called "Mah phone brikked. Hlp me plzzz!", following that thread will give you the best chance of being helped.
[HOW TO] Make A Good Signature - This really is needed because as you'll see in a lot of signatures, mine included, is that we list our current devices and what ROM/kernel we are using. This helps people to help us. Take a look at the thread to find out what else to include in your signature.
ASUS TF300T Helpful Links
Click to expand...
Click to collapse
- [INDEX][04 Feb 2013]TF300T & TG-INDEX of Roms/Dev Guides/Kernels/Recoveries/etc.
- [GUIDE]Upgrade your TF300t to Jellybean, recovery, root & remove bloatware[Noobproof]
- (TF300T)For All Your Jelly Bean discussions-problems
- (TF300TG)For All Your Jelly Bean discussions-problems
- Small guide for Install recovery and rooting when you are already to JB
- [GUIDE] Help for flash more faster when you use Fastboot Line Command
- How to install Universal Naked Drivers
In post 2 there'll be an FAQ which will help you out aswell
And don't forget to rate for this thread -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance
Reserved for FAQ
Reserved again
Reserved again
Aaaand I'll take #5
USB ADB Drivers (both OS and Recovery modes)
I have a new TF300T factory ICS 4.0.3.
I was able to setup APX mode and its driver is correctly
installed. The tablet is recognized as an MTP device and the
internal (/sdcard) mount point is reachable.
After enabling setup/developer options/USB debugging,
ADB does not 'see' the device though, adb devices
does not return the serial number.
I'm guessing I need more / different drivers.
I have the 'naked driver 0.72' package, but the
.inf is not setup for 'install' and device manager
update driver says I have the latest driver installed?
Do I uninstall the USB driver ASUS sync installed and
and then install the 'naked driver' package from the
new device wizard?
Thanks
fuzzynco said:
I have a new TF300T factory ICS 4.0.3.
I was able to setup APX mode and its driver is correctly
installed. The tablet is recognized as an MTP device and the
internal (/sdcard) mount point is reachable.
After enabling setup/developer options/USB debugging,
ADB does not 'see' the device though, adb devices
does not return the serial number.
I'm guessing I need more / different drivers.
I have the 'naked driver 0.72' package, but the
.inf is not setup for 'install' and device manager
update driver says I have the latest driver installed?
Do I uninstall the USB driver ASUS sync installed and
and then install the 'naked driver' package from the
new device wizard?
Thanks
Click to expand...
Click to collapse
First some info. Windows thinks it should make the choices about drivers and is designed to keep us from choosing something that might cause problems. We need to maintain control through the process. I just received a window computer last week and had the same issue. This will be a long post but was necessary for me.
Here are the choices I had to use to change my drivers
.
windows-start - in search type device manager and return.
right click on the entry you wish to change the driver for.
Update Driver Software.
Browse my computer for driver software.
Let me pick from a list of device drivers on my computer.
Have Disk
Browse
choose the universal naked drivers directory
click on the proper inf file
windows says not signed; install anyway
using this method you don't have to uninstall your current driver
if you deviate at any step windows will refuse to allow this change
Good Luck!
sigh MTP works but ADB doesn't
tobdaryl said:
First some info. Windows thinks it should make the choices about drivers and is designed to keep us from choosing something that might cause problems. We need to maintain control through the process. I just received a window computer last week and had the same issue. This will be a long post but was necessary for me.
Here are the choices I had to use to change my drivers
.
windows-start - in search type device manager and return.
right click on the entry you wish to change the driver for.
Update Driver Software.
Browse my computer for driver software.
Let me pick from a list of device drivers on my computer.
Have Disk
Browse
choose the universal naked drivers directory
click on the proper inf file
windows says not signed; install anyway
using this method you don't have to uninstall your current driver
if you deviate at any step windows will refuse to allow this change
Good Luck!
Click to expand...
Click to collapse
can'tn test fastboot yet, but guessing when one work both will.
fuzzynco said:
can'tn test fastboot yet, but guessing when one work both will.
Click to expand...
Click to collapse
I'm sorry your screen capture is not large enough to see.
With your tablet unplugged open device manager; now plug your tablet into the computer and you will either see asus adb interface or maybe a driver failure. Either a larger screen capture or try to explain the changes in device manager is needed.
It would be good if I knew the state of your tablet while you are doing this.
My screenshot for adb (at the top ) and data at the bottom.
followup: tf300 adb drivers?
tobdaryl said:
I'm sorry your screen capture is not large enough to see.
With your tablet unplugged open device manager; now plug your tablet into the computer
and you will either see asus adb interface or maybe a driver failure. Either a larger screen
capture or try to explain the changes in device manager is needed. It would be good if I
knew the state of your tablet while you are doing this.
Click to expand...
Click to collapse
Both tablets work normally with their OSes and the supplied apps work as expected.
For the ICS one all I did was set developer options to enable adb, the tablet does display
the icon in the lower right corner, so the 'server' is working. I wanted to experiment
with custom firmware, so I got a new tablet that still has ICS so it can run nvflash
for tf300t.
Normal boot (the ICS tablet is unrooted & locked as it came from factory,
the JB one is rooted, (using OTA Rootkeeper and OTA JB updates),
locked). I have 2 tablets (Black is JB and Blue is ICS).
MTP and APX modes are recognized, neither recognizes ADB
('adb devices' does not return serial number with normal 'desktop'
displayed).
I see code 10 on the ASUS Transformer ADB interface, (with the usual 'exclamation point' error flag).
MTP and APX drivers did install and work as expected. normal OS (either ICS or JB) boot).
As I said, after looking at the content of the .inf file, there is a section for tf101 and tf201
but not for tf300 and tf700, I wondered if that was the issue ? If so, where does one get the
correct tf300t drivers for adb modes and fastboot mode?
http://support.microsoft.com/kb/943104
As usual ASUS support was less than helpful. They tell me there are no ADB drivers
or Fastboot drivers.
While I'm asking, is ICS supposed to support USB mass storage, (on my HTC devices
I'm prompted for USB connection mode, (charge only (used with adb), disk (UMS) or
HTC sync)? ASUS doesn't prompt for UMS or MTP connection modes?
Thanks
fuzzynco said:
Both tablets work normally with their OSes and the supplied apps work as expected.
For the ICS one all I did was set developer options to enable adb, the tablet does display
the icon in the lower right corner, so the 'server' is working. I wanted to experiment
with custom firmware, so I got a new tablet that still has ICS so it can run nvflash
for tf300t.
Normal boot (the ICS tablet is unrooted & locked as it came from factory,
the JB one is rooted, (using OTA Rootkeeper and OTA JB updates),
locked). I have 2 tablets (Black is JB and Blue is ICS).
MTP and APX modes are recognized, neither recognizes ADB
('adb devices' does not return serial number with normal 'desktop'
displayed).
I see code 10 on the ASUS Transformer ADB interface, (with the usual 'exclamation point' error flag).
MTP and APX drivers did install and work as expected. normal OS (either ICS or JB) boot).
As I said, after looking at the content of the .inf file, there is a section for tf101 and tf201
but not for tf300 and tf700, I wondered if that was the issue ? If so, where does one get the
correct tf300t drivers for adb modes and fastboot mode?
As usual ASUS support was less than helpful. They tell me there are no ADB drivers
or Fastboot drivers.
While I'm asking, is ICS supposed to support USB mass storage, (on my HTC devices
I'm prompted for USB connection mode, (charge only (used with adb), disk (UMS) or
HTC sync)? ASUS doesn't prompt for UMS or MTP connection modes?
Thanks
Click to expand...
Click to collapse
The universal naked drivers work properly for our unit even though they are not marked as such.
Asus MTP, go to settings/storage and select (in my case) three dots in the upper right(options). This will give you usb computer connection, click that, place a check beside MTP.
Your device manager entry with code 10 is where you use the directions I provided earlier to install universal drivers. While you were away I made a post in general with screen shots that may help.
Uptate:
I forgot fastboot. The tablet will only present the fastboot interface to your pc when you are in fastboot mode. From bootloader menu volume down to the usb symbol and volume up to select. This is only available after you unlock!
progress ADB for JB works, ICS doesn't.
tobdaryl said:
The universal naked drivers work properly for our unit even though they are not marked as such.
Asus MTP, go to settings/storage and select (in my case) three dots in the upper right(options). This will give you usb computer connection, click that, place a check beside MTP.
Your device manager entry with code 10 is where you use the directions I provided earlier to install universal drivers. While you were away I made a post in general with screen shots that may help.
Uptate:
I forgot fastboot. The tablet will only present the fastboot interface to your pc when you are in fastboot mode. From bootloader menu volume down to the usb symbol and volume up to select. This is only available after you unlock!
Click to expand...
Click to collapse
Since neither tablet is currently unlocked I'm just trying
to get 'adb devices' to return the serial number in normal
OS boot mode. With the tablets in APX mode, Windows
Device Manager does see the APX driver correctly.
After updating the driver per your instructions, Windows 7
+ JB works, Windows 7 + ICS does not.
Windows 7 Pro '"see's" the Jellybean TF300T ('adb devices' responds with device serial number)
That tablet is running 4.1.1 (OTA JB) started life as 4.0.3 and was rooted without unlock while
on ICS, OTA Rootkeeper saved, JB OTA updated, OTA Rootkeeper restored root successfully.
The new ICS tablet that has nothing other than USB debugging turned on, is not seen on the same
Windows 7 Pro that see's Jellybean fine. I'm puzzled, if JB is seen properly, the driver is installed
correctly, right?? Unless there is factory defect in the new tablet, what else might cause different
behavior for ICS vs JB firmware, with the same driver?
Thanks
fuzzynco said:
Since neither tablet is currently unlocked I'm just trying
to get 'adb devices' to return the serial number in normal
OS boot mode. With the tablets in APX mode, Windows
Device Manager does see the APX driver correctly.
After updating the driver per your instructions, Windows 7
+ JB works, Windows 7 + ICS does not.
Windows 7 Pro '"see's" the Jellybean TF300T ('adb devices' responds with device serial number)
That tablet is running 4.1.1 (OTA JB) started life as 4.0.3 and was rooted without unlock while
on ICS, OTA Rootkeeper saved, JB OTA updated, OTA Rootkeeper restored root successfully.
The new ICS tablet that has nothing other than USB debugging turned on, is not seen on the same
Windows 7 Pro that see's Jellybean fine. I'm puzzled, if JB is seen properly, the driver is installed
correctly, right?? Unless there is factory defect in the new tablet, what else might cause different
behavior for ICS vs JB firmware, with the same driver?
Thanks
Click to expand...
Click to collapse
It is very possible that adb will not work properly on ICS unless it is unlocked. I can't remember but would say it is very likely since JB does work and both use the same drivers. In two days I was unlocked, on the latest JB, twrp installed and waiting for a non stock based rom.
There are some differences between JB and ICS. I received ICS input from wha2do concerning methods of entry into apx and bootloader while I was gathering info to update my thread. Here are the ones we identified.
or - no need to hold volume with these
8. adb reboot bootloader
or
9. fastboot -i 0x0B05 reboot-bootloader
or
10. from terminal - you must be rooted for this to work
su
reboot bootloader
Note 1: If you have nvflash installed some of the commands presented in this post may not work; possibly 8, 9, and 10 - THANKS TO wha2do for this info!
I need to update my info to: If you have ICS or Nvflash.
I think you are ok but give adb another try on ICS when you unlock and if you have problems let me know.
OK - 1st try will be unlock and attempt adb again
I think you are ok but give adb another try on ICS when you unlock and if you have problems let me know.
Click to expand...
Click to collapse
on ICS tablet
Do the locked root process
OTA Rootkeeper save
Unlock ICS bootloader
test fastboot devices
test adb devices
(if ok)
adb backup
fastboot flash recovery
boot to recovery
test adb devices (in recovery mode)
nandroid backup
Hopefully everything will work as it should
if everything else worked I can try nvflash backup process
*sigh* I hope it works
fuzzynco said:
on ICS tablet
Do the locked root process
OTA Rootkeeper save
Unlock ICS bootloader
test fastboot devices
test adb devices
(if ok)
adb backup
fastboot flash recovery
boot to recovery
test adb devices (in recovery mode)
nandroid backup
Hopefully everything will work as it should
if everything else worked I can try nvflash backup process
*sigh* I hope it works
Click to expand...
Click to collapse
Good list and order. I'm always in favor of getting adb and fastboot working properly before going forward. If you experience problems you have done everything possible to give yourself a path to recovery.
Let me know If I can help further.
Good Luck!
Be positive! It's going to work!
Just take your time and try to stick to your list.
Note: do not use WIPE DATA on the bootloader menu!!!
Note: do not use WIPE DATA on the bootloader menu!!!
Note: do not useWIPE DATA on the bootloader menu!!!
Click to expand...
Click to collapse
You know, I've often wondered why that is even there,
The right place to do 'wipes' is in a custom Recovery,
where there is an OS controlling the device mounts
and unmounts. The boot loader is more or less like
a PC's BIOS, while it can do it, its too early in the
boot process for it to have the right understanding
about whats happening in the devices setup, to
do it safely and properly.
fuzzynco said:
You know, I've often wondered why that is even there,
The right place to do 'wipes' is in a custom Recovery,
where there is an OS controlling the device mounts
and unmounts. The boot loader is more or less like
a PC's BIOS, while it can do it, its too early in the
boot process for it to have the right understanding
about whats happening in the devices setup, to
do it safely and properly.
Click to expand...
Click to collapse
+1
Thanks for the explanation.
how to unlock bootloader please?
I just received my asus t300 and updated all the software OTA so it is now on stock Jelly Bean. I have read in a few places saying use the ASUS bootloader unlocker but it was for ICS i believe. I have read posts of the asus unlocker bricking devices that have JB installed and I don't want to be one of those people. Please point me in the right direction on how to safely unlock the bootloader so I can root and try out a faster ROM. I have rooted my cell phones (note2, gsIII) all day long but for some reason I can't find the start of the "bread crumb" trial for this device.
Thanks!!!
Q
quantum3 said:
I just received my asus t300 and updated all the software OTA so it is now on stock Jelly Bean. I have read in a few places saying use the ASUS bootloader unlocker but it was for ICS i believe. I have read posts of the asus unlocker bricking devices that have JB installed and I don't want to be one of those people. Please point me in the right direction on how to safely unlock the bootloader so I can root and try out a faster ROM. I have rooted my cell phones (note2, gsIII) all day long but for some reason I can't find the start of the "bread crumb" trial for this device.
Thanks!!!
Q
Click to expand...
Click to collapse
Quot from Asus: ※This tool now only works with TF300T ICS & JB of TW,US,WW CN SKU. It won’t work on other devices.
Register your unit with Asus, log into play store, run the unlocker. The bricks I have seen unlocking have been caused by WIPE DATA on the bootloader/recovery menu. Never use that!
Note: I failed to add this link earlier. This is good simple directions for unlock.
I'm not sure how to search for my problem, but I can try to describe it
all of my root directory has been moved into a folder called 0, and now there are just some random folders in the new root directory
I recently unlocked my bootloader and flashed twrp, and I made a recovery image at that point.
Then I flashed CM10.1
Then I decided not to use CM10.1 , so i tried to restore from the recovery image
So now thats where I am, and I am trying to root it now.
The default root directory that i had previously placed the CM10.1 zip is in the folder 0, and it wouldnt read any zips i placed in the regular root directory.
So if i place the root-signed zip into the regular root directory, it doesn't read it.
It does read it if it is in the same directory as the CM10.1 zip, or the folder called 0
I flashed the zip, and it didnt seem to do anything.
I may have not done a certain step during the recovery or restoration process, but I was pretty sure to wipe cache before flashing stuff, and I reset to factory before flashing CM10.1
So the main problem I am having now is that I am unable to be rooted.
Im sorry this is horribly worded >.<
any help would be greatly appreciated!
i have posted earlier about my problem @ http://forum.xda-developers.com/showpost.php?p=53643114&postcount=747 and @ http://forum.xda-developers.com/showthread.php?t=2795429 and the XDA assist thread was closed so i am having to post here with more info.
i did search for "MT6572" on xda forums for any possible recoveries that might work, but now the only way i can use this tablet is via fastboot.
it doesnt have any recovery or a stock ROM.
further info about the brand and tablet:
their website www.kulala.hk ,
i have submitted query on their also and tried to contact the office in Dubai, UAE where i am located but non are operational no more. so this forum is only place i can get any help with this tablet.
i just want to get this tablet working again any rom will do
thanks.
I've found these threads for your model:
Android Development and Hacking > Android General > [TUT] MTK Root and CWM Guide (Really Easy)
Android Development and Hacking > Miscellaneous Android Development > [PORT] [TOOL] Carliv Touch Recovery for MediaTek devices
Hope it's a solution for you
philos64 said:
I've found these threads for your model:
Android Development and Hacking > Android General > [TUT] MTK Root and CWM Guide (Really Easy)
Android Development and Hacking > Miscellaneous Android Development > [PORT] [TOOL] Carliv Touch Recovery for MediaTek devices
Hope it's a solution for you
Click to expand...
Click to collapse
i dont have adb access no more only way is fastboot i downloaded the CTR but it needed adb access i am not able to use that.
We are not a support forum, but I can tell you that if you can use fastboot, you can use ADB
Go here and follow my guide which is for Nexus 7, but you can use it for all devices
FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND and FILES
and this => [GUIDE][30/10/2013]New To Adb And Fastboot Guide
philos64 said:
We are not a support forum, but I can tell you that if you can use fastboot, you can use ADB
Go here and follow my guide which is for Nexus 7, but you can use it for all devices
FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND and FILES
and this => [GUIDE][30/10/2013]New To Adb And Fastboot Guide
Click to expand...
Click to collapse
i do have those tools/folders (platform tools), but it wont work with adb, here i have taken screenshot to show.
when i was able to boot into stock rom i could turn debugging on and get adb working but now without a rom and just fastboot access only i am stuck.
I can suggest you this links => [Guide] Use your tablet/phone as PC for Fastboot and ADB
Update:
I located the distributor for KULALA brand here and visited their office and they reflashed with stock rom and its working normal now.
I will try to up the system dump or if anyone can guide how i should make a copy of that stock rom so it could help anyone else to use as well. Last time did copy of a stock rom was via adb using MTKDroid Tools and chose the backup option and it made a folder in mtkdroid tools folder of it. If thats how its done ill make a copy and post here.
Thanks for the help.
Ok and good luck
Thread closed
I wasn't sure where to post this, as the only Blackview-related subforum is for one of their phones... Anyway, I recently bought Blackview Tab 8 (a 10" tablet), and I'm quite pleasantly surprised about its quality (even the box is almost wooden-like ) and the fact that they give you basically everything you need in the package (unlike some manufacturers who keep taking away things season by season...). Also, pure Android without any bloatware - there were a couple of games and apps I don't really need, but they can all be easily uninstalled, or at least disabled (the latter didn't reappear so far, I hope it stays that way).
Three questions for now:
- Any idea which ADB drivers should I install to be able to use adb on this device? I already have three on my Windows 7 computer from before, but connecting this device to the computer didn't find a suitable one.
- How can I remove the "silhouette" of Google Search widget/box on the home screen (other than the workarounds such as changing the launcher, or moving icons to a secondary page and leaving the silhouette alone)? It just stays there after disabling Google/Assistant/etc apps, but doesn't do anything and it can't be moved. I had a similar issue in the past (I think it was a Chuwi tablet).
- How can I tell if the device can be connected to an external display via USB-C to HDMI adapter?
Google's ADB & Fastboot drivers basically are both device and Android OS version independent. However how they got implemented by OEM/Carrier is different. Also in most cases it's required to install an additional "Android USB Driver" provided by OEM/Carrier to make ADB and/or Fastboot flawlessly work.
A link to an ADB / Fastboot installer is to be found in my signature.
I think I actually need those "additional drivers". From what I can see your script downloads what I already have (from platform-tools). adb.exe doesn't show any devices, though. The exclamation marks in Device Manager are at "ADB Interface" and 3x "Unisoc Phone".
Neuromancer said:
I think I actually need those "additional drivers". From what I can see your script downloads what I already have (from platform-tools). adb.exe doesn't show any devices, though. The exclamation marks in Device Manager are at "ADB Interface" and 3x "Unisoc Phone".
Click to expand...
Click to collapse
Here you go:
Unisoc / Spreadtrum SPD drivers for Windows (SCI & USB)
Its important to install SPD drivers else Spreadtrum flash tools like Research Download, CM2 SPD etc won't be able to detect the phone. This is a collection of unsigned (.inf) drivers to be installed
forum.hovatek.com
I tried
Spreadtrum SCI Android USB drivers
Spreadtrum Drivers
SCI android usb driver jungo v4
SPD drivers 2018 ver2.0.0.131
but none of them worked.
In the end, I was able to make it work using these drivers:
How-to install SPD Driver R4.20.0201 (Easy Guide)
Step-by-step guidelines to download and install SPD Driver R4.20.0201 on Windows Computer to connect SPD/Unisoc Devices.
gsmusbdriver.com
But truth be told, I'm not sure if that was the only requirement (because there were also remnants from previous manual install from the link jwoegerbauer provided).