tdm 2,322 Posted December 18, 2019 Share Posted December 18, 2019 (edited) Please note, this is not an official FxTec tool. It is my own creation. FxTec should not be expected to support this tool or any damage caused by its use. This tool will allow you to restore your Pro1 to a factory clean state no matter how badly it is messed up. You may use it to restore a "bricked" device or just load the latest firmware. You can find the software and detailed instructions here: Factory Restore for FxTec Pro1 Please report any issues here. Edited December 19, 2019 by tdm 8 12 Quote Link to post Share on other sites
Craig 1,435 Posted December 18, 2019 Share Posted December 18, 2019 (edited) Ubuntu 18.04LTS based: ./qfpkg_gui: error while loading shared libraries: libjpeg.so.62: cannot open shared object file: No such file or directory I assume I just need to install a dependency (maybe libjpeg-dev? or libjpeg62? lotsa this stuff in repos), or is this an appimage? aptsearch.txt Edited December 18, 2019 by Craig 1 Quote Link to post Share on other sites
Benni 183 Posted December 18, 2019 Share Posted December 18, 2019 Use: apt search libjpeg.so.62 1 Quote Link to post Share on other sites
tdm 2,322 Posted December 18, 2019 Author Share Posted December 18, 2019 10 minutes ago, Craig said: Ubuntu 18.04LTS based: ./qfpkg_gui: error while loading shared libraries: libjpeg.so.62: cannot open shared object file: No such file or directory I assume I just need to install a dependency (maybe libjpeg-dev? or libjpeg62? lotsa this stuff in repos), or is this an appimage? You need libjpeg62 (sudo apt install libjpeg62). aptsearch.txt 1.95 kB · 1 download 1 1 Quote Link to post Share on other sites
Craig 1,435 Posted December 18, 2019 Share Posted December 18, 2019 (edited) On 12/18/2019 at 2:55 PM, kontakt said: Use: apt search libjpeg.so.62 I tried that first, didn't find it. Anyways thanks both for quick response. Edited December 20, 2019 by Craig 2 Quote Link to post Share on other sites
matf-kabouik 414 Posted December 18, 2019 Share Posted December 18, 2019 Great. And very encouraging to see growing support for the Pro¹. 3 Quote Link to post Share on other sites
Craig 1,435 Posted December 20, 2019 Share Posted December 20, 2019 I only get this when I try to flash... rebooted multiple times... 1 Quote Link to post Share on other sites
silversolver 849 Posted December 20, 2019 Share Posted December 20, 2019 I read somewhere that someone had a problem with flashing until they used a USB3 port. Are you on a 2? 1 Quote Link to post Share on other sites
silversolver 849 Posted December 21, 2019 Share Posted December 21, 2019 @Craig I read in another thread that you were bricked. Could you tell us how you got there so we don't do the same thing? 1 Quote Link to post Share on other sites
Craig 1,435 Posted December 21, 2019 Share Posted December 21, 2019 Don't use SystemUI tuner. 1 2 2 Quote Link to post Share on other sites
elvissteinjr 355 Posted December 21, 2019 Share Posted December 21, 2019 Some stuff in SystemUI Tuner does work, but it's danger zone. Test your changes in an emulator perhaps. Though even there I had the same setting not break as hard (System UI just kept crashing and could still use the screen to revert the setting). Stuff like forcing immersive mode or hiding status bar icons seem to work. We always think we know what we're doing, but stuff sometimes actually ends up going wrong after all. 1 Quote Link to post Share on other sites
Craig 1,435 Posted December 21, 2019 Share Posted December 21, 2019 It did work for applying immersive mode. But I don't think I'll be experimenting with any any more untested tweaks. What I did particularly that caused the crash was set it to only display 1 quicklaunch icon. My actual goal was zero, but saw that setting and decided to try just to see what it did... oops! 1 4 Quote Link to post Share on other sites
tdm 2,322 Posted December 28, 2019 Author Share Posted December 28, 2019 On 12/19/2019 at 7:32 PM, Craig said: I only get this when I try to flash... rebooted multiple times... Sorry for the late reply. Did you get the tool to work for you? I can try to help if you are stuck. 1 Quote Link to post Share on other sites
Craig 1,435 Posted December 28, 2019 Share Posted December 28, 2019 I did not get it to work; always timeout. But I'm not stuck, fastboot worked. 1 Quote Link to post Share on other sites
tdm 2,322 Posted December 28, 2019 Author Share Posted December 28, 2019 4 minutes ago, Craig said: I did not get it to work; always timeout. But I'm not stuck, fastboot worked. Okay good to hear you got your device working. One problem I've had is finding the correct programmer binary for all the devices out there. My device will only accept a very old programmer binary, not the production one. I suspect you may have a similar problem. Do you have a retail device or a pre-production device? 1 Quote Link to post Share on other sites
Craig 1,435 Posted December 28, 2019 Share Posted December 28, 2019 Retail 1 Quote Link to post Share on other sites
tdm 2,322 Posted December 28, 2019 Author Share Posted December 28, 2019 (edited) 18 minutes ago, Craig said: Retail Thanks. Do you mind testing a new package? I'll make it significantly smaller for the test and you don't need to actually write to your device. Edit: and which OS are you using on the host PC? Looks like Linux? Edited December 28, 2019 by tdm 2 Quote Link to post Share on other sites
Craig 1,435 Posted December 28, 2019 Share Posted December 28, 2019 I'd be happy too, but currently traveling for holidays (without pc), so it wouldnt be til later next week... 2 Quote Link to post Share on other sites
tdm 2,322 Posted December 28, 2019 Author Share Posted December 28, 2019 10 minutes ago, Craig said: I'd be happy too, but currently traveling for holidays (without pc), so it wouldnt be til later next week... Okay that works for me. I have limited time myself until January 6. 2 Quote Link to post Share on other sites
devyl 9 Posted December 30, 2019 Share Posted December 30, 2019 (edited) i have the same problem on macOS. on Windows the tool tells me "Cannot open device" 😞 at the moment i cant even boot my pro1 into bootloader or fastboot. but the tool it self says "device detected". i have the production device. Any ideas? Edited December 30, 2019 by devyl 1 Quote Link to post Share on other sites
tdm 2,322 Posted December 30, 2019 Author Share Posted December 30, 2019 4 hours ago, devyl said: i have the same problem on macOS. on Windows the tool tells me "Cannot open device" 😞 at the moment i cant even boot my pro1 into bootloader or fastboot. but the tool it self says "device detected". i have the production device. Any ideas? I'll get you a new package to try soon. 1 1 Quote Link to post Share on other sites
tdm 2,322 Posted December 30, 2019 Author Share Posted December 30, 2019 @devyl @Craig here is a package that has the "old" programmer that works with my prototype phone. I've excluded system, vendor, and userdata partitions from the package to make it smaller (77mb vs 1.5gb). Please let me know if it works. If it succeeds, you should be able to get to the bootloader and then flash system and vendor using fastboot. QX1000_user_20191028_oldfirehose_base.qfp 1 1 Quote Link to post Share on other sites
devyl 9 Posted December 30, 2019 Share Posted December 30, 2019 (edited) works, but my problem is not fixed... it still doesn't boot - even not to the bootloader. could you add all that is in /dev/sdb (bootloader)? Edited December 30, 2019 by devyl 2 Quote Link to post Share on other sites
tdm 2,322 Posted December 30, 2019 Author Share Posted December 30, 2019 5 minutes ago, devyl said: works, but my problem is not fixed... it still doesn't boot - even not to the bootloader. could you add all that is in /dev/sdb (bootloader)? Okay good to know that it works. I'll update the main package later today. That package has all that is needed to get into the boot loader. It only excludes system, vendor, and data. How are you trying to get into the boot loader? You should start with power off, then hold the volume down key, then press the power key. Once you see the boot loader screen, release the power key first and then release the volume key. If that does not work, tell me exactly what you see in the screen (if anything). 2 1 Quote Link to post Share on other sites
devyl 9 Posted December 30, 2019 Share Posted December 30, 2019 i never see anything on the screen; i even could not turn it off 😞 i tryed with volume down (holding) and pressing power... nothing happens, never. but the flash tool still see the "reboots". 1 Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.