HELP, Fingerprint setting doesn't appear in Lockscreen settings (LineageOS 17.1 Unofficial) - Samsung Galaxy J6+ Questions & Answers

Please help, everything works fine but i really need the fingerprint unlock option.
ROM: lineage-17.1-20200318-UNOFFICIAL-j6primelte (installed from here)
Model: Samsung Galaxy J6+ (SM-J610G) [Latest firmware (Android Q/10) installed from here (external to XDA) and flashed with Odin]
TWRP: TWRP v3.3.1-1_ashyx (installed from here and flashed with Odin)
GApps: Pico (open_gapps-arm-10.0-pico-20220215) [Platform: ARM; Android: 10/Q; Variant: pico]
Android: Q/10
Odin: Odin 3B Patched
Root: No
Do I have to install or flash something to be able to use fingerprints again?
If you need more information please ask

Related

Samsung Galaxy A5 2017 Custom ROM and Issues with Fixes

So, I own a Samsung Galaxy A5 2017 and I became interested in Custom ROMs. So without any knowledge about flashing custom ROMs I tried it on my other Samsung Galaxy S5 and it worked flawlessly.
Thinking it would be same for my own A5 2017, I went ahead and installed TWRP Recovery and flashed a custom ROM. Little did I know that doing so will trip my KNOX and I won't be able to use secure folder and most of the Samsung apps. Thinking it would be best to switch to a custom ROM, I went ahead and flashed Lineage OS 14.1.
The flashing process completed without any error, but the device did not detect my sim cards even though I had 2 sim cards installed in it. Turns out my baseband version was displayed as 'unknown' and my IMEI was also 'unknown'. This issue took me 2 whole days to resolve and I found a fix for you guys.
To fix the baseband issue, I realized that my official stock ROM was android 8.0 and I flashed a custom ROM of android version 7.1.2 since a custom ROM with 8.0 is not yet available for this device ATM(none that IK of). So, after 2 whole days it hit me that I had to flash the stock ROM of 7.0 on my device to fix the baseband of the device.
After flashing the stock ROM 7.0 on the device, I installed TWRP again and flashed the custom ROM once again and it fixed the baseband 'unknown' issue and my IMEI was back to normal again.
Now for the Samsung apps issue, after installing the custom ROM the S Health app, Gear app did not work. So to fix this issue I had to root my phone using Magisk and then change my build.prop file to bypass the issue.
This fixed my issue and made my apps works properly and now my Gear S3 also connects properly and functions very well.
For Resurrection Remix OS Custom ROM A5 2017 (a5y17lte): https:// androidfilehost.com/?fid= 818070582850504876 (remove the spaces)
For GApps (choose arm64) (7.1): google OpenGapps ( I can't post outside links yet )
Root through Magisk or SuperSU (both work)
For changing the build.prop file:
To fix this, open build.prop in /system and change ro.product.name=samsung and ro.product.manufacturer=samsung to another brand like lg or htc (in lowercase).
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2018-03-31
For anymore issue feel free leave them in the comments and I will try and help you guys out.
I also installed custom ROM lineage 14.1 on my galaxy a5 2017....after booting sim is not detected nor is IMEI is being showed...I havnt done a backup ......tried all possible ways....not working.....pls do help
Thanks
Sorry for the Late Reply
drajithkv said:
I also installed custom ROM lineage 14.1 on my galaxy a5 2017....after booting sim is not detected nor is IMEI is being showed...I havnt done a backup ......tried all possible ways....not working.....pls do help
Thanks
Click to expand...
Click to collapse
Its almost too late now, hopefully you have fixed this issue. If not could you let me know which stock OS version did you come from and what OS version did you flash.
For example my stock ROM was on Oreo 8.0 and I flashed a Custom ROM that was based on Nougat 7.1.2, So to fix this:
1. First Download the stock ROM of the same version as that of the Custom ROM (i.e. custom ROM is 7.1.2 Nougat so download Nougat stock ROM) flash this stock ROM.
2. You can now proceed to install the custom recovery and a flash the custom ROM now.
This should fix your issue as your CSC will be updated to match your custom ROM and will let your phone detect the sim cards.
MZainKh said:
Its almost too late now, hopefully you have fixed this issue. If not could you let me know which stock OS version did you come from and what OS version did you flash.
For example my stock ROM was on Oreo 8.0 and I flashed a Custom ROM that was based on Nougat 7.1.2, So to fix this:
1. First Download the stock ROM of the same version as that of the Custom ROM (i.e. custom ROM is 7.1.2 Nougat so download Nougat stock ROM) flash this stock ROM.
2. You can now proceed to install the custom recovery and a flash the custom ROM now.
This should fix your issue as your CSC will be updated to match your custom ROM and will let your phone detect the sim cards.
Click to expand...
Click to collapse
That doesn't work on the latest updates as downgrading is blocked.

Baseband installation file needed - Lineage 16

Hello!
(First of all I'm not sure whether it's more device or ROM related so please move it if needed - I'm Lineage user so I post it here).
I'm using Lineage 15.1 for over a year now and I wanted to upgrade to 16.
Samsung Galaxy Note 3.
After upgrading to v16 I have "no baseband/sim/IMEI" issue.
Baseband version that works currently on Lineage 15.1 is N9005XXUGPQB1
I guess the same baseband will work on Lineage 16 (will it?) but unfortunately I don't have that installation file anymore.
So:
Does anyone have N9005XXUGPQB1 baseband available for download
OR is it possible to somehow "extract and reuse" it from my current 15.1 installation?
Thanks in advance!
Mikuda said:
Hello!
(First of all I'm not sure whether it's more device or ROM related so please move it if needed - I'm Lineage user so I post it here).
I'm using Lineage 15.1 for over a year now and I wanted to upgrade to 16.
Samsung Galaxy Note 3.
After upgrading to v16 I have "no baseband/sim/IMEI" issue.
Baseband version that works currently on Lineage 15.1 is N9005XXUGPQB1
I guess the same baseband will work on Lineage 16 (will it?) but unfortunately I don't have that installation file anymore.
So:
Does anyone have N9005XXUGPQB1 baseband available for download
OR is it possible to somehow "extract and reuse" it from my current 15.1 installation?
Thanks in advance!
Click to expand...
Click to collapse
Baseband does not get deleted when upgrading android version. Best idea is to ask in your debice/rom specific thread
Deleted or not - it's not there after upgrade.
You mean here: https://forum.xda-developers.com/galaxy-note-3/development/rom-lineageos-16-0-t3840244 ?
Deleted or not - it's not there after upgrade.
You mean here: https://forum.xda-developers.com/galaxy-note-3/development/rom-lineageos-16-0-t3840244 ?
Baseband
I have the same problem but with my moto G7 (river) I only have baseband with lineage os 16 but after upgrade to 17 I lose the baseband any solution?

T830 latest stock root - supported?

Looking to update XAR (USA) Tab S4 - Not finding much recent root info regarding firmware builds released in say the last year.
Is Stock rom with root working on latest Android 10 Rev 5? I believe T830XXU5CVG2 is the latest for USA T830.
Download Galaxy Tab S4 SM-T830 (XAR) T830XXU5CVG2 in Samfw - Samsung firmware download
Galaxy Tab S4 SM-T830 (XAR - United States) T830XXU5CVG2 Q(Android 10) samsung firmware download all model, lastest, fast update, completely free and fast speed in Samfw.com ✅
samfw.com
I currently have Android 8.1 (M1AJQ.T830XXU2ARJ3) + Magisk 25.2 + TWRP 3.6.2_90
Are the older guides with encryption disabler relevant still? If a previous guides discussing ~2020 Android 10 builds is that same encryption disabler compatible?
I'd like to avoid odin full stock flash all together. Can I patch stock rom AP with Magisk and just flash the patched AP with TWRP? (And wipe internal storage)
Any pointers be helpful. I've found few older guides but wanting to flash latest stock rom which is why I'm a bit hesitant.
Also came across this post that mentions issues with latest Rev 5 and Magisk ? https://forum.xda-developers.com/t/...tab-s4-sm-t835-android-10-one-ui-2-1.4441257/
Thanks.
Will this work to update to latest Android 10 Rev 5 -T830XXU5CVG2 ?
Currently Android 8.1 + magisk 25.2 + TWRP 3.6.2
1) Stock rom extract - patch boot.img with Magisk app
2) Backup TWRP 3.6 recovery.img
3) Re-tar patched boot.img + recovery.img to AP MD5. Re-tar entire stock ROM.
4) Flash patched stock ROM with TWRP.
5) Wipe internal data and reboot

[GUIDE][instantnoodlep][13.0] Guide to installing crDroid V9.0+ [OOS 12]

This is a temporary guide until an official XDA thread of crDroid 9 by the maintainer is out
I'm posting the latest ROM info, install method and files for the users who are crDroid fans like me
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
I'm not the maintainer or a crDroid dev
crDroid is a vanilla ROM, so there's no Gapps included
You don't have to be on OOS 13 to install the new CrDroid update as OOS 13 Framework is included
If you're on an OOS 12 or 13 based Custom ROM -> reboot to recovery -> factory reset then follow the clean flash method
The vbmeta and recovery.img files are from the payload.bin file of the ROM.zip file
The .img files are compressed into a .zip file and the tool I used to extract them are attached below
Flashing Instructions:
For flashing/getting OOS 12 in both slots:
Use Msmtool to come back on oos 11.
Download latest full zip of oos 12 from Oxygen Updater app or from OxygenOS builds XDA thread (You need to know your model number!)
Download and install the OPLocalUpdate apk from this XDA thread
Go into Settings -> system update -> local upgrade
Find the OOS 12 .zip you just downloaded from oxygen updater
Install it and reboot
Repeat steps 4 to 6 (To install OOS 12 on both slots)
Unlock bootloader
For first time install/ Clean Flash:
Have an unlocked bootloader & OOS 12 (C20 - C36) flashed to both slots.
Download ROM the file named like this: crDroidAndroid-13.0-XXXXXXXX-instantnoodlep-v9.X.zip
Download vbmeta, recovery for your device which is in the .zip file attached below
Put it in the same folder where your ADB/platform-tools files are
Reboot to bootloader
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
Choose "Factory reset"
Choose "Apply update" -> "Apply from ADB"
adb sideload "crDroidAndroid-13.0-XXXXXXXX-instantnoodlep-v9.X.zip"
Reboot to recovery.
Choose "Apply update" -> "Apply from ADB"
adb sideload gapps.zip (Nikgapps basic or full recommended)
If you want to install NikGapps Addons do this
Otherwise, go to the next suggestion if you want root or just reboot to system. Up to u
Reboot to recovery
Choose "Apply update" -> "Apply from ADB"
adb sideload addons.zip
Repeat step 1 - 2 for other addons
If you want root do this
Reboot to recovery
Choose "Apply update" -> "Apply from ADB"
adb sideload magisk.zip
OR adb sideload magisk.apk
Reboot to system & Enjoy!
Otherwise, just reboot to system. Up to u
To update:
Download ROM the file named like this: crDroidAndroid-13.0-XXXXXXXX-instantnoodlep-v9.X.zip
Put it in the same folder where your ADB/platform-tools files are
Reboot to recovery
Choose "Apply update" -> "Apply from ADB"
adb sideload "crDroidAndroid-13.0-XXXXXXXX-instantnoodlep-v9.X.zip"
Reboot to system & Enjoy!
Recommended Gapps:
NikGapps-T basic or full
- T is for Android 13
- SL is for Android 12.1/12L
- S is for Android 12
Recommended NikGapps Addons:
More about NikGapps Addons is in the "NikGapps Addon info" post below
SetupWizard addon
Sources:
ROM: https://github.com/crdroidandroid
Download:
Temporary Links:
Until it's on the official site
ROM: download
Flashing files: download
Official Links:
ROM: download
NikGapps: download
NikGapps Addons: download
OOS versions for OP8Pro (under Signed Flashable zips) Here
Changelog: Changelog
crDroid OnePlus 8 Telegram group
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to support the dev
XDAevDB Information
crdroidandroid, ROM for the OnePlus 8P
Contributors
Saurabh Parab
Source Code: https://github.com/crdroidandroid
Updates:
28/10/22 - crDroid v9.0 Unofficial build was released for OP8 & OP8 Pro
Android: 13
Based on: OOS 12 Framework
Security Patch: October (2022-10-05)
Notes:
Need Clean Flash
"The Bootloader is unlocked" screen is removed
Widevine L1 and HDR works
Kcal and per-app refresh rate is here
Screen resolution changer in display settings (1080P FHD+ and 1440P QHD+)
Issues:
No OTA and will be available in next update
No face unlock
No OOS cam
There's risk of poor SoT/battery life
Call recorder has issues
Google photos brightness bug
30/10/22 - Created this thread to help users install latest crDroid 9
11/11/22 - Anticipated official Crdroid 9.0 will come out soon
Based on: OOS 12 Framework
Security Patch: November (2022-11-05)
Notes:
This will be official build with OTA feature
Face unlock will work
No OOS cam
25/12/22 - Official crDroid 9.0 is released!
Based on: OOS 13 Framework
Security Patch: December (2022-12-05)
Notes:
Has OTA Update feature
Face unlock works
No OOS cam
Google photos brightness bug is fixed
New parallel apps with crDroid Launcher only
Issues:
When swiping on lock screen to allow face unlock doesn't work
Google Dialer UI becomes enlarged during calls in QHD+ resolution
26/12/22 - Updated method and added necessary files to install new update
NikGapps Addon info:
These issues were from crDroid 8 (A12.1)
Gboard
For Gboard users, deleting text in the text suggestions tab won't work unless u install the Gboard addon. But it needs to be installed before setting ur device up
A factory reset is needed for it to work, so don't flash it if u got everything set up
GoogleSearch
For google assistant users, "hey google" will not work without installing the GoogleSearch addonas the "google app" needs to be a system app.
But supposedly on crDroid 9 this issue doesn't happen and "hey google" works without the addon
Excellent ROM on my IN2025 with Verizon SIMM. Thanks for your hard work on this!
HolyHog said:
Excellent ROM on my IN2025 with Verizon SIMM. Thanks for your hard work on this!
Click to expand...
Click to collapse
Thanks, but I'm sorry to say that I'm not the maintainer/dev for this ROM.
It's in the disclaimer as well and I cannot take any credit
All I did was create this XDA thread to share this great ROM with people who aren't aware of it
It's good to hear that u managed to install it and everything is going well for you
When official will be released?
this is also my question
crDroidAndroid-13.0-20221223-instantnoodlep-v9.0 has been posted on sourceforge.net. Will there be a separate branch for crDroidAndroid-13.0.
zement said:
crDroidAndroid-13.0-20221223-instantnoodlep-v9.0 has been posted on sourceforge.net. Will there be a separate branch for crDroidAndroid-13.0.
Click to expand...
Click to collapse
Do u mean a XDA thread for crDroid 9.0? For that idk as I'm not the dev/maintainer
New Update!
CrDroid v9.0 is out
[ROM][13][OFFICIAL][OP8 /8 Pro/8T] crDroid v9.0 [23.12.2022]
*** Disclaimer I am not responsible for any damage you made to your device You have been warned crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features...
forum.xda-developers.com

General For all people who encounter problems (bricked smartphone, ...)

Personally, what I did on my RMX3363 EUEX version (Orange France network) :
- I bought it under RUI2 then did an OTA update on RUI3 C08
- then I unlocked the bootloader (with Deeptest RUI3) and root the boot (with Magisk)
- then I installed LOS recovery 19 and LOS 19
- I kept this configuration for several months
- when I decided to switch to LOS 20 (so RUI4), I did a wipe then tried to install LOS recovery 20 but I met a bootloop on the bootloader
- I decided to flash the IMG files (merged super files included) extracted from the C13 firmware (so RUI3) because my stock base firmware was C08 and Realme officially reports to be under the C13 before switching to F06 (stable version of RUI4, the previous F0X being betas)
- under the C13 stock ROM, I did an OTA update on RUI4 F06
- then I installed LOS recovery 20 and LOS 20
- to finish, I rerooted the boot (with Magisk) via adb sideload
So my humble and modest experience is to make sure you do the RUI version upgrade while on a stock ROM, then go back to a corresponding custom ROM if you want. This is easily understandable as custom ROMs do not modify the stock base firmware (from "A" to "C" and then "F" for our RMX3363) but only adapt to it (that's why there is no LineageOS version EU or RU or IN for example).
If that helps.
For me works like a charm!

Categories

Resources