[GUIDE/TUTORIAL] Asus Transformer Pad TF300T Any version to Android 7.1 Nougat

[resetLetki]

For anyone having trouble unlocking their device: I have written a follow up in a different thread after having issues with unlocking a TF300TG. I falsely assumed that I could just use the latest firmware for TF300T mentioned in the guide, which apart from breaking many features (USB connection to PC, including adb and MTP stopped working completely) also seemed to break the unlock process of the modified UnlockApp.apk.

I finally managed to unlock my TF300TG.
The issue was I was following this guide and installed the version suggested, which is the latest version for TF300T. Apart from other issues, the Unlock App did not go through correctly and I just received the '105' responses from ASUS servers.
What I did to fix the issue was this:

1. I have created an account for ASUS support and registered the device using the serial number. Just make sure that it is registered, it does not matter which account it is registered to. If you can successfully register it, that's great. If it says something like 'device already registered', this should also be okay. Key here is that ASUS is "familiar" with the device serial.
2. I updated the tablet to the latest official firmware corresponding to my SKU (WW). I downloaded this from the ASUS support page (10.6.2.10 WW)
3. Downloaded the modified DMClient for TF300TG, as well as the UnlockApp for TF700T and TF701T from this thread (I tried both, can't remember which one worked in the end but I think it was the 700 one.
4. Followed the guide like usual (root, install ESFileExplorer)
5. Moved DMClient and UnlockApp .apks to the system apps folder, adjusted permissions to rw-r--r--.
6. Deleted/Renamed the DMClient.odex file
7. Restarted the device
8. configure Proxy / mitmproxy (v. 7.0.0), installed mitmproxy Android cert

Now.,after being on the correct firmware for the device, I got a different response code from the server after the initial GET request (response='0') following a POST request from the device (response had device details and "error" in it somewhere), but this time a new error appeared on the device (see post from @Mitrich.skype on p.16) "Failed to unlock device, please try again later.".
I tried installing three different UnlockApp apks as system apps, the ones from this thread, as well as from the TF300T guide.

I finally got to unlock it after this sequence of actions:

1. delete DMClient.apk (and DMClient.odex) from system apps folder
2. restart Device
3. moved the same DMClient.apk to system apps and adjusted permissions to rw-r--r--
4. restarted Device
5. Opened Unlock App, clicked the button, Device is restarting -> Device is now unlocked!!!

So in my case, the biggest issue was that I was being on a wrong firmware alltogether, making the request to ASUS servers fail. I realized this only when I was moving and trying out different modified DMClient.apks (for TF300T and TG and 700T...) in ESFileExplorer, and the version number for the TF300TG did not match the one on my device. If you click on the .apk in ESFileExplorer, it will show the version number of the app below the name I believe. So make sure you have the latest firmware installed, as well as use the correct modified DMClient.apk.

 

[Galmo13]

Hi. I've been trying to follow your tutorial, everything went pretty smoothly until I tried to unlock the bootloader. I had no problem with the proxy, I downloaded the certificate, but when I tried to launch the app ("Unlock Device Tool V7, the one from your zip) it said "Unknown error occured". I saw with mitmproxy that there was some tries to connect to Asus server. There is a text file linked with what mitmproxy said during the try. I think it's not that complicated to fix (although I did do everything about setting up the proxy like you said) but I don't know a lot about proxies and stuff. I did download the certificate on the tablet, and attempted multiple soft resets of the tablet, but it was all in vain... Many thanks in advance for anyone who will reply to this, and for all of those who keep those old hardwares alive !

 

[errhec]

Did you set the premission also for UnLock_App_V7_update.apk. ??

Did you use mitmproxy 7.0 ?

Follow the steps as is described in tutorial.

 

[Galmo13]

Yes, everything you said was done. I was working with a 4G connection with my phone, so it could be that. The tablet couldn't even load asus.com website due to chrome being too old. However, after switching to a standard Wi-Fi and installing Opera mini, it worked just fine, but thanks to you

 

[Ju5t3nC4s3]

Dns. Always the dns..lol

 

[beerpass]

I'm having issues with unlocking the bootloader as well. I was able to follow along pretty easily up to that point, and I'm not sure where things are going wrong.

Here's every step I took so far:

• Downloaded all files, installed drivers on my laptop, it recognizes the tablet and can transfer properly.
• Rooted the tablet, had to use the Windows app to do so but it worked and is definitely rooted.
• Copied DMClient and Unlock_App apks to the appropriate folder, changed permissions as listed, restarted tablet.
• Installed Mitmproxy v.5.0.0 because v.7.0.0 refused to open on my Win8 laptop. Changed the settings as listed, except for the tls_version_client/server_min settings because they weren't in the menu. (This might be where the issue is, but I can't figure out how to fix that if the setting isn't even there to change.)
• Changed the PIN on the tablet, changed the proxy settings to match my laptop IP, downloaded the certificate properly.

I know web traffic is going through the proxy as it should because I can see the log update whenever I open a website or an app. When I try to use the unlocker, however, I see a clientconnect followed by a clientdisconnect three times in the log before I get the "an unknown error occurs" message popping up on the tablet screen. I tried to change the ssl_version_client/server settings to "all" instead of the default "secure" to see if that would have an effect, but no such luck.

I've done a hard reset a couple times and started from the beginning (skipping the root since that's already done), but it still won't work. Both the laptop and tablet are connected to the same wi-fi, so there's no issue there. Laptop is set to private network as well. Turning off the laptop's firewall had no effect.

Is there something I'm missing with v5.0? Is there any way to get v7.0 to work on Win8? Any other suggestions as to what I'm not doing right?

 

[ChrisOfParis]

Hello
I do have the same pb when i try to unlock a TF700t....
Help appreciated.
Christophe

 

[lukjanet]

Hey, I have a problem because I think I crashed the bootloader. It hangs on my logo and on FASTBOT I can not restore the BLOP file. because I have a message:
fastboot -i 0x0b05 flash staging blob
sending 'staging' (800931 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.174s

 

[Ubaldo1616]

Hello
Awesome post!!
However , I am stuck with the bootlader part
I get the following message in mitmproxy
" error establishing server connection: [Errno 10060] Connect call failed"
Any idea what it might be?

 

[chupapimunanio]

Hi guys, im new in this world of bootloader and root in this device. I read everthing in the guide but i spend 1 month and still no root and no bootloader my device. Maybe someone can explain all the proces in one video for making more easy this thing. Have a great day. Thanks for all and sorry my bad english

 

[djibe89]

Hi guys, im new in this world of bootloader and root in this device. I read everthing in the guide but i spend 1 month and still no root and no bootloader my device. Maybe someone can explain all the proces in one video for making more easy this thing. Have a great day. Thanks for all and sorry my bad english

Hi, sorry for that.

But you should tell us more.

Tab recognized by PC ?
kingoroot installed on tab ?

 

[voiprostov]

Hello.
This guide has obviously helped a lot. But like some members, I also encountered the inability to unlock the bootloader. I have tried different versions of mitmproxy but failed every time.
At the moment, the mitmproxy event log outputs the following when trying to unblock:

192.168.30.17:51102: error establishing server connection: [Errno 10060] Connect call failed ('123.51.152.19', 443) 192.168.30.17:51102: client disconnect 192.168.30.17:51103: client connect 192.168.30.17:51103: error establishing server connection: [Errno 10060] Connect call failed ('123.51.152.19', 443) 192.168.30.17:51103: client disconnect 192.168.30.17:51104: client connect 192.168.30.17:51104: error establishing server connection: [Errno 10060] Connect call failed ('123.51.152.19', 443) 192.168.30.17:51104: client disconnect

I also noticed that when setting the proxy address in the wireless network settings, there is a warning: The HTTP proxy server is used by the browser, but is not available to other applications. But for unlocking, just another application is used - Unlock Device Tool v7.
Maybe someone has a solution to this problem?

 

[djibe89]

Hello.
This guide has obviously helped a lot. But like some members, I also encountered the inability to unlock the bootloader. I have tried different versions of mitmproxy but failed every time.
At the moment, the mitmproxy event log outputs the following when trying to unblock:

192.168.30.17:51102: error establishing server connection: [Errno 10060] Connect call failed ('123.51.152.19', 443) 192.168.30.17:51102: client disconnect 192.168.30.17:51103: client connect 192.168.30.17:51103: error establishing server connection: [Errno 10060] Connect call failed ('123.51.152.19', 443) 192.168.30.17:51103: client disconnect 192.168.30.17:51104: client connect 192.168.30.17:51104: error establishing server connection: [Errno 10060] Connect call failed ('123.51.152.19', 443) 192.168.30.17:51104: client disconnect

I also noticed that when setting the proxy address in the wireless network settings, there is a warning: The HTTP proxy server is used by the browser, but is not available to other applications. But for unlocking, just another application is used - Unlock Device Tool v7.
Maybe someone has a solution to this problem?

Hi, you may try with the specified mitmproxy version and another computer.

 

[tupadrotebbxd]

Hi, sorry for that.

But you should tell us more.

Tab recognized by PC ?
kingoroot installed on tab ?

Hi i have the same problem like that guys. My pc doesn't recognized my tab and also or unlock bootloader i cant. Kingroot has been installed correctly.

 

[djibe89]

Hi i have the same problem like that guys. My pc doesn't recognized my tab and also or unlock bootloader i cant. Kingroot has been installed correctly.

USB drivers installation is tricky.
You have to test within Windows Device Manager

 

[tupadrotebbxd]

USB drivers installation is tricky.
You have to test within Windows Device Manager

okay men. Thanks a lot

 

[djibe89]

okay men. Thanks a lot

You succeeded ?

 

[tupadrotebbxd]

You succeeded ?

Hi, i Plug tab to PC, i launch a command where adb.exe is located and enter command: adb devices but my PC still doesn't recognize the tab

 

[djibe89]

Hi, i Plug tab to PC, i launch a command where adb.exe is located and enter command: adb devices but my PC still doesn't recognize the tab

You need to install USB drivers with "disabled signature checking" again.

 

[Ubaldo1616]

My computer does recognize the tablet, and I was able to do the King root part, but stuck on this same part, any suggestion?

Hello.
This guide has obviously helped a lot. But like some members, I also encountered the inability to unlock the bootloader. I have tried different versions of mitmproxy but failed every time.
At the moment, the mitmproxy event log outputs the following when trying to unblock:

192.168.30.17:51102: error establishing server connection: [Errno 10060] Connect call failed ('123.51.152.19', 443) 192.168.30.17:51102: client disconnect 192.168.30.17:51103: client connect 192.168.30.17:51103: error establishing server connection: [Errno 10060] Connect call failed ('123.51.152.19', 443) 192.168.30.17:51103: client disconnect 192.168.30.17:51104: client connect 192.168.30.17:51104: error establishing server connection: [Errno 10060] Connect call failed ('123.51.152.19', 443) 192.168.30.17:51104: client disconnect

I also noticed that when setting the proxy address in the wireless network settings, there is a warning: The HTTP proxy server is used by the browser, but is not available to other applications. But for unlocking, just another application is used - Unlock Device Tool v7.
Maybe someone has a solution to this problem?