AOSP 12.0 GSI - G6 ALIHello friends, how are you? I was pretty tired of the traditional roms we have for the Moto G6 there, (I got sick), these roms are excellent, but with time it ended up being more the same, that's when phhusson released an Android 12 GSI, I went to test it and found it amazing the operation on the system, unfortunately there is no way to use the SIM, but some improvements are even nice, I'm starting in this area of customization of the latest ROMs (current android)
You need a recovery that accepts ARM64 ROMs, and the GSI itself
In the link you select system-squeak-arm64-ab-vanilla.img.xz and download, then unzip and install on your system and test
GSI:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Depending on when you are watching this post the performance is already better, however I made this post to motivate the community (us) to try to port ROMs and GSIs for the Moto G6 ALI.
For those who are having doubts a while ago I made a video installing the TWRP with the GSI of Android 11 on the Moto G6 ALI, I recommend you check it out if you have any questions!
(The video is in Brazilian Portuguese my native language)
How were you able to get an a/b partition GSI to boot properly on an A-only partition device like the Moto G6?. I've used A-only GSIs successfully on mine in the past but my understanding is A-only has been discontinued with release of a12.
I don't know man, but I just installed it, in the application that sees which system it is if it's AB or A only says it's AB, if I'm not mistaken I've already tested A only roms for it but it didn't work for some reason, I don't know if it's the current Vendor of the custom Roms I'm using or something else, I think it's the vendor since it's not an ARM32 but an ARM64, it can also be for recovery. In short, I don't know.
but it works
Don't know why an a/b gsi works on an a-only device but it does. Give this a12 gsi a try OctaviOS-v3.2-arm64_bvN-29122021-Unofficial.img.xz. It booted and I got an LTE signal no problem.
doesn't work for me
tried both 64 and 32, i'm using twrp 3.6.0_9-0 though, not sure if that is the problem, rolling back to 11 for now.
You might to flash permissive v4 before first boot after flashing the gsi image. https://androidfilehost.com/?w=search&s=Permissiver
Skippy12359 said:
You might to flash permissive v4 before first boot after flashing the gsi image. https://androidfilehost.com/?w=search&s=Permissiver
Click to expand...
Click to collapse
Nope, still gets a boot loop into the bootloader, i'll give it another try though
adhamnasr said:
Nope, still gets a boot loop into the bootloader, i'll give it another try though
Click to expand...
Click to collapse
Try man, because it's worth testing and seeing the Moto G6 ALI running Android 12, pretty cool
HeroRicky_Games09 said:
Try man, because it's worth testing and seeing the Moto G6 ALI running Android 12, pretty cool
Click to expand...
Click to collapse
i am, but maybe i'm doing something wrong
do you guys push the img and install using twrp or sideload?
edit: i reflashed it to stock, and gonna repeat the process
I didn't use stock boot or vendor when Octavia gsi booted for me. I was on the latest Ali Crdroid11 Dec patch, backed it up in latest twrp, did a normal wipe and flashed the vanilla Octavia arm64 a/b system gsi link above. Don't recall if it booted right away or if I went back to twrp and flashed permissiver v4. Either way it booted fine, got carrier signal right away (t- mobile) , sound also worked fine. Didn't flash gapps or anything else. Just was curious if an a/b gsi would actually boot on a G6 and both Aosp12 and Octavia both did for me. Try this permissive zip if the other doesn't work https://androidfilehost.com/?fid=6006931924117886495
Did a little research on telegram and found out a12 a/b gsi's will also work on an a-only device as long as the device supports SAR (system as root). Treble check app shows the G6 supports SAR and is arm64 so that's likely why they boot OK for some of us. That said the two I've tried Aosp12 and Octavia12 were laggy and would hang occasionally.
For those who are having doubts a while ago I made a video installing the TWRP with the GSI of Android 11 on the Moto G6 ALI, I recommend you check it out if you have any questions!
(The video is in Brazilian Portuguese my native language)
I can't believe it, but I made it work...
adhamnasr said:
I can't believe it, but I made it work...
Click to expand...
Click to collapse
The cool thing about this GSI is that it runs without lags, the only problem is the mobile data. if it worked it would be perfect
HeroRicky_Games09 said:
AOSP 12.0 GSI - G6 ALIHello friends, how are you? I was pretty tired of the traditional roms we have for the Moto G6 there, (I got sick), these roms are excellent, but with time it ended up being more the same, that's when phhusson released an Android 12 GSI, I went to test it and found it amazing the operation on the system, unfortunately there is no way to use the SIM, but some improvements are even nice, I'm starting in this area of customization of the latest ROMs (current android)
You need a recovery that accepts ARM64 ROMs, and the GSI itself
In the link you select system-squeak-arm64-ab-vanilla.img.xz and download, then unzip and install on your system and test
GSI:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Depending on when you are watching this post the performance is already better, however I made this post to motivate the community (us) to try to port ROMs and GSIs for the Moto G6 ALI.
For those who are having doubts a while ago I made a video installing the TWRP with the GSI of Android 11 on the Moto G6 ALI, I recommend you check it out if you have any questions!
(The video is in Brazilian Portuguese my native language)
Click to expand...
Click to collapse
I made a video installing this GSI on it, go there and check it out! It is in Portuguese Brazil.
Will it work on moto g6 play Jeter 3gb ram 64 bit cpu snapdragon 430 currently on Android 11 pixel experience
Nikhil15 said:
Will it work on moto g6 play Jeter 3gb ram 64 bit cpu snapdragon 430 currently on Android 11 pixel experience
Click to expand...
Click to collapse
possibly yes!
Can you tell the steps of installation because I don't understand brazilian
And please tell about bugs of anything
Related
Heavily based on the WIP LineageOS port for the Moto E4 (Qualcomm) [perry] -- for more information about that, click here.
Known working:
Booting
Connecting to Sprint's 1xRTT network (2G data, voice, SMS)
Fingerprint sensor
WiFi
Broken:
Sound
Sprint 3G data and LTE (need to add in Sprint network blobs)
XDA:DevDB Information
LineageOS 14.1 for Moto E4 Plus (Qualcomm), ROM for the Moto E4 Plus
Contributors
ReimuHakurei, squid2, Alberto97
Source Code: https://github.com/ReimuHakurei/android_device_motorola_owens
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Based On: LineageOS
Version Information
Status: Alpha
Created 2017-10-31
Last Updated 2017-10-31
Uploaded another build that seems to get LTE on Sprint. All of the menus are still broken so you presumably need to be activated on stock before flashing.
Is there any way to make the fingerprint function to wake up / close screen to work with out requiring a pin/pattern/code to be active? That'd be an awesome feature
Installed on my XT1775 briefly and except for the sound this looks pretty good. I'm on AT&T and LTE worked fine, etc. I just can't live without sound as I need my phone for work teleconferences. I will *definitely* use this as soon as I can daily drive it!
I have tried (and failed) to get CDMA data properly working. Once someone gets CDMA/Sprint support working properly on one of the other devices in this family, it should be simple enough to port whatever the fix may be, but until that happens, this will likely remain as-is.
Since gsm seems to get LTE will this ROM still be worked on to get sound working? Even though I know CDMA users are out of luck for now. I have the standard e4 and want to buy a plus but I definitely need aosp ROMs.
Thanks for your work porting this. Actually shocked to not see more development considering how huge the battery is on the device.
fix-this! said:
Since gsm seems to get LTE will this ROM still be worked on to get sound working? Even though I know CDMA users are out of luck for now. I have the standard e4 and want to buy a plus but I definitely need aosp ROMs.
Thanks for your work porting this. Actually shocked to not see more development considering how huge the battery is on the device.
Click to expand...
Click to collapse
I need to repair my shattered Moto X Pure so I have a working phone to use while developing before I can do much more work here (ie: on fixing audio). This was mainly a proof-of-concept to make sure I was, in fact, able to get the thing to boot, before I spent too much work fixing other things.
For CDMA, I think the root of it is the new architecture Sprint is using in preparation for CDMA+VoLTE; I tried porting over files from the Moto X Pure's LineageOS port, but it uses older tech for CDMA internally. The Moto G5S has the same ISIMv2 SIM card on Sprint so should be similar software-side, and the Moto G5S will almost certainly have a pretty active community judging from past Moto G series phones. Moto X4 should be similar as well.
I am likely to be pretty busy for the next month or so, though, so probably won't have time to do any work on this until then.
so does someone plan to pick back up development on this? really surprised there isnt more devs on the plus model. much better build, camera, cpu and that big ?.
What exactly did you have to do to get this to work. I'm considering trying to port a few roms from perry over to owens, but if it's too hard, or just practically impossible I'm not going to bother.
Which version seems to have LTE working? I currently have no LTE just call(no sound) and txt lol
So I am attempting to build my first rom for the Moto e4 plus Qualcomm. I'm just following the build instructions on lineageos's website. I'm stuck now because there is not a device tree in the lineageos git. I see that the OP has a device tree on git and I also see that there is now a Moto kernel on git. I am unsure what the next step is? I'm unsure how to make the device tree part of my local git and also how to mix the new kernel posted from Moto. Any help and I will post what I create. Thanks.
@ReimuHakurei would you please attempt to fix sound for this custom ROM now that the kernel sources have been released. I've been looking forward to replacing the stock room on my phone for a while
FlagersXDA said:
@ReimuHakurei would you please attempt to fix sound for this custom ROM now that the kernel sources have been released. I've been looking forward to replacing the stock room on my phone for a while
Click to expand...
Click to collapse
Yes please! I really want to use this rom but I use my phone for listening to music all the time. Will some please fix the sound?
Bump, can someone please fix this?
Thank you for releasing this!
+1 for no sound or mic on xt1775
I tried Bluetooth and wired audio devices and sound/mic is not functioning for them either.
I am able to connect to the Verizon network with a their Sim through net 10, but only 3g (EvDo-rev.A, by choosing global auto) and not LTE after trying various modes in the 4636 menu. With the same Verizon Sim through net 10 my Nexus 5x h791 does connect to LTE .
Besides the issues above, this appears to be working well!
Also, if anyone can share complete stock partition images files (boot, recovery, and system partitions) for the xt1775, this would be appreciated, but I'm ok using my phone as is for now. I wish I had thought to make a complete backup by booting twrp through fastboot (fastboot boot recoverimagefilenamehere.img) and then making a backup first instead of flashing twrp before doing that. After I flashed twrp, instead of the Motorola bootloader unlocked screen, all I see is the white text "N/A" on a black background in the top left corner during bootup. Also, after I installed twrp I could no longer boot to the os until I installed this unofficial lineageos rom. I'm not sure if that is expected. Since I didn't make a backup of the system partition and boot before flashing twrp, I'm unable to restore the stock os. Lesson learned... immediately after making the mistake. I did make a backup of the boot and system partitions after flashing twrp before installing this unofficial lineageos rom(when I was already having the boot up issue), but when I restore them I have the same issue where the phone will not boot into the os. This is what I expected, at that point anyways.
Thanks again!
For Mediatek Variant
Sir,Any custom rom for Mediatek variant of this handset
fllannell said:
Also, if anyone can share complete stock partition images files (boot, recovery, and system partitions) for the xt1775, this would be appreciated, but I'm ok using my phone as is for now. I wish I had thought to make a complete backup by booting twrp through fastboot (fastboot boot recoverimagefilenamehere.img) and then making a backup first instead of flashing twrp before doing that.
Click to expand...
Click to collapse
I'm not sure if its the exact same variant, but @_maerk released stock images for the retail (snapdragon) e4 plus. Even if yours is carrier specific, as long as your bootloader is unlocked and you have the Qualcomm version you should still be good. I remember on my old Sprint Moto E from 2015 I could still flash the OS/Recovery/Boot images from the retail version, just not the modems or bootloader.
Update: I was able to restore to stock using the following link.
SCROLL TO POST # 10 for directions for Moto E4 Qualcomm (Owens) retail unlocked:
https://forum.xda-developers.com/moto-e4-plus/how-to/moto-e4-qualcomm-owens-completely-to-t3743441
Then I flashed Reiku's version of TWRP for the phone:
https://forum.xda-developers.com/moto-e4-plus/development/twrp-twrp-moto-e4-plus-qualcomm-t3697154
Then I installed this unofficial Lineage version:
[ROM][UNOFFICIAL][owens] LineageOS 14.1 for Moto E4 Plus (Qualcomm)
https://forum.xda-developers.com/mo...lineageos-14-1-moto-e4-plus-qualcomm-t3734197
Then I installed OpenGAPPs and AddonSu. The only hiccup I had through the process was that I got an ERROR Code: 64 when trying to install the ARM 64 version of openGapps in TWRP, so I used a non 64 version without issue.
Thanks to everyone for all of your efforts on these projects.
So, am I correct in believing that almost all treble ROMs will boot on the H9, if so, there is an entire forum dedicated to project treble development on XDA, the H9 is listed as supported for at least AOSP 8.1.
Anyone think that other ROMs will work?
Link to forum: https://forum.xda-developers.com/project-treble/trebleenabled-device-development
I'm not sure if I want to risk bricking my device, it's too much effort to unbrick it etc...
Yes. I flashed LineageOS and AOSP, both are working fine. Due to us not having a properly working TWRP for Android 8.1 I couldn't install any Gapps manually meaning you can only use a bare custom rom without Gapps or Roms with pre-installed Gapps (like the AOSP Rom in your shared forum).
Have you tried the Pixel one?
Pixel Experience does not boot on my h9
wakko42 said:
Pixel Experience does not boot on my h9
Click to expand...
Click to collapse
+1
wakko42 said:
Pixel Experience does not boot on my h9
Click to expand...
Click to collapse
Just can't understand why...Really wish to have that one....:crying:
Hello, has anyone (using a Treble Rom) ever had a successful SafetyNet test?
Hi!
i am new to the treble-enabled stuff, this is the first phone i own that is treble capable and i have a few questions. I think they can apply to other NOBS, so here i go hoping some nice guy will help me understand:
Background: i have the redmi 5plus (global) which i have unlocked (after painful 720h) and i have flashed Pixel Experience 8.1 rom, but i like to experiment and it seems most of interesting roms are on treble.
1. By default, "vince" is not treble enabled. (treble check app says so)
2. "vince" seems to be an "A only" device, not A/B device,
Main Question: Now, what should i do to try (safely) some GSI roms (like here XDA LOS 16 GSI)?
Sub-Question 1: I must most likely flash some other things first, i guess... like a vendor or a treble image? Where do i find it?
Sub-Question 2: I have installed TRWP recovery, is it treble enabled or should i ALSO find a treble enabled recovery?
If i got it all wrong, please i would be happy to stand corrected!
Hi.
Well, yeah, you need to install another vendor, as far as I know, OrangeFox is the treble enabled recovery.
Someone already explained this in this post.
Have fun. :fingers-crossed:
Xyzko said:
Hi.
Well, yeah, you need to install another vendor, as far as I know, OrangeFox is the treble enabled recovery.
Someone already explained this in this post.
Have fun. :fingers-crossed:
Click to expand...
Click to collapse
Thank you! Sometimes hard to find the right threads...
Installed orangefox, cool recovery!
One last question... how does kernel works with treble? Do i need treble enabled kernels if i want to change the kernel? Are they provided with the treble-enabled rom already or i get to keep the existing kernel? Is the kernel on a dedicated partition separated from the GSI and the Vendor? (i am starting to understand this, maybe)?
gardiol said:
Thank you! Sometimes hard to find the right threads...
Installed orangefox, cool recovery!
One last question... how does kernel works with treble? Do i need treble enabled kernels if i want to change the kernel? Are they provided with the treble-enabled rom already or i get to keep the existing kernel? Is the kernel on a dedicated partition separated from the GSI and the Vendor? (i am starting to understand this, maybe)?
Click to expand...
Click to collapse
Months ago it started to appear some projects about android 9.0 before of Google revealed it as android Pie, then at this time devices with treble support also can support GSIs from these projects according two specific conditions: the processor (first qualcomm, then exynos, kirin and mtk were supported) and kind of partition system A-A/B.
At this first times was needed to flash a vendor treble supported rom to add treble support and flash over it a GSI 9.0. without the need to flash other kernel.
In this forum there are a lot of GSIs that eventually could work in our device but it could be many bugs https://forum.xda-developers.com/project-treble/trebleenabled-device-development.
Now is not needed to complicate the job flashing a vendor, then a GSI and maybe a custom treblized kernel so started to appear first developments of roms running 9.0 and these roms will work as exactly did it any rom 7.1 or 8.1, in the future they could be include treble support.
This is the short story.
Hi guys,
I am forced to upgrade my moto G5 plus due to a network update
In my moto G5 plus I have installed dotOS with android 11 and I am really happy with it, and I would like "clone" it on a Moto G Power.
Here are some questions:
1) since Moto G Power (2021) is not listed on dotOS but a GSI ARM64 available, has anyone experienced with that? I am also open to other custom ROMS (also Lineage OS doesnt have this devicelisted)
2) I also noticed that TWRP is not available for Moto G Power (2021), is there a good alternative or I have to use adb fastboot?
Thanks!
Edit:
I just found the thread:
[RECOVERY][UNOFFICIAL] TWRP 3.6.0-11 [BORNEO] Android 11 Based (updated 12/11/2021)
I can try that for question 2
Efone said:
Hi guys,
I am forced to upgrade my moto G5 plus due to a network update
In my moto G5 plus I have installed dotOS with android 11 and I am really happy with it, and I would like "clone" it on a Moto G Power.
Here are some questions:
1) since Moto G Power (2021) is not listed on dotOS but a GSI ARM64 available, has anyone experienced with that? I am also open to other custom ROMS (also Lineage OS doesnt have this devicelisted)
Click to expand...
Click to collapse
Presently I don't believe it is possible to have a custom rom as we need the kernel be released for it to have a chance, or a compatible similar device and its kernel.
Hi Onoitsu and thank you for the reply,
so I guess I could go with the stock ROM. I noticed that I can use https://mirrors.lolinet.com/firmware/moto/borneo/ has an official and blankflash (not sure what the difference is). If I understand the process correctly I could:
1) unlock bootloader
2) flash twrp in recovery
3) flash blankflash.zip (or official?) through twrp
4) flash magisk through twrp
5) restore my old phone dotOS android 11 backup through twrp
and I should have all the apps and data as in the old device?
Efone said:
Hi Onoitsu and thank you for the reply,
so I guess I could go with the stock ROM. I noticed that I can use https://mirrors.lolinet.com/firmware/moto/borneo/ has an official and blankflash (not sure what the difference is). If I understand the process correctly I could:
Click to expand...
Click to collapse
The blankflash is only if you can no longer flash anything by usual methods
Blankflash and EDL Mode
Is my device in EDL Mode?
How to boot into EDL Mode
Thanks for the info!
Should the reasoning above work if I use official instead of blankflash?
Efone said:
3) flash blankflash.zip (or official?) through twrp
Click to expand...
Click to collapse
Neither the blank flash nor official firmware are twrp compatible.
Thanks sd_shadow for the info, it is really helping me out.
I saw your post for using LSMA, but I couldnt find a Linux version. Is there one? Or the only other option I have is going through the fastboot process?
Can anyone tell me if there is going to be custom roms made for Borneo?
Hatrackman said:
Can anyone tell me if there is going to be custom roms made for Borneo?
Click to expand...
Click to collapse
Still the reason I cite in post 2 above, indeterminate, sadly.
Onoitsu2 said:
Still the reason I cite in post 2 above, indeterminate, sadly.
Click to expand...
Click to collapse
Mostly concerned because google has said they're going to stop their 'less secure app' thing at the end of this month and it might mean textnow will stop working outright for people that don't use play services.
Hopefully anyone working on making a custom rom for Borneo will see this thread and maybe give an idea if its going to happen.
Does this help?
If I wanted to start from scratch what would I need to know to make my own custom rom? Don't need a phone, will only ever use wifi. Just need microg basically.
The following statement is on the dotOS FAQs:
Q: My device is not supported! What should I do?!A: First reason can be that our development team doesn't have your device to support it or we no maintainer applied for this device. You can always use our GSI builds if your phone supports Treble Project.
Here we have this statement:
... Google requires every Certified Android device launching with Android 8.0 Oreo and above to support Treble.
Here borneo is listed as a supported device.
Does this mean dotOS GSI supports MotoGPower 2021 without the need of vendor blobs?
Onoitsu2 said:
Presently I don't believe it is possible to have a custom rom as we need the kernel be released for it to have a chance, or a compatible similar device and its kernel.
Click to expand...
Click to collapse
@sd_shadow
Two sites that potential rom developers may want to check out:
1) https://github.com/moto-common
check out: https://github.com/moto-common/andr...ernel/blob/12/dtb/bengal-moto-base-borneo.dtb
2) https://github.com/moto-sm6115
Scroll through the list of repositories, particularly in the moto-common site
@sdembiske that looks promising, I am willing to give it a shot and contribute to the community. Is there a good guide on how to build the kernel with vendor tree/blobs etc...?
Reference "Moto G Power 2021 XT2117-4 Firmware Extractions" - You will find the extracted kernel etc. in the boot.img extracted link that you can download - there are many other extractions that you hopefully can use to build a custom or AOSP rom.
Your best bet would be to add a pre-built kernel in the build - you can google that for how-to's.
Onoitsu2 said:
Presently I don't believe it is possible to have a custom rom as we need the kernel be released for it to have a chance, or a compatible similar device and its kernel.
Click to expand...
Click to collapse
The Xiaomi poco m3 has the same SoC and other innards as the Moto G Power 2021 and it also has unofficial Lineage OS 19 support. I am considering hitting them up and using their code as part of the build. I'm also requesting Motorola Mobility LLC to release the kernel source for Android 11. I already have a device tree for Borneo on my github. Me and Fazwalrus have a telegram chat set up for the ROM development here
What's up guys? I have a question, currently my device has Lineage 19.1 ROM installed (Unofficial), I'm not having any problems or anything like that, quite the contrary, it's super stable, but I'd like to test some GSI ROMs on my device, since there aren't many build options for it specifically (LGE G850UM). So I wanted to know if I can leave Lineage 19.1 and install a GSI through TWRP without having to go back to Stock ROM... how to do this smoothly? Also wanted an indication of a GSI on Android 12 or 13 that runs stably on it. Thanks for reading this far!
ThePhanton said:
What's up guys? I have a question, currently my device has Lineage 19.1 ROM installed (Unofficial), I'm not having any problems or anything like that, quite the contrary, it's super stable, but I'd like to test some GSI ROMs on my device, since there aren't many build options for it specifically (LGE G850UM). So I wanted to know if I can leave Lineage 19.1 and install a GSI through TWRP without having to go back to Stock ROM... how to do this smoothly? Also wanted an indication of a GSI on Android 12 or 13 that runs stably on it. Thanks for reading this far!
Click to expand...
Click to collapse
Hey! If you have enough knowledge about GSIs (image type required for your device, disable Verity etc. ), then you can proceed to flash any GSI(present version or above). As I don't have the device model that you're having, i can't say much about it. CLICK HERE for more information, maybe you'll find something about your device.
Note: it's best to have stock firmware downloaded in case something goes wrong
Click to expand...
Click to collapse