Discover Pro (MIB2.5) Stuck on boot splash screen

[leifalbor]

So I installed mib2-toolbox this afternoon. While checking out the settings it has available I must have done something wrong as my Discover Pro (MIB2.5) is now stuck on the boot splash screen.

The big problem is because I can't access any of the device menus I can't get back into the green developer menu to undo what I've done, nor can I enter the service menu to reflash firmware and overwrite back to factory default.

Any suggestions on what I can do here please?

[kamold]

Buy yourself a bench harness and the appropriate TTL to USB adapter and access the device over the debug pins so you can restore your backup from sdcard that you took before attempting to modify anything.

[leifalbor]

Hey Kamold - thanks for the response. Sorry but the instructions are a bit vague. Happy to listen and follow instructions from those more learned than me, but I'm far from an expert �� What is it exactly you're instructing me to do?

[kamold]

You need to build/buy a harness to power the unit on whilst on the bench. Connect a serial adapter to the debug pins on the back of the unit and then access it over telnet. Then you can use the command line to restore the files you backed up before modifying the unit.
If you didn't back anything up then best bet is force it into emergency SWDL mode and reload the current firmware version to overwrite whatever it is you broke.

[leifalbor]

Ah now I'm with you! Thanks. I know that MIB2-toolbox's dev jilleb states over on his github that you can telnet in using a D-Link Dub-E100 usb to ethernet adapter - so that would would be much more preferable to pulling the whole thing out.

Do you have any information on how to force SWDL mode? I'm happy to wipe everything back to factory default if its the easiest solution.

[kamold]

If you can find one of the Dlink adapters. They have been out of production for a while.
To get it into emergency SWDL mode you need to have the unit on the bench. Need to short the debug RX pin to ground for 5000ms at boot and then return it back to the serial connection you will have the recovery menu.

[leifalbor]

Hey kamold - Again, thanks for your help on this. Just wondering do you know of any more comprehensive guides for entering and using SWDL mode via serial/telnet? Google doesn't seem to come up with anything, and to be honest I'm not even sure which pins are which that I need to connect the USB to TTL to.

Thanks again!

[leifalbor]

Replaced with new comment below.

[leifalbor]

Another update.

Thankfully I've been able to set everything up with the MMX head unit sitting in my glove box still wired into the car - so haven't had to set up a test jig on a benchtop. I'm up and running with terminal via PuTTY.

Dr Google found me documentation showing the location of TX and RX serial debug pins -> MIB2 High - Nvidia - Recovery ifs-root.uifs via bench access - PDFCOFFEE.COM

Two things of note: It seems there's two sets of TX/RX pins. One shown as MMX and one shown as RCC. Which ones am am I supposed to use?

Second thing of note - these instructions show how to flash an IFS file. The firmware file I have is the usual one with the metainfo2.txt file and a heap of folders. Does anyone have instructions on how to flash that?

[leifalbor]

Duplicate post

[kamold]

I've been away on holiday.
I'll send you some docs via email.

[leifalbor]

Just to provide a resolution in this thread...

Huge thankyou to kamold and his efforts and numerous answers via email in trying to get the issue resolved.

Eventually I got it fixed today with the help of a user who contacted me via my post on jilleb's (MIB2 Toolbox's dev) github. We were about to re set the skin using long coding through the serial terminal interface into emergency boot mood.

[wachu153]

Just to provide a resolution in this thread...

Huge thankyou to kamold and his efforts and numerous answers via email in trying to get the issue resolved.

Eventually I got it fixed today with the help of a user who contacted me via my post on jilleb's (MIB2 Toolbox's dev) github. We were about to re set the skin using long coding through the serial terminal interface into emergency boot mood.

Can you provide me with information you got? I am in the same situation. I changed skin and I can see starting logo only.

[DV52]

@wachu153: Hmm....... if your problem has resulted from coding changes and you have used a diagnostic device like OBD11, or VCDS - the software will contain a record of the details of the tweak.

So, a way of often (and easily) fixing this problem is to simply revert the coding change the caused the fault back-to the original setting!

As I say, you already have the necessary data for this fix if you have used a good diagnostic device - why not try?

Don