Casey

Could you go to your dial pad and enter *#*#4636#*#*, then take a screenshot of the Phone info? Feel free to send it via DM. I am curious what it says..

I see. Things definitely were lost in translation here. As I wasn't the one handling your ticket, it appears my colleague left this out. Can you provide your ticket ID so I can follow up?

Sorry for the delays. I have your device with me and it is fixed already. The reason we ask to keep it for longer is to help our developers debug the issue so it doesn't happen again. We're working with Snapdragon to resolve this problem and will soon be able to send back your phone. Again, thank you for your patience.

I've relayed this issue back to our dev team and they will look into it. I'll update here when there's progress. Thanks for bringing this up.

@Hook @claude0001 Indeed there's a mix-up (on my part). I was misled by what was considered "upper-housing". You guys are right. We only offer the "frame" for replacement/for sale (the detachable screen itself after unscrewing the 5 bolts). This can be easily replaced by any user and requires no glueing etc.

You're right, our replacement parts for Pro1-X is the entire upper housing. But if you just want to change the screen, providing a detachable screen is enough. Changing the entire upper housing can be quite tricky as you'll be wiggling the hinges apart which may cause it to snap if not careful. We don't normally change the upper housing anyways (even with the Pro1) as there's no electrical components there (unless you somehow drop and break it). Replacing either the entire upper housing or just the detachable screen does not involve glueing, if that's what you're asking. Correc

Yes, I mean the detachable screen itself, not the entire upper housing. All I did was connect the flat ribbon cable of the Pro1-X upper housing to the detachable Pro1 screen. We have spare Pro1-X screens in the warehouse which will be shipped to us once everything resumes, but we do have Pro1 screens and other spare parts in stock in our office if anyone is looking for a replacement etc.

Yes, the screen is the same, however I think there's some sw/hw compatibility issue with the Pro1 screen on the Pro1-X body. The selfie camera does not work and it force quits the camera app, and touch screen is not alway responsive. Not sure what the reason this is as the screen itself is the same model 🙂

Can you make sure you've installed QPST package rather than QFIL standalone? Check this article here for ways to fix the sahara error, I'd focus on step 8 first: https://krispitech.com/how-to-fix-sahara-fail-error-in-qfil/

Thanks for the update. This is a tricky one. It takes a couple of trial and errors to get pass this error. Can you try uninstalling your current QPST package, then download the previous version of it. Make sure when you launch QFIL, you access it through your destination folder: 1. Go to the destination folder you downloaded the QPST package. a. e.g. C:\Program Files (x86)\Qualcomm\QPST\ . 2. Inside the “bin” folder, find and launch the QFIL software (green circle with white downward arrow). Worse comes to worse, you'd have to send the unit to us and I'll flash it for

adb sideload is used for flashing a new image (i.e. a firmware that has a higher build number compared to the current). The forum post you linked in your comment was for flashing the GMS-less build, which has a higher version number (2.1.5) than the stock OS (2.1.2). This process only requires you to flash the OTA package which adb sideload in recovery mode is better suited for. Although QFIL is the safest way to flash a full image (as it's a tool specifically designed for Qualcomm devices), it is faster and less tedious to use adb sideload for upgrading firmware and using fastboot scrip

@Ryan, I see, it's the infamous sahara error. I've got quite a few of those before too. According to your screenshots, you don't have the correct number of XML files (rawprogram and patch files). The correct files should be: rawprogram_unsparse0 rawprogram1 rawprogram2 rawprogram3 rawprogram4 rawprogram5 AND patch0 patch1 patch2 patch3 patch4 patch5 I suggest you to re-extract the tar.gz file again using a free software called 7zip. Once downloaded, right click on the tar.gz file and select "7zip >" to extract. Additionally, here's some tips to

We are aware of Expansys selling Pro1-X's on their website and we understand there's a lot of concerns and theories about the nature of these listings. We'll post a follow-up announcement to address this. But rest assured, all IGG and website orders are not compromised!

What type of error do you get when you tried flashing the stock OS on QFIL? Best to check if your PC is able to recognise your Pro1-X under EDL mode. Go to device manager on your computer and boot your phone into EDL mode, see if there's either an exclamation mark or e.g. COM10 port available. Either way, feel free to email all the info you've got so far to our support desk info@fxtec.com and let me know the ticket number. I'll take a look.

Thanks for providing this. I think the best thing to do here is to try factory reseting your phone again. If that doesn't work, then best to flash the stock OS again..

Welcome! Could you take a screenshot of the build number in Settings -> About phone -> (scroll to bottom) Build number.

Frankly speaking, we've been receiving a lot of emails from our customers compared to early days, so I'd say 10 working days. I know it's not ideal, but we're working on them urgently.

Unfortunately, we quickly found that the stock OS didn't support HDMI output so we've pushed out a beta firmware to address this in the beta testing scheme. And yes, you're right. The solutions company only demo'd us with a specific HDMI cable that needs an app or apk to work with it. We can confirm this cable does work on Android OS but only with a beta firmware version (not stock). We're planning to merge the fixes made in the beta version into the stock via OTA update. An ETA haven't been decided yet but I presume it should be in the next month or so.

Hi, one of our customer support agents (Francisco) is on leave at the moment so replies may be a bit slow these two weeks. But if you can provide your ticket ID, I'll be able to assist you.

There is another way to use a script to flash all OTA images in fastbootd mode, but this needs more fine tuning. Same method stated above also works with GMS build, but still need testing too. I'm working with beta-testers to ensure everything works before I publish here.

Yes, you can. I'll list the general steps below, let me know if you have any questions: 1. Unlock bootloader first by following the guide here. 2. Then, flash the GMS-less recovery.img by doing: adb reboot bootloader fastboot flash recovery recovery.img 3. After that, reboot your Pro1-X to recovery mode. On dead Android logo, use button combo : Power + Volume Up adb reboot recovery 4. Use Volume buttons to navigate the menu to select "Apply update from ADB", and use power button to select. 5. We will now use ADB sideload to flash the "“merged-qssi_bengal-ot

There is a GMS-less Android build available. I updated the G-drive link in here: I suggest using QFIL method to flash rather than adb sideload. Good luck!

We can ship a new Pro1 screen to you as soon as we can confirm your order ID and address. The cost would be £149 + shipping fee (I can simulate a shipping fee for you if you can provide your address). For the return/repair process, after we received your Pro1, it should take no more than a few working days to get everything sorted (depending on our backlog), then an extra few days for shipping back to you. We don't charge you for looking into the device, but if parts are needed for replacement, we will quote you. In this case, I speculate the problem could either be caused by a broken scr

Yes, you can superglue the "Z" key back on the keyboard. But please be careful when you do so, you must not glue the sides of the key as you won't be able to press it... Please check the image I've attached, drip a small drop of superglue on the tiny circle on the keyboard (marked red), and place the key back on. Good luck 😄

We have spare Pro1 screen in our UK office which we can ship to you directly. But I can't promise this will fix your issue as we don't know the root cause of this. If you'd like, you can submit a ticket to info@fxtec.com and we can initiate a return/repair process to have a look?