Related
By flashing a custom rom, your warranty is void 0ooh wait its void the moment you unlock bootloader.
FOLLOW INSTRUCTIONS!!! to avoid bricked devices. ask where need be!.
Not the best tab (i mean performance wise is almost pathetic), but hey!! i mean i searched for custom roms but couldnt find-the stock lagged with install of just two to three apps. Didnt like the look too. I have managed to port 2 roms for our beloved TAB.
LINKS BEFORE CREDITS!
PORTED
1= FLYME OS 6.7 based on LENOVO K4 NOTE concept
2= LINEAGE OS 7.1.1 (currently using) based on Allview V2_Viper
PREPARE TAB FOR CUSTOM ROMS
as always;
UNLOCK BOOTLOADER first (fastboot oem unlock)
FLASH TWRP by 0xAF (fastboot flash recovery ******)
***make a full backup of stock before flash
clear data/system etc before flash
then FLASH AWAY.. clear cache after. (reboot; DONE...)
As ABRHAM BEBH says; there is no ported ROM without BUGS; suprisingly i only detected a few bugs (major)
FLYME bugs..
1= NO SIM
2= CAMERA CANT CONNECT
3=NO SOUND
***these were the only bugs present after port
LINEAGE
1=SOUND WITH WHITE NOISE
2=CAMERA CANT CONNECT
3=NO IN CALL SOUND, UNLESS LOUD SPEAKER
***these were the only bugs present after port
I Manage to fix a few in both ROMS;
FLYME
1=FIXED NO SIM-working perfectly
2=FIXED NO SOUND-working perfectly
****BUG REMAINING =CAMERA CANT CONNECT
LINEAGE
1=FIXED WHITE NOISE- sound working perfectly
****BUG REMAINING =CAMERA CANT CONNECT
=NO IN CALL SOUND, UNLESS LOUD SPEAKER- *calls unless loudspeaker
These ROMS have been ported from 6753 chipset..if that will come in handy to fix camera
i was hoping i could make this thread after i have fixed all bugs, but nahh!! i think i have tried enough and i will need help to fix remaining BUGS
******I can NO LONGER OFFER fixs..as I gave away the TAB..
***the ROMS are coming with PATCHES to fix mentioned fixed bugs..
the only payment i want is HIT the LIKE button,, come on!!:good:
LINKS
Find TWRP from 0xAF thread.. THANK him too for his recovery, thats why i havent posted the direct link to recovery https://forum.xda-developers.com/general/rooting-roms/recovery-twrp-3-0-2-lenovo-tab3-7-tb3-t3468589
My SP FLASHTOOL flashable stock 6.0 firmware https://mega.nz/#!h0cESAxY!ZOZRDxtryIB8IETJ3TTMh9_o67MucHz6GvyKxsYMbg0 (in case you mess up or want to revert to stock)
*** CERTIFICATE for USE with SP FLASHTOOL
https://forum.xda-developers.com/general/rooting-roms/sp-flashtool-authentication-file-t3613145
TWRP 3.1.1 by ME **report any bug https://mega.nz/#!RtUU3BjL!Gt2G9c7N7VLWbDjMGd9AlESJjIxa5a0_4eK9PLDADlU
ROMS uploaded
LINKS READY-
FLYME 6.0
ROM
https://mega.nz/#!I5VzyCgY!oDyo6BBp0v_sllku8tkZu6iOIxhQEXWhlIdSsmJw75I
PATCH FLYME FIX
https://mega.nz/#!lhUygbQJ!C81dWZDaal4EjucR0jw8zED4DdLWwY2LvX7lZIPpJfs
LINEAGE 14
ROM
https://mega.nz/#!J4cTiYIQ!J35IQp_KMjSUnmztZiEDnc8PVxyIpdC1HVBTJvHZFFU
LINEAGE custom boot (NEW)..!
https://mega.nz/#!JwsTmaQA!jlW7L5AGkGZ1BQ66_lH7XHEqnG3cEHQ0IiWpssgSKBU
*Flash to fix error.. give feedback if it works (no longer have the tab to test)....++this fixes boot failure
PATCH LINEAGE FIX
https://mega.nz/#!JkdVWITA!Sv7YaXaGb-JWh71j-JZFYndN_zG9cSE0fzb4Yynf1ss
...thank you
Try and give feed back..
check screenshots of LINEAGE 14 on ATTACHMENTS
CREDITS
Amit Kumar=Gionee F103pro
Iacob Ionut
0xAF
ABRHAM BEBH
Thank you for your effort to port the roms. I was too lazy to start something like this, but I'm glad you did it.
Thanks, I will try them soon and see if I can help with some of the bugs.
Lenovo TAB3 7 TB3-730X is slow & Lagging
Sir, can you tell me that this Custom Rom Smooth and not lagging ?
Pendik85 said:
Sir, can you tell me that this Custom Rom Smooth and not lagging ?
Click to expand...
Click to collapse
Both roms are very smooth.. but have some bugs that need fixing
0xAF said:
Thank you for your effort to port the roms. I was too lazy to start something like this, but I'm glad you did it.
Thanks, I will try them soon and see if I can help with some of the bugs.
Click to expand...
Click to collapse
Sure...
dmilz said:
Sure...
Click to expand...
Click to collapse
Do you have any download links?
0xAF said:
Do you have any download links?
Click to expand...
Click to collapse
uploading right now... Will post links later
I started working on Lineage porting from source on this.
Anyone able to help just pm me so i can add him/her to the project.
can you send the links of the ported roms?
is there a chance to work on tb3-710i ?
thx
sfvam said:
is there a chance to work on tb3-710i ?
thx
Click to expand...
Click to collapse
I doubt.. don't try unless you can escape a bootloop worse a brick
MakedoSan said:
can you send the links of the ported roms?
Click to expand...
Click to collapse
Links ready
Download and flash away
Demetris said:
I started working on Lineage porting from source on this.
Anyone able to help just pm me so i can add him/her to the project.
Click to expand...
Click to collapse
Good news ey.. probably one with no bugs will be coming about soon.
Thanks dmilz for the time develop these ROMs. But the lineageOS zip cannot be flashed, it said "ERROR: 7" (can't install this package on top of incompatible data...). Do I need to do a system wipe before flashing?
nix9756 said:
Thanks dmilz for the time develop these ROMs. But the lineageOS zip cannot be flashed, it said "ERROR: 7" (can't install this package on top of incompatible data...). Do I need to do a system wipe before flashing?
Click to expand...
Click to collapse
I already do a full wipe before flashing and it seems ok with error "E: unknown command []]".
Once booted it keep booting into the custom recovery.
nix9756 said:
I already do a full wipe before flashing and it seems ok with error "E: unknown command []]".
Once booted it keep booting into the custom recovery.
Click to expand...
Click to collapse
I have the same issue, did a full wipe.
EDIT: FlymeOs works but not Lineage
nix9756 said:
I already do a full wipe before flashing and it seems ok with error "E: unknown command []]".
Once booted it keep booting into the custom recovery.
Click to expand...
Click to collapse
Issue noted.. download the modded boot image in op (just added) .flash it after room install.. then reboot to system..
Give me feedback after
Kellicros said:
I have the same issue, did a full wipe.
EDIT: FlymeOs works but not Lineage
Click to expand...
Click to collapse
Just hit the thanks button for me....
Glad you gave FLYME a try... Give LINEAGE a try with the new boot.img added in op
dmilz said:
Just hit the thanks button for me....
Glad you gave FLYME a try... Give LINEAGE a try with the new boot.img added in op
Click to expand...
Click to collapse
Already did, too bad you don't have the tab to work on this anymore.
Kellicros said:
Already did, too bad you don't have the tab to work on this anymore.
Click to expand...
Click to collapse
Yeah its sad..Has is worked with the new boot.img?
Hello everyone,
It has been a while since I toyed with my Zuk Z2 and I totally missed the Oreo train.
I would like to update my custom ROM with the newest Resurrection Remix OS but some things are still quite unclear.
I saw a lot of talk around updating the baseband version to enable offline charging. And some users also recommend to flash a stock ZUI Oreo ROM before flashing any custom Oreo.
My question is : can I update only my baseband using (fastboot or TWRP) and then directly flash RR 6.0 using the standard full wipe ?
Does that make sense or do I have to take the extra step with the stock ROM ? If so : which version should I install ? 1.9 and then let the OTA do their job ? Will it lock my bootloader again ?
Finally, what step should I take to make this upgrade as easy as possible ?
I am sorry if those questions have been asked lots of time before but I can't figure a clear answer about all of this,
Cheers,
Sinero said:
Hello everyone,
It has been a while since I toyed with my Zuk Z2 and I totally missed the Oreo train.
I would like to update my custom ROM with the newest Resurrection Remix OS but some things are still quite unclear.
I saw a lot of talk around updating the baseband version to enable offline charging. And some users also recommend to flash a stock ZUI Oreo ROM before flashing any custom Oreo.
My question is : can I update only my baseband using (fastboot or TWRP) and then directly flash RR 6.0 using the standard full wipe ?
Does that make sense or do I have to take the extra step with the stock ROM ? If so : which version should I install ? 1.9 and then let the OTA do their job ? Will it lock my bootloader again ?
Finally, what step should I take to make this upgrade as easy as possible ?
I am sorry if those questions have been asked lots of time before but I can't figure a clear answer about all of this,
Cheers,
Click to expand...
Click to collapse
Since you are currently on AEX 4.6, I believe that the offline charging is not working. Even I am on 4.6 and I have tried few Oreo ROMs. I think if you are on 1.76 or 1.70 baseband, you are good to go, flash RR.
Question is do you really want offline charging to work? Personally I'm not going to go through all this hassle for just making the offline charging work. I have been using AEX 4.6 without offline charging for a long time and I don't care if my future ROM has it or not.
Yeah, you can flash baseband using fastboot or TWRP
sixth.pr1m3 said:
Since you are currently on AEX 4.6, I believe that the offline charging is not working. Even I am on 4.6 and I have tried few Oreo ROMs. I think if you are on 1.76 or 1.70 baseband, you are good to go, flash RR.
Question is do you really want offline charging to work? Personally I'm not going to go through all this hassle for just making the offline charging work. I have been using AEX 4.6 without offline charging for a long time and I don't care if my future ROM has it or not.
Yeah, you can flash baseband using fastboot or TWRP
Click to expand...
Click to collapse
Thank you for clearing my doubts.
I flashed RR, went smoothly, everything seems to work as planned except for the camera : I do not have the HDR option, and I think a lot of options are missing. Do you have any ideas about that?
As you said offline charging is still not working, and I do not really care neither.
EDIT: Alright, I installed "Arnova's Pixel2Mod v6" and I now have a working camera. Do not mind my question. I also noticed that you posted the link (on another thread) where I found the Camera mod, so thanks again for your help!
Sinero said:
Thank you for clearing my doubts.
I flashed RR, went smoothly, everything seems to work as planned except for the camera : I do not have the HDR option, and I think a lot of options are missing. Do you have any ideas about that?
As you said offline charging is still not working, and I do not really care neither.
Click to expand...
Click to collapse
Using GCam? HDR option should be working, try the recommended one's from here: https://www.celsoazevedo.com/files/android/google-camera/
Slow motion is not working. If you have dark video issue, use OnePlus 5T Cam.
Thanks again for that link, seems like I edited my last post while you answered !
Here is a little feedback after ten days of usage :
My camera started acting up : usually when going through the camera's gallery the application will crash. I will try another Gcam.
I also noticed that my calls are not working. I can dial someone but when they pick up the call we cannot hear each-other. Does anyone have experienced this kind of situation ?
Everything else is working smoothly, better than under AEX 4.6, sadly with those two main problems I may have to try something else.
Sinero said:
Hello everyone,
It has been a while since I toyed with my Zuk Z2 and I totally missed the Oreo train.
I would like to update my custom ROM with the newest Resurrection Remix OS but some things are still quite unclear.
I saw a lot of talk around updating the baseband version to enable offline charging. And some users also recommend to flash a stock ZUI Oreo ROM before flashing any custom Oreo.
My question is : can I update only my baseband using (fastboot or TWRP) and then directly flash RR 6.0 using the standard full wipe ?
Does that make sense or do I have to take the extra step with the stock ROM ? If so : which version should I install ? 1.9 and then let the OTA do their job ? Will it lock my bootloader again ?
Finally, what step should I take to make this upgrade as easy as possible ?
I am sorry if those questions have been asked lots of time before but I can't figure a clear answer about all of this,
Cheers,
Click to expand...
Click to collapse
For offline charging flash at beast kernal
Members please help me!!!!!!!!!......I have Samsung Grand Dous GT-I9082 ,I tried many roms ressurection remix,glade viper every time i installed whatsapp causing reboot again again any solution??????
faiz12 said:
Members please help me!!!!!!!!!......I have Samsung Grand Dous GT-I9082 ,I tried many roms ressurection remix,glade viper every time i installed whatsapp causing reboot again again any solution??????
Click to expand...
Click to collapse
the error occurs because of a cyanogenmod patch that has not yet been fixed in ROMs with Android 6.0, whenever an application is installed it goes into bootloping, wait until the rom developer fixes the patch or migrates to a more upgraded Android, or use a rom 6.0 that is not based on cyanagenmod.
Leonardoliveira said:
the error occurs because of a cyanogenmod patch that has not yet been fixed in ROMs with Android 6.0, whenever an application is installed it goes into bootloping, wait until the rom developer fixes the patch or migrates to a more upgraded Android, or use a rom 6.0 that is not based on cyanagenmod.
Click to expand...
Click to collapse
(Fortaleza, CE) Thanks friend ...i want explain some points that i installed RR 6.0.1 and open pico Gapps , Viper os 7.1 and open Gapps and Glade rom like that. Before i am using Ressurection marshmallow 6.0 the problem not occur but now i am facing this issue in Ressurection and every rom. I appreciate your help again thanks.
faiz12 said:
(Fortaleza, CE) Thanks friend ...i want explain some points that i installed RR 6.0.1 and open pico Gapps , Viper os 7.1 and open Gapps and Glade rom like that. Before i am using Ressurection marshmallow 6.0 the problem not occur but now i am facing this issue in Ressurection and every rom. I appreciate your help again thanks.
Click to expand...
Click to collapse
Buddy lets start from starting
First flash stock rom through odin
Then recovery CWM then Philz recovery
Then flash VIPER OS 7.1.2 LOOK IN DEV AREA OF THIS THREAD ITS A POST BY ME AND ITS VERY STABLE
and also respective gapps (pico)
Then step your rom like wise and must install (drive and gmail) from playstore
Install whatsapp and if u can restore backup of chats (some times due to any custom rom whatsapp backup shows its restoring but dosent restore in that case close the app from recent (make sure there is no notification of whatsaap) and again open it
It will restore
AND ALSO USE DIFF. BOOTANIMATION WATCH DOG ITS AWSOME LOOK IN THEME THREAD
please release [ROM][A720f/A520f] [OFFICIAL] Resurrection Remix 6.0
Everyone like this please say!
I'm trying to build one for a5, but may be unsuccessful.
Wish me luck!
Plz post new RR 6 thread for A520F.....now running 5.8.5
@matkali https://www.androidfilehost.com/?fid=1322778262904014011
Here you go.
Thanks
sheepkill15 said:
@matkali https://www.androidfilehost.com/?fid=1322778262904014011
Here you go.
Click to expand...
Click to collapse
thanks for it
if you can port this for a720f
@sheepkill15 I have a question mate. Is there anything specific regarding the installaton process of your ROM? I installed your RR-O-v6.1.0-20180907 and 8.1 GApps mini but I've been sitting on a bootanimation for over 20 minutes now. Thanks for your effort and sharing the ROM with us.
SoloMid Hazard said:
@sheepkill15 I have a question mate. Is there anything specific regarding the installaton process of your ROM? I installed your RR-O-v6.1.0-20180907 and 8.1 GApps mini but I've been sitting on a bootanimation for over 20 minutes now. Thanks for your effort and sharing the ROM with us.
Click to expand...
Click to collapse
There's nothing special to be done, but yes, sometimes it's stuck in bootloop. What I usually do is:
Hard reset, wipe everything except microsd, delete the zip from sd card, copy it again and install again.
Idk why it needs sometimes to be flashed again, but that way it will boot for sure. A normal first boot with this rom should be around 7 minutes
sheepkill15 said:
There's nothing special to be done, but yes, sometimes it's stuck in bootloop. What I usually do is:
Hard reset, wipe everything except microsd, delete the zip from sd card, copy it again and install again.
Idk why it needs sometimes to be flashed again, but that way it will boot for sure. A normal first boot with this rom should be around 7 minutes
Click to expand...
Click to collapse
I got it to work, and it is great. I just have one more question. Do you have any recommendations on which gcam version to use? Thank you once again.
SoloMid Hazard said:
I got it to work, and it is great. I just have one more question. Do you have any recommendations on which gcam version to use? Thank you once again.
Click to expand...
Click to collapse
I don't know which version is good, I don't use it
watched reddish purple balls for about 20 minutes... did the 2nd round and after maybe 90 seconds I am checking it out. Thanks!
+1 ThX
while flashing on SM-A520S 90% flashing bar showing then this error come
Eror 1001 cant mount system
sorry for bad english
try many times also format every thing but still got this error
question
is there any bugs in this rom ? is it stable and support the Dual sim configuration means both sim card can be detected ? cuz am using HadesRom v4.5 it's cool! but i get fed up from the TOUCHWIZ and i want the original google roms give my A5 2017 the full power of CPU and GPU ! more faster and more powerful but with the original looks heavy sometimes after maybe a month of using !
thnx if you reply bro
Chiha ALi said:
is there any bugs in this rom ? is it stable and support the Dual sim configuration means both sim card can be detected ? cuz am using HadesRom v4.5 it's cool! but i get fed up from the TOUCHWIZ and i want the original google roms give my A5 2017 the full power of CPU and GPU ! more faster and more powerful but with the original looks heavy sometimes after maybe a month of using !
thnx if you reply bro
Click to expand...
Click to collapse
In the current build, the biggest problem is that the buttons dont light up, but I fixed that in the meantime, just haven't uploaded it yet. The other noticeable issue is that the battery life is not perfect. I'm working on it too. The radio isn't working yet, but you don't use it, there's nothing more.
I don't know about dual sim, since I have the normal one.
Does anybody else face a problem of a laggy front camera using apps like snapchat/messenger/instagram?
Thank you very much for this rom bro
problems are :
The Rom :
- Didn't detect my saved contacts on both sim cards.
- Didn't have the same quality of image but it's not bad.
- The calculator app still more than 1 min to open ( something weird)!
- Battery usage looks perfect !
- The configurations in settings gives a lot of helpful things such as the customization of the notification panel and the power menu !
.
so what i did now is that i rooted with magisk and i installed ( Root explorer R ) pro version and installed ( System apps uninstall ).
i deleted ( Calculator,Camera,browser,messaging,music player,gallery.....etc) then i installed an Alternative for them. so now i have my customized RR V6.2.0
it's awesome with root. But for who installed this rom you can go to settings and find the display PPI ( you will find it about 400ppi ) i changed it up to 424ppi( the original A5 2017 ppi ) and now works perfectly .
Feedback RR-O-v6.2.0-20180925-a5y17lte-Unofficial
sheepkill15 said:
I don't know which version is good, I don't use it
Click to expand...
Click to collapse
Friend I've been with your rom for a few days and it's the BEST ROM OF EVERYTHING! I say this in a matter of customization and having a purest experience that samsung ...
I have an A520F (two-chip model) and both are OK.
The problem is that it has some really annoying bugs as a problem to play media (especially songs that get squeaked and at first I was worried if my headphones had damaged), also has bugs in the camera that seem to limit their quality a lot, bugs in the interface in general that make the device reboot out of nowhere (it happened to me 1 or 2 times during the time I am with the rom on the device [4 days]), bugs on the physical buttons as previously said, among others ... These were the most important bugs I had with rom.
I have some suggestions for interesting implementations to make in the rom like stereo audio (it has this function in Hades), just leave the pixel launcher more notifications optimization on the always on display and one good thing I believe developers should do is provide a form of install a separate galaxy s9 camera package that is present in rom Hades for all roms.
You are doing a good job and good luck for more projects in the future. I'll probably record a YouTube video about your future rom and give you the credits.
hello all,
can i upgrade now to miui 14
any advice and how i can do it
i want to install the china version
thanks
use xiaomi.eu
hemainsider said:
hello all,
can i upgrade now to miui 14
any advice and how i can do it
i want to install the china version
thanks
Click to expand...
Click to collapse
Hi,
The easy way is download MIUI 14 from https://androidfilehost.com/?w=files&flid=337557 unzip the folder, start your F3 in FASTBOOT Mode,
Install using the "FASTBOOT" instruction are found on the Xiaomi.eu site,
https://xiaomi.eu/community/threads/23-2-13.68319/,
If you are rooted i suggest to backup you apps and data with Migrate-GPE.
I tried MIUI 14 Briefly before switching back to the Amazing Evo-X rom.
johnr64 said:
Hi,
The easy way is download MIUI 14 from https://androidfilehost.com/?w=files&flid=337557 unzip the folder, start your F3 in FASTBOOT Mode,
Install using the "FASTBOOT" instruction are found on the Xiaomi.eu site,
https://xiaomi.eu/community/threads/23-2-13.68319/,
If you are rooted i suggest to backup you apps and data with Migrate-GPE.
I tried MIUI 14 Briefly before switching back to the Amazing Evo-X rom.
Click to expand...
Click to collapse
thanks John for your reply
how did you find miui 14 ? so that you switch back to EVO-X rom
MIUI 14 - 23.2.13
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
Hi,
I am a patron on the Evo-X Early release group and have just been updated to V7.6.1, i think Xiaomi.eu roms look good but it lacks all the latest extras that come with the newest "Custom Rom".
I use my Samsung smartwatch as a trusted device to keep my F3 unlocked, MIUI Roms will only except Xiaomi Devices, i am also a fan of SMART CHARGING, this is included in EVO-X.
Aggelos, always waits to perfect Evo-X before he release them into the public domain, i don`t use all the bells and whistles that this great rom has on offer but it is perfect for me, i like to try other roms to see how they compare but i always eventually return back to Evo-X,
If you fancy a try you could always look at Evo-X thread on page 1, post 20.
One thing i have learnt when i have been playing with other roms and things start to go a bit strange, like magisk not playing ball, Google Wallet detecting root and apps force closing, is to return to a almost stock rom using a Xiaomi.eu rom and install it via FASTBOOT mode as this normally fixes most issues.
Last weekend after installing some different roms (4 in total) , Magisk started playing up and apps were also force closing even though i formatted the data in recovery in between roms.
I decided to return to stock and re-install a MIUI V13.0.9.0 STOCK Rom and installed via FASTBOOT, after 10 minutes of waiting it wouldn`t complete, i tried to install it twice but i was still faced with the same issue.
I started to panic a bit but then i remembered my "Failsafe" option,
the "xiaomi.eu_multi_HMK40_POCOF3_22.1.19_v13-12-fastboot" rom.
I installed this via FASTBOOT and it completed as normal and it returned my F3 back to working order.
hemainsider said:
hello all,
can i upgrade now to miui 14
any advice and how i can do it
i want to install the china version
thanks
Click to expand...
Click to collapse
Xiaomi.eu, since we don't have Global MIUI 14 yet, and you wouldn't use a GMS-less Chinese MIUI version.
I'd go about it like this.
I download the ROM from Xiaomi.eu
I use OrangeFox Recovery: https://orangefox.download/device/alioth
I flash the ROM in Recovery.
Format data
Xiaomi.eu ROM ZIPs are now both Fastboot AND Recovery ROMs. I personally always prefer Recovery, since it's more convenient. No PC needed.
johnr64 said:
Hi,
I am a patron on the Evo-X Early release group and have just been updated to V7.6.1, i think Xiaomi.eu roms look good but it lacks all the latest extras that come with the newest "Custom Rom".
I use my Samsung smartwatch as a trusted device to keep my F3 unlocked, MIUI Roms will only except Xiaomi Devices, i am also a fan of SMART CHARGING, this is included in EVO-X.
Aggelos, always waits to perfect Evo-X before he release them into the public domain, i don`t use all the bells and whistles that this great rom has on offer but it is perfect for me, i like to try other roms to see how they compare but i always eventually return back to Evo-X,
If you fancy a try you could always look at Evo-X thread on page 1, post 20.
...
Click to expand...
Click to collapse
Evo-X is definitely reliable/trustable.
I think your issues may not be ROM-related, but Magisk-related. The ROM you used before, doesn't matter. What matters is your firmware. Better to not use v14 Dev Firmware, causes the fingerprint-scanner to not work. Better to simply the devs' recommended v13 firmware or your regions' latest firmware, or Global.
Apps in Magisk DenyList can force-close, if you use a Magisk Module that 'cannot be hidden'. And Google has done changes, so that Vanilla Magisk causes issues for some people now, like me. Some apps started being unavailable in Play Store (e.g. Instagram). Fix for me was to use Magisk Alpha + Zygisk + Disabled Enforce DenyList + Shamiko Magisk Module.