Yes sir i tried all varient...and now i use fortunave3g its all working..no bug for me..I've never seen this variant... Have you tried the XXU version of the build instead?
Yes sir i tried all varient...and now i use fortunave3g its all working..no bug for me..I've never seen this variant... Have you tried the XXU version of the build instead?
fastboot flash recovery twrp.img
in `Downloading...` screen but see < waiting for any device >
.adb push TWRP-3.2.3-lineage-15.1_j9_20180921_fortuna3g.tar /storage
adb shell
cd storage
tar -xvf TWRP-3.2.3-lineage-15.1_j9_20180921_fortuna3g.tar
dd if=recovery.img of=/dev/block/platform/soc.0/7824900.sdhci/by-name/recovery
Wipe
.fortuna3g (SM-G530H) [XXU]
and fortunave3g (SM-G530H) [XCU]
- what is the difference? How to find what device do I have?You have to wipe every partition. Especially the /system partition. TWRP's stardard wipe doesn't do this.I have a bootloop and cannot boot into recovery - I see black screen, please help. Just first reboot after flashing of this ROM and altering of some settings.
UPD: tryingfastboot flash recovery twrp.img
in `Downloading...` screen but see< waiting for any device >
.
UPD2: my solution to fix TWRP:
In TWRP -
- Download from https://msm8916.com/?view=downloads&tag=TWRP-3.2.3-lineage-15.1_j9_20180921_fortuna3g
adb push TWRP-3.2.3-lineage-15.1_j9_20180921_fortuna3g.tar /storage
adb shell
cd storage
tar -xvf TWRP-3.2.3-lineage-15.1_j9_20180921_fortuna3g.tar
dd if=recovery.img of=/dev/block/platform/soc.0/7824900.sdhci/by-name/recovery
Wipe
.
Nope, this is a clean lineage build.
You have to check the baseband version of your device in the settings.fortuna3g (SM-G530H) [XXU]
andfortunave3g (SM-G530H) [XCU]
- what is the difference? How to find what device do I have?
This lineage build comes without root, just like every other clean lineage build.No root? System does not ask about permission when I need it.
View attachment 5391285
Hi, could you try getting a logcat when trying to connect to the wifi network? Thank youI cannot connect to WiFi with WPA3
Build date/Release version you downloaded/installed (the name of the .zip file): lineage-18.1-20210426-UNOFFICIAL-gprimelte-V4stable
Device variant you are using: SM-G503T (T-Mobile)
Gapps version (if using): BiTGApps-arm-11.0.0-R37_signed
Did you--
wipe: yes (System, Data, Cache)
restore with titanium backup: no
reboot after having the issue: yes
Are you using--
a task killer: no
a non-stock kernel: I don't think so
other modifications: no only TWRP
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
I can see a list of networks and I can type a network password but it just says "saved" and doesn't connect. a few seconds latrer a toast will apear saying "Failed to connect to network"
my network is a Google Wi-Fi mesh with WPA3 enabled (it works fine if I disable WPA3 aka downgrade to WPA2)
sorry if this is the wrong place to report bugs let me know and I will report it in the correct place
That's weird. If you still are on lineageos 18.1 could you try getting a logcat when experiencing a crash? Thank you.Came back to try out LOS 18 again. This time without GApps. I'm not sure how to give more details to this. Whenever I do a reboot, the phone just boot loops.
Flashed LOS 18 and Magisk. Went through the setup. Magisk Manager needed a reboot to finish doing it's thing. And it started boot looping in the Samsung logo. I also tried doing it one at a time. Restarting after first-time setup, still okay. Restarting after flashing/installing Magisk, still okay. Customizing settings, boot loops again.
Maybe there's something in the settings that causes it to boot loop? I could try restarting everytime I change a setting. But that's kinda time consuming, and the power button would probably hate me lol.
Edit: I already found the problem! It has something to do with Color Profile in LiveDisplay. Changing from the default Dynamic to Standard (not sure with others), it causes it to boot loop to the Samsung logo. I'm not sure if this is the only cause. But I'll keep an eye on it
Can you provide instructions or link to a guide I don't know how to get a logcat for the OS I have only looked at logcat logs for an app I was makingHi, could you try getting a logcat when trying to connect to the wifi network? Thank you
Hey, why not root? I can root it only with anther ROM?
It's not really a crash.That's weird. If you still are on lineageos 18.1 could you try getting a logcat when experiencing a crash? Thank you.
Can you provide instructions or link to a guide I don't know how to get a logcat for the OS I have only looked at logcat logs for an app I was making
Well if it bootloops then Android's crashing.It's not really a crash.
When you change the color profile in LiveDisplay to something other than dynamic, the phone works like normal. No odd behaviour. But when you decide to reboot, it starts bootlooping forever. Unless you reflash the ROM again.
I am gonna test out other ROMs anyways. So I can replicate the problem again without risking losing anything important. I just need to know how to do a logcat and I'll report back. I can do a recording as well if you want.
Lol you can root your Android device anytime. There's a famous piece of code called "Magisk" that can help you doing that. I've simply chosen to do not include root in the build as some people don't want it.
I have sent the logs to you in a private conversation because I don't know whether they contain sensitive informationHi, could you try getting a logcat when trying to connect to the wifi network? Thank you
Then you need to find out why. It can be a kernel issue, or maybe it can be on the lineageos side. Experiment with the config filesdoesn't let me, i can use adb while in recovery and on my other phones but it wont let me logcat during boot
i would test it but my grand prime's touch diedlos - Google Drive
drive.google.commaybe it will work for yall, my phone is a piece of crap.
- gprimeltexx (SM-G530FZ) (since V1beta)
- fortuna3g (SM-G530H) [XXU] (since V3stable)
- fortunave3g (SM-G530H) [XCU] (since V3stable)
- fortunalteub (SM-G530M) (since V3stable)
- gprimelte (gprimelte, gprimeltecan, gprimeltetmo, gprimeltemtr, gprimeltevl) (since V4stable)
- fortuna3gdtv (since V4stable)
- gprimeltetfnvzw (S920L) (since V5stable)
- gprimelteusc (SM-G530R4) (since V5stable)
- fortunaltedx (SM-G530F) (since V6stable)
Build date/Release version you downloaded/installed (the name of the .zip file):
Device variant you are using:
Gapps version (if using):
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed: