Кастомные прошивки и техническая часть устройств Joyetech, Wismec, Eleaf, Vaporflask

[ReikoKitsune]

So i try to write some not too stupid messages to get my postcount high enough to be allowed to attach files.

Hello,
You can provide links in your messages, but present them in the text form, not clickable. For example like this: http:// i.imgur.com/buIRwjX.png (blank image). Just insert space between url scheme and path.

[Musik234]

You can provide links in your messages, but present them in the text form, not clickable. For example like this: (blank image). Just insert space between url scheme and path.

Ok, I will try:
(try...try...try)
No, doesn't work.
Maybe, if I split the link from one line to another:
goo.gl/
7D2NDh
Ah, that works!

I also had a at-sign in my last posting to MicroSur, that made me get an error by the forum.

OK, back to topic.
I just tested MicroSur's patch and it works. So the "START" mode is now fixed (not yet written into the .patch file).

Now about the things I have done with the firmware eVic 3.01:
In the pictures in my dropbox-folder you can see the three different modes "POWER", "BYPASS" and "START".
To do this, I copied the "text"-block between 0xC660 and 0xC7A7 to the end of the file.
I tried to make a .patch file for the copied part, but that didn't work for some reason.

Then I had to change 4 hex values in the file to make the new text-positions work.

# Automatically generated content #
# You can add your comments here #
# changed adresses and offsets #
# new offset from "TEMP" -> "POWER" #
66B0: FF
# new offset from "TEMP" to new entry for "BYPASS" #
6738: 27
# new offset from "TEMP" to new entry for "START" #
67A0: FF
# new start address of "TEMP" #
6830: E9
6831: F3

This finally makes the new firmware.

When I want to edit this file with NFirmwareEditor (btw, great tool ) I have to change the definitions.txt:

<StringTable1>

<OffsetFrom>0xC9D0</OffsetFrom>
<OffsetTo>0xCB40</OffsetTo>

</StringTable1>

The firmware starts reading each string at a fixed address and reads to the next 0x00. NFirmwareEditor starts each text-block at 0x00 to the next 0x00 and i cannot access and change (add or remove) a 0x00.

ReikoKitsune; maybe you can change your program to start reading each text block at the last 0x00 before a non 0x00 value. That wouldn't change the behaviour from the files which are not patched and could handle "my" patched files. And if you could make it possible to choose a 0x00 at the point where I can change the letters of the strings I think it would be perfect (for me )
Maybe this point needs more brainstorming...

Thanks for reading and I hope you don't mind me writing in english.
And let me know what you think about my ideas: or