Open reihunter360 opened 7 years ago
@reihunter360 another anti-reroll things?.. i see some phone got affected as well.. let se our JP Part2 summer.. if its happen as well... then its officially get blocked by DW again --" [or by request of Aniplex USA]
@AkagiShiroe seems like the same ordeal a majority of chinese phones/tablets had on the Chinese Version. Its getting falseflagged. Not sure if AniplexUSA will fix it though.
@reihunter360 they sure will fix it, or get bombed by people who doesn't have compatible phone with that root-checker. i hope someone can fix it.. [i try a bit poke on it.. seems fgo library searching for superuser.apk dunno what's mean]
Remix is fine, so phones should be fine and no official fix is coming. ShittyNet updated few days ago, probably the case here.
@Teodor19 , nope Xiaomi phone get blocked as well.. probably every phones come from chinese , since memu developed from chinese? from what i recall in memory.
@AkagiShiroe if you can find the files its checking for, i can just delete those with Linux.
Oh, so phones too. Well, i'm not sure how many Xiaomi phones in US... Yeah, it's 60, not 10. Deleting files should work like last time.
@Teodor19 @reihunter360 best chance are changing Memu_launcher (if the root check that).. and poketest one need a bit overhaul on it (need @wDCat here), better choice are waiting to fix this.. seems only affecting X86 Android based (since xiaomi does use it, RemixOS use ARM and X86 Hybrid right?) (if you uninstall that.. it will allow you procces but cause you to close the game)
wait, its flagging memu_launcher? and poketest? Wut?
@AkagiShiroe I have no idea what to do here, kinda noobs with this tech thing. Can anyone tell me what to do? I kinda uninstall the game in my panic . . .
Remix is fork of Ansroid x86, pretty sure it's x86. So, i should try to install some Nova launcher and delete memu launcher?
@Teodor19 Would that delete the current games data that you have on memu?
@reihunter360 more like poketest allow you to access fgo like usual-phones (seems emulating chinese one or xiaomi.. dunno which reference @wDCat take if this correct),if you try delete it will allow you to access but with usual memu bug.. force close from begining, @Teodor19 try to decompile game apk.. its should be english now (mostly), i hope someone more experience on android can check this like @wDCat
@AkagiShiroe give me exact files its searching for.
@reihunter360 :lol im just try to read fgo main data (program library).. busy doing summer event too.. just play with RemixOS since JP are fine.. i hope they fix it soon.. (sorry i don't have time.. even translating Fate/Apo got discountinued xD)
@AkagiShiroe fategojp isn't even up yet. RemixOS is also extremely annoying to setup.
I'm just gonna go into linux and delete whatever file its flagging.
Does the early version of f/go NA work in memu?
Every version until today's 1.20 worked fine. On your unrooted Memu, i mean. Didn't work in vanilla Memu.
FGO NA 1.1 boots but will give you the update_apk message when you try to connect. I strongly suspect they didn't put this in the JP version just yet because just recently they had a login bug to deal with (that lasted like two weeks plus) and then an APK was buggy and they had to force a hotfix update on the APK (1.25 to 1.25.1) But there is little doubt they will add this to the JP version before long, possibly as early as next week for the anniversary maint. So NA is basically a head start to fixing JP later.
@ScienceOfMemory the problem are.. its an bug with it (some phone got caught as well).. 2nd are.. unlikely DW will spend another method to prevent emu-user (unrooted) to access the game. probably a bug mess come from US dev. or some anti-reroll action to take with for a while.. dunno.
Never assume incompetence before you can completely rule out intentional malice. I haven't seen any reports of non-chinese phones getting swept up in this and using a chinese make phone is basically asking for issues with FGO.
Edit: I'd like to add that the RemixOS thing still works fine. It's Memu alone that's being targeted here, which does seem much more likely to be malicious intent than an accident.
Yeah....Bad news...They began to anti-emulator.... or someday they will ban x86 devices.
@wDCat @ScienceOfMemory any work around available? --" i hope no for JP, so @wDCat are you planning to make some feature that hidden emulator core in ANRC?
@wDCat
They can be deleted right? or at least replaced? :O
Oh, so they finally began checking Memu (and Andy o__o) system files. I guess Memu is unfixable without Memu devs now. Unrooting different emulator would only be temporal solution, as these Aniplex shitters just add specific checks in next update. That also means they are fine with Remix. (or it was forgotten)
Please, memu wouldn't do that. they need name branding after all.
@AkagiShiroe maybe there is...but sorry that... I'm so tired in it...:(
@wDCat i see, thanks for the work you've been doing.
a friend was wondering why you aren't using config files for your ANRC apk, and why everything's hard coded.
@wDCat thx for your hardwork.. for now rest well.. its not guaranted jp server will got that too.. i hope it wasn't, yet thx for your all hardwork xD.. hope i can see your work in future.
There is no point in trying to have the memu developers play cat and mouse with the DW assholes. If ANRC can hide root, isn't it possible to hide specific system files and folders with another app? If their implementation of anti-emu security scans the system, the system needs to be hidden from scan. I don't know enough about android system structure to know if this can be done or not however. If just hiding them is not possible, can they be masked so they read as something they are not?
@wDCat how about using anrc to hide folders and whatnot?
Won't they just eventually scan for ANRC then?
@ScienceOfMemory @reihunter360 ANRC can hide,but very slow(only about 10 fps with Root Hide v2)...I still can not find a better way to hook the syscall,maybe modifying the kernel is a good way(like magisk...)
10 fps is still a much better option than no fps and the entire thing is permanently broken. At this point we're below the "beggars can't be choosers" level and take what we can get. Since this will obviously be a cat and mouse thing, have you considered making ANRC read what it has / wants to hide from a editable config file? That way you wouldn't have to deal with updating ANRC every time FGO decided to be an ass.
@wDCat i'm having problems running Root Hide v2 though. ANRC on Nox. Does it no longer work?
@ScienceOfMemory you can change these config files in ANRC's setting.
@reihunter360 It only has ARM version.I have no plan to develop X86 version because of the bad performance.
@wDCat are there any emulators that use ARM?
QEMU? Though it seems like a puzzle, not complete product.
@wDCat do we still need xposed install for Root Hide v2? or just Root?
@reihunter360 need root and xposed
@wDCat alright i tried on amiduos, installed special xposed, and xposed 3.1experimental, and then ANRC. ANRC managed to get Root Hide v2 on, but FateGONA is still detecting xposed. Error Code 92.
DLOG_1500646507190.zip No file mapping done.
EDIT : Nevermind, amiduos is x86 architechture. Damn.
@wDCat You listed the files FGO scans for. Which file in the APK actually contains a list of those?
@wDCat hey, are you still alive? I was wondering how you were able to get the files that FGO was scanning for... if its not too much to ask.
@reihunter360 just dump its memory and you will find something interesting.
@wDCat not experienced here with that.. since its android, i only know windows 🤣
@wDCat dump which memory? memuheadless.exe ? FGO?
Create FullDump or MiniDump?
FGO and dump its heap
@wDCat using what app/tool though? Wouldn't it require root?
IDA is enough.it require root
@wDCat Oh it seems you can use adbtools with android emulators,
and use this command "dumpheap [options] process file"
I'll test if i can get it to work. But i'd need a way to analyze the dump files.
Oh nevermind it requires usb debugging, guess a root emulator should suffice.
It seems that fgov2.ova by @wDCat is getting falseflagged with error code 60 (whitescreen on startup to email/messenger) Which is weird since Error Code 60 is for Root mode is on. It still works on JP though.