View Full Version : changing bitmaps..
homicidal10denC
30-12-2002, 04:17 PM
hi, when i try to change bitmaps in flsedit, they always get screwed up.. so i thought that if found the bitmap in the flash and manually changed it, it would work. so i tried searching for the hex that flsedit shows, and i found know results, so i am asking how are the bitmaps stored.. i mean if they are not stored as the hex that is shown in flsedit..then how can i find them?
cyclo
30-12-2002, 04:30 PM
flsedit shows binary not hex (correct me if I'm wrong here). What I would do if I were you was use the show graphics function in winarm to find the graphics you want to replace.
The procedure is rather easy. Ask if you need help ;-)
homicidal10denC
30-12-2002, 05:32 PM
flsedit does show the hex..unless binary has suddenly become more than 1s and 0s, and 'hex data' is an abbreviation for binary... lol..im jokin thanks ill try winarm
homicidal10denC
30-12-2002, 05:36 PM
ok yes, i do need help. i choose view bitmap and the bitmaps dont exactly show how i would expect them...help me!
GeeZuZz
30-12-2002, 06:17 PM
You can use NokHex to change graphics too.
Or PPMedit.
Or HexGraph.
There is a lot of programs!
Nokhex 1.04 is attached.
homicidal10denC
30-12-2002, 06:20 PM
doesnt seem 2 wrk with 6250 flashe (nokhex and ppmedit) so ill try hexgraph
tried hexgraph..it doesnt seem to load the bitmaps
NokDoc
31-12-2002, 03:50 AM
Hi,
Some phone types have their bitmapped stored in a coded way.
This is no real coding, I think it is a method to minimise storage space voor sequential same data strokes.
Here's a coding demo for 3410-409, adr 2592BC, size 10hx07h
Data 12003E110A00113C3E11123C110036...
Data is stored in "AB1122" 3 bytes blocks.
A is the number of repeats for the first byte '11'
B is the number of repeats for the second byte '22'
So the string 34AABB would give us uncoded AAAAAABBBBBBBB
In the 3410 logo:
12 003E, 1 time 00 and 2 times 3E (003E3E)
11 0A00, 1 time 0A and 1 time 00 (0A00)
11 3C3E, 1 time 3C and 1 time 3E (3C3E)
U now only have to paste all those blocks to one line again and the logo could be displayed like the regular ones.
003E3E0A003C3E123C00363E0836...
Like as in FlsEdit...
NokDoc
ryan_chong
31-12-2002, 06:08 AM
Hello.....
For me,PPMedit still the best to do this.Easier for me.
Just load any bitmaps tat suite and u'll get it work properly.
Have a try on it:)
Thanks....
homicidal10denC
31-12-2002, 02:59 PM
im not sure if i get you nokdok....
would:
000000000000c04040c0c000c0 (shown in flsedit)
be written as:
6100c02240c01100c0
in the flashes hex?
REYESITO
03-01-2003, 12:03 AM
somebody knows as finding the graphic of callers groups, because these they are not in mapbits กกกก
in that code this?
as I make to change callergroups them without logomanager?
:rolleyes: :rolleyes: :confused: :cool:
cyclo
03-01-2003, 12:48 AM
I think the caller group graphic is in the eeprom and is encoded different than the images in the ppm+mcu. It is also encoded differently on different phones as far as I remember.
It's a while since I looked into it, but if I'm not mistaken the 6150 has it encoded as a ota bitmap while a 6210 has it encoded in some unknown way.....
homicidal10denC
07-01-2003, 08:42 PM
nokdoc, can you answer my question please?
NokDoc
07-01-2003, 09:42 PM
Mr. Homicidal10denC,
I'm very sorry.
If 000000000000c04040c0c000c0 (shown in flsedit) should be written as 6100c02240c01100c0 ?
6 x 00
1 x C0
2 x 40
2 x C0
1 x 00
1 x C0
makes:
00 00 00 00 00 00 C0 40 40 C0 C0 00 C0
Yes, quite right.
About the group logos.
I think they are in the eeprom area and the bitmap pixel bits are lined up in horizontal rows.
Plain, no coding.
NokDoc
dzhun85
06-03-2003, 10:29 PM
uhmm... in using winarm??? when i view bmp... i don't see the bmp as is??? whats wrong with it??? anyonw pls help... im still an amateur in using this sw.. thanks :)
Powered by vBulletin® Version 4.2.0 Copyright © 2026 vBulletin Solutions, Inc. All rights reserved.