Database Develop

[Q] LG L90 D315 bricked without recovery access etc

So this is my first xda thread. I spent hours searching without finding a solution for my particular case.
I am using a LG L90 D415 (T-Mobile version) and I got bored of it and so I started playing with the system (not the first phone I'm doing that with, so I know a bit about that sutff). So I tried to install the new Android L home launcher from here http://forum.xda-developers.com/showthread.php?t=2796019
I did everything like explained, installed it and changed the build.prop like described. But after I rebooted my phone, expecting a new home launcher, the phone boots, I am at the lockscreen, but after like 4 seconds I receive multiple errors (like gapps stopped working) and than everything freezes and it reboots.
Unfortunaly I didn't install a recovery or unlocked fastboot. So I can access download mode, but that's it. My computer doesn't see my phone (because usb debugging deactivated?) and so I don't know what to do. I think that's a pretty tough case but I hope some smart person can help me
Thank you

mcfiish said:
So this is my first xda thread. I spent hours searching without finding a solution for my particular case.
I am using a LG L90 D415 (T-Mobile version) and I got bored of it and so I started playing with the system (not the first phone I'm doing that with, so I know a bit about that sutff). So I tried to install the new Android L home launcher from here http://forum.xda-developers.com/showthread.php?t=2796019
I did everything like explained, installed it and changed the build.prop like described. But after I rebooted my phone, expecting a new home launcher, the phone boots, I am at the lockscreen, but after like 4 seconds I receive multiple errors (like gapps stopped working) and than everything freezes and it reboots.
Unfortunaly I didn't install a recovery or unlocked fastboot. So I can access download mode, but that's it. My computer doesn't see my phone (because usb debugging deactivated?) and so I don't know what to do. I think that's a pretty tough case but I hope some smart person can help me
Thank you
Click to expand...
Click to collapse
No custom recovery and no fastboot? Factory reset is your only option. See this post. Scroll down to Q14. Even though it's titled something else, the same button presses apply for your device in it's current state, ie; no recovery, no fastboot

shinobisoft said:
No custom recovery and no fastboot? Factory reset is your only option. See this post. Scroll down to Q14. Even though it's titled something else, the same button presses apply for your device in it's current state, ie; no recovery, no fastboot
Click to expand...
Click to collapse
First thanks for the fast answer. So I figuered that I only need to delete the build.prop file and replace it with my backup file. Isn't there any way to rescue my files and/or access the /system folder? I'm an exchange student now and I don't wanna lose my picture memories
And btw I know that I build the perfect worst case scenario right now
Oh and in the L90 faq it says that when you flashed a recovery and you navigate to factory reset it won't reset but boot into recovery. Does something like this work even without recovery, so I could try doing stuff with adb?

mcfiish said:
First thanks for the fast answer. So I figuered that I only need to delete the build.prop file and replace it with my backup file. Isn't there any way to rescue my files and/or access the /system folder? I'm an exchange student now and I don't wanna lose my picture memories
And btw I know that I build the perfect worst case scenario right now
Click to expand...
Click to collapse
If adb isn't detecting the phone, no. There isn't any other way.
mcfiish said:
Oh and in the L90 faq it says that when you flashed a recovery and you navigate to factory reset it won't reset but boot into recovery. Does something like this work even without recovery, so I could try doing stuff with adb?
Click to expand...
Click to collapse
Unfortunately, no.
Factory reset will not erase your sdcard. It will however erase internal data. It will return the phone to the state it was in the first time it was powered on.

Can't enter recovery mode???

I can't seem to figure out how to enter into recovery mode on my T-Mobile G4. It's running everything completely stock. I have tried holding power button and volume up until the logo comes on and releasing both buttons and then immediately holding them both down again waiting.. and nothing happens. I've even tried waiting for one second after I initially release to hold them down again. Same outcome. It always just boots back up into Android. I have tried volume down instead.. Nothing. Can someone please show me how to boot into recovery mode? Again, running stock rom.

I had the same issue. This is what I did to resolve it.
1. Enable Developer Options (see here).
2. root the phone (see here).
3. Download TWRP for the LG G4 H811 from here.
4. Install Flashify from the Play store.
5. Open Flashify and select Recovery Image -> Choose file and select the file from Step 2 to install TWRP
6. Reboot to TWRP from Flashify
When I was on the factory ROM I had to repeat steps 5 & 6 any time I wanted to boot into recovery (TWRP). None of the other boot options worked for me. Not button combinations and not even using adb (adb reboot bootloader). So what I did next is I decided to try another ROM. I installed one of the CM12.1 nightlies. Now running on CM12.1 I can boot into recovery without issue. I have no idea what is in the stock ROM that made it impossible to boot to recovery. I haven't been very motivated to go back to the stock ROM to do any further troubleshooting.

Demati said:
I had the same issue. This is what I did to resolve it.
1. Enable Developer Options (see here).
2. root the phone (see here).
3. Download TWRP for the LG G4 H811 from here.
4. Install Flashify from the Play store.
5. Open Flashify and select Recovery Image -> Choose file and select the file from Step 2 to install TWRP
6. Reboot to TWRP from Flashify
When I was on the factory ROM I had to repeat steps 5 & 6 any time I wanted to boot into recovery (TWRP). None of the other boot options worked for me. Not button combinations and not even using adb (adb reboot bootloader). So what I did next is I decided to try another ROM. I installed one of the CM12.1 nightlies. Now running on CM12.1 I can boot into recovery without issue. I have no idea what is in the stock ROM that made it impossible to boot to recovery. I haven't been very motivated to go back to the stock ROM to do any further troubleshooting.
Click to expand...
Click to collapse
So, you're saying that there is no other way to get into recovery, but to root the phone first? I was hoping I didn't have to do that.. I haven't researched how to properly save the stock rom in case I need to get back to it because I need to bring it to the store for some reason or another..

From the T-mobile website: https://support.t-mobile.com/docs/DOC-21911

stringz90 said:
So, you're saying that there is no other way to get into recovery, but to root the phone first? I was hoping I didn't have to do that.. I haven't researched how to properly save the stock rom in case I need to get back to it because I need to bring it to the store for some reason or another..
Click to expand...
Click to collapse
If there is a way I didn't find one. There very well may be a way to do this. I just didn't put in more than a couple of hours of effort.

That's not what I'm talking about. That's talking about factory resetting your phone with the hardware keys. I'm talking about entering recovery mode (kinda like the bios of the phone) using the hardware keys.. It's different.

Demati said:
If there is a way I didn't find one. There very well may be a way to do this. I just didn't put in more than a couple of hours of effort.
Click to expand...
Click to collapse
I'm starting to think T-Mobile did something different with their variant to disable people from entering recovery mode.. This is irritating. I'd like to have the option of doing so in case I need to re-calibrate my battery or anything else that I'd need access to the recovery for.

stringz90 said:
So, you're saying that there is no other way to get into recovery, but to root the phone first? I was hoping I didn't have to do that.. I haven't researched how to properly save the stock rom in case I need to get back to it because I need to bring it to the store for some reason or another..
Click to expand...
Click to collapse
stringz90 said:
I'm starting to think T-Mobile did something different with their variant to disable people from entering recovery mode.. This is irritating. I'd like to have the option of doing so in case I need to re-calibrate my battery or anything else that I'd need access to the recovery for.
Click to expand...
Click to collapse
I have been trying a few different ROMs over the last few days. The modified stock ROM (Genisys) is pretty much the same as the stock minus some bloatware and it is rooted. I have no issue booting into recovery from it. Maybe that is worth a try for you?

Demati said:
I have been trying a few different ROMs over the last few days. The modified stock ROM (Genisys) is pretty much the same as the stock minus some bloatware and it is rooted. I have no issue booting into recovery from it. Maybe that is worth a try for you?
Click to expand...
Click to collapse
Alright.. I guess, I'll have to try that, but first is there any way to do a backup of some sort in case I have to go back to stock rom rooted? I got my G4 about a month ago and haven't done much research on rooting this specific device. I haven't had a high end phone with rooting and rom options in a long time. The last phone I had a chance to root and install cool custom roms on was a Samsung Galaxy S2. If you can guide me in the right direction I'd appreciate it. I guess I have to start from square one again. In the past I remember that in order to go back to completely stock you had to have a usb jib to reset the flash counter. Is it the same for this case? I welcome anyone's helpful input. Thanks, everyone.

F***ed my S**it up HELP!

i have absolutely no clue what i am doing here, i tried to reboot my tablet into TWPR menu
but i could not figure it out it has TWRP, and RR rom and root
i held the power button down and did reboot recovery and i did not get TWRP menu
so rebooted it and then i chose bootloader, and now all i get is a black screen that says fastboot..
holding power and it won't reboot it wont turn off or do anything
how do i fix this ****?
how do i get to the twrp menu screen?
how do i create a backup of my system to the SD card?
i want to try an experimental APK but i want to make sure i can recover if it messes up my tablet
but 1st how do i fix this?

gdroid666 said:
i have absolutely no clue what i am doing here, i tried to reboot my tablet into TWPR menu
but i could not figure it out it has TWRP, and RR rom and root
i held the power button down and did reboot recovery and i did not get TWRP menu
so rebooted it and then i chose bootloader, and now all i get is a black screen that says fastboot..
holding power and it won't reboot it wont turn off or do anything
how do i fix this ****?
how do i get to the twrp menu screen?
how do i create a backup of my system to the SD card?
i want to try an experimental APK but i want to make sure i can recover if it messes up my tablet
but 1st how do i fix this?
Click to expand...
Click to collapse
Clean up the language.
- no TWRP (custom recoveries) on this device
- to exit from fastboot untether and long press power until it turns off
- start with the forum index and read what you can/can't do with this device and how to accomplish it

Davey126 said:
Clean up the language.
- no TWRP (custom recoveries) on this device
- to exit from fastboot untether and long press power until it turns off
- start with the forum index and read what you can/can't do with this device and how to accomplish it
Click to expand...
Click to collapse
yes got it to reboot by holding volume and power finally ,it did not work the 1st few tries for some reason
i know i was in the TWRP screen before when i flashed the rom and xposed but now i forget how to get back to it now
so what happens if i mess up my system with an experimental APK, i am trying to add miracast
if it messes up something then will i be able to recover? or would i have to make a backup with TWRP 1st?

gdroid666 said:
yes got it to reboot by holding volume and power finally ,it did not work the 1st few tries for some reason
i know i was in the TWRP screen before when i flashed the rom and xposed but now i forget how to get back to it now
so what happens if i mess up my system with an experimental APK, i am trying to add miracast
if it messes up something then will i be able to recover? or would i have to make a backup with TWRP 1st?
Click to expand...
Click to collapse
Clean up thread title...go from there. Miracast won't work on this device.

Davey126 said:
Clean up thread title...go from there. Miracast won't work on this device.
Click to expand...
Click to collapse
sorry i can't edit it, it won't let me
also i have looked around and i found this .apk
http://cord-cutters.wonderhowto.com...rooted-android-device-running-kitkat-0156212/
(it says kitkat but there was a thread on here on it and it said kitkat or above)
https://www.androidfilehost.com/?fid=95784891001616583
and i searched and searched but i have not found any reports of it ever being tried on the 2015 5th gen fire 7
i can only seem to get to the thread in google cache ,and there are only reports of it being tried on the HD fire 7 and all posts end around 2014 so i am not sure if it will work, but what is the worst thing that could happen if i try this? with no backup and TWRP installed? could i still revert everything back?
have you ever heard of anyone trying this specific .apk on this device before?

gdroid666 said:
sorry i can't edit it, it won't let me
also i have looked around and i found this .apk
http://cord-cutters.wonderhowto.com...rooted-android-device-running-kitkat-0156212/
(it says kitkat but there was a thread on here on it and it said kitkat or above)
https://www.androidfilehost.com/?fid=95784891001616583
and i searched and searched but i have not found any reports of it ever being tried on the 2015 5th gen fire 7
i can only seem to get to the thread in google cache ,and there are only reports of it being tried on the HD fire 7 and all posts end around 2014 so i am not sure if it will work, but what is the worst thing that could happen if i try this? with no backup and TWRP installed? could i still revert everything back?
have you ever heard of anyone trying this specific .apk on this device before?
Click to expand...
Click to collapse
- have not heard of anyone trying linked apk on this device
- in general custom roms on Amazon devices do not support miracast (multiple devices/multiple roms)
- if you can access the stock recovery menu via <power>+<vol-up> recovery is possible (reload FireOS)
- unlikely a straight apk install will bork the rom; more likely it simply won't work

Davey126 said:
- have not heard of anyone trying linked apk on this device
- in general custom roms on Amazon devices do not support miracast (multiple devices/multiple roms)
- if you can access the stock recovery menu via <power>+<vol-up> recovery is possible (reload FireOS)
- unlikely a straight apk install will bork the rom; more likely it simply won't work
Click to expand...
Click to collapse
yup you are right it dod not work the app gave a message right away about not having some file for audio something t other i forget ,just uninstalled th eapk and no damage done

Rooting Samsung Galaxy Tablet E (8.0) SM-T377V Please Help

So I've had success rooting the SM-T377V thanks to electronhacker post on the forums.
I thought I would give my experience because anyone else doing this will most likely run into the same problems I did. I still have a few problems I am running into. I hope someone can help me out.
electronhacker had said to downgrade to stock firmware LMY47X.T377VVRU1AOL7 (5.1.1) Lollipop, from firmware MMB29K.T377VVRS1BPL1 (6.0.1) Marshmallow using Odin.
I ran into problems finding LMY47X.T377VVRU1AOL7 but I eventually did find it on samsung-firmware.org Thank you moonsh0t!
It did actually work and passed with Odin, however it got stuck in a bootloop. I thought there was nothing that could be done but after looking into the bootloop matter more I figured out how to get out of it and start it up.
1.) Wait for the device to turn off while it's bootlooping.
2.) Then hold down the power button and the volume up buttons to enter recovery mode.
3.) Restore factory defaults. "I think this actually gave me an error but clearing the cache got it to work."
4.) Clear the cache.
5.) Reboot the device.
There you have it now you're out of your bootloop, the device will start up now.
Now that we have downgraded electronhacker had said to run a program called Kingoroot using the Windows application.
I ran Kingoroot and it got stuck at 44% and my screen went black and would not come on or turn off. I am pretty sure you call this a soft brick, but maybe it's called hard brick as there was nothing that could be done.
So this is what I did to Unbrick the tablet:
1.) Hold the power button and the volume down button for 15 to 30 seconds.
2.) The screen should come back on.
3.) Scroll through settings to reboot device normally.
I tried to use Kingoroot again. This time it got stuck at 51% and my screen on the tablet got stuck. Nothing was responding, not the power buttons, the volume buttons, home button, nor the screen. This is because Google Application had showed up on the tablet while I was in the middle of rooting. The Google Application said "Do you want to enable Google Security?".
Again;
1.) Hold the power button and the volume down button for 15 to 30 seconds.
2.) The screen should come back on.
3.) Scroll through settings to reboot device normally.
The device booted normally and I tried Kingoroot again. I wasn't going to give up. This time it worked, 100% Root Successful. I couldn't believe it the SM-T377V was rooted. I checked and verified with Root Checker.
Now this is where I need help!
#1.) The device only stays rooted until you restart it. Then you have to Re-Root it with Kingoroot every time you restart. I found out if you run SuperSu and go into setting you can stop this from happening. I'm not exactly sure what you do yet because I can NOT get into SuperSu. It tried to install the binaries but gets interrupted by Knox. It says disable Knox on SuperSu but this does NOT work. This tablet does NOT have a way to open Knox in order to disable it. So I need to figure out how to delete it that way I can run SuperSu and stop the never ending root process. So if someone could help me figure out how to do that I would very much appreciate it.
So far I've figured out that you can run an application called Titanium Backup to freeze the Knox files and then remove them followed by a Re-Boot to get rid of Knox. I looked further into my SuperSu problems and found out that you can manually download a SuperSu.apk file that should bypass Knox and actually disable it.
Here is my new problem, installed Titanium Backup from Google Play Store only to find out that I can't freeze the Knox settings unless I pay the $5.99 for Titanium Backup Pro. So I removed Titanium Backup and downloaded Titanium Backup Pro.apk which I found for free on the internet. I can NOT install it though, because I have a new error that says "APP not installed".
This happens with the SuperSu.apk that I found on the internet too. I've tried a lot of things but can't get them to install. Google Play Store gives me error (-504) I've tried clearing cache and data for Google Play Store and Google Play Services but no luck. I even tried downloading APK Installer but it doesn't even work. Please help I don't know what to do.
02-09-2017
<UPDATE>
I'm at a loss, so I decided to do a factory reset from settings and that did not get the applications to install. So then I tried to clear the cache but again no suck luck. Then I decided to enter recovery mode and factory reset, but then got stuck on "Your tablet is getting ready for you". or something along the lines of that and wouldn't get past that on start up. (This is because I disabled setup with another application, and is my fault.) Not being able to get past that I realized I had no choice but to Re-Flash the System Update LMY47X.T377VVRU1AOL7 (5.1.1) Lollipop with Odin and that was successful, thank God. Now I have to Re-Root and before installing the wrong applications, which are Google Play Store SuperSu and Titanium Backup. Reason being that once you install these once and uninstall them you can't install them again without getting error (-504) in Google Play Store or even outside the Google Play Store such as manually downloaded .APK files or you will get the error "APP not installed".
Here is my idea, and I haven't done it yet. Re-Flash, Re-Root, Install for the FIRST time the right SuperSu.apk and Titanium Backup Pro.apk in order to disable Knox and stop the never ending Re-Root every time the tablet it restarted.
02-10-2017
<UPDATE>
I have been running Kingoroot with my PC using USB. This gives me temporary Root access until Re-Boot. So I installed Kingoroot.apk and tried using to mobile application but this one works, but I get stuck in bootloop on restart of tablet. Then have to Re-Flash with Odin to get out of bootloop. I'm not having any luck.
#2.) Even with my temporary root I can not seem to install Xposed because of SDK 22 not supported. I was wondering if anyone knows a way to get it to work on SDK 22 so I can run IMEI Changer. Unless there is another way to change the IMEI without Xposed.
Thank you to electronhacker for your post I found on this forum which has made me a lot of progress, and thank you moonsh0t for your help redirecting me to find that firmware. :good:

I just got a SM-T377V this weekend and have been trying o root it as well. Wow seems like nobody has had any luck getting a reliable root on it. Please update me as you keep at it! Brent your attempts at this are amazing!! Keep at it!

I'm trying to get this thing rooted too, so please keep me updated if you find a
Way!! Thanks for your help!

Yep
Ok

Same issues here. I never have trouble rooting with the APK, but its super annoying having to reroot all the time. also the superuser app is absolute cancer so learning to replace that would be dope.

Alright, so your goal is to run an IMEI changer, but why?
Also my luck was to get it temped root and try and use chainfire's supersu to take over.
from there I tried unlocking the bootloader with samdunk. The issue though, is the CID was deleted from the tablet, so when I restarted, never ending bootloops.
I just Odin'd it back to the AOL firmware today, will look more into samdunk later.

Treyday645 said:
Same issues here. I never have trouble rooting with the APK, but its super annoying having to reroot all the time. also the superuser app is absolute cancer so learning to replace that would be dope.
Click to expand...
Click to collapse
If you use Odin to flash android 5.1.1 via package T377VVRU1AOL7, you can use the kingroot or kingoroot app (desktop or android) to temporarily root the device. From there, if you delete the kingroot or kingoroot app from the device you can use SuperSu to take the binary over. From there you can use any flashing apps you'd like.
The issue is at this point, the second the device turns off, when it comes back it will no longer have root. (note so far in my attempts I've found that Kingroot, will reboot rootless, whereas kingoroot will bootloop.)
Kingoroot will bootloop because it modifies the boot file in some way, which causes the bootlooping. The work around to this is just flashing over the previous android. However, if you flash with Odin, you lose root, but keep your files.
Going back to flashing, when you attempt to use Odin to flash other packages, they are denied, due to the locked bootloader, however, you can use Flashfire to flash these firmwares. I attempted to flash the T-377P firmware and bootloader. Obviously the locked bootloader stayed locked, the recovery partition got errored out, but the android system itself actually started. Just sans root.
It's worth noting I've also attempted using SamDunk, the S5 bootloader unlocking tool, and so far all I've noticed is it deletes the CID file and doesn't finish. So I'm of the impression that the temp root, isn't a full root either.

Magisk GT King compatible

Hi all, has any GT King owner tried to root it with Magisk?
Many thx!

PLAY911 said:
Hi all, has any GT King owner tried to root it with Magisk?
Many thx!
Click to expand...
Click to collapse
Does not work and trying it will remove the current root on the device which will require re-flash of ROM to get it back.

syked said:
Does not work and trying it will remove the current root on the device which will require re-flash of ROM to get it back.
Click to expand...
Click to collapse
Yes I learned this hard way . Flashed it and lost root . Hoping something can be done soon enough to get Magisk supported on this device . Currently I'm still on without root which is fine for some apps that will not run on root . Unfortunately one of the sports app that detects root which works now keeps bombarding my device with pop-ups ads . Really unusable .

[email protected] said:
Yes I learned this hard way . Flashed it and lost root . Hoping something can be done soon enough to get Magisk supported on this device . Currently I'm still on without root which is fine for some apps that will not run on root . Unfortunately one of the sports app that detects root which works now keeps bombarding my device with pop-ups ads . Really unusable .
Click to expand...
Click to collapse
You could just force close the app in question and that way the ads won't appear in the background. Surely the ads won't appear when using the app and watching your sport.
Otherwise you can can flash the stock rom again (this will re-root) but will delete your data.
Alternatively, download blokada which is a ad blocking software. The catch is if you run an actual VPN, you won't be able to run this together as it's also treated as a VPN.

syked said:
You could just force close the app in question and that way the ads won't appear in the background. Surely the ads won't appear when using the app and watching your sport.
Otherwise you can can flash the stock rom again (this will re-root) but will delete your data.
Alternatively, download blokada which is a ad blocking software. The catch is if you run an actual VPN, you won't be able to run this together as it's also treated as a VPN.
Click to expand...
Click to collapse
They do trust me . When you watch live or replay games 5-10 min you just get full screen plastered add that won't go away unless you close it yourself sometimes 2 times and game gets paused while that happens . Tried Blokada didn't work some apps won't even start while running even if white listed . Only one that does the job best is AdAway which requires root obviously but then sport app will not run since detects root and so on and on.....very annoying .

[email protected] said:
They do trust me . When you watch live or replay games 5-10 min you just get full screen plastered add that won't go away unless you close it yourself sometimes 2 times and game gets paused while that happens . Tried Blokada didn't work some apps won't even start while running even if white listed . Only one that does the job best is AdAway which requires root obviously but then sport app will not run since detects root and so on and on.....very annoying .
Click to expand...
Click to collapse
Yeah I can imagine that's annoying. There is a way to install magisk but you have to use the recovery partition. Have a read through magisk instructions and how to load it into the recovery partition.
Ive tried it and and it works but you have to boot into recovery every time and will actually start the system but with magisk installed.
You could boot into recovery once and keep the device on.
You do lose the actual recovery partition though...but guessing you could fast boot via ADB to load that or maybe having the recovery on the SD card and depressing the reset pinhole underneath whilst plugging in power.
Btw, what streaming app are you using? I'm also a fellow Aussie.

syked said:
Yeah I can imagine that's annoying. There is a way to install magisk but you have to use the recovery partition. Have a read through magisk instructions and how to load it into the recovery partition.
Ive tried it and and it works but you have to boot into recovery every time and will actually start the system but with magisk installed.
You could boot into recovery once and keep the device on.
You do lose the actual recovery partition though...but guessing you could fast boot via ADB to load that or maybe having the recovery on the SD card and depressing the reset pinhole underneath whilst plugging in power.
Btw, what streaming app are you using? I'm also a fellow Aussie.
Click to expand...
Click to collapse
G'day mate . Optus Sport . Will give that a try I guess . This is by far the best Android Box I ever owned getting Full Magisk working on it would make this amazing . I also own one of X96 Android Box which runs Android 8.0 . Got Magisk installed and managed to hide app . Unfortunately box just doesn't seem to like Magisk at all so I deleted it . Luckily app starts ok . But there 's heaps of issues with this one video lags, freezes sometimes not a daily device at all . That is the reason I got myself Gt-King in the first place .

[email protected] said:
G'day mate . Optus Sport . Will give that a try I guess . This is by far the best Android Box I ever owned getting Full Magisk working on it would make this amazing . I also own one of X96 Android Box which runs Android 8.0 . Got Magisk installed and managed to hide app . Unfortunately box just doesn't seem to like Magisk at all so I deleted it . Luckily app starts ok . But there 's heaps of issues with this one video lags, freezes sometimes not a daily device at all . That is the reason I got myself Gt-King in the first place .
Click to expand...
Click to collapse
G'day mate.
That's strange. I have never seen Optus sport display pop up ads. I've just watched over 15 mins of an UEFA Champions league game on my un rooted Android tablet using the Optus sport app and there were no ads.
Are you sure there's no other apps running in the background that could be generating the pop up ads but thinking it's Optus sport.
Agreed. It is an awesome box
For me it was just easier to Chromecast from my phone or tablet when using the Optus sport app because I couldn't be bothered continuously loading into recovery to have magisk hide work and I don't see the point to leave my box on just for that reason.
As it stands my box is default rooted and I'm using ALVATECHs rom which I find works great.
I'll post some steps later to help you and others loading magisk though.

Magisk in Recovery mode
Before anything always back up your box. If you use TWRP then create a whole back up which makes it easier to restore and if don't use TWRP then maybe you should.
To get Magisk working on the GT-King follow these steps.
Magisk will be installed into the recovery partition so if you flash the image to recovery, you will loose TWRP or default recovery but you could use an SD card to load into TWRP or default recovery and similarly you can use the patched recovery image from Magisk to and load that from SD card when required. I have not worked out how you can load Magisk recovery partition but also load TWRP when required. Technically this is possible because it's a patched recovery image with TWRP. There might be some sort of key sequence that will allow this but have not played enough with it to work it out. If you leave your box on all the time it should be fine because you can boot into "magisk recovery" once and then leave it on.
1) You need a recovery image.
a)If you have root already (such as default root), you can use this command in a terminal app which will covert the recovery file from the system to recovery.img and we will save it on the internal storage (home level).​
Code:
dd if=/dev/block/revovery of=/mnt/sdcard/recovery.img
b) if you don't have root because you tried flashing Magisk through TWRP or have manually unrooted then or if you can't be bothered using terminal, you can use my recovery.img here recovery image and save this to a location of your choice​2) Download and install Magisk Manager APK from here
3) In Magisk manager main screen click advanced options tick Recovery mode
4) Now next to Magisk Click install then selection the option where you have to select the image
5) Select the image file from either step 1a) or 1b)
6) Give it a few moments and Magisk manager will create a patched recovery img to the same location as the original recovery img
7) Now you need to unroot your device if it's not already by trying to flash Magisk in TWRP. I use impactor universal unroot for this which can be sourced from the play store or other means and follow the instructions in the app. After you restart, the device is no longer rooted but we will need use the magisk patched recovery which will give you root
Now here is where you decide what to do next....
i)Do you boot into existing TWRP recovery via depressing the reset pinhole whilst plugging in the power and then permanently flashing the new patched recovery image or
ii)Do you copy that patched recovery image to a SD Card, renaming it to recovery.img and booting off that temporarily via depressing the reset pinhole whilst plugging in the power
Either way, once you boot into that "magisk recovery" it is now installed and works a treat and have root access but you can hide root per app via Magisk hide
The systemless-host module can be installed via the module manager if you use Hosts file to block ads (I use energized host file for this). I think the path for this after it's installed is /data/adb/modules/hosts

Really appreciate effort and detailed info mate . Will try that later tonight and will let you know. Cheers
Sent from my SM-G950F using Tapatalk

I flashed the magisk_patched/stock-recovery.img with twrp.app and worked!

Many thanks to Syked for this detailed info how to get Magisk working.
Maybe somebody could confirm this is working on the new 2022 GT king ii with the Amlogic a311D2 CPU.
Magisk is a must for me so I'm not buying until this is possible.