[Guide] PRO1, Restore to stock firmware using Fastboot method

[pebert 98]

 I have encountered an issue, my phone won't stay on fastboot mode, as soon as I send the first fastboot command (regardless if it's a "fastboot devices" or any other command the phone exits fastboot, shows the fxtec logo together with a small text in the upper left corner telling me that the any key will preform a reboot.  Just pushing one of the volume buttona it reboots back to LOS. 

Any ideas on this?

[EskeRahn 5,460]

10 hours ago, pebert said:

 I have encountered an issue, my phone won't stay on fastboot mode, as soon as I send the first fastboot command (regardless if it's a "fastboot devices" or any other command the phone exits fastboot, shows the fxtec logo together with a small text in the upper left corner telling me that the any key will preform a reboot.  Just pushing one of the volume buttona it reboots back to LOS. 

Any ideas on this?

The usual guesses would be PC, pc-usb-Port, Cable or port on the Pro1.
After upgrade to new PC last fall never got flashing to work well, and fastboot acts oddly too.

[pebert 98]

That's so Microsoft, I guess a Windows phone doesn't have any issues.

 

Will give it a try from my Linux machine instead, even though I'm sceptical that it will work, I'm running a Dell enterprise server, and that USB implementation/driver is a little bit "one of a kind"

 

//Per

[EskeRahn 5,460]

If I fiddle using unsigned drivers, I can get things to work, but not with signed drivers. And oddly Google's own drivers were still unsigned, last I checked....

ADD: See also this

[pebert 98]

Interesting reading, Maybe the easiest way is to boot from my previous harddrive with windows 10 then. 

 

[EskeRahn 5,460]

5 hours ago, pebert said:

Interesting reading, Maybe the easiest way is to boot from my previous harddrive with windows 10 then. 

 

Well at the least try that first, and if that works, you know the problem is at the PC side.

[pebert 98]

Fastboot flashing procedure went flawless under win10. Unfortunately the phone got stuck in a boot loop, changed the active slot, but still didn't boot. 

Did a EDM flash instead, so now the phone boots up as it should on stock software. 

 

 

[lockguy79 0]

On 9/7/2020 at 1:45 PM, divstar said:

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!

What was the package you used? I'm having this same issue...

[windows9g 0]

do we need an unlocked bootloader??!!

[Hook 3,020]

3 hours ago, windows9g said:

do we need an unlocked bootloader??!!

We probably need more information.

First, this is for the Pro 1, not the Pro1x.  Since this is your first post and you provide no information, just wanted to make sure you understood that,  The instructions for the Pro1x is here:

Second, if you are asking about flashing Stock Android, I am left to assume you are on another OS such as Lineage.  In which case, your bootloader is already unlocked as bad things happen if the bootloader is locked on another OS.