You can, but there is no guarantee that the data restore will go as intended, I recommend backing up important apps separately using Seedvault or another app like Migrate.
[ROM][OFFICIAL][montana][11] LineageOS 18.1
- Thread starter JarlPenguin
- Start date
So my phone is currently encrypted (have to enter my pin at boot), what happens when i switch to lineage recovery then?
Nothing as in I cant access the partition or nothing as in the recovery doesn't handle the encryption at all and im fine?
Sorry for asking so much just trying not to make any mistakes
You can't access the partition in recovery mode. The upgrade process itself doesn't touch the /data partition aside from the first boot.
I don't recall the details, but I think it was when I first switched from 17.1 lineage with TWRP, to 18.1 with Lineage recovery, that the phone would restart to the PIN entry screen but would not accept my PIN. In the end after trying various workarounds found online, I had to wipe the phone and start from zero. I seem to recall others having a similar issue, maybe discussed earlier in this thread. So definitely back up as much as you can preferably manually to be sure (seedvault unfortunately excludes a lot for me at least), and I think somewhere I saw someone suggest removing the PIN and fingerprint lock before you do the upgrade, but then someone earlier in this chain seems to say they had the same issue even having done that.
That issue was fixed in a recent build, so it shouldn't happen anymore (at least according to the user who was affected, it was fixed)
You are mistaken then, Vi supports VoLte!! It works fine with other devices.
So I think some problem with rom's carrier configuration.
Btw you are advertising a bug as feature
Sorry about advertising a bug as a feature...You are mistaken then, Vi supports VoLte!! It works fine with other devices.
So I think some problem with rom's carrier configuration.
Btw you are advertising a bug as feature
It might be true that there's a problem with the roms carrier config, also, I didn't know that Vi supports VoLTE because I never saw 4G during calls on the roms I used, i.e,stock rom, pixel experience pie and now lineage os 18, I'll try and see if I can get VoLTE working on another device...
You are right, VoLTE is broken in this rom, I tried vi on another device, and VoLTE worked without problems, and also, jio calls don't work at all, when I tested jio I put it in the second slot and the call ended up going through vi, after testing with jio as the only son in slot 1, I can also confirm that VoLTE is broken in this rom, and as confirmation, the ims status in * # * # 4636 # * # * says that ims is unregistered and VoLTE along with other things is unavailable...You are mistaken then, Vi supports VoLte!! It works fine with other devices.
So I think some problem with rom's carrier configuration.
Btw you are advertising a bug as feature
@JarlPenguin please try figuring out what might be causing ims to be unregistered, also, the VoLTE option does appear in settings along with wifi calling and carrier video calling,but enabling them doesn't do anything...
I don't have the issue here, so it's an issue on your end. Your carrier might not support VoLTE on montana, or your EFS/persist could be partially messed up. At any rate I can't do anything about it.
Is there something that can be done to the efs or persist partition that would possibly fix this behaviour?
And also I tried different carriers and all of them were the same...
Edit: I never touched the efs partition myself, all I do for installing custom roms is to wipe the system, cache and data partition, so, I'm not quite sure what to do now, is there anything you could suggest that would possibly fix this issue...
Last edited:
I'd suggest going back to stock and seeing if it works there. If it does, backup the persist/EFS partition, reinstall LineageOS and restore the persist & EFS backup.
How do I go back to the stock rom?
There are no qfil based stock roms for this device...
Most of the stock roms for this device are flashed from fastboot...
so I just switched to lineage from stock and I'm very happy with the rom, very clean and fast. I had problems passing safetynet with magiskhide props so I'd like to recommend an alternative called PixelFeatureDrops its easier cause it requires no terminal and now my phone passes safetynet. and by the way, ota updates did not work.
You should flash it via fastboot, how else would you do it?
Please check post #111 regarding OTA updates.
First of all, awsome work. Thanks for all of this.
I see though unofficial this is a good place to "report" a bug or at least do a heads-up.
I have an XT1794 latest montana linage build from today.
If I plug analogic earphones I can't controll the volume during a network call.
Volume is controlable in any other circumstance (Bluetooth earphones, or IP calls on analog earphones).
Is there anything I can provide you to help tackle this?
I see though unofficial this is a good place to "report" a bug or at least do a heads-up.
I have an XT1794 latest montana linage build from today.
If I plug analogic earphones I can't controll the volume during a network call.
Volume is controlable in any other circumstance (Bluetooth earphones, or IP calls on analog earphones).
Is there anything I can provide you to help tackle this?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
magnet:?xt=urn:btih:8667049feb2a3e17627d86457c1c4069956055f6&xt=urn:btmh:12202bc096ee9de470efbed81d66911b5759b401bd082f1bd59a22d4c7347710fdd4&dn=montana&tr=udp%3A%2F%2Fexodus.desync.com%3A6969%2Fannounce
1
if you have windows then use this app
Download Rescue & Smart Assistant (PC Only)| Motorola Support US
Visit the customer support page to view user...en-us.support.motorola.com
if you have linux then there is this file "MONTANA...".zip on google drive link I sent up there,
to flash it you need to unzip, install "google-android-platform-tools-installer" or "android-tools"
and then flash it with this file on attachment
open folder where "flash.sh" file is with "open in terminal"
and type ./flash.sh then wait until it's done. -
6
Code:#include <std_disclaimer.h> /* * Your warranty is now void. * * We are not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at us for messing up your device, we will laugh at you. * */
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
Instructions:
- Download the latest build, recovery image and GApps (if you need them)
- Flash the downloaded recovery image via fastboot
- Boot to recovery
- Format system and perform a factory reset
- Reboot to recovery
- Flash the latest build
- Flash GApps and any other necessary add-ons
What's working:
- WiFi
- Camera and Camcorder
- Bluetooth
- NFC
- Fingerprint - Oreo firmware required
- GPS
- OTG
- Video Playback
- Audio
- RIL
- VoLTE
- USB tethering/audio
- SELinux: Enforcing
Known issues:
- VoWiFi
- You tell me
Downloads:
Reporting Bugs
- All bugs should be reported here: Issue Tracker
- DO NOT Report bugs if you're running a custom kernel or you installed Xposed
- Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
- If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
- If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Code:What is your-- LineageOS version: LineageOS Download url: Gapps version: 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:
Thanks to:
@GivFNZ for testing my builds
@wiktorek140, @karthick mostwanted, @wh0dat, @KalilDev, @AsD Monio, @GoldeneyeS2, @Steve Mathew Joy and @rajatgupta1998 for their hard work on our device sources
LineageOS team
Changelogs:
Source code:
53I've uploaded a build for LineageOS 18.1. Official status will be gained shortly after we've tested things on a wider variety of devices.3Hi, normally I post here only when there is a problem. This time I wanted to post just to say everything has been working very smoothly for weeks and I really appreciate all the work that goes into making that happen!3
New posts
-
[ROM][10/12] LineageOS OFFICIAL [SURYA]KARNA]
- Latest: wilsonhlacerda
-
-
