Jump to content

mosen

Members
 View Profile  See their activity

  • Content Count

    90

  • Joined

  • Last visited

  • Days Won

    7

 Content Type 

Posts posted by mosen

    Pro-1x in Android does not go into landscape mode, ever

    in Support

    Posted · Edited by mosen

    If you did not overwrite the persist partition, this could be recoverable.

    More competent people than me are currently looking into how to fix just the sensors in backuped persist images.
    You can check if your keys still exist, for instance with the "Key Attestation" app from playstore.
    It shows "Not supported by this device" when no keys are present. Any other view in that app is fine.

    And it does not really help to state, but the Hardware Key Attestation is very rarely used by any apps currently.
    On the Pro¹ X i lost the keys on, SafteyNet still works when locking the bootloader. Did not try Gpay or such however.

    • Like 1

    Pro-1x in Android does not go into landscape mode, ever

    in Support

    Posted · Edited by mosen

    @Caseyis working on QFIL instruction which will be the official way to reflash to stock.

    The EDL method using EDL.py from BKerler is not perfectly easy to set up but used by the testers since the testing devices went out in may.
    Generally, the provided EDL image contains .xml files that more exactly define what to do with the images than fastboot could do.
    In our case the EDL images do not wipe/overwrite the persist partition. Meaning that there is no harm for the keys. But also its not the fix for the OT problem here.
    I borked my keys by flashing the stock persist image which only got the sensors configured correctly but contains no keys.
    The right way would have been to make a backup of my devices persist incl. key while the sensors had stock config. To manually flash that back over the UT/SFOS alternated persist, instead of using the stock one.

    An EDL cable is not required. The procedure described below the edl.py install is effectively doing the same like an EDL cable.
    The EDL cable just puts a device into EDL mode. EDL cables can easily be made DIY, Just look up YT.

    Install edl.py from: (Copying the install instructions below for convenience.
    https://github.com/bkerler/edl 

    # Debian/Ubuntu/Mint/etc
sudo apt install adb fastboot python3-dev python3-pip liblzma-dev git
sudo apt purge modemmanager
# Fedora/CentOS/etc
sudo dnf install adb fastboot python3-devel python3-pip xz-devel git
# Arch/Manjaro/etc
sudo pacman -S android-tools python python-pip git xz
sudo pacman -R modemmanager

sudo systemctl stop ModemManager
sudo systemctl disable ModemManager
sudo apt purge ModemManager

# Actual install on all OS
git clone https://github.com/bkerler/edl.git
cd edl
git submodule update --init --recursive
sudo cp Drivers/51-edl.rules /etc/udev/rules.d
sudo cp Drivers/50-android.rules /etc/udev/rules.d
python setup.py build
sudo python setup.py install

    Then download the 2.1.2 stock images from this google drive. Its the one F(x)tec released last week
    https://drive.google.com/drive/folders/1_sgQ64ef9Di9kJ63Y6WNqllGRgRFOjac
    Unzip and open the folder containing the images and .xml files in a Terminal.

     Put Pro¹ X in EDL mode using 

    adb reboot edl

    when you got adb available. Or connect your EDL cable now to automatically boot the device into EDL mode.
    Else, for the manual finger combo method:
    Hold power and vol + and vol - During boot and release all after android logo flashes up shortly and goes into a dark screen second. If it stays dark after you removed the combo and does not boot, show recovery or fastboot menu, Pro¹ X is in EDL mode.
    If it is booting or showing fastboot or recovery (dead droid logo), redo. I needed some tries first.

    Check if the usb connected Pro¹ X is in EDL mode: 

    lsusb

    It should show:

    Bus 003 Device 011: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

    Then become root or do the following with sudo each: 

    edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram_unsparse0.xml patch0.xml .

edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram1.xml patch1.xml .

edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram2.xml patch2.xml .

edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram3.xml patch3.xml .

edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram4.xml patch4.xml .

edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram5.xml patch5.xml .

    If any of the commands get stuck, redo the finger combo and enter EDL again.

    I did not need to do that since all went well with original cable and Pro¹ X not touched during flash.

    Reboot Pro¹ X  with 

    edl --loader=prog_firehose_ddr.elf reset reboot


    Please only follow this procedure if you are used to the command line.
    Mind for instance the dots at the end of each flash command.
    If you do not feel confident, wait for the official instructions using QFIL.

    Will add backup and restore instructions for individual partitions in a new Thread. Sorry, just read the suggestion now.

    • Like 1
    • Thanks 2

    Pro-1x in Android does not go into landscape mode, ever

    in Support

    Posted

    Yes, its fine.
    The sensors getting "lost" is due to UT and sfos altering the persist partition afaiu. The keys are not touched in that process.
    Only when attempting to fix the sensors for stock android by flashing the wrong persist.img, the keys get lost since the stock persist image only contains the correct sensor settings. But not the keys.
    Flashing your own backup with keys and stock sensor config is what ultimately fixes the problem correctly.

    Also the EDL flash does not touch your keys (but not fix sensor too) unless you falsely use the contianed .xml.bak to flash which completely overwrites the persist with the stock image.

    • Thanks 2

    Pro1x with SailfishOS

    in General Discussion

    Posted

    @matf Please add this warning to your first post. Users should backup their persist partition as early as possible.

    1. Attestation data in persist partition is unique to the device unit, therefore backup of persist is strongly recommended to people attempting to flash a custom OS.
    2. The consequences of losing this data currently don't seem too critical, as the standard attestation checks like SafetyNet are passed on such devices. But they won't pass rarely used hardware attestation checks.
    3. Warning, the rawprogram0.xml.bak from the EDL package will flash your persist partition with the generic image that will erase your attestation data.

    The backed up persist partition will be needed in case you want to flash back to stock and use the device specific attestation keys contained in the persist image.
    The catch is that the sensors "break" when flashing "back" from either UT or SFOS. And to restore those for stock android. A stock persist will be needed to flash.
    In best case that is the one you backed up before starting your journey into alternate OS.

    If you got EDL set up, its 

    edl r persist persist_backup.img


    Using fastboot 

    fastboot fetch persist persist_backup.img
    • Like 1
    • Thanks 3

    Pro1x with SailfishOS

    in General Discussion

    Posted

    Agreed, disclaimer, i was just curious and can not fully oversee the implications.
    Checking the device with fastboot getvar all revealed slot_a to be active "anyway". So i was curious to try what happens without the set active command.
    Note, the original ubuntu instructions even had a set active a before the boot image flash. Which is already omitted in the first posts instructions.

    • Like 2

    Pro1x with SailfishOS

    in General Discussion

    Posted

    36 minutes ago, ducksoup said:

    Interesting that that worked for you.  I have just tested that exact boot.img on my own device and it does not boot.  Flashing back the image from last week and I'm back to booting just fine.

    What is your hardware configuration?  I am 8/256 (and the device is black FWIW).

    Same hw config but i got the blue IGG model.
    They should be 100% the same, just different casings.

    I flashed sfos as first action after unboxing. Maybe you changed something to the stock settings the Pro¹ X got delivered with?
    If you are not keen to debug the issue, i'd just reflash to the 2.1.2 build factory image using EDL/QFIL to have the device in unboxing state again.
    Like described in this thread:

     

    • Like 1

    Pro1x with SailfishOS

    in General Discussion

    Posted

    Re: First post:

    I successfully flashed, omitting the set active command.
    All i did after receiving the Pro¹ X with Android built 2.1.2 was:

    1) Download Ubuntu Touch image and extract the boot.img
    From this build (2830649718 artifact.zip)

    2) Download the SailfishOS 4.4.0.64 devel build and extract the userdata.simg
    From here (2807435728 artifact.zip)

    3) Execute fastboot flash commands 

    fastboot flash boot_a boot.img
fastboot flash userdata userdata.simg


    Happy sailing! Hope this wrap up helps someone.

    20220811_105509.jpg

    • Like 1
    • Thanks 2

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

    in Support

    Posted · Edited by mosen

    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-Tool by bkerler

    https://github.com/bkerler/edl

     

    Put Pro¹ X in EDL mode using 

    adb reboot edl

    when you got adb available.
    Else, Pro¹-X needs to be put in EDL mode manually. Hold power and vol + and vol - During boot and release all after android logo flashes up shortly and goes into a dark screen second. If it stays dark after you removed the combo, Prawn is in EDL mode.

    If it is booting or showing fastboot, redo. I needed 5 tries first.

    Check if the usb connected Pro¹ X is in EDL mode using 

    lsusb

    , it should show:

    Bus 003 Device 011: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

     

    Then become root or do the following with sudo each: 

    edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram_unsparse0.xml patch0.xml .

edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram1.xml patch1.xml .

edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram2.xml patch2.xml .

edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram3.xml patch3.xml .

edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram4.xml patch4.xml .

edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram5.xml patch5.xml .

     

    If any of the commands get stuck, redo the finger combo and enter EDL again.

    I did not need to do that since all went well with original cable and Pro¹ X not touched during flash.

     

    reboot prawn with 

    edl --loader=prog_firehose_ddr.elf reset reboot


    Please only follow this procedure if you are used to the command line.
    Mind for instance the dots at the end of each flash command.
    If you do not feel confident, wait for the official instructions using QFIL.

    • Thanks 5

    Still waiting for my device

    in General Discussion

    Posted

    7 hours ago, Rob. S. said:

    Well, as I've also ordered a (QWERTZ) Pro1 X soon after the campaign had started, I will at least be able to follow up on all this first-hand! Maybe I should place a bet with myself as to which of the two devices will be the first – that way I can only win!

    Your optimism is inspiring! Thanks for being and staying cool 😄
    Also i ordered an X as soon as it was available since i share the bad conscience OSwaldo mentioned above from being lucky and receiving the Pro¹ early.
    Now want to support others that did not even receive that by making sure F(x) has some cash flow. Plus the outlook to finally have a spare not-daily-driver Pro¹ to test out all those yummy OS that have been adapted in the meanwhile.
    Imo the March delivery commitment has some safety margin already calculate in. Last time Chinese New Year was a delay reason and it looks to me they try to avoid impact this time.

    • Like 1

    My Pro1 first impressions and issues

    in Pro1 - Thoughts & questions

    Posted

    The work around for the fingerprint seems to be to register those parts of your palm that usually trigger the reader in error.
    I did the following, activate FP registration and do those task that trigger the reader.
    Like lay it on the table and pick it up and lay it down until this action is registered as FP1.
    Then move to FP2 and eg pull the pro¹ from your pocket multiple times until FP2 is registered.
    I did this with 5 actions and the result was the pro¹ unlocked as soon as i picked it up.
     

    • Like 2

    How long I have to wait??

    in General Discussion

    Posted · Edited by mosen

    No fear, you are even still in the given delivery timeframe of 4-6 weeks.
    But to already prepare you, it is not likely you will receive your Pro¹ before end of February (hopefully during march) since the devices produced pre chinese new year have been sent out and new ones are only produced starting from this week. There have been delays even in the month since you ordered sadly.
    And prepare for (friendly) laughter from other members triggered by your attitude.
    You are literally complaining amongst folk that waited for the original moto-mod since Feb 2017.
    Personally i was lucky and attended a hands-on with attached early delivery in November. (planned for early september)
    But that was more than 2 years waiting and everybody that got a device already, can attest there is not the slightest of scam involved.
    Only a starting company doing their best to swim in the shark tank and still stay true to their ideas and ideals.
     

    • Like 4
    • Thanks 1

    Defective Screen

    in Support

    Posted

    To give hope, we had a user on discord with a prominent pink line over the display.
    He got sent a new display unit with in ~2weeks.
    It was straight forward to change with only the screws to remove on the backside of the display.
     

    • Like 1
    • Thanks 2

    Headphones delivered

    in General Discussion

    Posted

    Today i got the headphones accompanying my very early delivery from November.

    I am very satisfied with the build quality.
    The cables are soft but sturdy enough to not knot easily.
    There is no plastic smell, all components feel worthy.
    Compared to quiet neutral Sennheiser, the the mids and bass are nicely emphasized. No distortion in the heights even at unbearable 100%.
    They sit very comfy and yet tight.
    My expectations are met, Thank you at F(x)tec.

     

    IMG_0135.JPG

    IMG_0133.JPG

    IMG_0132.JPG

    • Like 9
    • Thanks 8

    Fell in few drops of water. Can't switch on

    in Support

    Posted

    The good news from this thread seems to be the confirmation the Pro¹ being easily serviceable.
    Kudos to you taking the right action and let a professional solve this correctly.
    Was that a 3rd party repair shop not related to F(x)tec even or did they recommend to you where to go?

    • Like 3
    • Thanks 1

    Which car holder?

    in Pro1 - Thoughts & questions

    Posted · Edited by mosen

    The universal holder from Brodit does the job.
    Sorry, no idea about measurements and order number, it is like 6 years old.
    But i just needed to widen this universal holder to max after using it for XA2 which was more narrow.
    The thickness is exactly matching the cutout space so the pro¹ sits very tight.
    https://twitter.com/eLtMosen/status/1197074326245257216

    Oh, and cheers form an Audi 80 [B4] owner for ~10years 😄
    Now i upgraded to this nice [W639] Vito with just 260tKm.

    spacer.png

    • Like 3

    QWERTZ User Layout Setup

    in How Tos

    Posted

    3 hours ago, Bmbx said:

     

    I ordered QWERTZ and now I'm worried that I will have a confusion in the layout of the symbols after setting up the keyboard

    No fear.
    So far community members have perfectly helped each other in configuring and afaik everyone solved eventual starting issues.
    I had perfectly mapped QWERTZ on Android thanks to community members explaining FinQwerty use to me.
    Now that i run Sailfish i try to give back and have propsed a mapping for SFOS QWERTZ.

    Just ask here or in the unofficial Discord for more chattier help!

    • Like 2
×
×
  • Create New...

Important Information

Terms

  I accept