Fastboot not working in mt6592 tablet (stuck in ...)

[colibris79]

Hi everyone,
I have been reading posts here and in other sites trying to solve this problem. But since I haven't been able to do it I have registered and post here

I have an mt6592 Chinese tablet and I have been trying to make the fastboot commands work but it gets stuck with the three dots:

Code:

mik@mik-Lenovo ~ $ adb reboot bootloader
mik@mik-Lenovo ~ $ fastboot devices
0XXXXXXABCDEF    fastboot
mik@mik-Lenovo ~ $ fastboot oem device-info
...

Adb is working fine and in bootloader mode the computer finds my device, but I just can do anything with the fastboot commands. I have tried in both Linux and Windows PCs and both have the same results. I can connect other devices and use bootloader mode normally so my guess is that there has to be some kind of problem with this tablet.

The only different thing that has happened compared to my other devices is that Supersu never asked for permission for the Adb shell, although in terminal it says that it is ok:

Code:

mik@mik-Lenovo ~ $ adb root
adbd is already running as root

I've tried to erase the data from Supersu to get the prompt for the adb shell but I just didn't pop up (and I had to authorize again all the other apps )
I have also tried running fastboot as root in my Linux computer and many other commands but I get the same result.


Any suggestions about how to get fastboot to work again?
Thanks

[cookiedough]

Have you tried

Code:

fastboot oem unlock

[colibris79]

Have you tried

Code:

fastboot oem unlock

Yep, same result. The only one working is:

Code:

fastboot reboot

[cookiedough]

Yep, same result. The only one working is:

Code:

fastboot reboot

What version Android is it? Did you check developer mode in settings to see if there's a bootloader unlock option there?

[colibris79]

What version Android is it? Did you check developer mode in settings to see if there's a bootloader unlock option there?

Hi again cookiedough, thanks for your your answers
I had checked developer options as well, but it has no unlock option. Apparently it is Android 6.01 but it seems like it has a lot of Kitkat (4.4) and in CPU-Z it says it is Api 19 .

I also have tried different cables, computers, reinstalling Supersu, installing supersu as a system app. I still would like to know why I never get the prompt from Supersu to authorize the Adb shell. Do you think it could be related?

[DirKNirK]

The problem is mt6592 (if it's really even mt6592. It could be even lower/older chip) and MTK KitKat does not have proper bootloader like Snapdragon and newer MediaTek processors. You can't flash or unlock from here because there's nothing to unlock.

How did you install SuperSU?

What you need to do if you're trying to root is install SuperSU.zip through a TWRP or CWM made for your tablet.

For adb there maybe wouldn't be a SuperSU popup unless making some root commands, but you should get a device authorization request at least one time. You can check adb authorization by "adb devices"

[colibris79]

The problem is mt6592 (if it's really even mt6592. It could be even lower/older chip) and MTK KitKat does not have proper bootloader like Snapdragon and newer MediaTek processors. You can't flash or unlock from here because there's nothing to unlock.

How did you install SuperSU?

What you need to do if you're trying to root is install SuperSU.zip through a TWRP or CWM made for your tablet.

For adb there maybe wouldn't be a SuperSU popup unless making some root commands, but you should get a device authorization request at least one time. You can check adb authorization by "adb devices"

Thanks for your explanation. I installed Supersu after rooting with Kingroot (first I installed an older version to change the binary). I have tried using the shell as root in adb which usually would bring up the Supersu prompt. But when I run "adb shell" it directly goes into root-shell mode:

Code:

mik@mik-Lenovo ~ $ adb shell
root@X9:/ #

If you check the first post I also was getting this from "adb root":

Code:

mik@mik-Lenovo ~ $ adb root
adbd is already running as root

I'll try to install TWRP next then.

[cookiedough]

Thanks for your explanation. I installed Supersu after rooting with Kingroot (first I installed an older version to change the binary). I have tried using the shell as root in adb which usually would bring up the Supersu prompt. But when I run "adb shell" it directly goes into root-shell mode:

Code:

mik@mik-Lenovo ~ $ adb shell
root@X9:/ #

If you check the first post I also was getting this from "adb root":

Code:

mik@mik-Lenovo ~ $ adb root
adbd is already running as root

I'll try to install TWRP next then.

Can I ask what it is you're trying to do? I mean, just curious, Or are trying to achieve some goal?

If you can copy to /system and rootchecker says you're rooted and you're getting the "#" when you type "su" in adb, then you're good to go.

Is it that you're trying to replace KingUser with SuperSU?

[colibris79]

Can I ask what it is you're trying to do? I mean, just curious, Or are trying to achieve some goal?

Is it that you're trying to replace KingUser with SuperSU?

The tablet is rooted and I am using Supersu just fine.
I just wanted to be able to use fastboot commands in case I needed it (it is always good to be able to access the bootloader in case anything bad happens). Also wanted to be able to confirm that the bootloader was unlocked. But if what DirKNirK says is right I won't be able to use fastboot commands with this tablet so I will just keep on and install TWRP

[cookiedough]

The tablet is rooted and I am using Supersu just fine.
I just wanted to be able to use fastboot commands in case I needed it (it is always good to be able to access the bootloader in case anything bad happens). Also wanted to be able to confirm that the bootloader was unlocked. But if what DirKNirK says is right I won't be able to use fastboot commands with this tablet so I will just keep on and install TWRP

Right. Dirknirk speaks true. It's only been since last year or two that MTK started to use locked and proper bootloader.

You can TRY something like "fastboot boot recovery.img" just for curiosity and see what happens. It won't cause any problems. Probably will just do similar like before and show "..." or do nothing.