Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Several questions about fgov2.ova #105

Open
aacprime opened this issue Oct 2, 2017 · 3 comments
Open

Several questions about fgov2.ova #105

aacprime opened this issue Oct 2, 2017 · 3 comments

Comments

@aacprime
Copy link

aacprime commented Oct 2, 2017

Kinda offtopic tbh, but I need answers.
Fire Emblem Heroes has similar to FGO ways of spotting if the device has root access or/and if the device is an emulator. Several months ago someone figured out FEH works fine on that lollipop fgov2.ova image. It still works perfectly even today.
So, I want to "port" this workaround to newer version of memu. I need to understand how exactly is that fgov2 image modified. One man linked me this comment of wdcat:
"I just remove all content in /proc/bus/pci/devices by modifying kernel;
delete /system/bin/su and /system/xbin/su;
change system property in /default.prop and /system/build.prop".
Well, 2nd and 3rd steps are pretty easy, but what about "modifying kernel"? How do I modify kernel on MEmu and what exactly I have to do with it? Are there some extra steps besides these three? How can I contact wdcat if he doesn't visit github anymore?

@wDCat
Copy link
Owner

wDCat commented Oct 2, 2017

There is a similar guide(Chinese):https://bbs.pediy.com/thread-207538.htm
and I modified this function
static int show_device(struct seq_file *m, void *v);

@aacprime
Copy link
Author

aacprime commented Oct 2, 2017

It's such a relief you're still around here.
Thing is, I've tried to figure it out by myself for several days, but I couldn't do the simple thing - locate boot.img in memu. I mean dev/block/platform folder doesn't exist and I have no idea where else to search for it. I've located sda3 with kernel and ramdisk files but couldn't unpack it properly.

@wDCat
Copy link
Owner

wDCat commented Oct 3, 2017

Use vmware or vbox to mount MEmu44-2017****-disk1.vmdk and MEmu44-2017****-disk3.vmdk
and you will find a file "kernel" in a 6.4M partition.This is the zImage file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants