[ROM][OFFICIAL] LineageOS 17.1 [nightlies]

maciocho · Apr 6, 2020

No Magisk and Gapps

Hi All!

Thanks for the ROM!
I find it hard to flash (comparing to my previous experiences with lineage os on other devices) as it made me use blanklash twice

but I made it... somehow
I'm still not able to flash opengapps or magisk, no matter what path followed- instruction or previous experience and my question is:
Were you able to flash gapps or magisk?

P.S. Lineage OS web browser is not working for my device on any build (04, 05 and 06)

Thanks!

chincheta0815 · Apr 4, 2020 19 4 0

maciocho said:
I'm still not able to flash opengapps or magisk, no matter what path followed- instruction or previous experience and my question is:
Were you able to flash gapps or magisk?

Flashing Gapps works when you use "copy-partitions-AB.zip" instead of "copy-partition.zip".

maciocho · Apr 6, 2020

chincheta0815 said:
Flashing Gapps works when you use "copy-partitions-AB.zip" instead of "copy-partition.zip".

So, it did work but not for Gapps unfortunately.

gerchla · Apr 6, 2020

I got Magisk working, the way I did it was:
- starting with stock rom
- fastboot boot twrp
- sideload Lineageos
- reboot bootloader (!)
- fastboot boot twrp (!)
- sideload Magisk zip
- reboot system
- install MagiskManager apk

Note that rebooting twrp is important because Lineageos flashes to the inactive slot. If you immediately sideload Magisk after Lineageos, then Lineageos gets flashed to the currently inactive slot, while Magisk gets flashed to the currently active one. Active and inactive slots will switch after flashing Lineageos and rebooting. (At least that's my understanding).

------

different question: dual sim seems to not work properly; I can just use the first slot. anybody have similar experience? (ROM 2020-04-05)

Jleeblanch · Apr 6, 2020 at 11:35 PM

For now guys, just use TWRP to install, same as all the unofficial versions. You can use the info from my LineageOS 16.0 thread to install using TWRP. I've updated TWRP to work with Lineage 17.1 (meaning working decryption) which you can find links for in the OP of my TWRP thread.

I would also hold off on updating thru the Updater until that build gets released, as you may wreck your partition table (and btw, you don't need a blankflash to fix. Just flash gpt.bin and the bootloader.img using fastboot, then flash the full stock firmware to recover).

Apparently the 20200406 build was already in the pipeline to be built, so my gpt-utils changes didn't make it into that build, but will most definitely be in the 20200407+ builds and then the Wiki instructions will be fine to use again if you so choose.

I will update the 2nd post as as I can with proper TWRP installation info (an alternative method to install) as well as how to maintain TWRP and Magisk when updating via OTA's.

RoAM73 · Oct 19, 2018 8 3 0

USB tethering don't work

rom: lineage-17.1-20200406
logcat: https://paste.opensuse.org/5357026

chincheta0815 · Apr 4, 2020 19 4 0

Jleeblanch said:
Starting with the next nightly (20200406) you'll be able to OTA update without any issues. Just flash the next build that gets released in twrp and after that you'll be fine.

Okay I will do my very best (BTW: the changes you mentioning are not included in 20200406 as the "Recent Changes" on downloads.lineageos.org/lake shows). Nevertheless, I will flash a later build.
Another thing I found: Using copy-partitions.zip definitely was the cause for showing a blank screen when doing the first connect to a google account ising gapps. Using copy-partitions-AB.zip I was able to install gapps correctly.
Is that a behavior that will also be vanished or does that still exist?
And
Is it okay to use copy-partitions-AB-zip without having to do a total reflash from stock?

Jleeblanch · Apr 8, 2020 at 5:15 PM

chincheta0815 said:
Okay I will do my very best (BTW: the changes you mentioning are not included in 20200406 as the "Recent Changes" on downloads.lineageos.org/lake shows). Nevertheless, I will flash a later build.

Another thing I found: Using copy-partitions.zip definitely was the cause for showing a blank screen when doing the first connect to a google account ising gapps. Using copy-partitions-AB.zip I was able to install gapps correctly.

Is that a behavior that will also be vanished or does that still exist?

And

Is it okay to use copy-partitions-AB-zip without having to do a total reflash from stock?

Yea, the 20200406 build was already in the pipeline and those changes weren't included. The newly released 20200408 build has the new gpt-utils changes tho, so sideloading using Lineage Recovery (as well as OTA updates) should be fine from this point on.

As far as the copy-partitions-AB.zip vs copy-partitions.zip, I'm not sure. I don't have much control over that particular zip, and the only real difference is the partitions that are copied to the inactive slot. Realistically tho, you only need to use that zip the first time you install Lineage. Once you're up and running, you don't need to use it again. The whole point of that zips existence is because Moto doesn't populate slot "B" from the factory. They assume it'll be populated during your first OTA install (but many of us don't get that far before unlocking the bootloader and installing custom ROMs).

Zojak · Apr 9, 2020 at 7:29 AM

Jleeblanch said:
For now guys, just use TWRP to install, same as all the unofficial versions. You can use the info from my LineageOS 16.0 thread to install using TWRP. I've updated TWRP to work with Lineage 17.1 (meaning working decryption) which you can find links for in the OP of my TWRP thread.

I would also hold off on updating thru the Updater until that build gets released, as you may wreck your partition table (and btw, you don't need a blankflash to fix. Just flash gpt.bin and the bootloader.img using fastboot, then flash the full stock firmware to recover).

Apparently the 20200406 build was already in the pipeline to be built, so my gpt-utils changes didn't make it into that build, but will most definitely be in the 20200407+ builds and then the Wiki instructions will be fine to use again if you so choose.

I will update the 2nd post as as I can with proper TWRP installation info (an alternative method to install) as well as how to maintain TWRP and Magisk when updating via OTA's.

Thank you for the heads up about gpt.bin and bootloader.img. After spending the day switching from stock to lineageos 17.1. I broke it using the built in updater. Fastboot flashing those two files fixed it.

chincheta0815 · Apr 4, 2020 19 4 0

Jleeblanch said:
For now guys, just use TWRP to install, same as all the unofficial versions. You can use the info from my LineageOS 16.0 thread to install using TWRP. I've updated TWRP to work with Lineage 17.1 (meaning working decryption) which you can find links for in the OP of my TWRP thread.

I would also hold off on updating thru the Updater until that build gets released, as you may wreck your partition table (and btw, you don't need a blankflash to fix. Just flash gpt.bin and the bootloader.img using fastboot, then flash the full stock firmware to recover).

Apparently the 20200406 build was already in the pipeline to be built, so my gpt-utils changes didn't make it into that build, but will most definitely be in the 20200407+ builds and then the Wiki instructions will be fine to use again if you so choose.

I will update the 2nd post as as I can with proper TWRP installation info (an alternative method to install) as well as how to maintain TWRP and Magisk when updating via OTA's.

Thanks a lot for your efforts.
So there was not chance to update from 20200408 to 20200409. It chrashed partitions I think. Installing Gapps with the 20200409 build did not work - even using just copy-partitions-AB.zip.

jmozmoz · Apr 9, 2020

Update:
With TWRP working, I did a reformating of data, wiping of cache, system and the flashed LineageOS 16.0 (20200201).

_____________________________________________________________________________________________________

Update:
Using the stock rom from this thread: https://forum.xda-developers.com/g7-plus/development/flash-rom-bat-flash-stock-rom-moto-g7-t3910423
extracting gpt.bin and issuing the following command:

Code:

fastboot getvar max-sparse-size
fastboot flash partition gpt.bin

I am able to start TWRP again.

Is there another source for this gpt.bin file?

But LineageOS does not startup correctly. It reboots into recovery with this message:
"Can't load Android system. Your data ma"

It offers to do a "Factory data reset"

_____________________________________________________________________________________________________

After doing a OTA update from 20200408 to 20200409, my phone does not boot anymore. It is stuck in fastboot:

The bootloader logs says:

Code:

"Your device didn't start up successfully.
If this is a Verzion device ...

If this is not a Verizon device or Software Repair Assistent did not help for any reason, plase contact customer care center for further assistant.

AP Fastboot Flash Mode (Secure)"

If I try to start TWRP, I get the following output:

Code:

fastboot boot twrp-3.3.1-lake-Q-v1.img
        downloading 'boot.img'... OKAY [  1.172s]
                       booting... INFOFailed to load/authenticate boot image: 00000050
FAILED (remote failure)
 finished. total time: 1.203s

jadephyre · Apr 9, 2020 at 5:28 PM

A detailed instruction how to install would not go amiss

Since there are a lot of people having problems installing the ROM, i'm holding out on it as well.

jmozmoz · Apr 9, 2020 at 5:53 PM

Just more information about my experiance using this ROM:

I had big problems with accessing the file systems. Different apps were not working correctly. E. g. I could not download images in WhatsApp.

Also other apps did not start correctly, e. g. K9-Mail. It actually worked somehow, because I could access my accounts using different of its widgets, but not simply by starting the app.

maciocho · Apr 9, 2020

With some experimenting I managed to flash the 09 build with 08 pico gapps but no luck with installing magisk over this set as it always breaks the system and the device keeps on rebooting to bootloader.
Apart from not having magisk I must say it works great.

Zojak · Apr 9, 2020 at 10:18 PM

@Jleeblanch The Network traffic monitor in Settings > System > Status Bar is too close to the camera notch.

maciocho · Apr 10, 2020

Hi all!

I finally made it with the install.

Don't know if this is fine to share here but here's the guide that helped me:
https://forum.xda-developers.com/pixel-xl/how-to/slota-b-how-to-flash-roms-magisk-kernel-t3754175

With everything running as expected, my next question is, how do I safely flash an update?

RoAM73 · Oct 19, 2018 8 3 0

maciocho said:
Hi all!

I finally made it with the install.

Don't know if this is fine to share here but here's the guide that helped me:
https://forum.xda-developers.com/pixel-xl/how-to/slota-b-how-to-flash-roms-magisk-kernel-t3754175

With everything running as expected, my next question is, how do I safely flash an update?

this can be done through dirty flash update package from twrp

maciocho · Apr 10, 2020 at 8:42 PM

RoAM73 said:
this can be done through dirty flash update package from twrp

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.

KelleyCook · Apr 10, 2020 at 9:01 PM

Jleeblanch said:
ROM Firmware Required: Android 10 (Q) Stock Firmware

Where might I find this Q firmware?

My REVVLRY+ was on Pie before I moved to Lineage 16.

KC

digitaljeff · Apr 11, 2020 at 2:23 AM

KelleyCook said:
Where might I find this Q firmware?

My REVVLRY+ was on Pie before I moved to Lineage 16.

KC

lolinet

[ROM][OFFICIAL] LineageOS 17.1 [nightlies]

Senior Member

Member

Senior Member

Member

Senior Member

Member

Member

Senior Member

Senior Member

Member

Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member