{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 20.0 for the Pixel 7 Pro (cheetah) and Pixel 7 (panther).
Known issues:
NOTE: This is an early-stage build, and may not be the most stable. It works fine for me as a daily driver on a Pixel 7 (panther), however.
The status bar is mis-aligned to the left by a few pixels, but this does not cause any usability issues, fortunately.
Dual eSIM doesn't work (yet), but stock is probably affected too until the feature drop
You tell me.
Install Instructions:
Spoiler
Be sure you're on the latest stock 13 build and have an unlocked bootloader. You may also be able to flash from GrapheneOS, CalyxOS, or another ROM.
Go into fastboot mode (turn off phone and then Power + Volume down)
Make sure you have the adb/fastboot tools
Run fastboot flash --slot all boot boot.img
Run fastboot flash --slot all init_boot init_boot.img
Run fastboot flash --slot all vendor_boot vendor_boot.img
Run fastboot flash --slot all vendor_kernel_boot vendor_kernel_boot.img
Boot into recovery
Press Factory Reset and confirm
Go to Apply Update -> Apply from ADB
Run adb sideload LOS_BUILD (Replace LOS_BUILD with your LOS ZIP file)
To add GApps, go to Advanced -> Reboot to Recovery -> Apply Update -> Apply from ADB
Run adb sideload GAPPS_BUILD (Replace GAPPS_BUILD with your GApps ZIP file, repeat this step if you want Magisk)
Press Reboot System Now
Update Instructions:
Spoiler
Download the latest ZIP
Reboot to recovery
Flash the latest ZIP
Reboot to recovery
If you previously installed it, flash GApps and Magisk
Reboot to system
Passing SafetyNet/Play Integrity:
For some reason, this ROM only needs the Displax SafetyNet Fix and Shamiko (or DenyList) on top of Magisk in order to pass SafetyNet/Play Integrity, which is a nice bonus. As of 11/17, I was able to use GPay with this ROM if you use Magisk, Shamiko, and Displax SafetyNet Fix.
Download:
Pixel 7 Pro (cheetah)
Pixel 7 (panther)
Official MindTheGApps
UPDATE: LineageOS has "experimental" builds for Pixel 7 (and 6) here. They aren't technically mine, but I'm also the reason Google Tensor GKI kernels build there . Fortunately GPay still works with the experimental builds.
Sources:
Kernel
Device Trees
Vendor
ChangeLog:
2022/11/26:
Updated build to 2022/11/27 (arrgh, UTC/PST differences)
2022/11/16:
Initial build for cheetah/panther.
Is stable (for me at least) on a Pixel 7, your experience may vary however
Reserved 1
Reserved 2
Excited and excellent news. Thank you for your time and patience to bring something for a cheeta.
thanks for sharing
Ahhh Yeah! you rock man! I am dropping everything to get this installed now!! Thank you so much!
oh do you know if this build includes the google photos unlimited storage baked in? I Had It with SparkOS on my pixel 6 pro, and its a lifesaver! I guess Ill find out as soon as i get it running. Thank you again!
Heck ya! Finally! I have experience flashing lineage os. Thanks! Hope the battery life is great.
It did not recognize my sim card as the mobile data was greyed out. I had to revert back to stock rom and did everything correctly as you explained how to install it.
UltimateGamer83 said:
It did not recognize my sim card as the mobile data was greyed out. I had to revert back to stock rom and did everything correctly as you explained how to install it.
Click to expand...
Click to collapse
Are you on eSIM or physical SIM? Pro or non-Pro? Which carrier/country? Do you have a T-Mobile or AT&T variant?
On a unlocked non-carrier variant Pixel 7, this ROM recognizes my T-Mobile US eSIM, and also a Verizon MVNO (US Mobile) physical SIM.
MrNegative370 said:
Ahhh Yeah! you rock man! I am dropping everything to get this installed now!! Thank you so much!
oh do you know if this build includes the google photos unlimited storage baked in? I Had It with SparkOS on my pixel 6 pro, and its a lifesaver! I guess Ill find out as soon as i get it running. Thank you again!
Click to expand...
Click to collapse
I don't use Google Photos since I use Nextcloud and am not sure, but it should work since unlike official LOS builds, the ROM fingerprint is the same as stock (also similar to how Play Integrity passes).
MrNegative370 said:
Ahhh Yeah! you rock man! I am dropping everything to get this installed now!! Thank you so much!
oh do you know if this build includes the google photos unlimited storage baked in? I Had It with SparkOS on my pixel 6 pro, and its a lifesaver! I guess Ill find out as soon as i get it running. Thank you again!
Click to expand...
Click to collapse
No lineageos doesnt have this feature. Use the Pixelify.apk and you are good to go.
gapps doesnt have android 13? how do i get gapps after i flash lineageos?
my google playstore doesnt work, tried reflash gapps 3 times.
gapps : https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-T/08-Sep-2022/
SynGreis said:
gapps doesnt have android 13? how do i get gapps after i flash lineageos?
Click to expand...
Click to collapse
The GApps link does show A13 to me, it's the MindTheGapps-13.0.0-arm64-20221025_100653.zip file you need to download and flash for GApps.
SynGreis said:
gapps doesnt have android 13? how do i get gapps after i flash lineageos?
Click to expand...
Click to collapse
You have to reboot to recovery before you install GApps. If you just flash GApps after Lineage without rebooting to recovery, you won't get GApps.
This is an issue with A/B partition devices (basically all modern Android phones).
tried it again. reinstalling from scratch. i have a pixel 7 pro factory unlocked model straight from google.com. i have the bootloader unlocked with oem. my carrier is att with phsyical sim. so it is indeed working this time. maybe the first time didn't work because i forgot to factory reset.
UltimateGamer83 said:
tried it again. reinstalling from scratch. i have a pixel 7 pro factory unlocked model straight from google.com. i have the bootloader unlocked with oem. my carrier is att with phsyical sim. so it is indeed working this time. maybe the first time didn't work because i forgot to factory reset.
Click to expand...
Click to collapse
That's your issue, if you don't factory reset then it obviously won't work.
Well, sometimes I forget it too .
Can you install gcam after? And is it working properly?
Related
Disclaimer:
Only use TWRP for zips and Fastboot for images as TWRP isn't 100% stable yet. This would be my recommendation to anyone else looking to mess around with treble and custom roms. That is unless you know what you're doing. Also I am NOT responsible for any dead or bricked devices.
This threads purpose is for testing and documenting working treble roms for our Moto G7.
Roms that work:
Havoc OS
Roms that DON'T work:
All of Erfan's GSI Ports
Resurrection Remix
Q Developer Preview
Pixel Experience
Prerequisites:
Bootloader must be unlocked
ADB must be installed on a working PC
TWRP installed or able to boot from Fastboot
How to install:
Reboot to bootloader
Install boot.img in fastboot (Linked HERE)
Install the rom.img of your choice in fastboot (Rom must be ARM64 AB also make sure to flash system with the command "fastboot flash system -u your_image.img"))
Wipe userdata in fastboot
Reboot to TWRP and tap wipe, advanced wipe, system, then repair or change file system, then resize file system
Install Magisk (optional) and OpenGapps (also optional but recommended) in TWRP
Reboot and enjoy
PSA - If anyone finds any other working roms please report it on this thread and I will test the rom and update the thread accordingly.
Screenshots of Havoc OS on Moto G7
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Very nice. I will be giving this a shot soon.
Try BlissRoms/LineageOS and Aosp Extended
GamingHero said:
Try BlissRoms/LineageOS and Aosp Extended
Click to expand...
Click to collapse
I'll probably give them a try sometime soon here but just a word of advice. I think only phh-treble roms work on our device atm. So any rom based on the phh-treble source code.
I'm not a fan of project treble. the roms are too buggy. I really miss the days of lineage nightlies. there is literally zero development for the G7
Yeah well treble is just fine. No one wants to develop for specific devices anymore cuz once the correct patches are upstreamed to the treble source code the ROMs will work fine. Phh already has 99% of everything working out of the box for the g7. Just not Bluetooth audio and there isn't an overlay for the notch yet (easy fix).
CurbThePain said:
Yeah well treble is just fine. No one wants to develop for specific devices anymore cuz once the correct patches are upstreamed to the treble source code the ROMs will work fine. Phh already has 99% of everything working out of the box for the g7. Just not Bluetooth audio and there isn't an overlay for the notch yet (easy fix).
Click to expand...
Click to collapse
I'll stick to stock, rooted running edxposed for now.
fix-this! said:
I'll stick to stock, rooted running edxposed for now.
Click to expand...
Click to collapse
What modules are you using with edxposed?
Is there a way to install with TWRP?
How did you install RR. Was it fresh? Did you try to dirty flashover phh asop?
@CurbThePain sorry to go kinda off topic, but i have a g7 power, is it necessary to have a different kernel than stock (magisk patched) to boot a gsi on g7? Sorry if its a stupid question, im new to the whole treble/ab devices scene, and after the last rom i used, stock android is very lacking in features (came to the g7 power from sony xzp, existenz rom, non treble, a-only).
MIUI GSI from Erfan's ports works bro
CurbThePain said:
Disclaimer:
Only use TWRP for zips and Fastboot for images as TWRP isn't 100% stable yet. This would be my recommendation to anyone else looking to mess around with treble and custom roms. That is unless you know what you're doing. Also I am NOT responsible for any dead or bricked devices.
This threads purpose is for testing and documenting working treble roms for our Moto G7.
Roms that work:
Havoc OS
Roms that DON'T work:
All of Erfan's GSI Ports
Resurrection Remix
Q Developer Preview
Pixel Experience
Prerequisites:
Bootloader must be unlocked
ADB must be installed on a working PC
TWRP installed or able to boot from Fastboot
How to install:
Reboot to bootloader
Install boot.img in fastboot (Linked HERE)
Install the rom.img of your choice in fastboot (Rom must be ARM64 AB also make sure to flash system with the command "fastboot flash system -u your_image.img"))
Wipe userdata in fastboot
Reboot to TWRP and tap wipe, advanced wipe, system, then repair or change file system, then resize file system
Install Magisk (optional) and OpenGapps (also optional but recommended) in TWRP
Reboot and enjoy
PSA - If anyone finds any other working roms please report it on this thread and I will test the rom and update the thread accordingly.
Click to expand...
Click to collapse
I've gotten MIUI, PixelDust, and Q all to boot. Will be getting back to everyone once I have all the screens organized and might start making threads. Also working on LoS still, just been busy with irl/
thaunknownartist said:
I've gotten MIUI, PixelDust, and Q all to boot. Will be getting back to everyone once I have all the screens organized and might start making threads. Also working on LoS still, just been busy with irl/
Click to expand...
Click to collapse
Any issues with getting the GSI builds to run? All flashed through fastboot correct?
---------- Post added at 06:32 PM ---------- Previous post was at 06:31 PM ----------
thaunknownartist said:
I've gotten MIUI, PixelDust, and Q all to boot. Will be getting back to everyone once I have all the screens organized and might start making threads. Also working on LoS still, just been busy with irl/
Click to expand...
Click to collapse
Was going to attempt a RR install to my G7. Just making sure iylt was as straightforward as it should be.
BlissRoms/LineageOS/Paranoid Android/Dirty Unicorns/MIUI(?)/Bootleggers Rom/Viper OS/PixelDust
GSI left over
Was unable to get Resurection remix or MSM xtended to boot. RR gets stuck at boot animation. phh's trebble runs ofc.
GamingHero said:
BlissRoms/LineageOS/Paranoid Android/Dirty Unicorns/MIUI(?)/Bootleggers Rom/Viper OS/PixelDust
GSI left over
Click to expand...
Click to collapse
how successful were you with bliss roms. I got it to install but then after first boot the systemui stops working and is no longer functional
Druadach said:
how successful were you with bliss roms. I got it to install but then after first boot the systemui stops working and is no longer functional
Click to expand...
Click to collapse
I am with the Stock ROM of the motorola g7, waiting for the warranty to finish
CurbThePain said:
Disclaimer:
Only use TWRP for zips and Fastboot for images as TWRP isn't 100% stable yet. This would be my recommendation to anyone else looking to mess around with treble and custom roms. That is unless you know what you're doing. Also I am NOT responsible for any dead or bricked devices.
This threads purpose is for testing and documenting working treble roms for our Moto G7.
Roms that work:
Havoc OS
Roms that DON'T work:
All of Erfan's GSI Ports
Resurrection Remix
Q Developer Preview
Pixel Experience
Prerequisites:
Bootloader must be unlocked
ADB must be installed on a working PC
TWRP installed or able to boot from Fastboot
How to install:
Reboot to bootloader
Install boot.img in fastboot (Linked HERE)
Install the rom.img of your choice in fastboot (Rom must be ARM64 AB also make sure to flash system with the command "fastboot flash system -u your_image.img"))
Wipe userdata in fastboot
Reboot to TWRP and tap wipe, advanced wipe, system, then repair or change file system, then resize file system
Install Magisk (optional) and OpenGapps (also optional but recommended) in TWRP
Reboot and enjoy
PSA - If anyone finds any other working roms please report it on this thread and I will test the rom and update the thread accordingly.
Click to expand...
Click to collapse
Can somebody tell me the steps to install it? I didn't understand at all.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device. This is a straightforward port of the device tree for flame (Pixel 4) to sunfish (Pixel 4a).
Downloads:
sunfish (Pixel 4a) rom (v2): https://mega.nz/file/zG4UVTQB#ZXLw_qULzC8-an-MEdxdAvUMhmIa5qLI6YG54Feh2z0
410b3f523795d9d1481d183309adb170 lineage_sunfish-qd3a.200805.001-rel-v2.zip
sunfish (Pixel 4a) rom (v1, broken, do not install): https://mega.nz/file/jXRB2a4B#a5Dcf9T6emWAwvAj3oFvofkI0la0zf7vj5KIMn-yQaM
MD5: 86743134c3032a030d35195d44f02e1b lineage_sunfish-qq3a.200805.001.zip
This is not a recovery-installable zip! Please read below for how to install this image
Prerequisites:
Like the TWRP build for this device, this ROM build is only known to be compatible with older firmware. I only tested QD4A.200805.003, but .001 would likely work as well. If you have a newer version, you will need to downgrade at least the bootloader and radio first. I recommend installing the QD4A.200805.003 firmware image from Google, as that's what I tested with.
Instructions:
1. Flash the vbmeta.img file in the included zip (fastboot flash vbmeta vbmeta.img)
2. Reboot into fastbootd (fastboot reboot fastboot)
3. Run fastboot update -w lineage_sunfish-qd3a.200805.001-v2.zip
(If you do not have a working fastbootd, extract boot.img from the update zip and flash it from the bootloader first)
Working:
- Camera
- Fingerprint
- Wi-Fi
- Bluetooth
- Sound
- Mobile data (tested with T-Mobile only)
Not tested:
- Google apps (should work fine, but you never know)
Changelog/Source Code:
sunfish device tree: https://github.com/liamwhite/android_device_google_sunfish
sunfish kernel tree: https://github.com/liamwhite/android_kernel_google_sunfish
Credits:
Many thanks to all LineageOS team members and all the contributors out there in the community.
Android version: 10
Kernel version: 4.14.117
Sorry if this a dumb question but couldn't we use the same boot image used in derpfest and superior os to sideload the rom?
just asking because that's how I flashed a lineage test build.
thank you sir my devices 4a .. build number RP1A200720.010 this rom dont work....
Edmontonchef said:
Sorry if this a dumb question but couldn't we use the same boot image used in derpfest and superior os to sideload the rom?
just asking because that's how I flashed a lineage test build.
Click to expand...
Click to collapse
posıtıve said:
thank you sir my devices 4a .. build number RP1A200720.010 this rom dont work....
Click to expand...
Click to collapse
Like the TWRP build for this device, this ROM build is only compatible with older firmware. I only tested QD4A.200805.003, but .001 would likely work as well. If you have a newer version, you will need to downgrade at least the bootloader and radio first. I recommend installing the QD4A.200805.003 firmware image from Google, as that's what I tested with.
The Derpfest build uses the newer firmware and I don't think it would be compatible. You could certainly try, though.
liamwhite said:
Like the TWRP build for this device, this ROM build is only compatible with older firmware. I only tested QD4A.200805.003, but .001 would likely work as well. If you have a newer version, you will need to downgrade at least the bootloader and radio first. I recommend installing the QD4A.200805.003 firmware image from Google, as that's what I tested with.
The Derpfest build uses the newer firmware and I don't think it would be compatible. You could certainly try, though.
Click to expand...
Click to collapse
I'm no expert but my guess is that it won't work because the sideloaded versions, Dirty Unicorns, Derpfest, and Superior have the boot.img inside a payload.bin file so that recovery wouldn't recognize this. But then again, what do I know?
TheSayaMan said:
I'm no expert but my guess is that it won't work because the sideloaded versions, Dirty Unicorns, Derpfest, and Superior have the boot.img inside a payload.bin file so that recovery wouldn't recognize this. But then again, what do I know?
Click to expand...
Click to collapse
I can't install this. I keep getting a error that the device is corrupt and can't be trusted and may not work properly. Does not boot. Followed instruction to a T. Flashed to another rom. Also confirmed that flashing through du or twrp recovery does not work as I stated previously.
TheSayaMan said:
I can't install this. I keep getting a error that the device is corrupt and can't be trusted and may not work properly. Does not boot. Followed instruction to a T. Flashed to another rom. Also confirmed that flashing through du or twrp recovery does not work as I stated previously.
Click to expand...
Click to collapse
If this is what you're seeing, it typically means either the bootloader wasn't unlocked or verity was still enforcing. I am not sure how this could have broken considering I didn't take any special steps besides unlocking my bootloader before flashing the update image, and I even reflashed the phone to factory first before applying it and it still worked.
I added a MD5 of the zip image I flashed to the OP.
liamwhite said:
If this is what you're seeing, it typically means either the bootloader wasn't unlocked or verity was still enforcing. I am not sure how this could have broken considering I didn't take any special steps besides unlocking my bootloader before flashing the update image, and I even reflashed the phone to factory first before applying it and it still worked.
I added a MD5 of the zip image I flashed to the OP.
Click to expand...
Click to collapse
I'm sure it's not broken. Probably a issue with my phone. I'm getting a error in the bootloader about debug policy enabled, not in list. I know that's not normal because my wife has the same phone and hers doesn't say that. And I have no idea what or how to change verity. My bootloader is unlocked.
Same error here, getting corrupt error then it sticks to google logo
nixromancer said:
Same error here, getting corrupt error then it sticks to google logo
Click to expand...
Click to collapse
Yea this was tested on the tmobile brand. I'm assuming this does not work on the google store unlocked version. I give up.
TheSayaMan said:
Yea this was tested on the tmobile brand. I'm assuming this does not work on the google store unlocked version. I give up.
Click to expand...
Click to collapse
For what it's worth, I purchased my phone from the play store online. I didn't buy a T-Mobile branded version.
Board: sunfish MP1.0(NA)
Bootloader: s5-0.2-6539975
Baseband: g7150-00018-200701-B-6643937
Secure boot: PRODUCTION
NOS production: yes
liamwhite said:
For what it's worth, I purchased my phone from the play store online. I didn't buy a T-Mobile branded version.
Click to expand...
Click to collapse
any idea how to check if verity is enforcing and how to change it. Did a search, can't find anything.
Hmm, it seems like my bootloader was more up-to-date than I realized. The one I am running is actually the one from the RP1A factory image, not sure how/when it updated, because I definitely downgraded it first to get TWRP booting.
liamwhite said:
Hmm, it seems like my bootloader was more up-to-date than I realized. The one I am running is actually the one from the RP1A factory image, not sure how/when it updated, because I definitely downgraded it first to get TWRP booting.
Click to expand...
Click to collapse
Your going completly around what I asked. I'm done with this. Moving to another thread.
Stay away from this, it changes your file system to raw and is a complete waste of time.
I rebuilt my entire source tree, reflashed the Pixel system images and reproduced the corrupt device warning. Picking through the changes, it didn't work because I had inadvertently flashed vbmeta.img on my build but not included it in the zip. I've posted an updated version of the zip and provided new instructions for how to flash this, because Lineage's fastboot does not allow flashing the vbmeta partition (you have to first flash it from the bootloader).
I tested again with a clean wipe, reset to Pixel factory image QD4A.200805.003 and this time it worked without a problem. The android-info.txt will now ensure that you are using the right bootloader when flashing, so that issue should go away too.
Cool I'll give it a try tomorrow
TheSayaMan said:
Stay away from this, it changes your file system to raw and is a complete waste of time.
Click to expand...
Click to collapse
What does this mean
nixromancer said:
Cool I'll give it a try tomorrow
What does this mean
Click to expand...
Click to collapse
This doesn't work. That's what it means. If you want to waste about an hour of your life flashing this then having to flash back to stock or another custom rom than be my guest. This was posted by a new member, not a developer at all. I messed around with this quite awhile and no one is reporting success except the one that started this thread.
TheSayaMan said:
This doesn't work. That's what it means. If you want to waste about an hour of your life flashing this then having to flash back to stock or another custom rom than be my guest. This was posted by a new member, not a developer at all. I messed around with this quite awhile and no one is reporting success except the one that started this thread.
Click to expand...
Click to collapse
The fact that I messed up and didn't realize I had to include the vbmeta.img file in the first zip is my fault, and I totally own that. It isn't able to be flashed in Lineage's fastbootd ("file not found", presumably it's missing a devfs node) so I accidentally excluded it from the image I shipped, not realizing it was mandatory.
Yes, I'm new to this forum, but I'm not new to building Lineage and I've done it many times before. I have serial UARTs for my phones. I'm posting this build here because I'm excited to be the first to get stable lineage running on the 4a, with the full list of vendor blobs and such (see my posted device tree), and this is the first time I've ported Lineage to a new board. It took me a week of tiring work bootstrapping the board, getting the first serial output, getting into recovery, and then finally figuring out that the kernel modules were missing before getting a full boot.
I was annoyed that the flashable zip generated by mka bacon doesn't include the required modules, and in my testing applying it never worked (they were always excluded from the vendor parition, even after multiple makefile changes), which is why I decided to make an ad-hoc flash method using a fastboot update zip, which reliably worked. That was the primary source of the error here. I won't make that mistake again.
I know you're frustrated that the first image I provided didn't work, but I have looked into it, reproduced your issue, and fixed it (and it ironically was only missing one 4K file needed to make it work).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ArrowOS
ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : via the Matlog app included or check how to
DOWNLOADS
Here!
INSTALLATION
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and copy to your external sd card
Download/Install firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
Flash the ArrowOS zip
REBOOT TO RECOVERY!!
Reboot to system
Profit
*** Dont install Magisk until you have booted the ROM once
ROM Source: https://github.com/ArrowOS
Kernel Source: Stock Motorola Kernel
Device Source(s): https://github.com/omnirom/android_device_motorola_nairo
https://github.com/omnirom/android_device_motorola_dynamic_common
https://github.com/omnirom/android_device_motorola_sm7250_common
Vendor Source: https://github.com/DonkeyCoyote/proprietary_vendor_motorola
Many thanks to @vache for the above device/vendor trees, the flash tool, and building TWRP. The guy's a legend!
Reserved
Just in case..
Thank you to the developer! Finally someone showing the Nairo some love.
Definitely going to test this one…. !
There is also Omni-Rom available on telegram, built by vache, the twrp/device tree builder.
If you search moto g 5g plus official you should find the group.
I followed all steps but the rom won't flash error
Any advice ?
Love this ROM right from day 1!
Vache, will you add it to the ArrowOS website?
Will it have updates?
What about OTA, how can we enable it since TWRP does not allow so.
- Moto camera complain about updates
- As you know, Hey Google does not work
Thanks a lot
Wajdy
wajdyz said:
Love this ROM right from day 1!
Vache, will you add it to the ArrowOS website?
Will it have updates?
What about OTA, how can we enable it since TWRP does not allow so.
- Moto camera complain about updates
- As you know, Hey Google does not work
Thanks a lot
WajdyView attachment 5268655
Click to expand...
Click to collapse
Hey man, yeah there will be updates, more than likely monthly when the new security patch comes out, sooner if there's new features released. As for OTA updates, it won't happen as long as the builds are unofficial. But updating is no problem, just download and flash the update in twrp and reboot
Start of something big? I hope so
fawazed said:
Any advice ?
Click to expand...
Click to collapse
Were you able to resolve?
Got it to install. The essential part for me is -
Download/Install firmware with the latest version of Moto Flash Tool
After that flashing works like a charm. I will post more updates shortly.
Edit: Boot to system failed :-( with unable to open loop device. I tried it multiple times, all the steps from the start, but unfortunately same error. Does it matter if flash the Android 10 or 11?
I will attempt if I get the same error with omnirom.
peacemaker885 said:
Got it to install. The essential part for me is -
Download/Install firmware with the latest version of Moto Flash Tool
After that flashing works like a charm. I will post more updates shortly.
Edit: Boot to system failed :-( with unable to open loop device. I tried it multiple times, all the steps from the start, but unfortunately same error. Does it matter if flash the Android 10 or 11?
I will attempt if I get the same error with omnirom.
Click to expand...
Click to collapse
are you definitely rebooting to recovery after flashing the zip?
and are you formatting data, not just wiping?
Beetle84 said:
are you definitely rebooting to recovery after flashing the zip?
and are you formatting data, not just wiping?
Click to expand...
Click to collapse
Thanks so much for following up. I realized that when I was using the Moto Flash Tool, I was ending it too early. I rebooted the phone after the first "completed" and missed the second phase where it prepares slot b. I truly appreciate your efforts and now running ArrowOS on the Moto G 5G Plus. Thanks so much!
Nice rom do I got brightness issues do I need a logcat for that I will get it later today
wesleyvanneck12345678 said:
Nice rom do I got brightness issues do I need a logcat for that I will get it later today
Click to expand...
Click to collapse
Hey mate, what is the issue exactly?
Hey o.p hope all is well,.
Will this rom work on the 5GAce Kiev version.?
jhjhjhjhjhjh said:
Hey o.p hope all is well,.
Will this rom work on the 5GAce Kiev version.?
Click to expand...
Click to collapse
No I wouldn't think so, but you guys should have something soon, I'm pretty sure one of the LOS devs for g7 power, among other devices, has your phone
Any update of this rom maby the latest security patch
Yeah mate, sorry. Been busy at the moment. The April patch was done a while ago, I forgot to update the OP. I will have it fixed by the end of the day. Then expect the May one in a week or so
Evolution X 6.6 for the Motorola One Fusion+ [liber]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Living, Breaking, Keep Evolving.
Pixel UI, customization and more, we are Evolution X!
- Team Evolution X -
@joeyhuab (Founder/Lead Developer)
@peaktogoo (Project Manager/Co-Founder)
@AnierinB (Project Specialist/Co-Founder)
Reach us on Twitter! @EvolutionXROM
Check out our website!
Just flash and check "The Evolver". We have tons of features combined together from different ROMs.
Dual Volte wont work (Any one slot supports Volte)
DO NOT FLASH GAPPS, ALREADY INCLUDED
First Time Install / Clean Flash
1. Make sure you have stock recovery
2. Go to fastboot (bootloader)
3.Download the tool included so as to install the rom much easier
4.Unzip the tool and read the instructions
5.Follow it properly
6.It will Reboot to System and #KeepEvolving
Update / Dirty Flash
1. Same procedure as above, use the dirty flash bat file instead
KEEP IN MIND THERE IS ALSO OTA UPDATES!
Android version: 12.1.0_r12
Security patch level: August 2022
Build author: Manidweep
Kernel Source: https://github.com/sm6150-liber/kernel_motorola_sm6150
ROM Developer: joeyhuab
Source code: https://github.com/Evolution-X
Do banking apps work without magisk ?
Version without gapps? Thanks
Sid_DiCaprio said:
Do banking apps work without magisk ?
Click to expand...
Click to collapse
yes
Is this compatible with the XT2067-2 variant?
Fp not working
System update - veryfication failed over ota. Installs via fastboot but phone do not show when somone calls only ringtone plays but nothing on the screen. New version broken?
Sid_DiCaprio said:
Do banking apps work without magisk ?
Click to expand...
Click to collapse
Yes
After using all available rom for motorola one fusion plus I can say that this rom is more stable and can use as daily driver.
Everything working fine.. Only one problem is widevine decrease to l3... And i think its bacoz of bootloader unlock.
Banking app and UPI aap working fine.. Without magisk.. Root.
But i root my device and by just hide root all app works fine.. Bt in new canary update of magisk which remove many features....ie magisk hide. And module section.. Now cts failed with root.. But u can fix by enabling zygisk and it will work fine..
Only sbi yono don't work with root... Bt yono lite is working fine..
All thanks to developers.
I really liked the ROM, but unfortunately the fingerprint doesn't work on it, I don't know if I did something wrong when installing the ROM, but anyway... I had to go back to Stock ROM, I will wait the factory att to Android 11, is better...
Fingerprint doesnt work for me, and heating a little
Fingerprint not working for me either
jirka108 said:
Version without gapps? Thanks
Click to expand...
Click to collapse
not possible
evox comes with gapps default
there is no vanilla
mschwemberger11 said:
Fingerprint not working for me either
Click to expand...
Click to collapse
use latest
fixed
I followed all the instructions precisely but it failed, stuck at bootloader, I got many errors during flashing, don't know how to fix it now
Marian_Popescu said:
I followed all the instructions precisely but it failed, stuck at bootloader, I got many errors during flashing, don't know how to fix it now
Click to expand...
Click to collapse
I too faced the same issue. In bootloader mode ROM got flashed but with errors. Then it go to Fastbootd and system keeps showing waiting for device. It got struck. I then had to flash stock ROM via lmsa to proceed.
EDIT : This was happening because drivers were not updated on my PC running Win 11. For that I had to connect my phone in bootloader mode to PC. Just went to optional updates. There I installed 2 optional updates one named Qualcomm and the another one named Android ADB, Try again your phone will boot up in this Custom ROM
Gill Android said:
I too faced the same issue. In bootloader mode ROM got flashed but with errors. Then it go to Fastbootd and system keeps showing waiting for device. It got struck. I then had to flash stock ROM via lmsa to proceed.
EDIT : This was happening because drivers were not updated on my PC running Win 11. For that I had to connect my phone in bootloader mode to PC. Just went to optional updates. There I installed 2 optional updates one named Qualcomm and the another one named Android ADB, Try again your phone will boot up in this Custom ROM
Click to expand...
Click to collapse
thank you very much for this tip, much appreciated, the usb drivers were the culprit indeed
problem solved now, thanks!
Hey ich habe mir verschiedene Roms runtergeladen es fehlt immer die Datei payload.bin
mache ich was falsch?
soll fehlt heißen!
Mod translation via GT:
Hey, I've downloaded different ROMs and the payload.bin file is always missing
am I doing something wrong?
should mean missing!
I have a XT2067-3 (running Stock Android 11 - RPIS31.Q2-42-25-1) and have never installed a Custom ROM on it or rooted this device before. I followed Motorola's website instructions to unlock the bootloader using the key provided by them via email.
After that, I successfully flashed the ROM (after a few errors, I had to install the Google USB drivers as well, apart from the Motorola Drivers). When the phone rebooted into fastbootd, my Windows (10) would not recognize the phone. Installing the Google USB drivers through Device Manager worked immediately, incase anyone else runs into this error.
My main question is, can I flash a Custom Recovery (like TWRP) after flashing this ROM?
advaithk said:
I have a XT2067-3 (running Stock Android 11 - RPIS31.Q2-42-25-1) and have never installed a Custom ROM on it or rooted this device before. I followed Motorola's website instructions to unlock the bootloader using the key provided by them via email.
After that, I successfully flashed the ROM (after a few errors, I had to install the Google USB drivers as well, apart from the Motorola Drivers). When the phone rebooted into fastbootd, my Windows (10) would not recognize the phone. Installing the Google USB drivers through Device Manager worked immediately, incase anyone else runs into this error.
My main question is, can I flash a Custom Recovery (like TWRP) after flashing this ROM?
Click to expand...
Click to collapse
I flashed twrp and it's not working ..... The ota updates are not installing as well ( I guess ota updates require a recovery )
I did install another recovery and it's still not working so I manually flashed the update .....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/13.0/README.mkdn
Flashing Instructions:
Pre-installation:
OOS 12 H.38 firmware is mandatory (can update via firmware update tool found on download page, firmware button)
Download recovery (from download page, recovery button)
Optional NikGapps core (download - note that you may also need setup wizard addon if you rely on Google restore)
Optional Magisk (boot.img used to patch with Magisk in order to get root, can be found in recovery folder from download page)
First time installation (clean flash):
Backup your data to PC, OTG flash drive
Make sure you have OOS 12 firmware installed (if used firmware flash tool from download page, proceed straight to install crDroid.zip)
Enter fastboot
Flash our boot.img in fastboot
Code:
fastboot flash boot boot.img
Boot to recovery (can do from bootloader or with buttons from power off state)
Now in recovery go to factory reset and confirm the reset
Reboot to recovery
Choose apply update and Apply from ADB
Now install crDroid zip via sideload
Code:
adb sideload crDroid.zip
Go back to main menu and reboot to recovery to install gapps (if you don't want gapps, reboot to system)
To install gapps, simply reboot to recovery again and sideload gapps.zip the same way you installed crDroid.zip then reboot to system
Update installation:
Via recovery (recommended way):
Boot to recovery
Choose apply update and Apply from ADB
Now install crDroid zip via sideload and reboot
Code:
adb sideload crDroid.zip
If you had gapps, reboot to recovery and sideload gapps.zip and reboot
Via OTA:
Go to Settings -> System -> Updater and download latest build
Choose install and let it finish
If you have Magisk installed, don't click reboot when prompted and go to Magisk and choose install to inactive slot
Reboot
Note: In some cases where incompatible gapps used, may result in boot issues that should get fixed by flashing gapps again in recovery.
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sm8150
Download:
ROM https://crdroid.net/guacamole/9
Visit official website @ crDroid.net
crDroid OnePlus 7 Pro Telegram
crDroid Community Telegram
If you like my work, consider a donation > My Paypal
Hi dev, your rom title date is wrong we still in october . Anyway thanks for the rom. Is there any specific oneplus settings available in this rom?.
yakuzax1 said:
Hi dev, your rom title date is wrong we still in october . Anyway thanks for the rom. Is there any specific oneplus settings available in this rom?.
Click to expand...
Click to collapse
hehe
yeah... sorry about that )
@gwolfu Thanks for the first 13 build.
Is EROFS planned in the future? just curious.
Toutatis_ said:
@gwolfu Thanks for the first 13 build.
Is EROFS planned in the future? just curious.
Click to expand...
Click to collapse
not really
last I tried, had issues with gapps with it
For those not willing to go through the hassle to install OOS 12 on both slots just to update firmware before installing crDroid, I've made a "firmware flash tool" available on download page
Just boot to bootloader and run Update-firmware.sh (linux) or Update-firmware.bat (windows)
Can I upgrade to firmware 12 directly over OOS 9? Or do I need to upgrade over firmware 11?
Solved
gwolfu said:
For those not willing to go through the hassle to install OOS 12 on both slots just to update firmware before installing crDroid, I've made a "firmware flash tool" available on download page
Just boot to bootloader and run Update-firmware.sh (linux) or Update-firmware.bat (windows)
Click to expand...
Click to collapse
Hello Dev, thanks for a new support for android 13. To be root through magisk, is it done as in crdroid v8? that is, is the boot patched with magisk and flashed with fastboot?
gwolfu said:
For those not willing to go through the hassle to install OOS 12 on both slots just to update firmware before installing crDroid, I've made a "firmware flash tool" available on download page
Just boot to bootloader and run Update-firmware.sh (linux) or Update-firmware.bat (windows)
Click to expand...
Click to collapse
Wow that is awesome I was going to ask for clarification on that (if OOS 12 beta was indeed required or if it was a typo). And it seems it really is required but you made it super easy instead of needing to flash the full OOS 12.
MUCH thanks and appreciation for bringing us CRDROID 13 along with an easy to use flash tool for OOS 12 firmware. Been waiting for A13 of crdroid, crdroid being the best with features and stability. + a great dev to boot
Are you talking about the OOS12 H.31 gloabal beta? Either way, the firmware tool does the job and makes it easy.
Also, will features like smart pixels eventually be on A13 like in A12? nvm seems like all features are still here after dirty flash and firmware change. Switched to big fingerprint now, but it's miscentered like in the pic.
Well flashed the firmware update and the new build, everything went smooth. Nice!
I have a few bullet points:
--After flashing the firmware tool, the stupid "warning" that the bootloader is unlocked is now gone that is awesome. I've wanted that gone since I unlocked but I read it's dangerous to mess with...so I did not plan on that happening but love it
--Seems all crDroid settings from A12 are here and maybe a few extra. Sweet! I was thinking there may be a few things missing because it's a new base but nope, think it's all here.
--The "taskbar" for the crDroid launcher? Super amazing! Not sure if that was there on the previous A12 builds? I've been on Nova Launcher for years now so I'm not sure if this is new to the A13 build. But I absolutely love the taskbar idea (everything still works the same, swipe up for home, swipe up far for recents and drag left-right on taskbar for previous app). I'll attach a pic for those wondering incase it's new.
--Speaking of the launcher, is there any topic/place where we can talk about it? Request features, ask things? Like I'd like to request being able to hide drawer icons/apps and be able to put them into folders (in the app drawer). Also any way to back it up? Like the settings and placement of icons? Using nova and having a backup/restore makes it easy to clean flash ROMs and be right back to normal after. But I think I'd like to stick to crDroid launcher because of this taskbar feature - it's so handy!
--I notice the "Smooth Display" (going from 60Hz to 90Hz) works properly in this ROM. That is nice for people that want to save battery (if you don't want that half second delay from the change-over, in dev-tools it can be still forced to 90Hz all the time).
--Not a big deal but I think I notice the status bar icons very high up, almost touching the top bezel. The OCD in me says arrgg lol. WHY does google mess with the dang paddings on these things...
Those are the few things I've noticed so far. A very nice "initial" release! Seems really smooth too! Thanks again @gwolfu
I am having problems with the back gestures on the screen, anyone else having this problem?
Will wait for feedback regarding the Qualcomm crash dump issue many users and I had on v8 before flashing. Hopefully it's gone for good...
Toutatis_ said:
Will wait for feedback regarding the Qualcomm crash dump issue many users and I had on v8 before flashing. Hopefully it's gone for good...
Click to expand...
Click to collapse
That is not ROM related. That is firmware related.
I only had that happen to me once in the past 6 months (and I've tried every ROM possible during that time), I updated my firmware and never had it again on any ROM. So, updating the firmware here (to OOS 12 as instructed) you should be good to go.
If you still don't want to take the chance, I'd recommend sticking with stock OOS for full stability. These ROMs are basically always beta as it's cutting-edge and you'd have to deal with bugs/testing.
SLAlmeida said:
I am having problems with the back gestures on the screen, anyone else having this problem?
Click to expand...
Click to collapse
Like swiping back? Nope all working good here. I've had no bugs yet. Except 'maybe' slight lag in a game while auto brightness was on (I turned it off and there is now 0 lag).
theslam08 said:
That is not ROM related. That is firmware related.
Click to expand...
Click to collapse
I've always flashed latest OOS version available to both slot prior to flashing any crDroid v8 build, but always had the Qualcomm dump crash at some point regardless.
theslam08 said:
I only had that happen to me once in the past 6 months (and I've tried every ROM possible during that time)
Click to expand...
Click to collapse
I used quite a lot of A12 ROMs too (YAAP, KOSP, Bliss, PixelExperience, Project Elixir, EvolutionX, DerpFest) and only had this issue with crDroid.
theslam08 said:
So, updating the firmware here (to OOS 12 as instructed) you should be good to go.
Click to expand...
Click to collapse
Hopefully, I'll try v9 eventually and see how it goes.
gwolfu said:
For those not willing to go through the hassle to install OOS 12 on both slots just to update firmware before installing crDroid, I've made a "firmware flash tool" available on download page
Just boot to bootloader and run Update-firmware.sh (linux) or Update-firmware.bat (windows)
Click to expand...
Click to collapse
keeps "waiting for devices" at fastbootd mode, doesn't detect my device
Whatever it did prior to this stage killed the system and now I have to msm back to oos11 manually...
theslam08 said:
Like swiping back? Nope all working good here. I've had no bugs yet. Except 'maybe' slight lag in a game while auto brightness was on (I turned it off and there is now 0 lag).
Click to expand...
Click to collapse
Yes, but when I enable the bottom navigation bar in in the crDroid settings, it works again.
I just can't use the on-screen gestures without enabling the navigation bar, and one thing has nothing to do with another.
does this rom have a problem with screen wake up/fod with ambient display on? or is that stable on this one
also, anyone who used evolution x (a13), how does the battery life compare?
Toutatis_ said:
I've always flashed latest OOS version available to both slot prior to flashing any crDroid v8 build, but always had the Qualcomm dump crash at some point regardless.
I used quite a lot of A12 ROMs too (YAAP, KOSP, Bliss, PixelExperience, Project Elixir, EvolutionX, DerpFest) and only had this issue with crDroid.
Hopefully, I'll try v9 eventually and see how it goes.
Click to expand...
Click to collapse
Hm yeah I'm not sure then. Something weird going on there - I've personally never had any crash dumps on this ROM (it was on FlamingoOS) and rarely see anyone say they're having crash dumps on it either. The few times I have, they were told to update the firmware which they supposedly did and didn't have any problems after.
Your best bet if possible would be to get a log of it when it happens: https://pastebin.com/GGaRZ2nJ