Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 09/13/2022 in all areas

  1. Hah, that's what you are suppose to do.. Sorry if I didn't make that clear before ¯\_(ツ)_/¯ And I can confirm this works, I tested it out. You will need to have your bootloader/OEM unlocked before you commence this process. Glad everything worked out in the end 😄
    4 points
  2. Yeah at this price you may as well get a Samsung Fold it does landscape keyboard too.
    2 points
  3. My darling Francisco has been kind enough to teach me how to say "I am so sorry: in at least 8 different languages. It's a special game that we play. April, 19, 2021 here on Hubby's Pro1-x Batch #2
    2 points
  4. It is highly advised to take a backup of your device specific partitions right after you receive the device. Update 20220829: tl:dr: Community has not found a safe way to restore backups as of yet. Making below described backups is still highly advised for a future where some wizard found a reliable way to restore those backups. For now, if you have broken sensors from flashing another OS, the restorecon method described in the "Repair sensors/ folder..." section does 100% work to fix those while retaining your attestation keys. While restoring any backup has a high chance to make the keys
    1 point
  5. No need to restore Stock Rom. I last time I sent mine in it was on AICP. They can reflash it if needed.
    1 point
  6. => boot loop. At least I get to actual rom booting, as opposed to only the kernel running in circles with lineageOS. I like the AICP logo, though 😃 it makes one smile.. I'll leave the phone on charger for a while in case it somehow boots, but I won't hold my breath. Thanks all for the help. I am afraid this is not a software issue. I'll wait for the support response.. BTW if they tell me to send it in, is it better to return to stock ROM or does it not matter? EDIT; I'll try one more thing, AICP-r without gapps. Just for fun. EDIT2; no change. The boot loop seems faster,
    1 point
  7. The method looks sound in principle, but forget about AICP-S for now... And anyway I use a MUCH older boot/image lineage_18.1-20210913-recovery-pro1.img You should fetch AICP-R not S, S is not stable (yet?), and still on march security patch.... I had a LOT of trouble with S.... With S, I needed to do a factory reset from within the recovery, and even so, it still asked me at the seventh boot, to factory reset again. And still after that does a bootloop after each flash of new version.... AICP-R is stable, so fetch a copy of R ASAP, as it is likely to roll out the bottom of the
    1 point
  8. I'm out also. My order was from 17 April 2021 and with the last update I'm pretty sure that delivery will be at least at March 2023. It's too much for me to wait 2 years, so I sent mail last week to ask full refund. Now in their page my order is in status "refunded", but still money are not received. I don't know when fxtec will send money back, because I receive confirmation mail for full refund with word "soon", but fxtec's "soon" can vary from few days to few years ... I really wanted to have this phone - my previous phones has qwerty keyboard (Nokia 9210i, Nokia E90
    1 point
  9. Same. I've been planning to poke around at that a bit, but haven't had the chance yet.
    1 point
  10. Hey everyone, due to the current libsoup3 migration in Debian, `apt dist-upgrade` or the Software app might fail to let you upgrade an existing installation. You can unblock upgrades using the following commands: sudo apt update sudo apt upgrade ..and then proceeding as usual (i.e. doing an upgrade via `sudo apt update && sudo apt dist-upgrade` or using the Software app, which is the recommended way). As a reward, you'll also be able to upgrade to the newest phosh (0.21.0), which finally is available in Droidian 😀 Have fun!
    1 point
  11. It depends on what the problem is. At first, I would think the UFS / flash IC may failing which most probably means a mainboard repacement would be needed... or if not replacement, a replacement of a BGA part of the mainboard which does not seem to be an easy task if we are speaking about a replacement mainboard of Pro1. However, strange things may happen - I don't know how USB panel has caused unbootable phones (except triggering EDL mode by a failed connection), so who knows if it may cause other problems as well...
    1 point
  12. Joke aside, if they authorize you to send it in, you are likely to get it back within a month, depending mostly on how many other repairs they have. They have spare parts right now. if needed, so they will fix quickly and return. The first time I needed a repair on my Pro1, it was a month including travel to and from London (from US). Second time, I knew I had to wait months for parts, but when parts were available, they had repairs done in 2 weeks.
    1 point
  13. I have uploaded recovery of last official LineagaOS 18.1 here.
    1 point
  14. Ah! This description reminds a lot of AISP-S that after install goes into a boot loop, and only on the seventh(!) boot actually boots, and needed TWO sort of factory reset....
    1 point
  15. I am out. I send a mail and want my money back. I am waiting since May 2020. This is enough.
    1 point
  16. This is the complete guide on how to root your Pro1-X with Magisk. Rooting you Pro1-X can allow you to 'unlock' superuser permissions along with flashing custom ROMs. This process will require you to have OEM unlocked before proceeding as we will need to use Bootloader mode to flash a patched boot.img from Magisk. It should take around 20-30 minutes for users who are new with rooting their phones. Instructions for unrooting your Pro1-X are also included in this user manual. Click the attachment below to download the user manual for rooting your Pro1-X with Magisk. How to R
    1 point
  17. A new build of good-old LineageOS 16.0 for our good-old Pro1 (835) is available at http://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 Go for the ROM dated 2022-08-23. It contains backported AOSP security fixes up to patchlevel "1 August 2022". I bumped the Android security string to reflect that. Seemingly, people are slowly losing interest in Pie. While the AOSP patches since May have been backported and have undergone basic testing (by me and on other devices), they have not been merged into the official LOS 16.0 tree yet, due to pending code review. While I a
    1 point
  18. Now your point is correct, but what about 1-2 years later? Pro1x was good phone if was received in 2021 year with the original chipset - that was my reason to order 8G/256Gb version. But in 2023 year is not worth it I think. If my phone is good enough I can use it for longer time - even 5 and more years. Receiving of so outdated phone in 2023 will limit time for using it. For example my Nokia E7 (great phone, similar to Pro1x keyboard) was used below 2 years because of stop of Symbian support. Similar can happen with Pro1x - no support, no updates, problem with spare parts (display, batte
    0 points
  19. "Preferred" seems to be the key term there. Even when I set the device to "prefer" only bands not even available in my area, it still ends up on those that are. I don't think this menu is a means to actually blacklist bands, just to tell the device which ones to use if available. I got a SMS from a friend this morning telling me he was unable to call me last night. This despite everything seeming okay on the phone this morning. He was trying to call me after midnight, though, so missing the call isn't all bad. 😉
    0 points
×
×
  • Create New...

Important Information

Terms