oliviersenn6
-
Content Count
22 -
Joined
-
Last visited
-
Days Won
2
Posts posted by oliviersenn6
-
-
On 1/3/2024 at 12:25 AM, CornholioGSM said:
Have you tested to set sms center manually for vzw?
MMS is working because mms can be sent via data connection too.
Edit : dial *#*#4636#*#* - phone information - smsc refresh and reboot
...and maybe turn off in sms settings rcs chats (using data/wifi for texting)
thanks (and sorry for deadposting but i don't come here often), this fixed it. didn't have to turn off RCS.
-
3
-
-
4 hours ago, EskeRahn said:
I rarely tried, but it worked when I did, both send and receive. Is it constantly or occasional it fails for you?
constant, both RCS and SMS (but not MMS !) fail to send. LOS devs went "damn that sucks", and my carrier had me try things that went nowhere. at this point if i need to send an SMS i press send, it fails, i take a screenshot and send that as an MMS. Jus throwing it out there in case someone has seen that before but if you haven't heard of it then i'm definitely alone with this.
-
Well, Happy New Year.
to be honest owning a 25% more powerful version of the pro1, with an SoC released before 2020 and quite possibly the same screen QC issue, is not exactly my alley and i've been avoiding asking for a refund for years now because i thought they'de at least send it eventually. evidently they did not, and as my current pro1's battery health (hi Eske, yes, i did fast charge it, yes, you told me so, the thing is like 6 years old at this point it's fair to say it's old okay) is dwindling and there is not even a tracking number in sight, I asked support today for a refund. from what i can tell from the community chatter they won't actually send one to me, probably because they can't since IGG geve them a lump sum. no matter, i will chargeback if I have to.
the absolute irony of being backer number 565 and not being included in the actually shipped batches because of my audacity to ask for an AZERTY layout, then switching my PC layout to QWERTY since ordering, is not lost on me.
P.S.: any pro1 LOS users have had issues with sending SMS? not the right thread but LOS support doesn't care and neither does my carrier
-
1
-
-
I use magisk because it's easier for most things, honestly (also my banks don't use those methods). for example having an su manager for in-app su requests is very useful, for example for installing Vanced rooted. but obviously if that's not your use case then by all means ih8sn is leagues easier to use than trying to get magisk to install, not to mention the wiping risk if you fuck up your flash.
-
On 4/27/2022 at 10:24 AM, EskeRahn said:
I wonder if 18.1 -> 19.1 has any positive or negative effect in this matter? Anyone tried?
i have not tried 18.1, but i installed 19.1 this weekend.
i'm using:
lineage 19.1 with mindtheGapps
Magisk 25.0, apk 25.1, zygisk enabled (important)
Magisk modules, using fox magisk modules manager:
magiskHide props config, set to fxtec pro1
Universal SafetyNet Fix, no additional config
then reboot
i am passing all safetynet checks, and i am able to add cards to gpay (my bank is still not supported but instead of "this device has been modified" it now says "your bank is incompatible"). My insurers app doesn't like rooted phones either and i am now able to launch it no problems.
i suspect the new sepolicy thingy introduced in magisk 25.0 is much more powerful than whatever was possible before, and zygisk is just the cherry on top...
figuring out how to install everything was a bit of a pain, i think in the end the solution was to flash magisk 25.0 apk (renamed to .zip) in recovery.
there a several apps on the play store to check safetynet.
-
6
-
-
On 2/1/2020 at 5:07 PM, J_P said:
Finally got Magisk installed properly.
The issue was that I had an SD card in the phone, and Magisk manager automatically installed to the SD card which makes it not work.
Hopefully this info saves someone else some trouble.
THANK YOU
-
alright so that just fucking happened.
since my phone wasn't booting, i decided "hey you know what there can be no harm in trying to install lineageOS, worst case scenario it doesnt work and i'm back at square one."
so i flashed the boot.img for lineageos from tdm's website and the phone tries to boot into it and shows the lineage loading screen, but ultimately fails and ends up in a boot loop.So i used this tool yet again to actually go back to square one.
and now my phone boots.
what the hell is happening i'm so confused
-
i'm not sure what you mean, but i can enter EDL by pressing both volume buttons down and then the power button.
when i flash the phone using this tool, the flash process goes correctly but i always end up in fastboot. if I had unlocked the bootloader, it becomes locked again, so I can tell that it's doing something but it doesn't appear to work.
-
sorry to dig up an old thread, but i'm having trouble with this.
i used it once to do a full factory restore because i couldn't install updates and it worked fine. then after doing an update and rooting, i couldn't install any more updates (probably my fault) so I used this tool again.
now my phone can only boot to EDL or fastboot (which says it's locked, although that's not exactly a problem). if I try to flash either one of the 2 QFPs you provide, the result is the same, if I don't enter EDL the phone boots to fastboot no matter what i try.
additionnal info:
i'm using windows and have followed the instructions on your website. I am using a USB 3.0 port and the cable that came with the phone.
fastboot seems to be responding correctly but flashing a vanilla or magisk-patched boot.img doesn't appear to change my issue.
i did try to run this tool again and the result is the same.
thanks in advance
-
5 hours ago, SirBaconIII said:
Ah, yes. I had this one as well. You flashed the 2020 boot.img over the 2019 boot.img, and now patches don't work because you've entered some weird state the updater doesn't want to mess with. What I did was uninstall magisk (restore image) but didn't reboot (doesn't really matter if you do, you'd just lose root for the time being afaik), flash and install the proper boot image (the one that matches your version number in About QX1000), and proceed with the update from there using the "update on rooted OSes" guide you quoted. No issues after that.
well that's a damn shame, i can't seem to find a boot image for 20191203.
-
On 1/28/2020 at 6:27 PM, Hook said:
Supposed to work like this (minus the TWRP step):
Found this after my adventure, so never got to try it out. It depends on getting the original patching and rooting right.
this isn't working for me. my phone is asking me to install 20191210 (from 20191203), but regardless of whether i uninstall magisk or not, it fails with the message: "intall failed, reason: 20" which is rather cryptic.
the only thing i've done apart from magisk is AdAway (with systemless hosts) and some database hacks to get google pay working (read my standalone post if confused).
i've seen in another thread that adaway can cause otas to fail, but i've been very careful to not install it before enabling systemless hosts.
Am I screwed? do I need to flash back to stock?
EDIT: also i'm rather confused as to how i ended up on 20191203 considering I downloaded 20200106 from this thread before patching it and installing it.
-
5 hours ago, J_P said:
I am conscious that I may be completely barking up the wrong tree with regard to there being different versions - can anyone confirm if the EEA in my build number even signifies Europe - are there different builds that aren't 'EEA' ?
My build is QX1000_EEA_20200106110245
Can any of the people who have successfully rooted confirm exactly what version they rooted?
Has anyone successfully rooted starting with my exact build?
it worked on my phone, build number QX1000_EEA_20191203104303 after getting the boot.img from this post, patching it and flashing it. EEA doesn't seem to be the problem. i did not have to flash boot_b at all.
-
2
-
-
Disclaimer: i am not responsible for any harm that may come to your device as a result of following this tutorial.
as it turns out, Google pay has detection mechanisms that enable it to detect magisk even when hide is enabled and even when you pass safetynet.
this is annoying because some of use like to root our devices but would also like to be able to use features that were listed as a selling point for the phone.
i found this topic on XDA which details steps to fool it into thinking the checks have passed, which I will copy below for your convenience.
- download an sqlite database editor, such as https://play.google.com/store/apps/details?id=com.tomminosoftware.sqliteeditor
- download termux
- force close google pay
- open /data/data/com.google.android.gms/databases/dg.db with your sqlite editor. when asked what table to open, choose "main".
- edit every line with "attest" in the first column so that the 3rd columns value is 0 (instead of 10). there should be 4 of those lines.
-
open termux, get root access with
su
-
cd /data/data/com.google.android.gms/databases
-
chmod 440 dg.db
- reboot (reboot in termux works just fine)
- profit.
what you've done is edit the database google pay and other google apps use to store the results of their own integrity checks to say that you passed those checks, then changed it to read-only so that even if the check is ran again, the database won't be updated.
I was able to get past the "your device may be rooted" message when trying to configure a card to pay in-store, but unfortunately my bank doesn't support that yet so i got stuck further along. if your bank supports google pay, it should work just fine.
note that i haven't told you to hide magisk from google pay. this method should not need that, but i've done it anyway as a security.
-
1
-
4
-
as soon as i saw the title i knew i'd see Eske in the comments talking about battery life lmao
-
1
-
9
-
-
20 hours ago, jlavi said:
Once again F(x)tec failed to meet expectations.
just when we start expecting them to be late, they're early.
mine is also coming today, but i've instructed them to give it to my mother and i'm not sure they'll actually do that. we'll see
EDIT:well they won't even go inside my neighborhood because it's the bad part of town. they'll come to my office on tuesday, so that's that.
-
2
-
-
hey would you look at that i also got a tracking number from fedex and it arrives on the 27th.
-
4
-
-
Wow what a nice selection bias going on here 😄
-
1
-
-
On 1/19/2020 at 2:40 AM, CornholioGSM said:
...question is why is needed 5G? i mean that it is maybe only good for phone when you use phone as hotspot...but for internet inside phone is it not needed because speed is enough.
the discussion was the same when 4G rolled around. more speed would be great, especially considering the ever-increasing data speeds needed for video specifically.
personally i don't think rushing to get on 5G as a consumer makes a lot of sense right now considering the fiddling required to make milimiter wave working correctly and the current poor coverage, but in a few years it'll make more sense.so basically the same as when 4G came out.
-
2
-
-
adding mine to the pile, stock assigned order#6XXX QWERTY Europe, non-IGG, paid 2nd of August.
finally, my battery only lasts 4 hours per charge.
-
6
-
-
that's wierd, I'm pretty sure I paid with paypal in august.
-
I have permission to share this email from support:
QuoteHi Oliver,
Thanks for your message. I hope you’re doing well.
The first batch of the Pro1 has now been shipped to our earliest pre-orders, and we should hopefully see some of them sharing pictures and reviewing their devices online by the end of this week. Please be aware that the first batch is very small compared to the next one which is due to follow by the end of this month - November. If you haven’t yet received a shipping confirmation email, it means your order was not in the first batch. Again, the next mass batch will fulfil your order, alongside most pre-orders. We plan to be in general availability before Christmas, so all pre-orders will be completed and shipped in time for the holidays.
considering my preorder number is in the 6000s, I'm not exactly surprised I'm not in the first batch.
it seems people in batches 2+ are going to recieve their phone around later this month or early/mid next month.
-
3
-
2
-
LineageOS 21.0 Official Release for Pro1 (QX1000)
in General Discussion
Posted
I am aware and I have it installed. Issue is the same across versions so I'm moving to the newer thread. Disregard my previous comment about it being fixed, it enabled me to send 1 SMS and it broke again a few hours later.
Note that when I go to click smsc refresh, the text box only gets populated after I click "refresh".
I looked up what vzw was because I didn't know how to set anything to it, and it seems related to Verizon? Not sure how that is relevant as Verizon is not my carrier nor is it a carrier at all in my country (France). I was also unable to learn how to set smsc to it on my own.
The fact that it fixed it once does point to a carrier issue rather than an OS issue, which is good because I pay one of them.
If you have any idea on making it stick, I'll take it.