Quote:
Originally Posted by Advance-Box  It is the ENO,
From this file right here:
Processing Image File :
C:\Program Files\Nokia\Phoenix\Products\RM-505\RM505_APE_ONLY_ENO_09w23_v0.072.fpsx
CMT Type : BB5
CMT Algorithm : XSR 1.5
Secondary Sending Speed : 650000 Hz
Algorithm Sending Speed : 6500000 Hz
Program Sending Speed : 6500000 Hz
Message Reading Speed : 98000 Hz
Number of Blocks : 16
Entry Point : 0x0136
Page Format : 128K
Maximum Page Size : 0x00040000
ENO for N97 RM-505 lives in this address:
NAND_OFFSET: 0x00400000 ~ 0x007FFFFF
This address is ERASED by the MCU File, and is Erased again by the ENO File...
SO if you flash your phone without ENO FILE, then the MCU fill will just erase it and
it will be left BLANK and EMPTY. And so you will get missing APE TEST in scan phone
and your phone will never Boot into Normal mode at all.
You can check the first batch of files which you used, if they have a similar file
for ENO or not.
Some ENO files are also not compatible with certain MCU version or Phone.
So even if the RM-xxx is correct, it will still not work (Sometimes). You will
usually see this in E52 RM-689, and 1-2 years ago many people had this problem.
THe solution is just to search for an ENO File that will work with the phone,
In your case, you just used the one from the original Product Code, which fixed
the phone.
B.R. |
I have been flashing ENO files on several phones, however this is the first time I have so much knowledge abt it. This forum lacks this sort of knowledge, I wish you would make a thread explaining stuff like this as many ppl dont know how to read logs. they just want their phones flashed and not know what went wrong. I am one of those who like to get real knowledge rather then asking the same question again and again.
If you could make a thread with a knowledge base of stuff like this would be great.
thanks again
Br
frenzy