Boron LTE Stuck Flashing Green

boron
Tags: #<Tag:0x00007fe21f7e9bf0>

#1

So after opening two support tickets over the last week here and not getting a single response, I am about done with Particle’s Non Existent Support. You guys really need to hire more people for this, as your backend, has been having significant problems for me, for the last two weeks. My Boron LTE used to connect with zero issue from the location it is in now. With no software changes or location changes whatsoever, it began flashing green, and will occasionally connect and turn cyan, but only for short periods of time, but the majority of the time, even after going to sleep last night and waking up today, it is still flashing green. Either the hardware is defective in this unit, or your backend is still having significant issues, and your status page is not mentioning any of them. I have tried flashing it back to tinker, only to find the exact same problems. How do you expect companies or customers, to depend on your products, when you don’t respond to support tickets for an entire week(if the backlog is too big to handle for current staff, hire more, or fix the problems causing the enormous backlog)?? I am creating a product with your hardware and I find the complete lack of support for product creators or even just normal customers, to be absolutely atrocious. Let me be clear, that I am not here to bash Particle, as I see amazing potential with this ecosystem, but you guys are constantly strangling that potential, by not responding to your customers needs and requests for help. Please reach out to me ASAP, as I have a demo I need to be able to do next week. Even if it means paying to overnight new hardware, I will, but I need a response. Thank you,
-Spencer
Device OS:
1.2.1-rc.1


Boron LTE Stuck Blinking Green
#2

@sdevo619, I posted in the Particle Slack channel to hopefully get some attention.


#3

Thank you very much!!!


#4

Hi Spencer,

I want to apologize for the delay on this. We do recognize that there is a delay in support ticket handling. We are actively taking measures to reduce the support volume. We have recently hired a new member for our support team who will be assisting with our volume going forward. :slight_smile:

In regards to your particular issue, it’s unclear to me what exactly is going on at this time, but I’m going to do some digging into this and will be working with you today and tomorrow to ensure we get these resolved.

There are no known system outages on the backend at this time, so I suspect there is something going on with your device itself. If you could, please go ahead and run boron-clouddebug on your device and provide those logs either here or in one of your tickets and we can take it from there.

Thanks!


#5

Thank you very much, I really appreciate the response!!! This has been an ongoing issue with you guys for several years now, so it seems bit naive to hope this gets worked out, with the addition of one team member. I do sincerely appreciate that you guys are actively trying to tackle this issue👍🏻. My only advice, aside from hiring a larger amount support staff, if you don’t mind, is to create a position in the support department, for product creator support only, and even if it requires a reasonable monthly fee or a one time reasonable service fee, people in my position, will gladly pay it, to not play the waiting game like this. Offer them same day ticket response times 24hrs a day, expedited shipping on product replacements, maybe even a dedicated cloud server for the products backend. Make a service out of it, if works better that way, even potentially with multiple tiers. If you are worried about taking a hit on your bottom line for another new employee, figure how to pay for him/her with all, or a portion of the fees, this employee/department would collect from the service or one time fee for on the spot stuff. These are just some ideas I would highly suggest, because when my product finally makes it to production, this is not going to cut it for the type of product I’m developing, and have thousands of hours into scaling, or for most business attempting to launch a product with Particle at its heart.

A large portion of startups, don’t have a huge and loyal customer base, prior to launching their initial product (for obvious reasons), and often times, this will be their first product, which will very quickly end up getting obliterated by their own customers online, with bad reviews and product returns, because they can’t get responses in a timely fashion from you guys, without having to do what I did today. I really do very much appreciate your help today, and hope you guys will really consider these suggestions, but back to the main issue here.

I will run the boron-clouddebug here very soon in the next 30 mins. I will reply to the email i received with one of my ticket numbers so please be on the lookout for it. Thank you very much!!!


#6

After four failed attempts to flash my Boron with the boron-clouddebug , I am not sure what to say. The flash completes in the command line interface like normal and says Flash success!, but the boron still remains yellow and doesn’t appear to flash. And if i then reset it, it turns red. Even though I mentioned this twice in my tickets, I have the Boron LTE, just to make sure there isn’t any confusion. Any insight into what is going on here would be extremely helpful. Thank you!!!


#7

In case you overlooked this: https://www.particle.io/pricing#support

How are you trying to flash your Boron? Any chance we could get some videos/screenshots of the process/CLI?


#8

It’s certainly something we recognize and understand. The means of scaling our support team will require both near and long term efforts. We are already taking action for our near term and are working on initiatives to manage our support load in the long term.

Your suggestions are certainly valuable. I will be sharing your feedback with our internal teams. I do also encourage you to take a look at the link that @Moors7 provided as well. :slight_smile:

As @Moors7 also stated, if you are having difficulty flashing your boron, some videos and screenshots of the process/CLI would be helpful–especially in the case of error messages.


#9

Thank you both for your responses!!! I was not aware of this program. I will contact the sales team, but as you don’t have pricing listed for it, and the description of what that all means, is minimal at best, it is not easy to tell very much about how this will help here???

I am using the CLI from a Window 10 PC, that just flashed tinker to this same device prior times this week successfully, in an attempt to fix this. With the link you just sent me for the cloud debug, I tried downloading the whole repository and even just the file by itself, and cding to proper directory, and the flash begins, takes longer than normal, then says Success, but the Boron keeps on blinking yellow. In addition to the above statement, I went back and attempted to run the instructions at the bottom of this page you sent me the link to, to revert things back, and now it is flashing red constantly now. Also, what does that orange light keep blinking for up by the USB cable??

I also tried running the device doctor on the device and it fails and this is the message I’m seeing:
The Doctor didn’t complete sucesfully. Error writing firmware: file does not exist and no known app found.

Please visit our community forums for help with this error:

Any ideas? This has now cost me between the two emails i wrote you guys prioir to today, and troubleshooting time over 6hrs, and at a certain point, I cant keep doing this, as it will end up just being more cost effective to buy a new one. I of course would ideally not like to waste money, if this just needs a flash, but aside from these photos, due to the nature of my setup, it will not be possible to film both the command line and device at the same time, and if I did, would not be posting them here. The photo I included is what state it is currently in (red) and was prior to following your instructions today (yellow meaning if went into dfu no problem and turned cyan after the flash, prior to following the instruction I was given today by you guys).
Thank you again!!!


#10

Hey Spencer,

I suspect that your bootloader may be mismatched. The instructions on boron-clouddebug are based around 0.9.0, but I suspect your Boron was likely on the latest version 1.2.1.

When flashing files in DFU mode, the system does not automatically restart. It’s likely it required a manual restart. And, if it was flashing red after the manual restart, I suspect there was a bootloader mismatch.

If there’s a bootloader mismatch, the system can start up in an error state. If you are on v0.9.0 now, I would consider grabbing the bootloader from the v0.9.0 repository and flashing it while in serial (listening) mode with the command particle flash --serial <FILENAME>

Let’s give that a go and see if the device is acting a bit more healthy after a bootloader flash.


#11

Thank you very much!!! Hopefully you are right, however, I cannot get the device to enter listening mode. Even after holding the mode button for 3 seconds, the device won’t go into listening mode. Any suggestions??


#12

Hmm. That’s unusual. I assume you are able to boot it into DFU mode though.

The last reported device OS version for that unit is v1.2.1-rc.1. I would assume that the bootloader is for that version. What you might be able to do is get it back into DFU mode, then flash tinker and system-part1 for v1.2.1-rc.1 from the v1.2.1-rc.1 repository. That should stop the SOS error state and have the device boot normally again.

If that does let the device boot, you should be able to put it into listening mode then. From there, try flashing the v0.9.0 bootloader, then flashing the boron-clouddebug. Fingers crossed, that should boot up without an SOS error state.


#13

When you cannot get into “normal” Listening Mode you could try Safe Listening Mode.
Just start as if you were trying to get into Safe Mode but you don’t need to wait for the device to end up breathing magenta (which it probably won’t reach given your root issue).
Once the device starts blinking green press/hold SETUP again and then it should manage to get into LM.


#14

Ok, so I made some progress. I was able to get the boron-clouddebug all loaded up. Thanks for your help with that!. Here is the output from it. Not sure how any of this information is helpful in regard to troubleshooting connectivity issues, but here it is. I hope that we didn’t just waste a whole bunch more time on this. There isn’t a battery connected to the Boron while it is flashed, and I was not under the impression there needed to be, as I thought that was only for previous hardware versions. This also has never been an issue in the past either.


#15

Could you try hooking up a battery, to see if that makes a difference?
How are you currently powering the device? Cellular can cause some power peaks which your current power supply might not be able to handle, which is where the battery comes in.


#16

This information would definitely be helpful to know. It definitely looks like there’s something going on with the JST connector here, which could be related to your power source.

Connecting a battery, even temporarily, may be helpful in knocking it out of this state.


#17

Ok guys. I plugged in the battery, and the serial monitor is now collecting some useful data. For future reference, is there a way that boron can flash an led pattern or something along those lines, for inadequate input voltage. I was wondering if that was why the orange led by the USB cable kept blinking. Also, the battery should either be a hard requirement to run the boron at all times, or putting some type of capacitor inline with this circuit may help in future models not suffer from this issue, but the inconsistencies in your entire Cellular based product lineup that require batteries sometimes but not all times, has cost me a fair amount of time over my experience with them. I realize that not all USB ports are created equal, and there is good chance the front USB ports on my PC may not be kicking out enough voltage, but I have flashed this device multiple times over these same ports with no issues, and have also flashed my Spark Cores, Photons, and Electrons over these same ports. I also have an inline voltage and current monitor as well, so if you can let me know what the minimum voltage/current requirements are for running without batteries, that would be very helpful for future reference.

Please do try to fix this issue on the next hardware version though. The other reason I mention this, is that I have not been running my boron on a battery, for testing, for the product I’m creating, and it has been working just fine for quite a while, and these issues began to happen only after updating to the latest firmware version.

Here is the serial monitor output, any thoughts???

Serial monitor opened successfully:
0000187691 [ncp.at] TRACE: > AT+CEREG?
0000187742 [ncp.at] TRACE: < +CEREG: 2,2
0000187742 [ncp.at] TRACE: < OK
0000202743 [ncp.at] TRACE: > AT+CEREG?
0000202792 [ncp.at] TRACE: < +CEREG: 2,2
0000202792 [ncp.at] TRACE: < OK
0000217793 [ncp.at] TRACE: > AT+CEREG?
0000217842 [ncp.at] TRACE: < +CEREG: 2,2
0000217842 [ncp.at] TRACE: < OK
0000232843 [ncp.at] TRACE: > AT+CEREG?
0000232892 [ncp.at] TRACE: < +CEREG: 2,2
0000232892 [ncp.at] TRACE: < OK
0000247893 [ncp.at] TRACE: > AT+CEREG?
0000247942 [ncp.at] TRACE: < +CEREG: 2,2
0000247942 [ncp.at] TRACE: < OK
0000262943 [ncp.at] TRACE: > AT+CEREG?
0000263041 [ncp.at] TRACE: < +CEREG: 2,2
0000263042 [ncp.at] TRACE: < OK
0000278142 [ncp.at] TRACE: > AT+CEREG?
0000278193 [ncp.at] TRACE: < +CEREG: 2,2
0000278193 [ncp.at] TRACE: < OK
0000293194 [ncp.at] TRACE: > AT+CEREG?
0000293243 [ncp.at] TRACE: < +CEREG: 2,2
0000293243 [ncp.at] TRACE: < OK
0000297233 [sys.power] TRACE: Battery state CHARGING -> CHARGED
0000308244 [ncp.at] TRACE: > AT+CEREG?
0000308293 [ncp.at] TRACE: < +CEREG: 2,2
0000308293 [ncp.at] TRACE: < OK
0000323294 [ncp.at] TRACE: > AT+CEREG?
0000323343 [ncp.at] TRACE: < +CEREG: 2,2
0000323343 [ncp.at] TRACE: < OK
0000323343 [hal] WARN: Resetting the modem due to the network registration timeout
0000323343 [hal] WARN: Resetting the modem due to the network registration timeout
0000323344 [gsm0710muxer] INFO: Stopping GSM07.10 muxer
0000323344 [gsm0710muxer] INFO: Stopping GSM07.10 muxer
0000323345 [gsm0710muxer] INFO: Gracefully stopping GSM07.10 muxer
0000323345 [gsm0710muxer] INFO: Gracefully stopping GSM07.10 muxer
0000323346 [gsm0710muxer] INFO: Closing all muxed channels
0000323346 [gsm0710muxer] INFO: Closing all muxed channels
0000323347 [gsm0710muxer] INFO: Closing mux channel 1
0000323347 [gsm0710muxer] INFO: Closing mux channel 1
0000323348 [gsm0710muxer] INFO: Muxed channel 2 already closed
0000323348 [gsm0710muxer] INFO: Muxed channel 2 already closed
0000323349 [gsm0710muxer] INFO: Muxed channel 3 already closed
0000323349 [gsm0710muxer] INFO: Muxed channel 3 already closed
0000323349 [gsm0710muxer] INFO: Muxed channel 4 already closed
0000323349 [gsm0710muxer] INFO: Muxed channel 4 already closed
0000323450 [gsm0710muxer] INFO: Sending CLD (multiplexer close down)
0000323450 [gsm0710muxer] INFO: Sending CLD (multiplexer close down)
0000323501 [gsm0710muxer] INFO: Received response to CLD or timed out, exiting multiplexed mode
0000323501 [gsm0710muxer] INFO: Received response to CLD or timed out, exiting multiplexed mode
0000323503 [gsm0710muxer] INFO: GSM07.10 muxer thread exiting
0000323503 [gsm0710muxer] INFO: GSM07.10 muxer thread exiting
0000323503 [gsm0710muxer] INFO: GSM07.10 muxer stopped
0000323503 [gsm0710muxer] INFO: GSM07.10 muxer stopped
0000323504 [hal] TRACE: Hard resetting the modem
0000334504 [hal] TRACE: Powering modem on
0000334654 [hal] TRACE: Modem powered on
0000334655 [hal] TRACE: Setting UART voltage translator state 0
0000334655 [hal] TRACE: Powering modem off
0000334655 [hal] TRACE: Setting UART voltage translator state 0
0000346255 [hal] ERROR: Failed to power off modem
0000346255 [hal] ERROR: Failed to power off modem
0000346256 [hal] TRACE: NCP state changed: 0
0000346256 [net.pppncp] TRACE: NCP event 1
0000346356 [hal] TRACE: Modem already on
0000346357 [hal] TRACE: Setting UART voltage translator state 1
0000347358 [ncp.at] TRACE: > AT
0000347363 [ncp.at] TRACE: < OK
0000348364 [hal] TRACE: NCP ready to accept AT commands
0000348364 [ncp.at] TRACE: > AT+UGPIOC?
0000348372 [ncp.at] TRACE: < +UGPIOC:
0000348373 [ncp.at] TRACE: < 16,255
0000348373 [ncp.at] TRACE: < 19,255
0000348374 [ncp.at] TRACE: < 23,0
0000348375 [ncp.at] TRACE: < 24,255
0000348375 [ncp.at] TRACE: < 25,255
0000348376 [ncp.at] TRACE: < 42,255
0000348376 [ncp.at] TRACE: < OK
0000348377 [ncp.at] TRACE: > AT+UGPIOR=23
0000348384 [ncp.at] TRACE: < +UGPIOR: 23,1
0000348385 [ncp.at] TRACE: < OK
0000348385 [hal] INFO: Using internal SIM card
0000348385 [hal] INFO: Using internal SIM card
0000348386 [ncp.at] TRACE: > AT+CPIN?
0000348391 [ncp.at] TRACE: < +CPIN: READY
0000348392 [ncp.at] TRACE: < OK
0000348392 [ncp.at] TRACE: > AT+CCID
0000348398 [ncp.at] TRACE: < +CCID: 89014103271226457388
0000348399 [ncp.at] TRACE: < OK
0000348399 [ncp.at] TRACE: > AT+COPS=2
0000348409 [ncp.at] TRACE: < OK
0000348409 [ncp.at] TRACE: > AT+CEDRXS=0
0000348415 [ncp.at] TRACE: < OK
0000348415 [ncp.at] TRACE: > AT+CPSMS=0
0000348420 [ncp.at] TRACE: < OK
0000348420 [ncp.at] TRACE: > AT+CEDRXS?
0000348425 [ncp.at] TRACE: < +CEDRXS:
0000348426 [ncp.at] TRACE: < OK
0000348426 [ncp.at] TRACE: > AT+CPSMS?
0000348433 [ncp.at] TRACE: < +CPSMS:0,“01100000”,“00000000”
0000348434 [ncp.at] TRACE: < OK
0000348434 [ncp.at] TRACE: > AT+CMUX=0,0,1509,
0000348440 [ncp.at] TRACE: < OK
0000348441 [gsm0710muxer] INFO: Starting GSM07.10 muxer
0000348441 [gsm0710muxer] INFO: Starting GSM07.10 muxer
0000348442 [gsm0710muxer] INFO: Openning mux channel 0
0000348442 [gsm0710muxer] INFO: Openning mux channel 0
0000348442 [gsm0710muxer] INFO: GSM07.10 muxer thread started
0000348442 [gsm0710muxer] INFO: GSM07.10 muxer thread started
0000348494 [gsm0710muxer] INFO: Resuming channel 0
0000348494 [gsm0710muxer] INFO: Resuming channel 0
0000348494 [gsm0710muxer] INFO: Openning mux channel 1
0000348494 [gsm0710muxer] INFO: Openning mux channel 1
0000348546 [gsm0710muxer] INFO: Resuming channel 1
0000348546 [gsm0710muxer] INFO: Resuming channel 1
0000348546 [gsm0710muxer] INFO: Resuming channel 1
0000348546 [gsm0710muxer] INFO: Resuming channel 1
0000348548 [ncp.at] TRACE: > AT
0000348598 [ncp.at] TRACE: < OK
0000348598 [hal] TRACE: NCP state changed: 1
0000348598 [net.pppncp] TRACE: NCP event 1
0000348599 [hal] TRACE: Muxer AT channel live
0000348599 [hal] TRACE: PPP thread event LOWER_DOWN
0000348600 [hal] TRACE: PPP thread event ADM_DOWN
0000348600 [hal] TRACE: State READY -> NONE
0000348601 [hal] TRACE: PPP thread event ADM_UP
0000348602 [hal] TRACE: State NONE -> READY
0000348604 [ncp.at] TRACE: > AT+CIMI
0000348648 [ncp.at] TRACE: < 310410122645738
0000348648 [ncp.at] TRACE: < OK
0000348649 [ncp.at] TRACE: > AT+CGDCONT=1,“IP”,“10569.mcs”
0000348698 [ncp.at] TRACE: < OK
0000348698 [ncp.at] TRACE: > AT+CEREG=2
0000348748 [ncp.at] TRACE: < OK
0000348748 [hal] TRACE: NCP connection state changed: 1
0000348748 [net.pppncp] TRACE: NCP event 2
0000348749 [net.pppncp] TRACE: State changed event: 1
0000348749 [hal] TRACE: PPP thread event LOWER_DOWN
0000348750 [ncp.at] TRACE: > AT+COPS=0
0000348798 [ncp.at] TRACE: < OK
0000348798 [ncp.at] TRACE: > AT+CEREG?
0000348799 [ncp.at] TRACE: < +CEREG: 2
0000348848 [ncp.at] TRACE: < +CEREG: 2,2
0000348848 [ncp.at] TRACE: < OK
0000363849 [ncp.at] TRACE: > AT+CEREG?
0000363898 [ncp.at] TRACE: < +CEREG: 2,2
0000363898 [ncp.at] TRACE: < OK
0000378899 [ncp.at] TRACE: > AT+CEREG?
0000378948 [ncp.at] TRACE: < +CEREG: 2,2
0000378948 [ncp.at] TRACE: < OK
0000393949 [ncp.at] TRACE: > AT+CEREG?
0000393998 [ncp.at] TRACE: < +CEREG: 2,2
0000393998 [ncp.at] TRACE: < OK
0000408999 [ncp.at] TRACE: > AT+CEREG?
0000409048 [ncp.at] TRACE: < +CEREG: 2,2
0000409048 [ncp.at] TRACE: < OK
0000424049 [ncp.at] TRACE: > AT+CEREG?
0000424098 [ncp.at] TRACE: < +CEREG: 2,2
0000424098 [ncp.at] TRACE: < OK
0000439099 [ncp.at] TRACE: > AT+CEREG?
0000439148 [ncp.at] TRACE: < +CEREG: 2,2
0000439148 [ncp.at] TRACE: < OK
0000454149 [ncp.at] TRACE: > AT+CEREG?
0000454198 [ncp.at] TRACE: < +CEREG: 2,2
0000454198 [ncp.at] TRACE: < OK
0000469199 [ncp.at] TRACE: > AT+CEREG?
0000469248 [ncp.at] TRACE: < +CEREG: 2,2
0000469248 [ncp.at] TRACE: < OK
0000484249 [ncp.at] TRACE: > AT+CEREG?
0000484298 [ncp.at] TRACE: < +CEREG: 2,2
0000484298 [ncp.at] TRACE: < OK
0000499299 [ncp.at] TRACE: > AT+CEREG?
0000499348 [ncp.at] TRACE: < +CEREG: 2,2
0000499348 [ncp.at] TRACE: < OK
0000514383 [ncp.at] TRACE: > AT+CEREG?
0000514432 [ncp.at] TRACE: < +CEREG: 2,2
0000514432 [ncp.at] TRACE: < OK
0000529533 [ncp.at] TRACE: > AT+CEREG?
0000529582 [ncp.at] TRACE: < +CEREG: 2,2
0000529582 [ncp.at] TRACE: < OK
0000544683 [ncp.at] TRACE: > AT+CEREG?
0000544732 [ncp.at] TRACE: < +CEREG: 2,2
0000544732 [ncp.at] TRACE: < OK
0000559733 [ncp.at] TRACE: > AT+CEREG?
0000559782 [ncp.at] TRACE: < +CEREG: 2,2
0000559782 [ncp.at] TRACE: < OK
0000574883 [ncp.at] TRACE: > AT+CEREG?
0000574932 [ncp.at] TRACE: < +CEREG: 2,2
0000574932 [ncp.at] TRACE: < OK
0000589933 [ncp.at] TRACE: > AT+CEREG?
0000589982 [ncp.at] TRACE: < +CEREG: 2,2
0000589982 [ncp.at] TRACE: < OK
0000604983 [ncp.at] TRACE: > AT+CEREG?
0000605032 [ncp.at] TRACE: < +CEREG: 2,2
0000605032 [ncp.at] TRACE: < OK
0000620133 [ncp.at] TRACE: > AT+CEREG?
0000620182 [ncp.at] TRACE: < +CEREG: 2,2
0000620182 [ncp.at] TRACE: < OK
0000635183 [ncp.at] TRACE: > AT+CEREG?
0000635232 [ncp.at] TRACE: < +CEREG: 2,2
0000635232 [ncp.at] TRACE: < OK
0000650233 [ncp.at] TRACE: > AT+CEREG?
0000650282 [ncp.at] TRACE: < +CEREG: 2,2
0000650282 [ncp.at] TRACE: < OK
0000650282 [hal] WARN: Resetting the modem due to the network registration timeout
0000650282 [hal] WARN: Resetting the modem due to the network registration timeout
0000650284 [gsm0710muxer] INFO: Stopping GSM07.10 muxer
0000650284 [gsm0710muxer] INFO: Stopping GSM07.10 muxer
0000650284 [gsm0710muxer] INFO: Gracefully stopping GSM07.10 muxer
0000650284 [gsm0710muxer] INFO: Gracefully stopping GSM07.10 muxer
0000650285 [gsm0710muxer] INFO: Closing all muxed channels
0000650285 [gsm0710muxer] INFO: Closing all muxed channels
0000650286 [gsm0710muxer] INFO: Closing mux channel 1
0000650286 [gsm0710muxer] INFO: Closing mux channel 1
0000650287 [gsm0710muxer] INFO: Muxed channel 2 already closed
0000650287 [gsm0710muxer] INFO: Muxed channel 2 already closed
0000650288 [gsm0710muxer] INFO: Muxed channel 3 already closed
0000650288 [gsm0710muxer] INFO: Muxed channel 3 already closed
0000650289 [gsm0710muxer] INFO: Muxed channel 4 already closed
0000650289 [gsm0710muxer] INFO: Muxed channel 4 already closed
0000650389 [gsm0710muxer] INFO: Sending CLD (multiplexer close down)
0000650389 [gsm0710muxer] INFO: Sending CLD (multiplexer close down)
0000650440 [gsm0710muxer] INFO: Received response to CLD or timed out, exiting multiplexed mode
0000650440 [gsm0710muxer] INFO: Received response to CLD or timed out, exiting multiplexed mode
0000650442 [gsm0710muxer] INFO: GSM07.10 muxer thread exiting
0000650442 [gsm0710muxer] INFO: GSM07.10 muxer thread exiting
0000650442 [gsm0710muxer] INFO: GSM07.10 muxer stopped
0000650442 [gsm0710muxer] INFO: GSM07.10 muxer stopped
0000650443 [hal] TRACE: Hard resetting the modem
0000661443 [hal] TRACE: Powering modem on
0000661593 [hal] TRACE: Modem powered on
0000661594 [hal] TRACE: Setting UART voltage translator state 0
0000661594 [hal] TRACE: Powering modem off
0000661595 [hal] TRACE: Setting UART voltage translator state 0
0000673194 [hal] ERROR: Failed to power off modem
0000673194 [hal] ERROR: Failed to power off modem
0000673195 [hal] TRACE: NCP state changed: 0
0000673195 [net.pppncp] TRACE: NCP event 1
0000673295 [hal] TRACE: Modem already on
0000673296 [hal] TRACE: Setting UART voltage translator state 1
0000674297 [ncp.at] TRACE: > AT
0000674302 [ncp.at] TRACE: < OK
0000675303 [hal] TRACE: NCP ready to accept AT commands
0000675303 [ncp.at] TRACE: > AT+UGPIOC?
0000675310 [ncp.at] TRACE: < +UGPIOC:
0000675311 [ncp.at] TRACE: < 16,255
0000675312 [ncp.at] TRACE: < 19,255
0000675312 [ncp.at] TRACE: < 23,0
0000675313 [ncp.at] TRACE: < 24,255
0000675314 [ncp.at] TRACE: < 25,255
0000675314 [ncp.at] TRACE: < 42,255
0000675315 [ncp.at] TRACE: < OK
0000675315 [ncp.at] TRACE: > AT+UGPIOR=23
0000675324 [ncp.at] TRACE: < +UGPIOR: 23,1
0000675324 [ncp.at] TRACE: < OK
0000675325 [hal] INFO: Using internal SIM card
0000675325 [hal] INFO: Using internal SIM card
0000675325 [ncp.at] TRACE: > AT+CPIN?
0000675333 [ncp.at] TRACE: < +CPIN: READY
0000675334 [ncp.at] TRACE: < OK
0000675334 [ncp.at] TRACE: > AT+CCID
0000675343 [ncp.at] TRACE: < +CCID: 89014103271226457388
0000675343 [ncp.at] TRACE: < OK
0000675344 [ncp.at] TRACE: > AT+COPS=2
0000675357 [ncp.at] TRACE: < OK
0000675358 [ncp.at] TRACE: > AT+CEDRXS=0
0000675362 [ncp.at] TRACE: < OK
0000675363 [ncp.at] TRACE: > AT+CPSMS=0
0000675367 [ncp.at] TRACE: < OK
0000675368 [ncp.at] TRACE: > AT+CEDRXS?
0000675373 [ncp.at] TRACE: < +CEDRXS:
0000675373 [ncp.at] TRACE: < OK
0000675374 [ncp.at] TRACE: > AT+CPSMS?
0000675381 [ncp.at] TRACE: < +CPSMS:0,“01100000”,“00000000”
0000675381 [ncp.at] TRACE: < OK
0000675382 [ncp.at] TRACE: > AT+CMUX=0,0,1509,
0000675389 [ncp.at] TRACE: < OK
0000675389 [gsm0710muxer] INFO: Starting GSM07.10 muxer
0000675389 [gsm0710muxer] INFO: Starting GSM07.10 muxer
0000675390 [gsm0710muxer] INFO: Openning mux channel 0
0000675390 [gsm0710muxer] INFO: Openning mux channel 0
0000675390 [gsm0710muxer] INFO: GSM07.10 muxer thread started
0000675390 [gsm0710muxer] INFO: GSM07.10 muxer thread started
0000675442 [gsm0710muxer] INFO: Resuming channel 0
0000675442 [gsm0710muxer] INFO: Resuming channel 0
0000675442 [gsm0710muxer] INFO: Openning mux channel 1
0000675442 [gsm0710muxer] INFO: Openning mux channel 1
0000675494 [gsm0710muxer] INFO: Resuming channel 1
0000675494 [gsm0710muxer] INFO: Resuming channel 1
0000675495 [gsm0710muxer] INFO: Resuming channel 1
0000675495 [gsm0710muxer] INFO: Resuming channel 1
0000675496 [ncp.at] TRACE: > AT
0000675547 [ncp.at] TRACE: < OK
0000675547 [hal] TRACE: NCP state changed: 1
0000675547 [net.pppncp] TRACE: NCP event 1
0000675548 [hal] TRACE: Muxer AT channel live
0000675548 [hal] TRACE: PPP thread event LOWER_DOWN
0000675549 [hal] TRACE: PPP thread event ADM_DOWN
0000675549 [hal] TRACE: State READY -> NONE
0000675551 [hal] TRACE: PPP thread event ADM_UP
0000675551 [hal] TRACE: State NONE -> READY
0000675553 [ncp.at] TRACE: > AT+CIMI
0000675597 [ncp.at] TRACE: < 310410122645738
0000675597 [ncp.at] TRACE: < OK
0000675598 [ncp.at] TRACE: > AT+CGDCONT=1,“IP”,“10569.mcs”
0000675647 [ncp.at] TRACE: < OK
0000675647 [ncp.at] TRACE: > AT+CEREG=2
0000675697 [ncp.at] TRACE: < OK
0000675697 [hal] TRACE: NCP connection state changed: 1
0000675697 [net.pppncp] TRACE: NCP event 2
0000675698 [net.pppncp] TRACE: State changed event: 1
0000675698 [hal] TRACE: PPP thread event LOWER_DOWN
0000675699 [ncp.at] TRACE: > AT+COPS=0
0000675747 [ncp.at] TRACE: < OK
0000675747 [ncp.at] TRACE: > AT+CEREG?
0000675748 [ncp.at] TRACE: < +CEREG: 2
0000675797 [ncp.at] TRACE: < +CEREG: 2,2
0000675797 [ncp.at] TRACE: < OK
0000690798 [ncp.at] TRACE: > AT+CEREG?
0000690847 [ncp.at] TRACE: < +CEREG: 2,2
0000690847 [ncp.at] TRACE: < OK
0000705848 [ncp.at] TRACE: > AT+CEREG?
0000705897 [ncp.at] TRACE: < +CEREG: 2,2
0000705897 [ncp.at] TRACE: < OK
0000720998 [ncp.at] TRACE: > AT+CEREG?
0000721047 [ncp.at] TRACE: < +CEREG: 2,2
0000721047 [ncp.at] TRACE: < OK
0000736148 [ncp.at] TRACE: > AT+CEREG?
0000736197 [ncp.at] TRACE: < +CEREG: 2,2
0000736197 [ncp.at] TRACE: < OK
0000751298 [ncp.at] TRACE: > AT+CEREG?
0000751347 [ncp.at] TRACE: < +CEREG: 2,2
0000751347 [ncp.at] TRACE: < OK
0000766448 [ncp.at] TRACE: > AT+CEREG?
0000766497 [ncp.at] TRACE: < +CEREG: 2,2
0000766497 [ncp.at] TRACE: < OK
0000781598 [ncp.at] TRACE: > AT+CEREG?
0000781647 [ncp.at] TRACE: < +CEREG: 2,2
0000781647 [ncp.at] TRACE: < OK
0000796748 [ncp.at] TRACE: > AT+CEREG?
0000796797 [ncp.at] TRACE: < +CEREG: 2,2
0000796797 [ncp.at] TRACE: < OK
0000811898 [ncp.at] TRACE: > AT+CEREG?
0000811947 [ncp.at] TRACE: < +CEREG: 2,2
0000811947 [ncp.at] TRACE: < OK
0000826948 [ncp.at] TRACE: > AT+CEREG?
0000826997 [ncp.at] TRACE: < +CEREG: 2,2
0000826997 [ncp.at] TRACE: < OK
0000842098 [ncp.at] TRACE: > AT+CEREG?
0000842147 [ncp.at] TRACE: < +CEREG: 2,2
0000842147 [ncp.at] TRACE: < OK
0000857248 [ncp.at] TRACE: > AT+CEREG?
0000857297 [ncp.at] TRACE: < +CEREG: 2,2
0000857297 [ncp.at] TRACE: < OK
0000872398 [ncp.at] TRACE: > AT+CEREG?
0000872447 [ncp.at] TRACE: < +CEREG: 2,2
0000872447 [ncp.at] TRACE: < OK
0000887548 [ncp.at] TRACE: > AT+CEREG?
0000887597 [ncp.at] TRACE: < +CEREG: 2,2
0000887597 [ncp.at] TRACE: < OK
0000902598 [ncp.at] TRACE: > AT+CEREG?
0000902647 [ncp.at] TRACE: < +CEREG: 2,2
0000902647 [ncp.at] TRACE: < OK
0000917748 [ncp.at] TRACE: > AT+CEREG?
0000917797 [ncp.at] TRACE: < +CEREG: 2,2
0000917797 [ncp.at] TRACE: < OK
0000932898 [ncp.at] TRACE: > AT+CEREG?
0000932947 [ncp.at] TRACE: < +CEREG: 2,2
0000932947 [ncp.at] TRACE: < OK
0000948048 [ncp.at] TRACE: > AT+CEREG?
0000948097 [ncp.at] TRACE: < +CEREG: 2,2
0000948097 [ncp.at] TRACE: < OK
0000963198 [ncp.at] TRACE: > AT+CEREG?
0000963247 [ncp.at] TRACE: < +CEREG: 2,2
0000963247 [ncp.at] TRACE: < OK
0000978348 [ncp.at] TRACE: > AT+CEREG?
0000978397 [ncp.at] TRACE: < +CEREG: 2,2
0000978397 [ncp.at] TRACE: < OK
0000978398 [hal] WARN: Resetting the modem due to the network registration timeout
0000978398 [hal] WARN: Resetting the modem due to the network registration timeout
0000978399 [gsm0710muxer] INFO: Stopping GSM07.10 muxer
0000978399 [gsm0710muxer] INFO: Stopping GSM07.10 muxer
0000978399 [gsm0710muxer] INFO: Gracefully stopping GSM07.10 muxer
0000978399 [gsm0710muxer] INFO: Gracefully stopping GSM07.10 muxer
0000978400 [gsm0710muxer] INFO: Closing all muxed channels
0000978400 [gsm0710muxer] INFO: Closing all muxed channels
0000978401 [gsm0710muxer] INFO: Closing mux channel 1
0000978401 [gsm0710muxer] INFO: Closing mux channel 1
0000978402 [gsm0710muxer] INFO: Muxed channel 2 already closed
0000978402 [gsm0710muxer] INFO: Muxed channel 2 already closed
0000978403 [gsm0710muxer] INFO: Muxed channel 3 already closed
0000978403 [gsm0710muxer] INFO: Muxed channel 3 already closed
0000978404 [gsm0710muxer] INFO: Muxed channel 4 already closed
0000978404 [gsm0710muxer] INFO: Muxed channel 4 already closed
0000978504 [gsm0710muxer] INFO: Sending CLD (multiplexer close down)
0000978504 [gsm0710muxer] INFO: Sending CLD (multiplexer close down)
0000978555 [gsm0710muxer] INFO: Received response to CLD or timed out, exiting multiplexed mode
0000978555 [gsm0710muxer] INFO: Received response to CLD or timed out, exiting multiplexed mode
0000978557 [gsm0710muxer] INFO: GSM07.10 muxer thread exiting
0000978557 [gsm0710muxer] INFO: GSM07.10 muxer thread exiting
0000978558 [gsm0710muxer] INFO: GSM07.10 muxer stopped
0000978558 [gsm0710muxer] INFO: GSM07.10 muxer stopped
0000978558 [hal] TRACE: Hard resetting the modem
0000989558 [hal] TRACE: Powering modem on
0000989708 [hal] TRACE: Modem powered on
0000989709 [hal] TRACE: Setting UART voltage translator state 0
0000989709 [hal] TRACE: Powering modem off
0000989710 [hal] TRACE: Setting UART voltage translator state 0
0001001309 [hal] ERROR: Failed to power off modem
0001001309 [hal] ERROR: Failed to power off modem
0001001310 [hal] TRACE: NCP state changed: 0
0001001310 [net.pppncp] TRACE: NCP event 1
0001001410 [hal] TRACE: Modem already on
0001001411 [hal] TRACE: Setting UART voltage translator state 1
0001002412 [ncp.at] TRACE: > AT
0001002417 [ncp.at] TRACE: < OK
0001003418 [hal] TRACE: NCP ready to accept AT commands
0001003418 [ncp.at] TRACE: > AT+UGPIOC?
0001003425 [ncp.at] TRACE: < +UGPIOC:
0001003426 [ncp.at] TRACE: < 16,255
0001003427 [ncp.at] TRACE: < 19,255
0001003427 [ncp.at] TRACE: < 23,0
0001003428 [ncp.at] TRACE: < 24,255
0001003429 [ncp.at] TRACE: < 25,255
0001003429 [ncp.at] TRACE: < 42,255
0001003430 [ncp.at] TRACE: < OK
0001003430 [ncp.at] TRACE: > AT+UGPIOR=23
0001003439 [ncp.at] TRACE: < +UGPIOR: 23,1
0001003439 [ncp.at] TRACE: < OK
0001003440 [hal] INFO: Using internal SIM card
0001003440 [hal] INFO: Using internal SIM card
0001003440 [ncp.at] TRACE: > AT+CPIN?
0001003448 [ncp.at] TRACE: < +CPIN: READY
0001003448 [ncp.at] TRACE: < OK
0001003449 [ncp.at] TRACE: > AT+CCID
0001003457 [ncp.at] TRACE: < +CCID: 89014103271226457388
0001003458 [ncp.at] TRACE: < OK
0001003458 [ncp.at] TRACE: > AT+COPS=2
0001003475 [ncp.at] TRACE: < OK
0001003475 [ncp.at] TRACE: > AT+CEDRXS=0
0001003480 [ncp.at] TRACE: < OK
0001003480 [ncp.at] TRACE: > AT+CPSMS=0
0001003485 [ncp.at] TRACE: < OK
0001003485 [ncp.at] TRACE: > AT+CEDRXS?
0001003491 [ncp.at] TRACE: < +CEDRXS:
0001003491 [ncp.at] TRACE: < OK
0001003491 [ncp.at] TRACE: > AT+CPSMS?
0001003499 [ncp.at] TRACE: < +CPSMS:0,“01100000”,“00000000”
0001003499 [ncp.at] TRACE: < OK
0001003500 [ncp.at] TRACE: > AT+CMUX=0,0,1509,
0001003507 [ncp.at] TRACE: < OK
0001003507 [gsm0710muxer] INFO: Starting GSM07.10 muxer
0001003507 [gsm0710muxer] INFO: Starting GSM07.10 muxer
0001003508 [gsm0710muxer] INFO: Openning mux channel 0
0001003508 [gsm0710muxer] INFO: Openning mux channel 0
0001003508 [gsm0710muxer] INFO: GSM07.10 muxer thread started
0001003508 [gsm0710muxer] INFO: GSM07.10 muxer thread started
0001003560 [gsm0710muxer] INFO: Resuming channel 0
0001003560 [gsm0710muxer] INFO: Resuming channel 0
0001003560 [gsm0710muxer] INFO: Openning mux channel 1
0001003560 [gsm0710muxer] INFO: Openning mux channel 1
0001003612 [gsm0710muxer] INFO: Resuming channel 1
0001003612 [gsm0710muxer] INFO: Resuming channel 1
0001003613 [gsm0710muxer] INFO: Resuming channel 1
0001003613 [gsm0710muxer] INFO: Resuming channel 1
0001003614 [ncp.at] TRACE: > AT
0001003664 [ncp.at] TRACE: < OK
0001003664 [hal] TRACE: NCP state changed: 1
0001003664 [net.pppncp] TRACE: NCP event 1
0001003665 [hal] TRACE: Muxer AT channel live
0001003665 [hal] TRACE: PPP thread event LOWER_DOWN
0001003666 [hal] TRACE: PPP thread event ADM_DOWN
0001003666 [hal] TRACE: State READY -> NONE
0001003668 [hal] TRACE: PPP thread event ADM_UP
0001003668 [hal] TRACE: State NONE -> READY
0001003670 [ncp.at] TRACE: > AT+CIMI
0001003714 [ncp.at] TRACE: < 310410122645738
0001003714 [ncp.at] TRACE: < OK
0001003715 [ncp.at] TRACE: > AT+CGDCONT=1,“IP”,“10569.mcs”
0001003764 [ncp.at] TRACE: < OK
0001003764 [ncp.at] TRACE: > AT+CEREG=2
0001003814 [ncp.at] TRACE: < OK
0001003814 [hal] TRACE: NCP connection state changed: 1
0001003814 [net.pppncp] TRACE: NCP event 2
0001003815 [net.pppncp] TRACE: State changed event: 1
0001003815 [hal] TRACE: PPP thread event LOWER_DOWN
0001003816 [ncp.at] TRACE: > AT+COPS=0
0001003864 [ncp.at] TRACE: < OK
0001003864 [ncp.at] TRACE: > AT+CEREG?
0001003865 [ncp.at] TRACE: < +CEREG: 2
0001003914 [ncp.at] TRACE: < +CEREG: 2,2
0001003914 [ncp.at] TRACE: < OK
0001018915 [ncp.at] TRACE: > AT+CEREG?
0001018964 [ncp.at] TRACE: < +CEREG: 2,2
0001018964 [ncp.at] TRACE: < OK
0001033974 [ncp.at] TRACE: > AT+CEREG?
0001034023 [ncp.at] TRACE: < +CEREG: 2,2
0001034024 [ncp.at] TRACE: < OK
0001049024 [ncp.at] TRACE: > AT+CEREG?
0001049073 [ncp.at] TRACE: < +CEREG: 2,2
0001049074 [ncp.at] TRACE: < OK
0001064074 [ncp.at] TRACE: > AT+CEREG?
0001064123 [ncp.at] TRACE: < +CEREG: 2,2
0001064124 [ncp.at] TRACE: < OK
0001079124 [ncp.at] TRACE: > AT+CEREG?
0001079173 [ncp.at] TRACE: < +CEREG: 2,2
0001079174 [ncp.at] TRACE: < OK
0001094174 [ncp.at] TRACE: > AT+CEREG?
0001094223 [ncp.at] TRACE: < +CEREG: 2,2
0001094224 [ncp.at] TRACE: < OK
0001109224 [ncp.at] TRACE: > AT+CEREG?
0001109273 [ncp.at] TRACE: < +CEREG: 2,2
0001109274 [ncp.at] TRACE: < OK
0001124274 [ncp.at] TRACE: > AT+CEREG?
0001124323 [ncp.at] TRACE: < +CEREG: 2,2
0001124324 [ncp.at] TRACE: < OK
0001139324 [ncp.at] TRACE: > AT+CEREG?
0001139373 [ncp.at] TRACE: < +CEREG: 2,2
0001139374 [ncp.at] TRACE: < OK
0001154374 [ncp.at] TRACE: > AT+CEREG?
0001154423 [ncp.at] TRACE: < +CEREG: 2,2
0001154424 [ncp.at] TRACE: < OK
0001169424 [ncp.at] TRACE: > AT+CEREG?
0001169473 [ncp.at] TRACE: < +CEREG: 2,2
0001169474 [ncp.at] TRACE: < OK
0001184474 [ncp.at] TRACE: > AT+CEREG?
0001184523 [ncp.at] TRACE: < +CEREG: 2,2
0001184524 [ncp.at] TRACE: < OK


#18

Hey Spencer,

Much appreciated for providing those logs!

In regards to the battery requirement, due to the significantly reduced power draw of the u-blox R410M-02-B found in our LTE units, the battery is actually not a requirement for any of our LTE units under normal power operation.

The PMIC controller (the yellow blinking light you mention) kicks on whenever there is insufficient power. Either your provided power source was not supplying the minimum required power, and the battery was required–or it somehow got itself into a bad state, and connecting a battery reset the PMIC controller.

If you can try a few alternative power sources, you may find that your Boron LTE won’t require the battery when connected to them.

Based on the logs provided, I was able to cross check your Boron’s SIM ICCID with our platform and our telephony partner’s platform. The SIM is in an active and healthy state. However, based on the perpetual AT+CEREG 2,2 response, your device isn’t finding any towers that will accept it.

CEREG 2,2 as per documentation shows:
not registered, but MT is currently trying to attach or searching an operator to register to

I’d recommend you perform a tower scan, but unfortunately, as mentioned in boron-clouddebug:
If you press c (show carriers at this location), the program will scan nearby towers and show the carriers, frequencies, and signal strength. This takes several minutes to run, which is why it's not done by default. It is only supported on the Boron 2G/3G, it is not supported on the Boron LTE.

Since the R410M-02-B doesn’t support carrier scanning, I don’t have a lot of insight into what towers are nearby.

Either there are no accessible AT&T CAT M1 LTE towers in your area, or there is some sort of interference that is causing you from being able to connect.

If you were just on the border of CAT M1 LTE range and there is some sort of external interference, it could simply be a matter of the interference being the determining factor of whether your Boron LTE is able to get a signal to the tower

Otherwise, the only other consideration is that there is something wonky going on with the antenna. I would double check the integrity of your antenna, ensure it is a cellular antenna and not a wifi antenna, and make certain it is connected to the appropriate u.FL connector on your Boron. Keep in mind there are three u.FL connectors, one for cellular, one for bluetooth, and one for mesh. There is no in-built antenna for Borons, so if there is no properly connected external antenna, it won’t connect.

If you have any other antennas, especially any on other known working Boron units, I would absolutely recommend swapping them.

Also make certain you’re operating this unit outdoors without any large or apparent blockers that may interfere with signal to the tower.


#19

@sdevo619, Have you used 3rd party sim before and left sim in sim holder?
If so, it needs to be removed.


#20

Thank you for that information about the flashing orange light. That is very helpful! Might not be bad idea to include that in the LED state section on the boron troubleshooting. If it is there, I didn’t see it. I am using the antenna that shipped with my boron in the same place it was working prior to this issue, also, the antenna and connector have no visible damage that I can see.

The antenna never dropped off the network like this, ever before, in the same exact location and position, so it is a bit hard for me to believe this is an interference issue, or even a down cell tower, as this has persisted for two weeks now. Also to require this be run outdoors when I my cell reception in my home and with Boron, has never been an issue before, seems like a ridiculous request, as it comes off, as this was never designed to function indoors, which just makes me more apprehensive to build on this platform. I am not using any third party sim for this, and never have, am using the builtin one. I am including an image to show that the antenna is not at all damaged, but this brings me back to my original question here. How fast can you get me a replacement for this, if you truly believe at the end of this message, it still is a hardware issue???

I am going to purchase two more here shortly anyways as a backups, however, this now a dead stick or the current firmware/bootloader is causing issues, or the antenna is bad, as all my other antennas are for the 3g Electron, and I do not believe they are compatible, they probably wont help here. Also, as a side note, my 3g Electron, just connected in the same location, and is breathing cyan, in under 15 seconds.

To add to this already complex puzzle, the Electron is also having more frequent disconnects than normal on this same firmware/bootloader version, but not even close to as much as the Boron though, further helping to confirm my suspicion, that this is likely a software issue. Blaming it on bad or out of range cell service seems to be a bit of reach at this point. These are both drastic changes from the performance I am used to seeing with either of these devices. If they were both using LTE that would make a lot more sense, but as one is 3g and the other is LTE, it doesn’t make much sense to me. I live in Southern California, just so you can see if whoever is providing network coverage for Particle is having cell tower outages, but again, it seems like it is the least likely culprit here.

I have not had this Boron for long at all, and purchased it directly through your website, so if there is anything you can do here, I have spent the better part of my weekend troubleshooting failed hardware or buggy firmware or bootloader issues, which now adds up to well over 9 hrs of my time, so anything you guys can do here would go a long ways to helping.

Even if it means meeting you halfway on this, I will, but as I have not done any soldering on this device at all, it is still in the same condition I purchased it in, if you guys can step up in any way here, it would really mean a lot to me. I am happy to pay to ship this back to you guys, so you can figure out what happened to it.

I can’t continue to play the troubleshooting game with you though, or you just sending me an antenna alone though, as it will completely screw me if it ends up being the boron, and as far as trying any additional software changes, I can’t keep randomly trying these suggestions, as all they have done is bring me back to the same conclusion, buggy software or failed hardware, one which I can’t fix, and the other, I cant keep wasting time on, knowing that it could be an issue with the antenna.


Also, just FYI, I was able to get to it to work early this morning, and hold a cyan breathing light for quite a while, but tinker wasn’t working at all for this device, from my iPhone, which may be due to cloud debug being an old version of the firmware and bootloader, but it only kept a connection, running boron clouddebug firmware and bottloader. As soon as I switched back to v1.2.1-rc.1, it broke again, and it will occasionally connect, but very quickly loses connenction. So either I’m doing something wrong, which I am doubting at this point, if I am, speak up now, or there is more than likely, an issue with current firmware or bootloader or hardware, as far as I can conclude here. These are the files I’m using which are breaking it, and all of the flashes were successful and performed with a battery connected too. If there is no possible way, the issue is in one of those three files, then I just need a replacement, we’ll call it a day. Also, if you have any coupon codes for the two others I’m buying, that would be really helpful in this circumstance. Please let me know how you would like to proceed here.
Thank you very much for all your help this weekend!!!
-Spencer

59%20AM