Leaderboard

What the heck happened to delivering all pre-orders in January? If they just dispatch by that time we will only see devices in mid to end of February.... I am getting really sick of this. If I don't see a device this month I'll refund and be done with it.

Yea, the waiting is not much fun... Soon your life will be restored.

At least remove the hairs and give the screen a wipe on your shirt or something before taking a picture, please!

Then say Pro1 three times out loud (or once with a scottish accent)

As much as I love root access, I'll probably do without it for awhile on my clack when it arrives as it sounds like there's currently a certain amount of disruption in making it work. Perhaps @Waxberry will get the software people to add the root access switch in developer settings like LOS has. Not that this is terribly important, but I know I would appreciate it, and I'm sure I wouldn't be alone.

Nice. I'm (among other cables) still awaiting this one https://www.ebay.co.uk/itm/362332003394 And I hope it will be slightly more compact. The images/rendering are not that clear on the size, but it looks very compact.

https://www.fastcompany.com/90446946/this-wacky-smartphone-proves-why-so-many-phones-look-exactly-the-same

Okay so I bought this -> https://www.ebay.com/itm/Flip-PU-Leather-Magnetic-Card-Cover-For-Huawei-P20-P30-Mate-20-Lite-Pro-X-Nova-3/123548882300 I ordered one in black for the Huawei P20 Pro based on EskeRahn's website, but one that shipped to US sellers (and didn't look as maximally cheap as possible). The case arrived today, and I made the following modifications (pictures at end). It supports my use case of protecting the screen from scratches and hopefully some drop resistance, while getting out of the way for keyboard use or camera photos. Pretty, it is not, but I can n

Root switch would be convenient, though probably not allowed on Google's Android indeed. Magisk does more than just simply provide root though. On that note I'd like to urge F(x)tec to provide updated flashable images along the OTA updates or at least updated boot.img that can be patched with Magisk later. It appears to be not technically impossible to scramble together the image file from an intercepted incremental OTA archive and the initial image, but I don't think there's been success in this yet. Root is technically not an advertised feature like the alternative OS support, but I hop

I'm guessing the same thing that happened to delivering in July. Or 'Summer'. Or 'within a couple of weeks of payment'. Or early November. Or mid November. Or by the end of November. Or early December. Or "definitely by the 20th of December".

Every day I wait a small piece of me dies.

That review lives somewhere I don't. Shipping incomplete software? Wow when was the last time you got something which does not receive patches the following months? Sure most smartphones work great from the beginning, but they all have the same 3 components... The only valid point here is the FP sensor which is indeed horrible.

Just to complete with a follow up, the error was rooted in using USB 3.0 Port. As soon as @Astaoth used a USB 2.0 Port via a docking station, the flashing process worked as expected

Putting it in a bag of dry rice or using desiccant products won't require you taking it apart. They just make the air very dry, hence removing the water that made its way inside your phone. If something didn't short circuit and create physical damage, removing the water should allow it to work again.

Hurray! That's awesome! What a great leap in production 😄

Black Beauty arrived today:

Mine is 225.

Is it some sort of tradition to post cases covered in gross bits of dirt, mysterious white flecks, and hair? 🤢

Yes, I think there was one batch that didn't go to London first, but was sent directly to the European customers from our Hong Kong warehouse. We are legally required to pay VAT in Europe, which we already charged our customers for, therefore we are pre-paying the duty for EU-based customers. I am not sure if this is happening again though, as we'd likely continue shipping to London first and then to customers. Either way, customers are unaffected, and if there is a problem, let support help you with it - info@fxtec.com.

You know you can just paypal fxtec some money if you so badly want to go above and beyond to help them? Taking a net negative (waiting longer AND paying more AND giving them a zero interest loan in the meantime) is literally the same as giving them money, so you might as well just do that..... If you want to give fxtec the "absolute best future possible" just give them all your money. You can't put out absolute statements like that and then not follow it up. There is no line in the sand if you want the "absolute best future possible". Why not work for them for free, too?

For anyone else wanting to be able to intercept OTAs, here is what I've posted before. https://www.thecustomdroid.com/how-to-capture-ota-update-url-android/ At least one person was able to use the directions to get the URL: And here are the directions on how to flash it, in theory. The problem is that users have reported that we don't have a real recovery with the Pro1 and I'm not sure if TWRP is to the state where it can do this either. https://www.theandroidsoul.com/how-to-install-ota-updates-manually-using-recovery-and-adb-sideload/ And no idea what this would d

Bluetooth keyboards are THIS:

I think salted water is one of the worst thing one can have inside a phone - basically because it conducts and it causes corrosion and that is the cause why you need to disconnect battery. If you are lucky, the phone may work after cleaned, but there is no guarantee if it will ever work again. So that is why I would disassemble it to disconnect at least the battery - so to have a chance for it to work again. Otherwise it may also "eat" the PCB.

A single water drop that comes in the wrong place can cause havoc on any device though of course very unlikely. If you were unlucky and the snow was contaminated with salt from the road, it can have caused more problems than pure water by itself. I have used the device in very mild rain (took an incoming call), so it not just the first water drop it sees that kills it.

I feel this way exactly. Well put 👍

You not seen the pictures of his phone? 😂

Yes. That is the difference between real life and advertising images. 😇

A small hint for punching the mic-hole. Make a tiny hole first from the inside, to get the place right. And then punch from the outside, against a hard piece of wood, to get reasonably neat rounded holes

That is what I did. I'm after maximum protection and since I've done several cutouts to weaken the structure of the case, I want to add any strength back I can.

Well there is reduced tear to the usb port. But the long shot might again be in advantage to the manufacturing. Cheaper water proofed devices. Just one slab glued together. No ports at all. No repairability at all. The same reasons they prefer a device without a keyboard. It is again something big marketing campaigns try to force into our habits. Luckily our planet has inexhaustible resources for battery, so it does not matter that it literally fries yours ... Oh wait!

Lol, always the zero interest loan argument. What loan does your bank give you? Probably also zero. If you have a lot of money they may even give you a negative loan atm. Just paying them paypal money does not help them introduce their logistic, forum etc and even more important: it does not help in getting future investors on board!

I had also ssumed this to mean they hope to manufacture the remaining ~60% before the factory shutdown, after 30% are shipped to customers next week (with the assumption 5-10% have been delivered or will be this week (which includes all three batches we know about and the two retailers we know about)).

So clearly something is odd with the way it processes rotation information, perhaps a bug in the magic added for the keyboard slider. I'm certain that it's all in software and will be resolved in time.

I think I may end up with LOS in the end too, but I do want stock to be good out of the box. Anyways I've extracted the new boot.img from the ota payload, and just need to patch it with magisk manager. Unfrotunately, I'm running sailfishos right now so need someone else to do that... I've put the unpatched new boot image here: https://www102.zippyshare.com/v/vdReLyxO/file.html Will update this thread with a patched version soon as I can find someone to do it (hint hint Hook). update: magisk wouldn't patch it. unsure why. maybe I extracted wrong.

So, new OTA update today and installation fails. Lol. I sort of knew the fastest way to get an OTA published was for me to root. Now I have to figure out what I need to do. I suspect I have to flash old boot.img. Probably need to uninstall Magisk first. @Craig @netman or anyone else, any advice?

You do realize people's situations can change over time? When I pre-ordered in early 2019, my financial situation was different from when they asked us to pay in August. And I would've cancelled my order if my friend hadn't offered to lend me the money. And even now my situation is different from back in August. That said: I'd rather cut back on other things than not have a slider keyboard phone. I've been waiting for this for a decade. I imported and used outdated US phones in the past because touchscreen keyboards are a nightmare (for any kind of purpose). I used the Galaxy S4 with a BT

Yes, I removed the oldfirehose_base file. That was just for testing. Both of the qfp files linked from the web page have the old firehose now.

I'm a bit confused. I just downloaded the 20191028 file successfully. The index links to the LineageOS page and the Factory Restore page. But if you followed the link in the OP of this thread you should land on the Factory Restore page directly. The links for all the restore files are there and should be working.

My web page answers that, mostly. There are situations where the device must be disassembled to enter EDL, but they are exceedingly rare. Almost always either the PBL will fail to load XBL and panic to EDL (this is what devyl 's device did), or XBL will load and check for the data short on the USB connector that the EDL cable provides. So really you only need to disassemble the device if XBL is functional enough for PBL to load but not functional enough to make it to the USB check.

About that... Can we always get into EDL mode without disassembling the device and if not, how deep do we have to dig in trainwreck scenarios? Or do you just need a special cable in such cases?

Wait, what?!? What shop? Where you bought it? As in you returned it and are done with it for good, or is this just temporary? I hope it's temporary as @tdm was/is working diligently to get this corrected for you, and the solution might very well help everyone. @tdm I have been watching and reading this issue with interest, as always thanks for all your support!

@devyl I have added the 2019-12-03 package. You can try it to see if it works.

Hard reboot is done by holding the power button down for about 10 to 15 seconds. But I suspect that won't work either. I can make a package for the 20191203 build, perhaps that might work?

Well, I am looking at the programming files and it shows that it's writing both xbl_a and xbl_b from xbl.elf. So that part should be good. The files themselves should be good, I have flashed my device with these bits on multiple occasions. So I am a bit confused why this isn't getting you to the bootloader. You should at least get a splash screen no matter whether you hold the volume key or not. I've updated the full firmware package on my website to use the older, working programmer. The new md5 starts with 6b0... You can try downloading that instead of

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).

I'll get you a new package to try soon.

Okay that works for me. I have limited time myself until January 6.

I'd be happy too, but currently traveling for holidays (without pc), so it wouldnt be til later next week...

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?