david

The firmware download finished, so I tested your tool, selecting the "No Write" option, so that it wouldn't actually write anything to flash. I am using the 20191203 firmware. I got this error: That is with the driver changed to WinUSB: So maybe this is why the other EDL tools weren't working too. Maybe there is something wrong with my computer. Have you encountered this with any other users?

@tdm, on your web page for the tool, you wrote, "Please note that Qualcomm has an official EDL driver that will install by default. The official EDL driver is not compatible with this programming tool. It must use WinUSB." Can you explain more about why this is? I figured I'd test your tool to make sure I can connect to my phone properly *before* some future incident where I will need to use it. While I was waiting for the firmware to download, I grabbed some other tools online. For all of those, it *seems* like I have to leave the default Qualcomm EDL driver in place. I'm using Wind

Sorry, I should have mentioned that real pictures would be valuable, because the parts could have been changed since the photos were taken for FCC licensing. We know the flex cable and flex cable connector were change at some point in the testing phase. The USB port is supposed to be modular, not soldered, yet the FCC photos show a soldered type. ADD: I'm hoping they found some extra long, pre-existing flex cable, that other phones use, and used that. The fact that they said they switched the cable and connector after initial testing gives me a little more hope that it was something t

@FlyingAntero, since you will be taking your phone part way apart anyway, which I believe voids the warranty, if you have a chance to take photos of both sides of the battery, that would be very helpful in possibly finding a source online where we can get them. I realize you are replacing the screen, and might not need to open the bottom, but I'm just mentioning it since you will be doing some surgery anyway. Also, close up pictures of the flex cable, flex cable connectors and USB port would all be valuable, as those are parts we might want to replace over time and currently don't know w

Yeah, I saw that too (online). Clear as mud. 😕 Seems you might be charged with a crime if a police officer sees you sneezing into your hands or not covering it at all. Or shaking hands. Pretty drastic order. The part about sending homeless people indoors seemed counter-intuitive.

I haven't noticed a single random reboot. I *might* have had one early on, but my brain could be confusing that happening to me vs reading about it with someone else. :-) I'm on stock, though, and I also did a factory reset at one point. I used to have reboots fairly frequently on my Relay 4G phones with Cyanogenmod and whatever apps I was using and constant memory/storage swapping, due to low available RAM. I have hundreds of apps installed on the Pro1. Even though I don't use all of them, there are probably quite a few background processes. It could be some app I don't have ins

It is more fragmented in the USA. Big cities generally have all the providers, but even there, some may have more frequencies/bandwidth than others. But once you get outside of cities, there can be vast areas with very poor coverage or even no coverage.

I installed it by searching for it under "Downloads" in Magisk Manager and installing it from there.

I forgot to report that I got them too, last week or the weekend. They are definitely vinyl too. You have to be careful taking them off the sheets they are stuck to or they stretch and then don't want to stick anymore. I'm all set...now I just need about 160 Pro1s. That many phones should last me until I'm non-operational....unless I reach escape velocity and stay on the right side of the life extension curve. Even then, at 2 years for each phone, I figure I'll be good for a while. Now to find a box on the side of the road that fell off the fxtec truck....

Does your LOS + Safety Patch no longer pass the safetynet check in Magisk Manager?

I meant stock firmware, because I forgot you were talking about LOS. But the version of the LOS build helps others to compare too. Try the safety patch that @Craig mentioned.

Well, yes, some of those high proof types will do it. Maybe a little more expensive than isopropyl alcohol. Lol

Strong enough to feel good, not strong enough to kill the virus. 🍸😁

Which version of firmware and which apps and which safetynet check app?

As long as you follow the instructions and you don't install anything that modifies the system partition, then you should be able to update via OTA. You just have to be sure to follow the proper steps before and after you do the OTA and don't reboot in between.

That's the correct option to pick. If you click on the notification that is present at this point in time, it will change to 0% for a while and then tell you when it is done, without the status bar progressing. Congratulations! That all seems to indicate everything worked as planned. :-) Thanks for sharing the details.

This was with OTA or by installing the update you downloaded via URL?

Yay! Congratulations! :-) My guess is "temporary glitch" or "Adaway".

Although it doesn't seem like you installed any apps between he 20200106 OTA and the 20200306 OTA, this thread might help: https://community.fxtec.com/topic/2532-ota-update-fails-after-using-magisk-root/ The steps @zurvan2 took might help you figure out if a particular app is causing issues. It does require you to go back to the factory firmware though, and then try the first OTA repeatedly (with a subset of apps added each time) to see which app is changing /system. Alternatively, you can try running this command from the shell to see what has changed in the last day or two or

Maybe adaway makes some changes before you even tell it to modify hosts. You could still try uninstalling it to see if the OTA will work. Maybe a reboot will be needed in between.

Did you install or configure any apps between the 20200106 OTA and trying the 20200306 OTA? If it worked on 20200106 and nothing was done between that and 20200306, then maybe the error isn't due to a change to /system. I know other people have gotten that error before, but I'm not sure if anyone reported that they got around it by clearing data on certain system apps or not.

After you disable Magisk in Magisk Manager, test with an app that requires super user to see if it is truly disabled.