Develop Bugs

Think I screwed up my installation of LineageOS 15.1 on my Mi Mix 2. How to fix it?

Alright, so just to put it out there, I was way too eager with this. I'm coming over from an iPhone 5 to my very first Android phone, and I chose the Mi Mix 2 because the price to feature ratio was fantastic. I didn't fully understand the procedures, and I'm here to learn and get help from all you smart people.
The Issues: Installed LineageOS 15.1, then screwed up when installing GApps, didn't get Play Store. So I restored to a TWRP backup I made during the process, reflashed everything, but now I have too many GApps and only 48GB available, compared to MIUI's 55GB.
The Details: Installed LineageOS 15.1, GApps via the "Aroma" installer, and Magisk 16.0. Somehow I didn't install the Google Play Store, so I tried to reinstall everything by restoring to the TWRP backup I made as recommended by the official LineageOS install guide. From there, I re-flashed LineageOS, GApps "Stock", and Magisk 16.0. Had some trouble booting into LOS, but eventually did, only to realize I didn't want that many GApps. And, the available memory is only 48GB compared to MIUI's 55GB. I'm not sure if that's just LOS and GApps, or if I screwed something up with my meddling. Current assumption is the latter.
The Questions: I want to reinstall everything the cleanest way possible. Fresh LineageOS, fresh GApps, and no Magisk. My goal is to have Google Play Store, Google Drive, Gmail, YouTube, and that's about it from GApps. How do I fix what I've screwed up? And, furthermore, in case I don't like LineageOS, how can I go from LineageOS to Xiaomi.eu? Is it as simple as following the install guide for Xiaomi.eu?
Thank you for taking the time to help me. I do feel pretty dumb for not understanding the process more before starting, but hindsight is 20/20. I've learned my lesson for sure, and I'm excited to learn the correct process for doing all of this.

stupidcanuck said:
Alright, so just to put it out there, I was way too eager with this. I'm coming over from an iPhone 5 to my very first Android phone, and I chose the Mi Mix 2 because the price to feature ratio was fantastic. I didn't fully understand the procedures, and I'm here to learn and get help from all you smart people.
The Issues: Installed LineageOS 15.1, then screwed up when installing GApps, didn't get Play Store. So I restored to a TWRP backup I made during the process, reflashed everything, but now I have too many GApps and only 48GB available, compared to MIUI's 55GB.
The Details: Installed LineageOS 15.1, GApps via the "Aroma" installer, and Magisk 16.0. Somehow I didn't install the Google Play Store, so I tried to reinstall everything by restoring to the TWRP backup I made as recommended by the official LineageOS install guide. From there, I re-flashed LineageOS, GApps "Stock", and Magisk 16.0. Had some trouble booting into LOS, but eventually did, only to realize I didn't want that many GApps. And, the available memory is only 48GB compared to MIUI's 55GB. I'm not sure if that's just LOS and GApps, or if I screwed something up with my meddling. Current assumption is the latter.
The Questions: I want to reinstall everything the cleanest way possible. Fresh LineageOS, fresh GApps, and no Magisk. My goal is to have Google Play Store, Google Drive, Gmail, YouTube, and that's about it from GApps. How do I fix what I've screwed up? And, furthermore, in case I don't like LineageOS, how can I go from LineageOS to Xiaomi.eu? Is it as simple as following the install guide for Xiaomi.eu?
Thank you for taking the time to help me. I do feel pretty dumb for not understanding the process more before starting, but hindsight is 20/20. I've learned my lesson for sure, and I'm excited to learn the correct process for doing all of this.
Click to expand...
Click to collapse
Hey!
For a clean reinstall boot into TWRP, wipe system, data, cache and dalvik cache.
Then flash lineageos, the PICO gapps from https://opengapps.org and magisk. Those are the barebones google framework and include just enough for the play store and the play store itself. If you need any other google apps just download them from the play store.
I always use the pico package, because it works best on every ROM, some ROM devs even recommend it.
And if you wanna go back to MIUI, I strongly recommend you to use the official Global. Xiaomi.EU is in my opinion the worst MIUI experience.
Welcome to Android btw!

rr111 said:
Hey!
For a clean reinstall boot into TWRP, wipe system, data, cache and dalvik cache.
Then flash lineageos, the PICO gapps from https://opengapps.org and magisk. Those are the barebones google framework and include just enough for the play store and the play store itself. If you need any other google apps just download them from the play store.
I always use the pico package, because it works best on every ROM, some ROM devs even recommend it.
And if you wanna go back to MIUI, I strongly recommend you to use the official Global. Xiaomi.EU is in my opinion the worst MIUI experience.
Welcome to Android btw!
Click to expand...
Click to collapse
Why do you don't like MIUI.EU? I used it for a while before switching to LOS and I found it to be more smooth than Global

Jackie CDP said:
Why do you don't like MIUI.EU? I used it for a while before switching to LOS and I found it to be more smooth than Global
Click to expand...
Click to collapse
It's just so badly executed for example the 5 seconds you have to everytime you want to open the updater to simpy to boot into the recovery. They fix bigs from MIUI, but not the ones that they slam into their builds. On my last phone, which was a china exclusive, I had to use the EU ROM if I wanted to use MIUI, but my experience was so bad that it forced me to go back to lineage. Then when I gave it another shot with their MIUI 10 ROM, they hadn't fixed a single of their bugs, so I just went back to Global. And global is very smooth for me. Plus: the EU devs and moderators are just rude.

Android Auto - Something went wrong. Google play services doesn't seem to be working

I have had a problem loading Android Auto (AA) on my LG G4. I have rooted with Steadfaster's UsU and installed his Lineage 15.1 rom, opengapps nano (Sept 30) and the phone is working great. Prior to rooting the phone AA worked fine with MM 6.0. After rooting the phone, when I open the AA app on the phone I get the error "Something went wrong. Google play services doesn't seem to be working right now". The error comes up immediately and then the app closes. I tried plugged into in the car as well (Pioneer AVIC 4200 deck), but the error stops the phone when opened.
I have been through Google's forums and there have been lots of posts about this error and no real solutions for me posted. I have also tried other "fixes" I have come across, including this one - https://forum.xda-developers.com/android/help/delete-disable-downgrade-prevent-update-t3091832/. This method involves:
1. Download and install System App Remover from the Google Play Store.
2. Put your device in Airplane Mode in order to prevent auto upgrade of GPS.
3. Open System App Remover and select "System App" from the menu.
4. Find Google Play Services in the list. It should be marked "Should keep", which is a suggestion from the publisher. Select it and press "Uninstall". Ignore completion message.
5. Using Settings/Apps, verify that Google Play Services has reverted to the factory-supplied version. It should be <7. "Force Stop", "Uninstall Updates", and "Disable" buttons should no longer be grayed out.
7. Reboot device and toggle Airplane Mode off.
I followed these steps, but unfortunately stock seems to be the version that came with opengapps which is current.
I'm out of ideas with this problem and need some help. AA is a great app for me and really handy on long trips. I would like to get it running if at all possible.
Appreciate any help you can provide.

jjcdennis said:
I have had a problem loading Android Auto (AA) on my LG G4. I have rooted with Steadfaster's UsU and installed his Lineage 15.1 rom, opengapps nano (Sept 30) and the phone is working great. Prior to rooting the phone AA worked fine with MM 6.0. After rooting the phone, when I open the AA app on the phone I get the error "Something went wrong. Google play services doesn't seem to be working right now". The error comes up immediately and then the app closes. I tried plugged into in the car as well (Pioneer AVIC 4200 deck), but the error stops the phone when opened.
I have been through Google's forums and there have been lots of posts about this error and no real solutions for me posted. I have also tried other "fixes" I have come across, including this one - https://forum.xda-developers.com/android/help/delete-disable-downgrade-prevent-update-t3091832/. This method involves:
1. Download and install System App Remover from the Google Play Store.
2. Put your device in Airplane Mode in order to prevent auto upgrade of GPS.
3. Open System App Remover and select "System App" from the menu.
4. Find Google Play Services in the list. It should be marked "Should keep", which is a suggestion from the publisher. Select it and press "Uninstall". Ignore completion message.
5. Using Settings/Apps, verify that Google Play Services has reverted to the factory-supplied version. It should be <7. "Force Stop", "Uninstall Updates", and "Disable" buttons should no longer be grayed out.
7. Reboot device and toggle Airplane Mode off.
I followed these steps, but unfortunately stock seems to be the version that came with opengapps which is current.
I'm out of ideas with this problem and need some help. AA is a great app for me and really handy on long trips. I would like to get it running if at all possible.
Appreciate any help you can provide.
Click to expand...
Click to collapse
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
After rooting with UsU I followed sdembiske's recommendations for installing Lineage. This included a factory reset and formatting data with TWRP. I then installed Lineage 15.1 UsU and opengapps nano and then installed the apps I wanted. AA went on clean without restoring data. I will capture a logcat and post.
Thanks
Click to expand...
Click to collapse

steadfasterX said:
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
After rooting with UsU I followed sdembiske's recommendations for installing Lineage. This included a factory reset and formatting data with TWRP. I then installed Lineage 15.1 UsU and opengapps nano and then installed the apps I wanted. AA went on clean without restoring data. It never opened without the error I titled this thread with.
My first attempt at a logcat. I searched in Notepad++ and used carservice as the keyword. Some errors were shown. I don't know how to interpret them and would appreciate your help
Thanks
Click to expand...
Click to collapse

jjcdennis said:
steadfasterX said:
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
After rooting with UsU I followed sdembiske's recommendations for installing Lineage. This included a factory reset and formatting data with TWRP. I then installed Lineage 15.1 UsU and opengapps nano and then installed the apps I wanted. AA went on clean without restoring data. It never opened without the error I titled this thread with.
My first attempt at a logcat. I searched in Notepad++ and used carservice as the keyword. Some errors were shown. I don't know how to interpret them and would appreciate your help
Thanks
Click to expand...
Click to collapse
I just searched a bit regarding the errors of your logcat and found this:
https://productforums.google.com/forum/#!topic/nexus/-N8jJo7A8nI
maybe something there helps you out.
It seems definitively an issue with google play app/updates..
btw: I have just installed AA here without an issue, running LOS 15.1 on my h815..
.
Click to expand...
Click to collapse

steadfasterX said:
jjcdennis said:
I just searched a bit regarding the errors of your logcat and found this:
https://productforums.google.com/forum/#!topic/nexus/-N8jJo7A8nI
maybe something there helps you out.
It seems definitively an issue with google play app/updates..
btw: I have just installed AA here without an issue, running LOS 15.1 on my h815..
.
Click to expand...
Click to collapse
I have been through that forum and tried the last post just now - uninstall updates, clear cache, open AA - and I immediately get the error.
I'm thinking about doing a Titanium backup on apps and data (minus AA) then wipe, reinstall LOS 15.2, TWRP, Lineage SU, do a reboot, reinstall AA first and if it works then run Titanium restore for apps and data.
Make sense?
Click to expand...
Click to collapse

jjcdennis said:
steadfasterX said:
I have been through that forum and tried the last post just now - uninstall updates, clear cache, open AA - and I immediately get the error.
I'm thinking about doing a Titanium backup on apps and data (minus AA) then wipe, reinstall LOS 15.2, TWRP, Lineage SU, do a reboot, reinstall AA first and if it works then run Titanium restore for apps and data.
Make sense?
Click to expand...
Click to collapse
Sounds like a plan
Nevertheless I would to a titanium backup of play and AA BEFORE restoring as well..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse

steadfasterX said:
jjcdennis said:
Sounds like a plan
Nevertheless I would to a titanium backup of play and AA BEFORE restoring as well..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Well I wiped cache, Dalvik, system and then formatted data, installed the 15.1 UsU rom, then installed Gapps, rebooted to recovery and installed the Lineage addonsu. I rebooted, went through setup and the first thing I did was open the Playstore install Android Auto and run it - immediate error again. Also the addonsu did not root the phone. And to top it all I did not disable the pin code.
Back to the drawing board.
Click to expand...
Click to collapse

steadfasterX said:
jjcdennis said:
btw: I have just installed AA here without an issue, running LOS 15.1 on my h815..
.
Click to expand...
Click to collapse
I have been beating the bushes and looking for a solution. None so far. You mention AA worked on your phone. Are you running LOS 15.1 and if no, which rom? Also re your install can you look in apps and notifications and see if the more options * is shown on the AA app. I have it, but when I select it nothing happens. My old Nexus 5 the * works and Android Auto opens no problem. LOS 7.1.2.
Thanks
Click to expand...
Click to collapse

jjcdennis said:
steadfasterX said:
I have been beating the bushes and looking for a solution. None so far. You mention AA worked on your phone. Are you running LOS 15.1 and if no, which rom? Also re your install can you look in apps and notifications and see if the more options * is shown on the AA app. I have it, but when I select it nothing happens. My old Nexus 5 the * works and Android Auto opens no problem. LOS 7.1.2.
Thanks
Click to expand...
Click to collapse
I run LOS 15.1 build 20181002 and at the time of installing that ROM version I used this opengapps version: open_gapps-arm64-8.1-nano-20180705.zip (download)
AA works here yes. I run it now for several days, daily, no issues here.
My version of AA is 3.7.584044 (attached: View attachment com.google.android.projection.gearhead-ffadc269cc39417e152ffcdd22183045.apk)
Not sure what you mean by "the more options *" but I've attached 2 screenshots of the app settings which may show what you meant.. if not show a pic of that setting.
oh you may meant the gear symbol at the top right? Here it opens fine but as that opens google stuff it makes sense that it fails on yours
.
Click to expand...
Click to collapse

Isn't mine basically the same as yours, other than H815? That gear icon will not open up the more options page. On my Nexus 5 with LOS 7.1.2 it opens a page with Settings for AA ie: Limit wifi, Connected cars, phone screen settings, etc.
If not the same maybe I should run your version of LOS.

jjcdennis said:
Isn't mine basically the same as yours, other than H815? That gear icon will not open up the more options page. On my Nexus 5 with LOS 7.1.2 it opens a page with Settings for AA ie: Limit wifi, Connected cars, phone screen settings, etc.
If not the same maybe I should run your version of LOS.
Click to expand...
Click to collapse
I've mentioned and linked the opengapps version, attached the AA version and mentioned the exact build for a reason yes.
The idea was that you try the exact same setup.
btw: which model do you have?
.-

steadfasterX said:
I've mentioned and linked the opengapps version, attached the AA version and mentioned the exact build for a reason yes.
The idea was that you try the exact same setup.
btw: which model do you have?
.-
Click to expand...
Click to collapse
H812 on the UsU Oreo build H812 build.
So I can copy what you have, other than I'm using the H812 versus the H815 LOS rom.
Thanks steadfasterX

steadfasterX, is it necessary that I format the data when I reload this rom. Takes a long time to restore everything.

jjcdennis said:
steadfasterX, is it necessary that I format the data when I reload this rom. Takes a long time to restore everything.
Click to expand...
Click to collapse
Use my latest preview version of TWRP then you can backup your data AND internal storage . you can first try without format. if you still have issues try to format it and if it doesn't fix anything you can restore by TWRP but ensure that you use build 144 or higher
Sent from my LG-H815 using XDA Labs

OK, thanks again. Will give it a go. I have your latest TWRP, 144_g4_0.
On the positive side after all kinds of failed troubleshooting my G4 has all of a sudden decided to connect with my PC. It shows as H812 in Explorer and in Device Manager as Lemobile Android Device with Android Composite ADB Device driver. A lot easier than using Cloud.

jjcdennis said:
OK, thanks again. Will give it a go. I have your latest TWRP, 144_g4_0.
On the positive side after all kinds of failed troubleshooting my G4 has all of a sudden decided to connect with my PC. It shows as H812 in Explorer and in Device Manager as Lemobile Android Device with Android Composite ADB Device driver. A lot easier than using Cloud.
Click to expand...
Click to collapse
Gave it a go, but as soon as I tapped on AA the error came up. I did format data to start from clean and used the older versions of AA and Google Play.
Update - I reinstalled all my apps via Titanium Pro (not AA) and set things up. I decided to tryy AA one more time before removing it and bingo it opened. Kinda waking on broken glass here and unsure whether or not the app will continue to function. Hooefully this fixed things.
Thanks again steadfasterX.

[GSI][UNOFFICIAL] LineageOS 17.1 Modified [TEST][XT1952-2]

MODIFIED EXCLUSIVELY FOR MOTO G7 PLAY
WARNING
Do not try to install this via fastboot, remove the magisk, to remove just reinstall the Stock Rom
MAIN FEATURES
Root modified by Spaceminer
More speed
Added multiple apps
Several useless apps removed
Black theme automatically enabled in all supported applications
Gapps already installed
Notch fix
And more
DOES NOT WORK
Fingerprint
Automatic brightness
INSTALLATION INSTRUCTION
1. Download and extract
2. Put the GSI on your memory card
3. Restart your phone in Bootloader / Fastboot mode
4. Open fastboot on your computer
use the command: fastboot -w
use the command: fastboot boot twrp.img
5. TWRP: Install> Install image> Choose image file> Flash on the system
DOWNLOADS
TWRP by Spaceminer: https://mega.nz/#!roRzBCTK!THHq0VMWqgtowJNkY-Id3b9S9H9dhzsJhE83k0Kvt2k
GSI: https://www.drive.google.com/file/d/1000HaJJqMdGyOtEd7ribp4n5Eb9l-3my/view

Works great apart from when I make calls the microphone doesn't work...whatsapp calls are fine it only seems to be a problem on cellular!

When I select the image I get 4 options and it does not let me install with any

With this my G7 play stay 32bits or can change for 64 bits?

RafaelItape said:
With this my G7 play stay 32bits or can change for 64 bits?
Click to expand...
Click to collapse
until we get a 64 bit kernel, it'll stay 32. i want to build a 64 kernel cause i want to bring ubuntu touch to this phone, that requires a 64 bit boot image, if we are to use erfan's (only method for android 9 devices rn)

Thanks man.
Managed to get magisk working with this rom..alongside twrp
Simply install latest magisk canary APK (284). Give it super user when it asks and restart the app
Then when clicking install...it gave me option of direct install (make sure recovery is selected). It should install successfully
I then rebooted to bootloader and to get to twrp hold volume up after selecting recovery and dont hold anything to boot back to Los..
Can't share my boot image if that helps anyone

CFKod said:
Thanks man.
Managed to get magisk working with this rom..alongside twrp
Simply install latest magisk canary APK (284). Give it super user when it asks and restart the app
Then when clicking install...it gave me option of direct install (make sure recovery is selected). It should install successfully
I then rebooted to bootloader and to get to twrp hold volume up after selecting recovery and dont hold anything to boot back to Los..
Can't share my boot image if that helps anyone
Click to expand...
Click to collapse
I gave it a try. It did indeed let me patch directly. It was very unstable. Things asking for su multiple times and not remembering my choice, certain modules not installing, and I always seemed to lose root entirely after rebooting

BobbyBlunt said:
I gave it a try. It did indeed let me patch directly. It was very unstable. Things asking for su multiple times and not remembering my choice, certain modules not installing, and I always seemed to lose root entirely after rebooting
Click to expand...
Click to collapse
yup... sorry, forgot to post... I assumed it was after installing modules.

Lockscreen not work for me, in all gsi roms.
Only stock works.

rom works great, feels like a new phone.
model XT1952-4.
not working unfortunately is the FM radio.
based on the error message when trying to install FM apps, it looks like the kernel driver was not included in the rom?
I can deal with the fingerprint not working, it would be really nice to get the FM driver included so I don't have to use data.
Overall the phone is so much better with this rom, Thank You!!!!

Hi, probably a stupid question, considering I'm new: what does this differ from the Lineage OS instructions for Moto G7 Play at their web site? I mean, why shouldn't I stick with their instructions?
I just want to understand what is at stake here (again, I'm new at this world of smartphone os's)
I'm really interested in replacing Android (which I like, but it's... Google ) and all carrier bloatware stuff by a free OS.
EDIT: Nevermind. I've just realized that it isn't for the G7 Play, it's for G7 only. Sorry about this (maybe useful for other newbies like me)

Thanks for all the work
Everything seems stable been using on daily driver for 2 days now. Only issue is bluetooth audio not working. I'm wondering if the Motorola face unlock app would work however current version isn't available.

gadolf said:
Hi, probably a stupid question, considering I'm new: what does this differ from the Lineage OS instructions for Moto G7 Play at their web site? I mean, why shouldn't I stick with their instructions?
I just want to understand what is at stake here (again, I'm new at this world of smartphone os's)
I'm really interested in replacing Android (which I like, but it's... Google ) and all carrier bloatware stuff by a free OS.
EDIT: Nevermind. I've just realized that it isn't for the G7 Play, it's for G7 only. Sorry about this (maybe useful for other newbies like me)
Click to expand...
Click to collapse
I'm using this on a Moto g⁷ Play in the USA, currently it's pretty stable. As for what's at stake, you lose access to Bluetooth audio, fingerprint & faceunlock unless you have SD card formated as portable storage and manage to get magisk working. There's a fix for Bluetooth Audio with magisk or ADB but I don't remember what the command was. Also as for magisk you should be able to fix atleast faceunlock because Motorola uses an app for it.

XxLilJeepXx said:
I'm using this on a Moto g⁷ Play in the USA, currently it's pretty stable. As for what's at stake, you lose access to Bluetooth audio, fingerprint & faceunlock unless you have SD card formated as portable storage and manage to get magisk working. There's a fix for Bluetooth Audio with magisk or ADB but I don't remember what the command was. Also as for magisk you should be able to fix atleast faceunlock because Motorola uses an app for it.
Click to expand...
Click to collapse
Thank you very much for sharing. I await your further results if any new issues arise to proceed with installing Lineage OS 17

Good job with the notch feels good to swipe down properly I’m encountering a issue the captive login appears to be broken I can’t sign into any WiFi’s that need a portal entry the portal screen doesn’t come up also I found how to get magisk to work properly With twrp u need the newest canary version and u have to patch directly (have recovery option enabled) which u use the root of this rom to achieve that after that backup boot image in twrp which will leave it with the magisk patched and twrp after reinstall the rom remove the phh root and restore yeh boot image in twrp and reboot to recovery from twrp and install magisk manager just note it’s lineage that makes magisk act up hence certain apps not obtaining root is lineage fault cause with another GSI like havoc which this method works for also (works with all GSIs to my knowledge) there no root app issues or modules not working just noticed that on lineage

workin on fixing phone
yashor said:
Thank you very much for sharing. I await your further results if any new issues arise to proceed with installing Lineage OS 17
Click to expand...
Click to collapse
phone no longer working because of trying to install magisk but I'll be trying to fix with LMSA and then using @PoochyX's instructions tomorrow
Edit: LMSA is now Rescue and Smart Assistant, I just tried to restore it with this but it needs to be on stock firmware to restore.

XxLilJeepXx said:
phone no longer working because of trying to install magisk but I'll be trying to fix with LMSA and then using @PoochyX's instructions tomorrow
Edit: LMSA is now Rescue and Smart Assistant, I just tried to restore it with this but it needs to be on stock firmware to restore.
Click to expand...
Click to collapse
Why not just boot into bootloader mode and fast boot stock firmware to recover your device ?

PoochyX said:
Good job with the notch feels good to swipe down properly I’m encountering a issue the captive login appears to be broken I can’t sign into any WiFi’s that need a portal entry the portal screen doesn’t come up also I found how to get magisk to work properly With twrp u need the newest canary version and u have to patch directly (have recovery option enabled) which u use the root of this rom to achieve that after that backup boot image in twrp which will leave it with the magisk patched and twrp after reinstall the rom remove the phh root and restore yeh boot image in twrp and reboot to recovery from twrp and install magisk manager just note it’s lineage that makes magisk act up hence certain apps not obtaining root is lineage fault cause with another GSI like havoc which this method works for also (works with all GSIs to my knowledge) there no root app issues or modules not working just noticed that on lineage
Click to expand...
Click to collapse
Hi,
From your experience which GSI is better for MOTO G7 Play 1952-2:
Havoc or Lineage ?

It depends on what u trying to do exactly if u a heavy Magisk user u want to stay away from lineage and use havoc since magisk plays well with it if u don’t care about magisk and just want a simple root then this rom be a good experience for other then rom WiFi portal issues this rom it’s excellent cause it’s the only one with the notch fix if that fix was easily implemented out this rom and could be used with another GSI that would of been fantastic...

PoochyX said:
It depends on what u trying to do exactly if u a heavy Magisk user u want to stay away from lineage and use havoc since magisk plays well with it if u don’t care about magisk and just want a simple root then this rom be a good experience for other then rom WiFi portal issues this rom it’s excellent cause it’s the only one with the notch fix if that fix was easily implemented out this rom and could be used with another GSI that would of been fantastic...
Click to expand...
Click to collapse
Thank you for your reply.
I favor stability and performance over Magisk.
In my case, do your recommend Lineage as my best option to try?

[How To] Flash GSI ROMs

Requirements:
- Stock Clean Firmware: https://mirrors.lolinet.com/firmware/moto/kane/official/
- TWRP: https://forum.xda-developers.com/one-vision/how-to/twrp-3-3-1-0-root-updated-kane-troika-t4102839
- GSI ROM (arm64, A/B versions): https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
- Permissiver_V5 Flashable Zip: https://androidfilehost.com/?fid=6006931924117940902
- Google Play Services APK - Whenever you boot into a GSI the first thing you should do is install the Google Play Services APK. Installing it will clear the "System Updating..." notification and you will be able to login to your Google account.
Google Play Services for Android 9 GSI: https://www.apkmirror.com/apk/googl...-24-13-100400-316577029-android-apk-download/
Google Play Services for Android 10 GSI: https://www.apkmirror.com/apk/googl...-24-13-120400-316577029-android-apk-download/
Instructions:
- Flash Stock firmware
- Wipe system and data in TWRP
- Reboot to bootloader
- Run the following command in the command line:
Code:
fastboot flash system [yourGSI.img]
- While still in fastboot mode run:
Code:
fastboot -w
- Reboot to TWRP and flash Permissiver_V5 zip file
- Reboot to the system
Notes:
Look at the size of the downloaded GSI.img file (Not the zip file), If it's larger than 3GB you won't be able to flash it because the system partition is limited to 3GB)
Permissiver_V5 is required for some GSI to successfully boot, some of GSIs might work without it but if you don't flash it and the GSI doesn't boot that might be the main problem.
GSI ROMs might have some bugs, the most known bug at least on One Vision and maybe Action is the Bluetooth Freeze Bug that might happen when you try to play music over Bluetooth. Be prepared for anything.
Not every GSI will successfully boot. Some of them might not boot but don't worry as there are a lot of GSIs for you to try on.
Same procedure works for both One Action and One Vision

FAQ:
Do I need to flash GAPPS after I install an GSI?
No. Flashing GAPPS is an optional step, most of the GSIs might already come with GAPPS installed and all you have to do to enjoy your ROM is to install the Google Play Services apk mentioned in my post.
You must install GAPPS if the GSI you're using doesn't have the Google Play Store app and you want to install any apps from the Play Store, but even then there are alternatives to install Play Store apps even without installing any GAPPS package
After installing a GSI my phone it's stuck in a bootloop, what do I do?
The main reason for your android not booting up is that some vendors enforce SELinux which stops GSIs from booting and the fix for that is by flashing the Permissiver_V5 zip file to be able to boot into GSI.
But if you can't boot even after you flashed Permissiver_V5, you either downloaded the wrong GSI or the GSI isn't compatible with your device so you have to find another GSI to flash. Remember that not every GSI can successfully boot.
The X GSI has the Y problem! How do I fix it?
Even after your GSI finished booting there's no guarantee that everything will work as it should. The best thing you can do is to find support on google, or if the creator of the GSI has provided any contact links (Email, Telegram, etc) you can contact him and ask him if there's a fix for your problem or not.

This is something new for me, I was used to install rom and gapps, is this something similar?

simije97 said:
This is something new for me, I was used to install rom and gapps, is this something similar?
Click to expand...
Click to collapse
Flashing GAPPS is totally optional, GSIs will work even without flashing them. Most of them already have GAPPS installed, other might not work with GAPPS.
Is totally up to you if you want to flash GAPPS on a GSI, but as I said most of them don't need it, the most important thing to install after flashing a GSI is to install the Google Play Service to login into your Google account and fix any issues related to Android Setup
[Edit] I've added a small FAQ section to my post above

simije97 said:
This is something new for me, I was used to install rom and gapps, is this something similar?
Click to expand...
Click to collapse
There are 2 main reasons why you should install GAPPS:
1: The GSI you're flashing doesn't have any google apps and in that case to be able to login into a google account and install apps using Play Store you have to install a GAPPS package to have access to google play store
2: The GSI has access to PlayStore but you just want to have other apps like YouTube, Gmail installed in your system. In this case I myself, I prefer to install the Google apps that I need from play store rather than installing a GAPPS package that bloats my phone with apps I don't use.
Anyway, flashing GAPPS is totally optional and it's up to you if you want it or not.
The most important thing when installing a GSI is to look if it has any google apps, if yes then it's important to install Google Play Services apk listed in my post.
To give you a small example Google Experience comes with google apps included so you never have to install GAPPS. I'm using Google Experience and everything worked out of the box, it didn't require the Google Play Services but I guess I just got lucky.
This can't be said for when I've installed an Android 11 Pixel-based GSI, where I had to install the Google Play Services to be able to use my Google Account and finish the android setup.

After few weeks I decided to try this and it works just fine, thank you. Unfortunately ROMs are not created for that big hole on the screen. It hides time, notifications etc., otherwise it works pretty well.. Any sugestions how to repair it? Thank you again

Go to developer settings. You find notch settings.

rhaavin said:
Go to developer settings. You find notch settings.
Click to expand...
Click to collapse
I installed Descendant X, there are some options for notch, but it doesn't work for One Vision.

Put the apk attached in /system/overlay and it will correct the values for the punch hole. Don't forget to reboot after. Also I've made this a long time a go but I didn't had time to test it as I'm on Android 8 due to working on something.
Report back if it works or not thanks.

SnoopDoggyStyleDogg said:
Put the apk attached in /system/overlay and it will correct the values for the punch hole. Don't forget to reboot after. Also I've made this a long time a go but I didn't had time to test it as I'm on Android 8 due to working on something.
Report back if it works or not thanks.
Click to expand...
Click to collapse
Unfortunately, I had to install stock firmware because of my work and Google pay. I was trying to hide root but I was unsuccessful. Anyway, thank you very much for sharing this

I installed GSI ROM, I have been trying to root it for 3 hours. Can someone here tell me what to do?

[Q][RECOVERY][3.4.0-0][kane] Official TWRP & Root for Motorola One Vision
Root & TWRP 3.4.0 for Android 10. Page on the official TWRP website https://twrp.me/motorola/motorolaonevision.html Installation Instruction 1. Download twrp-3.4.0-0-kane.img and twrp-installer-3.4.0-0-kane.zip TWRP, patched vbmeta.img and...
forum.xda-developers.com

WellThisSucks1 said:
I installed GSI ROM, I have been trying to root it for 3 hours. Can someone here tell me what to do?
Click to expand...
Click to collapse
You can take the "Magisk-v20.x-phh.zip" for root
Magisk-v20.3-phh.zip | by shumway66 for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Should work

simije97 said:
Unfortunately, I had to install stock firmware because of my work and Google pay. I was trying to hide root but I was unsuccessful. Anyway, thank you very much for sharing this
Click to expand...
Click to collapse
This works

alphalog said:
This works
Click to expand...
Click to collapse
How do I make it work?
Como lo hago funcionar xd

ChriisTBv said:
How do I make it work?
Como lo hago funcionar xd
Click to expand...
Click to collapse
Copy the apk to system/vendor/overlay
and reboot

Thank you very much for continuing to support and improve this smartphone

Problems after first update of LineageOs 17.1 install

First update since installing Lineageos on Lenovo P2.
The navigation bar along the bottom disappeared. Couldn't be swiped up - had been fixed previously.
Then found other things as well. Fingerprint sensor not working. Pixel launcher failing. Had been using Nova launcher and foolishly removed it thinking I'd reinstall to see if it restored the nav bar. But now stuck with a failing launcher and can't start anything - including Play to reinstall Nova. Just says 'Pixel Launcher keeps stopping, App info, Close App.' Cleared cache from App info as that was all I could do but no difference.
I haven't read it anywhere but are updates cumulative? Ie, can I skip one if I miss it and get all updates rolled up into the next one. I hope so because that's what I did. Jumped from something like 9th August to 30th.
Any ideas?

Current update always include codes from previous builds so you can skip nightlies in between. There are few solutions for your problem. I'm telling you two:
1. Install a third party launcher apk through system settings
2. Reboot into TWRP, wipe system only and install latest update package with nano gApps and it should work.

alirazaagha said:
Current update always include codes from previous builds so you can skip nightlies in between. There are few solutions for your problem. I'm telling you two:
1. Install a third party launcher apk through system settings
2. Reboot into TWRP, wipe system only and install latest update package with nano gApps and it should work.
Click to expand...
Click to collapse
Thanks so much for your help. In fact, while trying your first suggestion I somehow got into Google Play through APK install settings from where I was able to reinstall Nova Launcher. So now I have a partly useable phone again but still with the problems that followed the update in my OP (navigation bar gone, fingerprint sensor stopped working plus the failing launcher - those are just the things I found without looking).
It's disappointing that the update failed though, not least as staying updated was a major reason for moving to Lineage. Any ideas why this might be?
Maybe I should try the second suggestion and reinstall the update by sideloading as described here. So do I use the same file that I use to install LineageOS in the first place from here https://download.lineageos.org/kuntao? It's not stated in the document. And will this wipe the phone clean again?
Finally would I have to re-sideload a GApps package at the same time and should it be Nano GApps as suggested? Originally I installed Open GApps as suggested in the upgrade instructions.

bind00 said:
Thanks so much for your help. In fact, while trying your first suggestion I somehow got into Google Play through APK install settings from where I was able to reinstall Nova Launcher. So now I have a partly useable phone again but still with the problems that followed the update in my OP (navigation bar gone, fingerprint sensor stopped working plus the failing launcher - those are just the things I found without looking).
It's disappointing that the update failed though, not least as staying updated was a major reason for moving to Lineage. Any ideas why this might be?
Maybe I should try the second suggestion and reinstall the update by sideloading as described here. So do I use the same file that I use to install LineageOS in the first place from here https://download.lineageos.org/kuntao? It's not stated in the document. And will this wipe the phone clean again?
Finally would I have to re-sideload a GApps package at the same time and should it be Nano GApps as suggested? Originally I installed Open GApps as suggested in the upgrade instructions.
Click to expand...
Click to collapse
The Pixel launcher in Android 10 force closes if it is not chosen as "Recents provider". Therefore, navigation bar also stops working. Hence, we need Quickswitch app to choose Pixel or any other launcher such as Lawnchair for giving them the mentioned right and that works without any hiccups.
You should install the latest update after wiping system only. You don't need to wipe everything, just wipe system partition.
Nano GApps are taken from Open Gapps website. I've suggested nano GApps because it doesnt include Pixel Launcher hence, stock ROM launcher will flawlessly work. However, if you want to use Pixel Launcher then install Magisk from recovery and Quickswitch module within Magisk. Then open Quickswitch app from launcher and click Pixel Launcher. Quickswitch app will process for a few moments and will restart your phone. Now, choose Pixel launcher as default from settings if it is not used as default and Done.

alirazaagha said:
The Pixel launcher in Android 10 force closes if it is not chosen as "Recents provider". Therefore, navigation bar also stops working. Hence, we need Quickswitch app to choose Pixel or any other launcher such as Lawnchair for giving them the mentioned right and that works without any hiccups.
You should install the latest update after wiping system only. You don't need to wipe everything, just wipe system partition.
Nano GApps are taken from Open Gapps website. I've suggested nano GApps because it doesnt include Pixel Launcher hence, stock ROM launcher will flawlessly work. However, if you want to use Pixel Launcher then install Magisk from recovery and Quickswitch module within Magisk. Then open Quickswitch app from launcher and click Pixel Launcher. Quickswitch app will process for a few moments and will restart your phone. Now, choose Pixel launcher as default from settings if it is not used as default and Done.
Click to expand...
Click to collapse
Many thanks again for your detailed help. Much appreciated.
Went for standard Open GApps just because that's what I had before and had hoped to get it all back as it was. (I've no particular preference for Pixel only that was all that was available to me after updating through updater. ) I've got the update loaded now, sideloaded with adb and TWRP. Unfortunately I seem to have accidentally factory reset from TWRP (thought I was just swiping to unlock and only noticed too late. Doh.)
TBH, this has been a whole lot of hassle for an update. After hours to get this far now have to set phone up from scratch yet again. And crucially, I still don't know why updater failed. Going to be very nervous about running update in future and staying updated was the main point of moving to Lineage in the first place.
But thanks for help again.

bind00 said:
Many thanks again for your detailed help. Much appreciated.
Went for standard Open GApps just because that's what I had before and had hoped to get it all back as it was. (I've no particular preference for Pixel only that was all that was available to me after updating through updater. ) I've got the update loaded now, sideloaded with adb and TWRP. Unfortunately I seem to have accidentally factory reset from TWRP (thought I was just swiping to unlock and only noticed too late. Doh.)
TBH, this has been a whole lot of hassle for an update. After hours to get this far now have to set phone up from scratch yet again. And crucially, I still don't know why updater failed. Going to be very nervous about running update in future and staying updated was the main point of moving to Lineage in the first place.
But thanks for help again.
Click to expand...
Click to collapse
No problem bro. Next time, when you update, follow these things:
1. Keep ROM, Magisk and GApps in a single folder.
2. When updating ROM, just install the ROM and restart.

alirazaagha said:
No problem bro. Next time, when you update, follow these things:
1. Keep ROM, Magisk and GApps in a single folder.
2. When updating ROM, just install the ROM and restart.
Click to expand...
Click to collapse
Thanks again. That's good information. So you recommend not using the Updater but adb sideloading instead?
OK, and I just read this at stackexchange "You normally don't need to re-flash GApps as most GApps installers will install an addon.d script which restores GApps automatically after flashing a new ROM that supports addon.d (LineageOS does so)." So if GApps is in the same folder it finds it automatically I guess.
I'd better clue myself up on Magisk now and a decent backup system.
cheers

bind00 said:
Thanks again. That's good information. So you recommend not using the Updater but adb sideloading instead?
OK, and I just read this at stackexchange "You normally don't need to re-flash GApps as most GApps installers will install an addon.d script which restores GApps automatically after flashing a new ROM that supports addon.d (LineageOS does so)." So if GApps is in the same folder it finds it automatically I guess.
I'd better clue myself up on Magisk now and a decent backup system.
cheers
Click to expand...
Click to collapse
Built in update works as required but if it messes with system partition then you better download update and install it through recovery.
GApps can be restored after update but the point is that you don't need it. System update only replaces the older system files with new ones without touching gApps files. Whereas, Magisk is automatically installed after update if it's in the same folder.