[TOOL] Newflasher (xperia command line flasher)

Search This thread
By:
Advanced…
Mohammed Ajeena

Mohammed Ajeena

Member
Sep 30, 2021
10
0
Guys, need your help and support to flash my 1 iv docomo version (SO-51C) to global version, I've tried to flash to (XQ-CT54) version, but it didn't work out knowing that I unlocked the bootloader and when trying to flash, it gives the below error.

signature:0000089c
device from 2021 and up?
download:0000089c
OKAY.
signature
Error, signature OKAY reply, got reply: FAILFAILFailed to verify cms!
 
munjeni

munjeni

Senior Member
Jun 2, 2011
9,666
22,362
Your phone model is SO-51C . You can't flash an fw if it is not SO-51C using newflasher , every firmware have signature verifiction and if fw is not designed for your phone model bootloader will reject flashing it because of wrong signature. The only way is botloader unlocking and some tools like https://forum.xda-developers.com/t/...-apple-unpack-any-sony-firmware-file.3530077/ so convert sin files to raw format and flash it jurself manualy trought command line. Don't ask how I do't know, not an easy task.
 
Last edited:
  • Like
Reactions: sieghartRM
Mohammed Ajeena

Mohammed Ajeena

Member
Sep 30, 2021
10
0
munjeni said:
Your phone model is SO-51C . You can't flash an fw if it is not SO-51C using newflasher , every firmware have signature verifiction and if fw is not designed for your phone model bootloader will reject flashing it because of wrong signature. The only way is botloader unlocking and some tools like https://forum.xda-developers.com/t/tool-sin2raw-v0-2-new-tool-to-extract-sin-files-updated.1834081/ so convert sin files to raw format and flash it jurself manualy trought command line. Don't ask how I do't know, not easy task. My tool doing almost the same https://forum.xda-developers.com/t/...-apple-unpack-any-sony-firmware-file.3530077/
Click to expand...
Click to collapse
Thanks for your help … so currently there is no way to flash a global ROM into my SO-51C easily like other versions
 
munjeni

munjeni

Senior Member
Jun 2, 2011
9,666
22,362
You should try one more time, if you getting "Failed to verify cms" thats mean rom is not compatible with your device.
 
Mohammed Ajeena

Mohammed Ajeena

Member
Sep 30, 2021
10
0
munjeni said:
You should try one more time, if you getting "Failed to verify cms" thats mean rom is not compatible with your device.
Click to expand...
Click to collapse
Well, i've tried many times and got the same error and below are the steps used:
1- Unblock the bootloader through official Sony website to get the code and then used ABD method to unlock and its unlocked.
2- Downloaded the official ROM for customized UK through Xperia Firm software.
3- Used Newflasher v.55
4- Deleted all .ta files include the one in the boot folder.
5- Follow the steps to flash untill get the error which i was explained earlier.
 
FirasMM

FirasMM

Member
Oct 3, 2021
7
0
Iraq
Sony Xperia 1 II
I try to convert the rom from japanese to global rom my phone is xperia 1 iv So-51c and i used newflasher v56 and rom XQ-CT54 but get this error
 

Attachments

  • newfasher.png
    newfasher.png
    128.6 KB · Views: 58
FirasMM

FirasMM

Member
Oct 3, 2021
7
0
Iraq
Sony Xperia 1 II
munjeni said:
Your phone model is SO-51C . You can't flash an fw if it is not SO-51C using newflasher , every firmware have signature verifiction and if fw is not designed for your phone model bootloader will reject flashing it because of wrong signature. The only way is botloader unlocking and some tools like https://forum.xda-developers.com/t/...-apple-unpack-any-sony-firmware-file.3530077/ so convert sin files to raw format and flash it jurself manualy trought command line. Don't ask how I do't know, not an easy task.
Click to expand...
Click to collapse
If i change all file sin by sony_dump what should be i rename the extension
 
munjeni

munjeni

Senior Member
Jun 2, 2011
9,666
22,362
FirasMM said:
If i change all file sin by sony_dump what should be i rename the extension
Click to expand...
Click to collapse
I don't have time for this, if you don't know I can't help sorry thats not easy and extremely danger for your phone, easily might brick your phone! My sugestion, don't play with it if you have no idea what you have need or what you have doing, otherwise big chance that you will need to buy new phone!
 
  • Like
Reactions: sieghartRM and FirasMM
FirasMM

FirasMM

Member
Oct 3, 2021
7
0
Iraq
Sony Xperia 1 II
munjeni said:
I don't have time for this, if you don't know I can't help sorry thats not easy and extremely danger for your phone, easily might brick your phone! My sugestion, don't play with it if you have no idea what you have need or what you have doing, otherwise big chance that you will need to buy new phone!
Click to expand...
Click to collapse
Sorry, I have some information, but I need additional information from you. Now I am converting all sin files or only partition folder files, and do I change the extension to ext4 or what? Thank you very much for your generosity.
 
munjeni

munjeni

Senior Member
Jun 2, 2011
9,666
22,362
Just open it with an hex editor and look, it might be ext4, fat, binary...etc, tool allready produce extension at the end if it detect it as an ext4 for example. I don't want to participate further because I haven't worked on it for a long time, today's phones are much more secure than before, so it's very possible that their protection is much more complicated and that it's very possible that if you flash something manually, you'll kill the phone, and I won't say anything further. You have to fend for yourself! I just made tool, the rest is "do it yourself".
 
  • Like
Reactions: sieghartRM and FirasMM
M

mantonio.lglez

New member
Jun 23, 2014
3
0
RIKEY0324 said:
Since My sony xperia XA2 Plus (H4493) occurs booting error (keep showing SONY when i boot)
then i got a problem like below when i want to flashing sony xperia XA2 Plus (H4493) by Newflasher v52
thanks fotr ur help (sorry for my bad English....)
Click to expand...
Click to collapse
I also have this problem.

My Xperia XA2 Ultra displays "Your device is corrupt. It can't be trusted and will not boot." when trying to boot into flash mode, but after several tries it boots to flash mode. This issue started after a few months stored without use. If I try too boot it normally (to Android), it hangs in the Sony logo.

I have the correct driver installed (SOMC Flash Device), the phone is charged, tried different USB cables, used USB 2.0 ports. Also, I tried Flash Tool and got error "Unit 10021 does not exist ( Hex unit value 00002725 )", Xperia Companion threw me error "UEUpdateFailed UE_2005" and trying to update with newflasher resulted in "Error, didn't got TA write 'go into flashmode' OKAY reply! Got reply: FAILUnable to write to TA unit 10100".

I'm trying to flash Customized US and the phone hasn't had the bootloader unlocked nor has never been rooted.

Searched everywhere but couldn't find anything else, and already ran out of ideas. I have no technical knowledge aside from reading tutorials and flashing some other phones.

Any help would be much appreciated.
 

Attachments

  • flashtool_2023-05-13_08-50-57.log
    3 KB · Views: 7
  • newflasher_H3223.txt
    2.2 KB · Views: 7
  • dump.rar
    6.2 KB · Views: 4
  • companion_log_2023_05_13T07_27_03Z.txt
    27.2 KB · Views: 4
Last edited:
munjeni

munjeni

Senior Member
Jun 2, 2011
9,666
22,362
What you have done before your device died? Looks like you have corupted trim area partition. Did you done something to it, did you wrote something to partitions? Do you have trim area backup?

In relation to FlashTool seems your firmware boot delivery xml file have some error, did you downloaded firmware trought XperiFirm? If yes make sure you not delete anything from it, just keep everything including all ta files, all .sin files, boot folder and all the rest unchanged. I will download 50.2.A.3.77-R2B and let you know if something is wrong with it! Edit, I'm checked your firmware its ok!

Edit:
I have made test version for XA2 devices, let me know if it work! Before you flash make sure you have downloaded firmware using XperiFirm and you didn't deleted or modified something inside firmware folder! Let me know!
 

Attachments

  • newflasher_XA2.zip
    2.1 MB · Views: 24
Last edited:
N

Noobie911

New member
Jul 15, 2018
2
0
Sony Xperia 5 II
I'm new with this stuff, and I wanna flash Japanese Global ROM for Xperia 5 II (Softbank A002SO to XQ-AS42), but I don't have any pc to work on atm. Can someone teach how to use newflash on android to android (via adb, or I guess termux or something)
 
M

mantonio.lglez

New member
Jun 23, 2014
3
0
munjeni said:
What you have done before your device died? Looks like you have corupted trim area partition. Did you done something to it, did you wrote something to partitions? Do you have trim area backup?

In relation to FlashTool seems your firmware boot delivery xml file have some error, did you downloaded firmware trought XperiFirm? If yes make sure you not delete anything from it, just keep everything including all ta files, all .sin files, boot folder and all the rest unchanged. I will download 50.2.A.3.77-R2B and let you know if something is wrong with it! Edit, I'm checked your firmware its ok!

Edit:
I have made test version for XA2 devices, let me know if it work! Before you flash make sure you have downloaded firmware using XperiFirm and you didn't deleted or modified something inside firmware folder! Let me know!
Click to expand...
Click to collapse
Hi.

Thank you very much for spending some of your time with my problem.

The device was dead before I tried to flash it. I don't think I did anything to the trim area partition, given that I flashed the firmware I downloaded from XperiFirm, but no, I don't have a trim area backup. I didn't delete any files from the firmware folder, the only thing I changed after the first failed attempt was the partition.sin file that I moved to the "partition" folder I created.

The test version of Newflasher did give me a different output, which I will attach. It said something about error code 997, but I was using a USB 2.0 port, since I already had this error before. I also noticed every flashing software I tried failed at rebooting the phone to every mode, I don't know what's with that.

I'm starting to believe it's a hardware issue from being stored so long without use (I don't know a thing about hardware). Maybe it's the battery, even though the phones charges and stays on. I will try to get a new one and try to flash it again.

Thank you very much again.
 

Attachments

  • newflasher_XA2.txt
    4.2 KB · Views: 13
munjeni

munjeni

Senior Member
Jun 2, 2011
9,666
22,362
Its something realy strange, for example this one:

Error writing command 'set_active:b'! Looks like slot B partitions is damaged.

Your phone is slot A active allready, You should try next steps:

I can sugest start from flashing partition since in most case your partitions is somehow messed up, since the newflasher got an error on the bluetooth and it didn't reach the flashing partition.sin, but it is important, so create an empty folder and put newflasher to it, than create "partition" folder in the same folder and put partition.sin file to partition folder, try flash! if everything went ok, reboot your device. Than flash bootdelivery, if succed try one by one sin file and see which one cause problem, start from bigest one for example system.sin and system_other.sin . I'm believing if you flash partition.sin sucesfully the rest will be easy (in case there is no hardware isue for example damaged emmc where partitions is stored).
 
Last edited:
AbibPirates_79

AbibPirates_79

New member
May 26, 2023
2
2
Indonesia
Sir can i ask? why always try to Flash Xperi 5 II Dual Sim - XQ-AS72

here says " Your Device is Error/Corrupt and cannot be trusted? "

i use newflasher_v55

any how to fix it sir? thank your sir ^_^
 
K

kodein

Senior Member
Jul 4, 2010
259
35
Zlín
Newflasher doesn't work for me either. After successfully flashing bootlop... Sony xperia 10IV. I had to fix the FW using sony companion
 
billycar11

billycar11

Senior Member
Mar 3, 2012
551
184
P.A.
Motorola Droid RAZR HD
Motorola Droid X
kodein said:
Newflasher doesn't work for me either. After successfully flashing bootlop... Sony xperia 10IV. I had to fix the FW using sony companion
Click to expand...
Click to collapse
forum.xda-developers.com

Flashing a Xperia 1 iii without unlocking

Things needed: 1. An Xperia 1 iii (of corse) 2. A Windows PC (I don't know if there's a Mac or Linux version, but I didn't find it) 3. A reliable USB-C cable 4. NewFlasher Download: [TOOL] Newflasher (xperia command line flasher) 5. XperiFirm...
forum.xda-developers.com forum.xda-developers.com
try this method it works on my 1 IV
 
K

kodein

Senior Member
Jul 4, 2010
259
35
Zlín
billycar11 said:
forum.xda-developers.com

Flashing a Xperia 1 iii without unlocking

Things needed: 1. An Xperia 1 iii (of corse) 2. A Windows PC (I don't know if there's a Mac or Linux version, but I didn't find it) 3. A reliable USB-C cable 4. NewFlasher Download: [TOOL] Newflasher (xperia command line flasher) 5. XperiFirm...
forum.xda-developers.com forum.xda-developers.com
try this method it works on my 1 IV
Click to expand...
Click to collapse
OK, I'll try. I just want to ask if I should delete the files with the extension *.TA from the FW folder? In some instructions for using newflasher, I read that they should be removed... And it was not in the instructions that I should use the command via cmd: newflasher set_active:a
 
You must log in or register to reply here.

Similar threads

A
[TOOL] [UPDATE 04/09/2015] Flashtool version 0.9.19.10 - Windows / Linux / Mac
Replies
4K
Views
5M
uriel cruzitho
uriel cruzitho
IgorEisberg
[TOOL] XperiFirm ~ Xperia Firmware Downloader [v5.6.5]
Replies
3K
Views
3M
P
poseidon35
zxz0O0
Easy Root Tool for various Xperia devices
Replies
2K
Views
1M
L
lawrenceh
DooMLoRD
[Drivers] FlashTool Xperia Driver Pack (v1.5) [20140318]
Replies
130
Views
975K
F
funnydoc
Toledo_JAB
  • Poll
[GUIDE] Recover 2012 and newer XPERIAs from SOFT-brick
Replies
2K
Views
579K
K
kentottxxzz

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 344
    munjeni
    munjeni
    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

    - version 52 (01.10.2021)
    Implemented userprompt for keeping userdata, thanks @OhayouBaka for figuring out! Removed bootloader log retrieval

    - version 53, 54, 55 (20.08.2022)
    Fix trimarea dumper crash on big endian machines, update building makefiles

    - version v56, v57 (07.07.2023)
    Add suport for Xperia 1 generation 5, changed bootdelivery xml atributes

    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
    View
    21
    munjeni
    munjeni
    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! ;)
    View
    14
    munjeni
    munjeni
    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!
    View
    12
    munjeni
    munjeni
    New version is out!
    View
    11
    munjeni
    munjeni
    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.
    View

New posts