VaZso

Have you tried Edge Null or a similar solution? For me, it has solved my problems with curved edge. However, I have also applied a case to its bottom...

Basically, I would like to flash the other phone which is not working and I think when it enters to EDL mode then it should work, so basically either the phone is faulty (it's flash) or there is some differences between phones which may result this tool to time out. I don't really wanted to enter EDL mode using my phone (I may do it using fastboot or the way you wrote anyways), just to check if the cable which should force the phone to enter EDL mode is working. However, it did not work even with my phone which is working. However, the phone I would like to flash using EDL does nothing if I try to enter EDL mode using the buttons you described. I think the phone hangs up during boot process before it would run the code which checks those buttons to enter EDL mode but it falls back to EDL after ~15 minutes.

Same for me. I still using it on minimal volume...

As far as I know, USB CDC-ACM has no baud rate option. So USB Virtual COM port (or ttyACM under Linux) is completely different than USB <--> RS232 converters like FT232, PL2303 and similar devices.

Somehow I could not get it work, although, theoretically the cable was built the way it should work. The other cable I have ordered is still not here and I think it will take a while because of current state here... Now I have tried the cable both ways with the same result. Maybe I should try it using another cable but I still did not want to destruct another cable and I am unsure if it may help... My phone works well, so yes, I wanted to find out why it does not work using my friend's phone and found out it seems to be also not working on mine. I have a home-made cable so it may be something undocumented (maybe in connection with the additional pins at Type-C side) or these phones do not have this option (maybe earlier or later models have it anyway). This is my own phone booting to charge mode, so Pro1 logo appears, then a charging indicator: I feel it is related in a way that the phone has not switched to EDL mode (also can be seen the same way at USB connection anyway). Exactly the same happened for me - I still hope that phone is not faulty but destructed its boot part somehow, thus falls back to EDL mode still before the first Pro1 logo appears (there is a delay of very close to 15 minutes anyway before entering EDL mode with that phone). Fortunately, charging works so time is not as limited as I thought first. I have mostly experienced with flasher under Linux because that is my main OS and I have the following experience looking at OS messages: When I press "Flash" button, it "immediately" disconnects at USB system then connects again... then waits a while, device disconnects again (I think it may not disconnect here), then for a very short time, program displays "Writing gpt_main0.bin to PrimaryGPT" message (remember phone is disconnected at this time) and when it comes up again on USB interface, program says the mentioned "Connection timed out" message. The "Writing gpt_main0.bin..." message is hardly noticeable because it immediately disappears and timeout message comes up. So I think maybe more delay or less delay (if any) may help somewhere. I mean I don't know what is the usual way how it should work, but I think the first disconnection may be expected behaviour (am I right?). I don't know what is the cause of second disconnection, but I think flasher program may wait too much here or too few after second disconnection. Maybe the above is completely wrong as it would be good to know what the program does when these disconnections happen. So if the program tries to reset connection or switch to other mode or upload something which reinitialize connection or anything else. What I find strange is the flasher seems to try writing gpt_main0.bin at a time the phone is not connected, which I am sure is wrong... but I have a feeling of the second disconnection is unexpected or if it is expected, flasher should wait till the device comes up again. If it is not too complicated, i may also happy to try a program which writes some debug outputs (may you compile a Linux version of it?). I haven't tried to examine it using wireshark but I may give it a try maybe this weekend.

I have experienced the same error message under Windows (using WinUSB) and "Connection timed out" under Linux. However, I was unsure if it is a problem with EDL state (as the phone falls back to EDL) or the phone itself. That phone is still with me (this is my friend's phone) so if you find something interesting, I would like to hear it. Also, I have tried to put my own phone to EDL mode using a home-made "deep flash" cable and it seemed to be not possible even though my phone has charging enabled when the phone is switched off so that icon has appeared and could not go to EDL that way... If anyone have any ideas, please share it with me.

I am also a developer of both hardware and software and I would not say that creating a phone from scratch is easy. You are right about the SoC itself does a lot of things but you should follow several considerations, select appropriate components and routing, so you have to have appropriate skills and experiences. Also, creating a phone from scratch can be relatively easy for an expert who is also familiar with multi-layer PCB design, but creating a good phone needs much more experience not speaking about good mechanical design and EMI / EMC considerations and the price of testing and certifications. In a project which has a microcontroller, accelerometer, GPS receiver and display, the PCB can be relatively simple compared to a good phone's PCB. On the other side, the main software can be complicated in other way (custom thing). Also it is much simpler to find an appropriate box or design the whole thing the way to fit in an existing outfit than to find someone who will do a custom box for you which has the appropriate parameters, dimensions and outfit - not speaking about the price of a more complex solution. Also, if you have a custom product, initiating the mass production needs different considerations and have potential problems. On the other hand, electronics are built from components, there are really clever solutions nowadays. Also softwares are built from components (existing components and own components and components written based on data sheets and so on)... so what are you call easy (simple) - as not being hard? Okay, it is not hard... but I would not call it simple even if it is simple for me. Every complex products basically built up on relatively simple parts (in detail) which results in a complex product. That is how an engineer builds up the project. So that way it can be simple, but the whole task together can be complicated especially if a relatively few people have to have the knowledge required. Anyway, not too long ago I had an old Rpi 1 in my hands and I have looked a bit of its PCB. It definitively works, but it is not a really good design... compare it with their later products and you will see a huge difference. So there can be a lot of differences between products even if all of them work. Creating something that works is one thing but do it right is another one, however, I haven't seen Pro1's internals yet... Building a plane is definitively not a one-man show or a show of a group of relatively few people. However, I think you should know these things and you just lost your patience...

It may also cause "random" reboots but it seems there is a problem somewhere in radio band switching which may cause reboot (there was a thread somewhere here where also another phone was mentioned which used to have the same problem on the same chipset). So it is not random but caused by certain circumstances. I had two unexpected reboots so far (since December) and both happened on the same road (motorway), same direction and near the same place where there are a few tunnels the road goes through. So some weaker signals are noticeable there. However, most of the times I traveled there it did not reboot. If somebody lives in a place where the coverage is similar, then this problem may come up more frequently which may be felt as random reboots. Edit: This problem exists in stock firmware but as far as I know, LineageOS is also affected as it is in a common part...

I don't want to restart your debate, just would like to write my own opinion. Those of high risks usually do some precautions. So they apply for vaccination and try to avoid to catch the virus. However, for this virus, there is no vaccination yet and it can spread very quickly and causes pneumonia not as the result of weakening the person's immune system but directly. The biggest and worst part of this whole virus I think is the very long incubation period. So if you are ill, you can do many precautions to not infect others... but if you don't even know you are ill (yet), then you don't really able to avoid to infect others. I think that is the most serious reason to do extreme precautions in general. Healthy system generally runs close to its limits in my country. If they are not do such restrictions, they run into their limits very quickly which would cause a lot of death which could be prevented if the amount of people would be not really high (unfortunately, they may easily reach their limits also if these restrictions applies but I hope I am not right). Even the strongest healthy system is not prepared to handle very high amount of ill people at once, especially not extreme cases which seem to be a really high chance caused by this virus. Unfortunately, even Italy has very serious bad weeks now and all what we want is to try to avoid a similar breakdown locally what these countries where the virus appeared earlier currently have. Remember, they were the first in Europe where this virus came up and we still didn't have real experience about it. Every other countries try to learn (more or less successfully) about how serious is the virus and how to avoid a high healthy problem. However, it will strongly affect economy so it causes a lot of non-health related problems to deal with.

I still had only two reboots on the same motorway and same direction where signal probably was very weak but the phone was in my pocket both times. After last reboot, I was on the same road once more without reboot...

Correct request. I hope F(x)tec will catch up production relatively soon and you will receive your product in the near future or at least you can find someone who don't need it or willing to wait a bit longer for a more polished software or any other reason. For me, I am really happy with my QWERTZ Pro1 what I use and I would personally buy it again so I hope you will also enjoy your Pro1 soon.

Just a question not related to your problem. Can you boot to EDL using a method of pulling data line to GND (using a button for example)? What problem you have when you try to flash the phone? It goes through but fails to boot then?

When the phone is unlocked and press power button for a few seconds, a menu appears where there is a shutdown option. Isn't it good for you?

I think he speaks about long-pressing the power button which will do a hardware poweroff and not a software one.

Is it also exists in LineageOS? I know stock firmware has this issue but I don't know if LineageOS also has it - we usually hear about issues in stock firmware I think.