Mib2 bootloop

[KJW13]

hello
I have a problem with my MIB2 High device.
Upgrading to MHI2_ER_SKG13_P4526 (MU: 1440) was successful.
I cleared the software installation error.
In the first installation attempt after inserting the SD card with the latest M.I.B and IFS-stage2 build, the device started the update automatically and completed it successfully. In the service mode, the green menu appeared, but there was no M.I.B tab.
I cleared the software installation error.
I made the second installation attempt through the update installation options. After successful completion, the M.I.B tab appeared in the green menu. I made a large backup.
The next day the device greeted me with a bootloop. Logo, sometimes menu view and reboot after 60s
Using D-Link USB-Ethernet and PuTTY in RCC mode, it does not connect to the device.
In MMX mode, I can login but "rm /mnt/efs-persist/FEC/mmx_fec_ids.bin" returns a missing file or folder error.
Is there a chance to save the device? What else can I do myself?
Regards
Krzysztof

[harman-f]

Let us start with your log file.

[KJW13]

MU1440-JTB-07411.12.171190067A.log

[KJW13]

Regards Krzysztof

[harman-f]

search File MU1440-ifs-root-part2-0x00ba0000-1C06F300.ifs

[flashlock] unlocking flash: DONEFlashing on OFFSET 0x00ba0000...
Label: PL_qnx_flashit_10495A QNX: RL_qnx_650_10494A Built: 2010/12/10_11-21-47_UTC
/net/rcc/dev/fs0
--------
Flash size: 0x04000000 [= 512 x 0x20000]
Base addr:  0x00ba0000
File size:  0x00f30628 (15926824)
End addr:   0x01ad0628
*** erasing:     0x00BA0000 .. 0x01AD0627 [01ADFFFF] .......................................................................................................................... 
*** programming: 0x00BA0000 .. 0x01AD0627            .........................................................................................

As visible in log file your flash process was interrupted before it finished.

RCC is now in a "bad" state. Quite unpredictable, depending on the missing files.
If connected via MMX, can you access /net/rcc/dev/fs0 ?

If not, you can use method to mount it:
https://mibwiki.one/doc/mount-rcc-fs0-6zJlPOu7Ml
Afterwards you can manually flash RCC.

Of course, as you only have 60s all this has to be quick ;)
You will have to change flashit parameters to ignore delete and verify.
To make flashing of ifs-root-stage2 possible in that short time frame.

[KJW13]

Thank you for your help.
The file fs0 is indeed not in the given path.
Unfortunately, I don't know how to perform the process you described in one go in 60s including restoring the fs0 files beforehand.
He doesn't want to make the problem worse by not following the instructions properly. Is there any guide to do it properly? If not, can you write me step by step how to do it?
Regards
Krzysztof

[harman-f]

as long as only ifs-root-stage 2 is written, there is no chance to make it worse ;)

1. Mount fs0 as mentioned on mibwiki
2. prepare binaries flashunlock/flashit/flashlock on SD card, as the once on unit are part of ifs-stage2 and most likely not working
3. flash ifs-root-stage2 (can be the patched one) directly to unit:

touch net/mmx/var/sm_disable_wd

on -f rcc /usr/bin/stop_efs_driver.sh
on -f rcc /sbin/devf-generic -s0x08000000,64M,,,128k,2,1 -r -D -P 1

mount -uw /net/mmx/fs/sda0
cd /net/mmx/fs/sda0
on -f rcc /net/mmx/fs/sda0/flashunlock
on -f rcc /net/mmx/fs/sda0/flashit -a 0x00ba0000 -d -f /net/mmx/fs/sda0/MU1440-ifs-root-part2-0x00ba0000-1C06F300.ifs
on -f rcc /net/mmx/fs/sda0/flashlock

[KJW13]

Thanks again for your help

The process didn't complete properly, but the device is working. I haven't checked all its features yet. Could the missing file (stop_efs_driver.sh) during resuscitation cause a problem?

Regards
Krzysztof

[harman-f]

Should all be finde now ;)
Great, that this worked