Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/05/2023 in Posts

  1. Got there in the end.. I put the comms problem down as Windows version and or CPU architect using USB 3.0 port. Bear-metal with up to update win10 and Intel HQ7700 got me over the line. My ferdora rig is packing a Ryzen 7 3000. Let's see how I got with UBports.. Thank all for all your input (M_P)
    2 points
  2. For some odd reason a 'factory reset' is needed after the flash of stock.
    1 point
  3. G'day @EskeRahn one thing to add after recovery fire flash, the phone now has 8G in storage when it had 256G before my brain fart. Is there a way to fix the partition? (M_P)
    1 point
  4. As far as I know, that PCB is different - at least they wrote in one of their update that they had to redesign that PCB as part of the radio problems they ran into, and also it looks different based on FCC photos. Anyway, potential problems with USB port were the reason they moved the connector to a different panel, so it would be very welcome to take advantage of that... I hope it will be available soon for purchase as a not expensive product. I really hope they have the manufacturing data for that board of Pro1... I would buy some of them for a reasonable price.
    1 point
  5. My VM was running Windows 11, not sure if that makes a difference or not. Did you see the phone in the list of devices to pass through to the VM? Maybe also make sure you've installed the guest tools in the VM as well. You can download them from here
    1 point
  6. Thanks! That's good to know. The source I had my information from must have done something wrong there then...
    1 point
  7. I made exactly the same mistake (you'll find my similar post somewhere a few weeks ago) But don't stress, the link EskeRahn gave you works, I followed the guide and got my phone working again. Just go through it carefully step by step. I can also confirm it does work in a Windows VM running on Linux, it does with Qemu/KVM anyway.
    1 point
  8. They made an official guide here https://community.fxtec.com/topic/3643-pro1-x-flashing-stock-android-with-qfil-windows-pc-only/ It is a bit complex. There might be easier ways to do it, but unfortunately there isn't (currently ?) a simple version with a zip file (like the one you used for the Pro1 Lineage), I have asked for that, and hopefully we will get it at some point...
    1 point
  9. So it looks like I too have an 'X' that's suffering bad cell connection issues 😪 I've done a full system reset and after only connecting to WiFi (to complete basic setup) & installing the Edge browser I'm now using + CX file explorer, I've tried to make & receive calls. Basically, the handset is totally unreliable. It hadn't suffered the bad call quality, or call drop outs, that I've seen others have complained of (prior to reset); it just seems to be utterly, horrendously, unreliable at holding cell connection in order to receive incoming calls. & while I initially attribut
    0 points
  10. Unfortunately, it has started the same way for me (prior to this point, it could charge relatively reliably only at one direction of Type-C connection).
    0 points
  11. Bit more on mine It has now got to the point that it will only charge under plug tension. in other words I have to place a weight on the charge cable and pull the phone away against the weight .It then charges quite reliably. No way to work long term any cure spring to mind ? It has to be a phisical fault.
    0 points
×
×
  • Create New...

Important Information

Terms