[ROM] [4.4.4] [OmniROM for ME301T] [OFFICAL]

Search This thread

scanno

Senior Member
Mar 27, 2008
2,248
3,810
Arnhem
Redmi K20 Pro
Xiaomi Poco F3
omnirom_logo-big_layout_transparent-250px-150x150.png
OmniROM for ASUS MeMO Pad Smart (ME301T)

About OmniROM
See what OmniROM is all about: http://omnirom.org/about/
This ROM is created because there are people who use the Asus MeMO Pad Smart and would like to have a choice. I personally do not own an Asus MeMO Pad Smart, but since the device is pretty simular to the TF300T, i am building this ROM together with the TF300T.

What do you need
OmniROM is a custom ROM and to be able to install a custom ROM, you will need to unlock your bootloader. You can unlock your bootloader from the Asus website. Please be advised that you will loose your warranty.

  • To be able to install OmniROM you will need TWRP 2.8.x
  • You need to have TWRP or CWM installed
  • You will need a flashable GApps package
  • You need SuperSU if you want to have root access

See the Downloads part of this message for the needed packages

How to install
To install OmniROM please follow these instructions:
  • Boot into recovery and flash the TWRP 2.8.0.0 (or a higher version) ZIP
  • Reboot the tablet into the old ROM
  • Reboot into recovery again
  • Do a factory reset / full wipe
  • Flash the OmniROM zip file, the GApps ZIP file and SuperSU ZIP file
  • Reboot the tablet and enjoy OmniROM

Downloads
Below are the files you need for flashing OmniROM:

Enjoy OmniROM

XDA:DevDB Information
OmiROM for ASUS MeMO Pad Smart (ME301T), ROM for the Asus Transformer TF300T

Contributors
scanno
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.1.x
Based On: OmniROM

Version Information
Status: Beta

Created 2014-01-28
Last Updated 2014-10-26
 
Last edited:

ebonit

Senior Member
Nov 28, 2015
696
428
Berlin
I am trying to use the bootloader unlocker and it errors out. Says something about network and try again later.

What does this mean exactly? The device has internet and is connected via wifi. Browse and download just fine.

Unlock TF300T
This problem is widely discussed on several forums. Please Google it if you want to unlock your devise. A very helpful way, I think the only one, has been advised by @berndblb in 2015:

1. V8 does not install at all anymore. Keep your hands off. V7 will install if you allow "less secure apps" in your Google account settings. On the web - not your Google account on the tablet!

2. Delete the Google account from the tablet (Settings > Accounts), then run the tool again,

3. If that doesn't do it, do a factory reset from Settings, reboot and during the initial setup establish a WiFi connection but skip the google account setup, then run the tool.

This can be a 5 Minute operation that goes without a hitch or a very frustrating experience with lots of error messages. There is no definite rhyme or reason for this. For some people it works like a charm, for others it works after 15, 25 or 55 attempts, for some never....
To check finally if you are unlocked, boot the tablet and read the tiny script in the left corner above. It should say: “The device is unlocked”.
 

ebonit

Senior Member
Nov 28, 2015
696
428
Berlin
Thanks, I will try to find v7.

Looks like I will never get this to work. v7 = device not supported lol =(

You are welcome! BTW using the thanks button is always a good manner.

What does it mean: "v7 = device not supported lol =" ?
As far as I know all tablets of the transformer family are supported for both unlock apps V7 and V8. So your device as well. You may go ahead as advised above. Then you will see what will be happen.
 

scanno

Senior Member
Mar 27, 2008
2,248
3,810
Arnhem
Redmi K20 Pro
Xiaomi Poco F3
Homebuild versions
The homebuild versions are NOT official versions of OmniROM and are build by myself. The reason for these builds are that some changes are not committed to OmniROM yet and might be interesting for you. One example is the multi-window feature. This feature is not yet included in the nightly builds.

Get the homebuild versions below:

[20141102]
ZIP: https://www.androidfilehost.com/?fid=95784891001605643
MD5: 0bc32700a4ffe5b1a582ef65d61e3307

[20141026]
ZIP: https://www.androidfilehost.com/?fid=95784891001602374
MD5: 92d6880b8ff83f24093741cb5fad5cc5

[20141019]
ZIP: https://www.androidfilehost.com/?fid=95747613655047706
MD5: 4ddbbab50e5d4b0cbdad74f853292593

[20140801]
ZIP: http://www.androidfilehost.com/?fid=23578570567723251
MD5: 35a797a1edf3c47eeb47c66db6b58f67

[20140719]
ZIP: http://www.androidfilehost.com/?fid=23578570567715448
MD5: ee97377d25c01702d96489050de81911

[20140622]
ZIP: http://www.androidfilehost.com/?fid=23501681358551130
MD5: 80e9291f81236ce450738793d617d0d4

[20140615]
ZIP: http://www.androidfilehost.com/?fid=23501681358547511
MD5: efb1c9b8ebd585582d6bd4a497a47971

[20140601]
ZIP: http://www.androidfilehost.com/?fid=23501681358540794
MD5: 2435427c59d05d1299f2fc2c059c61b3

[20140524]
ZIP: http://www.androidfilehost.com/?fid=23501681358538040
MD5: dae4e1499993f1c62def274ae799e2e9

[20140518]
ZIP: http://www.androidfilehost.com/?fid=23487008491965055
MD5: a1565b297318d53315acca9db10a92fe

[20140504]
ZIP: http://www.androidfilehost.com/?fid=23329332407591447
MD5: ed3a6d99e6f494947a8150be6ce1dfbf

[20140421]
ZIP: http://www.androidfilehost.com/?fid=23329332407587884

[20140411]
ZIP: http://www.androidfilehost.com/?fid=23329332407585669
MD5: 9ee8a76dc14d8480630572e366e574c4

[20140323]
ZIP: http://www.androidfilehost.com/?fid=23329332407581120
MD5: 10637148471bd04b45a5b0bf0d77219e

[201403016]
ZIP: http://www.androidfilehost.com/?fid=23329332407579271
MD5: 66d7edd541fc636922fe365aad2cd7fe

[20140309]
ZIP: http://www.androidfilehost.com/?fid=23329332407577368
MD5SUM: b15875f847dc87fad015031e22c38d5a

[20140216]
ZIP: http://www.androidfilehost.com/?fid=23329332407572024
MD5SUM: 94cae5d404727640bec08b5fe5f5f347

[20140212]
ZIP: http://www.androidfilehost.com/?fid=23329332407571011


[20140207]
ZIP: http://www.androidfilehost.com/?fid=23329332407569695
MD5SUM: 89b8317d42dac77bcdd4757760a70393

[20140204]
ZIP: removed
MD5SUM: 85f4b3043ff0bfce49c996d845dc6776

[20140128]
ZIP: http://www.androidfilehost.com/?fid=23329332407567587
MD5SUM: http://www.androidfilehost.com/?fid=23329332407567586

[20140127]
ZIP: http://www.androidfilehost.com/?fid=23329332407567217
MD5SUM: http://www.androidfilehost.com/?fid=23329332407567218
 
Last edited:

scanno

Senior Member
Mar 27, 2008
2,248
3,810
Arnhem
Redmi K20 Pro
Xiaomi Poco F3
Changelist homebuild versions

[20140801]
  • Wifi priority
  • Smartdimmer enabled

[20140719]
  • Synced with upstream changes
  • Settings app now has tablet layout
  • Hotword detection working (OK Google)
  • Cleanup of mountpoints - hopefully solves OTG problems some are having

[20140518]
  • Important kernel security fix
  • Synced and added the latest changes

[20140411]
  • App Circle side bar added (was removed in the previous april build)
  • Updated with the latest merged commits

[20140323]
  • Removed Multi-Window
  • App circle sidebar
  • Floating window (combined with the App Circle sidebar)

[20140309]
  • Synced with the repository
  • No new functionality, just the stuff from the nightly and multi-window

[20140216]
  • Multi Window is back (isolated PS18 and rebased it)
  • New bootanimation (upstream)
  • Power Savings
  • Synced so all other changes that are not listed here

[20140212]
  • Autorotation working
  • Boot animation working

[20140207]
  • OmniSwitch added
  • General sync with repsoitories
  • Temporary removal of Multi-Window due to the fact it is broken at the moment
 
Last edited:

scanno

Senior Member
Mar 27, 2008
2,248
3,810
Arnhem
Redmi K20 Pro
Xiaomi Poco F3
I have a question for the me301t users. I have created a workaround for flashing this rom with TF300T based recovery (CWM, TWRP). When a ROM gets flashed a check is being performed to see if the rom matches the device so the chance of flashing a wrong rom is minimal. But a recovery compiled for the TF300T will check if the rom is ment for the TF300T. This means that a ROM for the me301t will not be flashed because the check will fail (me301t does not equal TF300T).
The workaround adds TF300T to the check so it will not fail.

Part of the Omni build process is also building TWRP so I have a TWRP specific for the me301t. This version is exactly the same as the TF300T version with one exception and that is that the recovery will check for me301t instead if TF300T.

Using the me301t recovery has one disadvantage and that is that roms for the TF300T cannot be flashed anymore. So my question is do we need a separate recovery or use the TF300T one.

Verstuurd vanaf mijn Nexus 10 met Tapatalk
 

krash1256

Senior Member
Oct 7, 2013
245
49
The greatest treat the ME301T users could EVER receive.

I'd be jealous of the ME301T owners if not for your slick TF300T version :D

You are correct sir. It is a great treat.

---------- Post added at 06:31 PM ---------- Previous post was at 06:29 PM ----------

Thank you so much scanno. I really appreciate all your help and hard work. The ME301T has come a long way since I got mine and now I'm very happy with it. :D

---------- Post added at 06:39 PM ---------- Previous post was at 06:31 PM ----------

I have a question for the me301t users. I have created a workaround for flashing this rom with TF300T based recovery (CWM, TWRP). When a ROM gets flashed a check is being performed to see if the rom matches the device so the chance of flashing a wrong rom is minimal. But a recovery compiled for the TF300T will check if the rom is ment for the TF300T. This means that a ROM for the me301t will not be flashed because the check will fail (me301t does not equal TF300T).
The workaround adds TF300T to the check so it will not fail.

Part of the Omni build process is also building TWRP so I have a TWRP specific for the me301t. This version is exactly the same as the TF300T version with one exception and that is that the recovery will check for me301t instead if TF300T.

Using the me301t recovery has one disadvantage and that is that roms for the TF300T cannot be flashed anymore. So my question is do we need a separate recovery or use the TF300T one.

Verstuurd vanaf mijn Nexus 10 met Tapatalk

As far as I'm concerned, I say it's whatever is easiest for you. I'll be happy with either way. :D
 

scanno

Senior Member
Mar 27, 2008
2,248
3,810
Arnhem
Redmi K20 Pro
Xiaomi Poco F3
[/COLOR]Thank you so much scanno. I really appreciate all your help and hard work. The ME301T has come a long way since I got mine and now I'm very happy with it. :D

---------- Post added at 06:39 PM ---------- Previous post was at 06:31 PM ----------



As far as I'm concerned, I say it's whatever is easiest for you. I'll be happy with either way. :D

For now I will not post a separate recovery for the me301t. Perhaps when I am sure that both tf300t and me301t roms can be flashed with it.

Verstuurd vanaf mijn Nexus 10 met Tapatalk
 
  • Like
Reactions: lepa71 and hardslog

julle131

Senior Member
Mar 24, 2011
1,476
606
Are you aware of the bugs yet?
As I love AOSP roms, I have already flashed this one. It appears that auto-rotation is not working yet. I do not have a logcat of this issue, as I do not know how to debug it for you. Checking sensors from Elixir 2 shows that most of the "motion" sensors do not give any feedback.

I have yet to check whether GPS works or not. With GPS test it seems like the devices sees some satellites.
EDIT: GPS is working
 
Last edited:
  • Like
Reactions: scanno

krash1256

Senior Member
Oct 7, 2013
245
49
In the TF300T Omni Rom thread people keep referring to multi window but I'm not seeing any settings for it. Is this something that can only be done on the TF300T? I've also noticed auto rotate doesn't work and that there isn't a setting for that either.

Oh, and one other weird problem I'm having is with usb debugging. When I connect my tablet to my pc not all of the files are showing up on my sdcard. I can see them on the tablet with Root Explorer but not in my pc file manager. Do I need to reformat it coming from 4.3 to 4.4? Or is this just happening to me?
 
Last edited:

krash1256

Senior Member
Oct 7, 2013
245
49
Think i know why the sensors are not working. Proprietary file scripts were not working as it should. Try this build to see if the sensors are working

https://www.androidfilehost.com/?fid=23329332407567766

No, still not working. Oh and I found the auto-rotate settings, it's been moved to accessibility. If anyone else is wondering.


This might not have anything to do with it but just so you know, we were having the same issue with rotation for 4.3 roms on the me301t and nikybiasion and hardslog had to change the sensorservice file in /system/bin/
 
Last edited:

hardslog

Inactive Recognized Contributor
Nov 17, 2009
1,724
2,102
Think i know why the sensors are not working. Proprietary file scripts were not working as it should. Try this build to see if the sensors are working

https://www.androidfilehost.com/?fid=23329332407567766

No, still not working. Oh and I found the auto-rotate settings, it's been moved to accessibility. If anyone else is wondering.


This might not have anything to do with it but just so you know, we were having the same issue with rotation for 4.3 roms on the me301t and nikybiasion and hardslog had to change the sensorservice file in /system/bin/

Nikybiasion said that the problem was that the sensors were being detected as mpu3050 when they are supposed to be mpu6050. Apparently THIS commit was what fixed the auto-rotation.
 

mirrin

Senior Member
Feb 7, 2011
897
157
Oh, yeah, I remember that now.

In addition to the auto rotate bug I have found that the digitizer gets less able to see the touches the longer the tab is running the digitizer is great on reboot but 30min later it barely reads my touches and gets very inaccurate.
 

Top Liked Posts