[ROM][UNOFFICIAL][10.0][POTTER] LineageOS 17.1

siroccoxda

New member
Dec 23, 2014
2
2
0
I flashed this ROM (and stock GApps) to my G5 Plus but once I got finished with the initial setup, I was greeted with this as my home screen:

https://imgur.com/a/iXiMsqN

Can anyone clue me in as to what could be going wrong here?
 
Last edited:

siroccoxda

New member
Dec 23, 2014
2
2
0
I flashed this ROM (and stock GApps) to my G5 Plus but once I got finished with the initial setup, I was greeted with this as my home screen:

https://imgur.com/a/iXiMsqN

Can anyone clue me in as to what could be going wrong here?
Following up on my own issue; I wasn't aware that this was the consequence of that weird "Sample Leanback Launcher" default app launcher that this ROM comes with - I guess it's a launcher designed for smart televisions? My home screen looked so weird with that launcher I legitimately though something had gone wrong, like it was mis-detecting my screen resolution/DPI and rendering the "real" launcher improperly.

Per other advice in the thread (and having already rooted the install with Magisk) I was able to (though I do not remember how) get out of that launcher and actually access the Play Store, install Root Uninstaller, then locate, force-stop, and disable (some apps call it "freeze") the offending default launcher app, changing the default home screen/launcher app to the bundled Pixel Launcher.

Also, if anyone is curious, this proved to be a functional replacement for the default Camera app, which seemed to stop when starting pretty much 100% of the time:

https://f.celsoazevedo.com/file/gcamera/MGC_6.1.021_Potter_v7_san1ty.apk
 

time_nl

Member
Jun 28, 2006
17
3
33
64
Rijen
Following up on my own issue; I wasn't aware that this was the consequence of that weird "Sample Leanback Launcher" default app launcher that this ROM comes with - I guess it's a launcher designed for smart televisions? My home screen looked so weird with that launcher I legitimately though something had gone wrong, like it was mis-detecting my screen resolution/DPI and rendering the "real" launcher improperly.

Per other advice in the thread (and having already rooted the install with Magisk) I was able to (though I do not remember how) get out of that launcher and actually access the Play Store, install Root Uninstaller, then locate, force-stop, and disable (some apps call it "freeze") the offending default launcher app, changing the default home screen/launcher app to the bundled Pixel Launcher.

Also, if anyone is curious, this proved to be a functional replacement for the default Camera app, which seemed to stop when starting pretty much 100% of the time:

https://f.celsoazevedo.com/file/gcamera/MGC_6.1.021_Potter_v7_san1ty.apk

I too went back to recheck my own work. I reflashed the latest gothicVI ROM. Just switching to another launcher was indeed not successful. I used Titanium Backup to freeze the app instead of Root Uninstaller as you had done.

Now I was able to switch to ANY other launcher successfully and 3 button navigation worked properly for me.

I also download the camera APK you suggested and am quite satisfied with it.

Thanks to you and to gothicVI latest ROM I'm now a very happy camper!
 

bluntking

Member
Feb 19, 2020
15
1
3
Has anybody tried to install viper4android on this rom?
If that is successful I'll happily switch to this rom.
Please anyone test if it's working
I'm on android pie just because i can't find working viper on any rom
 

hotwert

Member
Feb 23, 2011
5
1
0
I can't do anything with that launcher. I can't even start a app or the settings. Only the terminal app on the desktop works, but it's without root. How can I remove it? Is der any script I could install from recovery mode?
Of course I have a backup of my old lineage os 16, but I better would like to use the newer version
 

time_nl

Member
Jun 28, 2006
17
3
33
64
Rijen
I can't do anything with that launcher. I can't even start a app or the settings. Only the terminal app on the desktop works, but it's without root. How can I remove it? Is der any script I could install from recovery mode?
Of course I have a backup of my old lineage os 16, but I better would like to use the newer version
Try to install Magisk to get root then use Titanium Backup or Root Uninstaller to freeze or uninstall the launcher as was already suggested in the thread.
 

Khazuo

New member
Jun 14, 2020
3
0
0
Moto g5 plus XT1680, I have problems only with the camera, it closes after taking a photo or when it enters it only closes, even so only that problem I have had, in my opinion it is stable, and I think it is a candidate to be an official, or I hope so.
Does anyone know if this problem still exists on the rom?
I have the same mobile model and I would like to change my current rom to this one, seeing the good recommendation it gives and because it is 64 bits.

(Note: I apologize if you do not understand my English, I am using a translator).
 

gravysteak

New member
Aug 3, 2019
1
1
0
Does anyone know if this problem still exists on the rom?
I have the same mobile model and I would like to change my current rom to this one, seeing the good recommendation it gives and because it is 64 bits.

(Note: I apologize if you do not understand my English, I am using a translator).
Camera all good here.
 
  • Like
Reactions: time_nl

stephone1

New member
Jun 20, 2020
3
0
0
No Signal / Service

Hey. I like this OS, thanks!

But unfortunately after installing TEST-lineage-17.1-20200607-UNOFFICIAL-potter_security-patch-date_2020-06-05.zip and various previous versions, I have no signal with both SIM in my MOTO G5 Plus. Can anybody help please? Both IMEI numbers are shown correctly.

I checked also various other custom Roms with Android 10 - no signal, same problem. But when I install Lineage OS 15.1 on that phone I have signal and the SIM is working. Why?

I used TWRP 3.3.1-0 to install. Why is this Lineage version called "TEST"?

OK, thanks in advance.

PS: I have had the same problem with the launcher, but after changing the launchers it based on the Tips in the previous Posts it worked!
 

TopazTestified

New member
Sep 21, 2019
1
1
0
Hey. I like this OS, thanks!

But unfortunately after installing TEST-lineage-17.1-20200607-UNOFFICIAL-potter_security-patch-date_2020-06-05.zip and various previous versions, I have no signal with both SIM in my MOTO G5 Plus. Can anybody help please? Both IMEI numbers are shown correctly.

I checked also various other custom Roms with Android 10 - no signal, same problem. But when I install Lineage OS 15.1 on that phone I have signal and the SIM is working. Why?

I used TWRP 3.3.1-0 to install. Why is this Lineage version called "TEST"?

OK, thanks in advance.

PS: I have had the same problem with the launcher, but after changing the launchers it based on the Tips in the previous Posts it worked!
Hey, I was having the same issue the first time I installed the ROM. The problem is actually widespread across all Moto G5 Plus users, and has to do with Persist and EFS partitions becoming inaccessible by the system due to changes made from previous ROM installs. I just figured out a fix, so I'm gonna list the exact steps I took. Some might be unnecessary, but I'll leave that up to your discretion.
  • Ensure that you have a backup of EFS and Persist from the stock firmware (when you first got the device). If you don't, backup your most recently working EFS and Persist, or use the earliest backups you have.
  • Wipe System, Data, Cache, Dalvik/ART Cache.
  • Install the latest [Nougat][Stock][Rom] TWRP Flashable Stock Build. Choose to erase the EFS in the installation wizard.
  • My EFS backup was from 7, so I restored it here.
  • Install the latest [Oreo][Stock][Rom] TWRP Flashable Stock Build. Choose to NOT erase the EFS in the installation wizard.
  • Install the latest LineageOS build from this thread. If you're using Gapps, install those too with API 10 and ARM64.
  • Install Magisk, or your root manager of choice.
  • Install your custom kernel if you're using one.
  • Try and boot, but it gets stuck on the boot screen, then realize you have no Persist partition, so you restore your Persist and boot again. My Persist was from my LineageOS 16 backup, but it seems to work fine here.
This is only exactly what I did on my device, and of course, using a Persist and EFS from different roms and installing them when I did could cause unforeseen issues. If you no longer have a persist or EFS, I've read it's possible to get those from fastboot installs of stock oreo or just flashing someone else's persist. I'm no expert on this, but I found this thread to be helpful in figuring out the "No Signal" issue. Good luck with fixing this issue.
 
  • Like
Reactions: stephone1

stephone1

New member
Jun 20, 2020
3
0
0
Hey, I was having the same issue the first time I installed the ROM. The problem is actually widespread across all Moto G5 Plus users, and has to do with Persist and EFS partitions becoming inaccessible by the system due to changes made from previous ROM installs. I just figured out a fix, so I'm gonna list the exact steps I took. Some might be unnecessary, but I'll leave that up to your discretion.
  • Ensure that you have a backup of EFS and Persist from the stock firmware (when you first got the device). If you don't, backup your most recently working EFS and Persist, or use the earliest backups you have.
  • Wipe System, Data, Cache, Dalvik/ART Cache.
  • Install the latest [Nougat][Stock][Rom] TWRP Flashable Stock Build. Choose to erase the EFS in the installation wizard.
  • My EFS backup was from 7, so I restored it here.
  • Install the latest [Oreo][Stock][Rom] TWRP Flashable Stock Build. Choose to NOT erase the EFS in the installation wizard.
  • Install the latest LineageOS build from this thread. If you're using Gapps, install those too with API 10 and ARM64.
  • Install Magisk, or your root manager of choice.
  • Install your custom kernel if you're using one.
  • Try and boot, but it gets stuck on the boot screen, then realize you have no Persist partition, so you restore your Persist and boot again. My Persist was from my LineageOS 16 backup, but it seems to work fine here.
This is only exactly what I did on my device, and of course, using a Persist and EFS from different roms and installing them when I did could cause unforeseen issues. If you no longer have a persist or EFS, I've read it's possible to get those from fastboot installs of stock oreo or just flashing someone else's persist. I'm no expert on this, but I found this thread to be helpful in figuring out the "No Signal" issue. Good luck with fixing this issue.
Wow, cool! Thanks. It worked. Perfect.

I also found out, that the Arrow OS works perfectly fine without the steps above. IMEI and SIM working fine - no work arounds neccessary.
 

uvahaole

Member
Sep 28, 2017
5
2
0
compass, ctsProfile, and disabling SampleLeanbackLauncher

This ROM is great, I am very happy with it. I only have two issues.

But first, I wish to note that you do not need a 3rd party app to disable the default SampleLeanbackLauncher that prevents functional launchers from running. Assuming you are rooted with Magisk, simply connect through ADB and run:

Code:
adb shell 
su
[I](grant su access on phone)[/I]
pm disable com.example.sampleleanbacklauncher
exit
exit
As for my two issues:
  1. The compass is not reported by Android. Note the physical compass is only in the US version of Potter (XT1687). Does anyone have ideas for getting the compass enabled?
  2. Does not pass SafetyNet Check; returns "false" for ctsProfile. I believe this is a common problem for Android 10 (Q). I tried Core Mode only in Magisk, disabling ADB, all the regular suggestions..., plus spoofing some other Potter fingerprints since the prefix of my fingerprint shows up as:
    google/coral/coral:10/QQ1B.200205.002/6084387:user/release-keys
    ... and I figured it should include potter instead. So using MagiskHide Props Config, I tried the tool's built-in 7.0 key plus:
    motorola/Moto G5 Plus/potter:10/QQ3A.200605.001/eng.sebast.20200607.090618:userdebug/test-keys (from this ROM's updater-script)
    8.1.0/OPS28.85-13/b8ea:user/release-keys (from stock)
    10/QQ3A.200605.001/5898e8a82a:userdebug/test-keys (from AncientOS; its thread claims SafetyNet is working)
    10/QQ3A.200605.001/e28685d066:userdebug/release-keys (from PixelExperiencePlus)​
    ... as well as adding "__2020-06-05" to each of them (for the latest security update).
 
Last edited:
  • Like
Reactions: 99913308

time_nl

Member
Jun 28, 2006
17
3
33
64
Rijen
Last edited: