Wireless Joint

Posted: **Thu Jan 30, 2020 1:58 pm**

I have a mofi sim 4 and have built two of the we826/mc7455 without issue. This is the 3rd one i've built and they dont seem to be playing nice. I ordered the router from The Wireless Haven and the modem from Aliexpress. My other builds I bought everything from Aliexpress.

Anyway, it seems like the modem is sort of being recognized by the WE826, but not fully connecting to it. This is what I see under device information

Code: Select all

T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 1	
B: Alloc= 0/800 us ( 0%), #Int= 1, #Iso= 0	
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1	
P: Vendor=1d6b ProdID=0002 Rev= 4.14	
S: Manufacturer=Linux 4.14.63 ehci_hcd	
S: Product=EHCI Host Controller	
S: SerialNumber=101c0000.ehci	
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA	
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub	
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms	
********************************************************************************************************	
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 4	
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1	
P: Vendor=05e3 ProdID=0608 Rev=85.37	
S: Product=USB2.0 Hub	
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA	
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub	
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=256ms	
********************************************************************************************************	
T: Bus=01 Lev=02 Prnt=02 Port=02 Cnt=01 Dev#= 3 Spd=480 MxCh= 0	
D: Ver= 2.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1	
P: Vendor=1199 ProdID=9071 Rev= 0.06	
S: Manufacturer=Sierra Wireless, Incorporated	
S: Product=MC7455	
C:* #Ifs= 5 Cfg#= 1 Atr=a0 MxPwr=500mA	
A: FirstIf#=12 IfCount= 2 Cls=02(comm.) Sub=0e Prot=00	
I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=qcserial	
E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms	
E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms	
I:* If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=qcserial	
E: Ad=83(I) Atr=03(Int.) MxPS= 10 Ivl=32ms	
E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms	
E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms	
I:* If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=qcserial	
E: Ad=85(I) Atr=03(Int.) MxPS= 10 Ivl=32ms	
E: Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms	
E: Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms	
I:* If#=12 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=0e Prot=00 Driver=cdc_mbim	
E: Ad=87(I) Atr=03(Int.) MxPS= 64 Ivl=32ms	
I: If#=13 Alt= 0 #EPs= 0 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim	
I:* If#=13 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim	
E: Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms	
E: Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms	
********************************************************************************************************	
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 1	
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0	
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1	
P: Vendor=1d6b ProdID=0001 Rev= 4.14	
S: Manufacturer=Linux 4.14.63 ohci_hcd	
S: Product=Generic Platform OHCI controller	
S: SerialNumber=101c1000.ohci	
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA	
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub	
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms

Under general Information I see:
Modem : Sierra_Wireless,_Incorporated MC7455
Modem 1
Modem ID :
1199 : 9071

Provider :
Connecting

Comm Port :
/dev/ttyUSB2

if you see under provider it says "connecting" yet never connects
I have the correct "broadband" APN for ATT, and the sim card works in my Mofi just fine.

Under misc modem features it says modem present/not connected.
When I enter the AT command: at!entercnd="A710"
it says TIMEOUT ERROR. I also see nothing but timeouts in the debug area for USB2.

See relevant screenshots. https://imgur.com/a/tuXRgvE

I'm suspecting that maybe the modem does not have a generic firmware, I think I have a USB to PCIe adapter so I might attempt flashing the generic firmware with my computer. But before I do that, does anyone have any other suggestions as to what could be going on? I first tried the WIFIX firmware on the 826 and then switched to the previous Goldenorb that was working on my other builds. The issues persist in both firmwares. Thanks in advance for any suggestions.

Posted: **Thu Jan 30, 2020 2:42 pm**

So as a test I decided to pull apart my cradlepoint CBA 750 / mc400 modem. (uses a Sierra 7354) I installed the latest windows driver package (same driver package is used for both the 7354 and the 7455) and plugged it into the computer and everything is recognized / working. This same process should work with the 7455. I guess my next question.. is there any way to see what firmware is installed on the modem within windows? I'm not familiar with flashing the sierra firmware is there a good resource I can refer to?

EDIT: I see two generic firmwares for the 7455, release 26 and release 27 which should be used? Screenshot: https://imgur.com/a/inGuHcl

EDIT 2: I found this document that I plan to look into as the possible cause/solution to my issues with the MC7455 although the doc is refering to an EM7455. https://docs.google.com/document/d/1IO- ... 9G5Wg6Ti6c
Edit 3:- I moved the card into the mc400 usb adapter and checked under device manager and it shows the com ports and modem, so this document doesn't seem to apply. Will try flashing the release 27 firmware and see how that goes. I also see in windows device manager that it shows the yellow alert icon under network adapters and says " Generic Mobile broadband adapter" - https://imgur.com/a/vX634KX

Posted: **Thu Jan 30, 2020 3:18 pm**

It is seeing the modem, so that is a good sign.

I would reset the modem to OEM, and then flash the MC7455 with latest Generic firmware (GN2) and then flash it a second time.

Posted: **Thu Jan 30, 2020 3:25 pm**

JimHelms wrote: ↑Thu Jan 30, 2020 3:18 pm It is seeing the modem, so that is a good sign.

I would reset the modem to OEM, and then flash the MC7455 with latest Generic firmware (GN2) and then flash it a second time.

Thank you for the reply, how do I reset the modem to OEM? I will search in the meantime. I will use the files you linked.

Posted: **Thu Jan 30, 2020 3:29 pm**

BrentV wrote: ↑Thu Jan 30, 2020 3:25 pm Thank you for the reply, how do I reset the modem to OEM?

Run this AT Command:

Code: Select all

at!entercnd="A710";!RMARESET=1

Then, when it acknowledges the files have been restored/updated/deleted, issue the command to reboot the modem:

Code: Select all

AT!RESET

Posted: **Thu Jan 30, 2020 3:32 pm**

JimHelms wrote: ↑Thu Jan 30, 2020 3:29 pm Run this AT Command:
Code: Select all
at!entercnd="A710";!RMARESET=1
Then, when it acknowledges the files have been restored/updated/deleted, issue the command to reboot the modem:
Code: Select all
AT!RESET

I won't be able to issue these commands from the WE826 the first AT command always times out. I now have the modem connected to my windows 10 machine is there a way to issue the commands from here, or should I skip to flashing the firmware?

Posted: **Thu Jan 30, 2020 3:35 pm**

BrentV wrote: ↑Thu Jan 30, 2020 3:32 pm I won't be able to issue these commands from the WE826 the first AT command always times out. I now have the modem connected to my windows 10 machine is there a way to issue the commands from here, or should I skip to flashing the firmware?

You can use the Huawei Terminal.

Posted: **Thu Jan 30, 2020 3:38 pm**

JimHelms wrote: ↑Thu Jan 30, 2020 3:35 pm You can use the Huawei Terminal.

I'm so sorry for all the hand holding you have to do lol. Which com do I connect to? https://imgur.com/a/3YZzZKN

Annotation 2020-01-30 154353.png

Posted: **Thu Jan 30, 2020 3:38 pm**

You will also need to first install the Sierra Wireless software drivers for Windows.

When using the Huawei Terminal, connect to the WAN Modem port to issue AT Commands.

Posted: **Thu Jan 30, 2020 3:39 pm**

BrentV wrote: ↑Thu Jan 30, 2020 3:38 pm I'm so sorry for all the hand holding you have to do lol. Which com do I connect to? https://imgur.com/a/3YZzZKN

Please upload any images. That way they are around for others to reference.

Posted: **Thu Jan 30, 2020 4:24 pm**

JimHelms wrote: ↑Thu Jan 30, 2020 3:38 pm You will also need to first install the Sierra Wireless software drivers for Windows.

When using the Huawei Terminal, connect to the WAN Modem port to issue AT Commands.

I dont know whats going on. Both Huawei terminal and Putty are giving me issues. Huawei usually just freezes after i enter my first command. Putty usually wont let me type, although at one point I was able to enter the first command and it said "ok" but after that I couldn't enter any other commands. So I closed it out and tried again but this time after the first command it says ERROR. I then switched to Huawei again and this time it didnt freeze but the first command also said error so I went to the next command and it never gave a reply. Then Issued the reset command and it said ok. I tried to start all over, with combinations of rebooting my computer, removing the modem and reinstalling and every other combination I could think of. Next i'm going to try a different usb port, But for now I have to run some errands.

Posted: **Thu Jan 30, 2020 4:30 pm**

How much time did you give the modem to reset to OEM after entering the code? It takes a minute for it to work. If it does not return anything within a minute, enter the code a second time. Then, just give it a few.

Posted: **Thu Jan 30, 2020 4:32 pm**

You might also want to try updating the Generic firmware. Twice.

Then reset it to OEM. Then, if it takes, flash the Generic again, twice.

Posted: **Thu Jan 30, 2020 4:32 pm**

Well I seem to have sort of made progress. I ran Huawei Terminal as Admin and was able to issue the following commands.

ATI (it then sent me a bunch of information on the modem)
at!entercnd="A710" (it said "OK")
!RMARESET=1 (i've been sitting here for 3 mins waiting on a response.)

Annotation 2020-01-30 16182212.png

Posted: **Thu Jan 30, 2020 4:34 pm**

BrentV wrote: ↑Thu Jan 30, 2020 4:32 pm Well I seem to have sort of made progress. I ran Huawei Terminal as Admin and was able to issue the following commands.

ATI (it then sent me a bunch of information on the modem)
at!entercnd="A710" (it said "OK")
!RMARESET=1 (i've been sitting here for 3 mins waiting on a response.)
Annotation 2020-01-30 16182212.png

THe code I posted needs to be run together as a single line of code.

Posted: **Thu Jan 30, 2020 4:36 pm**

If you are going to run it as two commands, then it takes:

Code: Select all

at!entercnd="A710"
AT!RMARESET=1

Posted: **Thu Jan 30, 2020 4:39 pm**

JimHelms wrote: ↑Thu Jan 30, 2020 4:36 pm If you are going to run it as two commands, then it takes:
Code: Select all
at!entercnd="A710"
AT!RMARESET=1

Ah, well I feel foolish then. Seems to have worked. I think? Do I need to be concerned with that "recieved: ERROR" or is that just because it needed the reset command sent? If all looks good I proceed with firmware update . Thank you

Annotation 2020-01-30 16182213.png

Posted: **Thu Jan 30, 2020 4:41 pm**

Something is going on with your modem. It seems not to have restored, or deleted any configurations, and you have an Error.

Maybe your firmware update will fix it.

Posted: **Thu Jan 30, 2020 4:42 pm**

JimHelms wrote: ↑Thu Jan 30, 2020 4:41 pm Something is going on with your modem. It seems not to have restored, or deleted any configurations, and you have an Error.

Maybe your firmware update will fix it.

Yeah I was just looking at that and updating my above comment.

Posted: **Thu Jan 30, 2020 4:52 pm**

Well the update seems like its not working either.

Posted: **Thu Jan 30, 2020 5:11 pm**

Unplug your modem.

Plug it back in.

Run the Sierra Wireless software for Windows again.

Let it set for a few minutes to load all three COM ports.

Posted: **Fri Jan 31, 2020 8:29 am**

JimHelms wrote: ↑Thu Jan 30, 2020 5:11 pm Unplug your modem.

Plug it back in.

Run the Sierra Wireless software for Windows again.

Let it set for a few minutes to load all three COM ports.

I finally just switched to a different computer and made more progress. This computer actually shows 7455 in device manager instead of generic mobile modem with a yellow alert. I started over with the Huawei terminal and entered the commands but still showed 0 items restored or deleted. So then I ran the firmware update and it worked, I let it settle then ran it again but it didnt seem to work properly the second time, so I tried a 3rd time and still didnt seem to work. I decided to switch back to the Huawei terminal and enter the codes again and still no items deleted or restored. After which I ran the firmware update twice more, one of them seemingly maybe worked? but having mixed results when running it. When I run the ATI command it shows the new firmware is installed. So I guess from here maybe ill just try it back in the WE826. I dont know if theres something buggy with this modem or whats going on, since Ive never had to do any of this before I dont have any previous examples to compare to, however it doesnt seem to have quite the expected results just based on your comments and other threads i've read.

Annotation 2020-01-31 080121.png

Annotation 2020-01-31 080301.png

Annotation 2020-01-31 081849.png

Posted: **Fri Jan 31, 2020 9:00 am**

I usually see this happen on updating the firmware when all the COM port drivers have not had time to load. Try unplugging the modem, and wait a few seconds and plug it back in.

then, just forget about it for 10 minutes or so, then try flashing it again.

Also, it never hurts to reload the Sierra software for Windows again.

Posted: **Fri Jan 31, 2020 12:05 pm**

JimHelms wrote: ↑Fri Jan 31, 2020 9:00 am I usually see this happen on updating the firmware when all the COM port drivers have not had time to load. Try unplugging the modem, and wait a few seconds and plug it back in.

then, just forget about it for 10 minutes or so, then try flashing it again.

Also, it never hurts to reload the Sierra software for Windows again.

I gave that a try multiple times, usually when I run the firmware updater it says awaiting adapter and then resetting and then it just closes out. It seems to have updated the firmware at least once, I cant remember if I ever saw any other successful updates, but everytime I do the OEM reset it gives me the ERROR and says item restored and deleted 0. I put it in the we826 again and it only ever shows "connecting" never connected. I also tried running the AT commands in there and same result.

Annotation 2020-01-31 112541.png

Annotation 2020-01-31 113718.png

Annotation 2020-01-31 112653.png

Posted: **Fri Jan 31, 2020 12:46 pm**

What does the AT!GSTATUS? show while it is trying to connect.

Posted: **Fri Jan 31, 2020 12:55 pm**

JimHelms wrote: ↑Fri Jan 31, 2020 12:46 pm What does the AT!GSTATUS? show while it is trying to connect.

Well ive moved it back into the computer to try and make headway, but I ran the command from Huawei and I get the following.

AT!gstatus 2020-01-31 125120.png

And here's what happens when I run the firmware update

resetting adapter 2020-01-31 125120.png

Posted: **Fri Jan 31, 2020 1:01 pm**

As long as it is in low power mode, it will never connect.

You are going to have to get the modem to take a good flash, or return it and get another.

Posted: **Fri Jan 31, 2020 1:09 pm**

JimHelms wrote: ↑Fri Jan 31, 2020 1:01 pmAs long as it is in low power mode, it will never connect.

You are going to have to get the modem to take a good flash, or return it and get another.

Alright, I'll keep trying for now. DOes this mean anything to you?

config missmatch 2020-01-31 130741.png

Posted: **Fri Jan 31, 2020 1:40 pm**

It seems to be flashing the firmware.... Ive managed to switch to the ATT firmware from the generic. And I was quick enough to catch a screenshot of the flash before it closed the window. However it still says LPM and it shows that carrier miss-match name -Not sure what to think of that.

ATT flash screen 2020-01-31 133253.png

ATT flash 2020-01-31 133253.png

Posted: **Fri Jan 31, 2020 1:42 pm**

Now try to flash with Generic and see what happens.

Posted: **Fri Jan 31, 2020 1:50 pm**

JimHelms wrote: ↑Fri Jan 31, 2020 1:42 pm Now try to flash with Generic and see what happens.

I guess it flashed?

Generic flash 2020-01-31 134950.png

Posted: **Fri Jan 31, 2020 1:54 pm**

I flashed the generic twice and then ran the commands in Huawei with same result of LPM and nothing changed from OEM reset.

Posted: **Fri Jan 31, 2020 2:05 pm**

PRI missing 2020-01-31 135417.png

It seems like maybe its not loading the PRI file into the modem?

Posted: **Fri Jan 31, 2020 2:12 pm**

Also I dont know if it matters but during most of these tests I do not have a SIM card installed in the modem. Only when I move it over to the WE826 have I been putting the SIM in, as I only have one active sim and its my primary means of internet.

Posted: **Fri Jan 31, 2020 2:22 pm**

BrentV wrote: ↑Fri Jan 31, 2020 2:12 pm Also I dont know if it matters but during most of these tests I do not have a SIM card installed in the modem. Only when I move it over to the WE826 have I been putting the SIM in, as I only have one active sim and its my primary means of internet.

SIM Card does not matter. You actually do not want a SIM Card in it as Windows will try to connect it to the internet and take control of the modem--which is ALWAYS a bad idea.

You still suffer from mismatches and low power mode, which is most likely the result of the mismatch.

Posted: **Fri Jan 31, 2020 2:36 pm**

JimHelms wrote: ↑Fri Jan 31, 2020 2:22 pm SIM Card does not matter. You actually do not want a SIM Card in it as Windows will try to connect it to the internet and take control of the modem--which is ALWAYS a bad idea.

You still suffer from mismatches and low power mode, which is most likely the result of the mismatch.

So is this because the modem isn't flashing properly? Is it failing to install the the PRI file which causes the low power? or is the low power causing the miss-match? Is there a way to force it out of low power mode, or disable that mode entirely? Is there a different method to install the firmware I should try?

Posted: **Fri Jan 31, 2020 2:54 pm**

I am not sure what is causing it. But there is something wrong or corrupt in its configuration.

You might try flashing it with older GENERIC firmware (twice) and then try the newer one.

Other than that, I do not have a clue how to repair it.

You may have to contact whoever sold you the modem, and ask them if they can swap it out.

Posted: **Fri Jan 31, 2020 2:58 pm**

JimHelms wrote: ↑Fri Jan 31, 2020 2:54 pm I am not sure what is causing it. But there is something wrong or corrupt in its configuration.

You might try flashing it with older GENERIC firmware (twice) and then try the newer one.

Other than that, I do not have a clue how to repair it.

You may have to contact whoever sold you the modem, and ask them if they can swap it out.

Alright thanks for your help. I'll update as needed. Might end up swapping for a different card.

Posted: **Fri Jan 31, 2020 4:00 pm**

I stumbled across this page and under modems it shows production vs engineering samples. https://github.com/danielewood/sierra-wireless-modems

and this comment " I would recommend you get a production model. Engineering Samples will sometimes contain an early (SWI9X30C_00.08.02.00) firmware that can be a royal pain to flash due to AT!BOOTHOLD not being implemented."

This is for an EM7455 but I imagine it's possible it applies to MC7455. And if that's the case my card does look like the engineering sample in the link. I've contacted the vender to see what can be done about the issues. But if it is an issue of it being an engineering sample maybe knowing that, there's a way forward?

MVIMG_20200131_155158.jpg

Posted: **Fri Jan 31, 2020 4:25 pm**

BrentV wrote: ↑Fri Jan 31, 2020 4:00 pm I stumbled across this page and under modems it shows production vs engineering samples. https://github.com/danielewood/sierra-wireless-modems

and this comment " I would recommend you get a production model. Engineering Samples will sometimes contain an early (SWI9X30C_00.08.02.00) firmware that can be a royal pain to flash due to AT!BOOTHOLD not being implemented."

This is for an EM7455 but I imagine it's possible it applies to MC7455. And if that's the case my card does look like the engineering sample in the link. I've contacted the vender to see what can be done about the issues. But if it is an issue of it being an engineering sample maybe knowing that, there's a way forward?MVIMG_20200131_155158.jpg

Funny, I was actually typing up a message asking if this might be an "engineering sample", which as you already found out is a pain in the rear to flash or just about impossible. Some shady sellers get these real cheap under the pretense of using it for engineering testing, and they sell it to consumers at a high profits, wasting your precious time and sanity. Yikes!

Posted: **Fri Jan 31, 2020 4:39 pm**

BillA wrote: ↑Fri Jan 31, 2020 4:25 pm Funny, I was actually typing up a message asking if this might be an "engineering sample", which as you already found out is a pain to flash (or impossible). Some companies get these real cheap under the pretense of using it for engineering testing, yet they sell it to consumers at a high profit, wasting your precious time and sanity. Yikes!

Well now that I know what I'm working with maybe I can plow my way forward lol. I've flashed an intermediate firmware, newer than what came on it but older than the latest. I seem to have made progress (i think) based on the new responses I'm getting that I didnt get before.

After entering
at!entercnd="A710"
at!priid?

It now shows carrier PRI

I don't understand enough of this stuff to know what it means, but it feels like progress lol

Posted: **Fri Jan 31, 2020 4:47 pm**

Is the circled what's causing the carrier miss-match? On the first line is shows 2.32.11_00_ATT_XXXX
and the line below is shows 02.20.03.00_00_GENERIC_XXXX

Posted: **Fri Jan 31, 2020 5:28 pm**

Hopefully, he can shed some light on which modem you have and can offer a swap.

It is often more expensive when buying thru China in an attempt to save a few dollars.

Posted: **Fri Jan 31, 2020 5:33 pm**

JimHelms wrote: ↑Fri Jan 31, 2020 5:28 pm Hopefully, he can shed some light on which modem you have and can offer a swap.

It is often more expensive when buying thru China in an attempt to save a few dollars.

Yeah worst case I file a dispute. My first few I bought from china without issues, but yeah often in an attempt to save money we do end up spending more if not in $$ in time.

Posted: **Fri Jan 31, 2020 5:39 pm**

BrentV wrote: ↑Fri Jan 31, 2020 4:47 pm Is the circled what's causing the carrier miss-match? On the first line is shows 2.32.11_00_ATT_XXXX
and the line below is shows 02.20.03.00_00_GENERIC_XXXX

Yes, that is not what the carrier PRI is supposed to look like. It should have a PRI Part number.

This is an example I just pulled on a Cradlepoint MC400LP6 (which I had handly) which uses a MC7455:

PRI Number.png

Posted: **Fri Jan 31, 2020 5:40 pm**

Will it now accept the restore to OEM command?

Posted: **Fri Jan 31, 2020 5:42 pm**

JimHelms wrote: ↑Fri Jan 31, 2020 5:39 pm Yes, that is not what the carrier PRI is supposed to look like. It should have a PRI Part number.

This is an example I just pulled on a Cradlepoint MC400LP6 (which I had handly) which uses a MC7455:

PRI Number.png

ohh interesting. Thanks for that. At the very least I'm learning something.

Posted: **Fri Jan 31, 2020 5:44 pm**

JimHelms wrote: ↑Fri Jan 31, 2020 5:40 pm Will it now accept the restore to OEM command?

Unfortunately not, each firmware I've flashed I try to OEM command and get the same result. It's odd, because it seems to actually flash the files, because it always reports whatever version I install. but the OEM command never works and it stays in LPM.

Posted: **Fri Jan 31, 2020 5:45 pm**

This is what it should show on restore to OEM:

Reset to OEM.png

Posted: **Fri Jan 31, 2020 6:00 pm**

JimHelms wrote: ↑Fri Jan 31, 2020 5:45 pm This is what it should show on restore to OEM:

Reset to OEM.png

Yeah mine just says 0 for all.

Posted: **Fri Jan 31, 2020 6:40 pm**

Set PRI 2020-01-31 183907.png

So I found this PDF document... could I just give the modem a PID part number? Or is it looking for that to match something else?

Posted: **Fri Jan 31, 2020 6:44 pm**

You can try it....not much to loose at this point.

Posted: **Fri Jan 31, 2020 6:47 pm**

JimHelms wrote: ↑Fri Jan 31, 2020 6:44 pm You can try it....not much to loose at this point.

Is there a particular format it should be in?

Posted: **Fri Jan 31, 2020 7:11 pm**

Well after looking at my cradlepoint modem, and comparing it to yours, I just mirrored yours. I might pull the one from my MOFI and see what it says and copy that. But for now it seems to have accepted it. ALthough the oem reset still isnt right, going to try some other stuff and see what happens. Still in low power mode prior to the reset also.

MirroredCRADLEPOINT 2020-01-31 183907.png

Posted: **Fri Jan 31, 2020 7:15 pm**

Carrier name and all that still say miss-match. Going to flash a new firmware and see what happens.

Carrier name missmatch 2020-01-31 183907.png

Posted: **Fri Jan 31, 2020 7:27 pm**

I think the current carrier name needs to match the preferred carrier name. So they both need to say Generic

Posted: **Fri Jan 31, 2020 7:33 pm**

not sure. why don't you flash all the carrier firmware and try it. they are available on the drive but I do not have access to them right now.

Posted: **Fri Jan 31, 2020 7:39 pm**

JimHelms wrote: ↑Fri Jan 31, 2020 7:33 pm not sure. why don't you flash all the carrier firmware and try it. they are available on the drive but I do not have access to them right now.

I'll try that. I previously downloaded them all

EDIT- Ok I installed all 4 twice. Will see what happens

Posted: **Fri Jan 31, 2020 8:05 pm**

So it seems like the firmwares all flash just fine, but they aren't being loaded. When I type
AT!IMPREF="GENERIC"
at!reset

It changes the prefered firmware but under current firmware it is blank.

So maybe they are corrupt, or maybe it's not compatible with them for some reason? Ill try switching between the others and see if anything changes, though I doubt it will. Im guessing the flashes are either not taking, are getting corrupted or putting some odd settings that the modem doesn't like. I might try flashing from an Ubuntu live thumb drive.

firmwares 2020-01-31 200155.png

images 2020-01-31 200155.png

Posted: **Sat Feb 01, 2020 9:30 pm**

Well I've tried as much as I'm willing at this point, unless someone has more information that could help. I created an Ubuntu drive and successfully flashed the firmware within linux. It still has the carrier miss-match. I'm not sure why, or how to resolve it, but something just isn't right here and it's beyond my capabilities. I still haven't heard from the vendor so Ill probably open a dispute to get their attention.

Posted: **Sun Feb 02, 2020 12:01 am**

BrentV wrote: ↑Sat Feb 01, 2020 9:30 pm Well I've tried as much as I'm willing at this point, unless someone has more information that could help. I created an Ubuntu drive and successfully flashed the firmware within linux. It still has the carrier miss-match. I'm not sure why, or how to resolve it, but something just isn't right here and it's beyond my capabilities. I still haven't heard from the vendor so Ill probably open a dispute to get their attention.

At some point it's time throw in the towel, once too much time and effort has been wasted on a relatively inexpensive device which was clearly not meant for production. Not trying to disappoint, but during all this time trying, could have worked the same amount of hours at a regular job, and bought two new of these modems with the earnings. lol Been there done it myself, but never again. There's nothing wrong with trying, but in my opinion at some point it's simply not worth spending any more time and effort beating a dead horse. At least you've learned to screen your next purchase better for these shady sellers. ;/

Posted: **Sun Feb 02, 2020 8:26 am**

BillA wrote: ↑Sun Feb 02, 2020 12:01 am At some point it's time throw in the towel, once too much time and effort has been wasted on a relatively inexpensive device which was clearly not meant for production. Not trying to disappoint, but during all this time trying, could have worked the same amount of hours at a regular job, and bought two new of these modems with the earnings. lol Been there done it myself, but never again. At least you've learned to screen your next purchase for these shady sellers. ;/

I'm a tinkerer and I'm stubborn. I don't like to let devices win. I've always been of the mindset if there's a will there's a way and if someone else can do it then I can do it. And it's that mindset that's given me the fortitude to even attempt projects such as these in the first place. The time spent and all that isn't a big deal. I either succeed or I learn. In this case I've definitely gone as far as I'm willing to go, but I've learned quite a bit at the same time. I'll now be prepared for any properly working mobile modem in the future lol.

Posted: **Sun Feb 02, 2020 10:22 am**

You have learned a lot and I commend your mindset to take no prisoners.

Wireless Joint

WE826-T2 & MC7455 not playing nice

WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice

Re: WE826-T2 & MC7455 not playing nice