[ROM][OFFICIAL] LineageOS 17.1 [nightlies]

[RoAM73]

OK, but do I flash it from slot b, as this will be the default one when booted to recovery? From my experience switching slots breaks the install.

Indeed, the slots, when flashing system updates from twrp, switch. However, this method works great for me. The sequence of my actions:
1. Download system update.
2. Reboot to recovery (twrp).
3. Flash system update.
4. Flash twrp-installer.
5. Reboot to system.
6. Reboot to recovery (twrp).
7. Flash magisk.
8. Reboot to system.
9. All done, profit for me
P.S. I’m not using google services.

 

[onnoêzeler]

Can anyone help me, I think I might have soft bricked my device.
After trying out this rom and not being able to get Google Services working I wanted to go back to Android 9.
I currently have no OS installed and TWRP 3.1.1 but the touch stopped working in recovery for some reason.
Any attempts to flash or boot a new recovery via ADB have proven fruitless.
Trying to fix my phone using the Lenovo Moto Smart Assistant has also failed, it can't seem to find my device despite it showing up in fastboot devices.

I first flashed copy-partitions.zip and later copy-partitions-AB.zip after wiping so maybe I messed up the partitioning?

Any help would be greatly appreciated, thank you

 

[jmozmoz]

Is this the same behavior as described in https://forum.xda-developers.com/showpost.php?p=82230537&postcount=31 ?

Can anyone help me, I think I might have soft bricked my device.
After trying out this rom and not being able to get Google Services working I wanted to go back to Android 9.
I currently have no OS installed and TWRP 3.1.1 but the touch stopped working in recovery for some reason.
Any attempts to flash or boot a new recovery via ADB have proven fruitless.
Trying to fix my phone using the Lenovo Moto Smart Assistant has also failed, it can't seem to find my device despite it showing up in fastboot devices.

I first flashed copy-partitions.zip and later copy-partitions-AB.zip after wiping so maybe I messed up the partitioning?

Any help would be greatly appreciated, thank you

 

[dr.haggis]

Hi Guys,

I have problem with the reboot after installing the offical Lineage 17.1 Update from the Settings Menu in the Phone.
The follwing error shows up:

Your device didn't start ip successfully
(...)
AP Fastboot Flash Mode (Secure)
Failed to boot Linux, falling back to fastvoot.
Fastboot Reason: Fall-through from normal boot mode

What I did to get in this situation:
1. OEM Unlocked the Phone
2. installed official Lineage Recovery lineage-17.1-20200411-recovery-lake over fastboot
3. booted into Recovery and flashed opy-partitionsAB.zip (I found it in some other thread here) via ADB Sideload
3. installed lineage-17.1-20200411-nightly-lake-signed.zip as OS via ADB Sideload
4. Added Gapps open_gapps-arm64-10.0-pico-20200412.zip via ADB Sideload
5. Booted and installed some apps from the Play Store and moved some data
6. Installed the lineage-17.1-20200412-nightly-lake Update with the official Android Updater in LineageOS in the Settings Menu
and after the next reboot: voila - the error above showed up instantly after the Moto Boot Wallpaper.
Even when I want to change to recovery, I get the same fastboot message.

Has anyone of you an idea to solve the boot failure?
Or should I flash the OEM Android with the Lenovo Smart Assitant Tool / flashfile.bat and having the risk to lose some data I just added today?

I tried to re-flash the Recovery, but got the following error in Fastboot:
fastboot flash recovery lineage-17.1-20200411-recovery-lake.img
target max-sparse-size: 256MB
sending 'recovery' (24429 KB)...
OKAY [ 0.657s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.687s


Thanks a lot for your help,
Andreas

 

[jmozmoz]

What shows up, if you use the volume keys in fastboot to show the cause of the boot failure? This sounds exactly like the error I reported above: https://forum.xda-developers.com/showpost.php?p=82230537&postcount=31

I "solved" it be flashing the gpt.bin file. But I have not checked, if I can access my old data partition before reformating it and install LineageOS 16.0.

Hi Guys,

I have problem with the reboot after installing the offical Lineage 17.1 Update from the Settings Menu in the Phone.
The follwing error shows up:

Your device didn't start ip successfully
(...)
AP Fastboot Flash Mode (Secure)
Failed to boot Linux, falling back to fastvoot.
Fastboot Reason: Fall-through from normal boot mode

What I did to get in this situation:
1. OEM Unlocked the Phone
2. installed official Lineage Recovery lineage-17.1-20200411-recovery-lake over fastboot
3. booted into Recovery and flashed opy-partitionsAB.zip (I found it in some other thread here) via ADB Sideload
3. installed lineage-17.1-20200411-nightly-lake-signed.zip as OS via ADB Sideload
4. Added Gapps open_gapps-arm64-10.0-pico-20200412.zip via ADB Sideload
5. Booted and installed some apps from the Play Store and moved some data
6. Installed the lineage-17.1-20200412-nightly-lake Update with the official Android Updater in LineageOS in the Settings Menu
and after the next reboot: voila - the error above showed up instantly after the Moto Boot Wallpaper.
Even when I want to change to recovery, I get the same fastboot message.

Has anyone of you an idea to solve the boot failure?
Or should I flash the OEM Android with the Lenovo Smart Assitant Tool / flashfile.bat and having the risk to lose some data I just added today?

I tried to re-flash the Recovery, but got the following error in Fastboot:
fastboot flash recovery lineage-17.1-20200411-recovery-lake.img
target max-sparse-size: 256MB
sending 'recovery' (24429 KB)...
OKAY [ 0.657s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.687s


Thanks a lot for your help,
Andreas

 

[nightmw]

HI, am I missing anything or does this rom not have a full/working WebView (Trichrome, ...) configuration? Apps like K9-Mail, Fasthub-Libre and others which depend on "System WebView" just crash. Under "developer options" I cannot choose anything as a "webview implementation".
Is there anything I forgot? (I do not have gapps installed)

 

[dr.haggis]

Holy s#it,
thanks Man!
I flashed as you described (gpt.bin from OEM XT1965-3_LAKE_RETEU_10_QPWS30.61-21-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) and LineageOS booted from Recovery like a charm again.
Everything look like its working as before.

What shows up, if you use the volume keys in fastboot to show the cause of the boot failure? This sounds exactly like the error I reported above: https://forum.xda-developers.com/showpost.php?p=82230537&postcount=31

I "solved" it be flashing the gpt.bin file. But I have not checked, if I can access my old data partition before reformating it and install LineageOS 16.0.

 

[jmozmoz]

HI, am I missing anything or does this rom not have a full/working WebView (Trichrome, ...) configuration? Apps like K9-Mail, Fasthub-Libre and others which depend on "System WebView" just crash. Under "developer options" I cannot choose anything as a "webview implementation".
Is there anything I forgot? (I do not have gapps installed)

I had the same problems as you with K9-Mail with this ROM.

 

[nightmw]

I had the same problems as you with K9-Mail with this ROM.

were you able to solve it?

 

[jmozmoz]

were you able to solve it?

I found a workaround: You can access your account(s) using widgets. E.g. if you use the unread messages widget, it opens it inbox. From there you can navigate up to the folder list.

But after doing an OTA update, I nearly bricked my phone so I am no back to LineageOS 16.0.

 

[onnoêzeler]

Is this the same behavior as described in https://forum.xda-developers.com/showpost.php?p=82230537&postcount=31 ?

When trying to flash or boot anything via fastboot it just gets stuck at sending.

 

[xdafriek]

Can´t somebody tell if you can invert the navigation button´s?

 

[brunopetit17]

When trying to flash or boot anything via fastboot it just gets stuck at sending.

I had the same issue and I solved it by changing cable and usb port on my computer. It worked when I used a better cable and a more reliable usb port.

---------- Post added at 12:42 PM ---------- Previous post was at 12:28 PM ----------

Hi

First thanks for putting out this ROM. I am a newbie in the world of root and custom ROMs but I successfully unlocked my bootloader, boot and flash TWRP, installed lineage OS, GAPPS, and Magisk. It took me a lot of trials and errors but I did end up having a rooted lineage OS that worked fine... until I upgraded to the latest update (the 12th one) from the settings menu and the phone got soft-bricked.
Frankly I am a bit surprised that the update firmware option is available without any warning when it seems to be breaking phones from my experience and from what I read from others...
Anyway my phone got stucked in a bootloop, it would not even boot into recovery (the lineage one), it would not temporarily boot any recovery from fastboot boot command. So following what other did in this thread I used the .bat executive along with fastboot and the stock ROM to return my device to a kinda functional state. Then I was able to flash again any recovery and/or ROM but a much bigger problem happened: whatever the ROM installed (stock or lineage) it cannot anymore connect to cellular network nor wi-fi... Those functionalities just seems to be totally broken. I've tried factory reset, all sorts of wipes, installing different ROMs, everything works fine except for those super essential functionalities... I also tried to restore my first full backup but twrp keeps on telling me something is corrupt with it so it cannot restore.
Anyone has an idea why that happened and how I could fix it?

 

[Jleeblanch]

I had the same issue and I solved it by changing cable and usb port on my computer. It worked when I used a better cable and a more reliable usb port.

---------- Post added at 12:42 PM ---------- Previous post was at 12:28 PM ----------

Hi



First thanks for putting out this ROM. I am a newbie in the world of root and custom ROMs but I successfully unlocked my bootloader, boot and flash TWRP, installed lineage OS, GAPPS, and Magisk. It took me a lot of trials and errors but I did end up having a rooted lineage OS that worked fine... until I upgraded to the latest update (the 12th one) from the settings menu and the phone got soft-bricked.

Frankly I am a bit surprised that the update firmware option is available without any warning when it seems to be breaking phones from my experience and from what I read from others...

Anyway my phone got stucked in a bootloop, it would not even boot into recovery (the lineage one), it would not temporarily boot any recovery from fastboot boot command. So following what other did in this thread I used the .bat executive along with fastboot and the stock ROM to return my device to a kinda functional state. Then I was able to flash again any recovery and/or ROM but a much bigger problem happened: whatever the ROM installed (stock or lineage) it cannot anymore connect to cellular network nor wi-fi... Those functionalities just seems to be totally broken. I've tried factory reset, all sorts of wipes, installing different ROMs, everything works fine except for those super essential functionalities... I also tried to restore my first full backup but twrp keeps on telling me something is corrupt with it so it cannot restore.

Anyone has an idea why that happened and how I could fix it?

It's been discussed in previous posts, but initially sideloading LOS using Lineage recovery was wrecking the gpt table (causing the exact issue your reported). I was able to fix that by updating gpt-utils (was missing dtbo partition), TWRP didn't have this issue as it accounted for the dtbo partition whereas Lineage recovery wasn't.

So that was fixed on the 20200408 build.

What I didn't realize at the time, is that wasn't the whole issue for taking OTA's, which were causing the same issue (wrecking the gpt table).

I scratched my head over that for a couple days, until I realized it was actually an SELinux issue. Our file_contexts wasn't accounting for the fact that Lake actually has one more partition than the other sdm660 devices we share the tree with, so some of the partitions in the higher mmcblk0p* values weren't being flashed correctly (if at all), thus causing your issue as described above.

FWIW, flashing the builds same as you do for Lineage 16.0 using TWRP would not have had any issues. You can download the full update and dirty flash in twrp same as you guys do on Lineage 16.0.

Anyway, starting with 20200413 (which is currently in the pipeline to be built) it will have the SELinux changes needed for properly working OTA's. I've thoroughly tested OTA's/Seamless updates using the Updater app, so they should work for real this time.

 

[chincheta0815]

Anyway, starting with 20200413 (which is currently in the pipeline to be built) it will have the SELinux changes needed for properly working OTA's. I've thoroughly tested OTA's/Seamless updates using the Updater app, so they should work for real this time.

Thanks a lot for all your efforts. I am really keen to install it.
But before I just flash right now (I got a little coward...), I checked the changelog and there is no "lake SELinux" commit in the list. Could you just re-check that the relevant commit is in?

 

[onnoêzeler]

I had the same issue and I solved it by changing cable and usb port on my computer. It worked when I used a better cable and a more reliable usb port.

No luck unfortunately when trying I first get an error like:
(bootloader) is-logicalartit: not found
or
(bootloader) max-downlo: not found

before it gets stuck at sending.

 

[Jleeblanch]

Thanks a lot for all your efforts. I am really keen to install it.

But before I just flash right now (I got a little coward...), I checked the changelog and there is no "lake SELinux" commit in the list. Could you just re-check that the relevant commit is in?

The 20200413 build isn't finished yet, looks like it's still in the works, but when it's ready the commit I'm referring to should be there.

Also, for clarification purposes, most of the SELinux stuff is in the sdm660-common tree, only a couple very specific device policies are in Lake's device tree.

Commit: sdm660-common: update eMMC block nodes sepolicy

 

[brunopetit17]

It's been discussed in previous posts, but initially sideloading LOS using Lineage recovery was wrecking the gpt table (causing the exact issue your reported). I was able to fix that by updating gpt-utils (was missing dtbo partition), TWRP didn't have this issue as it accounted for the dtbo partition whereas Lineage recovery wasn't.

So that was fixed on the 20200408 build.

What I didn't realize at the time, is that wasn't the whole issue for taking OTA's, which were causing the same issue (wrecking the gpt table).

I scratched my head over that for a couple days, until I realized it was actually an SELinux issue. Our file_contexts wasn't accounting for the fact that Lake actually has one more partition than the other sdm660 devices we share the tree with, so some of the partitions in the higher mmcblk0p* values weren't being flashed correctly (if at all), thus causing your issue as described above.

FWIW, flashing the builds same as you do for Lineage 16.0 using TWRP would not have had any issues. You can download the full update and dirty flash in twrp same as you guys do on Lineage 16.0.

Anyway, starting with 20200413 (which is currently in the pipeline to be built) it will have the SELinux changes needed for properly working OTA's. I've thoroughly tested OTA's/Seamless updates using the Updater app, so they should work for real this time.

Thanks for your explanation and for your hard work.
I did everything as was described in the lineage 16 post, flashed the latest version of lineage OS 17, but my device still cannot connect to any wifi or recognize the sim card. It's like those parts of the phone just shut downed.
Is there any way to solve that? Looking at what has been discussed in this post I do not find an answer. Or maybe it's so complicated I don't understand the answer that is already there.

 

[gerchla]

Thanks for your explanation and for your hard work.
I did everything as was described in the lineage 16 post, flashed the latest version of lineage OS 17, but my device still cannot connect to any wifi or recognize the sim card. It's like those parts of the phone just shut downed.
Is there any way to solve that? Looking at what has been discussed in this post I do not find an answer. Or maybe it's so complicated I don't understand the answer that is already there.

What always worked for me is to go fully back to stock ROM using the Lenovo Moto Smart Assistant (LMSA) tool and start all over.
You should at least be able to download the stock ROM ("resue"). If flashing with the tools doesn't work, do it manually

# (this folder is part of the downloaded, unzipped ROM)
cd RomFiles/LAKE_RETEU_QPWS30.61_21_3_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml  

fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear

fastboot reboot

 

[gerchla]

Fakeedit: I cannot access the sim card in 2nd slot either. (on this ROM)