Bypassing Nintendo Miitomo Root Check and Crash

Search This thread

Azbulldog

Senior Member
Jul 16, 2012
117
46
EDIT: Nintendo is not allowing their Miitomo app to run on Android phones with root, jailbroken iPhones, and some other conditions. The app will crash immediately or shortly after launch. To bypass this on Android phones install Xposed, then install RootCloak and ChrisJosten's Miitomo Bypass modules and reboot your device. Add Miitomo to RootCloak's list of cloaked apps, and be sure to 'Thanks!' ChrisJosten for his help.

Original text:
Tonight Nintendo has first released their Miitomo app exclusively to Japan, however the app apparently already has a full English translation.
Unfortunately it does not appear to run on rooted devices, as reported by a few users here. One user reported success with RootCloak, however others and myself have not had such success. I have a Galaxy S5 with CyanogenMod 13.0. The app starts with a black screen for a second before crashing back to the home screen. Tried clearing any cached data for the app. Any other ideas?
 

Attachments

  • MiitomoSecurituBypasser-1.0.2.apk
    56.5 KB · Views: 4,360
Last edited:
Mar 17, 2016
35
20
Looks to me to be a problem with cyanogen.
Here's an interesting line in the debug:
03-17 11:51:55.399 8036 8036 I art : Thread[1,tid=8036,Native,Thread*=0xb4d76500,peer=0x74f993b0,"main"] recursive attempt to load library "/data/app/com.nintendo.zaaa-2/lib/arm/libNuanceVocalizer.so"
03-17 11:51:55.618 8036 8036 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 8036 (m.nintendo.zaaa)
03-17 11:51:55.618 253 253 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
03-17 11:51:55.618 253 253 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
03-17 11:51:55.618 253 253 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
03-17 11:51:55.671 813 1584 D NetlinkSocketObserver: NeighborEvent{elapsedMs=68823126, 192.168.32.1, [544A009C3344], RTM_NEWNEIGH, NUD_STALE}
03-17 11:51:55.720 253 253 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-17 11:51:55.720 253 253 F DEBUG : Build fingerprint: 'oneplus/bacon/A0001:5.1.1/LMY48B/YOG4PAS1N0:user/release-keys'
03-17 11:51:55.720 253 253 F DEBUG : Revision: '0'
03-17 11:51:55.720 253 253 F DEBUG : ABI: 'arm'
03-17 11:51:55.720 253 253 F DEBUG : pid: 8036, tid: 8036, name: m.nintendo.zaaa >>> com.nintendo.zaaa <<<
03-17 11:51:55.720 253 253 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
03-17 11:51:55.739 253 253 F DEBUG : r0 00000000 r1 00001f64 r2 00000006 r3 00000000
03-17 11:51:55.739 253 253 F DEBUG : r4 b6fcdb88 r5 00000006 r6 b6fcdb38 r7 0000010c
03-17 11:51:55.739 253 253 F DEBUG : r8 12ca4180 r9 b4d76500 sl 12c62c30 fp 70f4d6b0
03-17 11:51:55.739 253 253 F DEBUG : ip 00000000 sp beb02ef8 lr b6d1a42d pc b6d1cb90 cpsr 200d0010
03-17 11:51:55.745 253 253 F DEBUG :
03-17 11:51:55.745 253 253 F DEBUG : backtrace:
03-17 11:51:55.745 253 253 F DEBUG : #00 pc 00049b90 /system/lib/libc.so (tgkill+12)
03-17 11:51:55.745 253 253 F DEBUG : #01 pc 00047429 /system/lib/libc.so (pthread_kill+36)
03-17 11:51:55.745 253 253 F DEBUG : #02 pc 0001bbc3 /system/lib/libc.so (raise+10)
03-17 11:51:55.745 253 253 F DEBUG : #03 pc 0001846d /system/lib/libc.so (__libc_android_abort+36)
03-17 11:51:55.745 253 253 F DEBUG : #04 pc 000164cc /system/lib/libc.so (abort+4)
03-17 11:51:55.745 253 253 F DEBUG : #05 pc 009bf848 /data/app/com.nintendo.zaaa-2/lib/arm/libcocos2dcpp.so (Java_jp_co_nintendo_NativeSystem_nativeAbort+8)
03-17 11:51:55.745 253 253 F DEBUG : #06 pc 011218fd /data/app/com.nintendo.zaaa-2/oat/arm/base.odex (offset 0x985000)
03-17 11:51:56.064 253 253 F DEBUG :
03-17 11:51:56.064 253 253 F DEBUG : Tombstone written to: /data/tombstones/tombstone_03
03-17 11:51:56.064 253 253 E DEBUG : AM write failed: Broken pipe
 
Last edited:

SeeinNarnia

New member
Mar 17, 2016
2
0
Android N develop a no-go too

On launch of miitomo if running the android N developer preview you get a gray screen and that's it
 

xhead12

New member
Dec 3, 2013
3
0
Galaxy S4 Resurrection Rom
Rooted - Crash
Un-rooted - Crash
Root Cloak - Crash

Nexus 10 CM13
Rooted - Crash
Un-rooted - Crash
Root Cloak - Crash

Galaxy S2 Stock
Crash

Literally cant get any device to work.
 

Azbulldog

Senior Member
Jul 16, 2012
117
46
Thanks for the responses. I mean I wouldn't be surprised if Nintendo wanted to prevent cheating, but if this is a more widespread issue it might get fixed legitimately.
 

Incineroar

Senior Member
Sep 24, 2012
557
106
pushingbuttons.tech
I'm using my Alcatel OT Idol X with Slimkat 4.4.2 and I'm getting crashes on both rooted and cloaked Miitomo. I haven't tried my other devices yet, but I doubt they'll fare out well.
 

ryandanger

Member
Feb 9, 2016
34
4
Perth
app was crashing on my rooted Nexus 5X running stock 6.0.1, with ElementalX Kernel. All I did to fix it was use RootCloak and add Miitomo to the list. Bang, straight into the game :)
 
Last edited:

Firipu

Senior Member
Mar 7, 2011
258
52
Nexus 5x - Systemless Root - Purenexus - Franco Kernel

Crashes every time.

Works fine on my wife's stock Samsung 5.
 

zelendel

Senior Member
Aug 11, 2008
23,371
20,605
OnePlus 6T
Samsung Galaxy S21 Ultra
More and more apps are refusing to run on rooted devices. This should not be surprising. Some are even looking for xposed and monitoring the forums here to see how people are getting around it so they can block it.
 

drfsupercenter

Senior Member
Aug 21, 2010
84
14
Can confirm... I have a Motorola Droid 4 running CM11 and it crashes.

I tried updating to CM13 nightly, still crashes.

I tried disabling root from within CM, still crashes.

I went back to stock (rooted), still crashes.

I used superSU to unroot stock, it loaded.

This is infuriating, at least with Pokémon Shuffle it would load and let you play and just stop you from doing tournaments due to being rooted. This fake app crash GS is annoying. Someone needs to fix this :/
 

zelendel

Senior Member
Aug 11, 2008
23,371
20,605
OnePlus 6T
Samsung Galaxy S21 Ultra
Can confirm... I have a Motorola Droid 4 running CM11 and it crashes.

I tried updating to CM13 nightly, still crashes.

I tried disabling root from within CM, still crashes.

I went back to stock (rooted), still crashes.

I used superSU to unroot stock, it loaded.

This is infuriating, at least with Pokémon Shuffle it would load and let you play and just stop you from doing tournaments due to being rooted. This fake app crash GS is annoying. Someone needs to fix this :/
Well see that's the thing is that it is not broken. Root is a security risk and an issue for game developers even Google is making root harder to get on Many devices and sooner or later unless you have a nexus root may not even be an option.
 

drfsupercenter

Senior Member
Aug 21, 2010
84
14
That's just stupid, I use root for things like taking backups of my phone, not hacking stupid games to begin with.

I do find it funny how the first thing that comes to people's mind when you tell them you have a rooted/jailbroken phone is that you must be some kind of pirate. You don't even need root to install .apks, and most people don't know enough to actually hack games like that anyway. (Pro tip: the leaderboards are kept server-side, it's not as simple as just modifying your data files)
 

zelendel

Senior Member
Aug 11, 2008
23,371
20,605
OnePlus 6T
Samsung Galaxy S21 Ultra
That's just stupid, I use root for things like taking backups of my phone, not hacking stupid games to begin with.

I do find it funny how the first thing that comes to people's mind when you tell them you have a rooted/jailbroken phone is that you must be some kind of pirate. You don't even need root to install .apks, and most people don't know enough to actually hack games like that anyway. (Pro tip: the leaderboards are kept server-side, it's not as simple as just modifying your data files)
Well see the thing is root makes those things possible. There are apps that use root to hack the games. I won't mention them here as they are banned. Also it's not the leader boards they are worried about. It's things like in app purcheses.

You have to understand there are very real risks with root. An app can get granted root and do all types of things including ransom based viruses.


It's just something you will have to get used to. The older android gets the harder root will be to get.
 

drfsupercenter

Senior Member
Aug 21, 2010
84
14
I'm sure there will always be ways. While 99% of users don't need root abilities, there are those of us who are power users who have an actual use for it.

Even the newest phones have root exploits (I hate that word exploit, sure it's exploiting a locked-down system arbitrarily set by the manufacturer, but we should be able to do it like a real machine and choose if we want to allow root access or not!).... looks like the S7 has one already.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 31
    I've made a Xposed module (it's also my first module) that should bypass the Miitomo root check, you can download both the source and apk from Dropbox

    EDIT: I've updated both the sources and APK to fix the IllegalAccessError, for me it works on all of my devices now
    12
    EDIT: Nintendo is not allowing their Miitomo app to run on Android phones with root, jailbroken iPhones, and some other conditions. The app will crash immediately or shortly after launch. To bypass this on Android phones install Xposed, then install RootCloak and ChrisJosten's Miitomo Bypass modules and reboot your device. Add Miitomo to RootCloak's list of cloaked apps, and be sure to 'Thanks!' ChrisJosten for his help.

    Original text:
    Tonight Nintendo has first released their Miitomo app exclusively to Japan, however the app apparently already has a full English translation.
    Unfortunately it does not appear to run on rooted devices, as reported by a few users here. One user reported success with RootCloak, however others and myself have not had such success. I have a Galaxy S5 with CyanogenMod 13.0. The app starts with a black screen for a second before crashing back to the home screen. Tried clearing any cached data for the app. Any other ideas?
    7
    Version 1.0.5 attached

    Code:
    Version	short description			for Miitomo Version
    1.0.5	improve build, fix Xposed illegal	1.2.0 - 1.2.2
    	access issues for some users

    Thanks, it works with the new update for me. However I still get the problem I posted about previously, the gift box, miitomo news, and any other act that connects to the server still crashes my app. Even the shop. But actually hearing questions and answers works like normal. Does still stuff work for anyone? Any idea if that's able to be fixed?

    It works for me as it should. Did you grant Storage permissions to Miitomo in Settings > Apps > Miitomo > Permissions? Else we don't know anything without a logcat.

    Both 1.0.3 and 1.0.4 have this problem. So I cannot use it. I quoted my post as it contains a useful link.
    (Basically don't include XposedBridge classes in the apk)

    Fixed in 1.0.5

    I tried new version in Nox emulator but it doesn't work.

    MiitomoSecurityBypasser 1.0.2 worked with previous version of Miitomo, but with this update it stopped and version 1.0.4 of bypasser doesn't fix it, at least in my case.

    You still need 1.0.2 for Miitomo up to 1.1.3. Newer versions of the module are only for Miitomo 1.2.0 or newer.
    6
    Ahaha, great work ! I just finished fixing it here, I tried it and was about to share it temporarily until your next update.
    Thanks a lot !

    So, since I had a look at the source code, I'm pretty curious right now : what exactly are the multiples ways Miitomo detect root ? And why in the world does it think my phone is an emulator XD ?

    Anyway, that means Nintendo didn't want rooted users to play his games, which is pretty bad news. Blocking IAP or something like that was enough, I guess.
    Well, it is using a library to detect root (no idea which, but the package name is jp.dena.securelib). The library was checking for the following apps:
    Code:
    com.noshufou.android.su
    com.thirdparty.superuser 
    eu.chainfire.supersu
    com.koushikdutta.superuser
    com.zachspong.temprootremovejb
    com.ramdroid.appquarantine
    The library also checks for the following files:
    Code:
    /system/bin/su
    /system/xbin/su
    /sbin/su
    /system/su
    /system/bin/.ext/.su
    /system/usr/we-need-root/su-backup
    /system/xbin/mu
    It also checks via reflection if 'ro.debuggable' in the build.prop is equals to 1:
    Code:
    Method method = Class.forName("android.os.SystemProperties").getMethod("get", new Class[]{String.class});
    return "1"..equals(method.invoke(null, new Object[]{"ro.debuggable"}));
    When the application starts up, if one of the first two conditions are met, it will call 'NativeSystem.nativeAbort()' which is a native method that presumably crashes the application.

    The third one gets also called, but I have no idea when and where, what I do know is that it crashes the app too :(
    5
    Greetings, everyone!

    I cannot wait so I made one on my own based on @ChrisJosten 's xposed module source. Updating those xposed hooked method works.
    But I couldn't find logging method any more. So we could not steal the logcat for now. Just enjoy the game :)

    Tested on v1.2.2

    P.S. And I change the version code to v1.0.3
    Both the Apk and the updated source available here