LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Mobile (https://www.linuxquestions.org/questions/linux-mobile-81/)
-   -   OEM command not working on Fastboot mode, Android 4.4.2 / Linux Mint 17.3 (https://www.linuxquestions.org/questions/linux-mobile-81/oem-command-not-working-on-fastboot-mode-android-4-4-2-linux-mint-17-3-a-4175614847/)

orestisfra 10-01-2017 07:42 PM

OEM command not working on Fastboot mode, Android 4.4.2 / Linux Mint 17.3
 
Hello forum,

I try to unlock the bootloader on my android phone (4.4.2 android, MLS iQ1055 model same idVendor as HTC, mt6582 processor) but when I try to execute any of the oem commands, the command doesn't seem to execute. It get stuck with 3 dots in the terminal and doesn't move. Also the phone does nothing. I have to either reboot the device manually or Ctrl+C + unplug the device and plug it in again to fix this.

I tried: changing the cable, changing the usb port, reinstalling ADB, using the ADB drivers given from my operating system's repositories, using the ADB drivers offered by google, running everything as root, creating a new rule in /etc/udev/rules.d/, adding my user to plugdev group, restarting udev.

What works: every ADB command. When my device is on Fastboot mode works everything except oem commands.

What doesn't work:
Code:

fastboot oem device-info
and
Code:

fastboot oem unlock
they give this output
Code:

...
and I can do nothing.

I use linux mint 17.3. Please tell me if you need more information about my setup or the issue. I have read a ton of tutorials on this topic none of them worked. I can give the links if you want but I don't want to make this topic huge.

Thank you in advance


EDIT:

I tried the same commands on another device (Xiaomi RedMi Note 4):
Code:

fastboot oem device-info
gave this output:
Code:

...
FAILED (remote: unknown command)
finished. total time: 0.002s

So are the oem commands no longer working?
Code:

fastboot getvar all
is working and says the bootloader is locked as it should do but I don't wanna mess up this phone so i didn't try anything else.

I got into fastboot of the other device again (MLS phone) and tried:
Code:

fastboot flashing get_unlock_ability
,
Code:

fastboot flashing get_unlock_bootloader_nonce
the output was:
Code:

...
then typed:
Code:

fastboot flashing unlock_critical
and got:
Code:

...
FAILED (command write failed (Success))
finished. total time: 0.000s

this statement contradicts itself and nothing happened on the phone. Then i tried
Code:

fastboot flashing unlock
with output:
Code:

...
FAILED (status read failed (Protocol error))
finished. total time: 5.032s

nothing on the phone but at least it gives an output now...

EDIT 2:
Code:

fastboot flashing getvar all
didn't say if the bootloader is unlocked or not.

orestisfra 10-11-2017 12:43 PM

sorry for the double post but i wanted to inform you that i don't have the phone anymore and to warn everyone NOT TO USE KINGROOT ONE CLICK ROOT APP OR ANY ONE CLICK ROOT APP ON YOUR PHONE! it's better to take your time back up what you need, reset and root properly through a computer (any operating system).

if someone has the same phone (MLS iQTalk color 1055) you can find a stock rom here: https://www.needrom.com/download/mls...-color-iq1055/ but any stock rom for any mt6582 phone will work, if you don't want the MLS applications that come preinstalled with the phone.

this is not solved but there is no need to reply. something went wrong when i tried to use the app mentioned above in the past.

X-LFS-2010 10-11-2017 03:31 PM

Return for refund and get one that works. Succeeded!


All times are GMT -5. The time now is 12:00 AM.