Jump to content

Pro1X - Stock Android OS (Build Number: v2.1.2_20220707)


Recommended Posts

My backup persist does have keys in it.  My persist flashed onto the device (for now) does have keys in it.  restorecon relabeled everything.  After a reboot, I still don't have attestation.  restoredon did fix the sensors though.

I've never touched the backup persist.  Even my read-only explorations of the image have been performed on a copy.

 

 

  • Thanks 2
  • Sad 2
Link to post
Share on other sites
  • Replies 83
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

NEW Version of guide here   Below the original text: (above inserted by EskeRahn)     If you're reading this, it seems like you miss the good old Android OS or you've acciden

F(x)tec will release flashing instruction using Qulcomms QFIL software on windows soon. The unofficial method to flash the provided EDL images that testers used on linux would be: Install EDL-T

Same situation here.  I had broken sensors, but working attestation, but then when I reflashed my persist backup, which ostensibly valid keys, I lost attestation.

Posted Images

All of this, despite being a completely different matter, reminds me a bit of an old Chinese 'Chuwi' x86 tablet/convertible that came with an Android + Windows dual boot setup which was so fragile that even just looking at the incredibly complex flash drive partitioning "from the outside" with a pendrive-booted Linux left the system in a state so that Android wouldn't start anymore. In the end I repartitioned the flash drive, the 64 MB of which had been too small to share it between Android and Windows anyway, and installed Linux Mint. Should have done that earlier...)

Link to post
Share on other sites
10 hours ago, mosen said:

However, i understand correctly that you did alterations to all of your backups by copying into all of them at some point?

No,  I always made a copy and modified that copy. One of the originals was only ever copied,  while the other was mounted read only at some point to copy from the backup into the stock image in an attempt to put the keys on the stock image.

Regardless, I will try restorecon and see what happens 🤞

Edited by sspiff
  • Like 1
  • Thanks 1
Link to post
Share on other sites
On 8/4/2022 at 3:43 PM, Casey said:

NEW Version of guide here

 

Is this guide safe to follow? If I (theoretically, since my device has yet to be sent) flash a custom ROM and then use these instructions to flash stock, will every feature work afterwards, like attestation and/or sensors?

Also, where can one get a legal copy of windows (like an .iso, I suppose) to run in the mentioned VM setup? What VM software is recommended (I am on Debian Sid)? And is there any special steps one need to take to make this work on the VM, or will it simply work out of the box?

Edited by toast
Link to post
Share on other sites
1 hour ago, toast said:

Also, where can one get a legal copy of windows (like an .iso, I suppose) to run in the mentioned VM setup? What VM software is recommended (I am on Debian Sid)?

As a fellow linux user, i advise to use the edl.py method explained here.
Testers are using this method since month intensly. The windows QFIL instructions are a recent thing to make full reflash possible for windows users. Never tried the QFIL method myself. Always used edl.py as of yet and had no problems.

But mind to make backups before flashing anything.

  • Thanks 3
Link to post
Share on other sites
2 hours ago, mosen said:

i advise to use the edl.py method explained here.

Actually, I have already gotten edl fixed on my computer in preparation (atleast in theory, as I have been unable test it yet), but thanks for the tip 🙂 And ofcourse I will be backing up as much as possible when starting to tinker with it. I was just curious as to if there is any significant drawback to using this method instead of the official windows-method?

  • Thanks 1
Link to post
Share on other sites
1 hour ago, toast said:

I was just curious as to if there is any significant drawback to using this method instead of the official windows-method?

It takes longer to type or copy a command and it gives you the chance to do it wrong and both of these things are seen as "bad" when it comes to officially supporting something.  It's copying - either it works or it doesn't and both methods do so why would you want to mess around installing windows, drivers and reading licenses when you could just use a simple tool 🙂

  • Like 1
Link to post
Share on other sites
35 minutes ago, suicidal_orange said:

why would you want to mess around installing windows, drivers and reading licenses when you could just use a simple tool 🙂

Ah, no, dont get me wrong, I am all for doing it the simple way. Im not totally new to the terminal, so I would think a couple of commands should be fine 🙂 And I understand that the mainstream instructions should probably be kept at a level where mistakes are as hard as possible to make.
Anyhow, seems like my computer is good to go then. Now, all that is left to do is actually recieving the Pro1-X. 🙂

  • Like 3
Link to post
Share on other sites
8 hours ago, Rob. S. said:

Regarding that guide...

 

... I've read somewhere else that QPST/QFIL doesn't work from a Windows VM within a Linux installation, either, as @Casey did suggest; or does someone have other information/experience?

 

It probably was me.

However, edl.py does the required job for the commands that QFIL does in windows. It appears to be even more stable that QFUL too!

  • Like 1
Link to post
Share on other sites
2 hours ago, steeb said:

That's fair. You can get generic build instructions from the EDL GitHub page, then simply enter the equivalent commands into the terminal. I've had success in both macOS and Arch using this method.

Sure it can be done, but someone has to make a variant of step by step guide for people not on Linux. So (almost) any Pro1X user can step back to the build they got it with.
We have to remember that some might also be using a pc from the fruit company.

So optimally a guide that step by step list what has to be done initially to get edl up on either Linux/Windows/Mac, and then a (almost?) common step by step guide on how to retrieve the persist the first time, and flash all the needed (including the saved persist)

I'm sure that if anyone would do the work to create such a guide, it could benefit many. I'm not sure if/when FxTec will do it, if we do not.

Link to post
Share on other sites
1 hour ago, EskeRahn said:

Sure it can be done, but someone has to make a variant of step by step guide for people not on Linux.

 

1 hour ago, EskeRahn said:

people not on Linux

Typo?

27 minutes ago, EskeRahn said:

...Also remember that to compile it requires the PC to be infected with phewton 🤢

Compile what?

Link to post
Share on other sites
4 minutes ago, EskeRahn said:

The Guide we got for using edl for flashing the Pro1X is for Linux, if I remember right.

It works on all 3 major OS. It's made in python and with the different OS in mind.

There's the setup process for Linux, MacOS & Windows:
image.thumb.png.bb7f422e0513db1aac2606fc3a82f7eb.png

Nothing really changes in between them after doing the setup.

So, the guide done, although only tested on linux, also works on the other 2 major OSs.

7 minutes ago, EskeRahn said:

Compile edl

There's no separate compilation process. It's python. The compilation is just-in-time. There's an installation step in case the user wants the program to run globally but that's about it.

(Well... For windows there the "QC 9008 Serial Port driver" but that's about the same as the steps with QFill)

  • Thanks 1
Link to post
Share on other sites
25 minutes ago, brunoais said:

It works on all 3 major OS. It's made in python and with the different OS in mind.

There's the setup process for Linux, MacOS & Windows:
image.thumb.png.bb7f422e0513db1aac2606fc3a82f7eb.png

Nothing really changes in between them after doing the setup.

So, the guide done, although only tested on linux, also works on the other 2 major OSs.

There's no separate compilation process. It's python. The compilation is just-in-time. There's an installation step in case the user wants the program to run globally but that's about it.

(Well... For windows there the "QC 9008 Serial Port driver" but that's about the same as the steps with QFill)

YIKES So you are saying that I can not limit Phewton to a (virtual) machine  to compile edl? Phewton actually have to infect the physical machine that is connected to the phone? ... Not a chance... But thanks anyway.

  • Confused 2
Link to post
Share on other sites
2 minutes ago, EskeRahn said:

YIKES So you are saying that I can not limit Phewton to a (virtual) machine  to compile edl? Phewton actually have to infect the physical machine that is connected to the phone? ... Not a chance... But thanks anyway.

Who or what is Phewton?

Link to post
Share on other sites
1 minute ago, EskeRahn said:

Python=Phewton

I don't understand why you see python as something that infects but if you have a linux OS, you mostly don't have a choice any mainstream linux-based OS needs python to function.

If you are with windows, I don't understand how it's a problem to you. Maybe a bad past? Python is open-source (FOSS, even!) too...

You don't have to install python, even. You can just run a self-executing package and delete it after use without trace, if you prefer.

  • Like 1
Link to post
Share on other sites
1 minute ago, brunoais said:

I don't understand why you see python as something that infects but if you have a linux OS, you mostly don't have a choice any mainstream linux-based OS needs python to function.

If you are with windows, I don't understand how it's a problem to you. Maybe a bad past? Python is open-source (FOSS, even!) too...

You don't have to install python, even. You can just run a self-executing package and delete it after use without trace, if you prefer.

An ugly hack/workaround but something like py2exe, encapsulating all the junk might do the trick.

It is not that I see it as malware.

I'm pretty picky on what I install on my PC, and let us say that Puketon is not on my wish-list...

And the "without a trace" would -unfortunately- be a first for stuff under Windows.
Sure I could do backup and restore points, but that would be a bit excessive...

I had Docker and Python 3.9 on a previous machine installed about a year ago, never got fully rid of it. Though the culprit for the issues could have been Docker,

Link to post
Share on other sites
8 hours ago, EskeRahn said:

An ugly hack/workaround but something like py2exe, encapsulating all the junk might do the trick.

It is not that I see it as malware.

I'm pretty picky on what I install on my PC, and let us say that Puketon is not on my wish-list...

And the "without a trace" would -unfortunately- be a first for stuff under Windows.
Sure I could do backup and restore points, but that would be a bit excessive...

I had Docker and Python 3.9 on a previous machine installed about a year ago, never got fully rid of it. Though the culprit for the issues could have been Docker,

Can't you simply use the livedvd? - I assume the image can be put on a USB drive e.g. using Etcher.
https://github.com/bkerler/edl

 

Quote

 

Use LiveDVD (everything ready to go, based on Ubuntu):

User: user, Password:user (based on Ubuntu 22.04 LTS)

Live DVD V4

 

 

Edited by Benni
  • Thanks 1
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

Terms