PMOS test image: failed EG25 test broke modem fw
#1
I was using the PMOS factory test image and while running the Automatic Test it hangs at "Upgrading EG25" and never completes.

The modem is now undetected by any OS I've tried. Any tips on getting it back?

Thanks!

edit: after looking at restoring the eg25 fw to its factory state via https://github.com/Biktorgj/quectel_eg25_recovery/ it's such a convoluted mess. Is there any other way or does clicking TEST on the Test img. just brick modems? aargh.
  Reply
#2
Did you get it booted in EDL mode as described on that firmware restore page? Or what is the step that actually fails for you?
  Reply
#3
(02-28-2021, 11:15 AM)kuleszdl Wrote: Did you get it booted in EDL mode as described on that firmware restore page? Or what is the step that actually fails for you?
I flashed PMOS test image an booted normally. When it booted to the test app I tapped "automatic test" and that was the end of the modem Smile .

I'm just curious what is the best path forward for recovery. (I'm supper pissed that the "test" started changing the fw and then promptly failed and broke hardware.) Angry  .

Now I'm just looking to get the pp back to its factory state. Any help is appreciated!!
  Reply
#4
(02-28-2021, 12:17 PM)MtnSk8 Wrote: (I'm supper pissed that the "test" started changing the fw and then promptly failed and broke hardware.) Angry  .

Now I'm just looking to get the pp back to its factory state. Any help is appreciated!!

I’d be super pissed, too. When newer modem firmware first became available (thread), we were told that the process was dangerous, and that if it failed, to try again a few more times. I’m not aware of any way to get it back to the factory state.

Edit: Maybe I’m wrong about the factory state and Biktor’s recovery stuff, but I do seem to recall that no one has the original modem firmware at hand, in which case the only way is forward.
  Reply
#5
Biktor’s fix seems to have worked (after I remembered to chmod +x the qfirehose file, oops). I have to drive down the road to get a carrier but everything else seems as it was before. Jumping the pins was much easier than the ADB method.

My advice is to never use the PMOS test image!

Marking this as solved, thanks for the replies and moral support (mostly what I needed, lol)

Cheers!
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Latest suggestion to fix modem instability? feklee 10 3,101 01-31-2022, 01:16 PM
Last Post: feklee
  No Application Data PMOS 21.12.1 Captain1ndustry 2 581 01-27-2022, 12:00 PM
Last Post: Captain1ndustry
  Application list PMOS-Phosh jmorris 6 2,383 12-04-2021, 02:26 AM
Last Post: Juergen
  sudo broke - "/usr/bin/sudo must be owned by uid 0 and have the setuid bit set" cowsay 2 1,416 07-07-2021, 12:41 PM
Last Post: cowsay
Thumbs Up Modem Shutdown/Startup Scripts big_fluff 0 979 05-08-2021, 12:59 AM
Last Post: big_fluff
  Where is the original PM OS image for Pinephone? mw4jet 1 1,441 03-14-2021, 07:37 AM
Last Post: ludix
Wink Extremely fast pmOS build for the pinephone lucasanss 0 1,817 02-03-2021, 04:05 PM
Last Post: lucasanss
  Modem can't dial out jmorris 12 8,000 11-25-2020, 08:24 PM
Last Post: bcnaz
  Wifi and bluetooth disabled after upgrading to PMOS kernel 5.9.1 aithal 0 1,198 11-09-2020, 01:17 AM
Last Post: aithal
  Is a Software update the same as instaling an updated image Word5 1 1,843 09-19-2020, 10:23 PM
Last Post: jmorris

Forum Jump:


Users browsing this thread: 1 Guest(s)