Related
Q&A for [ROM] [COMMUNITY] ANDROID 5.1.1 OCTOS *Obake*
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [COMMUNITY] ANDROID 5.1.1 OCTOS *Obake*. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Can I install it without bootloader unlock?
Summersett said:
My bootloader unlocked Maxx is on 4.4 (19.5.3.obake-maxx_verizon.Verizon.en.US). Since my bootloader is unlocked, do I really have anything to fear when flashing ROMs or am I pretty much guaranteed to be able to always have WP off and root? I'd like to give this one a shot but don't want to cross any bridges I may not be able to come back across if need be.
Click to expand...
Click to collapse
My bootloader is locked, I'm on 4.4.4 with root, but I don't now how I can unlock my moto, I must to have TWRP? How can I install this recovery? Help me please, I want lollipop, and verizon is so slow.
This isn't the place to ask that, and right now you are stuck on stock. Please dig around the forums and do some research before spamming threads where content does not belong.
No GPS
Flashed this ROM on my Droid MAXX and love it. Everything seems to work except I cannot get any GPS lock on any application I tried. Downloaded GPS toolbox and reset and downloaded aGPS data but no change. Anyone have this problem? From what I've searched on forums it seems to be a somewhat common issue in Lollipop. FYI I also flashed a different 5.1.1 ROM and it had the same problem.
jwieler88 said:
Flashed this ROM on my Droid MAXX and love it. Everything seems to work except I cannot get any GPS lock on any application I tried. Downloaded GPS toolbox and reset and downloaded aGPS data but no change. Anyone have this problem? From what I've searched on forums it seems to be a somewhat common issue in Lollipop. FYI I also flashed a different 5.1.1 ROM and it had the same problem.
Click to expand...
Click to collapse
I haven't had this issue and have reflashed this ROM a few times. Tbh I have never even heard of that as an issue (though it's not like I researched Lollipop problems since I wasn't having any).
I used TWRP 2.8.4.0, factory reset, flashed the ROM, and then flashed these GApps. Idk if that makes a difference. Give it a shot if nothing else is working for you? Good luck.
Dang... That is exactly how I did it. I used that same exact gapps file and also am on TWRP 2.8.4.0. Seems like none else is reporting this problem on our phones. Maybe the radio got screwed up? Just thinking out loud here
Installed OctOS on two separate MAXXes. My gfs seems stable. Mines been touchy though-
A) Like someone else mentioned, using the flashlight for an extended period often ends up in the phone doing a hard reboot. Haven't tested this with her phone but she hasn't reported anything to me either.
B) WiFi has been unstable. Initially it was fine, but every now and then it starts refusing to connect to any network. It doesn't kick back any error. It will say connecting, etc, then at some point fail and go back to just noting it's a saved connection. Have to go through some combination of forgetting the connection, wiping cache/Darvin, think I even tried running fix permissions. Eventually it will work normally again, but not for long before having the same issue. There haven't been any wifi issues with the other phone. The first time this ever occurred was right after using it as a hotspot, but its happened more often without any hotspot usage than with it.
C) Did great at first, but without installing very many apps, it feels like it's gotten slightly sluggish and is often low on memory, and is burning through the battery much quicker. Used the be able to clear 24 hours before needing to charge, now I'm lucky to get 16. I haven't had the chance to see if this is also an issue on the other phone or not.
GPS works nicely for me with this rom. My phone got a fix in seconds with 16 satellites.
Question: which is the best way to theme this (or others, for that matter) rom? Download CM12 themes from mayket?
jwieler88 said:
Flashed this ROM on my Droid MAXX and love it. Everything seems to work except I cannot get any GPS lock on any application I tried. Downloaded GPS toolbox and reset and downloaded aGPS data but no change. Anyone have this problem? From what I've searched on forums it seems to be a somewhat common issue in Lollipop. FYI I also flashed a different 5.1.1 ROM and it had the same problem.
Click to expand...
Click to collapse
Did you ever get GPS back? Some say going back to stock, getting a lock, and then go back to the custom rom works. There is also a link in the exodus thread about doing two fastboot commands, which worked for me for a bit, bit now I'm back on stock with no GPS at all. Curious if you got yours working.
Hi all,
Last weekend I rooted my phone. I treble-ized it and tampered with a few GSIs. I finally chose to use PHHs Treble 9 GSI.
When I connected my phone to my car's Bluetooth I could call, but there was no sound. Is this a driver issue on my Vendor partition (ie did I use the wrong Vendor), or is this a general problem with GSI?
roytje88 said:
Hi all,
Last weekend I rooted my phone. I treble-ized it and tampered with a few GSIs. I finally chose to use PHHs Treble 9 GSI.
When I connected my phone to my car's Bluetooth I could call, but there was no sound. Is this a driver issue on my Vendor partition (ie did I use the wrong Vendor), or is this a general problem with GSI?
Click to expand...
Click to collapse
it wouldnt be a dirver since android doesnt use drivers, it would be in the bluetooth stack. likely caused by a failed flash of your ROM especially if other users arent having the same issue. What kind of car is it (assuming the deck is stock to the car)
Youdoofus said:
it wouldnt be a dirver since android doesnt use drivers, it would be in the bluetooth stack. likely caused by a failed flash of your ROM especially if other users arent having the same issue. What kind of car is it (assuming the deck is stock to the car)
Click to expand...
Click to collapse
Good to know it's only a problem what's occurring on my phone. That would mean flashing a different rom could solve the issue.
The car is a Punto EVO. I haven't tried any other Bluetooth devices, but I expect the same result.
I'll flash a new rom and report back. Thanks for replying.
roytje88 said:
Good to know it's only a problem what's occurring on my phone. That would mean flashing a different rom could solve the issue.
The car is a Punto EVO. I haven't tried any other Bluetooth devices, but I expect the same result.
I'll flash a new rom and report back. Thanks for replying.
Click to expand...
Click to collapse
yeah, reflash the same ROM or try a different one. Back in the day, there were tons of issues with stuff that was designed to work on the phone based on specific kernel programming that spoke to the hardware to allow these features to physically operate, but only in touchwiz based ROMs, AOSP based ROMs were left out in the cold. With the emergence of the necessity of a clean knox in order for certain things to work, i have given up on root for the time being so that i can enjoy the awesomeness that is paying for stuff with my watch (which requires an unrooted phone to work. Technically your phone can be rooted but it makes it a pain in the anus)
anyways, i think your audio issue might be a GSI specific thing, just a hunch tho. Might want to go look in the GSI threads and see if there is a list of what works/whats broke in the ROMs. They usually just come out and tell you if ti doesnt work because if its the other way around, the devs reputation will be tarnished
I flashed Lineage OS 16 (Android 9) GSI. Same problem. Also with other Bluetooth devices. I'm thinking it's the vendor I flashed. I did find an Oreo vendor for this device mentioning Bluetooth calls don't work.
Searched for a rom without Treble but couldn't find one that has December security (or November). For now I'll use my earbuds when calling from the car.
I could flash a number of images, but don't really want to the time of finding the perfect rom for my devices has passed. I'll just keep this rom and when I feel like it, I'll flash the stock rom.
Thanks anyways for the advice!
Originally, this was thread was centered on the LineageOS 17 GSI by AndyYan, however, CodeF86 has so very generously made a working GSI for the Moto G6 which you can try out now!
Unlike AndyYan's generic GSI, for this you do NOT need to flash johnaltg1's LineageOS 16 image (if you do, this GSI will NOT boot). It is recommended you use stock Pie firmware. Oreo firmware has not been tested and may result in bugs.
Download here—Compiled Feb 22nd, w/ working LTE!
See CodyF86's thread post
Some notes:
Unlike the generic GSI, calling works.
Also unlike the GSI, the colors don't invert randomly.
Magisk DOES NOT work at the moment, neither phhuson's nor regular Magisk. Flashing it will cause a bootloop.
Bluetooth audio has been reported to not work
As with many Android 10 GSIs/ROMs, Chrome freezes or crashes because GApps packages currently are missing the new Trichrome WebView implementation which replaces Chrome as the default WebView. This being worked on (see OpenGApps wiki and issue #773 on their GitHub.) For now, use another browser (like LineageOS's default browser) if you install GApps. —As soon as Trichrome is added onto the ARM package just as it has for ARM64, Chrome should be stable.
For now, that's all I can think of. However, if you notice any other bugs or caveats, let me know so I can add it to the list.
This is a GSI based on phhuson's prereleased GSI work and also based on the prereleased LineageOS 17. This is a pre-release so please be careful and don't use this as a daily driver. Things may break randomly, whoops, so please be patient! If you see any bugs, report them here.
Extremely huge shoutout to CodyF86 for this GSI!
The developer of this ROM has moved on to another phone and the community now has a full fledged 64-bit ROM which has much better support for things.
AgentICS said:
The LineageOS 17 GSI works great on the Moto G6. There are some caveats however for anyone willing to try it:
You MUST first flash the LineageOS 16.0 ROM first or else you will bootloop.
Use this Magisk from phhuson's official GitHub
Your screen may change colors and look weird, when this happens, go to Settings > Display > LiveDisplay> Color mode and change it to the value under the value selected on the menu and then back to the original one and that should fix it
If you flash GApps before first boot, follow AndyYan's suggestions as the Setup Wizard is broken for some reason on most GApps packages.
Calling while not on WiFi is broken for now.
For now, that's all I can think of. However, if you notice any other bugs or caveats, let me know so I can add it to the list.
This is a GSI based on phhuson's prereleased GSI work and also based on the prereleased LineageOS 17. Things may break randomly, whoops, so please be patient!
Click to expand...
Click to collapse
Just to reiterate, you are stipulating that this pre-release build doesn't permit me to make an outgoing phone call (nor possibly receive any) unless connected to a WiFi network? Please pardon my not-so-subtle-sarcasm ... but, why would anyone release this with a bug (or limitation) which inhibits the core functionality of the device? I could see a million other issues being permissible but not being able to make normal phone calls (or possibly even receive them) doesn't warrant any kind of release for testing. That being said, I'd be happy to help if possible and eagerly await a usable version of Android 10 to put on my Moto G6 which I only got a month ago (happily unlocked at a great price on Amazon). However, it is (currently) my main phone for making calls.
xda4joe said:
Just to reiterate, you are stipulating that this pre-release build doesn't permit me to make an outgoing phone call (nor possibly receive any) unless connected to a WiFi network? Please pardon my not-so-subtle-sarcasm ... but, why would anyone release this with a bug (or limitation) which inhibits the core functionality of the device? I could see a million other issues being permissible but not being able to make normal phone calls (or possibly even receive them) doesn't warrant any kind of release for testing. That being said, I'd be happy to help if possible and eagerly await a usable version of Android 10 to put on my Moto G6 which I only got a month ago (happily unlocked at a great price on Amazon). However, it is (currently) my main phone for making calls.
Click to expand...
Click to collapse
everything works for me
taiyofurukawa said:
everything works for me
Click to expand...
Click to collapse
so you can make phone calls without WIFI conection?
xavcasgar said:
so you can make phone calls without WIFI conection?
Click to expand...
Click to collapse
yesssss
xda4joe said:
Just to reiterate, you are stipulating that this pre-release build doesn't permit me to make an outgoing phone call (nor possibly receive any) unless connected to a WiFi network? Please pardon my not-so-subtle-sarcasm ... but, why would anyone release this with a bug (or limitation) which inhibits the core functionality of the device? I could see a million other issues being permissible but not being able to make normal phone calls (or possibly even receive them) doesn't warrant any kind of release for testing. That being said, I'd be happy to help if possible and eagerly await a usable version of Android 10 to put on my Moto G6 which I only got a month ago (happily unlocked at a great price on Amazon). However, it is (currently) my main phone for making calls.
Click to expand...
Click to collapse
It is pre-release so not all the bugs are ironed out, I should have added that this should not be used on your daily driver. But yes, it's dumb to use a phone that can't make calls without WiFi. Just as a note, you can make and receive calls however if you're not using WiFi, the caller can't hear you. I have filed a bug upstream with phhusson as this affects every GSI built using his work (Pixel Experience, Lineage and AOSP which I've tested). I hope this gets fixed soon so stay tuned to that GitHub issue
taiyofurukawa said:
everything works for me
Click to expand...
Click to collapse
xavcasgar said:
so you can make phone calls without WIFI conection?
Click to expand...
Click to collapse
taiyofurukawa said:
yesssss
Click to expand...
Click to collapse
How? What is your modem version/phone model?
Can't Boot
AgentICS said:
The LineageOS 17 GSI works great on the Moto G6. There are some caveats however for anyone willing to try it:
You MUST first flash the LineageOS 16.0 ROM first or else you will bootloop.
Use this Magisk from phhuson's official GitHub
Your screen may change colors and look weird, when this happens, go to Settings > Display > LiveDisplay> Color mode and change it to the value under the value selected on the menu and then back to the original one and that should fix it
If you flash GApps before first boot, follow AndyYan's suggestions as the Setup Wizard is broken for some reason on most GApps packages.
Calling while not on WiFi is broken for now.
Bluetooth is horribly broken for now, it causes the app playing audio to lag and crash so please stay away from it.
Chrome is wonky at the moment. It'll work and then all of a sudden cause the whole OS to lag and crash or become unresponsive. This is possibly an upstream GApps issue.
For now, that's all I can think of. However, if you notice any other bugs or caveats, let me know so I can add it to the list.
This is a GSI based on phhuson's prereleased GSI work and also based on the prereleased LineageOS 17. This is a pre-release so please be careful and don't use this as a daily driver. Things may break randomly, whoops, so please be patient!
I am documenting everything on here. Stay tuned to that page for more info and further updates. Addiotionally, I have filed a bug report regarding calling, please add on to that GitHub issue and bump it so it can get resolved.
Click to expand...
Click to collapse
Ok, so I installed and flashed Lineage 16 first. Then I flashed Lineage 17 GSI in system img, but then when I did that I go into twrp and it said an os was not installed and wouldn't boot. But if I just flash Lineage 16 it would boot. Am I doing something wrong?
SomeAndrodGuyWithInternet said:
Ok, so I installed and flashed Lineage 16 first. Then I flashed Lineage 17 GSI in system img, but then when I did that I go into twrp and it said an os was not installed and wouldn't boot. But if I just flash Lineage 16 it would boot. Am I doing something wrong?
Click to expand...
Click to collapse
First off, are you unzipping the file? The standalone uncompressed file is unflashable. It needs to be decompressed from it's .gz (or whatever it was compressed to) form. If you have, have you tried using fastboot flash system <lineage file name> from a PC?
AgentICS said:
It is pre-release so not all the bugs are ironed out, I should have added that this should not be used on your daily driver. But yes, it's dumb to use a phone that can't make calls without WiFi. Just as a note, you can make and receive calls however if you're not using WiFi, the caller can't hear you. I have filed a bug upstream with phhusson as this affects every GSI built using his work (Pixel Experience, Lineage and AOSP which I've tested). I hope this gets fixed soon so stay tuned to that GitHub issue
Click to expand...
Click to collapse
Just wanted to jump in here and say I'm seeing same bug on xt1925-6 with callers not able to hear me on any 10 gsi's and speakerphone does not work at all. Phh aosp 10 build 209 with stock pie 55-37-7-2 boot vendor boots fine, other gsi's will only boot using the Ali lineage full ROM boot- vendor but call audio is broken as well. Thanks for submitting the bug report, hopefully it will get fixed in future builds.
Hello friends,
It's been a while since i've posted on XDA. I was the person who originally rooted the g6 play. I managed to build a GSI image of 17.1 with the latest code as of today if anyone is interested I can upload it to gdrive or something, didn't feel like making a new thread.
It boots, mobile calls work, dark mode works (which is amazing), it all seems to work.
Getting it to compile was just short of a miracle...lol.
Only bad thing is I cannot get it to boot with any version of magisk even the version specifically for phh / Android 10, but with just the stock kernel with the ,verify removed it boots fine.
CodyF86 said:
Hello friends,
It's been a while since i've posted on XDA. I was the person who originally rooted the g6 play. I managed to build a GSI image of 17.1 with the latest code as of today if anyone is interested I can upload it to gdrive or something, didn't feel like making a new thread.
It boots, mobile calls work, dark mode works (which is amazing), it all seems to work.
Getting it to compile was just short of a miracle...lol.
Only bad thing is I cannot get it to boot with any version of magisk even the version specifically for phh / Android 10, but with just the stock kernel with the ,verify removed it boots fine.
Click to expand...
Click to collapse
That's amazing! Could you upload it please so I can test it?
Thank you!
AgentICS said:
That's amazing! Could you upload it please so I can test it?
Thank you!
Click to expand...
Click to collapse
GSI-Lineage-17.1-2-16-2020-system.img
It seems it only connects at 3g although it lists a different apn server on lineage, I may be able to fix that, and I couldnt get the sd card to format as anything but adaptive storage, but everything works more or less. going to recompile in a week its still pretty early in development stage of lineage.
CodyF86 said:
GSI-Lineage-17.1-2-16-2020-system.img
It seems it only connects at 3g although it lists a different apn server on lineage, I may be able to fix that, and I couldnt get the sd card to format as anything but adaptive storage, but everything works more or less. going to recompile in a week its still pretty early in development stage of lineage.
Click to expand...
Click to collapse
Huge thanks for this GSI!!! I've been using it and it works flawlessly, I have also observed that only 3G works for now but regardless of that, everything works fine.
Again, I can't reiterate enough how thankful I am with you for this GSI!
AgentICS said:
Huge thanks for this GSI!!! I've been using it and it works flawlessly, I have also observed that only 3G works for now but regardless of that, everything works fine.
Again, I can't reiterate enough how thankful I am with you for this GSI!
Click to expand...
Click to collapse
May have a fix for LTE compiling it now, using the stock apn file with the adjusted mcc mnc numbers.
If I could get root I could get it for sure, but I can't get it to boot with a magisk flashed kernel, even the android 10 special version of magisk.
I got LTE but now mobile network stays disconnected although there is an LTE connection. It's an apn issue will work on it. if I get it working will make a thread...not sure why magisk won't work with my builds / kernel though yet.
https://github.com/codyf86
I've noticed that restarting always restarts to the bootloader. I don't know if it's just me but that's weird
Could you provide a link to the kernel source used in the rom?
Uclydde said:
Could you provide a link to the kernel source used in the rom?
Click to expand...
Click to collapse
It's on his GitHub
The kernel is actually just the stock kernel from the latest firmware with the ',verity' flag hexedited out to disable encryption. (You also need to change the fstab that is in all the guides ever made including my original one), but I'm working on building the kernel and making it work...but I got LTE to woooooork with some changes to the stock apn file lineage provides ! lol.
Only thing now is that it thinks my external sd card is corrupted and wont format right unless i set it to adaptive storage, so make a backup of your external sd card for now. Going to try using TWRP to format it with a couple different file systems.
Here she is boys.
Lineage-17.1-02.22.20-treble-arm-system
Still working on getting it to boost with magisk not sure why it won't when it was fine in Pie.
Still playing with the apn file the apn its using says sprint ehrpd but not sure what makes it pick which apns to show on the screen, but the apn is set to x.boost.ispsn which makes LTE work. I'll clean it up soon.
(All of this is assuming you're on Boost / Sprint)
I was bored looks like we have a version out there but i havent tried it yet it has step by step pretty much but you will have to unroot go back to latest stock i think first then flash if anyone checks it out lemme know
https://www.getdroidtips.com/android-10-moto-g7-power/
the github is here https://github.com/phhusson/treble_experimentations/releases/tag/v210
AOSP 10.0 v210
Dev is phhusson <<-----all credit would be to this gentleman i just happened across it while i was surfing, and saw 10 was out for the plus.
toxinburn said:
the github is here https://github.com/phhusson/treble_experimentations/releases/tag/v210
AOSP 10.0 v210
Dev is phhusson <<-----all credit would be to this gentleman i just happened across it while i was surfing, and saw 10 was out for the plus.
Click to expand...
Click to collapse
I tried the android 10 system image on my moto g7 power. I tried wiping system and installing the system image in twrp.
Phone kept bootlooping. Ended up trying to restore my backup via twrp but data would not restore,and I ended up in a twrp bootloop. Eventually I somehow hardbricked the device. Luckily I was able to find a blankflash to restore the phone to fastboot and I used rsdlite to reflash fw. Maybe I should have wiped everything, not just sytem, but I'm not willing to risk trying again.
skalnas said:
I tried the android 10 system image on my moto g7 power. I tried wiping system and installing the system image in twrp.
Phone kept bootlooping. Ended up trying to restore my backup via twrp but data would not restore,and I ended up in a twrp bootloop. Eventually I somehow hardbricked the device. Luckily I was able to find a blankflash to restore the phone to fastboot and I used rsdlite to reflash fw. Maybe I should have wiped everything, not just sytem, but I'm not willing to risk trying again.
Click to expand...
Click to collapse
Same to me with the difference I wiped all. But I don't pretend to be a guru of the phone's firmwares so it might be I did it wrong.
Maybe it's not a good section for this thread, it's more like Q&A.
It's possible to flash Android 10 GSI, but it wasn't ready for a daily driver.
What was working:
-booting
-screen
-audio
-connecting to 4G network
what wasn't:
-connecting to wifi
-receiving SMS on 4G network
I did not test rest of it.
Just wait a little while longer. The official stock upgrade will be released and Android 10 custom ROMs will be developed.
robson_89 said:
Maybe it's not a good section for this thread, it's more like Q&A.
It's possible to flash Android 10 GSI, but it wasn't ready for a daily driver.
What was working:
-booting
-screen
-audio
-connecting to 4G network
what wasn't:
-connecting to wifi
-receiving SMS on 4G network
I did not test rest of it.
Click to expand...
Click to collapse
ut
Here are some notes about Android 10 gsi and Moto G7 power from the main developer. I believe there's a flashable wifi zip PHH made as a fix for the wifi somewhere on this page: https://github.com/phhusson/treble_experimentations/wiki/Moto-G7-Power
Yes, I've seen it.
I don't have telegram account nor do I wish to create any, so WiFi patch is not for me.
Besides, it's only applicable when your WiFi works with static IP but not with dhcp.
Mine wasn't working at all.
And by debloated I mean Google too. I prefer zero crap on the phone but baked in"features"aren't bloat hahhaahaha. I've gotta run microg that's what I bought it for lol. Prefer toot so I can do what I want.
Well since no one knows, has tried all three, or is afraid to offend sunshine, I'll chime in myself.
The Omnirom build is very good and let's me do everything I need but not everything I want. I've read that it's better than using a GSI (generic system image - I think). Omni has been very stable to be as old as it is. I was able to remove the gapps and install microg.
Microg won't install in twrp, and won't work in magisk unless you make 100% sure Google play services are gone.
An easy way to check if things are on the right track with microg is to look in settings under system, if it shows up at the near the bottom it's going to work.
I was unable to get microg working with stock but I think I could now.
With big red ( Verizon) wifi calling is available on stock but not in omni. This is expected as I've never had to work on anything other than a stock rom in the past. So if you're at the edge of signal coverage or like I am at the edge and about the same distance between 2 towers in two states with different service in both lol, you might want to keep stock if you need that feature. If not I'd say Omni all the way.
Perhaps I'll add to this as time goes on.
If you are just starting out tahr note that fastbootd isn't the bootloader, and use the latest adb and fastboot from Google, even on Linux I downloaded the most recent to be sure but that's up to you.
The Lenovo Recover works great but fastbootd works well for fixing small blunders too.
Fastbootd says Fastboot in huge letters at the top you can't miss it. Hahaha
One thing I find peculiar is that I was able to use the Fastboot command in the bootloader mode to install twrp. This gave me a false sense of hope.
And I falsely assumed I was in Fastbootd. Fastboot has been around for years I just never used it. I think it was around in the Droidx days but I could be mistaken.
Good luck!
We are very fortunate to have vache and other devs working on these devices. As well as users who can test and stuff.
Another user asked this previously without any response ... Could you post a degoogled Omni ROM without gapps? Or give any advice how to remove it ? You were the one to put it all together so surely for you it must be easy removing it? As for me, I've been stuck.
Sorry i never saw this until now but I'm not a developer just a microg and self-hosted nextcloud user.