anubhav3011 wrote:DroidMoteFan wrote:Thank you! This is great information. I had no idea that you can modify these things with build.prop. I'm still learning. In fact, after your mention of it, I ended up googling and finding out a lot more information regarding it, and I can now see that the Magisk Hide Props Config basically does exactly the same as what you can do by manually editing build.prop yourself. It's just automated with the module, that's the only difference.
However, I'm still having some issues. Googling build.prop brought up a lot of information on how to edit it using real devices, but not emulators, so I just assumed that with an emulator you could edit the build.prop file found in the system-images folder on PC using Notepad. It does open up in notepad, and you can edit it of course, but none of the changes are reflected when booting into the emulator. So far I changed these: ro.product.model=ONEPLUS A6003 ro.product.brand=oneplus ro.build.fingerprint=OnePlus/OnePlus6/OnePlus6:8.1.0/OPM1.171019.011/06140300:user/release-keys but the information under "About device" still comes up as Android SDK built for x86, not OnePlus. From what I saw from google searches and videos on youtube, changing what I changed should change the Model under 'About device' and such. I ended up trying to do it exactly as I read online and saw in videos for real devices, which is by using a file explorer with root privileges to go into the system folder on the device, find the build.prop file, and edit it from there. I thought I found the solution when I did this because once I opened the build.prop file in the emulator, none of the changes I made using Notepad to the build.prop file found in the system-images folder on PC were reflected. Everything was still original, so I ended up using ES File Explorer's Note Editor to edit the file directly and then saved the changes and rebooted. Once again the information that shows up in 'About device' has still not changed. It's all original. SafetyNet also still does not pass. Maybe there's more information that I need to edit? Can you tell me all the information that I should be editing in build.prop to pass SafetyNet?
As for the SD issue, I already installed from scratch from when I attempted to flash Magisk 17.1 using flashify and bricked the emulator lol. By bricked I mean that it would force-close everytime I attempted to boot the emulator after that. I simply deleted everything and unpacked the original rar archive brand new. There is still no SD card, but it's not that big of a deal since I can work around it. I can install apps from the play store, I can download APK's to my PC and install using ADB if necessary, the internal storage is working fine, root works fine, MagiskHide works fine (I confirmed this by hiding root from Root Checker temporarily and it was not detected), so I'm happy with everything. The only thing I need now is to pass SafetyNet, then purchase DroidMote server and set that all up (this should be easy though), and I will be good to go.
I completely understand what you mean by patching the ramdisk.img with the Magisk Manager app. I read about how 1 way to root using Magisk is to patch the boot image of your device if you have it. In our case it's the ramdisk.img. I'm going to leave it alone for now since as you say, I should be able to do everything with 16.6 anyway. If it becomes necessary to update at a later time, then maybe I will attempt to patch the ramdisk.img
Anyway, can you help me with editing build.prop to pass SafetyNet? Molto grazie!
bro i think we are on the same page as i also want safetynet, please teach me how to pass it as i tried installing modules of magisk it doesnt install
I haven't gotten it to pass yet (if it's even possible with the emulator), but follow this thread because zulu may know how to get it passed. We will have to wait for replies.