Develop Bugs

fastboot usb mode (device not found)

Ok I can use commands VIA fastboot when the phone is on. The problem is using commands when the phone is in bootloader. It says "fastboot usb" But when i am trying to use commands like :adb reboot" i get a " device not found " error
The device is Eng s off and ship s off
Tryed this with 3 computers with no luck
I have all the needed drivers.
And using commands in bootloader worked before.

you cannot use adb commads while in fastboot, not will your device show up with the "adb devices" command, you can only issue fastboot commands. so to reboot you must use the command "fastboot reboot" and to show your device you can use the command "fastboot devices"

AndroHero said:
you cannot use adb commads while in fastboot, not will your device show up with the "adb devices" command, you can only issue fastboot commands. so to reboot you must use the command "fastboot reboot" and to show your device you can use the command "fastboot devices"
Click to expand...
Click to collapse
K thnx .
One more thing
I have SU on (#) and i cant even use commands in terminal .. tried reboot command : not permited

primpower said:
K thnx .
One more thing
I have SU on (#) and i cant even use commands in terminal .. tried reboot command : not permited
Click to expand...
Click to collapse
are you using leedroid's rom? i had the same problem, when i used his rom, some of the permissions in /system/bin/ are wrong on his rom, they are rwsr-xr-x and they should be set to rwxr-xr-x, try using adb

AndroHero said:
are you using leedroid's rom? i had the same problem, when i used his rom, some of the permissions in /system/bin/ are wrong on his rom, they are rwsr-xr-x and they should be set to rwxr-xr-x, try using adb
Click to expand...
Click to collapse
I was using Leedroid, i f**** up and installed multiple .zip at once.... first "leedroidRom.zip" and then "theme" without rebooting between.
After that it stopped working ( I think )
I then wiped everything and installed Android Revolution 2.0.12..
"Terminal"
# Reboot
not permited!
About the question i asked earlier. So its not possible to use adb commands trough fastboot. only fastboot commands.
so i have to use : "fastboot flash" and "fastboot push" to execute commands ?

you cannot use the push command while in fastboot for the same reason you cannot use ADB commands, because at that moment android is not booted, you can use adb commands from recovery though
here are the fastboot commands i know of:
fastboot devices - fastboot devices will give you a list of devices connected to the computer. This is also a good way to make sure that your phone is actually connected to the computer.
fastboot reboot - this will reboot your phone normally
fastboot oem unlock - Dont think this works with the DHD
fastboot erase XXX - Will erase the partition XXX (such as userdata, cache) - mainly used for resetting phone and clearing userdata / factory settings.
fastboot flash XXX YYY - This will flash XXX partitionn with YYY image

[SOLVED]fastboot with linux: Arc device not detected

Hello,
I wanted to update one SE Arc Experia already running cm7, but with a few months old Rom.
fastboot is not detecting my device, and I have no ideas why. After a few hours of search, I am still unable to fastboot it.
Arc is running fine with cm7.2.0 with FXP Kernel, debug is ON.
I am on Ubuntu 11.10, and everything is correctly set up. I already flashed Rom & Kernel in the past. The file 51-android.rules is in /etc/udev/rules.d.
Code:
#SE Arc Xperia
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”0fce″, ATTRS{idProduct}==”014f″, OWNER:="gabx", GROUP:="plugdev", MODE=”0666″
the usb is working :
Code:
[email protected]:~/Xperia/xperia$ lsusb
Bus 001 Device 005: ID 0fce:0dde Sony Ericsson Mobile Communications AB
fastboot executable is in my box, with correct permission. The fastboot command works.
The phone is correctly in download mode, with the blue led (turn off, press menu, plug USB).
When I fastboot devices, I have no entry :
Code:
[email protected]:~/Xperia/xperia$ fastboot devices
[email protected]:~/Xperia/xperia$
Weird, the -i 0x0fce option doesn't seems correct:
Code:
[email protected]:~/Xperia/xperia$ fastboot -i 0x0fce devices
usage: fastboot [ <option> ] <command>
.../.... list here of all otions and command
Sudoing doesn't change anything.
Code:
[email protected]:~/Xperia/xperia$ fastboot reboot
< waiting for device >
The device is not detected. Why ??
TY for any help
EDIT
As I couldn't fastboot my device, I placed the boot.img from cm7 update on my sdcard. then from terminal emulator on my device:
Code:
flash_image boot /sdcard/boot.img
Then reboot in recovery, but now black screen, can't boot at all!!

gabx said:
The device is not detected. Why ??
TY for any help
Click to expand...
Click to collapse
Funny how I lost a whole day investigating the same issue Answer: invalid fastboot binary. Use this one
gabx said:
As I couldn't fastboot my device, I placed the boot.img from cm7 update on my sdcard. then from terminal emulator on my device:
Code:
flash_image boot /sdcard/boot.img
Then reboot in recovery, but now black screen, can't boot at all!!
Click to expand...
Click to collapse
Don't use flash_image, it doesn't work with Xperias
Cheers,
z

zdzihu said:
Funny how I lost a whole day investigating the same issue Answer: invalid fastboot binary. Use this one
Don't use flash_image, it doesn't work with Xperias
Cheers,
z
Click to expand...
Click to collapse
TY so much. Yes, a lot of wasting time, checking everything on my Linux box!! Your answer is nice to me, as I was doubting about my Linux set up, and now I feel safe.
I managed to settle everything today on a Winodows box, in just 15 mn! Fastbooted boot.img, flashed update from sdcard, et hop!
TY for the binary. I will use it next time on my Linux box.

fastboot -i 0x0fce devices
Click to expand...
Click to collapse
shouldnt it be
Code:
fastboot -i 0xfce devices
instead?

try running
Code:
fastboot -i 0x0fce
.
You might also require running it as root. At least that's what i'm forced to do everytime, i guess it has sth to do with the udev entry but not sure what.
Also running as root means i'm not able to use tools like FlashTool, but if you just need fastboot, it will probably work.
Cheers,
G

g el said:
try running
Code:
fastboot -i 0x0fce
.
You might also require running it as root. At least that's what i'm forced to do everytime, i guess it has sth to do with the udev entry but not sure what.
Also running as root means i'm not able to use tools like FlashTool, but if you just need fastboot, it will probably work.
Cheers,
G
Click to expand...
Click to collapse
You need to add the udev rule mentioned in OP and it will work for regular users too.
Code:
#SE Arc Xperia
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”0fce″, ATTRS{idProduct}==”014f″, OWNER:="yourusernamehere", GROUP:="plugdev", MODE=”0666″
Also, I don't use 'fastboot -i 0x0fce' (just fastboot <command>) and it still works fine
Cheers,
z

zdzihu said:
You need to add the udev rule mentioned in OP and it will work for regular users too.
Code:
#SE Arc Xperia
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”0fce″, ATTRS{idProduct}==”014f″, OWNER:="yourusernamehere", GROUP:="plugdev", MODE=”0666″
Also, I don't use 'fastboot -i 0x0fce' (just fastboot <command>) and it still works fine
Cheers,
z
Click to expand...
Click to collapse
Agree totally, no need sudoing, neither use option. As previoulsy mentioned, a wrong binary was the only culprit. Usually, fastboot is trivial in Linux, with the only condition being the correct android rules in /etc/udev.

[Q] Bricked Kindle Fire not recognized by either ADB or Windows

Hey guys, I'm a new member to XDA but I've been browsing on it for a while. I figured you guys could help. I rooted my Kindle Fire a couple months ago and had Clockwork Recovery(TWRP is better). I decided I didn't want it rooted so I restored the Kindle thinking it would remove the root, it actually bricked it. Now all that comes up is the Kindle Fire boot screen with the android bot over top of it, it doesn't glimmer or flash, that's all. It isn't recognized by ADB or Windows(and Device Manager). I haven't found a thread exactly like mine so I figured I'd post one. Please help guys, I miss Minecraft PE and Netflix!

Assuming you know how to access recovery...
Download the latest version of FireFireFire and either "adb push" it to your sdcard or use the mount function in recovery and transfer it.
FireFireFire 1.4 can be found here. It comes in a .zip file for flashing in recovery. DO NOT install the .zip file with the "fastboot flash bootloader" command or you will brick your device.
When installed reboot and use your power button at the kindle fire screen as if you were trying to enter recovery. At some point some options will show up on the bottom. Use the power button to select "Normal Boot".

@soupmagnet
what do you mean by ADB Push? Recovery as in turning the kindle on and then holding the power button again until it turns orange?

mrpike9416 said:
@soupmagnet
what do you mean by ADB Push?
Click to expand...
Click to collapse
Actually, it would be easier to explain how to mount your sdcard.
Recovery as in turning the kindle on and then holding the power button again until it turns orange?
Click to expand...
Click to collapse
Yes. While in recovery, there will be a mount to USB function that will mount the sdcard partition to your computer as if it were an external drive, such as a USB thumb drive.

Good thing I know that, however, I can't access recovery..
I think I might've reformatted the system folder while in recovery..

mrpike9416 said:
Good thing I know that, however, I can't access recovery..
I think I might've reformatted the system folder while in recovery..
Click to expand...
Click to collapse
Recovery is in a separate partition from the system files and cannot be formatted while in recovery. I'm not sure why you wouldn't be able access recovery so you'll probably need to reinstall it.
How comfortable are you with using command prompt?

A little experienced, how hard can entering commands be?

mrpike9416 said:
A little experienced, how hard can entering commands be?
Click to expand...
Click to collapse
OMG Don't EVER say that.
Do you have adb and fastboot on your computer? If yes...Is it from AndroidSDK or KFU?

Hahahahha my mistake.
I do have ADB but I don't think I have fastboot(I probably do).

I do have fastboot.

mrpike9416 said:
I do have fastboot.
Click to expand...
Click to collapse
Okay, make sure the you have TWRP version 2.1 and place it in the same folder as fastboot. It would be wise to rename it to something manageable like "twrp.img"
In your command prompt, enter:
fastboot flash recovery twrp.img
Note: version 2.0 will not work with this command
And while you're at it:
fastboot oem idme bootmode 4000
fastboot reboot
[Edit:] That will likely fix your problem (barring driver issues) but you should still install FFF1.4

I just tried a different cable and the computer recognizes my kindle in device manager as Android ADB Interface... the twrp 2.1 cmd thing you told me to do was a no go but I assume we have more options now now that device manager recognizes it?
(EDIT)
It is now recognized on device manager as "Unknown Device" and no longer as Android ADB Interface..

1. What happens when you enter:
Code:
fastboot devices
2. What error message, if any, did you receive when entering the "twrp 2.1 cmd thing"?

"fastboot" is not recognized as an internal or external command, operable program or batch file.
That happened for both instances.

mrpike9416 said:
"fastboot" is not recognized as an internal or external command, operable program or batch file.
That happened for both instances.
Click to expand...
Click to collapse
Do you have fastboot and what folder is it in?

Yeah its an .exe file i believe... under the "Files and Tools" folder when I downloaded ADB from Android SDK.

Better yet...fastboot and adb are programs with a certain set of commands associated with them. Those commands only work with each individual program. In order to issue a certain command that isn't associated with "shell" or "DOS" you have to include an "identifier" so the computer knows from which program to run the commands. In this case it is "fastboot" because you are using the fastboot program. In order issue commands this way, the program you are using must either be listed in your "PATH" or be in the directory from which you are issuing the commands.
The easiest way to do this in Windows is to shift+right click on the folder containing the program and select "Run in Command". The command window that opens is were you will be entering your commands.

error: cannot load "twrp.img"
I typed "fastboot devices!" (out of frustration I must admit).
This is what came up:
C:\Users\Nick\Documents\KindleRoot\tools>fastboot devices!
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048

Turn your device off then enter the command. When it says "waiting for device" turn it back on.
Fastboot commands only work in fastboot mode. If you have a modified bootloader installed, the first few seconds of the boot process is a temporary fastboot mode which will accept fastboot commands.
If it just hangs at "waiting for device", you need to fix your drivers.

soupmagnet said:
Turn your device off then enter the command. When it says "waiting for device" turn it back on.
Fastboot commands only work in fastboot mode. If you have a modified bootloader installed, the first few seconds of the boot process is a temporary fastboot mode which will accept fastboot commands.
If it just hangs at "waiting for device", you need to fix your drivers.
Click to expand...
Click to collapse
what command am I entering?

Able to access bootloader?

This is just a quick poll to find out how many G3 owners can access their bootloaders.
Terminal:
Code:
su
reboot-bootloader
ADB (windows):
Code:
adb reboot-bootloader
ADB (Linux):
Code:
./adb reboot-bootloader

I cannot it seems.

Cheers, glad to know it's not just me. Anyone else?

[email protected] :/ reboot-bootloader
tmp-mksh: reboot-bootloader : not found
127|[email protected] :/
D855 32gb

sabret00the said:
This is just a quick poll to find out how many G3 owners can access their bootloaders.
Terminal:
Code:
su
reboot-bootloader
ADB (windows):
Code:
adb reboot-bootloader
ADB (Linux):
Code:
./adb reboot-bootloader
Click to expand...
Click to collapse
Should be:
From device
Code:
su; reboot bootloader
PC
Code:
adb reboot-bootloader
There is no reboot-bootloader binary so your probably getting an error "reboot-bootloader does not exist" or something similar. reboot is the binary and bootloader is one of its commands.

wedgess said:
Should be:
From device
Code:
su; reboot bootloader
PC
Code:
adb reboot bootloader
There is no reboot-bootloader binary so your probably getting an error "reboot-bootloader does not exist" or something similar. reboot is the binary and bootloader is one of its commands.
Click to expand...
Click to collapse
still doesn't work. Though though typing just ADB does suggest the hyphenated version.

sabret00the said:
still doesn't work. Though though typing just ADB does suggest the hyphenated version.
Click to expand...
Click to collapse
I don't actually have the device just though I could lend a helping hand when I saw the command were wrong from adb, adb reboot-bootloader.works but on a device it doesn't. it uses the reboot binary.

wedgess said:
Is your bootloader unlocked? If you don't have the reboot binary inside /system/bin or /system/xbin then it ain't going to work. What is the shell throwing at you when you do reboot bootloader?
I don't actually have the device just though I could lend a helping hand when I saw the command were wrong from adb, adb reboot-bootloader.works but on a device it doesn't. it uses the reboot binary.
Click to expand...
Click to collapse
I just tried it from terminal and the phone just reboots, sadly not into bootloader.

wedgess said:
Hmm, is your bootloader unlocked? And can you attach the last_kmsg please.
Click to expand...
Click to collapse
Pass, tell me how to find out and I will tell you. Also where do I find the last_kmsg, my ageing brain can't remember where to find it

Bootloader is locked. Its accessible by flashing a bad boot.img. it will then take you into fastboot mode which oem unlock does nothing.

p70shooter said:
Pass, tell me how to find out and I will tell you. Also where do I find the last_kmsg, my ageing brain can't remember where to find it
Click to expand...
Click to collapse
it is in >proc>last_ksmg
also here is mine the phone reboots but not into booloader,but this is because i installed drivers from here
for the people reading my last_kmsg I tried the adb reboot-bootloader command a couple of times and just for fun I tried adb reboot oem-unlock once
last_kmsg
papi92 said:
Bootloader is locked. Its accessible by flashing a bad boot.img. it will then take you into fastboot mode which oem unlock does nothing.
Click to expand...
Click to collapse
kernel sources are up so now wwe play the waiting game I guess

Install rom toolbox or similar and choose reboot bootloader from it and see what happens
Sent from my SM-N900P using Xparent BlueTapatalk 2

Epix4G said:
Install rom toolbox or similar and choose reboot bootloader from it and see what happens
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
nop it just reboots the phone:crying:

[6039] Custom Recovery - TWRP - 2.8.7.0

Hello guys/girls,
I have built successfully a TWRP 2.8.7.0 recovery for Alcatel Idol 3 6039 4.7 inch (tested on 6039y). The recovery image can be downloaded from here:
Edit (30.09.2015): I think this will be the final version of the recovery. The date/time issue is fixed now and additionally small adjustments to the initialization process have been added.
twrp_recovery-2.8.7.0-idol347.img
md5sum: 175be787d67839d15beab7285279a72c
Please note that the latest OTA updates from the end of August and the start of September disable the fastboot commands which means that this recovery cannot be started as described below (if your device is already upgraded)!!! The device will return FAILED (remote: unknown command) when you try to boot the recovery.
If you find yourself in this situation but want root access please see this thread.
It can be tested as follows:
- enable the developer options
- allow the USB debugging
- reboot to bootloader:
Code:
adb reboot-bootloader
- start the recovery image with:
Code:
fastboot -i 0x1bbb boot twrp_recovery-2.8.7.0-idol3-6039y.img
Please do not forget first to make a backup of the system partition by selecting System Image from the Backup settings. The backup image will be needed in order to install future OTA updates if available, so please keep it in a safe place.

petrov.0 said:
Hello guys/girls,
I have built successfully a TWRP 2.8.7.0 recovery for Alcatel Idol 3 6039 4.7 inch (tested on 6039y). The recovery image can be downloaded from here:
twrp-2.8.7.0-idol3-6039y.img
It can be tested as follows:
- enable the developer options
- allow the USB debugging
- reboot to bootloader:
Code:
adb reboot-bootloader
- start the recovery image with:
Code:
fastboot -i 0x1bbb boot twrp_recovery-2.8.7.0-idol3-6039y.img
Please do not forget first to make a backup of the system partition by selecting System Image from the Backup settings. The backup image will be needed in order to install future OTA updates if available, so please keep it in a safe place.
Click to expand...
Click to collapse
Great job! A couple of the outstanding issues on the 6045 TWRP are that the date/time stamp of the backup is screwy because of a known bug with 64 bit chips and also the recovery identifies every model as a Y model (you can see in recovery.log) because the boot.img for a Y was used. Yours may also encounter one or both of these issues. I suggested in the other thread they consider building for each model using the individual boot.img but didn't get a reply.

famewolf said:
Great job! A couple of the outstanding issues on the 6045 TWRP are that the date/time stamp of the backup is screwy because of a known bug with 64 bit chips and also the recovery identifies every model as a Y model (you can see in recovery.log) because the boot.img for a Y was used. Yours may also encounter one or both of these issues. I suggested in the other thread they consider building for each model using the individual boot.img but didn't get a reply.
Click to expand...
Click to collapse
Yes, the date/time stamp is wrong. The device model however is not much . The ro.product.model is shown as idol347. It is a custom build after all.

I tried to use TWRP on my 6039Y and it's not working. Well to be more precise I don't know if your custom recovery works or not because I can't seem to get past the first step. Here's what happened
Code:
adb reboot-bootloader
So the device reboots, but doesn't get past the first screen (Alcatel OneTouch Powered by Android) even after a minute or so. Should I let it more time or is this the bootloader?
Then i try this
Code:
fastboot -i 0x1bbb devices
This seems to have no effect, the command seems to execute without any consequence and I'm able to type a new line in cmd
And if I try
Code:
fastboot -i 0x1bbb boot twrp_recovery-2.8.7.0-idol3-6039y.img
I get a <waiting for device> and I'm stuck on that line, having to Ctrl+C to stop the command and reboot the phone by holding power
Yes I know, I'm on Windows and it might be the drivers causing this. However I have installed the ADB drivers through SDK just fine. I would like to be able to install the drivers from the phone but the only options I see in the USB connection settings are MTP, PTP and Charging only. Any idea on how to get that CD-Rom option to appear?
Thanks for your help in advance

Rorshan said:
I tried to use TWRP on my 6039Y and it's not working. Well to be more precise I don't know if your custom recovery works or not because I can't seem to get past the first step. Here's what happened
Code:
adb reboot-bootloader
So the device reboots, but doesn't get past the first screen (Alcatel OneTouch Powered by Android) even after a minute or so. Should I let it more time or is this the bootloader?
Click to expand...
Click to collapse
This is OK it's in the bootloader.
Rorshan said:
Code:
fastboot -i 0x1bbb devices
This seems to have no effect, the command seems to execute without any consequence and I'm able to type a new line in cmd
And if I try
Code:
fastboot -i 0x1bbb boot twrp_recovery-2.8.7.0-idol3-6039y.img
I get a <waiting for device> and I'm stuck on that line, having to Ctrl+C to stop the command and reboot the phone by holding power
Click to expand...
Click to collapse
Looks like a driver issue. I use Linux no problems here no need of drivers too.
Rorshan said:
Yes I know, I'm on Windows and it might be the drivers causing this. However I have installed the ADB drivers through SDK just fine. I would like to be able to install the drivers from the phone but the only options I see in the USB connection settings are MTP, PTP and Charging only. Any idea on how to get that CD-Rom option to appear?
Thanks for your help in advance
Click to expand...
Click to collapse
Try with the drivers posted by @famewolf here or with these.
Meanwhile the first post has been updated with a new link. Please download the recovery again. There was a bug with the screenlock in the previous build. The screenlock is disabled in this one.

Alright I'll make sure to try that. Otherwise I guess I'll just try with Linux or Mac. Thanks
Sent from my 6039Y using Tapatalk

Rorshan said:
Alright I'll make sure to try that. Otherwise I guess I'll just try with Linux or Mac. Thanks
Sent from my 6039Y using Tapatalk
Click to expand...
Click to collapse
A quick check of the dirvers shared by @famewolf shows that they should work on windows with 6039y (at least to start the recovery). These are the vendor and the product IDs of 6039y from one of the INF files in the archive so the drivers should be compatible with the device when is in the bootloader (they match with those reported by the device).
Code:
USB\VID_1BBB&PID_D00D.DeviceDescRelease="Android Sooner Single ADB Interface"
I don't see however the IDs for the recovery mode:
Code:
[726530.487224] usb 1-4: New USB device found, idVendor=18d1, idProduct=4ee2
and the IDs from when the phone is connected as MTP device:
Code:
[726695.431624] usb 1-4: New USB device found, idVendor=1bbb, idProduct=af2b
but I hope everything to be OK. Good luck.

Why is this thread in Mi Note pro development section ? It's about idol 3 6039....

frankee207 said:
Why is this thread in Mi Note pro development section ? It's about idol 3 6039....
Click to expand...
Click to collapse
I asked the moderator to move it to the development section of Idol 3, but something went wrong. The moderator is informed about this. Now I'm waiting to be moved to the Idol 3 forum again.

petrov.0 said:
I asked the moderator to move it to the development section of Idol 3, but something went wrong. The moderator is informed about this. Now I'm waiting to be moved to the Idol 3 forum again.
Click to expand...
Click to collapse
Yeah I was thinking that's a bit strange! Got me excited thinking theres newer TWRP for Mi Note Pro xD

Cyanogen recovery
Here is a download link of the cyanogen recovery (built from the 12.1 branch). It's useless. But if someone wants to try it. The md5sum of the image is 3ff21bbf5ece48422f3135fa583eaa78

Should this work on 6039J?

Has not been tested on 6039J until now, but you can try it. Don't rush with backups wipes etc. (because the partition table can be different) just boot with it through fastboot. You can examine your partitions with the recovery from the repartitioning guide which contains gdisk (if your phone is not rooted yet). But this is only if this one works with your device. By the way what is the J version ? Dual sim ?

I'm trying to create a backup of the 6039S (North American 16GB, 1-SIM/1-SD model), and am having some issues with fastboot.
ADB is working flawlessly, and I can boot into the bootloader. As petrov.0 noted earlier in this thread there is no dedicated bootloader screen, just the onetouch splashscreen displays.
I can enter:
Code:
fastboot -i 0x1bbb devices
and the device shows up: "6346ce6d fastboot".
However, when I go to run any of the OEM commands, e.g.
Code:
fastboot -i 0x1bbb oem device-info
it shows:
...
FAILED (remote: unknown command)
finished. total time: 0.016s
Any ideas? By all appearances the alcatel driver seems to be working, but could this still be a driver issue?

Bradlee22 said:
I'm trying to create a backup of the 6039S (North American 16GB, 1-SIM/1-SD model), and am having some issues with fastboot.
ADB is working flawlessly, and I can boot into the bootloader. As petrov.0 noted earlier in this thread there is no dedicated bootloader screen, just the onetouch splashscreen displays.
I can enter:
Code:
fastboot -i 0x1bbb devices
and the device shows up: "6346ce6d fastboot".
However, when I go to run any of the OEM commands, e.g.
Code:
fastboot -i 0x1bbb oem device-info
it shows:
...
FAILED (remote: unknown command)
finished. total time: 0.016s
Any ideas? By all appearances the alcatel driver seems to be working, but could this still be a driver issue?
Click to expand...
Click to collapse
Probably this problem is not related to the driver. Something is different in your device. By the way can you boot this recovery ?

petrov.0 said:
Probably this problem is not related to the driver. Something is different in your device. By the way can you boot this recovery ?
Click to expand...
Click to collapse
No, I can't boot this TWRP recovery either. I get the same error message: FAILED (remote: unknown command).

I must admit that the internal sd card has not been mounted properly until now. I found the proper way however how to do it. The first post has been updated and now contains a link to the recovery which includes the corrections. The configuration files with which I do these recoveries, are also publicly available now and can be found here. Nothing special but ...

Bradlee22 said:
No, I can't boot this TWRP recovery either. I get the same error message: FAILED (remote: unknown command).
Click to expand...
Click to collapse
Any output from
Code:
fastboot -i 0x1bbb getvar secure
fastboot -i 0x1bbb getvar version-bootloader
fastboot -i 0x1bbb getvar all

petrov.0 said:
Any output from
Code:
fastboot -i 0x1bbb getvar secure
fastboot -i 0x1bbb getvar version-bootloader
fastboot -i 0x1bbb getvar all
Click to expand...
Click to collapse
Nothing useful from any of those.
Code:
fastboot -i 0x1bbb getvar secure
Output is:
secure:
finished. total time: 0.016s
Code:
fastboot -i 0x1bbb getvar version-bootloader
Output is:
version-bootloader:
finished. total time: -0.000s
Code:
fastboot -i 0x1bbb getvar all
Output is:
all:
finished. total time -0.000s
P.S. Thanks for your help. It's much appreciated!

Bradlee22 said:
Nothing useful from any of those.
Click to expand...
Click to collapse
remote: unknown command is a protocol error, as long as I understand the source. What is the host OS ? Windows ... which version ... did you try to start cmd.exe as administrator ? Which drivers you use ? On what port is your device connected (USB 2 or USB 3). Do you have access to a Linux box ? If you have try from there. I'm not sure how Windows handles the sharing of the USB ports with a virtual machine. You can try to start a distro in VirtualBox, which have option to expose a device connected on the host to the guest system and then to try fastboot from there.