Leaderboard

Hi folks, I just started working on the mainline kernel a few days ago with ichernev and so far I've got USB and simplefb up and going, no button, storage or regulators yet.

These guys can't catch a break. Us neither, but we know that already. I think this news calls for a pizza.

Thank you all, I will attempt to try the measures that you suggested. It may take a couple of days to unravel it and I'll keep you posted (if only to report success, or I get mixed up again) I particularly take note of mosen's post as I very well may have mixed the Pro¹ and Pro¹-X up, in fact I didn't discern between the two at all. I just went to the box it came in and on the front of the quick start instructions I think that means I have Pro 1 x, but I've definitely not check whether I'm downloading the wrong thing or followed the instructions for wrong phone. From now on I'll

Well, of all 3 scenarios you put forth this would be the best one. Meaning we might get a fixed version. Oh man. Everyone has limits. I am pushing mine further away in hopes that the outcome will be a good one.

Oh my... December? It's quite a change in tune from "it will ship next week". I hope people at FxTec are getting better at estimates, rather than spitballing the December 2022 date which then might turn into March 2023. I've been supportive of FxTec's struggles and endeavour to make a grat phone but with my Pro1 turned into a paper weight (for now at least) and my replacement phone showing signs it might soon give up the ghost... I'm utterly disapointed. I'm trying to find solace in the reasoning that since they changed the estimates from "next week" to December, they might have

Wow... They keep being attacked and attacked and things keep not working out for them! Wow... I really really commend their perseverance!

Okay, I guess it is just too long since I had stock Android on my Pro1. Sorry.

The wrong logo might be caused by using the wrong slot [A,B] the lineage wiki is very specific about when to flash to which slot

(moved your post over here)

Probably the incorrect topic to ask but maybe it's relevant here a bit as well. Recently I got a new 128GB pendrive which has both usb 3.2 and usb c. I plugged it into my Pro1 but it can't read it no matter the file system (it is recognized at least). So I am wondering if this is an android 9 limitation or if it would work on newer version / a different OS. Works fine on PC. Edit: Nevermind, FAT32 formatting works if I do it with the phone itself. lol Too bad it doesn't support NTFS.

Have not got any update mails anymore. Would have liked to get news.

I am out. I send a mail and want my money back. I am waiting since May 2020. This is enough.

F(x)tec communication at its best ... 🙂 "Contractual issues" with their partners that lead to a 4-month-delay? With their tradition to underestimate delays by a factor 2 to 3? That's asking for the wildest speculations ... Here are mine: Option 1: The logistics partners suddenly want more money due to prices skyrocketing because of the ongoing crisis. F(x)tec can't pay more so they insist on fulfilment of the existing contract. Parter refuses and stops all activity, witholding the phones. They need to take it to court. Option 2: The entire batches 1 and 2 have "disappeared" fr

September update: Dear Pro1-X backers, Here are the latest updates! As mentioned in our previous update shipping is temporarily on hold - we are deeply sorry for these delays! We have spent the last few weeks working through some contractual issues that have come up with our shipping partners in Hong Kong. This has unfortunately impacted the operations and logistics of all orders which were scheduled to leave the warehouse last month. The most realistic estimate we can provide for shipping and delivery is December 2022. Whilst we understand that this is not id

One week is a short time. They are a very small shop and are probably getting a high volume of email right now. Hopefully they will get to you. I would guess shipping to Russia from HK won't be too troublesome, but I would imagine if there were specific problems with that, they would contact their Russian backers-- However, I am not knowledgeable on this, just guessing.

This is a user-to-user forum, so the chance that your message is spotted by staff here is slim to none. Sorry.

@maridavAre your sure to not mix up Pro¹ and Pro¹-X intructions and even images? Those are two completely different devices due to different SoC and the Firmware is not interchangeable. For the Pro¹, the unlock command is `fastboot oem unlock` for example. Also, there is no LineageOS for Pro¹-X yet. so i figure you tried to flash the Pro¹ LOS files? LineageOS for Pro¹-X has just now been booted up first time by a dev as reported on Telegram.

Hello everyone! Is there even a small chance that my ticket #16243 will be attended and replied? I've filed it a week ago and asked Fxtec team if I can change the delivery address as they can experience troubles with sending my Pro1 X to Russia. Thank you.

@maridav It should still be possible to flash the stock rom using EDL, probably even using fastboot. Fastboot restore guide: https://drive.google.com/drive/folders/18Clj6qv4jXIFGfy0S1NO1K8DoN8bJ3Ms A locked bootloader should only prevent you from installing custom ROMs. I would still recommend you contact fxtech.

Yes, the situation definitely is unsatisfactory. Personally, while I'm in the comfortable position of already owning a (battered but still mostly functional) Pro1 and a shiny new Pro1X (backed on IGG October 2020), I'm also still waiting for my September 2019 Pro1 website order (later changed to Pro1X) to be fulfilled. I can report, though, that three weeks ago (production updates usually come once a month, more frequently only if significant things are happening in between) I requested some information, and while they didn't give me any specific dates, they assured me that the order defi

The new magisk is not any dumber that the old one. I am using magisk v24.3. Everyhting works the same that in the older versions, what is different is that the hide list is deny list and you need zygisk mode on and configuring the list is in the app settings, but the functionality is the same and if you have to use external modules like MagiskHidePropsConfig you need to download them manually but they work the same. So i have all the same banking apps still working that i had since magisk v20 ->. Edit: And there is no more the builtin safetynetcheck but there are various apps for that in

Also for me... anyway, Magisk has started to notify an update is available few months ago which lead for disabled notification for Magisk on my phone as I did not want to update to the "dumb" version. (Also, one of my friends did it and Safetynet has stopped working.) However, I am curious of the new solution but I will stick to LineageOS 18.1 till I don't see it is working...

Wow, seems I haven't been up to date with regard to Magisk... Looks like not only MagiskHide, but also everything related to SafetyNet is removed from current Magisk releases. (See John Wu's statement in https://topjohnwu.medium.com/state-of-magisk-2021-fe29fdaee458) now that he's working for Google, and also this XDA Developers thread: https://forum.xda-developers.com/t/discussion-magisk-the-age-of-zygisk.4393877/.) That said, MagiskHide seems to be in the state of being replaced by the Zygisk (Magisk running in the new Zygote mode) "deny list"... And the tools to ensure Safety

Alas, hello again 🙂 I've been using my pro1 (non-x) for some years now. Basically just on LineageOS, usually the latest version. Apart from the usual ,Connected, not charging' and some trouble with location in maps in some applications things were going quite fine. But yesterday all of a sudden the device restarted itself and kept doing so indefinitely. I am able to get into recovery, bootloader, no problem. The lineageos recovery seems not to offer any of the usual ,empty cache' options apart from factory reset, so.. after a while of trying various ways how to break this loop I bi

There's no wrong logo, it's just that the device reboots again as soon as the ,ROM logo' would show up. I'll try fastboot erase (although after fastboot flash stock rom I'm pretty sure the phone was basically bone stock before my last attempt). FWIW this is like my 40th time of android flashing to various android devices and apart from an old samsung core prime (which had 0 custom roms and 1000s of stock ones) I've never encountered anything like this.. 😞 .. The worst thing it just happened out of the blue, there was no update, no nothing, I haven't even held the phone in my hand. I've just st

well but the point is I never get past the boot sequence :[ I can try installing once more. I do it through fastboot & adb EDIT.. fastboot flashed lineage recovery, adb sideloaded lineage 19.1, mindgapps 12.1 and no, it immediately after first Powered by android logo goes to another reboot. Doesn't even show the lineageOS blue curve logo. F** hell.