Help Rooting LG Riso 3 (LMX210CMR) Oreo 8.1 - Android Q&A, Help & Troubleshooting

I've spent so much time on this forum and learned so much that I thought this is best place to go for my last resort. I really need to root this phone. I want to be able to use some rooted apps and especially be able to get more apps on my SD Card. My phone is unlockable (In fact Cricket said all their current phones are) I have no fastboot, no proper recovery mode and not even a bootloader mode. When I type adb reboot bootloader it only reboots the phone. I've looked into flashing a new boot, but I don't completely understand how to make or how to get all the any of the Qualcomm flash tools required files. I'll need help with that if it comes to it. I can't even flash a different models stock, because all LG stock I can find is ARB00 and right now I'm ARB03 it doesn't matter if it's even a higher version stock like Pie or even a it's LG G7 ThinQ unless it's ARB03 or higher I can't flash it and of course I can't downgrade. Which would save me a lot of headaches because the Nougat version at least still has fastboot and is ARB00. Something I can work with.
I am about to go to Walmart and just buy it again, because their version is still Nougat. That's what I'll do if I find no answer here, but I want to give this phone another chance. I read this phone can be rooted with Magisk, but with no recovery and no fastboot unless there's another option I don't know if that's even an option. Is there any way to dd install Magisk? If so please let me know. I've also been told it needs to be manually rooted, but I don't know where to get started doing that. I know it's get the right su files in the right places, and busybox but how do I do that with no root to start with, and being unable to mount the system? Is there a way?
I'm seriously willing to try anything at this point even if it will brick my phone. I have insurance on it that will replace it no matter how much damage I cause it and like I said am willing to re-buy the phone at Walmart which might be the better option since getting it from Cricket will most likely just take me back to where I started with an 8.1 phone that I can't do anything with. I don't care much about custom roms or that sort of thing. There isn't any for this phone anyway. I just want it rooted! please if you can think of anything, anything at all please let me know!
I have Windows 10 and Ubuntu
Also If these will help
Partitions:
HTML:
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 DDR -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 aboot -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 abootbak -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 apdp -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 boot -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 cache -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 cmnlib -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 cmnlib64 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 cmnlib64bak -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 cmnlibbak -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 devcfg -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 devcfgbak -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 devinfo -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 dpo -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 drm -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 dsp -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 eksst -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 encrypt -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 factory -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 fota -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 fsg -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 ftm -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 grow -> /dev/block/mmcblk0p60
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 keymaster -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 keymasterbak -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 keystore -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 laf -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 lafbak -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 mcfg -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 modemst1 -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 modemst2 -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 mpt -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 msadp -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 persist -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 persistent -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 raw_resources -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 raw_resourcesbak -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 rct -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 recovery -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 recoverybak -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 rpmbak -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 sbl1 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 sbl1bak -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 sec -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 sns -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 spare1 -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 spare2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 spare3 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 spare4 -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 spare5 -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 srtc -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 system -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 tzbak -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 userdata -> /dev/block/mmcblk0p59

---

Nothing?
Okay from the lack of any reply I'm guessing there isn't a current way to root this device or nothing anybody knows. So I guess I'll get the Nougat version then, and see if I have better luck with it or wait until I save up enough money for another phone that I can unlock and root. If anybody thinks of anything I'm still willing to try, but I'm getting it's about time to give up and just never buy directly from cricket again.

---

@sjjtnj
Rooting a phone's Android doesn't depend on its Android version but whether it's bootloader can get unlocked or not what basically prevents rooting Android. Take note that not all OEMs/Carriers allow this.
If phone in question is accessable via ADB then to find this out you run this command sequence
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If 1 is returned then phone's bootloader is unlockable otherwise not.

---

Thanks!
jwoegerbauer said:
@sjjtnj
Rooting a phone's Android doesn't depend on its Android version but whether it's bootloader can get unlocked or not what basically prevents rooting Android. Take note that not all OEMs/Carriers allow this.
If phone in question is accessable via ADB then to find this out you run this command sequence
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If 1 is returned then phone's bootloader is unlockable otherwise not.
Click to expand...
Click to collapse
Thanks this is gave me some hope! I got a 1 so I guess it is unlockable! I can't use fastboot though. If I can figure a way to enable it maybe I can unlock and root it. The Nougat version still has fastboot enabled so that's why I wanted it, but it would be nice to find a way to unlock this one.

---

@sjjtnj
It's well known that not all OEMs/Carriers support Fastboot as intended by Google. They think that providing Revovery is enough.
FYI: The phone in question has a Recovery partition - as that's default with all Android devices. You enter Recovery mode this way
Code:
adb devices
adb shell "reboot recovery"
Now once you are in recovery, ADB will work instead of Fastboot.
Anyway:
Have you already tried
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
to unlock phone's bootloader - what requires the USB drivers suitable at 100% to the phone are got installed on your Windows computer?
How-To:
1. Download the Android Fastboot Tool v1.2 from here.
2. Once you have downloaded the file, extract the zip file.
3. When you are done with the extraction you open the tool by clicking on Android Fastboot .exe file as Adminstrator.
Note: Never have tried out this.

---

jwoegerbauer said:
@sjjtnj
It's well known that not all OEMs/Carriers support Fastboot as intended by Google. They think that providing Revovery is enough.
FYI: The phone in question has a Recovery partition - as that's default with all Android devices. You enter Recovery mode this way
Code:
adb devices
adb shell "reboot recovery"
Now once you are in recovery, ADB will work instead of Fastboot.
Anyway:
Have you already tried
to unlock phone's bootloader - what requires the USB drivers suitable at 100% to the phone are got installed on your Windows computer?
How-To:
1. Download the Android Fastboot Tool v1.2 from here.
2. Once you have downloaded the file, extract the zip file.
3. When you are done with the extraction you open the tool by clicking on Android Fastboot .exe file as Adminstrator.
Note: Never have tried out this.
Click to expand...
Click to collapse
Rebooting recovery gives me the little green guy passed out with a triangle with exclamation mark as a heart and says no command. I clicked the buttons you're supposed to click with that error to get the recovery options, but it just reboots. Sometimes though very randomly I do get to a place to wipe data and reset the phone. So I say the recovery works about .05% of the time. Unfortunately I can't flash new partitions with dd without root so no changing the boot.img or recovery.img like I had hoped either. Thank you! I haven't saw that tool before, I'm on Linux right now, but will download it as soon as I get back on Windows. I'll update after I try it.

---

Still need to try
jwoegerbauer said:
@sjjtnj
It's well known that not all OEMs/Carriers support Fastboot as intended by Google. They think that providing Revovery is enough.
FYI: The phone in question has a Recovery partition - as that's default with all Android devices. You enter Recovery mode this way
Code:
adb devices
adb shell "reboot recovery"
Now once you are in recovery, ADB will work instead of Fastboot.
Anyway:
Have you already tried
to unlock phone's bootloader - what requires the USB drivers suitable at 100% to the phone are got installed on your Windows computer?
How-To:
1. Download the Android Fastboot Tool v1.2 from here.
2. Once you have downloaded the file, extract the zip file.
3. When you are done with the extraction you open the tool by clicking on Android Fastboot .exe file as Adminstrator.
Note: Never have tried out this.
Click to expand...
Click to collapse
Sorry I haven't got this tried yet. I was trying to set up my Linux when it messed up and I had to restart the process. I'm keeping backups this time, but anyway just finishing that because I had to stop when I got a concussion. On the picture, it says to get in fastboot mode. I can't do that only download mode. So I don't think it will work, but I'll still try. I decided I'm going to rebuy the phone from Walmart that has Nougat and fastboot still enabled. That seems my only hope to unlock a phone and root it. The Nougat version is also ARB00 so I can flash firmware of a variant on that one if I need to as well. I know it sounds crazy to buy the same phone, but it's really all I can afford at this time. I'm saving up money for a better phone though, and my nephew has a really bad phone right now. So I can just give this one to him. He doesn't need root or anything so he'll like it.