F3311 Dead After Flash

[alamgarh]

I flash this phone with this version after that it was giving errors.

APP-SW_Bassoon_GLOBAL-LTE1A_37.0.A.2.156_1301-9750_S1-SW-LIVE-8C38-PID1-0005-MBR

FSP_Bassoon_Cosmote-GR_GENERIC_37.0.A.2.156_1303-0166_R9A_S1-SW-LIVE-8C38-PID1-0005-MMC

Then i flash with this version. and now phone is not coming on and not connecting with pc. i dissconnect battery but same.



8/21/2017 3:31:37 PM SIGNED MODE (USING SERVER)
8/21/2017 3:31:37 PM CFG:100000000000
8/21/2017 3:31:37 PM PLEASE ATTACH TURNED OFF PHONE NOW
8/21/2017 3:31:37 PM PRESS AND HOLD "BACK" OR "VOLUME DOWN" BUTTON ...
8/21/2017 3:31:56 PM
8/21/2017 3:31:56 PM RUNNING S1_LOADER VER "S1_Boot_MT6735_M0.MP16_27"
8/21/2017 3:31:56 PM
8/21/2017 3:31:56 PM ACTIVE_COMP_AID : 0004
8/21/2017 3:31:56 PM HWCONF_AID : 0004
8/21/2017 3:31:56 PM LOADER_AID : 0004
8/21/2017 3:31:56 PM BOOT_AID : 0004
8/21/2017 3:31:56 PM
8/21/2017 3:31:56 PM [ llcomm: 00800000,00080000 ]
8/21/2017 3:31:56 PM DEVICE ID: AE38B5AC8164D7C9
8/21/2017 3:31:56 PM FLASH ID: "0015/01000001"
8/21/2017 3:31:56 PM LOADER VERSION: S1_Boot_MT6735_M0.MP16_27
8/21/2017 3:31:56 PM
8/21/2017 3:31:56 PM PHONE IMEI : 35374808922803
8/21/2017 3:31:56 PM writing "D:\SeTool\FLASH FILES\f3311\New folder\APP-SW_Bassoon_GLOBAL-LTE1A_37.0.A.1.83_1301-9750_S1-SW-LIVE-8C38-PID1-0005-MBR.zip"
8/21/2017 3:31:56 PM Processing package
8/21/2017 3:31:56 PM APP-SW_Bassoon_GLOBAL-LTE1A_37.0.A.1.83_1301-9750_S1-SW-LIVE-8C38-PID1-0005-MBR.zip
8/21/2017 3:31:56 PM
8/21/2017 3:31:56 PM Testing package integrity ...
8/21/2017 3:32:20 PM PROCESSING: partitions_S1-SW-LIVE-8C38-PID1-0005-MBR.sin
8/21/2017 3:32:21 PM UPDATING S1_BOOT TO VERSION : 1301-1718 S1_BOOT_MT6735_M0.MP6_13
8/21/2017 3:32:21 PM PARSING: "DEVELOPMENT"
8/21/2017 3:32:21 PM value OTP_LOCK_STATUS_1 : UNLOCKED, not match LOCKED
8/21/2017 3:32:21 PM PARSING: "COMMERCIAL"
8/21/2017 3:32:21 PM value OTP_LOCK_STATUS_1 : LOCKED, match LOCKED
8/21/2017 3:32:21 PM value PLF_ROOT_1 : 1DAEA2E9731CA81CAD71EF4655B0E73A4F5AF6F194518ADCA1 350D92E9F3E468, match 1DAEA2E9731CA81CAD71EF4655B0E73A4F5AF6F194518ADCA1 350D92E9F3E468
8/21/2017 3:32:21 PM PROCESSING : preloader_s1sbl_S1-BOOT-LIVE-8C38-0004-MMC.sin
8/21/2017 3:32:21 PM PROCESSING : secro_S1-BOOT-LIVE-8C38-0004-MMC.sin
8/21/2017 3:32:21 PM PROCESSING : lk_S1-BOOT-LIVE-8C38-0004-MMC.sin
8/21/2017 3:32:21 PM PROCESSING : logo_S1-BOOT-LIVE-8C38-0004-MMC.sin
8/21/2017 3:32:22 PM PROCESSING : tee1_S1-BOOT-LIVE-8C38-0004-MMC.sin
8/21/2017 3:32:23 PM PROCESSING : tee2_S1-BOOT-LIVE-8C38-0004-MMC.sin
8/21/2017 3:32:23 PM PROCESSING : Bassoon_S1BootConfig_MiscTA.ta
8/21/2017 3:32:23 PM Writing TA unit 0002/084F/0075
8/21/2017 3:32:23 PM Writing TA unit 0002/08FD/0001
8/21/2017 3:32:23 PM BOOT UPDATED
8/21/2017 3:32:23 PM SKIP: partitions_S1-SW-LIVE-8C38-PID1-0005-MBR.sin
8/21/2017 3:32:23 PM PROCESSING: cache_S1-SW-LIVE-8C38-PID1-0005-MMC.sin
8/21/2017 3:32:23 PM PROCESSING: apps_log_S1-SW-LIVE-8C38-PID1-0005-MMC.sin
8/21/2017 3:32:23 PM PROCESSING: diag_S1-SW-LIVE-8C38-PID1-0005-MMC.sin
8/21/2017 3:32:24 PM PROCESSING: boot_S1-SW-LIVE-8C38-PID1-0005-MMC.sin
8/21/2017 3:32:26 PM PROCESSING: fotakernel_S1-SW-LIVE-8C38-PID1-0005-MMC.sin
8/21/2017 3:32:28 PM PROCESSING: system_S1-SW-LIVE-8C38-PID1-0005-MMC.sin
8/21/2017 3:34:34 PM writing "D:\SeTool\FLASH FILES\f3311\New folder\FSP_Bassoon_Optimus-PT_GENERIC_37.0.A.1.83_1303-5533_R2A_S1-SW-LIVE-8C38-PID1-0005-MMC.zip"
8/21/2017 3:34:34 PM Processing package
8/21/2017 3:34:34 PM FSP_Bassoon_Optimus-PT_GENERIC_37.0.A.1.83_1303-5533_R2A_S1-SW-LIVE-8C38-PID1-0005-MMC.zip
8/21/2017 3:34:34 PM
8/21/2017 3:34:34 PM Testing package integrity ...
8/21/2017 3:34:34 PM PROCESSING: userdata_S1-SW-LIVE-8C38-PID1-0005-MMC.sin
8/21/2017 3:34:38 PM PROCESSING: oem_S1-SW-LIVE-8C38-PID1-0005-MMC.sin
8/21/2017 3:34:47 PM Processing UPDATE files
8/21/2017 3:34:47 PM SKIP: simlock.ta
8/21/2017 3:34:47 PM PROCESSING: cust-reset.ta
8/21/2017 3:34:47 PM Writing TA unit 0002/08A4/000E
8/21/2017 3:34:47 PM Elapsed: 190 seconds

[alamgarh]

I m still waiting for someone to help me.

[moshman]

According to TAC database phone IMEI is for Sony Xperia E5

[:Aishur:]

that is correct, maybe the firmware is too old. Please, reflash the newest one

TAC8 = 35966607;35374808

0000 "F3311 Optimus_PT 1303-5533" "F3311/Mobile Phone/MH410cWhite/Optimus PT (Portugal)/White"
elabel-F3311-row-row_201607140137939.1_37.0.A.2.108_S1-ELABEL-LIVE-8C38-PID1-0004-MMC.zip
APP-SW_Bassoon_GLOBAL-LTE1A_37.0.A.2.108_1301-9750_S1-SW-LIVE-8C38-PID1-0005-MBR.zip
FSP_Bassoon_Optimus-PT_GENERIC_37.0.A.2.108_1303-5533_R3A_S1-SW-LIVE-8C38-PID1-0005-MMC.zip
1303-2337_R4A_Generic_GGL_Released.zip

this time don't forget the elabel part and a full charged battery

[alamgarh]

Originally Posted by moshman

According to TAC database phone IMEI is for Sony Xperia E5

Thanks for reply. Sir every time before flashing I m taking Info with identify botton. I got this model in identify then I flashed.

[alamgarh]

Originally Posted by :Aishur:

that is correct, maybe the firmware is too old. Please, reflash the newest one

TAC8 = 35966607;35374808

0000 "F3311 Optimus_PT 1303-5533" "F3311/Mobile Phone/MH410cWhite/Optimus PT (Portugal)/White"
elabel-F3311-row-row_201607140137939.1_37.0.A.2.108_S1-ELABEL-LIVE-8C38-PID1-0004-MMC.zip
APP-SW_Bassoon_GLOBAL-LTE1A_37.0.A.2.108_1301-9750_S1-SW-LIVE-8C38-PID1-0005-MBR.zip
FSP_Bassoon_Optimus-PT_GENERIC_37.0.A.2.108_1303-5533_R3A_S1-SW-LIVE-8C38-PID1-0005-MMC.zip
1303-2337_R4A_Generic_GGL_Released.zip

this time don't forget the elabel part and a full charged battery

Thanks Sir the battery was almost more than 50% .. then I flashed it. And I m 100% sure it is F3311. Because I identify it. And I can relax it because I mentioned already that. Is not connecting with pc . I try holding all keys one by one and together also. Is it possible that if it's boot damage . Can I fix with tp or....

[:Aishur:]

there is a big issue with downgrading F32xx and F33XX ie MT67x5
The result of downgrading is a dead phone
I reported your thread to setool forum
https://support.setool.net/showthrea...311-test-point

[:Aishur:]

Now it is confirmed, downgrading F3311 results a dead phone
Please visit https://support.setool.net/showthrea...DATES-AND-NEWS and read posts #287 and #288
hope you can find soon enough the testpoint.

[:Aishur:]

credits go to kerpua and bravo-tel

[the_laser]

Originally Posted by :Aishur:

there is a big issue with downgrading F32xx and F33XX ie MT67x5
The result of downgrading is a dead phone
I reported your thread to setool forum
https://support.setool.net/showthrea...311-test-point

only some phones are prone to this.
i'm personally repeat "dead flash" attept : flashed F3311 phone to firmware version, which was initially in user phone and then downgraded it to exactly same version, which was in user log.

result : live phone.

after this, i'm tried another 3 versions in various configurations.
result : live phone.

in any case, you can fix any boot problems with MT-based sony phones using setool2, testpoint is not required in case of dead boot.

ps.
shown testpoint picture is very bad : need to cut shielding screen,etc.
testpoint matrix should be freely accessible on board ( it is done for factory flashing )

[:Aishur:]

Hi, thanks sir for your precisions.

I haven't seen yet the mobo and missed with it. I can only guess it is easy to remove the shield cover (no hassle) . It is not needed to cut the shield. With a simple needle we can shunt the test point to the ground (shield). I can’t estimate the hardness of the work.
https://www.youtube.com/watch?v=qDlxL_PgRRE&vl=en
Anyway very happy to lecture you
Best regards

[the_laser]

again - there MUST be NORMAL testpoint matrix, which freely accessible after back cover removal, without shield cover removal,board removal,etc.

and thanks, i'm perfectly know, how to disassembly any sony phone to shreds

[soebpatel1988]

f3311 after flashing on setool phone is dead any solution?

[the_laser]

for you : take phone to other service center with setool2.

[zagalo2]

Originally Posted by the_laser

only some phones are prone to this.
i'm personally repeat "dead flash" attept : flashed F3311 phone to firmware version, which was initially in user phone and then downgraded it to exactly same version, which was in user log.

result : live phone.

after this, i'm tried another 3 versions in various configurations.
result : live phone.

in any case, you can fix any boot problems with MT-based sony phones using setool2, testpoint is not required in case of dead boot.

ps.
shown testpoint picture is very bad : need to cut shielding screen,etc.
testpoint matrix should be freely accessible on board ( it is done for factory flashing )

good day brother please can i get driver?