yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] G4 Man2:
Miitomo now allows root but will not run on some custom roms like CyanogenMod without this module.
[Android Q&A, Help & Troubleshooting] m-p{3}:
Is Miitomo 1.1.3 still working with Rootcloak and the MiitomoSecurityBypass module?
[Android Q&A, Help & Troubleshooting] Doopliss:
1.1.3 still works on my Nexus 5 CM13 with just MiitomoSecurityBypass.
[Android Q&A, Help & Troubleshooting] xdavn.com:
:d:d:d:d:d:d:d:d:d:d:d:d:d
[Android Q&A, Help & Troubleshooting] Radium3D:
Miitomo is still not working on my OnePlus One with CM13 Nightly 2016-04-15. I never installed xposed or any of the other root cloaking scripts/apps and I have root set as disabled in developer options.
[Android Q&A, Help & Troubleshooting] DJ_Tomato:
I want to play miitomo, my phone is Xiaomi MI4C, i have MIUI 7.2 (Android 5.1.1)

but i don't want to install xposed

https://play.google.com/store/apps/details?id=com.nintendo.zaaa

but game crash after opening, i don't have root or custom rom, no locked bootloader either

I can't run it ;_;
[Android Q&A, Help & Troubleshooting] Hobox10:
When I try to open the giftbox or shop the app crashes, but otherwise it is fine. Any ideas?
[Android Q&A, Help & Troubleshooting] Hobox10:
I've realized it's not just the shop but anything that connects to things like buying items in the shop, playing the mini games for items, when it gets the miitomo news, or anything account related in addition to the gift box. Like it is failing some sort of specific server authentication. But before installing the miitomo root bypasser it didn't work at all so the app is working at least partially. I tried googling for other people saying they have the same issue but nothing comes up.
[Android Q&A, Help & Troubleshooting] legendt:
It seems last update v1.2.0 break this module. :(
[Android Q&A, Help & Troubleshooting] thejedimex:
hopefully it gets fixed soon
[Android Q&A, Help & Troubleshooting] NativeCain:
I can confirm that.

It's right back to crashing immediately like it did originally.
[Android Q&A, Help & Troubleshooting] Setialpha:
Yep isEmulator() and then crash. When unrooted and dev opts off, no crash, but return to Launcher.

You can dl 1.1.3 from apkmirror for now. Big N does not (yet) force the new version.
[Android Q&A, Help & Troubleshooting] micro17:
Tis is just ridiculous. I will keep my one * review on Google play updated until they remove that crap.

You should do that too ;)
[Android Q&A, Help & Troubleshooting] xstahsie:
Yep Miitomo v1.2.0 is not compatible with Miitomo security bypasser v1. 0.2. Force closes.
[Android Q&A, Help & Troubleshooting] Chris-woods:
Force close in latest version with Root cloack and miitomo bypasser

Hope it get fix fast

It's really ridiculous from Nintendo to block Rooted phones
[Android Q&A, Help & Troubleshooting] Setialpha:
So, I got it working. For me it failed with the following message:

(...)MIITOMO : fatal_error . : [COLOR="Red"]isEmulator[/COLOR]

If you get a different start up error my fix might not work for you.

As I have now clue about Xposed, I edited the Miitomo 1.2.0 apk like this to get around it:

file: smali/jp/co/nintendo/SecureController.smali

method: public static checkEmulator()Z

replace the whole method with this:

.method public static checkEmulator()Z
.locals 5

.prologue
const/4 v0, 0x0

return v0
.end method

file: smali/org/cocos2dx/lib/Cocos2dxActivity.smali

method: private static final isAndroidEmulator()Z

replace the whole method with this:

.method private static final isAndroidEmulator()Z
.locals 3

.prologue
const/4 v0, 0x0

return v0
.end method

OMG!!! I can haz haxed apk, cuz ai don't know how to apktool?? Yesiry, juz grabz diz: Derpiitomo 1.2.0 I is no Emu.
[Android Q&A, Help & Troubleshooting] StarBeing:
Yea, tried this (didn't have the same error you did though, so not fully surprised I had problems), and it worked partially. It started and loaded, and I could see my mii, but certain sound notifications were not going off, and it could not connect to get the current miifoto album picture. Also, seems Nintendo is no longer allowing update 1.1.3 to work
[Android Q&A, Help & Troubleshooting] Setialpha:
Does it have all permissions (Settings > Apps > Miitomo > Permissions)? Also try a clean install (all data, level etc. is restored, if you have a MyNintendo Account connected).

Else you might provide a logcat, I may have a look, but I'm not promising anything.
[Android Q&A, Help & Troubleshooting] Setialpha:
Two more notes:

1) You may get sound issues, here's how I worked them around:

while running Miitomo
turn off all volume (ring, notification, media, system)
turn volume back on

2) Crash on MiiFoto (in case Miitomo does not ask for permissions):

go to Settings > Apps > Miitomo > Permissions
grant: Camera
grant: Storage
[Android Q&A, Help & Troubleshooting] Uddasa:
Thanks Setialpha but your apk is not signed so we can't install it.

I just made the modifications myself and it seems to work.

The app starts even without RootCloak and MiitomoSecurityBypasser.

However I got an error "801-1650" regarding the time on my device... but I doesn't seems to be related to the fix.
[Android Q&A, Help & Troubleshooting] Setialpha:
You can, if you uninstall the previous version or 'adb install -r <apkfile>'
[Android Q&A, Help & Troubleshooting] Uddasa:
Yes I know, but as you took the time to build/upload the apk, I was thinking that you just forgot (because signing an apk is very fast).

Thanks anyway ;)

Edit: just tried your apk to see if the error "801-1650" occured but I can't install it.

C:\Users\******\Desktop>adb install -r Derpiitomo-1.2.0-IisNoEmu.apk
7342 KB/s (33569571 bytes in 4.465s)
pkg: /data/local/tmp/Derpiitomo-1.2.0-IisNoEmu.apk
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
[Android Q&A, Help & Troubleshooting] Scratch.:
Getting a parse error on my phone as well
[Android Q&A, Help & Troubleshooting] Setialpha:
Nintendo pushed an update, so will I later today. This time signed.
[Android Q&A, Help & Troubleshooting] Uddasa:
Damn, I patched the last version 1.2.2 but still got my error "801-1650" (device clock error).

I was hopping that Nintendo fixed this issue in this update.
[Android Q&A, Help & Troubleshooting] legendt:
Greetings, everyone!

I cannot wait so I made one on my own based on [MENTION=5117653]ChrisJosten[/MENTION] '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
[Android Q&A, Help & Troubleshooting] Uddasa:
The xposed module worked fine with the 1.2.2 from Play Store, and I got no error this time (still no need for RootCloak).
[Android Q&A, Help & Troubleshooting] zelendel:
Just a heads up guys, more and more apps are starting to look for xposed framework. So things like root cloak may not always be an option, as google locks android down more and more things will get harder.

Also keep in mind that if found sony could ban people from using the app.

Just some food for thought.
[Android Q&A, Help & Troubleshooting] celeadyne:
Installed updated APK but miitomo still crashes on launch with and without rootcloak, I'm running cyanogenmod. 1.0.2 worked fine. Let me know if I can get you a log of some sort passed along.
[Android Q&A, Help & Troubleshooting] legendt:
Apparently, according to the decompile smalis, v1.0.2 is for Miitomo v1.1.3 and below. So are you on v1.2.2 for sure? If so, show me the xposed log and I might figure out the problem.
[Android Q&A, Help & Troubleshooting] celeadyne:
A 2nd hard reboot fixed the issue, sorry for troubling you!
[Android Q&A, Help & Troubleshooting] Incineroar:
So I had the old version of MiitomoSecurityBypasser installed when I installed the update, however, I did find out that I think Nintendo is still checking for Developer Options being enabled. When I disabled the dev options, the black screen before the crash was much longer.

The update to MiitomoSecurityBypasser (1.0.3) doesn't seem to work for me, though. I still get a crash on launch. Guess I'm SOL for now ¯\_(ツ)_/¯ Gotta love Nintendo for blocking legit users!
[Android Q&A, Help & Troubleshooting] Setialpha:
[MENTION=5117653]ChrisJosten[/MENTION] [MENTION=5305150]legendt[/MENTION]

I found the logger func in 1.2.0+ to be changed from u.cS() to v.dp(), uploaded source to github. Version 1.0.4 apk attached and available on github, too.
[Android Q&A, Help & Troubleshooting] legendt:
Thanks for the update. I am really afraid of Nintendo obfuscating their codes each update.
[Android Q&A, Help & Troubleshooting] Setialpha:
Yes, it's annoying. I don't know what they are actually afraid of to do those checks. I mean everything is in the cloud. You are not getting any MyNintendo Coins if your actions are not verified with the Nintendo server and I doubt it's different for shop coins, where your purchase needs to be verified by both Nintendo and Google.

But even with unrooted phone and devopts never enabled Miitomo believes my S6 to be an SDK-Emulator, so yes, MiitomoSecurityBypasser is here to stay.
[Android Q&A, Help & Troubleshooting] legendt:
Only if my S4 installed with Samsung stock Touchwiz is allowed to run Miitomo. Google Play Store edition ROMs and CM / AOSP are "emulators". It seems that Nintendo use a model whitelist to judge whether you are using a phone or not. That's ridiculous...

Plus: DevOpts can be enabled. I have tested on stock touchwiz on S4.
[Android Q&A, Help & Troubleshooting] thejedimex:
thanks for this update
[Android Q&A, Help & Troubleshooting] jrk190:
Can't seem to get new version to work
[Android Q&A, Help & Troubleshooting] cristianmiu:
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.
[Android Q&A, Help & Troubleshooting] Hobox10:
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?
[Android Q&A, Help & Troubleshooting] LuigiBlood:
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)
[Android Q&A, Help & Troubleshooting] Setialpha:
Version 1.0.5 attached

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

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.

Fixed in 1.0.5

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.
[Android Q&A, Help & Troubleshooting] Hobox10:
For some reason I can't take logcats on my phone. They all end up recording zero lines. Could this have something to do with the storage permissions you mentioned? I never explicitly denied permissions to it or Miitomo so if that's what it would take to deny storage permissions then they should have it.
[Android Q&A, Help & Troubleshooting] LuigiBlood:
It works now, thanks!
[Android Q&A, Help & Troubleshooting] xstahsie:
Things are working again. Thanks to everyone for getting this to work again! Now back to Miitomo! ?
[Android Q&A, Help & Troubleshooting] Ryone:
Works really good for me. I'll never understand Nintendo for doing this kind of ****.
[Android Q&A, Help & Troubleshooting] Vingadero:
Thx!!
[Android Q&A, Help & Troubleshooting] Setialpha:
Miitomo Security Bypasser does now have it's own thread over here. Also version 1.0.6 available there, though only internal changes and new icon (so if you have 1.0.5 installed, you're fine, too).
[Android Q&A, Help & Troubleshooting] HarvHouHacker:
This new root passing package for 1.2.x works well. I'm running Miitomo version 1.2.2, and everything works fine. However, since I'm on CM Nightlies, I have to keep flashing Xposed along with each update for Miitomo to keep working.

Using my Samsung Galaxy S5 to post this.
[Android Q&A, Help & Troubleshooting] unbreakable360:
Working with new update to module. The 102 link should be udated or add the 105 to it this thread is full of irrelevant comments it was tedious looking for the solution
[Android Q&A, Help & Troubleshooting] Setialpha:
Look two posts sbove yours, there's now a new thread and the module is now in xposed repo.
[Android Q&A, Help & Troubleshooting] unbreakable360:
Just found it on xpo had a different name and I'm already subscribed to the new thread I just had this one bookmarked not the other one thanks
[Android Q&A, Help & Troubleshooting] simonepsp:
I have installed and activated the last SecurityBypasser version but Miitomo still stuck at loading screen :(

Here's my logcat (debug)...

What can I do? thanks
[Android Q&A, Help & Troubleshooting] Uddasa:
This one is outdated.

Look at this new thread instead [Xposed] Security Bypasser (Miitomo / YWWWUS / Amazon Flex / PKMN Jukebox).
[Android Q&A, Help & Troubleshooting] simonepsp:
I've just installed the version 1.0.9 of the module.

Same problem :(

this is my logcat
[Android Q&A, Help & Troubleshooting] Uddasa:
Well I can't help you with that sorry.

Try by reinstalling the app (do not start it), then activating the xposed module and reboot.
[Android Q&A, Help & Troubleshooting] Delebird:
Any way to make miitomo work without installing xposed?
[Android Q&A, Help & Troubleshooting] Andrew-J-Larson:
Any fixes for CM14.1/LOS14.1 yet?
[Android Q&A, Help & Troubleshooting] HarvHouHacker:
In May, Miitomo will be no more. https://miitomo.com/en/events/180125_final/
[Android Q&A, Help & Troubleshooting] zelendel:
Yes there is buy without being able to unlock the bootloader in the US versions a root exploit doesn't do any good.

It's not set by the manufacturer but by Google themselves. Did you read all the issues with getting root on the first release of Android M? It's coming to a point that you will need a modded kernel to get root even on nexus devices.

I'll be honest very few have a real need for root. Even if they think they do. You see it all over the place. More and more people are staying completely stock. With more and more viruses targeting rooted users, unless you are very tech savvy it has very real risks.
[Android Q&A, Help & Troubleshooting] drfsupercenter:
My Motorola Droid 4 has a locked bootloader (which, despite some hackers being mad about it, I think is a good thing as it protects you from bricking if you do something wrong) and that doesn't really matter. I use Safestrap which is an amazing "run-before-the-OS" type of thing, and what's better is it lets you take nandroid backups.

No, I haven't kept up on it in a while since I'm still using an older phone. (I refuse to give up the physical keyboard, as much as I'd love an S5 or S7...)

But I know for a while it was the CARRIER forcing the manufacturer to do stupid things. Like Verizon would bundle all this useless garbage with the phone that you couldn't remove without rooting. And of course if you did root it, they'd refuse warranty service on the phone even if it was something unrelated (like a bad screen or Wi-Fi antenna). I don't think Motorola actually wanted to put built-in Verizon junk on the phone, as it just makes people complain, but they were forced to in order to get the phone released in the US.

I do half-agree on that point. I've been using Android since 2.1 was the newest version, and at the time you couldn't even take a screenshot without root. That was honestly the reason I rooted my original Droid... just taking bloody screenshots, not even because of backups. But of course that's built in now and the "take screenshot using root+hotkey" programs are useless.

You also used to need root to block ads. It still helps, but you can do it without root these days.

Same with tethering.

Etc.

And honestly, if there was a way to take nandroid backups without needing root, I'd be fine unrooting. But it's so easy to screw something up (especially when you're me and have like 400 apps installed) so taking weekly backups is a must.

Edit: Back on topic... I cannot get RootCloak to work in CM11. I tried both the new and old ones.

I even tried deleting the su binary itself from /system/bin and Miitomo still crashes. Oddly, all my apps can still use root powers as well, even though I removed the binary. Not sure why... I wanted to test if it's actually looking if you have a su binary and that's how they were able to detect it. :/
[Android Q&A, Help & Troubleshooting] zelendel:
The carriers were forcing the oem to lock the bootloaders. Root is a native Linux option. Like admin rights in Windows. Both which are disabled by default. (if you look at a stock pc you are not even the full owner when it comes to admin rights.)

I know about flashify and safestrap, both are no longer working on newer devices. As things become more locked down.

Root cloak really is not much better as many apps are also looking for xposed. I can name at least a dozen that will not work if either root or xposed are installed.

Part of your issue might be CM. As they use an outdated SU setup that hasn't been updated in years and was abandoned by the developer. Most developers no longer even use cm as a base due to merging untested code and other issues.

You do know that Google backs up all your apps for you right?

Wow 400 apps. I have a newer device and only keep 5 apps installed. But that is also my personal device. My work device is unrooted (I don't allow rooted device on the work network) completely stock. And that has no apps installed outside of stock.

I know the feeling about the keyboard. I miss mine as I have used them for over 10 years with my smartphones but unfortunately they have gone the way of the dodo unless you get the BB priv which is completely locked down without even root for it.
[Android Q&A, Help & Troubleshooting] drfsupercenter:
Google supposedly backs up my apps but it actually causes more problems due to how many I have. If I factory reset it just crashes the phone trying to download them all at once LOL... also, I know it *says* it backs up app data, but it really doesn't. Not for most things. I need Titanium Backup for that (oh, the other super-useful root thing)

There's also one called MyBackup that I use (pro version), but also requres root to backup data rather than just an .apk.

And come to think of it, restoring apps has gotten much harder for non-root users... while things like screenshots eventually got built in, some things went backwards in terms of user-friendliness :/

And yeah, I've read that about Xposed. I'll get rid of it. I actually made a nandroid backup before setting it up FOR that reason. I also tried "Hide my root" but same problem... think I'm gonna try some logcats now and see if I find anything of interest.

But like you mentioned, Cyanogenmod has the root done oddly, it's integrated into the OS, rather than an app like superSU or the others. I WOULD use stock, but since my phone is old, the newest stock image is 4.1, which is stupidly outdated now. I don't suppose you know of any third-party firmwares for Motorola phones that don't use outdated SU setups? I know there are alternatives to CM, but CM11's milestone builds have been the most stable of anything I've tried. (The hardware might be over 4 years old, but that doesn't mean I can't run newer Android builds on it!)
[Android Q&A, Help & Troubleshooting] zelendel:
To be honest I have used TIBU for years and it has never failed me.

Yeah I don't use the Google backup either. It never really worked for me either.

To be honest I can't say for sure. The only devices I mess with are nexus devices as they have full aosp support.

With cm having it built into the Os will make it almost completely impossible to hide it.

Oh don't get me wrong. Just because a device is older doesn't mean it's useless. My last device was 4 years old. And I will hold on to my n6 for at least 5 years or until it's broken.

I'm not sure what's available for that specific device but I would look at maybe slim roms or something of that nature.
[Android Q&A, Help & Troubleshooting] drfsupercenter:
Pardon my ignorance, but what exactly is AOSP? I've heard the term, but don't know what it actually means.

A lot of newer apps run super sluggish on my phone, which sucks. It's almost always using all its RAM too, which is why I started using Greenify to kill stuff after a while (funny, the Google apps are the ones sucking up the most resources...)

I'll look around, but CM tends to just work for what it is. It's just this one app I have trouble with, and it's annoying as I really want to use it. I can try to get some more logcats if that would help anyone... just hoping somebody can figure out how the app is detecting root. .apks are just archives, I extracted it but grep found nothing. Might be some other way...
[Android Q&A, Help & Troubleshooting] zelendel:
AOSP stand for Android open source project. It is where all the source code that rom developers use to build their roms and kernels. Google pushes the code so people can build for devices. Only nexus devices are officially supported but people make it work on other devices.

What it is most likely doing is making a call looking for any SU binaries and apks. (many banks are doing this to learn how to block their app from rooted users) with it being built into cm there will be no way to prevent it. With other options you can kinda hide it but it doesn't always work.
[Android Q&A, Help & Troubleshooting] drfsupercenter:
Why are banks blocking root users? It's not like you can somehow steal money using superuser... luckily Chase bank doesn't care.

But yeah, I figured as much. What I don't get though, is why I wouldn't get a notification that it's asking to use root... apparently apps don't need root to *see* root but just to write to system folders? e.g. if I wanted to mount /data as RW I'd need root.
[Android Q&A, Help & Troubleshooting] zelendel:
Because with root. One could steal your login and password. Many root viruses come built in with keyloggers and screen recorders. The same could be done with xposed.

Chase is working on a root blocking option as well.

I could easily write an app the request root and grants it's without it ever appearing to the user. These are some of the reasons apps are blocking rooted devices.

Many don't know how powerful root is and how open it makes a system.

The last set of ransom ware viruses used root to auto grant it root rights and then download the needed files in the background, then encrypt all files on the device and lock the user out until the ransom is paid.
[Android Q&A, Help & Troubleshooting] drfsupercenter:
Never had anything like that happen... are people just installing random apps from non-GooglePlay sources without actually reading about them first? It's the same logic as people saying you'll get viruses from using file-sharing. Um, not really, only if you're an idiot and download shady material from untrustworthy sources.

I mean, I guess it makes sense about keyloggers... I was thinking more along the reasoning that games don't like root due to cheating, and it's not like you can just hack into the bank and steal money using root.

So let me get this straight... are you telling me an app can actually superuser itself without actually requesting it the correct way, and meaning I wouldn't know it's gotten access? With the built-in su manager that CM has, I can choose to block root entirely, accept once, accept for 10 minutes, or accept always. I "accept always" for ones I know aren't viruses (like Titanium Backup)...