divstar

EDIT: Sold. Hello, I decided to sell my Pro1, too. I prefer to sell it in Germany only. If you want to bid or buy: https://www.ebay.de/itm/F-x-tec-Pro-1-128GB-Schwarz-Ohne-Simlock-Dual-SIM-6-Display-QX1000/373198744195 Not sure how the price is, so if it doesn't sell for this price, I'm gonna lower it. Please: when I posted it on ebay-kleinanzeigen, I got like 30 messages from people supposedly wanting it and asking me to deliver it to the UK. I won't do it unless you are an active member on here. In this case I might lower the price by around 75€ compared to the buyout pri

So ... last update: after applying some regular minor system update (58 megabytes) and a restart, the touchscreen started working again. It seems everything works now as expected, though it is weird I had to do something in order to be able to use "fastboot set_active a". Edit: locking it again (as it was supposed to be), worked, too. Why? Because in general I'd like to be able to use banking apps, that might not work otherwise. Thanks everyone for their efforts! Also: locking the phone erases the data.

Alright: so in order to repair it - sort-of - I had to use a certain package. After that I was able to do "fastboot set_active a" and reboot - AND it started booting again. I've still got another problem: somehow the touchscreen of the display does not work at all (hardware keys do though - don't ask me why). I'm gonna research more and since this won't be my daily driver anymore, I might as well just try SailfishOS or the likes. Anyhow: a massive thank you to @tdm and @EskeRahn - wouldn't be able to make it even this far without you!

Just for the sake of voicing what I have tried and done: Stuck in Fastboot Mode (probably after the last update) Booted into EDL-Mode (ABL/XBL using keys, 3rd option in tdm's instruction guite) Flashed while keeping data --> one of the boot partitions still was marked "not-unbootable:yes" Flashed without keeping data --> stats-wise everything looks fine to me --> Phone does not yet boot into anything else than Fastboot Mode and EDL-Mode (upon powering off and restarting into EDL-mode). If anyone attempts to use Q Flash Tool, I recommend the following:

So.. "fastboot --set-active=b" sadly does not work: $ ./fastboot.exe --set-active=b Setting current slot to 'b'... FAILED (remote: Slot Change is not allowed in Lock State ) finished. total time: -0.000s I cannot mark it as active due to being in a locked state. Recovery mode does not actually boot into recovery; instead it boots into the same bootloader menu. I guess I will give a full flash a try. It's sad, because I had some nice pictures there that I didn't share, because I didn't think this device would break. It's really a pity considering this device is not even one yea

Alright.. I did get Q Flash Tool to flash the phone. I did chose to "keep data", though, because I still have hopes on recovering the pictures and videos I had taken... Unfortunately after it automatically restarted, it went back into fast mode... This is the result of fastboot getvar all after flashing: (bootloader) hw-revision:20001 (bootloader) unlocked:no (bootloader) off-mode-charge:0 (bootloader) charger-screen-enabled:0 (bootloader) battery-soc-ok:yes (bootloader) battery-voltage:4174 (bootloader) version-baseband: (bootloader) version-bootloader: (bootloader) erase-block-

I am sorry - could you point me to the fastboot method? I only found But it does not work, because I am apparently not allowed to flash, unlock, set_active or anything else for that matter, meaning I am stuck. I just wish it would boot into the system as it did before ... Edit: therefore I am trying with EDL. I set up connection for QUSB__BULK to WinUSB as required. But whenever I try to flash, I get either "Connection timed out" (non-elevated qfpkg_gui.exe) or "Unknown error" (elevated qfpkg_gui.exe). I don't suppose there's a log to know what caused the error? I'll keep

@tdm - I must confess I don't exactly know how to do it.. but now I could boot into QDL (EDL) and it shows properly and Q Flash Tool detects the device. Let's see if I can fix the phone now. Hm.. flashing with Q Flash Tool still does not seem to work: Apparently the connection timed out? It's weird though, because after pressing the "flash" button, it showed this dialog just after a few seconds... Edit: on my Laptop it says "Cannot open device" instead:

@tdm: I will try a couple of combinations, but is it generally possible for it to become an EDL connection within the following screen at all?: I ask, because I am stuck and no matter what I chose, I always end up in this screen. Edit: I tried running lsusb each time I rebooted into a different mode ("boot to QMMI", "boot to FFME", "recovery mode") - the fastmode is pretty much the only mode I currently have :x . I don't even know how I ended up with it - I did not even attempt to flash anything...

@tdm: I have tried "lsusb" on my Ubuntu set up. It says: Bus 002 Device 004: ID 248a:8363 Bus 002 Device 005: ID 0951:16da Kingston Technology Bus 002 Device 003: ID 04f3:249f Elan Microelectronics Corp. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 18d1:d00d Google Inc.

@EskeRahn do you think it's even possible while my phone is stuck in that bootloader screen? After all only "fastboot devices" shows devices - while "adb devices" does not...

@tdm thank you very much for your work and replies! Sadly I cannot get http://files.nwwn.com/android/pro1/factory.html to work. I am not entirely sure why. Since my Windows 10 Laptop relies on a hub and USB3, I decided to go with my Ubuntu Server-PC. The following command works and I am able to "reboot" the device - to no avail though: [sudo] Passwort für remoteadmin: dc4648e9 fastboot However, Q Flash Tool does not see a device attached even though I ran it with elevated permissions: Also, adb devices does not show a device. I suppose that's beca

remoteadmin@...$ sudo fastboot getvar all (bootloader) hw-revision:20001 (bootloader) unlocked:no (bootloader) off-mode-charge:0 (bootloader) charger-screen-enabled:0 (bootloader) battery-soc-ok:yes (bootloader) battery-voltage:3950 (bootloader) version-baseband: (bootloader) version-bootloader: (bootloader) erase-block-size: 0x1000 (bootloader) logical-block-size: 0x1000 (bootloader) variant:MSM UFS (bootloader) partition-type:fsc:raw (bootloader) partition-size:fsc: 0x1000 (bootloader) partition-type:fsg:raw (bootloader) partition-size:fsg: 0x200000 (bootloader) partition-type:modemst2:raw (

Thank you for your reply! But it does not work, because "Flashing Unlock is not allowed". What I really want is to boot back into the regular image... I suspect the last regular update to have broken my phone and thus it does not enter anything except the bootloader no matter what I chose there... Edit: of course I'd love to keep my data, but if it isn't possible, I would rather get the phone back to work instead of just being sad. If it means losing the data, I am in. Though I don't really want to flash anything - I didn't want to in the first place. I was on regular stock ROM and h

@is: do you happen to have more details? I ended up being stuck in bootloader screen and I cannot flash anything, because the bootloader is locked. I did not try to flash anything - when I picked up my phone in the evening, it was stuck in this screen. I wish I wouldn't have to wipe my data partition, but I have tried a lot, but because the bootloader is locked (and I also get no option to e.g. draw the pattern - which I do know), I am stuck.. nothing is booting. Do you happen to know what can be done to fix this? Preferably without losing data (but if it's only possible with the data bei

Hm.. I tried flashing, but it says: target reported max download size of 536870912 bytes sending 'boot_b' (65536 KB)... OKAY [ 2.088s] writing 'boot_b'... FAILED (remote: Flashing is not allowed in Lock State) finished. total time: 2.089s remoteadmin@base:/mnt/storage/Temp/QX1000_user_20191028191838_0a493a1_Fastboot$ So .. I cannot flash? I am stuck in bootloader and I cannot chose to unlock it (I know the pattern). Any help here is greatly appreciated.

So .. I am stuck with the same problem. I have not attempted to even flash the phone at all. I suppose, that the last system update (in contrast to most others it did contain information on what it is going to update) might be the culprit. My screen is nearly the same as the one @cjacksonz has on his picture. No matter what I chose ("Restart bootloader", "Recovery mode", "Power off", "Boot to FFBM", "Boot to QMMI", "Start"), I end up at this very screen cjacksonz showed in the first post. If I detach the USB cord, "Power off" turns off the phone (otherwise it restarts the phone). I h

Me, too. I however didn't map anything to a "double-press". It just so often happens that when I try to power on from standby, the camera starts.

I repaired that screen on my pro1. Since I am by no means a pro, I didnt really get it right the first time and had to reglue it. It is about 1-2 hour(s) of work - you have to remove aby preexisting glue very well. And it takes time and effort. Removing and attaching the screen is pretty easy if you know how (or watched enough material on that). Elephant U screen works as I pointed out in my thread. The problem is we don't know if that's the only thing that broke. Also: by sending a SMS with a certain code (PIN I think) one can enter the device in order for USB connect

No problem there... ✂️ exist for a reason 😄.

You just did so - pollute the thread that is. Placement of buttons and your unwillingness to install an app to prevent round edges from responding is your personal preference. Same goes to the bloatware you call "UI". Anything other than stock android with the possibility to install your own launcher sucks in my eyes. Fixing errors without the knowledge of software is generally next to impossible if they are software issues. That's like wanting to handle lawsuits against you yourself: you can do it, but if you don't know your way around the laws, you won't really get anywhere.

Mediatek SoC kills it for me.

Works just fine. Most menus (context etc.) stay white though. Also there's a plugin for turning white pages into dark(er) ones.

Honestly, I just think you wanted to vent. So it's alright. While the phone indeed does have some mistakes, most of them can be worked around and if you want a proper phone with a keyboard - the pro1 is currently as good as it gets (I still have my BB Priv, but due to a hardware lock I cannot root it and so I'd have to use an OS, which is heavily outdated). I also paid about 720€ and while some errors do annoy me a bit, I use this phone as my daily driver and it works as expected. While venting is okay, you don't even seem to be interested in fixing the issues you have with the phone

I've been using *#*#4636#*#* to check some network settings.