[X]Assistant

[Armstell]

Asus Eee Pad Transformer TF300 - Firmware
TF300T, TF300TG

Description | Discussion пїЅ | Purchase пїЅ | Accessories пїЅ | User club пїЅ | Embellishments пїЅ | FAQ | Firmware пїЅ | Ubuntu Touch Firmware пїЅ | XDA-developers

Important information

From the drain to the current firmware

What firmware to choose? - See the latest survey in the archive.

пїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅ - пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅ download

пїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅ пїЅпїЅпїЅпїЅ. пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅ пїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅ пїЅ пїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅ.

For your own good it is recommendedmake NVFLASH backupbefore installing custom! Without it, you have a chance to fly into an expensive repair in the service center and lose all data on the tablet in case of incorrect actions when flashing the device. The NVFLASH manual is in the section"Instructions".

Drivers, utilities

Drivers

ASUS_Android_USB_Drivers.zip(8.28 MB)
Universal_Naked_Driver_0.72.zip(8.28 MB)
ADB_Fastboot.rar(477.14 KB)

• ADB Driver for Recovery
  
• Correct installation of drivers

Utilities

• Android SDK Tools
  
• QtADB
  
• Multifunction batch file (NowenUI)
  
• Multifunction batch file (BrateloSlava)
  
• Improving sound (as well as gps and hosts)

Custom recovery

Attention! The recovery data is for the latest firmware version of the bootloader (10.6.1.27.X for tf300t and 10.6.2.X for tf300tg / tl). Attempting to install them on the old Android 4.1 bootloader will scan your device with a probability of 99.99%.

On custom firmware, it is not recommended to reset user data (either via android / via the bootloader menu) - this leads to failure of the internal memory. If you want to do a reset, do it through TWRP

TWRP version 3.0 F2FS system does not support!

TWRP Official

TWRP for TF300T fully fits TF300TG

Download
Installation

TWRP Unofficial

Download:[email protected](7.12 MB)
XDA-developers topic
Installation

Instructions

Setting up 3G connections on custom

To installPPP Widget
How to configure the connection:That way
Setting Method # 2 with Xposed:That way
If it stopped working (or option number 3):That way

Nvflash

Detailed instructions for 4.2here.
Detailed instructions for 4.0here.

• NvFlash recovery from Linux
  
• List of NvFlash files
  
• If you have a brick and there is no NvFlash: information for consideration.

Unlock device

ATTENTION!!! When you unlock the device, you lose the warranty !!! You also lose the right to receive OTA firmware updates !!!

1. Download the correct version for your firmware version:
4.0/4.1 ==>UnLock_Device_App_V7.apk(599.16 KB)
4.2 ==>Unlock_v8.rar(338.95 KB)
2. Copy the .apk to the tablet.
3. Install, run. We read the agreement, we press the treasured button. The device will reboot with the unlocked bootloader, which will be written in the upper left corner when loading.

Unlock issues

• If there is no button when unlocking, then try to reduce the font.
  
• If you give an incorrect password when requesting Google account data, delete the account from the device.
  
• If network connection error
  
• If all the ways do not work

  Recently, there have been frequent cases of getting errors when unlocking (Network connectivity problem). Solution - contact those. support!
  In field*Description of the problem*need to write "I want to unlock the bootloader, but when you use your official utility, the device gives an error: "Unknown error while connecting to the network. Please wait and try again later.", regardless of 3G or Wifi connection. Current firmware is"write firmware version", the screen error is attached". More screening is necessary at the moment when their software swears at the lack of connection. After 1-2 days, you can unlock the device - they exclude your tablet from their registry! You can also try via Wi-Fi, not at home, but somewhere Cafe. You need a secure connection, ssl, because the Asusov server blocks the connection using the open protocol http.
  thankmyacherdfor information.
  
  
• If the tablet is refurbished

Original ASUS warning

If you are an appliance, you must be able to use it. ("Original Product"); The Original Product; It is not necessary to receive any software updates; your purchased digital content may also be affected.

Firmware

To roll back from custom to stock, use the batch file from the utility section!

• If not installed KatKiss:That way
  
• Rollback from 4.2 to 4.0
  
• Flashing graphic mods, deodex-versions of firmware, butanimations for stock firmware on a locked bootloader
  
• Firmware official firmware through custom recovery (TWRP) (not suitable for rollback with custom)
  
• Touchscreen firmware
  
• Firmware archive for recovery using a PC (for example, in the case of a broken screen and the lack of a docking station; we take the archive with the roothere)

Recovery

• Tablet recovery using NVFlash 4.2
  
• "Detector" of the state of the tablet and the decision to go to the SC
  
• Recovery using fastboot (manual flashing the drain with a wipe of all partitions) + Solving the problem"Unrecoverable bootloader error"
  
• Restoring official firmware on a locked bootloader
  
• Detailed instructions for restoring a dead tablet (after firmware is not a true recovery)
  
• Delete all user data via ADB (analog format data)
  
• Attempt to cure a bootlap with non-working recovery
  
• If you always boot into rekoveri and hangs on the TEAMWIN screensaver

Install official update

1. Find out the territorial identity of your tablet (SKU). Go to "Settings">"About Tablet PC">"Build number". There you will see the line WW_epad-8.X.X.XX_2011xxxx, where 8.X.X.XX is the firmware version and WW is a territorial identity (SKU).
WW- International assembly.
US- American assembly.
2. Download the firmware from the header forYour region.
3. After you have downloaded the file with the firmware, unpack its contents into the root of the memory card, and insert it into the tablet.
4. FurtherSettings - About Tablet PC - Check for update.

How to copy the archive with the firmware to the internal memory if the tablet does not turn on

All here

Bootloader update

• Update Bootloader for TF300T to version 4.2 (10.6.1.27.5) without firmware drain (Graiden).
  
• Bootloader Update for TF300TGup to version 4.2 (10.6.2.11) without flashing firmware (Clamor).

F2fs

Migration to F2FS

APX and fastboot transition methods

List of APX and fastboot transition methods

In fastboot / recovery without buttons

Here

Touchscreen calibration

• Touchscreen calibration (in case of spontaneous clicks) for 4.2
  
• Touchscreen calibration (in case of spontaneous clicks) for 4.0
  
• Touchscreen calibration instructions via ADB (root and docking station are not required)

Accelerometer calibration

Accelerometer calibration instructions (g-sensor)

Firmware

Official support of our device stopped at 4.2

On custom firmware, it is not recommended to reset user data (either via android / via the bootloader menu) - this leads to failure of the internal memory. If you want to do a reset, do it through TWRP

If you logged in for the first time and do not know where to start

What firmware to choose? - See the latest survey in the archive.

Android 7.1

Android 6.0 - Recommended

Android 5.1

Android 4.4

Android 4.3

Android 4.2

Android 4.1

Android 4.0

miscellanea

• Extracting the system folder from the official firmware
  
• Removing the system folder from the official firmware (2)
  
• Recover deleted files from internal memory (/ sdcard)
  
• I / O scheduler's & Governors
  
• Homemade USB-OTG (connecting a mouse and other devices without a dock)

Polls archive

Part 1

Part 2

KatKiss Nougatella

What's new?

13.05.2019 KatKiss # 038
01/03/2019 KatKiss # 035
10/28/2018 Added instructions for restoring via NvFlash from under Linux fromSage felixoid
10.10.2018 KatKiss # 033
07/25/2018 KatKiss # 031
04/13/2018 Added experimental firmware Unlegacy Android Project (7.1) fromClamor.
05/22/2018 KatKiss # 030
04.04.2018 KatKiss 7.1 # 029
03/14/2018 KatKiss 7.1 # 028
01/20/2018 KatKiss 7.1 # 027
12/05/2017 The KatKiss Nougatella firmware survey is over and moved to the archive.
10/21/2017 KatKiss 7.1 # 026
08/26/2017 KatKiss 7.1 # 025
07/17/2017 KatKiss 7.1 # 024
06/03/2017 Poll about KatKiss Nougatella firmware added.
05/17/2017 Added instruction fromthanderbirdfor those who do not put KatKiss above 4.4 (Instructions>Firmware)
05/15/2017 KatKiss 7.1 # 023
05/07/2017 The _that16 kernel fromClamorfor 7.1
04/29/2017 If you have a brick and do not have NvFlash: information for consideration (Instructions>NvFlash).
04/15/2017 KatKiss 7.1 # 022 - pay attention to the installation algorithm of this version (in the post)!
04/05/2017 Katkiss 7.1 # 021
03/23/2017 Translation of timduru tips on this firmware has been added to the post with Katkiss 7.1
03/18/2017 Katkiss 7.1 # 020 - now long presses are working in the navbar. + Last of. T / TG ​​firmware for WW region versions 4.0 / 4.1 / 4.2 are uploaded to the Ya.D.
03/09/2017 Katkiss 7.1 # 019 - the video now works.
02/28/2017 Katiss 7.1 # 018c - only for those who do not have Wi-fi on # 018b.
02.24.17 Katkiss 7.1 # 018b
02/10/2017 Katkiss 7.1 # 017
01/13/2017 K.РђРў - a post with the settings and the latest versions of the corporate "amp" for the Katkiss + firmware has been added to the gaps for Android 7.1 and 6.0 added to the "Utilities" section
01/08/2017 Katkiss 7.1 # 015 - firmware received Stable status
12/10/2016 Katkiss 7.1 # 014 - Bluetooth stopped working
11/15/2016 Katkiss 7.1 # 013 - the problem with recording audio has been solved
09/27/2016 Katkiss 7.0 # 008
09/03/2016 Katkiss 7.0
09/02/2016 Core _that15 fromClamorfor Android 6.0; Changed the structure of links to posts with firmware
08/30/2016 Kernels for CM 12.1 frompashkovwinsandClamor
05/10/2016 KatKiss # 26
04/16/2016 From the "Firmware" section, the subsections "Android 6.0", "Android 5.1."
04/14/2016 Added subsection "Setting up 3g connections on custom" in the section "Instructions"
04/13/2016 The cap on the requirements of the new section rules has been completely redone

All suggestions for filling and updating the caps should be written exclusively to the curator of the topic inQMS!

Statistics posts in the topic

Post has been editedArmstell - 13.05.19, 19:53

Reason for editing: KatKiss # 038

[andrew_z1]

dave312 @ 06/27/2012, 20:24

do not tell me how?

1. Get the blob from the firmware you like from the ASUS website and put it on the tablet (inside is / sdcard)
2. reboot with CWM - the tablet is connected, a device with the name Transformer appears in the devices - put the driver from the Android SDK forcibly for it (I have here c: \ Program Files (x86) \ Android \ android-sdk \ extras \ google \ usb_driver \ (Android driver ADB Interface)
3. in CWM, choose mount / data (like in advanced somewhere, although I could be wrong)
4. launch the console (with the loaded CWM!) And type adb shell there
5. get root shell in CWM - type dd if = / sdcard / blob of = / dev / block / mmcblk0p4
6. Go smoking for 5 minutes
7. after dd (disk dump) worked in CWM do wipe cache and wipe davlik cache
8. overload and wait until everything is set up again.

on exit (after reboot) CWM recovery will crash to stock because blob contains 5 partitions within itself:
1. partition table
2. bootloader
3. linux kernel
4. recovery
5. applications (what is in / system) - root will also fly

sobsno like this somewhere ...

[andrew_z1]

Actually how to cure the "crash video" on this tablet. It turns out everything is simple.
1. The tablet should be rooted
2. On the computer, take Notepad ++, create a new file, copy the following there:

#! / system / bin / sh

echo 2> / proc / cpu / alignment
exit 0

there should be no empty lines at the top - "#" should be the first character in the file.
3. In Notepad ++ go to the "Edit->Line end conversion->Convert to Unix format ".
4. Save the file as align.sh in the folder where adb is stored - more for convenience. If done correctly, the file size will be 53 bytes.
5. Run cmd in the folder with adb.
6. Type "adb push align.sh / data / local /"
7. Type "adb shell"
8. Type "su"
9. We type "cp /data/local/align.sh / data /" - right in / data / you can not shove - not the right :)
10. Type "chown 0.0 / data / align.sh; chmod 755 / data / align.sh"
11. Go to the Play Market and install the Script Manager - it's there alone.
12. Run, select in it to run as root.
13. Go to the / data / folder in the internal SManager explorer, select align.sh there
14. In the menu that appears, mark the icons "Su" and "Boot" - so that the script runs on reboot.

actually everything :)

echo 2> / proc / cpu / alignment

means to correct alignment errors in some operations (streaming - SIMD), while some video slowing down is possible (in places where the player would have flown out without it)
You can change this line in the script to

echo 0> / proc / cpu / alignment

to ignore and not to correct - tried it this way - also works

To see how many such errors have been fixed, you can type in the adb console under the root

cat / proc / cpu / alignment

PS In the stock firmware, the value is 4 (send a SIGBUS signal) and it is installed in / init.rc - if the craftsmen have a desire to reassemble ramdisk - you can do it :)

[andrew_z1]

[email protected], 14:50

Read the main Temka about our tablet, on the hardware one does not throw it out on the software codec, it throws it out of the video every 5-40 minutes. So if you work fine, I'm very happy for you. I bought the mh had to buy a dice.

Madam, you can buy the whole market - no one bothers you :) That's what I amexactly absolutelyI know - the problem of video playback here is not so much in the player as in the tablet :) And believe me, it does not depend on the number of processor cores :) And I will tell you more - applications like MX Player do not have and cannot be able to manage the number of cores involved processor :) The number of cores that is written in all players is the number of decoding threads (threads are for those who are familiar with programming) :) And it's not a fact that they will be executed in parallel - each on its own core :) I will say more - the probability of this is very small :) proof of my words - two links:
Kernel for TF300T from firmware 9.4.3.30
Kernel for TF300TG from firmware 9.4.4.28.1
To install, the device must be unlocked (I do not have the opportunity to sign these things with the ASUS key) and you must have a working root
1. save the file in the folder where adb is
2. enable USB debugging on the tablet and connect it to the computer
3. Run cmd in the folder with adb
4. in cmd we type "adb push kernel.blob / data / local / tmp /"
5. in cmd we type "adb shell"
6. In the already appeared shell of the tablet, type "su"
7. in the rue shell of the tablet, type "dd if = / data / local / tmp / kernel.blob of = / dev / block / mmcblk0p4" and wait for completion - 5-10 seconds
8. in the rue shell of the tablet, type "rm /data/local/tmp/kernel.blob; sync; reboot" and the tablet will disconnect from the computer and reboot.
when you boot you will see the blue bar - installing a new kernel, and another reboot.
after downloading you can forget about the problems of the video departure (and not only the video)

[andrew_z1]

HiLL_RSM @ 02.08.2012, 14:03

In 90% of cases, flashing to the stock will resolve issues. Moreover, some manufacturers even in the presence of the root accept devices under warranty, in case problems with the device arise through no fault of the root. For example, Samsung. I saw their letter to one friend on this subject. But I also heard about cases when the device that seemed to be reflashed from scratch was not accepted into the service, since it was somehow determined that it was ruto in the past. How they do it, what tails they find there, if the system partition is fully formatted - I personally do not know. But the cases really were. The probability of this is small, but it is still there. Therefore, keep in mind its all-worth it.

Well, now listen to the situation in reality:
The TF300T uses the so-called blob as firmware (there are 2 more files for the modem in the TG). Inside this blob are the following parts:
APP is the partition that is mounted directly inside / system (the usual Linux ext4 file system)
EBT is a bootloader - analog BIOS in the computer
LNX is the Linux kernel + ramdisk, which is mounted on / and serves as the root of the entire file system.
PT - internal memory partition table (although not sure)
SOS - recovery - structure like LNX, only there is everything to work

These parts are not signed separately each (like HTC does), but the entire blob is signed (the first 28 bytes). Actually blob is a kind of container that allows you to flash what you need.

In addition, the android system has mutable parts - / data and / cache (well, / mnt) - where users can write and these parts are formatted during factory reset.

If you flush a blob (signed) on a device with a locked bootloader and make a factory reset, you will get a device out of the box and more than one service center will not be able to prove that you got root on it. Well, if you certainly do not leave the SDCARD with SuperSU.apk in the tablet :)

[VARVAR_NEKIT]

again my instruction;)
HOW TO DISABLE AUTOCONTRAST!

!!! ONLY FOR ROOT DEVICES !!!

Instructions fromTHIS POST

Even when the auto-adjustment of the backlight brightness is disabled, the tablet sometimes adjusts the brightness / contrast, this is most noticeable in the power saving mode and at low backlight brightness.
The reason was the Didim technology (also known as dynamic dimmer, smart dimmer, dynamic contrast) implemented in Tegra3 processors - its essence is that the processor constantly analyzes the image and adjusts the brightness / contrast to bring it out without losing quality, but with a lower brightness of the backlight, which reduces consumption. More can be read, for example,here

To get rid of this, the root is required, then in the console we execute the command

echo 0> /sys/devices/tegradc.0/smartdimmer/enable

Valid until reboot.
Automatic command execution can be achieved, for example, using the programВ® Script Manager(Better to install from the market - there is a fresh version)
Or, if you don’t mind editing system scripts, you can add the ABOVE line to the files

/system/etc/cpu1.sh
/system/etc/cpu2.sh
/system/etc/cpu3.sh

These three scripts are executed when switching power modes.
A source

P.S. Do not forget to put likes hereTHIS COMRADEbecause this is his instruction well, and I can;)

Do not forget to unsubscribe!

[desjkee]

Wipe data / factory reset - reset all settings, remove third-party applications
Wipe cache - cache cleaning
Wipe dalvik-cache - cleaning the "tails" of the kernel
Wipe battery stats - so clear

This is all in brief)

[desjkee]

I tried now with drivers from the header, it did not work to get adb to work.

Here is Prime's driverUniversal_Naked_Driver_0.7.zip(8.28 MB)

With him a deviceTransformerin the device manager it becameTranformer Prime ADB InterfaceAnd I without problems threw the archive on the memory card.

Here is a more detailed instruction without unnecessary gestures. To make everything so much easier, do everything as it says.

1. DownloadUSB driverabove, unpack anywhere, but do not install.
2. Downloadadb.zip(196.56 KB)
, unpack and put the folderadbatC root
3. Copy the archive with the firmware inC root.
4. Turn on the tablet in recovery mode, connect it to the PC.
5. The device will appear in the device manager.Transformer.
6. Click onTransformerright click -Update driver - Install from a specified location - Overview- specify the path to the folderUniversal_Naked_Driver_0.7(this is the driver folder).
7. The device becomesTranformer Prime ADB Interface.
8. Run the command line.Win + R - cmd - OKorStart - Run - cmd - OK
9. On the command line, write the commands in turn:
cd c: \ adb(don't forget the space betweencd and c)
adb push c: \ Firmware name.zip / sdcard /(don't forget the space betweenThe name of the firmware.zip and / sdcard /)
10. Numbers will appear.

All archive in the internal memory.

If you did everything as described in this manual, observing all the paths and names, then everything will work out.

After installing the firewood from Prime'a, all the above written can be done on the included tablet.

Post has been editedArmstell - 18.04.16, 20:02

[sawax]

t1m5,
You can, you just need to download the firmware from the site in the memory of the tablet and in the lower bar there will be a notification that there is a firmware, then you click on it and then everything will go.
Help put a plus :)

M

Forum Rules
5.3. Implicit or explicit extortion of raising a reputation is forbidden, for example: “I helped you, and you didn’t even say thanks!” Or “You could have raised your reputation!” If you deserve a raise of reputation, you will be raised without reminders.

Post has been editedK-User - 18.08.12, 16:02

[Zee-X]

Zee-X @ 08/20/2012, 1:24 PM

People, and if you put a custom, dock keyboard with a mouse will work? Tell me please

M

Forum Rules
4.13. It is forbidden to raise the topic. Namely, the publication of messages aimed at only raising the topic in the list and not bearing a semantic load.

Post has been editedK-User - 20.08.12, 12:30

[gralexon]

Install TWRP recovery and root rights to Jelly Bean


Download both files at the bottom of the post.
fastboot.zip unpack and put in the root of the disk
Turn off the tablet
Just as before, we hold the volume down and paver, hold for 3 seconds
We fall into the bootloader. Now there are already 4 icons
Then lower the volume by moving the cursor to the USB icon confirm the choice with the volume up button
connect the hose. We are waiting for the Windows to recognize the device.
On the PC, run CMD (Start ->To find ->CMD)
Go to drive C: write fastboot
Then we writefastboot -i 0x0b05 flash recovery tf300t-jb.blobyou can even need to copy and paste!
We press Enter.
We wait for 8 seconds to see the blue strip, the firmware process is completed. In the command line we see OKAY

Turn off the hose, restart the pill, pressing the volume up and paver. I kept sec 10 pressed

Now copy the Superuser-3.2-RC3-arm-signed to the tablet in any place.
And again we start the bootloader, but now you need to select the RCK icon
Start TWRP
Stitching Superuser-3.2-RC3-arm-signed
Restart tablet
Download Supersu from Google Play and install
Open, agree to update the binary file

Everything. Now your jelly with root rights: thank_you:

All we need is:
[attachment = "1962938: fastboot.zip"]
Superuser-3.2-RC3-arm-signed.zip(1.08 MB)


Post has been editeddesjkee - 23.08.12, 22:33

[andrew_z1]

Desjkee @ 08.28.2012, 09:50

Everything is correct, do not install recovery without an unlock. Recovery is sewn into the bootloader, but does not replace it. In this case, JB does not block the bootloader, but replaces it. If I'm not mistaken, then the bootloader is sewn into the core. In the JB at the kernel version 3.0 ... while all the custom on the JB (except the last hydra) are collected on the source code have a version of the kernel 2.6 ... Apparently, this is the whole problem. This is like an assumption) If I am mistaken, then andrew_z1 will correct)

Will correct :)
1. The bootloader is an analogue of the BIOS in the tablet. nothing is sewn in its place. flashing something into the tablet is loading “this good” into a special staging section (/ dev / block / mmcblk0p4), checking that “this good” is signed with the correct keys (this is done by the bootloader), and the firmware of “this good” is already there, where necessary. The bootloader unlock is the prohibition of checking keys before flashing. The fastboot protocol is supported by the bootloader.
2. recovery is the usual linux kernel plus a minimum set of utilities for firmware, system recovery updates. stitched in a separate section. usually takes 5-6 MB (4 of which are the core)
3. linux kernel - in composition - in practice, this is recovery. By and large, the only difference is the script for mounting the / system partition and running dalvik - the virtual machine on which the android is running.
4. system - actually dalvik virtual machine and android applications.

as for the difference between kernels 3.0 and 2.6 - there is not much difference.

The boot process for both the recovery and the main kernel is as follows:
1. boot compressed kernel
2. ramdisk is loaded (from the same section)
3. the kernel starts and unpacks itself in memory and starts
4. mounts ramdisk to /
5. the first process "/ init" is started, which executes the script "/init.rc"

like that :)

[gralexon]

We don’t have a theme for decorators, so I’m writing here, and let the curator decide what to do with it;)
I rummaged through the whole xda and our forum, there is no information anywhere on how to change for example the soft buttons or for example the battery in percent.
Soft buttons on the native JB are completely different and I want it to be the same as on the phone and on the tablet.
Therefore, a small manual for jelly buttons.

Attention! Do not put on official firmware!

Just in case, make a backup!

Works on deodex firmware! Such is JellyBean-Hydro.
If there is a root, you candeodexing stock themselves.
Accordingly, you need a root

DownloadingSystemUI.apk(2.81 MB)

In root explorer (or similar with root rights) go to the system / app folder and rename the SystemUI.apk file to SystemUI.apk.bac
Place the downloaded SystemUI.apk in this folder
We give the file rights rw-r-r
Overload tablet
And admire

For the more advanced, there is another way. Good old MetaMorph
Downloadingbutton setin zip format
Open and slightly change the name of the folders. All icons are placed in the destination folder "drawable-sw720dp-hdpi" and "drawable-sw720dp-mdpi"
InstallMetaMorphon the tablet, choose your modified zip and apply. After the restart, the wallpaper flies from the desktop,
But the buttons successfully change: thank_you:
Here is an example of zip, stock buttons with reflectionsoftkeys_JBstockreflect.zip(14.4 KB)


For example, I set myself


Post has been editedgralexon - 05.09.12, 12:18

[SergeyIA]

GTR_skyline @ 09/10/2012, 10:13

"I've just been quoted $ 122 + $ 65 + $ 10 shipping. Which comes out under a shade under $ 200 total."

Something after such messages on xda seems to me that the authorized service center will tell me that I need a replacement mate. fees. and they can not sew through apx themselves. If over the hill all the same.

200 it’s in my opinion they have godly way (we don’t have any sense to do such things, or the techie joked today and I didn’t understand his joke, or the way it is) will tell you in order, I decided as I had time to reel today in the asus center (central!), well, I was greeted nicely there, what they say you want, well, I wished)) rollback from JB to ICS, then the receiver received such a mine, I will tell you, and what they say is wrong and why you want it to do, all the more for their own money, they say ... well, okay, I told him that I simply didn’t like it and that’s it, I want ICS, in short, he outlined a situevin, h About the pier, Asus put the pig, gave the unblocker, I used it - I lost the guarantee, and then with the update I will get the lock again and there is no guarantee back, in general he ran a couple of times to the engineers, apparently told them how and what, they asked what to put (in meaning what version) I was really glad, so they say any .29 .30, like I will be again like a normal person on SM and it was not there, they tormented him for about an hour and so I stayed with this jelly bean, but the option was offered , if they say they are satisfied, then let's leave it, we will contact with asus (bu It’s 2-3 days minimum) they should give the code and we will only be able to restore the bootloader and ICS after you, I didn’t do that yet, all the hope is that something will come up with either the cyan team or the second (forgot, AOKR that seems) . casually wondered how they say then restore the APX, who replied that not all of them are being restored, well, he asked the next question about the cost of replacing the motherboard and the matrix (I didn’t understand the answer so far, he flipped the roofing felts the way it was we are with this, for both this and that case under 400 bachi, is inclined to think that he was not joking, for I said to this that this is the same as something with something simpler to buy and spare parts will remain, to which he seemed to agree with me) in general, this is my trip turned out, no words just mat m

[andrew_z1]

[email protected], 22:54

Have you tried modprobe to load the modem driver module? rmnet or raw_ip_net. I can’t find where the modules are hidden in this "free" OS ...

The raw_ip_net module does not control modem power. It is used only to transfer IP packets from the modem over the USB bus (to which it is connected by the way).
Power, reset and some other things are controlled through the so-called GPIO - general purpose input-output outputs of this SoC.
The module that is responsible for managing the modem’s power is called baseband-xmm-power.c and is located in arch / arm / mach-tegra. It is assembled into the core and cannot be rebooted.
In addition to the modem in the TG is still using one module - baseband_usb_chr.ko. It is used only to update the firmware in the modem and is loaded only in the recovery. It is for this reason that TG needs a specially collected recovery - otherwise the modem will simply not be updated.

Another caveat for those who want to build the kernel itself (on a Linux machine, this is not difficult) - do not try to build the standard adroid NDK - the kernel will boot, the modules will not be loaded. The compiler must be taken here -Building kernels

Post has been editedandrew_z1 - 12.09.12, 14:13

[andrew_z1]

[email protected], 18:39

andrew_z1,
is it about nvflash? And what is the use of it for users? just a fastboot replacement?

nvflash is a NVIDIA utility that allows you to flash an absolutely clean device (which just has a clean flash memory - a brick in APX mode) via USB.
but to use it, you need to pull out or generate a certain key (SBK - Secure Boot Key), its own for each tablet and is generated based on the processor's serial number.
Here you can generate (or pull out) it (as I understand it) only in the old bootloader.

This is not a replacement for fastboot, although recovery (slightly corrected) and other sections can be flashed to it for example (in APX mode)

is it clear?

[andrew_z1]

[email protected], 21:17

Good day to all) I wanted to clarify about NVflash, what is it that he can put the locked bootloader back on? or something I did not understand?))

When unlocking, the bootloader does not change.
Just flashing the so-called Unlock Token - an individual for each.
If you erase it - the device will block again.

Quote:

2:21 pm and if I erase unlock token - I just get locked device? :)
14:23 <@RaYmAn> yup

[} I {IvchiK]

Attention, the whole procedure was done on my tablet.
All actions you take at your own peril and risk. I or the curator, we are not responsible for your devices.
AFTER SUCH HOW YOU PERFORM THIS INSTRUCTION, YOU WILL LOSE ALL CONTENT OF THE DEVICE'S INTERNAL MEMORY (including NVflash / Custom Recovery / Route)
So, instructions for upgrading to 4.1 (for TG version owners. Who doesn’t install the update in a regular way)
1) Downloading the update from the site asus
2) Extract the firmware itself from the downloaded archive (also .zip archive)
3) Extract a file named blob from 2 archives (yes, yes, a needle in an egg-egg in a duck)
4) File blob put in the folder with fastboot (On the computer naturally)
5) Next, you need to transfer the tablet to fastboot mode
6) Open the command line, go to the directory in which we have fastboot and blob file
7) We write fastboot -i 0x0b05 flash staging blob in the command line
Next, the process of uploading the firmware to the tablet and installing it
ATTENTION
For some unknown reason, fast boot does NOT write about the completion of the process.
So I just waited ~ 15 minutes after the last line appeared on the command line.
8) After an anxious wait, we restart the tablet manually.
We are waiting for the system to update itself.
We are happy with the updated version of the OS, at our discretion we put custom recovery and root (Do not forget what to set for 4.1)
Update
Straiker13
Successfully updated on this guide

Post has been edited} I {IvchiK - 09.10.12, 10:16

[Razorr1996]

TF300 NVFLash Verified!
Details:here

Nvflash kitforASUS Transformer Pad 300. (TF300 NVFLash).

UtilityTF300 NVFLash allows completely unlock the tablet.
For this, severalblob files , specific (unique) forspecifictablet ,
with which access to all functionsNVFLASH .
This makes it possible to recoverany software , partition , brick and even bootloader !
Of course, only as long as you keep these files safe! ;)

Make this procedure is highly recommended to all who unlocked the tablet.
This is achieved almost 100% guarantee that the tablet can be revived after any "bullying".

You can install a custom loader and, accordingly, initially create NvFlash blob files only on the old (ICS) loader.

Video instruction: youtube.com

Instruction (in Russian):

First of all check out some of the details:

1. TF300 NVFLash will work only on UNLOCKED the tablet.
   
2. For the preliminary preparation of the tablet is requiredFastboot access .
   
3. TF300 NVFLash does not work on completely ripped tablet For see. 2 .
   
4. You must store files in a safe place!
   

Introduction

• After many months of painstaking research, the developersAndroidRoot.mobi released Nvflash kit for ASUS Transformer Pad 300 that provides full NVFLASH access .
  
• As part of the process of obtaining such access, you must flashcustom loader AndroidRoot.mobi which has many advantages over stock loader .пїЅ
  However, loader firmware is a potentially very risky operation. Please consider before proceeding.
  
• As part of the application of this guide, you disclaim all obligations or liability to the development team for any damages suffered by AndroidRoot. By following these steps you are aware of all the risks.
  
• Please note that this is a rather complicated procedure that must be performed by a competent user.
  

AndroidRoot Patched Bootloader

• Current versionbootloader-butAndroidRoot.mobi for Transformer Pad 300 : 9.4.3.30r01 .
  

The necessary conditions:

• Unlocked the tablet Transformer Pad 300 .
  
• Binaryfastboot and necessary drivers: Universal_Naked_Driver_0.7.zip ( or more recent ).
  
• BinaryNVFLASH from Nvidia .
  
• Nerves of steel! : superman:
  

File generationnvflash blob.

• To obtain NVFLASH access You need to generate nvflash-blob files that allow authentication for mode Apx on the device.
  
• First, download the files (see below):
  NvflashTF300_Full.zip
  
• Connect the tablet cableUSB to PC . As usual in such cases, DIRECTLY and not through DOCK!
  
• Now you need to restart the tablet in modefastboot .
  This is done by rebooting the device while holding the button."Volume down" before the inscription "Checking for RCK image” . At this stage, you do not need to do anything until the boot menu appears.
  When the boot menu appears, press the volume down key."Volume down" until you choose a badge "fastboot / usb" and then press the volume up key "Volume up" to put the device in mode fastboot .
  
• Open the command consoleCMD (Win + R =>cmd) and go to the "working directory" with the command:
  
  cd C: \ Nvflash
  
  
  
• Attention! Now we have to perform the most potentially dangerous operation.
  It will last only a few seconds. But before continuing:
  
  • Make sure your cat, child, wife with a mop (husband with a bottle of beer), etc. are locatedout risk areas.
    
  • Measures have been taken to prevent a sudden power failure.
    Ideal to use a laptop or PC with UPS.
    
  
  So, when the tablet is in modefastboot , execute the following command, which will run the custom loader AndroidRoot :
  
  fastboot -i 0x0b05 flash bootloader ebtblob.bin
  
  
  
• Before continuing, make sure that the custom loaderAndroidRoot successfully sewed.
  To do this, restart the device again in the modefastboot .
  In the upper left corner of the screen instead of text"This Device is UnLocked" should now be text: "AndroidRoot 9.4.3.30r01" .
  
• After you have loaded the tablet in the modefastboot with loader AndroidRoot finally it is time to create files NVFLASH blobs using the following command:
  
  fastboot -i 0x0b05 boot nvfblobgen.img
  This command will generate the necessaryblob files and save them on tablet in the catalog / sdcard / AndroidRoot .
  Please note that this process may take 20 - 30 seconds and will automatically restart the device after its completion.
  During this time, no progress is displayed, just wait patiently for its completion.
  After rebooting, the device should fully boot intoAndroid .
  
• Afterblob files have been created, you need to get them from the "internal" SD card from the catalog AndroidRoot ( / sdcard / AndroidRoot ).
  This can be done either through the mode.MTP or by Adb , or in any other way .
  ** You must save these files in triplicate - this is your life **
  Besides,copy these files to the "working directory" C: \ Nvflash .
  

Access NVFLASH

• Finally you can now getNVFLASH access using the program wheelie .
  To do this, you need to restart the tablet inAPX mode :
  • Turn off the tablet, connect it to the computer and turn on holding the button volume up "Volume UP" .
    
  • Keep the buttons pressed until your computer determines that a new device is connected. At the same time, he will emit a sound notification about the device found.
    Note:
    • At this stage, you may again need to install drivers.
      
    
    
  • In case of success,screen should remain blank, and in the notification panel of your computer, the tablet will show up as"NVIDIA APX mode device" .
    
  
  
  
• For"bootstrap"("bootstrap") atNVFLASH , run the following command:
  
  wheelie --blob blob.bin
  whereblob.bin - one of the files generated above.
  If successful, the tablet will boot intoNVFLASH and the bootloader screen will appear.
  From this point on, you can finally useNVFLASH !
  

What's next?

• Good news! You receivedNVFLASH access ! So what else to do next?
  Highly recommended to absolutely everyone who got NVFLASH access , executed the following commands to create backup files bricksafe.img , "unlock-token.img" and "factory-config.img" using the following commands:
  
  nvflash --resume --rawdeviceread 0 2944 bricksafe.img
  nvflash --resume --read 14 factory-config.img
  nvflash --resume --read 7 unlock-token.img
  nvflash --resume --go
  The last command will reboot the device.
  Note:
  
  • These files are in the "working folder"c: \ Nvflash .
    
  
  These are very important backup files that you need to keep in a safe place along with NVFLASH-blobs files (see above).
  ** Failure to create or lose backup filebricksafe.imgwill lead to a denial of support, in case you ever turn your device around!
  You are warned! **
  

Original instructions

Download:

• ForWindows :
  • All the necessary files "in one bottle": NvflashTF300_Full.zip (13.59 MB)
    
    
  
  

Note:

• Instruction "Backupandrecoveryfirmware withNVFlash." located here .
  
  
  
• Instructions in Russian on how to restore the tablet "from the ashes" using NVFlash!
  

P.S. Translated and completed this manual.Dasdranagonfor which heTHANK!

Post has been editedArmstell - 14.11.16, 18:06

[bald1984]

M

desjkeeexempt from supervision on their own.

[bald1984]

M

sad96appointed curator of the topic.