• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[TOOL] Newflasher (xperia command line flasher)

Search This thread

munjeni

Senior Member
Jun 2, 2011
9,409
21,998
Thanks for fast response, Why this issue not happened to my xperia 1ii? it's working fine with SEA firmware and volte working fine. I have few more doubts I only once unlocked bootloader before, I think it was xperia z2. is this cause to lose DRM keys? will that affect low light photography? HDR will work on netflix? Can it be repaired through xperia companion? I need to know this before try.
Response for your question about drm is on this page allready! See post 1827. Further question about feature please ask in your device forum

One more thing i noticed, it may be a bug i guess, Battery capacity changing after flash, last month before i flash checked battery health it was 3850mah, after flash i got device corrupted message then i fixed it by changed slot and flash. After flash i checked battery health it was showing 3660mah(I was shocked). yesterday also i checked battery before flash it was 3660mah. but after device corrupted message i used xperia companion to fix the issue. now it showing 3575mah. will this be a bug? i am checking battery health by entering "*#*#SERVICE#*#*".
This have nothing to do to newflasher, this is firmware or hardware related
 
Last edited:

munjeni

Senior Member
Jun 2, 2011
9,409
21,998
Thanks.
version 49 worked for me.
but I also have another problem. My phone is a development board.
it's not have Volte setting option, but my sim card has Volte
so sim card not worked in China.
I hope you can help me;
Thanks!
Hi, this depend on firmware in use, you will need to flash firmware which have working volte, I can sugest ask in xperia 10 mark III forum to get idea which rom have working volte
 
  • Like
Reactions: songxuke

munjeni

Senior Member
Jun 2, 2011
9,409
21,998
Dear sir, need help with this log,
I need to flash SOV37 AU to global Rom

=========== BOOTLOADER LOG =============
INIT: Wed Jan 24 00:28:07 1973
[ERROR @ fastboot.c:2255]:
fastboot_get_variable: Could not find variable Emmc-info
[ERROR @ authenticate.c:594]:
Failed to get key. (-1007)
INIT: Wed Jan 24 00:28:07 1973

=================================================

=========== FIRMWARES HISTORY LOG =============
NEW_VERSION: erased_user_data:true, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA1.0_O_57, cdf_version:1313-4752_R15A, fs_version:GENERIC_51.1.C.0.385, sw_version:1311-9107_51.1.C.0.385
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA1.0_O_61, cdf_version:1313-4752_R17A, fs_version:GENERIC_51.1.C.9.31, sw_version:1311-9107_51.1.C.9.31
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA2.0_P_118, cdf_version:1313-4752_R13B, fs_version:GENERIC_52.0.C.1.112, sw_version:1311-9107_52.0.C.1.112
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA2.0_P_118, cdf_version:1313-4752_R13B, fs_version:GENERIC_52.0.C.5.46, sw_version:1311-9107_52.0.C.5.46
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA2.0_P_118, cdf_version:1313-4752_R13B, fs_version:GENERIC_52.0.C.5.90, sw_version:1311-9107_52.0.C.5.90
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA2.0_P_118, cdf_version:1313-4752_R13B, fs_version:GENERIC_52.0.C.5.164, sw_version:1311-9107_52.0.C.5.164
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA2.0_P_118, cdf_version:1313-4752_R13B, fs_version:GENERIC_52.0.C.5.205, sw_version:1311-9107_52.0.C.5.205
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA2.0_P_118, cdf_version:1313-4752_R13B, fs_version:GENERIC_52.0.C.5.253, sw_version:1311-9107_52.0.C.5.253
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA2.0_P_118, cdf_version:1313-4752_R13B, fs_version:GENERIC_52.0.C.5.282, sw_version:1311-9107_52.0.C.5.282
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA2.0_P_118, cdf_version:1313-4752_R13B, fs_version:GENERIC_52.0.C.5.295, sw_version:1311-9107_52.0.C.5.295
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA2.0.1_Q_206, cdf_version:1313-4752_R14C, fs_version:GENERIC_52.1.C.0.157, sw_version:1311-9107_52.1.C.0.157
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA2.0.1_Q_206, cdf_version:1313-4752_R14C, fs_version:GENERIC_52.1.C.0.192, sw_version:1311-9107_52.1.C.0.192
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA2.0.1_Q_206, cdf_version:1313-4752_R14C, fs_version:GENERIC_52.1.C.0.220, sw_version:1311-9107_52.1.C.0.220

=================================================

Set slot 'a' active.

Device is put now out of flash mode.
Sent command: reboot.

Done.
Closing device.
Press any key to continue . . .

Please, need your help
Your log is incomplete and not enought. If you have flashed rom without errors thats a question for appropriate forum!
 

diva2711

New member
Aug 1, 2021
2
1
Dear sir, need help with this log,
I need to flash SOV37 AU to global Rom

=========== BOOTLOADER LOG =============
INIT: Wed Jan 24 00:28:07 1973
[ERROR @ fastboot.c:2255]:
fastboot_get_variable: Could not find variable Emmc-info
[ERROR @ authenticate.c:594]:
Failed to get key. (-1007)
INIT: Wed Jan 24 00:28:07 1973

=================================================

=========== FIRMWARES HISTORY LOG =============
NEW_VERSION: erased_user_data:true, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA1.0_O_57, cdf_version:1313-4752_R15A, fs_version:GENERIC_51.1.C.0.385, sw_version:1311-9107_51.1.C.0.385
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA1.0_O_61, cdf_version:1313-4752_R17A, fs_version:GENERIC_51.1.C.9.31, sw_version:1311-9107_51.1.C.9.31
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA2.0_P_118, cdf_version:1313-4752_R13B, fs_version:GENERIC_52.0.C.1.112, sw_version:1311-9107_52.0.C.1.112
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA2.0_P_118, cdf_version:1313-4752_R13B, fs_version:GENERIC_52.0.C.5.46, sw_version:1311-9107_52.0.C.5.46
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA2.0_P_118, cdf_version:1313-4752_R13B, fs_version:GENERIC_52.0.C.5.90, sw_version:1311-9107_52.0.C.5.90
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA2.0_P_118, cdf_version:1313-4752_R13B, fs_version:GENERIC_52.0.C.5.164, sw_version:1311-9107_52.0.C.5.164
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA2.0_P_118, cdf_version:1313-4752_R13B, fs_version:GENERIC_52.0.C.5.205, sw_version:1311-9107_52.0.C.5.205
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA2.0_P_118, cdf_version:1313-4752_R13B, fs_version:GENERIC_52.0.C.5.253, sw_version:1311-9107_52.0.C.5.253
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA2.0_P_118, cdf_version:1313-4752_R13B, fs_version:GENERIC_52.0.C.5.282, sw_version:1311-9107_52.0.C.5.282
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA2.0_P_118, cdf_version:1313-4752_R13B, fs_version:GENERIC_52.0.C.5.295, sw_version:1311-9107_52.0.C.5.295
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA2.0.1_Q_206, cdf_version:1313-4752_R14C, fs_version:GENERIC_52.1.C.0.157, sw_version:1311-9107_52.1.C.0.157
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA2.0.1_Q_206, cdf_version:1313-4752_R14C, fs_version:GENERIC_52.1.C.0.192, sw_version:1311-9107_52.1.C.0.192
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1310-7079_X_Boot_SDM845_LA2.0.1_Q_206, cdf_version:1313-4752_R14C, fs_version:GENERIC_52.1.C.0.220, sw_version:1311-9107_52.1.C.0.220

=================================================

Set slot 'a' active.

Device is put now out of flash mode.
Sent command: reboot.

Done.
Closing device.
Press any key to continue . . .

Please, need your help
solved sir, thank you
 
  • Like
Reactions: munjeni

jamshadinho

Senior Member
Jan 21, 2013
82
0
thrissur
Response for your question about drm is on this page allready! See post 1827. Further question about feature please ask in your device forum


This have nothing to do to newflasher, this is firmware or hardware related
Thanks, Now i changed slot to A and flashed. Now its showing SEA. unfortunately no VOLTE. *#*#4636#*# shows volte provisioned disabled and greyed out. Xperia 1ii SEA firmware supports VOLTE in india. is it possible to flash modem files of xperia 1ii to 5ii? or else any other way? I think sony removed Volte configuration of indian carriers. Now I am afraid xperia 1 iii may also not include Volte configuration. Now i need to switch to 1ii. I really miss my blue xperia 5ii and it's 120hz refresh rate.
 

munjeni

Senior Member
Jun 2, 2011
9,409
21,998
Thanks, Now i changed slot to A and flashed. Now its showing SEA. unfortunately no VOLTE. *#*#4636#*# shows volte provisioned disabled and greyed out. Xperia 1ii SEA firmware supports VOLTE in india. is it possible to flash modem files of xperia 1ii to 5ii? or else any other way? I think sony removed Volte configuration of indian carriers. Now I am afraid xperia 1 iii may also not include Volte configuration. Now i need to switch to 1ii. I really miss my blue xperia 5ii and it's 120hz refresh rate.
I have xperia 10 mark 1, and I dont know anything related to mark 3, so as I said ask in your device model xda subforum to get more chance for what you need, newflasher thread is only for newflasher related things
 

munjeni

Senior Member
Jun 2, 2011
9,409
21,998
I think new version, need to add a feature that allows you to choose whether to format the data or not.
Option allready exist! Yoo need to know which files to delete before start flashing. Those files is userdata.sin, fota-reset.ta and maybe some more, to get idea consults with somebody in your device subforum which files to delete. Do in mind unlocking bootloader mean fota reset and erase userdata is performed by bootloader by default. Keeping userdata when flashing I call it "lazy flashing", my sugestion is always to backup personal files before flash, than flash all including userdata erase, than simply restore userdata when I found right rom for my personal use. That way I know that everything is setled right. If I do "lazy flash" at least I learned it on my z1c when I didn't erased userdata I got selinux denials on internal storage since my files on userdata didn't had right selabels and I had problems to access, modify, delete personal files. After that my option is always to erase userdata.
 
Last edited:

alphonsezero

Member
Jun 5, 2013
36
4
Hi. I try Xperia 1 III SO-51B flash SOG03 firmware. this is log. Can support SO-51B version 49?

Product: SO-51B
Version: 0.4
Bootloader version: 1322-1669_X_Boot_SM8350_LA1.0_R_25
Baseband version: 61.0.C.5.24
Serialno: QV780J9P8R
Secure: yes
Loader version: 1322-1669_X_Boot_SM8350_LA1.0_R_25
Phone ID: 0000:35782335053552
Device ID: BDD675C1
Platform ID: 301350E1
Max download size: 805306368
Sector size: 4096
Rooting status: NOT_ROOTABLE
Ufs info: SAMSUNG,KLUEG8UHDB-C2E1,0102
Emmc info: FAILEmmc-info not supported
Default security: ON
Keystore counter: 2
Security state: kYtGG7IOxouuokR2xwoaY2Yr8Js+GZ2FVy6ZB0QuGZI=
Sake root: 032F03E14777E1B8A88520664B7B
S1 root:
Root key hash: DE899A8AE73A3BB3062F1597B3316A930095EEC7CE8BD9641DE7850E034211E10B8D032F03E14777E1B8A88520664B7B
Slot count: 2
Current slot: a
Battery level: 15

Device is put now in flash mode.

Repartitioning...
Found partition_delivery.xml in partition folder.
Determining LUN0 size...
UFS raw data[0xE0]:

00000000 59 00 00 00 00 00 03 04 01 00 01 7F 00 01 04 00 Y...............
00000010 03 10 02 21 00 01 02 03 01 CE 16 1A 02 00 00 01 ...!............
00000020 01 20 00 00 20 00 00 00 00 00 04 00 00 00 00 00 . .. ...........
00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000050 00 01 01 01 01 00 00 1E 00 2D 02 00 01 00 00 00 .........-......
00000060 00 00 00 0C 00 00 00 00 03 B9 48 00 00 00 00 01 ..........H.....
00000070 03 00 00 00 00 03 B9 48 00 00 00 00 00 00 00 00 .......H........
00000080 00 00 00 00 00 00 2D 02 01 01 01 01 00 00 03 00 ......-.........
00000090 0C 00 00 00 00 00 00 08 00 00 00 00 01 03 00 00 ................
000000A0 00 00 00 00 08 00 00 00 00 00 00 00 00 00 00 00 ................
000000B0 00 00 00 2D 02 02 01 02 01 00 00 03 00 0C 00 00 ...-............
000000C0 00 00 00 00 08 00 00 00 00 01 03 00 00 00 00 00 ................
000000D0 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

LUN0 size = 249896960

Processing partition-image-LUN0_124936192_X-FLASH-ALL-4BA8.sin
Skipping partition-image-LUN0_124936192_X-FLASH-ALL-4BA8.sin

Processing partition-image-LUN0_249896960_X-FLASH-ALL-4BA8.sin
- Extracting from partition-image-LUN0_249896960_X-FLASH-ALL-4BA8.sin
- Extracting signature partitionimage_0.cms
- Uploading signature C:\Users\Owner\Downloads\newflasher_v49\SOG03_KDDI JP_61.0.D.2.89\partition\partitionimage_0.cms
signature:0000089c
device from 2021 and up?
download:0000089c
OKAY.
signature
Error, signature OKAY reply, got reply: FAILFAILFailed to verify cms!

=========== BOOTLOADER LOG =============
TA_PHONE_NAME is empty
TA_SW_UNIT is empty
Emmc-info not supported
Soc-unique-id not supported
XCmdSakeChallenge: 1325: sake_ssn=1 Save
XCmdSakeResponse: 1380: sake_ssn=1 Get
XCmdSakeResponse: 1423: res=0 auth_level=1
backup xflkeystore
xflkeystore sz=65536
backup xflkeystorebak
xflkeystorebak sz=65536
backup TA
TA sz=8388608
backup xflkeystore
xflkeystore sz=65536
backup xflkeystorebak
xflkeystorebak sz=65536
backup TA
TA sz=8388608
backup xflkeystore
xflkeystore sz=65536
backup xflkeystorebak
xflkeystorebak sz=65536
backup TA
TA sz=8388608
FAILFailed to allocate memory
CmdErase: 2328: bootloader NOT YET SUPPORT !!!
CmdFlash: 1970: No check partition exists or not for bootloader
CmdErase: 2328: bootloader NOT YET SUPPORT !!!
CmdFlash: 1970: No check partition exists or not for bootloader
FAILUnit 4917 does not exist
Emmc-info not supported
Soc-unique-id not supported
Error, failed to handle USB event
Emmc-info not supported
Soc-unique-id not supported
Emmc-info not supported
Soc-unique-id not supported
XCmdSakeChallenge: 1325: sake_ssn=1 Save
XCmdSakeResponse: 1380: sake_ssn=1 Get
XCmdSakeResponse: 1423: res=0 auth_level=1
Error, failed to handle USB event
Emmc-info not supported
Soc-unique-id not supported
Emmc-info not supported
Soc-unique-id not supported
Error, failed to handle USB event
FAILUnit 10021 does not exist
Error, failed to handle USB event
Emmc-info not supported
Failed to verify cms
FAILFailed to verify cms
Failed to verify cms
FAILFailed to verify cms
Emmc-info not supported
Failed to verify cms
FAILFailed to verify cms
Failed to verify cms
FAILFailed to verify cms
Error, failed to handle USB event
Emmc-info not supported
Failed to verify cms
FAILFailed to verify cms
Failed to verify cms
FAILFailed to verify cms
v)m╧r└fT√Ωi
=================================================

=========== FIRMWARES HISTORY LOG =============
NEW_VERSION: erased_user_data:true, variant:user, s1boot_version:1322-1669_X_Boot_SM8350_LA1.0_R_25, cdf_version:Unknown: May 4 2021/02:53:38, fs_version:Unknown: May 4 2021/02:53:38, sw_version:61.0.C.5.24

=================================================

Set slot 'a' active.

Device is put now out of flash mode.
Sent command: powerdown.

End. You can disconnect your device when you close newflasher
Closing device.
Press any key to continue . . .
 

munjeni

Senior Member
Jun 2, 2011
9,409
21,998
Hi. I try Xperia 1 III SO-51B flash SOG03 firmware. this is log. Can support SO-51B version 49?

Product: SO-51B
Version: 0.4
Bootloader version: 1322-1669_X_Boot_SM8350_LA1.0_R_25
Baseband version: 61.0.C.5.24
Serialno: QV780J9P8R
Secure: yes
Loader version: 1322-1669_X_Boot_SM8350_LA1.0_R_25
Phone ID: 0000:35782335053552
Device ID: BDD675C1
Platform ID: 301350E1
Max download size: 805306368
Sector size: 4096
Rooting status: NOT_ROOTABLE
Ufs info: SAMSUNG,KLUEG8UHDB-C2E1,0102
Emmc info: FAILEmmc-info not supported
Default security: ON
Keystore counter: 2
Security state: kYtGG7IOxouuokR2xwoaY2Yr8Js+GZ2FVy6ZB0QuGZI=
Sake root: 032F03E14777E1B8A88520664B7B
S1 root:
Root key hash: DE899A8AE73A3BB3062F1597B3316A930095EEC7CE8BD9641DE7850E034211E10B8D032F03E14777E1B8A88520664B7B
Slot count: 2
Current slot: a
Battery level: 15

Device is put now in flash mode.

Repartitioning...
Found partition_delivery.xml in partition folder.
Determining LUN0 size...
UFS raw data[0xE0]:

00000000 59 00 00 00 00 00 03 04 01 00 01 7F 00 01 04 00 Y...............
00000010 03 10 02 21 00 01 02 03 01 CE 16 1A 02 00 00 01 ...!............
00000020 01 20 00 00 20 00 00 00 00 00 04 00 00 00 00 00 . .. ...........
00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000050 00 01 01 01 01 00 00 1E 00 2D 02 00 01 00 00 00 .........-......
00000060 00 00 00 0C 00 00 00 00 03 B9 48 00 00 00 00 01 ..........H.....
00000070 03 00 00 00 00 03 B9 48 00 00 00 00 00 00 00 00 .......H........
00000080 00 00 00 00 00 00 2D 02 01 01 01 01 00 00 03 00 ......-.........
00000090 0C 00 00 00 00 00 00 08 00 00 00 00 01 03 00 00 ................
000000A0 00 00 00 00 08 00 00 00 00 00 00 00 00 00 00 00 ................
000000B0 00 00 00 2D 02 02 01 02 01 00 00 03 00 0C 00 00 ...-............
000000C0 00 00 00 00 08 00 00 00 00 01 03 00 00 00 00 00 ................
000000D0 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

LUN0 size = 249896960

Processing partition-image-LUN0_124936192_X-FLASH-ALL-4BA8.sin
Skipping partition-image-LUN0_124936192_X-FLASH-ALL-4BA8.sin

Processing partition-image-LUN0_249896960_X-FLASH-ALL-4BA8.sin
- Extracting from partition-image-LUN0_249896960_X-FLASH-ALL-4BA8.sin
- Extracting signature partitionimage_0.cms
- Uploading signature C:\Users\Owner\Downloads\newflasher_v49\SOG03_KDDI JP_61.0.D.2.89\partition\partitionimage_0.cms
signature:0000089c
device from 2021 and up?
download:0000089c
OKAY.
signature
Error, signature OKAY reply, got reply: FAILFAILFailed to verify cms!

=========== BOOTLOADER LOG =============
TA_PHONE_NAME is empty
TA_SW_UNIT is empty
Emmc-info not supported
Soc-unique-id not supported
XCmdSakeChallenge: 1325: sake_ssn=1 Save
XCmdSakeResponse: 1380: sake_ssn=1 Get
XCmdSakeResponse: 1423: res=0 auth_level=1
backup xflkeystore
xflkeystore sz=65536
backup xflkeystorebak
xflkeystorebak sz=65536
backup TA
TA sz=8388608
backup xflkeystore
xflkeystore sz=65536
backup xflkeystorebak
xflkeystorebak sz=65536
backup TA
TA sz=8388608
backup xflkeystore
xflkeystore sz=65536
backup xflkeystorebak
xflkeystorebak sz=65536
backup TA
TA sz=8388608
FAILFailed to allocate memory
CmdErase: 2328: bootloader NOT YET SUPPORT !!!
CmdFlash: 1970: No check partition exists or not for bootloader
CmdErase: 2328: bootloader NOT YET SUPPORT !!!
CmdFlash: 1970: No check partition exists or not for bootloader
FAILUnit 4917 does not exist
Emmc-info not supported
Soc-unique-id not supported
Error, failed to handle USB event
Emmc-info not supported
Soc-unique-id not supported
Emmc-info not supported
Soc-unique-id not supported
XCmdSakeChallenge: 1325: sake_ssn=1 Save
XCmdSakeResponse: 1380: sake_ssn=1 Get
XCmdSakeResponse: 1423: res=0 auth_level=1
Error, failed to handle USB event
Emmc-info not supported
Soc-unique-id not supported
Emmc-info not supported
Soc-unique-id not supported
Error, failed to handle USB event
FAILUnit 10021 does not exist
Error, failed to handle USB event
Emmc-info not supported
Failed to verify cms
FAILFailed to verify cms
Failed to verify cms
FAILFailed to verify cms
Emmc-info not supported
Failed to verify cms
FAILFailed to verify cms
Failed to verify cms
FAILFailed to verify cms
Error, failed to handle USB event
Emmc-info not supported
Failed to verify cms
FAILFailed to verify cms
Failed to verify cms
FAILFailed to verify cms
v)m╧r└fT√Ωi
=================================================

=========== FIRMWARES HISTORY LOG =============
NEW_VERSION: erased_user_data:true, variant:user, s1boot_version:1322-1669_X_Boot_SM8350_LA1.0_R_25, cdf_version:Unknown: May 4 2021/02:53:38, fs_version:Unknown: May 4 2021/02:53:38, sw_version:61.0.C.5.24

=================================================

Set slot 'a' active.

Device is put now out of flash mode.
Sent command: powerdown.

End. You can disconnect your device when you close newflasher
Closing device.
Press any key to continue . . .
Newflasher support SO-51B but you need to flash SO-51B firmware, you can NOT flash SOG03 firmware!
 

Avn88

New member
Aug 5, 2021
2
1
Hi @munjeni

Thank you for providing the tools and tutorials, I have the same issue with my xperia 1 III, and trying every posible ways to fix it. May I know how to switch the slot from B to A ? where should I insert this command line?

newflasher set_active:a
 

munjeni

Senior Member
Jun 2, 2011
9,409
21,998
Can Newflasher flash baseband?
if it can, how to flash?
if it can not, how to flash base band?
my phone is xperia 10 iii
Hope for help,
Thanks!
It can! You need to know which sin file contain baseband so when you found it simply flash those sin file. If you not know which sin file contain baseband ask somebody in xperia 10 III forum
 
Last edited:
  • Like
Reactions: songxuke

munjeni

Senior Member
Jun 2, 2011
9,409
21,998
Hi @munjeni

Thank you for providing the tools and tutorials, I have the same issue with my xperia 1 III, and trying every posible ways to fix it. May I know how to switch the slot from B to A ? where should I insert this command line?

newflasher set_active:a
You need to insert it in windows command prompt https://www.google.com/search?q=10+Ways+to+Open+the+Command+Prompt+in+Windows+10

Or simply create batch file in the same folder with newflasher. If this is all hard for you see this tutorial https://www.androidjungles.com/check-and-change-current-active-slot-on-android/
 

Avn88

New member
Aug 5, 2021
2
1
  • Like
Reactions: munjeni

DennisDD78

Senior Member
Apr 22, 2011
435
72
Vladivostok
So, let me to summarize, please, to flash normally Xperia 1 III i should switch to slot A before flashing with phone connected in flash mode and then flash any f/w with Newflasher as usual ?
 

DennisDD78

Senior Member
Apr 22, 2011
435
72
Vladivostok
By the way, i do not see simlock.ta in the TW and HK downloaded firmwares! Yes, i read that NF is skipping this file by default in new versions, but i prefer to play it safe and delete it manually, but i can`t find this file in firmware`s files structure, maybe it`s hidden somewhere ?
 

munjeni

Senior Member
Jun 2, 2011
9,409
21,998
You no need to change slot, you should change slot to A if slot B is not bootable for you. Simlock.ta is not hiden, if you not see it it probably not exist
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Is it ok to always forcing "set active slot a" command before flashing, or should I do it after first time flash was failed and getting a corrupt screen only?
    Its simple, if your device not boot on slot b you should switch to slot a and reflash, and vicewersa.
    1
    Is it possible to downgrade Sony Xperia 1ii with Android 11 to Android 10 without unlocking bootloader?
    Not because of rollback protection
    1
    Hi everyone, PLEASE HELP ME, I have Xperia 1 III(XQ-BC72) HK fw, I tried to flash TW fw for my phone, flashing done but my phone doesn't open reboot and reboot again. I tried to repair with Xperia Companion but device no charge enough fot repair. I want to charge it but when I plug it to charge reboot and reboot again. How can I charge it? How can I save my phone? @munjeni

    Please there are a lot of user like this https://forum.xda-developers.com/t/...w-to-charge-it-with-infinite-reboots.4314999/
    I see you solved it https://forum.xda-developers.com/t/...t-with-infinite-reboots.4314999/post-85648815 , it would be great if you share info to others with the same isue.
  • 309
    Disclaimer:

    newflasher tool was made for testing and educational purposes, ME is not responsible for what you do on/with your device using newflasher, you must agree that you using newflasher on your own risk, I am not responsible if you brick your device or anything else!


    How to use:

    OPTIONAL STEP 1:
    - if you have missing flash driver just double click exe and confirm driver extraction, an exe will become available, run it and install driver.

    OPTIONAL STEP 2:
    - this step is optional, this step dump trim area, you can do this and keep those file somewhere on your pc in case you hard brick your device so give it to servicians to repair your phone.

    STEP 1:
    - Download right firmware for your device using XperiFirm tool, put newflasher.exe into firmware dir created by XperiFirm tool. Before you double click newflasher.exe do in mind something, newflasher tool is programed to flash everything found in the same dir!!! So tool flash all .ta files, all .sin files, boot delivery (whole boot folder), partition.zip, in short all files found in dir! If you no want to flash something just move file which you no want to flash OUT OF FOLDER! Partition.zip .sin files can be flashed only if you extract partition.zip into newly created folder called partition!

    STEP 2:
    - To start flashing phone put your phone into flash mode, double click newflasher.exe and wait wait wait until your device gets flashed, thats it. Look into log to see if something goes wrong! If all right you are done. If not post your log so I can look!

    SOME MORE THINGS:
    "You do not need to unlock bootloader or to root the phone if you want to flash a stock firmware from XperiFirm.
    There are no files in the stock firmware that need to be deleted. Prompts will ask you to skip some files.
    Feel free to press N to every prompt since:
    - TA dumping it's not related with DRM keys.
    - Flash persist_* files only if you know what you are doing, since you will lose your attest keys. Backup persist partition.
    If you need the firmware on both A and B slot use fastboot commands to choose the inactive partion and re-flash."

    Happy flashing!


    Supported platforms:

    - Newflasher is working on Windows, Linux, Android and Darwin, just chose right newflasher binary. With Android version you can flash phone by using another phone!


    Changelog:

    - version 1: Sorry a lot of work is done in pre pre alpha version and I can't count every changes, just folow development process about version 1, a lot of work is done before it started working. One esential change was done to tool improvement and it is described in one of the my posts related to moving function "erase:" to the section before function "flash:", it is realy improvement and more safer than in time when it was at the start of flashing routine.

    - version v2 (15.Aug.2017)
    Implemented free disk space safety check, it was missing and danger in case flashing process gets interupted because of the lack of the free disk space needed for sin extractions and temporary files. I have also include GordonGate flash driver prompt so in case somebody have missing flash drivers, simple need to double click exe and folow drivers archive extraction procedure, later need to install these drivers trought Windos device mannager. Also I have implemented an realy pre pre alpha version of the maybe non working trim (why maybe? Because I don't own xzp so can't test) area dump routine, in case it is working we can dump some esentials trim area units from device (probably not a full dump as like it was on every oldest xperia models - no permissions for dumping drm key unit)

    - version v3 (23.09.2017)
    Some more security checks, it's now a bit safer than v2

    - version v4 (21.10.2017)
    Updated trim area dumper, now it stores log to the trimarea.log but dump is now in .ta format and writen to the 01.ta and 02.ta

    - version v5 (22.10.2017)
    Updated trim area dumper, add progress meter, fix y-n prompt (thanks @pbarrette)

    - version v6 (22.10.2017)
    Updated trim area dumper

    - version v7 (23.10.2017)
    Updated trim area dumper, newflasher redesigned a bit, fix new partitioning for Oreo

    - version v8 (24.10.2017)
    Fix trim area dumper

    - version v9 & v10 (25.10.2017)
    Workaorunds on trim area dumper

    - version v11 (07.04.2018)
    Support for 2018 devices

    - version v12 (29.04.2018)
    Try fix doublefree bug/crash (most noticed on Linux 64 bit binary)

    - version v13 (01.05.2018)
    Fix doublefree bug/crash by removing dynamic allocation from function get_reply

    - version v14 & v15 (12.06.2019)
    Sony XPeria 1 support added.

    - version v16 (16.06.2019)
    LUN0 detection optimized.

    - version v17 (24.06.2019)
    LUN0 detection bug fixed.

    - version v18 (10.08.2019)
    Untested fix for https://forum.xda-developers.com/cr...wflasher-xperia-command-line-t3619426/page105
    Using builtin mkdir instead of calling it trought system call

    - version v19 (08.10.2019)
    Implemented prompt for flashing persist partition; print skipped .sin files

    - version v20 (13.12.2019)
    implemented prompt for flashing bootloader,bluetooth,dsp,modem,rdimage to booth a,b slots

    - version v21 (29.06.2020)
    implemented battery level status check before flashing, flashing bootloader,bluetooth,dsp,modem,rdimage to booth a,b slots is mandatory now and is flashed by default right now, more info, try fix previously reported isue on sync and powerdown command reported 2-3 years ago so I have disabled it and now enabled for test, implemented Macos support (curently need to be tested! If you have plan to test please flash only cache.sin DO NOT flash the rest because of safety for your device!)

    - version v22 (30.06.2020)
    trying to fix battery capacity retrieval

    - version v23 (04.07.2020)
    removed battery capacity retrieval (not going to work that way), fix trim area dump file name, new gordongate drivers

    - version v24 (04.07.2020)
    new feature - now you can run newflasher from script or console with your own command, e.g. newflasher getvar:Emmc-info , I didn't tested all the list of commands, if you do it share them with us!

    - version v25 (09.07.2020)
    New trim area dump tool, with this change trim area dump is created in 3 secconds. Do in mind this not dump protected units like drm key...etc! Some changes in scripting feature from v24

    - version v26 (10.07.2020)
    Added 4 diferent reboot modes, reboot to android, reboot to fastboot, reboot to bootloader, power off

    - version v27 (11.07.2020) (not yet released)
    Workaround in mac libusb

    - version v28 (12.07.2020)
    Workaround to sync response bug; Fully implemented support for Mac. I'm tested myself on mac 10.14 but confirmed working on mac 10.15 too

    - version v29 (12.07.2020)
    Mac proper libusb deinitialisation

    - version v30 (13.07.2020)
    Preparation for Debian packaging; I'm noticed that hex modified arm64 fake pie binary is not working so its now compiled with ndk and its true pie binary now

    - version v31 (14.07.2020)
    Fix cosmetic bug https://forum.xda-developers.com/showpost.php?p=83056693&postcount=1212 which might confuse somebody

    - version 32, not yet released

    - version 33 (30.07.2020)
    Allow bootloader unlocking with newflasher; Try fix sync response bug for win and darwin too

    - version 34 (08.08.2020)
    Added support for 32bit sized trim area units (as trim area api changed in xperia mark 2 line) (not yet released because of bug)

    - version 35 (08.08.2020)
    Updated support for 32bit sized trim area units (as trim area api changed in xperia mark 2 line); Move trim area dumps out of root folder so it not get acidentaly flashed, dumps is now inside folder tadump

    - version 36 (27.08.2020)
    Some improvements and and possible bug fixes

    - version 37 (09.12.2020)
    Added support for Xperia 5 II with emmc instead of ufs (not working)

    - version 38 (10.12.2020)
    Fixed impropper implementation from v37

    - version 39 (13.12.2020)
    Since mark 2 devices protocol is changed a bit and on some devices OKAY reply is not in separated usb poacket, instead it is merged with data packet, added support for it

    - version 40 (03.01.2021)
    Temporary solution for determining partition 0 sin file caused by two diferent emmc csd info we found recently on mark 2 devices

    - version 41 (03.01.2021)
    Removed temporary solution from version 41 so right lun0 sin file get flashed and seccond lun0 get skipped or booth skipped if lun0 sin file do not match device storage size

    - version 42 (11.03.2021)
    Fix bug in flashing booth slots when current slot is A, thanks to @chrisrg for discovering bug!

    - version 43 (12.06.2021)
    Support for Mark 3 devices

    - version 44 (19.06.2021)
    Fully Mark III device implementation

    - version 45 (20.06.2021)
    Implemented battery level check and prompt user to take a risk and continue flashing or stop flasing if battery level is less than 15 percent

    - version 46 (08.07.2021)
    Fix problem with filenames which contain "_other", it need to be always flashed to the diferent slot

    - version 47 (15.07.2021)
    Removed prompt for persist.sin flashing, now its by default skip. Implemented bootloader log retrieval at the end of flashing for better understanding when something goes wrong. Implemented firmware log history retrieval for those who want to know history of the flashed firmwares

    - version 48 (19.07.2021)
    Flash bootloader,bluetooth,dsp,modem,rdimage to booth slots only on a,b devices

    - version 49 (31.07.2021)
    Support for XQ-BT41

    - version 50 (12.08.2021)
    Workin progress on asynchronous usb to make it more like synchronous, added progress bar during send-receive usb packets and more logging. Increased usb timeout to 2 minute. Trying fix sync command at the end of flashing as reported here -> https://github.com/munjeni/newflasher/issues/42

    - version 51 (12.08.2021)
    Fix empry line printed while receiving usb packets, thanks @elukyan

    Credits:

    - without @tanipat and his pc companion debug logs this tool will never be possible! Thank you a lot for your time providing me logs! (by the influence of others, He was disappointed me with last post, but I still appreciate his help and can't forget it)
    - without @thrash001 who helped testing our tool I never be continue building our tool since I don't have device for testing, thanks mate!
    - didn't forgot @beenoliu, thanks mate for testing!
    - thanks to @porphyry for testing linux version!
    - thanks to @Snow_Basinger for providing sniff log from 2018 device and for testing on his 2018 device
    - thanks to @frantisheq for testing newflasher on his 2018 device and for notify about doublefree bug
    - thanks to @serajr for providing me some logs which helped me to figure out some things related to 2018 devices
    - thanks to @noelex for helping in Xperia 1 implementation
    - thanks to @Meloferz for testing on his xperia 1 mark II
    - thanks to github contributors, testers and reporters: vog, noelex, TheSaltedFish, solarxraft, pbarrette, MartinX3, kholk
    - thanks to Chirayu Desai for tracking addition to Debian and thanks to vog for initiating all that
    - thanks to @elukyan for testing and providing me usb sniff logs for mark 3 devices imlementation, thank you so much

    Common errors and how to solve:
    https://forum.xda-developers.com/t/tool-newflasher-xperia-command-line-flasher.3619426/post-72610228

    Source code:

    https://github.com/munjeni/newflasher
    20
    Please remember something, I made newflasher for all you, I didn't made it for me remember that, I dodn't ask for money for my work, all is for free, all is done in my spare time and for free, I have made everything just to make all you happy, remember that! I must say something more, some xda members, including some moerators, don't appreciate my effort, thats shame. I lost my recognised developer / recognised contributor title because ot that guys, I allways must remind all you that.

    Enjoy flashing! Cheers! ;)
    14
    V14 is out, added Xperia 1 support (curently untested!)

    If you flash partitions please give me newflasher log, need to know if I implemented things right!
    12
    New version is out!
    11
    New version is out! Changelog:
    - implemented flash driver, just double click exe and folow procedure (optional step)
    - trim area dump (optional step and maybe not a functional! Need confirmation.)

    Do not use any old newflasher, its soo old and definitelly not a better than latest one! Folow my instructions and put a trust on me, I am developer of the newflasher and nobody know that better than me, if you have a questions just ask here! I have removed my posts because virus tolal found a malware on all my exe files. Later I found what was going on. UPX (any version) contain the same malware, but since my exe was packed with upx all my exe contain the same malware, reason was UPX! Have no idea why virustotal see upx as a malware but I need now to recompile all my exe without using upx just because I no want to risk with it, don't know if that upx is false warining or not but definitelly better idea omiting upx.