[Android General] FijiWaterDrinker:
Yeah I get that, just wish they would've made it more like Pixi 4, Pixi 5, Pixi 6, Pixi 7, etc... So there wouldn't be any confusion. And they aren't really almost identical if they use different SoC's which in my case qualcomm is very different since the same tools you know of and use you said don't work on qualcomms right? So I shouldn't try to use the SPFT flash tool right? Yea not going to if it's only for MTK devices.

So mine is a Pixi 4 (4.5") 4060W then, just wanted to confirm that, now I at least know that, thanks. Kingoroot calls it a Pixi445 as in Pixi 4 (4.5) and Kingroot identifies it as a TCL 4060W

How could it not have fastboot mode, but have the OEM unlocking option? I don't understand that. To another user you said maybe it's already unlocked, I think that's a possibility, otherwise it's silly for them to tease you with the OEM unlocking option but not allow a way to actually do it.

As for Kingroot, is that the same people who make King-o-root? It seems like it as they are very similar and I tried both of them again with their latest APK app downloads. It says it has a root strategy but doesn't say what it's actually attempting to do. Wish it did as then maybe I'd have more success reproducing the method manually. They say try the windows version and you might have more success, well my windows is screwed up right now as I mainly use Linux, so I'll have to re-install windows to try it that way. On the plus maybe it'll provide more info to what it's trying to do and maybe actually work.

Well on my main device I use SuperSU and there is an option for systemless root. Although checking that box within SuperSU won't be possible and it would have to be a SuperSU configured to be systemless from the get go. Browsing the SuperSU site though it's not clear how to make sure your flashable SuperSU zip will be installed in the systemless fashion.

On the plus side 288 people (and I'm the 289th) have requested for Kingroot to figure out a working root method for my particular device, but it says not enough. When do they usually do that? On 300 people? :D lol

P.S. I suppose I'll have to wait it out if nothing can be done at this time. Or if I can figure out a way to change my WiFi MAC address on this device then I almost wouldn't need root. Or I can always just make that one App I've been thinking of making in which location services are only enabled when I change a flag on my site that says I lost it, and then it tracks it's movements while preventing location services from being disabled, so I can go pick it up! It will have to be a deep system level process though that no one knows about, not even the likely thief that grabbed it. It can even maybe automatically answer my call and turn on speaker phone, so I can ask the person to return the device to me or else send the police to their current location if they want to be an asshole. Extreme measures, but I don't like tracking myself by keeping location services on all the time and need a way to only turn it on if I actually lose the device... :)

Thanks though Kirito and if you learn anything new about what can be done with Qualcomms let me know!

EDIT: I just for the hell of it tried to get into fastboot mode again, this time by unchecking and re-checking USB debugging and hitting ok, unchecking and re-checking OEM unlocking and hitting ok, then:

user@Linux:~$ adb devices
List of devices attached
XXXXXXXX	device

user@Linux:~$ adb reboot bootloader
user@Linux:~$ fastboot devices
user@Linux:~$ fastboot devices
user@Linux:~$ fastboot devices
user@Linux:~$ fastboot devices
user@Linux:~$ fastboot devices
user@Linux:~$ fastboot devices
user@Linux:~$ fastboot devices
user@Linux:~$ fastboot devices
user@Linux:~$ fastboot devices
user@Linux:~$ fastboot devices
user@Linux:~$ fastboot devices
user@Linux:~$ fastboot devices
user@Linux:~$ fastboot devices
user@Linux:~$ fastboot devices
user@Linux:~$ fastboot devices

And... nothing. By the time the last fastboot devices command was sent it was already starting to boot up normally indicating that it was just a standard reboot not a reboot into fastboot mode. Oh well...