yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] zelendel:
Some of the apps have even been found in the playstore. Google recently removed alot of them that did alot of the things i mentioned. There is even a well known SMS app that has a built in keylogger. But as the country where the app is developed allows this there is nothing anyone really can do.

Games dont like it because most of them use IAP which with the right app (a root required app that I wont mention) this can be bypassed and the developers lose money. You could use root to get all the paid unlockable items without paying for them.

Think about it this way. Screen presses are nothing more then readings by the OS. So an APP could request SU and then before displaying the SU prompt it simulates the grant key press. This way auto granting root access without the user ever seeing it.

I dont want you to think that doing this is by any means easy. Just info on the fact that it can be done.
[Android Q&A, Help & Troubleshooting] drfsupercenter:
Yes, I'm well aware of ripping off IAPs. But devs have their own way of countering it, some games I've seen keep the counter of coins/plays/whatever on their own servers, so even if you try to edit your data to make it think you have more, it will "phone home" and fix itself anyway.

That's a bit scary. I suppose it's why some of the newer root management apps have a PIN option so it's not as simple as just hitting allow. Also, CM11's built in one makes you wait ~5 seconds before allowing, so you'd notice if an app was trying to simulate a keypress like that.

I suppose I answered my own question though - the /system folder is readable by nonprivileged users, you just can't write to it without root. On the other hand, I think /data itself is locked off so you can't even view it.

Anyway, I got some logcats. I see some strange stuff...

W/InputDispatcher( 521): Attempted to unregister already unregistered input channel '42321fc8 com.nintendo.zaaa/jp.co.nintendo.AULActivity (server)'

I/WindowState( 521): WIN DEATH: Window{42321fc8 u0 com.nintendo.zaaa/jp.co.nintendo.AULActivity}

Will have to poke around some more. I opened it three times and let it crash so I can see what's the same and what's not.

Also, lots of activity about Facebook trying to access permissions it doesn't have. My fault, I modified the .apk so it can't take over my phone (no root required, I literally rebuilt the installer). :P
[Android Q&A, Help & Troubleshooting] LuigiBlood:
So I have CyanogenMod 11 for HP Touchpad (tenderloin), Miitomo isn't working either.

I wanted to try RootCloak, but it isn't loading on Xposed. (IllegalAccessError)

I also unrooted CM11 with SuperSU with that complete unroot option (which indeed removed root access, I should mention, no matter how you set it in the developer settings), and Miitomo isn't working.

This is kind of embarassing because most of my devices are under Android 4.1 (there are no official updates), and I don't feel like buying a phone, or even a new tablet (my HP Touchpad was always fine) for this. D:

Hoping someone would find a way to get it to work.
[Android Q&A, Help & Troubleshooting] BloodRose:
It's crashing on my unrooted Elephone P7000 running the stock firmware.

I have double checked and the device definitely isn't rooted. If it was then my banking app and a couple of others wouldn't work anyway.
[Android Q&A, Help & Troubleshooting] pkgingo:
What I noticed is that in the log, after the crash EGL (open gl es) finally gets initialized. I think they are not waiting for it to finish init before using it. Root cloak might very well be delaying the thread long enough for this to work. Not sure how we can delay the main app thread a bit as a hack to allow it to start up.
[Android Q&A, Help & Troubleshooting] harsh2909:
I am a shuffle player and I always see hackers hacking their way to leaderboard of competition.

I need to unroot to get access in competition
[Android Q&A, Help & Troubleshooting] ThatKawaiiGuy:
The app worked on my LG V10 on stock with RootCloak, however going on CM today the app refuses to function, even with RootCloak.
[Android Q&A, Help & Troubleshooting] KevinX8:
From further looking into this I can concur that the app checks if your build keys match your build number (only stock can change build keys) and so Custom roms are a no go. Also it those have a root checker but root cloak works just fine in blocking it. Also it seems anyone not running android 6.0 is running into problems as even thought it supports 4.1 and above in its manifest, it seems to only work on 6.0. So in conclusion, to run miitomo you must be running a phone with stock 6.0.1 rom, unrooted or rooted but with root cloak for the app to work
[Android Q&A, Help & Troubleshooting] LuigiBlood:
I've looked fast into it and basically, yes, there are checks.

Root check is stupidly simple, it just checks packages and executables based on this: https://blog.netspi.com/android-root-detection-techniques/

However there is another check used in isEmulator(): it checks if ro.debuggable is 1, and in that case it seems to loop itself?

So try to disable ro.debuggable if you can.
[Android Q&A, Help & Troubleshooting] KevinX8:
tried that only disabled root but miitomo still crashed. Seeing as it checks if you have test keys or not you could try and forge some keys to match your build number
[Android Q&A, Help & Troubleshooting] LuigiBlood:
I have no idea how to do that.
[Android Q&A, Help & Troubleshooting] KevinX8:
yeah like I said custom roms will just not work until someone creates a way to bypass all the miitomo checks. Until then stick to a stock 6.0 device with root cloak. Also custom kernels don't seem to matter as my nexus 7 2013 seems to be running miitomo fine with only root cloak
[Android Q&A, Help & Troubleshooting] FyrusCarmin:
Well I suppose that's also the reason why it worked on Darkobas yet failed on Dirty Unicorns. Darkobas is more close to AOSP than this.

Guess I'll have to dual boot for the time being.
[Android Q&A, Help & Troubleshooting] zelendel:
That is not really true as DU is built directly from AOSP.
[Android Q&A, Help & Troubleshooting] FyrusCarmin:
Hmm what could cause this crash then, I'm not really tech savvy on the matter to be honest

Envoyé de mon A0001 en utilisant Tapatalk
[Android Q&A, Help & Troubleshooting] smvb64:
Hey, I have a Nexus 4 stock with root (4.4)and the app crashes with root cloak enabled. From what I can tell from the thread, it's only working on 6.1 with root, plus RC?
[Android Q&A, Help & Troubleshooting] KevinX8:
6.0.1 full aosp and yeah or just stock

However I did test it on a htc m8s and it worked fine but that's only running 5.0.2 so yeah (no root) but others are reporting even on full stock they can't get app to launch
[Android Q&A, Help & Troubleshooting] HenkKalkwater:
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
[Android Q&A, Help & Troubleshooting] AmineI:
Is it safe, had someone already tried it ? I'm a bit sceptical about that. Thank you anyway
[Android Q&A, Help & Troubleshooting] Dimpap28:
It works! I'm on 6.0.1 custom ROM with RootCloak (don't know if it plays a role). Before it crashed, now it doesn't!
[Android Q&A, Help & Troubleshooting] LuigiBlood:
Unfortunately for me I get IllegalAccessError in the Xposed log. I really wish I could get this working but I'm really unlucky.

EDIT: Okay I just got to know how to fix my problem it seems, the APK is apparently done wrong:

http://xdaforums.com/showpost.php?p=48500265&postcount=6879

You shouldn't include the XposedBridge JAR in it apparently.
[Android Q&A, Help & Troubleshooting] KevinX8:
Yeah must suck for you works fine for me. What rom and device you have?
[Android Q&A, Help & Troubleshooting] AmineI:
How does it work ? What is bypassed here ? Root detection ? Supersu detection ? Rootcloak detection ? How did you find the problem ?

---------- Post added at 06:19 AM ---------- Previous post was at 05:55 AM ----------

I finally tried the module, same problem here. 4.2.2 stock, Samsung, and rootcloak also show an illegalaccess exception
[Android Q&A, Help & Troubleshooting] Azbulldog:
Thank you for taking the time to make the module, but it still crashes for me on the device described in the OP.

I think this is a complete log.

http://pastebin.com/GsikD5qz
[Android Q&A, Help & Troubleshooting] LuigiBlood:
Running ROM 'cm_tenderloin-userdebug 4.4.4 KTU84Q 865aede3dd test-keys' with fingerprint 'hp/hp_tenderloin/tenderloin:4.4.4/KTU84P/1227136:user/release-keys'

Basically it's a HP Touchpad with CyanogenMod 11. I'm not planning to move from CM11 because it seems all the others are pretty unstable. And I want to stay on the stable one because I'm not the only one using it.

EDIT: I should mention that rootcloak2 also does the same thing, but not the original rootcloak which just works apparently. (That said Miitomo still won't boot)
[Android Q&A, Help & Troubleshooting] KevinX8:
yeah you have an x86 device so xposed is a whole different story there also it is technically a pc and those not boot like a normal android so that might interefere with xposed modules working
[Android Q&A, Help & Troubleshooting] LuigiBlood:
Nah it's ARM-based. It's a tablet. It's maybe not booting like a normal Android but yet the original Rootcloak works.
[Android Q&A, Help & Troubleshooting] KevinX8:
Just realised something root cloak 2 is for android 5.0 + so yeah thats why it ain't working. So maybe that miitomo root block has the same story
[Android Q&A, Help & Troubleshooting] LuigiBlood:
It's supposed to work on 4.4.4. It's said to be tested on HTC One GPE - 4.4.x on the page.
[Android Q&A, Help & Troubleshooting] VictorLandim:
I report that it works for me too! I have a LG G3 running Dirty Unicorns and root cloak. It crashed but now it works! Thanks a lot.
[Android Q&A, Help & Troubleshooting] FyrusCarmin:
Works perfectly on Bacon with Dirty Unicorns
[Android Q&A, Help & Troubleshooting] LuigiBlood:
So I just tried APK tool with the APK and I guess those classes are present just like that post, where it isn't supposed to happen?

I don't get why it does not work for me while it works for others.

EDIT: All the Xposed modules I've tried, RootCloak original does not include those classes, and I can definitely say it's working.

RootCloak2 includes those classes, just like that Miitomo module, and does not load in my case.
[Android Q&A, Help & Troubleshooting] AmineI:
I'm in the same state as you, with a stock ROM however. I think I'll try to recompile the apk for us in Android Studio without these classes,if I understand what i should do exactly (Never touched anything Xposed related in development, I'll read the documentation i guess).
[Android Q&A, Help & Troubleshooting] LuigiBlood:
I guess this reddit post may help you? https://www.reddit.com/r/xposed/comments/2sfdjx/help_basic_xposed_tutorial_causes/
[Android Q&A, Help & Troubleshooting] Dinjoralo:
Sorry for not contributing, but neither the Xposed module posted here or rootCloak are letting me run Miitomo on my Galaxy S4 with Cyanogen. Hopefully, this gets sorted out before the worldwide release...
[Android Q&A, Help & Troubleshooting] LuigiBlood:
Did you check the Xposed Log? Does it have IllegalAccessError?
[Android Q&A, Help & Troubleshooting] Dinjoralo:
Yeah, I'm seeing that for the Miitomo module. So whatever problem everyone else is having with the module, I'm having it, too.
[Android Q&A, Help & Troubleshooting] AmineI:
Hey, may I have your permission to edit and recompile your module ?

Of course, I won't say that it's my work.
[Android Q&A, Help & Troubleshooting] HenkKalkwater:
Thank! I've now updated the build, so it should work now.
[Android Q&A, Help & Troubleshooting] LuigiBlood:
Just tested, it boots fine! Thank you very much!
[Android Q&A, Help & Troubleshooting] AmineI:
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.
[Android Q&A, Help & Troubleshooting] HenkKalkwater:
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:

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:

/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:

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 :(
[Android Q&A, Help & Troubleshooting] AmineI:
After somes searches, here's what i gathered :

It's not a library, it's hardcoded in jp.dena.securelib, by a simple "haspackages" check, which mentions everything you said

Aaaand it looks like that adb access is checked too :0 . I'm not sure, but I guess that explains why my RemixOS PC got the app crashed, without root, and why rootcloak isn't working for some peoples..
[Android Q&A, Help & Troubleshooting] Azbulldog:
So is ro.debuggable the only thing holding it back?
[Android Q&A, Help & Troubleshooting] Dinjoralo:
Hooray, it's working for me! Now to wait for the worldwide launch... I just wanted to make sure it worked on my device first.

Say, if Miitomo was updated, would the Xposed module need to be adjusted to suit it?
[Android Q&A, Help & Troubleshooting] japzone:
Can confirm it working on CyanogenOS 12.1(Android 5.1.1), Rooted with SuperSU, Custom Kernel, and Xposed Framework installed.

PS: Your link is missing the period in "dropbox.com". Here's the fixed link for those that need it.
[Android Q&A, Help & Troubleshooting] Manu-M3:
For me it still doesnt work. (Meizu MX5 with Root, Xposed - Root Cloak & your Miitomo Bypasser).

Still crashes.

Edit: Got it working after a reinstall. Thanks!
[Android Q&A, Help & Troubleshooting] japzone:
Have you tried the Xposed module ChrisJosten posted? I linked to it in the post above yours.
[Android Q&A, Help & Troubleshooting] AmineI:
I think it could be needed only on some cases : It depends on Nintendo's choice, if they :

1 - launch the app globally with another package name, but that would be a one-time really small & easy update. It's possible however, since I spotted a lot of "jp.xxxxx.xxxx" packages names in the app.

2- Implement new root detection system. They could even have delayed the global launch to see the developers & community reaction to their root blocking thing.

3- Spotted us and blocked this module. Actually, this is the 1st result to googling "Miitomo root" soooo, a simple search and they're aware of that, if they aren't already

Anyway, next Miitomo update is already announced within the app, so let's wait to see if something has changed :D
[Android Q&A, Help & Troubleshooting] fernandogdl:
i have a MTK device with stock rooted 4.4 kitkat, and have this same issue, but i tried miitomo on a Moto X (2013) with stock lollipop and no root, and it works flawlessly
[Android Q&A, Help & Troubleshooting] HouseBreaker:
Your module is working perfectly on Moto G 2014 with CM13, SuperSU and Xposed!

off topic: Is it possible to make an xposed module which redirects the cache away from /data? Currently it puts it in the app data and that's about 500MB on the /data partition.

I decompiled the apk and checked it out briefly and it uses the Environment.getExternalStorageDirectory() to set that path which is supposed to be either the SD card or internal SD card but it still keeps it in /data?
[Android Q&A, Help & Troubleshooting] AmineI:
Eehhh, I'm not quite sure that those 500mb uses .getExernalStorageDirectory.

However, I myself have a small disk phone and Miitomo is eating all my memory, so I already thought of this. Even if I'm still searching a way to do this, I think it's a bad idea :

Have you played the game yet ? If so, Do you see some lags during dialogs ? Imagine 10x worse ; it's the performance it'll have if we move that data to an sd card. And even worse if your sd isn't high-speed :/
[Android Q&A, Help & Troubleshooting] HouseBreaker:
In my opinion, I would take that over the unnecessary storage hog. The possibility is what matters, whether people wanna use it is up to them!

Just now I tried the naive approach i.e. both mount the res folder I moved to my SD card and symlink it and all that did is give me a nintendo-style error code 801-9999 which I don't know how to fix (apart from deleting cache which people were recommending and didn't work), but I'll try to get it working somehow.
[Android Q&A, Help & Troubleshooting] SirGustav:
The module is working perfectly on LG G3 Beat (D722p) with CM13! Thank you!
[Android Q&A, Help & Troubleshooting] smvb64:
Module working fine on my Nexus 4 stock with root!

Huge thanks man
[Android Q&A, Help & Troubleshooting] xhead12:
03-23 17:06:18.499 F/DEBUG ( 239): Revision: '0'
03-23 17:06:18.499 F/DEBUG ( 239): ABI: 'arm'
03-23 17:06:18.499 F/DEBUG ( 239): pid: 5121, tid: 5162, name: GLThread 381 >>> com.nintendo.zaaa <<<
03-23 17:06:18.499 F/DEBUG ( 239): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
03-23 17:06:18.537 F/DEBUG ( 239): Abort message: 'PRODUCTION: Adjust is running in Production mode. Use this setting only for the build that you want to publish. Set the environment to `sandbox` if you want to test your app!'
03-23 17:06:18.537 F/DEBUG ( 239): r0 00000000 r1 0000142a r2 00000006 r3 00000000
03-23 17:06:18.537 F/DEBUG ( 239): r4 9dd19980 r5 00000006 r6 9dd19930 r7 0000010c
03-23 17:06:18.537 F/DEBUG ( 239): r8 ffffe1e8 r9 ffdf1c61 sl 12ffe090 fp 00000000
03-23 17:06:18.538 F/DEBUG ( 239): ip 00000002 sp 9dd190e0 lr b6c9f445 pc b6ca1ba8 cpsr 200f0010
03-23 17:06:18.580 F/DEBUG ( 239):
03-23 17:06:18.580 F/DEBUG ( 239): backtrace:
03-23 17:06:18.580 F/DEBUG ( 239): #00 pc 00049ba8 /system/lib/libc.so (tgkill+12)
03-23 17:06:18.580 F/DEBUG ( 239): #01 pc 00047441 /system/lib/libc.so (pthread_kill+36)
03-23 17:06:18.580 F/DEBUG ( 239): #02 pc 0001bbe3 /system/lib/libc.so (raise+10)
03-23 17:06:18.581 F/DEBUG ( 239): #03 pc 0001848d /system/lib/libc.so (__libc_android_abort+36)
03-23 17:06:18.581 F/DEBUG ( 239): #04 pc 000164ec /system/lib/libc.so (abort+4)
03-23 17:06:18.581 F/DEBUG ( 239): #05 pc 009cc1c8 /data/app/com.nintendo.zaaa-1/lib/arm/libcocos2dcpp.so
03-23 17:06:18.581 F/DEBUG ( 239): #06 pc 009cbc7c /data/app/com.nintendo.zaaa-1/lib/arm/libcocos2dcpp.so
03-23 17:06:18.581 F/DEBUG ( 239): #07 pc 009cb1c4 /data/app/com.nintendo.zaaa-1/lib/arm/libcocos2dcpp.so
03-23 17:06:18.581 F/DEBUG ( 239): #08 pc 00359aec /data/app/com.nintendo.zaaa-1/lib/arm/libcocos2dcpp.so
03-23 17:06:18.581 F/DEBUG ( 239): #09 pc 00b0bb01 /data/app/com.nintendo.zaaa-1/lib/arm/libcocos2dcpp.so (cocos2d::Application::run()+8)
03-23 17:06:18.583 F/DEBUG ( 239): #10 pc 00b0d7b5 /data/app/com.nintendo.zaaa-1/lib/arm/libcocos2dcpp.so (Java_org_cocos2dx_lib_Cocos2dxRenderer_nativeInit+256)
03-23 17:06:18.583 F/DEBUG ( 239): #11 pc 0117f0d5 /data/app/com.nintendo.zaaa-1/oat/arm/base.odex (offset 0x99b000)
03-23 17:06:19.473 F/DEBUG ( 239):
03-23 17:06:19.473 F/DEBUG ( 239): Tombstone written to: /data/tombstones/tombstone_05
03-23 17:06:19.473 E/DEBUG ( 239): AM write failed: Broken pipe

S4 6.0.1 rootcloak + xposed mod. not sure whats going on.
[Android Q&A, Help & Troubleshooting] AmineI:
Can you try to disable usb debugging, please ?
[Android Q&A, Help & Troubleshooting] xhead12:
It wasn't on when i went to dev options. tried it with usb debugging on and off still crashes. same tombstone error.
[Android Q&A, Help & Troubleshooting] luxemas:
Hey so... just figured I'd mention a little discovery after watching this thread for the past couple days (much thanks to all your guys' sleuthing, something I'd be lost trying myself otherwise) and I'd been trying out loading Miitomo on various versions of Android builds on my Nexus 7 tablet. However I figured as shot in the dark, I'd see if using the Xposed module supplied earlier if I could get the thing to work on a Windows androind emulator aaaaaaand...

(Sorry for the lame way of link sharing. 10 post limit to prevent spam but anyway)

http : // i . imgur . com / Sj4HcOp . png

Presto, it happens to run quite flawlessly. At least in using the Nox App player (its using Android version 4.4.3 if I remember correctly) so... yeah, for those having issues getting it to run on a specific piece of hardware, I had relative ease and success going this route.
[Android Q&A, Help & Troubleshooting] japzone:
Not sure about requiring Google Play framework, but it definitely uses Google Play for IAP and a couple other things. And judging by, "Both Google Play Services and legacy GSF package are missing", I'd say that it indeed might need to have GApps installed. At the very least the framework and store.
[Android Q&A, Help & Troubleshooting] KevinX8:
For goodness sake has anyone heard of pastebin? Pouring your whole log onto the forum makes it impossible to navigate! At least make it hidden
[Android Q&A, Help & Troubleshooting] Azbulldog:
Are they not enclosed in a code box with its own scroll bar? Is that a Tapatalk thing?
[Android Q&A, Help & Troubleshooting] KevinX8:
I'm using XDA labs and no but a lot of other guys didn't even bother with that
[Android Q&A, Help & Troubleshooting] PokeParadox:
Just a heads up... I continued to have the "crash" with CM12.1 on S4 Mini with RootCloak, Xposed and the updated Xposed module in this thread.

I was using the 1.0.0 release of the APK.

I updated Miitomo to the 1.0.2 APK file and it is now working.
[Android Q&A, Help & Troubleshooting] herzblutnord:
Works perfectly thanks to the updated xposed module and rootcloak on my oppo find 7a with official CM13 android 6.0.1, thank you guys so much!
[Android Q&A, Help & Troubleshooting] Azbulldog:
Didn't realize there was an updated Miitomo APK, I thought it was only a module update. It works now, thanks!
[Android Q&A, Help & Troubleshooting] heahmad:
anyone interested to be miitomo friend
[Android Q&A, Help & Troubleshooting] japzone:
Only way you can Friend remotely is if you are already friends on Facebook or Twitter and link those accounts to Miitomo. Other than that there is only the "Face-to-Face" friending method where you have to be physically near each other.
[Android Q&A, Help & Troubleshooting] Scratch.:
Worked on my Nexus 5 MIUI7

Thanks a heap!
[Android Q&A, Help & Troubleshooting] ACE_CLOUD:
Hi guys, I'm running version 5.1.1 rooted on my note 4. I downloaded the bypasser apk, installed it but still crashes. Keeps giving me "unfortunately..." error. Any clues why?
[Android Q&A, Help & Troubleshooting] KevinX8:
Um you got xposed right? Get the unofficial one for Samsungs on the xposed forum if no
[Android Q&A, Help & Troubleshooting] MichMasteR:
Not working for me in a LG G3 :/

And got this, means I can't use it in this phone?
[Android Q&A, Help & Troubleshooting] KevinX8:
Um check xposed log what's your rom and do you have root cloak?
[Android Q&A, Help & Troubleshooting] MichMasteR:
You wont believe how stupid this will sound but how do i confirm my rom?
[Android Q&A, Help & Troubleshooting] KevinX8:
Well the question is if you have a custom rom at all and if not what android version are you on (it's under about phone in settings)
[Android Q&A, Help & Troubleshooting] MichMasteR:
Its is in 5.0.1 Lollipop