[Onetouch Idol 3 Android Development] Ricod11:
Hello. I have an Alcatel Idol 3 (4.7, 6039S) running Android MM (6.0) and I was following the method on here that would allow me to use fastboot commands with my upgraded device. I also have the latest Android Studio application installed on my computer with SDK Platform-tools usable in any command prompt (cmd). I followed all the steps correctly, excepted I used QPST 2.7 Build 425 Qfil.

This is what I did after getting the necessary items and what resulted:

I attached my phone, which was turned off, to my computer.

The battery symbol comes up and after the screen goes off, I press all three buttons (pwr + vol+ + vol-).

Then, while I'm at the red warning/"Download" screen, I press vol+ and open QFIL.

It detects my device and ports, but one thing that confused me at this point (until I believe I understood/guessed) was the "Build Type" radio buttons ("Flat Build" or "Meta Build", which the latter is selected by default), of which determined what options were available.

So, I selected the "Flat Build" one since the other one didn't allow me to use "Select Programmer."

I pressed the "Browse" button to get to the path of the files folder for my device (...\6039S\6039S).

After that, "Select Build" was automatically filled in.

Then, I pressed the "Load XML" button, which found rawprogram0.xml and patch0.xml.

Finally, I pressed the download button.

I waited for a bit, but nothing happened. I thought I was done (which I may have been) so I unplugged my phone and powered it back on.

When it got to the bootloader screen, where the "powered by Android" part is at the bottom of the screen, I notice that "Alcatel" was not written and two fat, white, fuzzy lines were across the screen.

Then, it went into the normal Alcatel loading screen and came to the Android desktop.

Then, I turned on USB debugger and plugged my phone in.

In cmd, I typed "adb reboot-bootloader" after checking and typing "adb devices."

The device rebooted but did not stay on the bootloader screen.

I double checked what I did and I tried to get into the "Download" mode again, but now I can't. Another thing is that when I am at the lockscreen after a reboot on my phone, it counts my correct password wrong one time and then I can enter it again and unlock my phone. However, whenever my phone locks after that and I try to unlock it, a blue screen fades in and the phone reboots. When I tried to change my password in settings and enter the correct password for confirmation, the "blue screen" occurs.

I was able to get into my device's stock recovery and wipe all data and cache. After doing this and setting up the phone again and reinstalling all app data, I find that I can't setup a screen lock. I think I setup the same one in the phone setup, but the screen lock setting shows that it is set to "Swipe." When I go to edit it, it asks for my password confirmation. When I type the same correct password, it thinks it is wrong. After a few types of this, at some point or step the "blue screen" occurs still. I have no idea what has happened with the bootloader and why screen lock is messed up. Any help is appreciated!

This is my log file from QFIL:

Validating Application Configuration
Load APP Configuration
COM:-1
SAHARA:True
SAHARA:C:\Users\Ricardo\Downloads\Drivers & Customization Tools\Android AIdol3 custom\6039S\6039S\prog_emmc_firehose_8916.mbn
SEARCHPATH:C:\Users\Ricardo\Downloads\Drivers & Customization Tools\Android AIdol3 custom\6039S\6039S
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
READBACKMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
Load ARG Configuration
Process Index:0
Validating Download Configuration
Image Search Path: C:\Users\Ricardo\Downloads\Drivers & Customization Tools\Android AIdol3 custom\6039S\6039S
RAWPROGRAM file path: C:\Users\Ricardo\Downloads\Drivers & Customization Tools\Android AIdol3 custom\6039S\6039S\rawprogram0.xml
PATCH file path:C:\Users\Ricardo\Downloads\Drivers & Customization Tools\Android AIdol3 custom\6039S\6039S\patch0.xml
Programmer Path:C:\Users\Ricardo\Downloads\Drivers & Customization Tools\Android AIdol3 custom\6039S\6039S\prog_emmc_firehose_8916.mbn
Image Search Path: C:\Users\Ricardo\Downloads\Drivers & Customization Tools\Android AIdol3 custom\6039S\6039S
RAWPROGRAM file path: C:\Users\Ricardo\Downloads\Drivers & Customization Tools\Android AIdol3 custom\6039S\6039S\rawprogram0.xml
PATCH file path:C:\Users\Ricardo\Downloads\Drivers & Customization Tools\Android AIdol3 custom\6039S\6039S\patch0.xml

P.S.

I am still new to rooting and adb even though I have looked on this site and rooted an old phone in the past.

EDIT/UPDATE:

Fastboot works now! I'm guessing that wiping the data and resetting the phone fixed the issue with getting into "Download" mode again as well as getting into "fastboot" mode. However, I typed adb reboot bootloader this time instead of adb reboot-bootloader in cmd, which I believe was why my phone did not go into or stay in fastboot mode. I still can not figure out the "blue screen" reboot issue with the screen lock password, though. I don't think that matters now if I flash a compatible custom recovery and install a compatible custom ROM now (?).