Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to patch MIB 2.5 due to header seize wrong #581

Open
Honeybadger-22 opened this issue Nov 8, 2024 · 0 comments
Open

Not able to patch MIB 2.5 due to header seize wrong #581

Honeybadger-22 opened this issue Nov 8, 2024 · 0 comments

Comments

@Honeybadger-22
Copy link

Is this just a typo in the patchfile i got from mibsolution or is it really a different one? If so, does anyone know where I can find the correct patch?

GEM info........ -> done :-)
Folder lists..... -> done :-)
FEC folders...... -> done :-)
HMI folders...... -> done :-)
Shadow files..... -> done :-)
lsd.jxe.......... -> done :-)
Dataset's........ -> done :-)
EEPROM...........

timestamp: 1970_01_01_00_02_42
-> done :-)
storage1......... -> done :-)
storage2......... -> done :-)
RCC Flashlock.... -> done :-)
RCC.............. -> done :-)
MMX.............. -> done :-)
IFS-stage2.......4512+0 records in
4512+0 records out
-> done :-)
OFFSET's......... -> done :-)
backing up backup -> Backup part 1 is already there! -> Backup part 2 is already there!

ls -als /net/mmx/mnt/boardbook --> total 192
64 drwxrwxrwx 3 root root 32768 Jan 01 00:03 .
64 drwxrwxr-x 5 root root 32768 Jan 01 00:03 ..
64 drwxrwxrwx 3 root root 32768 Jan 01 00:08 MU1367
Free space on /net/mmx/mnt/boardbook 376M

OK: Patch folder /net/mmx/fs/sda0/patches/MHI2_ER_VWG13_K4525_MU1367_PATCH found on SD card

File MU1367-ifs-root-part2-0x00ba0000-5404F300.ifs found in patch folder
File MU1367-ifs-root-part2-0x00ba0000-5C04F300.ifs nedded to patch this unit
Header seize on unit - 5C04F300 - does not match patch files seize - 6004F300 - or stock - 5404F300 - image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant