Jump to content

sspiff

Members
  • Content Count

    37
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by sspiff

  1. 58 minutes ago, mosen said:

    I am writing instructions for a complete backup thread just now.
    Copying the data folder from the backup to the stock persist did not work.
    What worked for me however is to copy the sensors folder from the stock partition to the backup persist.

    Copying the sensor data from the downloaded ROM and then flashing (using `edl w persist persist_backup.img`) did not fix the keyboard & rotation for me.

    I did not remove the directory before copying the stock sensor files into it - so it still contains more files from my backup, not just the files from the stock ROM. Should I remove the directory and replace it with the stock ROM files only?

  2. 3 minutes ago, eBrnd said:

    I guess I broke it on mine. I flashed the persist.img from the stock rom archive in order to bring back rotation and keyboard backlight*, which worked. However, I get "Not supported by this device" from the Key Attestation app.

    *) I thought I had already wiped my persist at that point by installing Ubuntu and Sailfish, but apparently that wasn't the case. Bummer.

    Sucks 😞 I made a backup of my persist partition and I notice they're just ext4 partitions. I guess copying the right files from one to the other would resolve it.

    I wonder what happens  when you flash the same keys to multiple devices? 🤔

    • Like 1
  3. 2 minutes ago, mosen said:

    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.

    I installed Key Attestation and it shows "Security level: TrustedEnvironment"

    • Thanks 1
  4. 42 minutes ago, EskeRahn said:

    Or it could be the lack of a backup/restore of the persist partition, mentioned in other threads that are making problems here t

    After reading more on this, it's starting to sound like I bricked some crucial functionality of a phone I ended up paying 800 euros for, and waited 2.5 years for, on day #1.

    Is there any chance or recovering from this without case-by-case assistance from f(x)tec? (which seems very unlikely judging by their reputation online)

  5. So, I'm in the same boat. I've flashed a recent UT build, didn't work.

    Then I reset by following these instructions to restore to a booting phone, and to try out SailfishOS instead. On Sailfish, everything seemed to work, apart from the lock screen rotation when flipping out the keyboard bit. Normal rotation worked fine based on the gyroscope, so I didn't really think much of it other than "early community build".

    After deciding the software ecosystem on SFOS is a bit spartan, I decided to hold out for a more mature, working Ubuntu Touch build for the phone, but go back to Android in the mean time. Now I have no rotation, neither from sliding out the keyboard or tilting the phone. It does detect the slide mechanism, because it lights up the display. According to the software, it seems it thinks the keyboard is always active, because it never shows the virtual onscreen keyboard.

    I really hope this is recoverable. I would hate to have waited 2.5 years for this phone, only to receive it with a slower SoC and brick a crucial feature of the phone on day #1.

    • Like 1
  6. 5 minutes ago, EskeRahn said:

    Or it could be the lack of a backup/restore of the persist partition, mentioned in other threads that are making problems here too?

    Sounds interesting, I did not flash the persist partition manually (I've only flashed boot_a, system_a, userdata and recovery through flashboot IIRC).

    I did run the EDL commands provided by @mosen above (on a Mac, if that matters), do those wipe the persist partition?

    Like I edited above, resetting userdata from fastboot fixed my storage problem, but not the rotation.

  7. I used this to reflash the phone after testing SailfishOS - but now the screen doesn't rotate and it's reporting only 8GB storage. Did I do something wrong?

    Update: after rebooting into fastboot, and issuing `fastboot erase userdata`, the storage problem seems resolved. But still no rotation or any kind of detection when I slide open the keyboard.

    • Sad 2
×
×
  • Create New...

Important Information

Terms