ive read all the charging problems and battery full posts and..

[cjard]

..none of them really answered this question:

upgraded to 5.87, 3310, genolited bubble signal meter, genolited DEAD faid and MCU checksums, nfader fading leds.. have yet to ppmedit the fonts in, cause i screwed the phone with that flash last time..
still needed to quick set faid (is this normal, even after killing checksums?), reset sp locks, convert 3310-3315, reset full factory, quick set faid again.. etc etc
and eventually got the phone working pretty much okay..

but it wouldnt charge.. plugging the charger in, says battery full after a few seconds. check out netmon 20.. unplug charger, display -> xxxxx, plug charger in, InitC (initialise charge, check battery), FastC (fast charging), FullM (battery full going into maintenance mode) all in about 5 seconds..

I left it in FullM all night, to see if it would charge anyways. No luck.

Turned phone off, and plugged charger in. Appeears to be charging normally, and has been for last few hours. Turn on and check volts with NetMon 20.. its about 448, better than the 336 it was before when "full" ..

but is this the way it will have to be now? phone turned off to charge correctly?

has this happened to anyone else?

[LeeH]

Hi cjard,

I read some have had your prob; others not!

I have not tried charging mine yet as the battery is full!

Maybe it depends on the particular flash IC?

Also, I have searched the forums for the answer to my question and can not find any info.

What I would like to know with PLEASE to everyone, can somebody explain why it was necessary for me to correct the checksums first to flash,
after creating an *.fls file from separate Wintesla mcu and ppm?

Maybe you have the info to help me please, cjard?

Best regards,
Lee.

[cjard]

not sure what you mean.. to solve my charging problem , i reflashed with an earlier version... on 557 now, and still not happy with the dictionary.. its very dumb. might just be my phone.

also cant answer your question about checksums cos i dont understand it! necessary to calculate checksums when its flashed, because if the checksums are wrong, the phone wont go, incase it crashes, and just displays CONTACT SERVICE

[chunkhead]

Your Dictionary is "Dumb" because it is new! You have to "Teach it" your words again before it will get smarter! If you use Nfader, check the "KILL CS\FAID" Box! This will sort you out!!! This is better then G3nolite for Checksums\Faid!

[NokDoc]

Hi,

Just a remark here.

>> This is better then G3nolite for Checksums\Faid!

Nfader is based on G3nolite.

NokDoc

[LeeH]

Hi NokDoc,

Please help!

To simplify matters,
My question is why do I have to correct checksums when I have used an original file?

Best regards,
Lee.

[NokDoc]

Hi,

U not need to,
only on modified files.

I think the charging problem is not due to the DeadMcu/Faid.

NokDoc

[LeeH]

Thanks very much NokDoc!

I know this is usually NOT the case to need to correct checksums for original files.

I did not make myself clear, either. Sorry!

This only concerns NHM-5 3310/3315 v5.87 and what I did was to make an *.fls file from separate Wintesla mcu + ppm. I used Rolis v4.78b6 as I normally do without probs to make *.fls file.

There was an mcu check prob after creating this *.fls file and when I flashed I got Contact Service.

It was only after I corrected all checksums the new v5.87 worked when I flashed again!

Please, do you understand why this was necessary?


Also, another question please.

Does killing FAID / mcu check change anything in the eeprom area, i.e. does the eeprom remain as original afterwards?

Best regards,
Lee.

[NokDoc]

Hi,

Logical.

The last 3 versions of 3310/ 3315 I saw, had incorrect conversion done in wt2dejan.

Those files, have a 64K gap between the mcu and ppm.

If U fill the gap with all FF's, then the calcs should be ok.

I expect the Rolis conversion U did, used other values there.

Or maybe not filled with FF's but write the old values to that area.

That incorrect data will give U the incorrect mcu & flash checksum values then.

Hope U understand my idea.

Also, there is no effect on Ur eeprom area at all.

The concept of DeadMcu is, we let it calc it's own value, so result is always ok.

The concept of DeadFaid is, we predict the flashcheck calc outcome.

That value, together with Ur own phones identity values, will be used to calc and set the Faid later.

Sorry if I talk confusing.

NokDoc

[LeeH]

Thank you so very much NokDoc,

You are one of a few advanced enough to explain all of the info I wanted and both clearly and accurately.

You are most excellent, my friend ( excuse me, not that I know you personally! )

Best regards,
Lee.

[NokDoc]

Hi,

Ah, I just wrote what I saw on my tv, last Sunday morning...

Good Luck...

NokDoc