Factory Restore Tool

[Whitey 8]

Hi @tdm. Is the CLI version still around?

On macOS M1 (ARM based), the GUI one doesn't like libpng built for ARM, so I tried to use the CLI, but the link appears dead.

Thanks!

[EskeRahn 5,580]

50 minutes ago, Whitey said:

Hi @tdm. Is the CLI version still around?

On macOS M1 (ARM based), the GUI one doesn't like libpng built for ARM, so I tried to use the CLI, but the link appears dead.

Thanks!

Unfortunately we have not seen @tdm active in here for quite a while, so I guess you should look for other sources (with a little luck someone saved a copy)

[Milky_Pimms 10]

Using fedora get this error.

 

Thanks for your hard work

(M_P)

Edited January 4, 2023 by Milky_Pimms
spelling

[pebert 98]

Hi guys

 

I had me pro1 in the drawer box for i while now since it won't boot.

Tried today to EDL flash it, everything seems good, device is detected as it should, flashing progress is going as it should. 

 

When flashing is done, i see the message that I can remove the device. 

 

But, it only boots in to fastboot, don't boot normally and won't boot to recovery. 

Any ideas? 

 

 

[Wunder Wungiel 9]

Have you tried the normal fastboot flashing method?

 

In most cases you don't need to use such an advanced and "low-level" mode like EDL. In most cases.

[pebert 98]

so, managed to bring new life in my beloved device.

 

1. disassemled the unit to accss and manually charged the battery, this stopped the strange boot loop.

(phone still only goes to fastboot)

2. instead of using my pretty new computer running win10 I connected it to my 13 year old laptop running Debian made it able to communicate in fastboot.

3. flashed original ROM via fastboot

(phone still only goes to fastboot)

4. (almost a bit embarresed to say but...) manually change active slot via fastboot. Now it boots 😁

5. flash Lineage again and change active slot once more, and now it's runninge perfectly fine again

 

 

[Hook 3,215]

7 hours ago, pebert said:

so, managed to bring new life in my beloved device.

 

1. disassemled the unit to accss and manually charged the battery, this stopped the strange boot loop.

(phone still only goes to fastboot)

2. instead of using my pretty new computer running win10 I connected it to my 13 year old laptop running Debian made it able to communicate in fastboot.

3. flashed original ROM via fastboot

(phone still only goes to fastboot)

4. (almost a bit embarresed to say but...) manually change active slot via fastboot. Now it boots 😁

5. flash Lineage again and change active slot once more, and now it's runninge perfectly fine again

 

 

Although I am primarily a Windows user (I have one main activity that uses Windows only software, so it is just more convenient to have everything in one place), I use Majaro on an old Thinkpad for all my ADB  and Fastboot stuff with my Pro1 an Pro1x.  It just always works. I recommend an old computer with Linux for any Windows user wanting to do a lot of flashing. :) 

[EskeRahn 5,580]

9 hours ago, pebert said:

2. instead of using my pretty new computer running win10 I connected it to my 13 year old laptop running Debian made it able to communicate in fastboot.

It is a known issue that it is quite picky on especially fastboot. Often a USB2-port works better. For me it does not work directly on any port on the laptop, but I got a Thunderbolt docking, and it works fine connecting to a USB3 port on that...

[agent008 248]

 

On 2/8/2020 at 1:10 AM, tdm said:

Hmm, so it looks like you are using Linux and you are rather anxious to get your device working.  I can't blame you.  🙂  Please try this test version of the programmer.  It is a CLI version, and it has the fix to flash xbl properly:

 

http://files.nwwn.com/android/pro1/qfpkg_cli.gz

 

And a smaller "base" version of the 20191028 package which does not flash system, vendor, userdata, etc.:

 

http://files.nwwn.com/android/pro1/QX1000_user_20191028_base.qfp

 

Please report back and let us know how it goes.  🙂

 

Hi all,

Does anybody have a copy of the qfpkg_cli tool? @tdm's file repository is gone.
After receiving and reviving my DOA Pro¹X via EDL using the linux "qdl" tool, I'd like to give my long dead Pro¹ a shot.

I can make it boot into EDL mode but @tdm's graphical qfpkg_gui tool on Linux just reports a timeout immediately after clicking the "Flash" button.

Unfortunately the power switch on this Pro¹ is shot after I replaced the screen on it for the second (or 3rd? don't remember) time. So it's kinda difficult to restart the phone to start the EDL sequence from the beginning every time. So, before I pull this phone apart again and try wiring an external power SW to reproduce the EDL boot sequence more reliably, I'd like to give the cli tool a try and especially check for any debug messages that might give me greater insight on what's wrong.

Thanks!