Firmware updating Dell 5811e with ancient firmware (SWI9X30C_00.08.02.00)


#1

I have a dell 5811e with ancient firmware, which I’ve been unable to firmware update. Its running this:

Revision: SWI9X30C_00.08.02.00 r1706 carmd-fwbuild4 2015/03/10 08:07:02

Although I can easily change its pid:vid to be generic, I’ve been unable to update to any firmware. I dont easily have access to a dell laptop, but I’m unsure of whether or not even that would work using the Dell firmware updater.

I’d appreciate any help on getting this running recent firmware.

Thanks in advance


#2

any luck with this? I am having the same issue.


#3

Pay now or pay later. I’ll just assume you , like me, got yours from Aliexpress. I’d bet yours doesn’t have any Regulatory labels either…

Check this post out, I was able to get mine working with it:

However, I could not get mine to flash automagically, and had to do it by hand, with the fdt/fdt2 exe inside the Sierra Tools directory.

In all of my experimenting, at the end, I have a strange impref setting, which tells me the config name is GENERIC_001.007_000, even though !priid says its GENERIC_002.021_000; I think this may be because I found an old Dell driver and managed to flash it completely (spk file), which got me from 00.08.02.00 to 01.08.07.00.

If the post doesn’t help, I can try to dig out my notes for you…


#4

eBay, but same issue. I didn’t even realize all the differences in this chip until after I got it.

you were able to get it updated though?

I tried this:

.\fdt2.exe -d 9x30 -f .\SWI9X30C_02.24.05.06.cwe SWI9X30C_02.24.05.06_GENERIC_002.026_000.nvu
FDT version: 1.0.1804.0
Awaiting suitable port or adapter ...
Switching to boot & hold mode ...
Disabling selective suspend ...
Awaiting DM port ...
Switching to boot & hold mode ...
Disabling selective suspend ...
Awaiting port removal ...
Awaiting download port ...
Downloading images ...
Writing image -
Flashing image \
Writing image |
Flashing image /
Awaiting adapter ...
Enabling selective suspend ...
Firmware download failed.
Primary error code: 82 - Failed in checking modem mode.
Secondary error code: 55 - Failed in closing unframed data write.
Device error code: 0x2 - Flash write failure.

Preexisting images information:
        Current:
                Firmware:
                        ImageId:
                        BuildId:
                Configuration:
                        ImageId:
                        BuildId:
Final images information:
        Current:
                Firmware:
                        ImageId:
                        BuildId:
                Configuration:
                        ImageId:
                        BuildId:

OEM PRI:

IMEI:

Total time elapsed: 282828 ms.

Time to switch to boot mode: 22610 ms.

Images downloaded:
        Image ID: ?_?
        Build ID: 02.24.05.06_?
                write time: 9562 ms
                additional flash time: 0 ms
        Image ID: 002.026_000
        Build ID: 02.24.05.06_GENERIC
                write time: 0 ms
                additional flash time: 0 ms

Time to reset to application mode: -1 ms.

not sure why it is failing though. Maybe I need an intermediate firmware version?


#5

Looks vaguely familiar.

You’ll need to find this driver on the Dell website
R9YXH_WN32_7.8.4376.507_A01

Use 7Zip to extract the DELL7455DriverSetup.exe file, and again 7Zip to extract that (I did this originally on linux, where I had funny directory names; if you do it on Windows, you only need to extract the directory thats named “7455”). Inside the 7455 directory, you will find SWI9X30C_01.08.07.00 and SWI9X30C_02.01.03.00. I think that I managed to flash 01.08.07.00 and the matching GENERIC PRI, and never bothered with the 02.01.03 version, and then went to 02.24.03, after rebranding (Note you have to use the older AT!UDPID and AT!UDVID to rebrand).

Its also not clear to me what the difference between the fdt and fdt2 binaries are. did you try both ? I think that I used fdt and not fdt2 (i got that hint from a Russian forum and google translate!)


#6

can you do me a favor?

What do you have set for all of these?

AT!UDVID?
AT!UDPID?
AT!UDUSBCOMP?
at!priid?

I was able to get the 01.08.07.00 files, but FDT2.exe is having the same issue. FDT.exe is having a different one, so I will continue to play with that.

Thanks so much for your feedback so far, I was worried I was up a creek.


#7

okay, I got it to 1.08.08.00!

It turns out, there are not only differences between fdt and fdt2 but there are actually 2 different fdt.exe files in that DELL7455DriverSetup

It would still be helpful to know that info from before when you get the chance. I am gonna go work to upgrade to the latest.

To anyone else having this issue, it is fixable! thank you to panachoi. I though I bricked this chip at least 4 different times (different behavior) including windows refusing to see it, but thankfully I used linux and was able to screen /dev/ttyUSB2 to pass AT commands and fix it.

Cheers

Edit: got it to 02.24.05.06 tonight. Thanks again.


#8

I’d be interested in actually seeing your output from:

at!impref?
AT!PRIID?
at!image?

I’m curious, because I got mine into a working state with SWI9X30C_02.24.03.00, after (like you) spending many hours (i.e. more than I would have paid for an original Sierra Module), but I have bizzare artifacts like this:

at!image?
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
FW 1 EMPTY 0 0 0
FW 2 EMPTY 0 0 0
FW 3 EMPTY 0 0 0
FW 4 EMPTY 0 0 0
Max FW images: 4
Active FW image is at slot 255

TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
PRI FF GOOD 0 0 0 002.021_000 02.24.03.00_GENERIC
Max PRI images: 50

Notice how there is no firmware (at least its reporting that) in any of the slots.

And this:

at!impref?
!IMPREF:
preferred fw version: 02.24.03.00
preferred carrier name: GENERIC
preferred config name: GENERIC_001.007_000
current fw version: 02.24.03.00
current carrier name: GENERIC
current config name: GENERIC_001.007_000

Notice the config names ? It says that, but its not true:

AT!PRIID?
PRI Part Number: 9904609
Revision: 002.021
Customer: GENERIC

Carrier PRI: 9999999_9904609_SWI9X30C_02.24.03.00_00_GENERIC_002.021_000

Note sure how/if the output from impref and priid are related…

If yours looks “normal”, I’m sure others might benefit of how exactly you got your module from the ancient version to the latest, with detailed steps…


#9

I don’t think mine is normal, but I am actually not sure what the consequences of having it screwed up are. I am able to use it in Windows as a LTE Modem just fine.

My actual goal is to be able to use AT commands in Linux to do some LTE reception scanning and that work fine as well.

at!impref?

!IMPREF:
 preferred image setting does not exist
 current fw version:      02.24.05.06
 current carrier name:
 current config name:

 fw version mismatch
 carrier name mismatch
 config name mismatch

AT!PRIID?

PRI Part Number: 9902812
Revision: 01.07
Customer: GENERIC

Carrier PRI: 9999999_9904609_SWI9X30C_02.24.05.06_00_GENERIC_002.026_000

at!image?

TYPE SLOT STATUS LRU FAILURES UNIQUE_ID   BUILD_ID
FW   1    EMPTY  0   0 0
FW   2    EMPTY  0   0 0
FW   3    EMPTY  0   0 0
FW   4    EMPTY  0   0 0
Max FW images: 4
Active FW image is at slot 255

TYPE SLOT STATUS LRU FAILURES UNIQUE_ID   BUILD_ID
PRI  FF   GOOD   0   0 0      002.026_000 02.24.05.06_GENERIC
Max PRI images: 50

Do you have the GPS working on yours? I have mine in an external case with 2 antenna, one attached to main, and I’ve tried the other on both GPS and AUX, but it never gets a GPS lock…any suggestions?


#10

Are you sure that its actually working ? I’m pretty sure it doesn’t work in this state, as it will remain in low-power mode, and not actually power up the modem; this may be the reason you have no GPS

What does the output of at!pcinfo? say ? It should look like this:

at!pcinfo?
State: Online
LPM voters - Temp:0, Volt:0, User:0, W_DISABLE:0, IMSWITCH:0, BIOS:0, LWM2M:0, 0
LPM persistence - None

If it doesn’t, the modem is not actually operational (did you make an LTE connection under windows ?)

But I guess its “good” that yours too, doesn’t show any firmware in any of the slots, although, similar to mine.

A “genuine” 7455 looks like this (this is the mPCIe version of the 7455):

AT!PRIID?
PRI Part Number: 9904514
Revision: 001.006
Customer: Generic-M2M

Carrier PRI: 9999999_9904609_SWI9X30C_02.24.03.00_00_GENERIC_002.021_000

OK
at!image?
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
FW 1 GOOD 1 0 0 ?? 02.24.03.00?
FW 2 EMPTY 0 0 0
FW 3 EMPTY 0 0 0
FW 4 EMPTY 0 0 0
Max FW images: 4
Active FW image is at slot 1

TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
PRI FF GOOD 0 0 0 002.021_000 02.24.03.00_GENERIC
Max PRI images: 50

My guess is that these are all very early engineering samples, hence they are missing all of the regulartory approval IDs, etc, and come with a 00.xx firmware.

Once you get it out of LPM, the GPS should work just fine. My works without anything connected to the GPS antenna connector (I also have mine in a USB to M.2 adapter, all metal)