my device is asus zenfone c z007, anyone know how to unlock this device, or related to unlock this device. I has been searching all the threads but I can't find one, please help me to unlockbootlader this device. I only find to unlock app for asus A400CG with the same specification.http://dlcdnet.asus.com/pub/ASUS/ZenFone/A400CG/Unlock_Tool_A400CG.zip from this threads https://forum.xda-developers.com/zenfone-4/cm-12-1-cyanogenmod-12-1-asus-zenfone-4-t3249637.
.
.
here the specification + compare = https://www.ubergizmo.com/products/lang/en_us/devices/zenfone-c,zenfone-4/
@ArthurBalaOs
Before wasting your time with this check for boot-loader can get unlocked
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
jwoegerbauer said:
@ArthurBalaOs
Before wasting your time with this check for boot-loader can get unlocked
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
Click to expand...
Click to collapse
ok it's nothing happened, but I try this command to my other device which supporting oem unlock it's nothing happened to. why ? btw, thanks :good:
0
ArthurBalaOs said:
ok it's nothing happened, but I try this command to my other device which supporting oem unlock it's nothing happened to. why ? btw, thanks :good:
Click to expand...
Click to collapse
May be they forgot to populate that entry...
Because not ADB but Fastboot is needed to unlock a Android device's boot-loader you always can try
Code:
fastboot devices
fastboot oem unlock
fastboot reboot
fastboot unlock-info
If outpout of last command is TRUE, then boot-loader got unlocked.
jwoegerbauer said:
May be they forgot to populate that entry...
Because not ADB but Fastboot is needed to unlock a Android device's boot-loader you always can try
Code:
fastboot devices
fastboot oem unlock
fastboot reboot
fastboot unlock-info
If outpout of last command is TRUE, then boot-loader got unlocked.
Click to expand...
Click to collapse
[COLOR="RESULT : FAIL (unknown OEM command)"][/COLOR]
that"s the result, what's that mean?
Seppppx said:
I checked the Asus website and I found no official unlocking tool for the zenfone c. I don't think I missed anything because other model have that.
Click to expand...
Click to collapse
nahh. they release the source code and kernel source, without unlocking tool. I mean everytime I trying to force unlock or force installing twrp the result always error
ArthurBalaOs said:
[COLOR="RESULT : FAIL (unknown OEM command)"][/COLOR]
that"s the result, what's that mean?
Click to expand...
Click to collapse
As I can see the version of Fastboot you use doesn't support the subcommand "OEM unlock":
Each OEM/Carrier has its own version of the Fastboot driver.
Try this instead
Code:
fastboot flashing unlock
BTW:
Become familiar with Fastboot subcommands supported on your device. Simply run
Code:
fastboot
or
Code:
fastboot OEM
you can see on this thread.
https://forum.xda-developers.com/zenfone-4/how-to-unlock-bootloader-asus-zenfone-c4-t3577340/amp/
Related
Hi, i have an acer liquid zest 4g t07, i cant find anyway on how to root it.
EDIT:
here's the solution https://forum.xda-developers.com/android/general/tutorial-root-acer-liquid-zest-4g-z628-t3534746
flamendless said:
Hi, i have an acer liquid zest 4g t07, i cant find anyway on how to root it.
Click to expand...
Click to collapse
Can you give me any information about your phone? model,kernel,android version,etc.
Ziisehahvulon said:
Can you give me any information about your phone? model,kernel,android version,etc.
Click to expand...
Click to collapse
According to CPU-Z
Model: T07 (t07_ww)
Manufacturer: acer
android version: 6.0
Api level: 23
Kernel: 3.18.19+(1469620262)
Would these suffice?
flamendless said:
According to CPU-Z
Model: T07 (t07_ww)
Manufacturer: acer
android version: 6.0
Api level: 23
Kernel: 3.18.19+(1469620262)
Would these suffice?
Click to expand...
Click to collapse
Do you have any any custom recoveries for your phone so we can flash a supersu.zip?
If not could you boot this recoveries I repeat boot not flash or install.
How to Boot into recovery without flashing:https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/
Custom Recovery:https://www.androidfilehost.com/?fid=24591023225178597
The custom recovery may not be for your phone but I have tried booting random recoveries to my phone similar to its specs and it worked!
SuperSU download in attachment
Is it possible to brick my device by that procedure?
flamendless said:
Is it possible to brick my device by that procedure?
Click to expand...
Click to collapse
Not the device but maybe the recovery but since you are booting it and not flashing it maybe it won't.I did this procedure to my phone but the 3g T06 model of acer liquid zest and it worked. Well I changed some links so that the recovery would be compatible for your chipset which is mt6735 and kernel 3.18.19+
PS.you need unlocked bootloader and developer options on for oem unlocking
Thank you, i will try that as soon as possible, although, whats the way to boot in bootloader in acer device?
flamendless said:
Thank you, i will try that as soon as possible, although, whats the way to boot in bootloader in acer device?
Click to expand...
Click to collapse
Turn off phone then hold power button and up button at the same time or you can boot in fastboot using ADB commands.
Make sure you have an unlocked bootloader and good luck!
PS. Unlocking bootloader formats the phone
Ziisehahvulon said:
Turn off phone then hold power button and up button at the same time or you can boot in fastboot using ADB commands.
Make sure you have an unlocked bootloader and good luck!
PS. Unlocking bootloader formats the phone
Click to expand...
Click to collapse
How to know if the bootloader is unlocked?
flamendless said:
How to know if the bootloader is unlocked?
Click to expand...
Click to collapse
I had problems for my phone but try this commands:
adb reboot bootloader
fastboot getvar all or fastboot oem device-info
if that doesnt work try:
adb shell
su
cat /proc/mtd
Ziisehahvulon said:
I had problems for my phone but try this commands:
adb reboot bootloader
fastboot getvar all or fastboot oem device-info
if that doesnt work try:
adb shell
su
cat /proc/mtd
Click to expand...
Click to collapse
Im in fastboot mode, but the device is not listed in adb
flamendless said:
Im in fastboot mode, but the device is not listed in adb
Click to expand...
Click to collapse
ADB cannot detect phone if in fastboot mode but fastboot commands can be accepted while adb commands cannot while in fastboot mode
after typing adb reboot bootloader type this command while in fastboot mode
fastboot get var all or just var if that doesnt work try fastboot oem device-info
if that doesnt work either reboot your phone not in fastboot mode type fastboot reboot then type this commands while you are in home screen
adb shell
su
cat /proc/mtd
Ziisehahvulon said:
ADB cannot detect phone if in fastboot mode but fastboot commands can be accepted while adb commands cannot while in fastboot mode
after typing adb reboot bootloader type this command while in fastboot mode
fastboot get var all or just var if that doesnt work try fastboot oem device-info
if that doesnt work either reboot your phone not in fastboot mode type fastboot reboot then type this commands while you are in home screen
adb shell
su
cat /proc/mtd
Click to expand...
Click to collapse
It just says waiting for device
flamendless said:
It just says waiting for device
Click to expand...
Click to collapse
do you have drivers for fastboot and adb?
If you do and still get errors get the latest version
When the cmd says waiting for device make sure that the device is in fastboot mode
its just a black screen with a text fastboot mode
Ziisehahvulon said:
do you have drivers for fastboot and adb?
If you do and still get errors get the latest version
When the cmd says waiting for device make sure that the device is in fastboot mode
its just a black screen with a text fastboot mode
Click to expand...
Click to collapse
Yes i have fastboot and adb, and yes the screen is black and theres a text at the bottom left that says fastboot mode
flamendless said:
Yes i have fastboot and adb, and yes the screen is black and theres a text at the bottom left that says fastboot mode
Click to expand...
Click to collapse
Try the version of adb and fastboot that I used
Ziisehahvulon said:
Try the version of adb and fastboot that I used
Click to expand...
Click to collapse
still says waiting for device,
flamendless said:
still says waiting for device,
Click to expand...
Click to collapse
That can be caused if you dont have drivers installed and are you sure you have developer options on and usb debugging on? Also bootloader unlocked?
Hmm can you give me a picture of the procedure?
Pic of the device and the pc.
The picture of the device while the pc is saying waiting device and vice versa
Ziisehahvulon said:
That can be caused if you dont have drivers installed and are you sure you have developer options on and usb debugging on? Also bootloader unlocked?
Hmm can you give me a picture of the procedure?
Pic of the device and the pc.
The picture of the device while the pc is saying waiting device and vice versa
Click to expand...
Click to collapse
Yes, in the setting, the usb debugging is enabled, and the allow bootloader to be unlocked oem something, i also hve the proper drivers installed,
I think the bootloader is something thats quite not right, tell me whats the complete details about that.
Ill try to provide images.
flamendless said:
Yes, in the setting, the usb debugging is enabled, and the allow bootloader to be unlocked oem something, i also hve the proper drivers installed,
I think the bootloader is something thats quite not right, tell me whats the complete details about that.
Ill try to provide images.
Click to expand...
Click to collapse
I'll give you proper details later I need to go to school
Hi guys!
does anyone knows how to unlock bootloader for lyf flame 1.
I have tried many methods but didn't work
I have tried getting into fast boot and typing "fastboot oem unlock" I am getting "FAILED <remote: unknown command>"
but nothing works.
i have tried using different tools (all in one tools, unlock my bootloader and many) but nothing works
it has been very hard to root my mobile as there is no full rooted script for my mobile and I have many tools to root my mobile(iroot,vroot,mobogenie,unlockroot,safe root,kingoroot,king root,mobile go,zroot,poot,etc) but kingroot has worked but not giving full permission. i cant give shell commands.
please help me to unlock my bootloader
my phone:LYF Flame-1 (LS-4503) running 5.1.1
kvbkiran said:
Hi guys!
does anyone knows how to unlock bootloader for lyf flame 1.
I have tried many methods but didn't work
I have tried getting into fast boot and typing "fastboot oem unlock" I am getting "FAILED <remote: unknown command>"
but nothing works.
i have tried using different tools (all in one tools, unlock my bootloader and many) but nothing works
it has been very hard to root my mobile as there is no full rooted script for my mobile and I have many tools to root my mobile(iroot,vroot,mobogenie,unlockroot,safe root,kingoroot,king root,mobile go,zroot,poot,etc) but kingroot has worked but not giving full permission. i cant give shell commands.
please help me to unlock my bootloader
my phone:LYF Flame-1 (LS-4503) running 5.1.1
Click to expand...
Click to collapse
If your android rooted using KingRoot then it must your bootloader is unlocked.
Try command in fastboot mode
"fastboot oem device-info" then see bootloader unlocked is true or false. If true means your bootloader is unlocked.
What ever i am typing its saying only "FAILED <remote: unknown command>"
Only the working code is "fastboot devices" 😥
kvbkiran said:
What ever i am typing its saying only "FAILED <remote: unknown command>"
Only the working code is "fastboot devices" 😥
Click to expand...
Click to collapse
Is your android detect in fastboot mode. When you run command fastboot devices then device shows their serial number.
yes it is showing my device with some serial key
is anytihng possible with download mode
Please anyone help me to unlock bootloader
please can anyone reply me
kvbkiran said:
please can anyone reply me
Click to expand...
Click to collapse
Have you enabled oem unlock option in developer setting.
yeah i did it but nothing happens
kvbkiran said:
yeah i did it but nothing happens
Click to expand...
Click to collapse
It may be because your android secure with FRP protection. Try Merapitool to remove FRP protection from your android.
there is nothing like that i have already bypassed frp
i have my resetted gmail account and also i have succesfully using my mobile
and i dont think removing frp will helps in unlocking bootloader
please help me i cant able to do anything from the bootloader
fastboot is detecting but cant able to execute any commands
Buddy may be ur boot.img needs to be modified root device using this . Toolkit
https://forum.xda-developers.com/android/general/how-to-rooting-guide-lyf-water-1-ls-5002-t3563825
Its a fastboot based if this works then other commands will start working
this is for LYF water
will it works me ?
please reply me
still i tried but still same problem
getting failed <remote: unknown command>
Can u send Boot.img
?
Also make sure usb debugging is enabled and drivers are installed for ur device .
please reply quick. Send me ur boot.img
Yes i have enabled the usb debugging and installed the perfect drivers for my phone
i have just extracted the boot.img from the flash file
https://drive.google.com/open?id=0B5f1QUUHbjhccjMzWHN3ZFNVVW8
Flame 1 and flame 8 these both devices have fastboot problems these devices never boot in fastboot properly. They just stuck at "power by android" screen when given command "reboot bootloder" or maually from recovery "reboot to bootloader"
Hey xda plz help me how to unlock bootloader for Lenovo a3300-hv plz help running ROM 4.4.2
Hi
I recently upgraded a Honor 5c to Nougat(which works)NRD90M test keys build. I did this through Flashfire to try and preserve root. It failed(what a surprise).
The device is recognised now with 'fastboot devices', by running ADB using root in Linux.
I can get into bootloader screen using fastboot and have unlocked the phone AGAIN to be sure. BUT, cannot flash TWRP which is vital. The error now is:
Sending 'boot.img' (24464 KB) OKAY [ 0.869s]
Booting FAILED (remote: 'Command not allowed') fastboot: error: Command failed
This suggests the phone is locked which is absurd. I think this is a permission problem within Android, it that possible?
It doesn't matter how I'm going to root, if I can't communicate the whole thing is usesless.
The same issue continues with ADB in Win10
Any thoughts hear, because I've trawled Google.
thanks
To clarify things: ADB and Fastboot are 2 completly different things. Fastboot deals with device's bootloader, whereas ADB deals with device's Android OS.
Run this command sequence
Code:
fastboot devices
fastboot getvar all 2>%TEMP%\phoneinfo.txt
fastboot reboot
type "%TEMP%\phoneinfo.txt" | more
which will get you a list of various variables on the phone with model and such useful things.
jwoegerbauer said:
To clarify things: ADB and Fastboot are 2 completly different things. Fastboot deals with device's bootloader, whereas ADB deals with device's Android OS.
Run this command sequence
Code:
fastboot devices
fastboot getvar all 2>%TEMP%\phoneinfo.txt
fastboot reboot
type "%TEMP%\phoneinfo.txt" | more
which will get you a list of various variables on the phone with model and such useful things.
Click to expand...
Click to collapse
Excuse if this format is incorrect
Thanks for that.
ADB and Fastboot are 2 completly different things
Click to expand...
Click to collapse
Sure
fastboot devices
Click to expand...
Click to collapse
MQH4C17330000094 fastboot
fastboot getvar all 2>%TEMP%\phoneinfo.txt
Click to expand...
Click to collapse
Returns to prompt
fastboot reboot
Click to expand...
Click to collapse
Works
type "%TEMP%\phoneinfo.txt" | more
Click to expand...
Click to collapse
getvar:all FAILED (remote: 'Command not allowed')
Finished. Total time: 0.005s
Same thing again
Cliff
cliffhanger54 said:
getvar:all FAILED (remote: 'Command not allowed')
Click to expand...
Click to collapse
That a Fastboot cmd does not work ( e.g. error Command not allowed ) is not unusual because Fastboot is different from version to version and also depends on how OEM/Carrier implemented it.
Again:
Bootloader and Android OS are different things, as this is same on PC where UEFI/BIOS and Windows OS are different things, too. A device's bootloader doesn't depend on any permissions granted within device's OS. A bootloader is a kind of software that runs as soon as you start up your phone. It tells the phone which programs are loading in order to make your phone run smoothly. This software packages all the instructions that are supposed to boot the Android OS, and initializes hardware and serves as security checkpoint.
Don't mix things up.
BTW:
Whether device's bootloader is unlockable / is already unlocked or not is stored in system file named build.prop.
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then unlocking bootloader is supported otherwise it's not.
or
Code:
fastboot devices
fastboot oem device-info
If "Device unlocked: true" is shown then bootloader is unlockedd.
jwoegerbauer said:
That a Fastboot cmd does not work ( e.g. error Command not allowed ) is not unusual because Fastboot is different from version to version and also depends on how OEM/Carrier implemented it.
Again:
Bootloader and Android OS are different things, as this is same on PC where UEFI/BIOS and Windows OS are different things, too. A device's bootloader doesn't depend on any permissions granted within device's OS. A bootloader is a kind of software that runs as soon as you start up your phone. It tells the phone which programs are loading in order to make your phone run smoothly. This software packages all the instructions that are supposed to boot the Android OS, and initializes hardware and serves as security checkpoint.
Don't mix things up.
BTW:
Whether device's bootloader is unlockable / is already unlocked or not is stored in system file named build.prop.
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then unlocking bootloader is supported otherwise it's not.
or
Code:
fastboot devices
fastboot oem device-info
If "Device unlocked: true" is shown then bootloader is unlockedd.
Click to expand...
Click to collapse
Thanks again for answering. I understand what you say. I've used Linux for 20 years and understand the differences. But where does this leave us/me. I should be able to flash TWRP into the recovery partition surely? Or are we dependent on software versions here as you say? It would be relatively easy in Linux and of course Android is based on it.
cliffhanger54 said:
I should be able to flash TWRP into the recovery partition surely?
Click to expand...
Click to collapse
TWRP completely removes device's default /recovery partition if it exists ( exists only on A-only Android devices), TWRP creates its own in device's /boot partition.
To flash TWRP on A-only ( or on current active boot slot if it's an A/B ) device
Code:
fastboot devices
fastboot flash boot <PATH_ON_PC_TO_YOUR_TWRP_IMAGE_HERE>
jwoegerbauer said:
TWRP completely removes device's default /recovery partition if it exists ( exists only on A-only Android devices), TWRP creates its own in device's /boot partition.
To flash TWRP on A-only ( or on current active boot slot if it's an A/B ) device
Code:
fastboot devices
fastboot flash boot <PATH_ON_PC_TO_YOUR_TWRP_IMAGE_HERE>
Click to expand...
Click to collapse
Thanks I think I've tried this one. I do get a different response though:
'fastboot: error: cannot get boot partition size'
I've seen suggestions that formating the boot partition is required - sounds extreme.
Why not simply re-flash device's Stock ROM to restore it to its original state ?
:good:
Sukrus said:
:good:
Click to expand...
Click to collapse
Yes wouldn't that be great. Have tried that from the beginning when I couldn't flash TWRP.
Put the Update.app on the SDcard, reboot the phone, hold down the buttons(tried them all), Bingo, it always takes me to eRecovery and how useless that is.
I have backups of Marshmallow with TWRP and Flashfire, which is why I took the flash TWRP route.
Wish I'd never upgaded now, although was forced to because of banking.
thanks
@cliffhanger54
I have noticed that current thread basically is a duplicate of this thread you started on XDA some days ago, too.
jwoegerbauer said:
@cliffhanger54
I have noticed that current thread basically is a duplicate of this thread you started on XDA some days ago, too.
Click to expand...
Click to collapse
Yes, couldn't really get anyone to answer, needed more info. Apologies. Will cease other question
Cliff
cliffhanger54 said:
Yes, couldn't really get anyone to answer, needed more info. Apologies. Will cease other question
Cliff
Click to expand...
Click to collapse
Right. After many attempts at other things I became convinced this was a locked bootloader problem despite the phone saying it was unlocked. Anyway have persisted in unlocking the phone several times and am now at a screen saying 'Your device is unlocked' but it also says 'you device is booting now'. But that's as far as it goes. If I turn the phone off it comes back to this screen and holding the power button+-volume also comes back to this screen, i.e I can't turn it off. How do I get back to the bootloader/fastboot mode or is this a genuine brick?
thanks
Cliff
cliffhanger54 said:
Right. After many attempts at other things I became convinced this was a locked bootloader problem despite the phone saying it was unlocked. Anyway have persisted in unlocking the phone several times and am now at a screen saying 'Your device is unlocked' but it also says 'you device is booting now'. But that's as far as it goes. If I turn the phone off it comes back to this screen and holding the power button+-volume also comes back to this screen, i.e I can't turn it off. How do I get back to the bootloader/fastboot mode or is this a genuine brick?
thanks
Cliff
Click to expand...
Click to collapse
Okay finally solved it. Let the battery run down as all I was getting was a bootloop. I was then able to get into fastboot mode with the necessary keys. From here i flashed TWRP but this required numerous attempts with different versions, finally got '3.1.1 venus' to load and the rest was straight forward!
thanks to everyone
I am trying to unlock the bootloader for my device (it's a cheap Chinese phone) and then root using Magisk. The first problem is that OEM Unlock option is not available in developer options, so I got no choice other than try unlocking using fastboot. Now the second problem is that fastboot doesn't show anything at all. Normally there is a Fastboot written at the top left corner of the device but in my case there is no output but the blank screen, and I do verify that my device is in fastboot mode because when I do fastboot devices, it show's the output:
Code:
C:\Users\Mujtaba>adb devices
List of devices attached
Y3123A0310Q0100020953 device
C:\Users\Mujtaba>adb reboot bootloader
C:\Users\Mujtaba>fastboot devices
Y3123A0310Q01000209 fastboot
Since fastboot was responding (partially), I tried to unlock the bootloader using different commands but each time I get read/write failed error.
Code:
C:\Users\Mujtaba>fastboot oem unlock
...
FAILED (command write failed (Unknown error))
finished. total time: 5.011s
C:\Users\Mujtaba>fastboot oem unlock
...
FAILED (status read failed (Too many links))
finished. total time: 80.886s
Alas, I got the same results with fastboot oem unlock-go and fastboot flashing unlock as fastboot is not accepting (at least I think) any command except fastboot devices.
I read the official guide and there I found that:
Devices should deny the fastboot flashing unlock command unless the get_unlock_ability is set to 1. If set to 0, the user needs to boot to the home screen, open the Settings > System > Developer options menu and enable the OEM unlocking option (which sets the unlock_ability to 1).
Click to expand...
Click to collapse
My device supports unlocking bootloader because I've checked the build.prop file using adb shell getprop and it includes the properties stated below:
The ro.oem_unlock_supported property should be set at build time based on whether the device supports flashing unlock.
If the device suppports flashing unlock, set ro.oem_unlock_supported to 1. If the device doesn't support flashing unlock, set ro.oem_unlock_supported to 0. If the device supports flashing unlock, then the bootloader should indicate the lock status by setting the kernel command line variable androidboot.flash.locked to 1 if locked or 0 if unlocked.
For devices that support dm-verity, use ro.boot.verifiedbootstate to set the value of ro.boot.flash.locked to 0; this unlocks the bootloader if the verified boot state is orange.
Click to expand...
Click to collapse
Code:
C:\Users\Mujtaba>adb shell getprop
[ro.oem_unlock_supported]: [1]
[ro.boot.verifiedbootstate]: [green]
[ro.boot.flash.locked]: [1]
[sys.oem_unlock_allowed]: [0]
.
.
Someone on reddit did this to find the OEM unlock state, mine of course returned 0 as you can see above.
Code:
adb shell getprop sys.oem_unlock_allowed
Device Specs:
CPU: ARM Cortex-A-7 @ 1.20 Ghz
GPU: Mali-400 MP
Board: sp7731cea (Unisoc aka Spreadtrum)
Build: Q Infinity C_MP_26_01
Treble: NA
Seamless update (A/B): NA
Your phone is based on Spreadtrum chipset. Means such a device has its own mechanism to unlock the bootloader.
jwoegerbauer said:
Your phone is based on Spreadtrum chipset. Means such a device has its own mechanism to unlock the bootloader.
Click to expand...
Click to collapse
Yes I know that and I already found a method but again it uses oem get_identifier_token to get Identifier token and when I do that fastboot returns nothing.
There are other methods as well, like getting a PAC file for your device then extracting boot.img from it, patching it with magisk manager and then flashing that single partition (in this case BOOT partition) using SPD Research Tool but it gives me error as well.
Install the matching Android USB Driver if not done yet. Having installed common ADB / Fastboot drivers isn't enough.
Additional advice: Replace Help in this thread's title by QMobile QInfinity C
jwoegerbauer said:
Install the matching Android USB Driver if not done yet. Having installed common ADB / Fastboot drivers isn't enough.
Additional advice: Replace Help in this thread's title by QMobile QInfinity C
Click to expand...
Click to collapse
I have installed SPD drivers and Google USB drivers however the problem is not with drivers because I can use the following commands without an issue:
Code:
fastboot devices
fastboot reboot
fastboot reboot bootloader
The problem occurs when using:
Code:
fastboot oem unlock
fastboot flashing unlock
Google's USB driver is only suitable to Google devices like the Pixel / Nexus.
As already said: Install the Android USB Driver matching your phone!
Take note that OEM's Fastboot implementation isn't always same as AOSP 's Fastboot.
IMO before trying to unlock a device's bootloader it's always a good idea to check by means of ADB whether unlocking the bootloader is natively supported on device:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
BTW: I no longer participate this thread.
jwoegerbauer said:
IMO before trying to unlock a device's bootloader it's always a good idea to check by means of ADB whether unlocking the bootloader is natively supported on device:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
Click to expand...
Click to collapse
I've already included this property in the post. It returned 1
first of i apologise if i have bad english
ok so i had this device for some time and decited to root it (my first time rooting a phone). And i need to unlock bootloader to flash stuff and i have all necessary things on my pc (platform tools,drivers,) everything seems to be working but as soon as i get into bootloader the only command that works is "fastboot devices" Any other commands dont work. I tried everything online and this is my only other thing left to do. I've been researching for 2 days at this point and i am almost certain that the commands are disabled by the company itself (like huawei) did anybody else ever root/unlock bootloader for this device because i didnt find any actual root guide for the particular device (besides from the auto generated ones like https://rootguia.com/how-to-flash-caterpillar-cat-s31/ https://mobilewithdrivers.com/unlock-bootloader/cat-s31-16gb-2gb-ram )
The exact error is:
FAILED (remote: 'unknown command')
fastboot: error: Command failed
(and this error is for every single command that uses fastboot besides from fastboot devices. Adb works just fine)
I tried:
reinstalling drivers
installing drivers that are "prepared" for the cat s31
changing cable
changing port to usb 2.0
reinstalling platform tools (from official google site)
checking device manager for the device (it shows up as android bootloader interface)
trying alternative oem unlock commands (fastboot oem unlock, fastboot flashing unlock and 2 other commands that i cant remember rn)
having oem unlocking and usb debugging enabled from the developer options
in my opinion the only explanation is the commands being disabled by default and even if it was it wouldnt be known if it was since most people dont root or purchase this device
please help me out here
fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
or
command finished but unlocking not allowed?
you can try to dump ROM, maybe it's possible to unlock bootloader on devinfo partition
https://github.com/bkerler/edl
aIecxs said:
fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
or
command finished but unlocking not allowed?
you can try to dump ROM, maybe it's possible to unlock bootloader on devinfo partition
https://github.com/bkerler/edl
Click to expand...
Click to collapse
sorry i forgot to mention im running android 8.1 oreo on this device and devinfo partition method will not work according to what i read
Never mind. anyway, if you dump phone in edl mode (or download stock ROM somewhere else) you can search aboot for device specific fastboot oem commands
How to Discover Hidden Fastboot Commands
There are many hidden fastboot commands on your device. In order to find them, we will need to dump the bootloader and examine the contents!
www.xda-developers.com
aIecxs said:
Never mind. anyway, if you dump phone in edl mode (or download stock ROM somewhere else) you can search aboot for device specific fastboot oem commands
How to Discover Hidden Fastboot Commands
There are many hidden fastboot commands on your device. In order to find them, we will need to dump the bootloader and examine the contents!
www.xda-developers.com
Click to expand...
Click to collapse
what do you mean by dump phone into edl mode do i download one of these https://ministryofsolutions.com/2022/01/cat-s31-edl-firmware-android-8-1-official-rom.html and install it from recovery mode and try to get it in edl mode and will it not work if i dont dump
just extract that ROM you found
aIecxs said:
just extract that ROM you found
Click to expand...
Click to collapse
and do what. im new to the rooting stuff
find the file aboot.mbn (or similar) and analyze for fastboot commands
aIecxs said:
find the file aboot.mbn (or similar) and analyze for fastboot command
Click to expand...
Click to collapse
so i downloaded the file and these are the things in the firmware file (attachement)
i cant find a file that looks or resambles aboot.mbn
it's emmc_appsboot.mbn so download strings for windows (see link post #4) and try to find fastboot commands, maybe you are lucky and find the proper command to unlock bootloader.
edit: not sure about Windows 10/11 comes with strings binary (powershell?)
aIecxs said:
it's emmc_appsboot.mbn so download strings for windows (see link post #4) and try to find fastboot commands, maybe you are lucky and find the proper command to unlock bootloader.
edit: not sure about Windows 10/11 comes with strings binary (powershell?)
Click to expand...
Click to collapse
sooo turns out win11 strings commands are kinda different or broken (probably not im just dumb) i just used notepad with ctrl+f and couldnt find anything besides the text that says are you sure you want to unlock bootloader but that is probably not related since i didnt find any commands or anything. So im actually going to attach the emmc_appsboot.mbn i know it looks sketchy you dont have to download it its totally understandable but if you do please do give it a check and respond. I want to get this done one way or another its 1 am i want to sleep ;(
could it be true that they made a truly un unlockable unrootable device
I had a look but there are no fastboot commands in it. However "oem unlock" is mentioned, so the usual fastboot oem unlock should work.
maybe there is more in secondary bootloader sbl1.mbn
aIecxs said:
I had a look but there are no fastboot commands in it. However "oem unlock" is mentioned, so the usual fastboot oem unlock should work.
Click to expand...
Click to collapse
trust me i have tried many many many many times and only got a
FAILED (remote: 'unknown command')
fastboot: error: Command failed
edit: the only place oem unlock is mentioned is a text that says oem unlock not allowed which might be default text by android or whatever but cat devs somehow messed it up somehow??
aIecxs said:
I had a look but there are no fastboot commands in it. However "oem unlock" is mentioned, so the usual fastboot oem unlock should work.
maybe there is more in secondary bootloader sbl1.mbn
Click to expand...
Click to collapse
just saw the edit i will check now
nope nothing related no oem unlock no fastboot no flashing no flash nothing is mentioned ill attach it if you want to look
oem unlock not allowed is standard text if one forgot to enable oem unlocking in developer options in android settings.
maybe flash this ROM maybe it is unlockable?
aIecxs said:
oem unlock not allowed is standard text if one forgot to enable oem unlocking in developer options in android settings.
maybe flash this ROM maybe it is unlockable?
Click to expand...
Click to collapse
from recovery using the flash firmware with adb option??
edit: i meant apply update from adb
edit2: what if i hard reset from recovery would that reset the firmware?
edl firmware cannot flashed from recovery. power off phone, press both volume keys and plug in usb-cable. check VID/PID from windows device manager. if you see device ID (05c6:9008) the phone is in EDL mode. you can now use EDL tool (post #2) and backup current ROM. then you can flash other ROM.
aIecxs said:
It's edl firmware cannot flashed from recovery
Click to expand...
Click to collapse
so what do i download that can be flashed from recovery