Fastboot unknown command

Hmm, @Odin89, a quick Google search reinforces what you're saying for some other Alcatel devices, too...

So, fastboot devices by itself doesn't return anything but fastboot -i 0x1bbb devices does work?

How about fastboot -i 0x1bbb getvar all ?

It is possible that the bootloader won't respond to any useful commands--some devices just don't (blame the manufacturer for that ).

Also, are you using a USB 3.0 port? If so, try a USB 2.0 port and possibly another/different USB cable just to rule-out some other possible causes.

That's all I got at the moment...

 

Yeah, the bootloader might be locked-down and the lack of response from the fastboot commands may indeed indicate that your bootloader is locked. There's precious little information out there from what I can find in a Google search, so that may not necessarily be true, though dunno: ).

I did find this interesting chain of pages:

http://www.smartphonezero.com/alcatel-one-touch-conquest-7046t-specs/​

that says that your device has a Qualcomm Snapdragon 410 MSM8916 processor.

A search of "Qualcomm Snapdragon 410 MSM8916 bootloader" provides this PDF document:

https://developer.qualcomm.com/qfile/28821/lm80-p0436-1_little_kernel_boot_loader_overview.pdf​

and that document reveals a few other fastboot commands that might be fruitful for you (all cautions apply, though--be careful about what you choose to try ), but the "oemdevice-info" option does look like it might be helpful.

 

Unfortunately, you'll likely be unable to change the bootloader to enable those extra command since the bootloader is developed (compiled and burned into a chip on your phone) and locked by the manufacturer and not changeable by folks like us .

I was just hoping that some of the commands shown in there might be helpful and/or revealing to you.

 

did you find solution i am noob and facing same issue on my mobile

 

Does your mobile allow the use of fastboot commands? I know some manufacturers block fastboot access.

 

Well, on the surface, as I indicated in my PM reply, without further information--same question would likely lead to the same replies. Please post that additional information here for all to see .

Also, as EP alluded to, some manufacturers will also block certain fastboot commands, notable the unlock feature if that's what you're trying to do / getting at...

 

i am able to boot in fastboot, mobile detected as fastboot devices retured serial no . and also fastboot getvar-all returned, but rest command like boot, reboot,unlock all failed remote unknown command
@scary alien what additional information u need please tell i will try to proivide
i have attached schreenshot

 

Can't see your attachment as it's an MS/Word document...can you re-post as an image (.png, jpg, .gif, etc.), please?

That may not matter if it matches what you said above...many bootloaders are simply "locked" because the device-side that fastboot "talks to" simply will not implement or ignores things like the unlock commands, or disabling the key/button sequence to enter bootloader mode or flat-out disabling the USB driver when in bootloader mode. I.e., several ways to lock you out.

From https://www.codeaurora.org/blogs/little-kernel-based-android-bootloader:

Q2) How do I disable 'fastboot' for my commercial device?

A2) Personally, I would like to see commercial devices leave 'fastboot' enabled. It goes in the spirit of Android Open Source Project where end users and developers have access to the source code to allow them to modify it and upgrade their device over usb using 'fastboot'. However, if OEMs or network providers want to lock down 'fastboot' it can be done by disabling the keypad and usb driver in bootloader. This can be customized in the following files:

lk/app/aboot/fastboot.c

lk/app/aboot/aboot.c​

If fastboot otherwise works (i.e., fastboot devices and fastboot getvar all), then any error you get after that indicates a command sequences that's incorrect or not implemented.

There is one last/other thing to consider, on many devices--especially Nexus devices--there is a Settings -> Developer options -> OEM unlocking switch that must be enabled before you're allowed to unlock your bootloader. I'm not sure that's relevant in your case, but it certainly wouldn't hurt to check.

 

please find the attached file of response of my fastboot command if you need any thing else, then say i will try to get this
i dont where the fastboot.c ane aboot.c file is located in my firmware so elobrate more because i am noob in this, also the firmware in.cpb format which i already extracted but not found any file like u mentioned .
please check my file and reply , thx

 

yes my mobile coolpad note 5 has option oem unlocking option on developer setting , which i already enabled before trying above

 

It looks like your bootloader is locked (note the "secure:yes" line from the getvar all output) and/or the fact that the commands to unlock / flash / boot all report "FAILED (remote: unknown command)".

Some devices simply do not allow unlocking the bootloader--not sure what else to tell you or to have you try...

Sorry .

 

you replied about editing the files aboot.c will this work so how i do this plese tell about this

 

Not sure what you mean...I never posted anything about editing aboot.c--I posted a link that discussed/included information about methods for how some vendors / manufacturers might lock down their bootloaders.

 

well ok one more question i have complied twrp for this , but stuck because cant flash it , ygdp tool flash .cpb of it. and i am unable to replace stock recovery with custom on it , because the version supported is directly flashing it without decompressing so can you help on it

 

Sorry, but I'm not at all familiar with .cpb files or the ygdp flash tool.

 

ok i did it flashed recovery

 

hari pashad
look like we on same track on same train with same issue.
i have also one of the phone of cool pad and faced same problem while try to do same command <fastboot boot twrp.img> as seen in pic so at last how did u flashed recovery? and did these command working for u <fastboot boot twrp.img>??

 

Good grief.. has a problem a lot of people are facing, incessantly asks for help, then suddenly just says "Ok I did it" and never returns to explain how.

Thanks a lot mate.

 

Agree with you Parishna. Whatever we figured out we should share.