[Q] TF300 and ME301t compatibility

SnowmanDK

Senior Member
Aug 21, 2009
321
45
0
Hammel
Hi all.

I just got my ME301T today, and off course I wanted to root and unlock it right away.

I read up on these forums first (as you can see I have been on XDA for a little while).

Then I updated to 4.2.1 (I see ppl mention 4.2.2 official, but can't find it).

I followed the guides from THIS post

My results are as follows:

Motochopper gives this
Code:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Pushing exploit...
1264 KB/s (1283460 bytes in 0.991s)
[*] Pushing root tools...
1121 KB/s (91980 bytes in 0.080s)
1229 KB/s (1867568 bytes in 1.483s)
1191 KB/s (969701 bytes in 0.794s)
        pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
[*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.
[*] Cleaning up...
[*] Exploit complete. Press enter to reboot and exit.
When trying to push the recovery I get this
Code:
sending 'recovery' (6448 KB)...
OKAY [  1.202s]
writing 'recovery'...
FAILED (remote: (InvalidState))
finished. total time: 1.670s
Anyone have any tips as how to get past these issues? Even the official Unlock.apk fails as it claims there is internet issues.
 

sbdags

Inactive Recognized Contributor
Jun 24, 2007
12,753
15,556
0
Kenilworth, Coventry
Hi all.

I just got my ME301T today, and off course I wanted to root and unlock it right away.

I read up on these forums first (as you can see I have been on XDA for a little while).

Then I updated to 4.2.1 (I see ppl mention 4.2.2 official, but can't find it).

I followed the guides from THIS post

My results are as follows:

Motochopper gives this
Code:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Pushing exploit...
1264 KB/s (1283460 bytes in 0.991s)
[*] Pushing root tools...
1121 KB/s (91980 bytes in 0.080s)
1229 KB/s (1867568 bytes in 1.483s)
1191 KB/s (969701 bytes in 0.794s)
        pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
[*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.
[*] Cleaning up...
[*] Exploit complete. Press enter to reboot and exit.
When trying to push the recovery I get this
Code:
sending 'recovery' (6448 KB)...
OKAY [  1.202s]
writing 'recovery'...
FAILED (remote: (InvalidState))
finished. total time: 1.670s
Anyone have any tips as how to get past these issues? Even the official Unlock.apk fails as it claims there is internet issues.
Sounds like you haven't unlocked.
 

SnowmanDK

Senior Member
Aug 21, 2009
321
45
0
Hammel
Sounds like you haven't unlocked.
I tried, both using the Unlock_V8.apk and the official Unlock.apk

They both fail with a message that there is a problem with internet.
Browser works fine online, so I DO have a hole through...

I managed to root it now by reverting to .25 release though. Bootloader is still locked.
 

SnowmanDK

Senior Member
Aug 21, 2009
321
45
0
Hammel
I managed to root it now by reverting to .25 release though. Bootloader is still locked.
After rooting with .25 installed I used instructions from ChungHung.Chen earlier in this thread, and rolled on .31
Sadly OTA rootkeeper can't see my backed up root so I can't reinstall it.
Wonder if that's a change from .29 to .31?
 

SnowmanDK

Senior Member
Aug 21, 2009
321
45
0
Hammel
I had to revert to .25 and root again.

I'd like to refer to my previous post and ask if others have the same problem with rooting/re-rooting .31 firmware?
Anyone found a solution that works?

Also, anyone have an idea as to why I can't unlock my bootloader? It just keeps failing with a message
saying that there might be a network connection problem, but the tablet tells me that a .31 update is available.
 

patrickdass

Senior Member
Oct 24, 2012
84
14
38
Kepong
I had to revert to .25 and root again.

I'd like to refer to my previous post and ask if others have the same problem with rooting/re-rooting .31 firmware?
Anyone found a solution that works?

Also, anyone have an idea as to why I can't unlock my bootloader? It just keeps failing with a message
saying that there might be a network connection problem, but the tablet tells me that a .31 update is available.
Can you confirm root access?
 

krash1256

Senior Member
Oct 7, 2013
239
48
0
This is what I did.

I downloaded Kingo Android ROOT and rooted the tablet. when it rebooted I installed supersu.apk
adb install supersu.apk
adb shell
/system/xbin/su
mount -o rw,remount /system
cp /system/xbin/su /system/bin/
reboot

Then make sure Unknown sources is checked. Install Unlock_v8.apk, it will ask you if you are sure you want to unlock your device, tell it yes, after it runs it will reboot your tablet and the message about device is unlocked will appear. Put the twrp.blob on internal or external card.
once again run
adb shell
/system/xbin/su
mount -o rw,remount /system
(if the recovery is on internal run) dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
(if the recover is on external run) dd if=/Removable/MicroSD/twrp.blob of=/dev/block/mmcblk0p4
reboot
your tablet should now be rooted, unlocked and have twrp recovery on it. Boot to recovery make a backup of your Asus rom.

I use Titanium Backup Pro without any issues, and Root Checker confirms root as well, so I'd say yes.

Sent from my LG-P990 using xda app-developers app
 

SnowmanDK

Senior Member
Aug 21, 2009
321
45
0
Hammel
@krash1256

I get to the unlock part, then the app just says it can't unlock, and that there might be a problem with the network.
It have said that every time I have tried for the last week.
Odd thing is that browser connection is fine.

I even tried installing the unlock app from Asus own homepage.
It gets to the point where it want either my Google login or pin code for my device to continue.
Then IT pops up, saying a problem occurred, and that I can try again later.

Seems like I'm not gonna be able to unlock my device.

Sent from my ME301T using xda app-developers app
 

krash1256

Senior Member
Oct 7, 2013
239
48
0
That's odd.

[/COLOR]
Off the top of my head; WiFi and touch driver/module are the main issues. Everything else seemed to work fine, I didn't test much beyond basic functionality because of how much I hated navigating the tablet like a mouse!
Is there a simple way to change the wifi and touch driver/modules and try again? I have the source code from Asus but I don't know how to figure out how to change the modules. I'm willing to give it a try anyway.
 
Last edited:

coolloser

Senior Member
Sep 25, 2009
399
103
63
Calgary
[/COLOR]

Is there a simple way to change the wifi and touch driver/modules and try again? I have the source code from Asus but I don't know how to figure out how to change the modules. I'm willing to give it a try anyway.
The WiFI module is in /system/lib/modules (it's either cfg80211.ko or prima_wlan.ko, whichever one is there, can't remember off the top of my head which one it is) but I have no idea where to begin with the touchscreen driver, from my limited knowledge; I think it's actually baked into the kernel.
 

krash1256

Senior Member
Oct 7, 2013
239
48
0
In the kernel, but the problem was caused by missing idc files
OMG thank you. I'm downloading now and will give it go and let you know how things went. If this works I will bow at your feet and definitely donate some money for your time and effort. It might now be a whole lot because I live on a fixed income but I will donate as much as I can, even if I have to donate every month for awhile. And maybe others will step forward and help out as well.

---------- Post added at 06:48 PM ---------- Previous post was at 06:21 PM ----------

OMG thank you. I'm downloading now and will give it go and let you know how things went. If this works I will bow at your feet and definitely donate some money for your time and effort. It might now be a whole lot because I live on a fixed income but I will donate as much as I can, even if I have to donate every month for awhile. And maybe others will step forward and help out as well.
Failed.

Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
assert failed: getprop("ro.product.device') == "me301t || getprop("ro.build.product") == "me301t"
E:Error executing updater binary in zip '/external_sdcard/cm-10.2-20131202-UNOFFICIAL-me301t.zip'

Was I suppose to put it on internal sdcard?
 

nikybiasion

Member
May 8, 2011
37
45
0
mogl.altervista.org
Can you connect with adb and post a logcat?


Edit:
I've two folders in my build structure, me301t and me301t.old ... brunch has done a "merge" of them :D
I rebuild all as soon as possible and fix "assert failed" problem
 
Last edited: