0613e34637 6.Mysterious system pops- up. Retrieved from Categories: SoftwareTemplates . So what can we use to prevent that, and make sure our dumps are as proper as we can check? Visual inspection HxD - hexeditor Open up the flashdump (make it unified first if it is still 2 seperate NAND dumps) with a hexeditor (e.g. So are you still looking for solutions to fix this error on your computer? Trust me, the best method is to enable a reliable flowrebuilder v.4.2.2.0.exe error fixer on your computer. -> bugreport -> Fixed in FlowRebuilder v.4.2.2.0 From unified to seperate low/high NAND files If for some reason you lose the original seperate low/high NAND files and only have the unified, you need donor files to regenerate them. You can this error manually, but the manual process might be difficult and only recommended to the expert users. 5.Browser crashes. If not, the one on your computer must be mistakenly removed by yourself or other virus attacks. The presence of this dangerous Trojan is a serious threat for the system security, status and performance. It will be extremely dangerous that remote hacker can control your PC and steal whatever important data stored in the system some day without any notification.
0x10 in dump with hexeditor is in reality 0x8 on the address bus because we read 2 bytes at once so the address is no longer 0x10000 but 0x8000 0x8000 (hexadecimal = base 16) = 1000 0000 0000 0000 (binary = base 2) which means the 16th bit = 1, we start counting at A0, so the 16th is A15 conclusion: A15 is bad Quick lookup table repetition addressline 'stuck' 0x2 A0 0x4 A1 0x8 A2 0x10 A3 0x20 A4 0x40 A5 0x80 A6 0x100 A7 0x200 A8 0x400 A9 0x800 A10 0x1000 A11 0x2000 A12 0x4000 A13 0x8000 A14 0x10000 A15 0x20000 A16 0x40000 A17 0x80000 A18 0x100000 A19 0x200000 A20 0x400000 A21 0x800000 A22 0x1000000 A23 0x2000000 A24 0x4000000 A25 0x8000000 A26 0x10000000 A27 0x20000000 A28 0x40000000 A29 0x80000000 A30 Check metldr bootldr sizes If they are even missing or bad, its a sure road to permabrick You can check metldr and bootldr sizes easily with HxD either after extracting flash with Flowrebuilder and opening seperate files or by looking in the unextracted Flash dump at the correct offset. And best of all. This table lists some common known values for your convenience as quick lookup: IDPS/TargetID SKU - Datecode / Manufacturing date metldr offset bootldr Notes lowverchk 0x2F077(NOR)0x80877(NAND) 0x81E(NOR)0x4081E(NAND) 0x842(NOR)0x40842(NAND) size 0xFC0002(NOR)0x0(NAND) 0xFC0012(NOR)0x12(NAND) 0103 CECHAxx (COK-001) with 1.00fromfactoryCECHCxx (COK-002) ED A0 0E D6 - - - incomplete dump 0104 CECHAxx (COK-001)CECHExx (COK-002) EE 10 0E DD 2A430 2A 3F 2A 3F OK 0102 DECHAxx (COK-001)CECHBxx (COK-001) ED A0 0E D6 2A2E0 2A 2A 2A 2A OK 1.00 03 CECHCxx (COK-002) with 1.00fromfactory EB F0 0E BB 30480 30 44 30 44 OK 1.00 0103 CECHAxx (COK-001)CECHCxx (COK-002) ED E0 0E DA 2A3B0 2A 37 2A 37 OK 1.00 05 CECHGxx (SEM-001) E7 B0 0E 77 2E900 2E 8C 2E 8C OK 1.90 0506 CECHGxx (SEM-001)CECHHxx (DIA-001) E7 B0 0E 77 2F200 2F 1C 2F 1C OK 2.30 0506 CECHGxx (SEM-001)CECHHxx (DIA-001) E8 C0 0E 88 2EF80 2E F4 2E F4 OK 2.30 06 CECHHxx (DIA-001) E8 E0 0E 8A 2EF80 2E F4 2E F4 OK 1.97 06 CECHMxx (DIA-001) EA 60 0E A2 2EE70 2E E3 2E E3 OK 1.97 07 CECHJxx (DIA-002)CECHKxx (DIA-002) datecode 8C EA 60 0E A2 2EE70 2E E3 2E E3 OK 2.30 08 CECHLxx / CECHPxx (VER-001) E8 D0 0E 89 2EAF0 2E AB 2E AB OK 2.45 08 CECHLxx (VER-001) E8 D0 0E 89 2EB70 2E B3 2E B3 OK 2.45 0809 CECHLxx (VER-001) with 2.30 from factory - datecode unknownCECH-20xx (DYN-001) with 2.76 from factory E8 90 0E 85 2F170 2F 13 2F 13 OK 2.70 09 CECH-20xx (DYN-001) E9 20 0E 8E 2F3F0 2F 3B 2F 3B OK 2.70 0A CECH-21xx (SUR-001) E9 20 0E 8E 2F4F0 2F 4B 2F 4B OK 3.20 030B0B CECHExx (COK-002W) refurbishedCECH-25xx (JTP-001) with 3.40 from factory - datecode OCCECH-25xx (JSD-001) with 3.41 from factory - datecode OC E9 20 0E 8E 2F4F0 2F 4B 2F 4B OK 3.40 0B CECH-25xx (JSD-001) with 3.56 from factory - datecode 0DCECH-25xx (JTP-001) with 3.56 from factory - datecode 1A E9 60 0E 92 2F570 2F 53 2F 53 OK 3.50 0B CECH-25xx (JTP-001) with 3.56fromfactory - datecode1B E9 60 0E 92 2F5F0 2F 5B 2F 5B (RLOD )poweroffdowngrade355 3.56 0B0B0C CECH-25xx (JSD-001) with 3.60fromfactory - datecode1BCECH-25xx (JTP-001) with 3.60fromfactory - datecode[N.A.]CECH-30xx (KTE-001) with 3.65fromfactory - datecode[N.A.] F9 20 0F 8E 2FFF0 2F FB 2F FB "metldr.2"(RLOD )poweroffdowngrade355 3.60 0D CECH-40xx - - - - - (RLOD )poweroffdowngrade355 ?4.10? Flowrebuilder Flow Rebuilder Links to versions FlowRebuilder v.4.2.2.0.exe (389 KB) // mirror FlowRebuilder v.4.2.1.2.exe (313.50 KB) // mirror FlowRebuilder v.4.2.1.1.exe (473.57 KB) // mirror FlowRebuilder v.4.2.0.1.exe (474.01 KB) // mirror FlowRebuilder v.4.1.3.2.exe (459.95 KB) // mirror FlowRebuilder v.4.1.0.0.exe (454.85 KB) // mirror (don't use, for historic reasons listed) Flowrebuilder options (NAND only) UNSCRAMBLE then interleave two NAND flashes into one unified dump - (4.1.0.0 and higher): Makes a unified dump.bin from 2 seperate NAND flash dumps. In the second step it also extract the content of the unified dump. Byte reverse and EXTRACT a NOR dump file - (4.1.0.0 and higher): First byte reverse the single dump.bin then extract NOR content. Just check the folder: C:windowssystem32 to check whether it is there. To sum, it is extremely important that you fix flowrebuilder v.4.2.2.0.exe error as early as you can to avoid future damages to the computer. NAND0-1.rar extract and in Flowrebuilder select the option "RE-SCRAMBLE a modified dump then de-interleave it into two new flashes" Select the NAND backup "Flash 0" (TOP) file: here drop the 1bkp.bin Select the NAND backup "Flash 1" (BOTTOM) file: here drop the 2bkp.bin Select the Input NAND interleaved Modified file: here drop your unified flash .bin file and click Execute Operation This will result in making 2 new deinterleaved files you could use for reflashing (it is recommended to alway use your own deinterleaved sourcedumps, this method is only mentioned as last resort for people that lost their backups). If you are getting the error message immediately after installing a new program on your computer, just uninstall it.
Cateell replied
464 weeks ago