Kaali
-
Content Count
34 -
Joined
-
Last visited
-
Days Won
7
Posts posted by Kaali
-
-
I guess ih8sn should work with magisk too but i have not tried so it's not proven. You could just use magiskhidepropsconfig and denylist with magisk though. But if you give ih8sn with magisk a try please report your findings here on the thread.
-
1
-
-
There are so little instructions on the ih8sn in the internet so i thought i could share how to get it to work on pro1 if anyone is interested in that. Fresh install is not needed and you don't need magisk or any SU package to pass safetynet after this. Not sure if this works for other OSes than Lineage but someone can have a shot and tell if it does.
Requirements:
-ADB on your computer
-Debugging and rooted debugging enabled on your phone from developer options.
-Latest ih8sn aarch64 release downloadable here, extract the zip, you don't need the .conf file as it is for different phone.
-ih8sn.conf file with all the props from last pro1 stock rom i attach to this post.Steps to install:
-Connect your phone to your computer and open a terminal (linux) or a powershell (windows) on the folder your ih8sn files are.
-type in commandadb rootit should say restarting adb as root otherwise make sure your device is connected and rooted debugging enabled.
-type in commandadb remountdo not restart the phone at this point
-there are scripts included in the zip so all you need to do is execute the script.\push.ps1If you are a windows user. You might need to allow powershell to execute foreign scripts, there are instructions for that easily available on the internet so i wont fill it in here.
Or if you're on linux../push.shIt should push 4 files onto your device. Note i did this on windows so i can't guarantee how the linux script works. You can always manually execute the push commands that are in the scripts, instead of using these scripts.
-then type in commandadb enable-verityOtherwise the phone will bootloop at next OTA
-Now restart your phone and check that safetynet passes using f.ex. YASNAC or some other safetynet checker app.-
8
-
-
I too used magisk to the point vanced was killed by google. I realised i don't need root anymore. Yes old installs of vanced still work but for how long that we cannot know.
-
17 hours ago, oliviersenn6 said:
Universal SafetyNet Fix, no additional config
You actually don't need UniversalSafetyNetFix with pro1 if you use MagiskHidePropsConfig. I have understood that USNF is more needed on devices with hardware attestation and pro1 uses basic attestation so only changing of the fingerprint with MHPC and putting google gms on denylist is needed to pass safetynet, and that always worked for me too. Then you might need to set some other props with MHPC for some programs to work that check more than just Safetynet pass.
Anyways there is a new way to pass SafetyNet on Lineage without magisk at all called ih8sn. I personally switched completely to that and uninstalled magisk. LoS has builtin adb root option that is enough for this to work. I can share the .conf file with working props from stock rom if someone is interested. It basically is just script that changes the fingerprint like MHPC but without magisk. With this i can get more banking apps to work that i can't get to work with magisk because they use some advanced way to detect magisk on the system. (S-pankki for finnish folks)
-
6
-
-
MtG isn't even that huge, and it just works. I used NikGapps with LOS18.1 when it first came out and there was no opengapps yet, it gave me all kinds of problems with apps and bugs and crashes. Then changed to opengapps when it was available just to see that all the same bugs were there too. Finally when i talked to someone with OP5 with lineage (has the same chipset) had all the same bugs than i, asked what gapps package he using, turns out the problem was opengapps. Then we both changed to MtG and all the crashing and errors are gone. I guess there is a reason lineage lists it as the only option for gapps.
-
1
-
-
On 5/26/2022 at 4:57 PM, EskeRahn said:
I agree with you, I was surprised that it did not require a factory reset.
And for my case I think the mess I had was due to changing from OpenGapps to MindTheGapps simultaneously. Had I reflashed latest 18.1 with MindTheGapps before the upgrade to 19, it might have worked smoothly.(OpenGapps is not yet available for Android 12 / hence I was forced to do the swap. I Prefer OpenGapps, as they have lesser packages than MindTheGapps, as I mapped out extending the OpenGapps compare schema last year)
MTG has the upside that it just works. Opengapps have weird bugs and crashes at least on LOS17 and 18 they even say it on their download page that it is not stable yet. I had so many wierd problems, some apps suddenly not getting any network even i had connection on other apps. All went away when i finally changed to MTG as Lineage suggests.
-
1
-
-
I just follow what the images show i don't read chinese either.
33 minutes ago, patrykgrzesiak said:Thank you for posting. The instructions are in Chinese š
Ā
-
5 hours ago, silversolver said:
You sure about that? The instructions seem to call for some root ADB instructions, though being mostly in Chinese I can't be 100% sure. Perhaps it works anyway if that section is skipped, or the ADB part providesĀ root access without actually rooting the device.....though I didn't think this was possible.
I'm not 100% sure as i have rooted with magisk, but i recall doing that flash when i was running stock way back and i didn't need to root then. Also on lineage under developer options i have allow rooted debugging so it might be enough itself.
-
1
-
-
6 hours ago, silversolver said:
I am running 17.1 to avoid the bugs introduced in 18 and 19, and hence could root it and use the apk updater if I can get it. How hard is it to add root to an existing system? Is it necessary to do before first boot like gCraps?
You don't need root to use the APK screen firmware flashing tool. The files are found from the unofficial discord server, dragonbox guy also has them, and i remember they have been posted somewhere else too. Look for Boe.rar
Edit. The file was posted to matrix originally by The Kit, i think at this point it probably is safe to post it here so here's the link to the BoE files that can fix the screen margins on Android 10 or 9. Instructions are included in the file.
https://matrix.revreso.de/_matrix/media/r0/download/matrix.org/MhQPLNrIHbyoMahdOvuZLWtA-
1
-
3
-
-
On 5/19/2022 at 3:21 PM, silversolver said:
How annoying. Is the necessary programming function something that could be put in an APK to avoid having to completely rework your software for a simple screen change? Of course I'm hijacking this thread with an OT now.....
There is an APK to flash the screen firmware but it only works on Android 10 or lower (basically stock or LoS16 or 17)
-
1
-
-
9 hours ago, EskeRahn said:
Bad news, the charging bug is still there on 19.1 š
Here stuck at 30% for 3h
I noticed this too today, iirc that bug was originally introduced in a update to LOS18.1 as it wasnt there in the beginning. Can't remember which one though.
Ā
6 hours ago, agent008 said:However, stock would show 'no updates'. But when configuring the device I realised that Google asked me to confirm on my other devices the new "Sony Xperia" I was setting up. So I realised I reflashed my phone with an altered device signature done with MagiskHideProps module (used to make banking apps work with AICP).
I unsuccessfully tried to install Magisk to stock. Then I had the idea of using Magisk with Lineage 19.1 to install MagiskHideProps and return the device signature to the original. That's where I got stuck. So I reflashed stock again.
Now I'm flashing AICP 16.1 which was what I had been using until yesterday, in order to see if I can get to Magisk and return the device signature to normal. Maybe then the "screen update" will be able to be downloaded.
Another option would be a fix "package" that someone had here (I think it was @EvilDragon ?) that I could run on stock.
Man, that's why I hate reflashing... why couldn't our replacement Elephone screens work out of the box? š¤
Interesting, did you use device fingerprint from another device? That is definitely not recommended as it can lead to all kind of problems. There is a working fingerprint from the stock firmware for the pro1 in the MagiskHidePropsConfig fingerprint list which is only one that one should use with pro1.
-
2
-
-
3 hours ago, agent008 said:
Great news! I'm reinstalling today because I replaced my screen (again) and need to go back to stock to make the touch digitiser to work.
Has anybody at this point tried Magisk and Google Pay?
Google pay working here with magisk v24.3 for some time already and works on LOS 19.1 too.
-Zygisk mode on
-Enforce denylist
-Put com.google.android.gms and com.google.android.gms.unstable to denylist under google play services. You might need to check show system apps from the denylist donfiguration settings
-You manually need to download and install MagiskHidePropsConfig and do the edit device fingerprint, probably no need to do this if you upgrade from v23 and have already done this.
-make sure play store says device certified, if not try clearing play store and play services cache and reboot.
Should work easy as that. If you already use v24 in LOS18.1 it should work all the same in 19.1 like mine did. Just remember to sideload magisk the same time with mindthegapps before first reboot into 19.1.
-
6
-
-
Decided to upgrade now because i must at somepoint anyway. First impressions are good, everything seems to work with magisk v24.3 and MindTheGapps. The extra dim mode is very very welcome with the pro1, now i can finally get the screen brightness to a reasonable level in dark.
-
2
-
-
7 hours ago, Rob. S. said:
Nice to see 19.1 is there for the Pro1!
My phone says manual upgrade only; before I'd go into that, would there beĀ anything special to take care ofĀ whenĀ upgrading a LineageOS + Magisk 23 + Gapps setup except sideloading MagiskĀ and Gapps in the process? I think my last version upgrade also was the first time I added Magisk.
Hmmm... A quickĀ look has turned upĀ no traces of any LineageOS work in progress for the Pro1X on either Github or gerrit, did I miss something. Anyhow I wonder, now that the delivery of two Pro1X devices (with LineageOS asĀ OS choice)Ā seems to come closer, what OS will it have installed?
Be aware that you need to upgrade to magisk 24 for Android 12 support. No need to fear the new changes, it still works all the same than before. Zygisk+denylist is basically the same than former magiskhide. Any external modules have to be manually installed f.ex. MagiskHidePropsConfig, but they work normally.
-
3
-
-
Magisk 24.3 supports android 12 so i guess it should work all the same. One person in the discord alrready upgraded to OS19 with magisk.
-
2
-
-
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 play store.-
3
-
2
-
-
I had the exact same charging problems and only the cable connectincg the usb board to the main board was loose, the connector is shown in your picture. Just snapped it back in firmly and never had any problems since.
-
1
-
-
Is battery life better or worse with the new lineage? Also does the charging work?
I only had problems with opengapps on 18.1 anyway so mindthegapps is the way to go. -
On 2/13/2022 at 2:39 PM, Fxtecish said:
How did you fix it? By soldering or with by other means?
It could be good to have here on the forum a section for different fixes with pictures. Then it could become a habit that when people fix something they could report and show what they fixed and how.
I am still waiting to get my first Fxtec device and have to say I am a bit alert what I have got to know on this forum about the problems with Oses or hardware. The lack of support from team is expected but maybe hard to accept. For me it is just awesome Chen had the courage to make this even possible.
No soldering, just pressed the connector back to the socket firmly. Probably had come little bit loose when i dropped the phone or something.
-
1
-
-
On 2/17/2022 at 2:13 AM, MickH said:
I'm beginning to think it's the battery actually. It's been on charge now for 4 hours and is showing 71% and 14 hours until fully chargedĀ š§
Damn thing's going backwards.
Really sounds like the LineageOS charging bug. Have you tried if it charges normally after a reboot?
-
2
-
-
There might be some dirt or lint in the charging port if it doesn't click anymore, it can be cleaned very carefully. The usb port on the phone is very sturdy and i say it won't fail easily, my unit had the cable that is connecting the usb to the mainboard loose and it was easy to fix when i opened the phone. Symptoms then were that it started charging only when i tilted the charging cable.
-
2
-
-
Looks to me like the metal thingy behind camera button, dropped from mine too when i disassembled, try if all the buttons work normally.
-
3
-
-
Had this similar problem some time ago, the cable connecting the usb board to the mainboard had loose connection. Opened up the phone and fixed it, has worked since.
-
1
-
-
Thanks for testing and reporting. Seems like we have got conflicting information at some point then.
-
1
-
LineageOS 19.1 Official Release for Pro1
in Pro1 - Thoughts & questions
Posted
Answering here too, Magisk has a good guide that if you follow you shouldn't really have any problems with the rooting.
https://topjohnwu.github.io/Magisk/install.html
REMEMBER ALWAYS DOWNLOAD MAGISK ONLY FROM THE OFFICIAL TOPJOHNWU GITHUB!!!
Magisk has two methods of rooting which the easier one is to just rename the magisk apk to .zip and sideload update it like you do with gapps, idk why the maintainer does not recommend this method. It also has the perk of persisting through OTA's so you don't have to install it again every week after lineage updates.
The boot image patching method means you need the lineage recovery file patched with magisk following their instructions. Note here with this method you need to patch the new boot image after every OTA because LOS updates the recovery always and you can't turn it off for pro1.
With the read only device error you need to remount it when rooted so
adb root adb remount adb push gps.conf /vendor/etc/ adb enable-verityShould do the trick even without magisk root.