HOW TO UNLOCK alcatel one touch fierce xl

[rajan nishchal]

HOW TO UNLOCK alcatel one touch fierce xl
5054N

[.:hack3r2k:.]

Root the phone, enable diag, unlock via diagnostic port

Br

[mastersolid]

Originally Posted by .:hack3r2k:.

Root the phone, enable diag, unlock via diagnostic port

Br

kingroot apk work last version
enable diag work
unlock no work in alcatel fierce xl (5054N)

log

Software engine version: 1.0.0.9827
Searching phone ...

MODEL : QCOM SERIES 48
COMPILED DATE : Oct 4 2015 16:51:00
RELEASE DATE : Sep 30 2015 08:00:00
FIRMWARE INFO : MPSS.JO.1.0.c5.2-00018-M8909EAAAANVZM-1
IMEI : 01445100xxxxxx-x
BLUETOOTH ADDR : 00 00 00 00 00 00

DONE;
Error ...
Error ... !

Log file saved to: LOG_18_01_2016_17_01_43.txt

Time needed - 00:00:24

[.:hack3r2k:.]

Originally Posted by mastersolid

kingroot apk work last version
enable diag work
unlock no work in alcatel fierce xl (5054N)

log

Then try the firehorse mode. Is still doesn't work contact me over skype pls

Br

[unlockphones]

I just got some fierce XL, but the 5054W. T-Mobile version. I'm stuck with the adb drivers for that model.

[unlockphones]

update: Got the adb driver to work by forcing it from the OT993 driver from support. Still no luck getting a comm port. Kingo root failed to root it as well.
Any ideas more than welcome. I see too little to no info out there about this model.

[unlockphones]

update 2: Also forced the com port driver into the phone and worked fine. Tried qcomm smart tool, firehorse mode (vol up & down) and it recognized the phone but didn't worked either. Here is the log:
Connect the phone powered off with both volume down and up pressed;
Phone detected (@oem123.inf,%qcomdevice90080%;RELINK HS-USB QDLoader 9008)
Preparing to start flash mode;
Preparing to open COM75
Connecting;
Loading;
Init;
Port opened;
ERROR: Boot loading failed;

Log file saved to: LOG_26_01_2016_22_09_01.txt

Time needed - 00:00:14

[.:hack3r2k:.]

Originally Posted by unlockphones

update 2: Also forced the com port driver into the phone and worked fine. Tried qcomm smart tool, firehorse mode (vol up & down) and it recognized the phone but didn't worked either. Here is the log:
Connect the phone powered off with both volume down and up pressed;
Phone detected (@oem123.inf,%qcomdevice90080%;RELINK HS-USB QDLoader 9008)
Preparing to start flash mode;
Preparing to open COM75
Connecting;
Loading;
Init;
Port opened;
ERROR: Boot loading failed;

Log file saved to: LOG_26_01_2016_22_09_01.txt

Time needed - 00:00:14

You have the wrong drivers installed ! RELINK HS-USB QDLoader 9008. Must use the alcatel ones !

Br

[BillA]

Failed even with Alcatel drivers, but at least it shows "Hello Received;"


Connect the phone powered off with both volume down and up pressed or connect the phone powered off and leave it connected to the usb till it shows the battery/charging screen ;
Phone detected (@oem573.inf,%qcomdevice90080%;ALCATEL HS-USB QDLoader 9008)
Preparing to start flash mode;
Preparing to open COM3
Connecting;
Loading;
Init;
Port opened;
Hello Received;
ERROR: Boot loading failed;

Log file saved to: LOG_28_01_2016_04_16_20.txt

Time needed - 00:00:02

[unlockphones]

Originally Posted by .:hack3r2k:.

You have the wrong drivers installed ! RELINK HS-USB QDLoader 9008. Must use the alcatel ones !

Br

Tried with right driver, same answer:
Connect the phone powered off with both volume down and up pressed;
Phone detected (@oem120.inf,%qcomdevice90080%;ALCATEL HS-USB QDLoader 9008)
Preparing to start flash mode;
Preparing to open COM75
Connecting;
Loading;
Init;
Port opened;
ERROR: Boot loading failed;

Log file saved to: LOG_28_01_2016_12_20_58.txt

Time needed - 00:00:14

This time the phone is even rooted. I checked trough cmd and it gained superused status and everything. Some help here would be greately appreciated. Remember my model is the 5054W from T-Mobile

[.:hack3r2k:.]

Originally Posted by unlockphones

Tried with right driver, same answer:
Connect the phone powered off with both volume down and up pressed;
Phone detected (@oem120.inf,%qcomdevice90080%;ALCATEL HS-USB QDLoader 9008)
Preparing to start flash mode;
Preparing to open COM75
Connecting;
Loading;
Init;
Port opened;
ERROR: Boot loading failed;

Log file saved to: LOG_28_01_2016_12_20_58.txt

Time needed - 00:00:14

This time the phone is even rooted. I checked trough cmd and it gained superused status and everything. Some help here would be greately appreciated. Remember my model is the 5054W from T-Mobile

Hi,

Can arrange such model to be sent yo us ? We will pay it

Br

[papsnew]

TCL 5054N Metro-Pcs (Fierce XL) Device Locked.
Normal mode..Diag Mode..Rooted
Software engine version: 1.0.0.9830
Searching phone ...

MODEL : QCOM SERIES 48
COMPILED DATE : Oct 4 2015 16:51:00
RELEASE DATE : Sep 30 2015 08:00:00
FIRMWARE INFO : MPSS.JO.1.0.c5.2-00018-M8909EAAAANVZM-1
IMEI : 0144xxxxxxxxxxxx
BLUETOOTH ADDR : 00 00 00 00 00 00

DONE;
Error ...
Error ... !

Log file saved to: LOG_14_02_2016_15_16_26.txt

Time needed - 00:00:24

Firehorse Mode
Connect the phone powered off with both volume down and up pressed or connect the phone powered off and leave it connected to the usb till it shows the battery/charging screen ;
Phone detected (@usb.inf,%usb\composite.devicedesc%;USB Composite Device)
Preparing to enter download mode;
Preparing to open COM169
Connecting;
Init;
Port opened;
Phone detected (@oem197.inf,%qcomserialportdesc90080%;Android HS-USB QDLoader 9008)
Preparing to start flash mode;
Preparing to open COM71
Connecting;
Loading;
Init;
Port opened;
Hello Received;
ERROR: Boot loading failed;

Log file saved to: LOG_14_02_2016_15_19_26.txt

Time needed - 00:00:29

[.:hack3r2k:.]

Originally Posted by papsnew

TCL 5054N Metro-Pcs (Fierce XL) Device Locked.
Normal mode..Diag Mode..Rooted
Software engine version: 1.0.0.9830
Searching phone ...

MODEL : QCOM SERIES 48
COMPILED DATE : Oct 4 2015 16:51:00
RELEASE DATE : Sep 30 2015 08:00:00
FIRMWARE INFO : MPSS.JO.1.0.c5.2-00018-M8909EAAAANVZM-1
IMEI : 0144xxxxxxxxxxxx
BLUETOOTH ADDR : 00 00 00 00 00 00

DONE;
Error ...
Error ... !

Log file saved to: LOG_14_02_2016_15_16_26.txt

Time needed - 00:00:24

Firehorse Mode
Connect the phone powered off with both volume down and up pressed or connect the phone powered off and leave it connected to the usb till it shows the battery/charging screen ;
Phone detected (@usb.inf,%usb\composite.devicedesc%;USB Composite Device)
Preparing to enter download mode;
Preparing to open COM169
Connecting;
Init;
Port opened;
Phone detected (@oem197.inf,%qcomserialportdesc90080%;Android HS-USB QDLoader 9008)
Preparing to start flash mode;
Preparing to open COM71
Connecting;
Loading;
Init;
Port opened;
Hello Received;
ERROR: Boot loading failed;

Log file saved to: LOG_14_02_2016_15_19_26.txt

Time needed - 00:00:29

This model is already supported. Contact me for tests on skype

Br

[BillA]

Originally Posted by .:hack3r2k:.

This model is already supported. Contact me for tests on skype

Br

So what's the correct procedure for the 5054N?

[.:hack3r2k:.]

Originally Posted by BillA

So what's the correct procedure for the 5054N?

You have to wait the update

Br