yashsingh1/xdaforums huggingface dataset:
[Sony Cross-Device General] tanipat:
Seems we have progress here, really sorry i might not be able to get near my computer at least today. Tomorrow will try to involve this process, sorry about that mate. Cheers
[Sony Cross-Device General] thrash001:
--------------------------------------------------------
newflasher.exe by Munjeni @ 2017
--------------------------------------------------------
Device path: \\?\usb#vid_0fce&pid_b00b#5&15c311e1&0&12#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: USB-Controller
Device Instance Id: USB\VID_0FCE&PID_B00B\5&15C311E1&0&12

- Successfully write 0x18 bytes to handle.
- Successfully read 0xd bytes from handle.
Raw input [0xD]:

00000000 4F 4B 41 59 31 30 34 38 35 37 36 30 30 OKAY104857600

- Successfully write 0xe bytes to handle.
- Successfully read 0x9 bytes from handle.
Raw input [0x9]:

00000000 4F 4B 41 59 47 38 31 34 31 OKAYG8141

- Successfully write 0xe bytes to handle.
- Successfully read 0x9 bytes from handle.
Raw input [0x9]:

00000000 4F 4B 41 59 47 38 31 34 31 OKAYG8141

- Successfully write 0xe bytes to handle.
- Successfully read 0x9 bytes from handle.
Raw input [0x9]:

00000000 4F 4B 41 59 47 38 31 34 31 OKAYG8141

- Successfully write 0x17 bytes to handle.
ERROR: GetOverlapped_in_Result: failed with error code 31 as follows:
Ein an das System angeschlossenes Gerõt funktioniert nicht.

- Error reaply: less than 4!
Raw input [0x0]:

Drücken Sie eine beliebige Taste . . .

the new
[Sony Cross-Device General] munjeni:
New version is out, hope finally we get some good progress :fingers-crossed:
[Sony Cross-Device General] thrash001:
--------------------------------------------------------
newflasher.exe by Munjeni @ 2017
--------------------------------------------------------
Device path: \\?\usb#vid_0fce&pid_b00b#5&15c311e1&0&12#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: USB-Controller
Device Instance Id: USB\VID_0FCE&PID_B00B\5&15C311E1&0&12

- Successfully write 0x18 bytes to handle.
- Successfully read 0xd bytes from handle.
Raw input [0xD]:

00000000 4F 4B 41 59 31 30 34 38 35 37 36 30 30 OKAY104857600

- Successfully write 0xe bytes to handle.
- Successfully read 0x9 bytes from handle.
Raw input [0x9]:

00000000 4F 4B 41 59 47 38 31 34 31 OKAYG8141

- Successfully write 0xe bytes to handle.
ERROR: GetOverlapped_in_Result: failed with error code 31 as follows:
Ein an das System angeschlossenes Gerõt funktioniert nicht.

- Error reaply: less than 4!
Raw input [0x0]:

- Successfully write 0x19 bytes to handle.
ERROR: TIMEOUT: failed with error code 997 as follows:
▄berlappender E/A-Vorgang wird verarbeitet.
- Error reaply: less than 4!
Raw input [0x0]:

ERROR: TIMEOUT: failed with error code 997 as follows:
▄berlappender E/A-Vorgang wird verarbeitet.
- Error write! Need nBytes: 0x17 but done: 0x0
- Error writing command!
Drücken Sie eine beliebige Taste . . .
[Sony Cross-Device General] munjeni:
Hmm seems definitelly isue with function "receive" :( Will investigate more on this, again thanks a lot!

Edit:

Or maybe device disconnects when var not exists, strange :(
[Sony Cross-Device General] munjeni:
New version again, now I have added 3 retries on receive function, lets see
[Sony Cross-Device General] thrash001:
--------------------------------------------------------
newflasher.exe by Munjeni @ 2017
--------------------------------------------------------
Device path: \\?\usb#vid_0fce&pid_b00b#5&15c311e1&0&12#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: USB-Controller
Device Instance Id: USB\VID_0FCE&PID_B00B\5&15C311E1&0&12

- Successfully write 0x18 bytes to handle.
- Successfully read 0xd bytes from handle.
Raw input [0xD]:

00000000 4F 4B 41 59 31 30 34 38 35 37 36 30 30 OKAY104857600

- Successfully write 0xe bytes to handle.
- Successfully read 0x9 bytes from handle.
Raw input [0x9]:

00000000 4F 4B 41 59 47 38 31 34 31 OKAYG8141

- Successfully write 0xe bytes to handle.
ERROR: GetOverlapped_in_Result: failed with error code 31 as follows:
Ein an das System angeschlossenes Gerõt funktioniert nicht.

ERROR: TIMEOUT: failed with error code 997 as follows:
▄berlappender E/A-Vorgang wird verarbeitet.
ERROR: TIMEOUT: failed with error code 997 as follows:
▄berlappender E/A-Vorgang wird verarbeitet.
- Error reaply: less than 5!
Raw input [0x0]:

Drücken Sie eine beliebige Taste . . .
[Sony Cross-Device General] munjeni:
It crash on first receive, seccond two have status "operation in progress" OMG :(

Maybe I need to define excatly size of the receiving bytes, curently its determined by size of the tmp_buff which is 4096 so maybe that cause problem, strange. New version is out, let see
[Sony Cross-Device General] thrash001:
--------------------------------------------------------
newflasher.exe by Munjeni @ 2017
--------------------------------------------------------
Device path: \\?\usb#vid_0fce&pid_b00b#5&15c311e1&0&12#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: USB-Controller
Device Instance Id: USB\VID_0FCE&PID_B00B\5&15C311E1&0&12

- Successfully write 0x18 bytes to handle.
- Successfully read 0xd bytes from handle.
Raw input [0xD]:

00000000 4F 4B 41 59 31 30 34 38 35 37 36 30 30 OKAY104857600

- Successfully write 0xe bytes to handle.
- Successfully read 0x9 bytes from handle.
Raw input [0x9]:

00000000 4F 4B 41 59 47 38 31 34 31 OKAYG8141

- Successfully write 0xe bytes to handle.
- Successfully read 0x10 bytes from handle.
Raw input [0x10]:

00000000 4F 4B 41 59 30 2E 34 2D 53 4F 4E 59 2D 30 2E 31 OKAY0.4-SONY-0.1

- Successfully write 0x19 bytes to handle.
- Successfully read 0x29 bytes from handle.
Raw input [0x29]:

00000000 4F 4B 41 59 31 33 30 36 2D 35 30 33 35 5F 58 5F OKAY1306-5035_X_
00000010 42 6F 6F 74 5F 4D 53 4D 38 39 39 38 5F 4C 41 31 Boot_MSM8998_LA1
00000020 2E 31 5F 4E 5F 35 39 2D 41 .1_N_59-A

- Successfully write 0x17 bytes to handle.
- Successfully read 0x1a bytes from handle.
Raw input [0x1A]:

00000000 4F 4B 41 59 31 33 30 36 2D 38 34 39 39 5F 34 35 OKAY1306-8499_45
00000010 2E 30 2E 41 2E 31 2E 32 32 39 .0.A.1.229

- Successfully write 0xf bytes to handle.
- Successfully read 0xe bytes from handle.
Raw input [0xE]:

00000000 4F 4B 41 59 43 42 35 31 32 45 41 44 54 36 OKAYCB512EADT6

- Successfully write 0xd bytes to handle.
- Successfully read 0x7 bytes from handle.
Raw input [0x7]:

00000000 4F 4B 41 59 79 65 73 OKAYyes

- Successfully write 0x12 bytes to handle.
- Successfully read 0x8 bytes from handle.
Raw input [0x8]:

00000000 4F 4B 41 59 34 30 39 36 OKAY4096

- Successfully write 0x15 bytes to handle.
- Successfully read 0x14 bytes from handle.
Raw input [0x14]:

00000000 4F 4B 41 59 58 46 4C 2D 4D 53 4D 38 39 39 38 2D OKAYXFL-MSM8998-
00000010 4E 2D 33 35 N-35

- Successfully write 0xf bytes to handle.
ERROR: GetOverlapped_in_Result: failed with error code 31 as follows:
Ein an das System angeschlossenes Gerõt funktioniert nicht.

- Error reaply: less than 4!
Raw input [0x0]:

Drücken Sie eine beliebige Taste . . .

---------- Post added at 01:08 PM ---------- Previous post was at 01:00 PM ----------

Sorry, i must go now. See you later
[Sony Cross-Device General] munjeni:
Oh thats it. Definitelly receive packet must be defined explicitly to expected size, if defined size is bigger than receive size it crash whole things. Good thing we have identified isue finally! :highfive: Thank you a lot for your time!
[Sony Cross-Device General] munjeni:
Based on this info https://msdn.microsoft.com/en-us/library/windows/desktop/aa365467(v=vs.85).aspx parameter lpNumberOfBytesRead is only used in synchronous read/write which was case in my tool, now that parameter is NULL since we using asynchronous read/write, hope finaly we get thing working. New version is out :)
[Sony Cross-Device General] munjeni:
New version is out! I don't believing why I didn't saw this very banal thing in my code:

if ((tmp_reaply = get_reaply(dev, EP_IN, tmp, strlen(tmp), USB_TIMEOUT, 0)

thats a reason why thing not worked :) Instead of that it must be:

if ((tmp_reaply = get_reaply(dev, EP_IN, tmp, sizeof(tmp), USB_TIMEOUT, 0)

If this version is not working I will revert part of the previous post and it will definitelly work in next version, but I am pretty sure curent one will work too :)
[Sony Cross-Device General] munjeni:
OMG thats ok finaly! Just need to add support for FAILE and it will fully work :) I will told when new version is out! Many thanks!
[Sony Cross-Device General] munjeni:
New version is out! I am 99 percent sure this one will work finaly :)
[Sony Cross-Device General] munjeni:
mem leak fixed (hope), new version is out :)
[Sony Cross-Device General] mirhl:
Radare2? Snowman?
[Sony Cross-Device General] munjeni:
Didn't searched google but hope I will do that
[Sony Cross-Device General] :
attached file in theory should lock bootloader back

snowman didn't understand thumb2 and useless.

as for radare ;) well, check yourself
[Sony Cross-Device General] sToRm//:
Maybe you can send the files to me. If you want to, I could try to reproduce it.
[Sony Cross-Device General] munjeni:
Hm where you found that signed sin? I can't see that file in any firmware, devinfo.000 contain only single byte 0x00

Edit:

Anybody with unlocked bootloader post here dump of the devinfo partition?

dd if=/dev/block/platform/msm_sdcc.1/by-name/devinfo of=/data/local/tmp/devinfo.dump
[Sony Cross-Device General] :
found this file on my hard disk ;)

basically, its purpose to write zero to devinfo partition
[Sony Cross-Device General] munjeni:
So devinfo keeps unlock data? Or in case locked its empty?
[Sony Cross-Device General] levone1:
No devinfo here (XA)...
[Sony Cross-Device General] munjeni:
Basing on this https://xdaforums.com/showpost.php?p=73510405&postcount=370 it exist but seems its not mapped to userspace :)

Can you show list of the partitions?

ls -l /dev/block/platform/xxxxxxxxxxxx/by-name
[Sony Cross-Device General] :
and what ? it is also not present on Samsung S8 ;)

we talking here about G814x - first SFB device on Sony home-brewed Yoshino platform ( SDM630-based Discovery,Pioneer, MSM8998 G834x Maki-Anna-Aya and new flagship on SDM845 will all use UEFI-based XBoot ... )

and XBoot will use

devinfo - Guid Id B2509E68-B678-46C3-86D7-D05D432D714A
GUID Attributes	0x0000000000000000
GUID ID	B2509E68-B678-46C3-86D7-D05D432D714A
GUID Type	65ADDCF4-0C5C-4D9A-AC2D-D90B5CBFCD03
Mid	0x00000004
Name	devinfo
Size	4,00 KB
Start	0x00000A06
[Sony Cross-Device General] :
android 7.x will display "permission denied", but i'll show better stuff ;)
[Sony Cross-Device General] munjeni:
6 luns, I saw that in partition.zip. One thing which I have found on unlocked bootloader trim area dump, there is no 0x8b2 unit :confused: Seems totaly new way for unlocking bootloader. Probably drm key is also out of trim area?
[Sony Cross-Device General] munjeni:
66667 unit is drm key definitelly, seems its still on xzp trim area , thats great! Unit 0x8b2 is not inside trim area, at least inside [MENTION=8004595]FartyParty[/MENTION] unlocked xzp trim area dump, you can search for hex string B2 08 00 00 10 00 00 00 C1 E9 F8 3B or something like B2 08 00 00, but that unit exist on every unlocked pre xzp device, so that mean that unit is changed name or probably no more inside trim area.

But in s1loader we clearly have this, I have no idea why FartyParty trim area dump doesn't contain unit 8b2, see:

.text:00000000000318C4 MOV W1, #0x8B2
.text:00000000000318C8 MOV W0, #2
.text:00000000000318CC MOV X2, X19
.text:00000000000318D0 MOV W3, W21
.text:00000000000318D4 BL sub_410DC
.text:00000000000318D8 MOV W20, W0
.text:00000000000318DC CBZ W20, loc_31950
.text:00000000000318E0 ADRP X0, #aVendorSemcFs_2@PAGE ; "vendor/semc/fs/build/../main/build/linu"...
.text:00000000000318E4 ADD X0, X0, #aVendorSemcFs_2@PAGEOFF ; "vendor/semc/fs/build/../main/build/linu"...
.text:00000000000318E8 BL sub_23338
.text:00000000000318EC MOV X8, X0
.text:00000000000318F0 ADRP X0, #asc_E80F1@PAGE ; "[ERROR @ %s:%d]:\nFailed to write to mi"...
.text:00000000000318F4 ADD X0, X0, #asc_E80F1@PAGEOFF ; "[ERROR @ %s:%d]:\nFailed to write to mi"...
.text:00000000000318F8 MOV W2, #0x298
.text:00000000000318FC MOV X1, X8
.text:0000000000031900 BL sub_4D838
.text:0000000000031904 ADRP X4, #aFailfailedToWr@PAGE ; "FAILFailed to write to miscTA"
.text:0000000000031908 ADD X0, X23, #0x49
.text:000000000003190C MOV W2, WZR
.text:0000000000031910 MOV W1, #0x41
.text:0000000000031914 ADD X4, X4, #aFailfailedToWr@PAGEOFF ; "FAILFailed to write to miscTA"

Another trim area partition??
[Sony Cross-Device General] :
UEFI app "LinuxLoader" working with trim area too ... way earlier than xflash kernel loaded ;)
[Sony Cross-Device General] munjeni:
Whats name of the .mbn?

tzxflattest used for checking rooting status :confused:
[Sony Cross-Device General] :
abl_X_Boot_MSM8998_LA1_1_N_59-A.mbn

confirmed, that rooting status kept in devinfo partition with some kind of android boot status : red, orange, green.

once it cleared, no more root ( device key is deleted, though )
[Sony Cross-Device General] munjeni:
what about unit 8b2? Why it is no more inside trim area but function which write that unit stil exist in s1loader, can it be that we have another trim area?
[Sony Cross-Device General] :
i'm already wrote - this unit parsed by UEFI app and removed afterwards, similar to google lock reset unit.

if unlock key correct - device key erased, user area wiped, devinfo partition updated.

i'm think we can get raw trim area using ETS firmware, so far i'm can't find suitable commands, but i'm not finished research yet
[Sony Cross-Device General] munjeni:
I can see "hello sake" but seems function is unused, didn't saw href to it. Wbere you found part of the errasing unit, which mbn file?
[Sony Cross-Device General] :
format of devinfo partition

TDevInfo=record
magic: array [0..12] of char; // "ANDROID-BOOT!"
bUnlocked:byte;
bUnlock_critical:byte;
bChargerScreenEnabled:byte;
strBootVer: array [0..63] of byte;
strBasebandVer: array [0..63] of byte;
bVerityMode:byte;
end;
[Sony Cross-Device General] munjeni:
So guys can modify bytes in devinfo? But drm key is still bye bye after unlocking?
[Sony Cross-Device General] :
so devinfo.sin, which i'm posted, will reset bUnlocked and bootloader will be "locked" again.

as for device key, it is erased during bootloader unlock for sure
[Sony Cross-Device General] munjeni:
How can we dump x boot (on old devices it was s1 boot, PBL right?) We probably can patch it trought units 84F and 8FD as it was done on z1 - z3 lines for enabling permanent recovery mode. I din't had luck to dump pbl since apsolutly had no idea where pbl leave, but I am pretty sure we can patch pbl trought these two units, right?

This units was in trim area in time when we didn't had recovery mode:

//===========================================================
//===========================================================
// Rhine S1 Boot Config Data
//
// Config Data Description: http://metadoc.sonyericsson.net/?DOCS=1/15935-5/FCP1191274 PA2
// Honami
//
//
//
// Created: 20130115 1430
// Author: Fredrik Tiliander, 23048727
//
// Specification document: 8/159 35-LXE 108 010, Rev PA4
// Format:
// [TAPartition<HEX8>]{1}
// [UnitID<HEX32> UnitSize<HEX16> Data<HEX8>{UnitSize}]{n}
//===========================================================
02

0000084f 0049 1A CE 1D 00 01 00 04 05 00 02 02 51 00 10 03 00 02 04 02 05 00 01 03 02 00 10 05 00 03 03 05 00 10 0A 00 02 00 A9 09 BE BA A9 09 00 00 04 00 03 00 02 00 04 00 04 00 B0 04 0E 00 06 00 B8 0B 01 4B 00 00 00 03 96 00 2C 01
000008fd 0001 00

and this is configuration which I sniffed when used emma to enable recovery mode:

// this enables recovery mode
0000084f 0054 1A CE 28 00 01 00 06 05 00 02 02 51 00 10 03 00 02 04 02 05 00 01 03 02 00 10 05 00 03 03 05 00 10 05 00 05 83 02 00 10 02 00 05 85 0A 00 02 00 A9 09 BE BA A9 09 00 00 04 00 03 00 02 00 04 00 04 00 B0 04 0E 00 06 00 B8 0B 01 4B 00 00 00 03 96 00 2C 01
000008fd 0001 00
[Sony Cross-Device General] munjeni:
What is ETS, you mean baseband right?
[Sony Cross-Device General] :
PBL is is ROM

ETS - it is special firmware, testprogram for calibration and tests.

attached main binary
[Sony Cross-Device General] munjeni:
What mean ets? How can I dump pbl from xperia z1 compact? File which you atached cant be primary boot loader (first one in boot chain) PBL because pbl can't be dynamic binary, its first thing in boot chain.
[Sony Cross-Device General] mirhl:
Easy Test System maybe?
[Sony Cross-Device General] sToRm//:
I think it's "Evil Trolling System". That's more Sony like :laugh:
[Sony Cross-Device General] mirhl:
Mhh, tbh if it's that.. It doesn't seems just a sony thing.
[Sony Cross-Device General] munjeni:
ETS - it is special firmware, testprogram for calibration and tests.
[Sony Cross-Device General] munjeni:
Where is pbl excatly? Maybe in an of the 8 pin chips?? I have another spare z1c, and I have equipment like rt809F and I have some more like easy jtag with emmc adapter, Seger Jlink Edu... but I no want to waste time by reading every 8 pin chips from mainboard, just need precise info about location of the pbl! I have pinouts of the direct emmc on main board, no need to desolder it! If I get pbl location I will try my best to understand units 84f and 8fd

Edit:

Oh your etc binary is from yoshino (XZ2) :eek: but that phone is not released yet :confused:

Library rpath '../../_fs_yoshino/system/lib/'
[Sony Cross-Device General] :
1.

PBL is inside qualcomm MCP, but it is unlikely that it is accessible from android

define BOOT_ROM_START_ADDRESS_BASE 0xfc000000
define BOOT_ROM_END_ADDRESS_BASE 0xfc02ffff

2.

yoshino is sony platform, based on msm8998, first yoshino is xperia xz premium
[Sony Cross-Device General] munjeni:
https://www.google.rs/search?biw=12...cfro=1...0...1.2.64.psy-ab..0.0.0.TspdFR1p6lc

No result. Is there any way to dump it with rt809? PBL is not inside emmc, right?
[Sony Cross-Device General] :
PBL is in embedded ROM inside qualcomm msm8974 chipset

can be read with JTAG if chipset unfused
[Sony Cross-Device General] Boscep:
hi [MENTION=4120742]munjeni[/MENTION],

I'm sorry due to unable pm so I post here.

if you don't mind, may I request make_ext4fs.exe which support file_contexts.bin?

most user would happy with it.

thank you.

---------- Post added at 02:24 PM ---------- Previous post was at 02:23 PM ----------

hi [MENTION=4120742]munjeni[/MENTION],

I'm sorry due to unable pm so I post here.

if you don't mind, may I request make_ext4fs.exe which support file_contexts.bin?

most user would happy with it.

thank you.
[Sony Cross-Device General] munjeni:
I'm believing make_ext4fs is already on xda, you can try search
[Sony Cross-Device General] munjeni:
I'm believing that we can't dump pbl from android anyway, if I am not wrong I tried to map that region from kernel and wasn't lucky
[Sony Cross-Device General] AJHutchinson:
Good to see your back :good::highfive:
[Sony Cross-Device General] the_brad:
my post

Maybe you guys have anything, I could test :good:
[Sony Cross-Device General] ImSpiderman:
Hey, first time Sony user here, can i flash a firmware from a different operator without unlocking bootloader? will i get updates?
[Sony Cross-Device General] munjeni:
Yes sure! But pay attention to model, e.g. G8141 or G1842
[Sony Cross-Device General] askermk2000:
Hello

I have not read this thread, only the last bit here, but I think I have something relevant.

On LG V20, which uses msm8996 chipset, there appears to have been dumped pbl with FlashFire by [MENTION=631273]Chainfire[/MENTION]

I was requesting partition dump for my hardbrick recovery testing. This guy gave me a zip containing some unusual partition names and sizes.

He said it was a backup made by FlashFire app.
[Sony Cross-Device General] munjeni:
I'm believing there is no pbl inside partition dump since pbl is not on partitions. It would be so easy for hack in case pbl lives on partition :)
[Sony Cross-Device General] askermk2000:
I know pbl is not on normal storage.

But a file called *pbl* was in the dump, so I thought it must been dumped from memory. There was some other weird things also, like a combined xbl1 and 2 (there are two xbl's on partitions).

I'll attach the file, maybe you can determine if it is actually what it seems.
[Sony Cross-Device General] ch3mn3y:
XZ1 and Compact firmware is out (at least StoreFront) and is same as XZp's, so Newflasher seems to be the only way to flash it :)

Other new Xperia, XA1 Plus, still uses old flashing protocol, so FLashtool or Xflasher will work with it.
[Sony Cross-Device General] munjeni:
1600 downloads after last update and only 3 thanks received :confused: Lets hope xz1 guys give more grates to newflasher. I will give updates to xz1 line!
[Sony Cross-Device General] serajr:
Sad but true, this is what unfortunately is happening lately here. And it's because of this kind of thing that I'm starting to think this way !
[Sony Cross-Device General] munjeni:
I'm a litle mad, not because of no thanks, but because I made newlasher for free. But I thinking to move to the revolutionary tool (user side + server side), server side will be hiden and nobody will be able to reverse enginer it, ofcourse all paid ;)
[Sony Cross-Device General] mirhl:
You are kind mad because you made the tool for free and..??

Also wtf, I'm counting 161 thanks in the OP.

Totally in line with the 90-9-1 rule.
[Sony Cross-Device General] munjeni:
157 was before attachment! 1700 downloads! That say something? To remind you, I don't own xzp. I done it just to make peoples happy. I made it for free. I made it in my spare free time. I don't need money for it. I'm not paid for it. And last thing, I had no needs to make it! If our facts is not clear I have nothing more to say, everything clear. I know, not all can understand our post, but I'm sure gratefull peoples can. And one more thing, when all devs gone and when everything gets paid everybody will think about why it is no more free.
[Sony Cross-Device General] mirhl:
Yes, I know it's free, in your free time, by your kind soul and all.

But I really cannot understand what's the physical happening that you are talking about then. I just checked google cache, and you had 158 (and 1592 views) 36 hours ago.

I'm not sure why just 4 *

new* forum users

(because for as much as I'd like to make thanks rain I cannot more than once per post) having discovered your work in a day and half is such a disgrace?

I mean, even if the number was far lower (or higher?), even if you had to have all your sources on github under the WTFPL..

people (noobs mostly) downloading, getting happy because of your work as you say, but not reporting, would be disrespectful of your credit because..?
[Sony Cross-Device General] munjeni:
I am 6 years on xda and never saw 1600 downloads and just 5 thanks. I have no problem with it! I just found it strange! Is not that a strange?
[Sony Cross-Device General] ishemes:
Hey munjeni,

First thank you for the flasher. It helped me get a different firmware on my phone.

About the amount of thanks, probably the people who downloaded the latest version include people who also downloaded older versions and already pressed thanks. They can't thank the same post again (can they?).

Also, for me personally, I have two modes when I'm on xda. Either I'm reading and investigating which is when I give a lot of thanks. Or I'm getting ready to do make some change on my phone, like flashing firmware or flashing some zip. Then I'm just downloading something and closing the page. I then need to remember to go back later to hit the thanks button. I often forget this.This is how I used your tool without giving thanks. Anyway, I hit the thanks button after reading your post. Because hey, thank you! :D
[Sony Cross-Device General] munjeni:
Ok lets skip this thema, as I wrote it was strange for me. Ican't force anybody to press thanks, It's a matter of respect.
[Sony Cross-Device General] G-FACE:
I can't find an instrucion on how to use this tool to flash firmwware from another android device.

Can you please explain in details?

Thanks.
[Sony Cross-Device General] munjeni:
The same like doing it on pc. Main diferencie is on android you can't double click newflasher, instead run it trought terminal emulator :)
[Sony Cross-Device General] zohaib0001:
Is any one try this tool on Xperia XZ