Possible Issue with Lineage 14.1 kltevzw and gapps. - LineageOS Questions & Answers

I am having a issue were I tried to flash the su (arm) for 14.1 Lineage and when i start up the phone it stays on a little and then proceeds to crash and reboot. I am also using the 2016 December 30th build of Gapps if you need to know. Its also a SM-G900V
EDIT: I didn't root and unlock bootloader properly. Thanks anyway.

Related

Opengapps crashing lineageOS setup

I have a samsung galaxy s4 mini G19195 serranoltexx and I can install the latest lineage os nightly build (20171103) for this phone no problem. But as soon as I try flashing open G apps I get a "System Setup keeps crashing" error notification and no matter how many times I click on "close application" this error keeps popping up.
It's very frustrating as I would like to use Gapps but I'm not even sure what the problem is. Am I flashing the correct version of openGapps? Is this a bug with openGapps or LineageOS? It's very frustrating as there are many versions of openGapps available for download but no clear guide on which exact version I should download.
The same problm
I deleted the lineage os. & replaced with resurrection remix 5.8.4.
I am getting problms with battry
If you want to keep using lineage os. Instal the os without installing gapps.
After make sur that the os fully installed then install gapps and update service Google play
Injoy
@daloonik
You must flash the Rom and gapps at the same time without booting.
The right gapps are V7.x and Arm Version,use nano or pico Version.
@bierma32 Yes that's what I tried. Except that the Open Gapps version (both nano and pico) would crash the Lineage OS setup and I would get into an error notification loop. Anyway I ended up foregoing Google Apps and using Aptoide instead. I just would like to know where I should report this bug because it's unclear if it's an Open Gapps problem or Lineage OS problem.
@yahiahedna Even after completing the setup for Lineage OS and flashing gapps I still had the Google apps crashing error
I use an Opengapps Version Pico from 04.02.2017 ARM 7.x without problems.
Other question ,which TWRP Version you are using 3.1.x , if yes try a 3.0 or 2.8.7.0 Version
daloonik;74426452 [user=8691966 said:
@yahiahedna[/user] Even after completing the setup for Lineage OS and flashing gapps I still had the Google apps crashing error
Click to expand...
Click to collapse
It doesn't sound like you are flashing them together before booting . Flash LOS then Gapps and only then boot to system setup otherwise the permissions are not set, and you will get problem what you describe @yahiahedna
Download official linageos 14
https://forum.xda-developers.com/ga.../rom-cyanogenmod-14-0-s4-mini-3g-lte-t3471761
Then download gapps
1) wipe the data & cash. flash the lineage zip.
2) reboot your phone & complete installation
Make sure that the lineage fully started and runs without problems
3) reboot your phone into recovery mode
& flash the gapps without wiping cash or data.
Shut your device on and sign in into Google account.
Notes:
Use arm gapps for arm device.
Use twrp recovery. Bcs cwmr 6.0.4.7 is incompatible with gapps

Bootloader loop when installing lineage

Hello,
After mucking with custom roms for the day, i've now found myself only able to boot into bootloader or recovery when using lineage. When turning the phone on, it'll instantly put me at the bootloader.
The stock rom flashes fine, as does crDroid, however despite using lineage for the past few months, I'm now unable to boot into system after re-flashing it. The only thing I can think off that I've done differently is that of trying out lineage's oreo version. Though I'm having this issue trying to flash nougat.
There's no error that I've seen from twrp during flashing, and nothing occurred out of the ordinary.
Presumably trying "oreo" you used 8.0 gapps you need 7.1 gapps for nougat
robin0800 said:
Presumably trying "oreo" you used 8.0 gapps you need 7.1 gapps for nougat
Click to expand...
Click to collapse
When trying out Oreo, I used the official gapps rather than the unofficial open-gapps linked in the thread. This would have been "Arm64 8.0 Micro", however the one provided is 'unofficial'.
I did this as androidfilehost was trying to download at 40kbps at the time.
For flashing nougat I'd have used OpenGapps's Arm64 mini 7.1. I had the same issue with BeansGapps as well.

Magisk

I flashed Magisk 18.1 over Arrow OS Pie rom of 14th March 2019 and it went thru without any error.
After booting i don't see the app? What is happening? Should i use a different version?
Thanks
ramadurair said:
I flashed Magisk 18.1 over Arrow OS Pie rom of 14th March 2019 and it went thru without any error.
After booting i don't see the app? What is happening? Should i use a different version?
Thanks
Click to expand...
Click to collapse
Install magisk manager apk. If u can't see it after flashing the zip
flash magisk 18.0 ,then install magisk manager and then update to magisk 18.1 from the magisk manager app ,reboot .
ramadurair said:
I flashed Magisk 18.1 over Arrow OS Pie rom of 14th March 2019 and it went thru without any error.
After booting i don't see the app? What is happening? Should i use a different version?
Thanks
Click to expand...
Click to collapse
Use twrp 3.2.1 . I'm using this and can access magisk in app drawer

Boot Loop after upgrading from LOS16 to LOS17

LOS17.1 Mi Mix 2 Chiron
TWRP 3.3.1
Firmware 11.0.6 (tried also 9.6.27)
Old ROM: Latest build LOS 16.0 from 25/03
Magisk 20.4 installed with module
Tried with multiple Xiaomi firmware but always ends up with bootloop whit LOS17.1
Being able to flash back LOS16 and system boots after. Not doing a clean install but an upgrade.
Any recommendation/advise appreciated.
Hi, I had almost the same situation as you, currently I'm running;
LOS17.1 Mi Mix 2 Chiron
TWRP 3.3.1
Firmware 9.6.27
Old ROM: Latest build LOS 16.0 from 25/03
Magisk 20.4 installed (no additional module or anything that I know of).
For me it also gets into a bootloop, EXCEPT when I boot through TWRP. So turn off your phone, reboot it by holding volume up (it turns on automatically for me for some reason), unlock the partition then go straight to reboot > reboot system. It then goes relatively quickly to LineageOS for me and your there. Maybe it works for you too.
SpHEROs said:
Hi, I had almost the same situation as you, currently I'm running;
LOS17.1 Mi Mix 2 Chiron
TWRP 3.3.1
Firmware 9.6.27
Old ROM: Latest build LOS 16.0 from 25/03
Magisk 20.4 installed (no additional module or anything that I know of).
For me it also gets into a bootloop, EXCEPT when I boot through TWRP. So turn off your phone, reboot it by holding volume up (it turns on automatically for me for some reason), unlock the partition then go straight to reboot > reboot system. It then goes relatively quickly to LineageOS for me and your there. Maybe it works for you too.
Click to expand...
Click to collapse
Got it sorted with some help. Reset privacy guard permissions , reset apps permissions within LOS16. Flash LOS17.1 .
Upgrade successful.
andr6 said:
Got it sorted with some help. Reset privacy guard permissions , reset apps permissions within LOS16. Flash LOS17.1 .
Upgrade successful.
Click to expand...
Click to collapse
Interesting, I'll give that a try! Thanks.
After upgrade to lineage os 17.1 without wipe data, get stuck at boot animation. I have tried reboot to system in twrp, but it doesn't works.
I tried to downgrade to lineage os 16.0, and it booted to system again. Then I backup all my apps using Titanium Backup, upgrade to lineage os 17.1 with wipe data, it works well.
I have the exact same problem. I have to boot through TWRP every time I reboot my device.
What's going on here ? This is so weird...
SpHEROs said:
Hi, I had almost the same situation as you, currently I'm running;
LOS17.1 Mi Mix 2 Chiron
TWRP 3.3.1
Firmware 9.6.27
Old ROM: Latest build LOS 16.0 from 25/03
Magisk 20.4 installed (no additional module or anything that I know of).
For me it also gets into a bootloop, EXCEPT when I boot through TWRP. So turn off your phone, reboot it by holding volume up (it turns on automatically for me for some reason), unlock the partition then go straight to reboot > reboot system. It then goes relatively quickly to LineageOS for me and your there. Maybe it works for you too.
Click to expand...
Click to collapse
Can confirm I have to boot through OrangeFox recovery on a fresh LineageOS 17.1 installation.
andr6 said:
Got it sorted with some help. Reset privacy guard permissions , reset apps permissions within LOS16. Flash LOS17.1 .
Upgrade successful.
Click to expand...
Click to collapse
So I should flash back to los16.0 first,then reset privacy guard permissions and apps permissions, try flash los17.1 again?
seancheng said:
So I should flash back to los16.0 first,then reset privacy guard permissions and apps permissions, try flash los17.1 again?
Click to expand...
Click to collapse
I tried this and the only way to boot is through OrangeFox. I even tried to reset and reinstall all the apps after going back to LOS16 but it still only boots through recovery. Not sure if there's an issue with the builds, I'm on April 22nd build.
Krystlie said:
I tried this and the only way to boot is through OrangeFox. I even tried to reset and reinstall all the apps after going back to LOS16 but it still only boots through recovery. Not sure if there's an issue with the builds, I'm on April 22nd build.
Click to expand...
Click to collapse
After several times flash, I probably found the key. The following reasons will cause this bootloop:
1, Sync the setting from LOS16.0 though Google. The first boot after flash LOS17.1 and OpenGapps is normal, Once synchronized setting will bootloop, but contacts is ok.
2, Magisk. I tried all 20.X and 19.4 versions, I heard this is a known issue.
3, Restore permissions of applications backed up in LOS16.0. I don’t know if it ’s because Android 9 and 10 have different permissions.
LOS17.1 April 22nd
TWRP 3.3.1-1
Firmware v11.0.6.0 Global
Old ROM: Latest build LOS16.0
Magisk 20.4 installed (no additional module).
Fix:
1. Wipe Dalvik cache, cache and system
2. Install LOS 16
3. Install OpenGapps for Android 9.0
4. Reboot
5. Developer options: Enable root for adb
6. On computer: adb shell pm reset-permissions
7. On computer: adb root
8. On computer: adb shell pm reset-permissions
9. Reboot to TWRP
10. Wipe Dalvic cache, cache and system again
11. Flash LOS 17.1
12. Flash OpenGapps for Android 10
13. Reboot

(SOLVED) 5T with LineageOs 19.1 rooted with Magisk, unrooted after update

I've rooted my OP 5T with Lineage Os 19.1 with Magisk but, evrytime I install a nightly rom update, device results unrooted. Is there any way to root permanetly LineageOS? I tryed both metods, renaming magisks apk in zip file, sideloading with adb or patching boot.img with Magisk manager but in both cases I've the same problem.
I've found solution by myself. I had installed lineageos recovery, changed with TWRP and now root is mantained after rom nightly update.

Categories

Resources