Video

@@QiaNurwatikain BlueStacks you uninstall the magisk (kitsune) app then clone the instance from the manager. The clone will have the root removed. The alternative option will be, create a new instance or may even go as far as needing to completely remove and reinstall BlueStacks. This is an untested method, but should work in theory. Report back on if it worked.

@@wakkinito only to see how messed up it was. However, it really wasn't that bad. It's all about less is more with thermal paste.

368° Fahrenheit +/-

@@ALLISMIND it's a finicky thing. Updates to the software, updates to Windows, creating or deleting instances all trigger it to go back to read only. So yes you just have to be vigilant and or do a clean install.

Same for me

@@Mikha2212 yes, in the description I have a link to my GitHub. It's a written tutorial.

@@AW-ht1ly Go here, it's the only way to go . support.bluestacks.com/hc/en-us/articles/360057724751-How-to-uninstall-BlueStacks-5-BlueStacks-X-and-BlueStacks-Services-completely-from-your-PC

There are tools to get screws out like that

I downloaded and installed the Pie64 version from the website. Following the installation, I uninstalled both Bluestacks X and Bluestacks Services. The Pie64 instance launched automatically after the installation. I then closed all running Bluestacks programs. Something that is different is that when you run the Pie64 instance, you have to modify the same text section in the bluestacks.conf. The same situation exists with Pie64 in the engine folder. I had no issues installing Magisk or rooting the instance. After installing Magisk, I shut down the instance. Note that Bluestacks automatically updates the main root option in bluestacks.conf, so you need to manually adjust the remaining setting still set to 1 (the Pie64 setting). Save the changes, and you should not encounter any issues unless Bluestacks updates, you create a new instance, or you modify files on the Windows side. In answer to the question, no, it has not been patched. I hope this helps.

@@viralweb936 I'm sorry to hear that. There are many reasons one might assume this method does not work. However, if you read some of my replies to other comments, I detail some basic troubleshooting steps. This method works with the latest versions of BlueStacks and Windows 11.

I get it, it rewrites files because I used BlueStacks Multi-Instance Manager to launch instance, you need to to run it directly through icon on desktop

@@ceilingfanman1877 two things, one the part in the center where the wires connect for the lights had been twisted by hand so many times that the wires shorted out. Two, it's such an old fan that the motor was humming and would barely turn so I figured, "It's gone!" Lol

Ok

Yes, when you go to root a new instance, you must change all the 0's to 1's in the bluestacks.conf. Also, all the READONLY's to NORMAL in the bstk files for all instances. Then revert back the 1's to 0's in the bluestacks.conf. I will test it right now, just to be sure. edit(1) From what I can gather, this method only works on the version of Android you install from the website. Like Pie64, downloading and installing it from the website will only work on that master image. The same can be said of the Android 11 download and install process. I hope this helps. edit(2) After running the uninstall tool I have linked in the video description and reinstalling, I was able to get root on both the pie64 and rvc64 instances to function at the same time. I did not do anything special besides doing them both at the same time and from a fresh install.

My apologies, I need to make sure my video is clear on the final steps. It is essential that all the options for "root" in the bluestacks.conf file are set to 0 after installing Magisk. By default, the file automatically changes when opened after rooting. As a result, I only show how to change the instance root option back to 0, because the other one is already set correctly. Long story short, this behavior is normal.

When I troubleshoot, I like to systematically check for potential causes. Below, I have a few steps to make sure that Windows or other factors aren't the issue: 1. Reboot! Sometimes a simple reboot can resolve temporary glitches. 2. Update Windows OS and drivers to reduce compatibility issues. 3. Temporarily disable any antivirus or security software to see if they are interfering. 4. Try a clean boot on Windows. 5. If all else fails, reinstall Windows. I have some tutorials for these on my website, 'www.zero-one-zero.com/do-it-yourself'. Let me know if you need additional steps or more detail.

@@RobThePCGuy hello,I watched again and now it's working,thx!!

@@andreifilip504 I am glad to hear this. Enjoy!

did you install it into system partition

Glad I could help. Enjoy!

I guess you're referring to the bluestacks.conf. If so both the values for root should be zero after the root has been completed for this to work. Any BlueStacks updates or repairs to the instance will cause the root to be removed.

@@RobThePCGuy I thought I had followed your guide, but every time I opened an instance it would reset the conf to 0 for the enable root option. I'd check in the setting in the phone section and there was no root switch. I did it about ten times then gave up. I tried using read-only mode but it prevented masgisk from working. Anyway, I got it working so thanks.

@@Rooxie973 how did you fix it ? the value for feature rooting option is reverting to 0 .. and i cant install kitsune :( please halp

@@hadid90 I really don't know. I ended up reinstalling everything and following more carefully

I tried to explain it a little bit better. Better audio quality as well. No change is needed; when it works it works. Thanks for checking it out!

Just for the sake of trying: czcams.com/video/eRXeasi6GQQ/video.html (my latest video)

Try the updated video: czcams.com/video/eRXeasi6GQQ/video.html (my latest video)

Consider trying the beta or developer branch of Magisk. The stability of this setup depends on both the applications running within the instance and external factors, such as antivirus software detecting something that could cause a crash. Realistically, there are numerous scenarios that might be causing the issue, like interference from Hyper-V. If you can provide more details, I'd be happy to help you stabilize your system. Also try the updated video: czcams.com/video/eRXeasi6GQQ/video.html (my latest video)

Try the updated video: czcams.com/video/eRXeasi6GQQ/video.html (my latest video)

Same issue here

Yes, this issue often occurs whenever the application updates. One solution is to set the file to "Read-only" via the properties screen, which you can access by right-clicking the file in Windows.

Glad it helped!

Glad I could help!