TWRP for Rikomagic MK39 available (RK3399)? ROOTING with MAGISK?

[jean-louis]

If I understand right how rooting with Magisk works, I need to have a TWRP version of my Android TV box (Rikomagic MK39. with Rockchip RK3399) if I want to root my box with Magisk (without using a PC).
I have searched everywhere but could only find 2 versions for RK3399 which do not seem to work (they do not load TWRP when booting and I get an error message).
Is my understanding correct or am I doing something wrong?

[ClarkKent]

If I understand right how rooting with Magisk works, I need to have a TWRP version of my Android TV box (Rikomagic MK39. with Rockchip RK3399)
Is my understanding correct or am I doing something wrong?

When you find a working TWRP for the rk3399 make sure to let me know. As I have yet to see one. Magisk will root as a standalone app, at least it has for me.

[jean-louis]

When you find a working TWRP for the rk3399 make sure to let me know. As I have yet to see one. Magisk will root as a standalone app, at least it has for me.

Thank you very much for your reply ClarkKent. When you say that Magisk has rooted as a standalone app for you, have you done that on an RK3399? And if yes could you let me know how you have done that, as I have searched a lot and could not find a way to do it. Maybe it is that easy that I overlooked it. In that case can you send me a link. Thanks so much in advance.
Jean-Louis

[ClarkKent]

I may have misspoke. If you're searching using several variations, and haven't found anything, that's a good indicator. Thinking more clearly now I think I used the systemless root on an unlocked bootloader for my phone sometime back. I have gotten magisk to run on my rk3399 oh, but it is rooted. So it became the super user manager, and does a good job.
Through some magical button-pushing I managed to lose magisk oh, and have had no luck reloading it. But don't miss it that much.
What device do you have oh, and what are the specs? I think you're going to have to search that down and it's rooting process. There are not that many rk3399 s that are locked down though. Most I believe all rooted. There are the exceptions.

[gefattern]

I may have misspoke. If you're searching using several variations, and haven't found anything, that's a good indicator. Thinking more clearly now I think I used the systemless root on an unlocked bootloader for my phone sometime back. I have gotten magisk to run on my rk3399 oh, but it is rooted. So it became the super user manager, and does a good job.
Through some magical button-pushing I managed to lose magisk oh, and have had no luck reloading it. But don't miss it that much.
What device do you have oh, and what are the specs? I think you're going to have to search that down and it's rooting process. There are not that many rk3399 s that are locked down though. Most I believe all rooted. There are the exceptions.

Hi ,

how did you made it with Magisk as your Superuser
Manager , only installing the apk ???

greetings / gefattern

[jean-louis]

Just to avoid confusion, I am talking about Android TV box, not a phone. On phones we are in a different environment.
I have a Rikomaginc MK39 and I use the latest firmware (10 mai 2019). By the way this firmware also runs on other machines with RK3399 boards (H96 MAX, X99, CSA96, MK39. If you want more info in this respect, please let me know). I have tested all RK3399 firmwares available on the net (between 25 and 40 different one's) and this one for my purpose is by far the best. It is very stable and pre rooted, I can print in a network using the PrintBot app, thus sharing 1 printer amongst 5 different stations. I have one machine, the CSA96 which is dedicated to testing.
The only thing I would like to add is increase the security using a root manager app like Supersu or Magisk or a RootSwitcher.
Supersu:
does seem to work, but if I accept to update binaries during the installation of Supersu, the box goes into a bootloop. I could use Supersu without updating the binaries, but I am afraid that on the long run it could stop working or would not be working properly and safely.
Magisk:
So far I have not found a way to install it. If any one knows how to do that on this machine, please let me know.
Root Switcher app:
I wonder if this is a good and safe way to work. The problem with that is that it is difficult to know what this app is doing exactly.

I also have a A95X MAX which has a root switch build into its firmware which seems to be a good solution. The drawback with this machine, is that it is much much slower that the RK3399 boxes. Therefore do not use this box so often.

thanks for any suggestions?

[mo123]

You need Android Pie firmware for RK3399 to use Magisk correctly.
The manufacturer then also has to enable the Magisk flag when building the firmware.
Magisk is already supported on RK3399 Pie since Dec 2018.
But if Rikomagic will ever release an updated OS is another question.

[ClarkKent]

Hi ,

how did you made it with Magisk as your Superuser
Manager , only installing the apk ???

greetings / gefattern

Again the memory slips me. But gef oh, it was pretty straightforward download the app, install pull the files, execute the files in direct load. This was on the n6, so naturally other issues came up and it went away. I was able to execute the installed once again, and like Pierre are used it mostly for a s u manager. Liked it very much. I think it's more complete and runs quicker, more responsive. But subsequently, I lost it ... and for the life of me I can't get it back! I'm not sure what I did to get it to cooperate then oh, but it will not now.

[ClarkKent]

Just to avoid confusion,
~~ No confusion, got that.

I have a Rikomaginc MK39 and use the latest firmware ... this firmware also runs on other RK3399 boards, If you want more info in this respect, please let me know.

~~ ~ Okay, I am. I really, Really would like to try it on my Magicsee N6/ rk3399.
Would you be willing and able to upload a bootcard maker/ SDcard/ toe loadable version?
Without flashing (can't do it), and no twrp, that is the only way to loaded. Thoughts??

The only thing I would like to add is increase the security:

~~ Sure! Understandable.

Supersu: ~~ Use the pre-updated ver. Proven long term Stability.

Magisk: ~~ imho, Much better. But, not 3399 friendly. Perhaps following other rk soc install processes.
I felt like it could be the combination of magisk ver/ installer ver. Mix and match is not ez to do lately.
I'll link anything helpful I find.

....it is much slower than the RK3399 boxes. Therefore do not use this box so often.
~~ Yepper! ...that's a fact.

suggestions?

- iT IS OUT THERE....somewhere?

[ClarkKent]

mo123 I believe it ran well, and correctly in Android 7, on my n6.
ultimately I did lose it somehow okay, so maybe it's not so correctly?
I still believe what worked for me, was an older magisk file installed by an even older installer. Since the forced updating, the installer refuses to run unless it is the latest release... So it would not accomplish the install once again, correctly.

[mo123]

mo123 I believe it ran well, and correctly in Android 7, on my n6.
ultimately I did lose it somehow okay, so maybe it's not so correctly?
I still believe what worked for me, was an older magisk file installed by an even older installer. Since the forced updating, the installer refuses to run unless it is the latest release... So it would not accomplish the install once again, correctly.

If Magisk is working properly, it will have 2 green check marks at the top 2 items in Magisk Manager.
In Magisk Manager's log it should also say that it loaded properly and after a few reboots it must not loose root access.
I've implemented Magisk in a few Nougat firmwares where the source code was available but you really need Android Pie as it's better supported and you can easily update it.
On older Android OS's you can use it but not update and Magisk is updated on a daily basis to fix bugs, so after a few months you will get problems if apps update their Safetynet.

[ClarkKent]

The truth comes out. That was the case. I had my green check marks everything was good. I usually switch off auto updates. But that's probably what happened I lost it and couldn't duplicate the scenario that let me load it in the first place.

[ClarkKent]

[QUOTE=jean-louis;n785659]
Just to avoid confusion,
I have a Rikomaginc MK39 and I use the latest firmware (10 mai 2019). By the way this firmware also runs on other machines.
If you want more info in this respect, please let know.
/QUOTE]

J, I had hoped to hear back from you about your mk39 software. As I say I'd really like to try it on my n6.
would you be willing and able to upload an SD file, that can be installed via the factory recovery? You would be a hero to me and other n6 owners when that update is able to override a smoother more stable UI.
by the way, have you looked at modifying the factory recovery? It seems like a good basis if it had some substantial tweaks. Anything would be a benefit to the 3399, absent the availability of TWRP. Which I believe is a lost cause oh, it's just not going to happen.

[jean-louis]

I have tried the latest Rikomagic firmware on the H96MAX (RK3399), X99, CSA96 and obviously also on the MK39. It runs very stable on the H96MAX and MK39. On the X99 it runs a bit less stable. Sometimes the screen is frozen and I need to cut power to reboot. Booting also takes around 1min50 secs against 10 to 15 seconds on the H96MAX and MK39. X99 has 64 gb of storage which is the reason why I bought it. As I only boot once or twice a day I can accept waiting one and a half minute more during booting. The CSA96 is similar as the X99 but takes a bit less to boot, about 40 seconds.
You can download the Mk39 firmware from the "Rikomagic official site" or here:

https://www.mediafire.com/file/3zrdu5tt5opamp3/mk39_7.1_box_closer_190510_RKM_public.zip/file

I found that burning a SD card gives best results for flashing the firmware. Using a usb cable and a Windows PC also works but seems less reliable. In the past Rikomagic provided a link on how to properly burn a SD card for flashing, but I did not see it now. If you are unsure, I should be able to find it back.
I have also tried the N6 firmwares on the H96MAX and the CSA96. The flashing worked, but I did not like the firmwares at all. To me they were a step backwards.
So if the N6 firmwares can be installed on other RK3399 boards, it should also be possible to install firmwares from those machines on the N6.
Make sure you got a N6 firmware to revert back in case there is a problem.
Please also bear in mind, that my requirements may be different from yours. I use the MK39 mainly as replacement of a PC and besides that ocasionally as a TV box.

Good luck.

[ClarkKent]

Almost all of that I'm already aware of. The 32 gig storage vs 64 could be an issue. Somebody else over in the n6 thread has run it's ROM on the MK. We were not entirely sure that the mk39 would run on the n6. My problem is no PC. I have no immediate plans to get one. I thought maybe making a boot card was not a laborious issue for you, thus hoping for the upload of same. Volume six runs primarily for TV but I also use it as a desktop ... with a 55 inch screen. One does what one has to

[jean-louis]

Almost all of that I'm already aware of. The 32 gig storage vs 64 could be an issue. Somebody else over in the n6 thread has run it's ROM on the MK. We were not entirely sure that the mk39 would run on the n6. My problem is no PC. I have no immediate plans to get one. I thought maybe making a boot card was not a laborious issue for you, thus hoping for the upload of same. Volume six runs primarily for TV but I also use it as a desktop ... with a 55 inch screen. One does what one has to

have never done "I thought maybe making a boot card was not a laborious issue for you, thus hoping for the upload of same". Not so sure how to do that. Can you guide me.