Development [CLOSED] [ROM][14.0_r25][OFFICIAL] Evolution X 8.3 [03/05/2024]
- Thread starter AnierinB
- Start date
- Status
Yes, that definitely is an issue but happened intermittently to me. With A to C I never had any complications and that is the preferred way AFAIK.
lil_michelle
Senior Member
installing now on linux mint. I think its worth noting to not use the adb and fastboot available on the ubuntu repo's because it is way out of date. Just download Platform tool and extract, open the folder and place rom zip in it and right click and open in CLI
For root download magisk manager and change file name from APK to ZIP and flash via ADB sideload command in the Evolution recovery. I managed with USB C to C. Obviously you wipe data first before istalling rom OTA and place rom zip in platform tools folder, it is common procedure.
For root download magisk manager and change file name from APK to ZIP and flash via ADB sideload command in the Evolution recovery. I managed with USB C to C. Obviously you wipe data first before istalling rom OTA and place rom zip in platform tools folder, it is common procedure.
Last edited:
Are all the Pixel goodies working? Like call screening, "Now playing" on lockscreen, Google camera, etc.
And do bank apps work fine as well?
I'd love to use this ROM if that's the case
And do bank apps work fine as well?
I'd love to use this ROM if that's the case
Last edited:
If now playing is the only thing not working atm that's fine then.
The one I would really need is call screening, so hopefully that one is included.
The one I would really need is call screening, so hopefully that one is included.
Call Screening Not ready to say, I have a spam block at the level of the organization providing communication (my operator).
SIM card from the organization
Now Playing is working fine for me on the Pixel 6a, I followed the install instructions. Note: I am not rooted and have L1 widevine and SafetyNet passing (have not tried to use Magisk yet). Finishing setup and will swap my SIM in later today.
Attachments
Forgot about this method TBH... But I only root to flash custom kernels, a s you have to be on stock boot.img for that
kpirnie
Recognized Contributor
So far so good on Raven. Was even able to pull the boot.img from the payload.bin
Now my issues will be my own
Now my issues will be my own
kpirnie
Recognized Contributor
bummer... soft-bricked by flashing Kiri kernel
only rooted EvoX boot.img (after pulling from payload), so that may have something to do with it
only rooted EvoX boot.img (after pulling from payload), so that may have something to do with it
You likely have to flash the stock patched kernel, then the custom kernel.bummer... soft-bricked by flashing Kiri kernel
only rooted EvoX boot.img (after pulling from payload), so that may have something to do with it
kpirnie
Recognized Contributor
aye... that's what I've been seeing in the thread, if I need it bad enough I can do that...but, really I only use Kiri for the 1080 tweak
came across one more "gotcha"... looks like Project Themer isn't compatible
kpirnie
Recognized Contributor
Are you even rooted?
You need magisk, zygisk on and lsposed zygisk for it to even function
Attachments
kpirnie
Recognized Contributor
Of course I am. Please by all means PM me, this is OT.
I posted it because it should be mentioned, and not discussed.
Don't see how it's ot when it's about the ROM and I'm the one responding to questions regarding it, but whatever floats your boat.
kpirnie
Recognized Contributor
didn't realize this was your thread lol. Yeah, it's probably not a rom issue.
I'm sifting through a logcat now...
- Status
Top Liked Posts
-
There are no posts matching your filters.
-
54
Google Pixel 6, 6 Pro & 6a
[oriole][raven][bluejay]
Pixel UI, customization and more, we are Evolution X!
Joey Huab - Founder/Lead Developer
Anierin Bliss - Co-Founder/Project Specialist
Akito Mizukito - Co-Founder/Project Manager
Reach us on Twitter! @EvolutionXROM
Check out our website!
Added features
DO NOT FLASH GAPPS, THEY ARE ALREADY INCLUDED
First Time Install
(Note: These releases include firmware)
1. Download boot, dtbo, vendor_boot & rom for your device from here
2. Reboot to bootloader
3. fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot reboot recovery
4. While in recovery, navigate to Factory reset -> Format data/factory reset and confirm to format the device.
5. When done formatting, go back to the main menu and then navigate to Apply update -> Apply from ADB
6. adb sideload rom.zip (replace "rom" with actual filename)
7 (optional). Reboot to recovery (fully) to sideload any add-ons (e.g magisk)
8. Reboot to system & #KeepEvolving
Update
1. Reboot to recovery
2. While in recovery, navigate to Apply update -> Apply from ADB
3. adb sideload rom.zip (replace "rom" with actual filename)
4 (optional). Reboot to recovery to sideload any add-ons (e.g magisk)
5. Reboot to system & #KeepEvolving
OTA
1. Check for update. If available, select "Download and install" (approx 10-15 min)
2. Reboot & #KeepEvolving
Android version: 14.0_r25 Security patch level: February 2024 Build author: Anierin Bliss Kernel Source: https://github.com/Evolution-X-Devices/kernel_google_gs201 Clang version: 14.0.7 ROM Developer: Joey Huab Source code: https://github.com/Evolution-X 26Latest releases
Simply install the updated apk, reboot and clear data for Play store. Afterwards, CTS/Play integrity API will pass again. Root is not required.
(Until this one stops working. In which case, check back here for an updated date and repeat as instructed above. This is not needed if the date above is lower than the date of the latest ROM zip)
(If you root with magisk, you will need to enable magisk hide/force deny list and hide magisk from gms & gms unstable.)
rom:
boot:
dtbo:
vendor_boot:
rom:
boot:
dtbo:
vendor_boot:
rom:
boot:
dtbo:
vendor_boot:
21
Commonly asked questions & answers
Q: Why am I getting "error cannot read" while attempting to sideload the ROM or are unable to fastboot flash vendor_boot
Well, you should be using the latest platform-tools and have it added to PATH. A lot of unofficial drivers floating around on the internet install outdated adb/fastboot along with the drivers. Please refrain from installing these as well as minimal adb & fastboot; Use the official google driver and official platform-tools instead.
Alternatively you can prefix each adb/fastboot cmd with./while in the platform-tools folder via powershell or bash, etc.
For example:
./adb sideload ./rom.zip
This basically tells the shell "Hey, I want to execute this local binary rather than the one in PATH".
Q: I'm a windows user and my device is not being listed when I runadb/fastboot devices. I'm using the latest platform-tools, what could be the reason for this?
Use the official Google USB driver
Q: I'm a linux user and my device is not being listed when I runadb/fastboot devices. I'm using the latest platform-tools, what could be the reason for this?
Q: Will you release builds in the update.zip format?
No, we will not be releasing builds in that format due to a handful of reasons; The main reason being that it is not able to be installed via OTA and is incompatible with our official devices infrastructure.
Don't see your question? Well, feel free to post a comment in this thread, we will reply as soon as we can. We'd appreciate if users used XDA FIRST and the discord group as a LAST RESORT.
Custom Kernels
Custom kernels may be flashed at YOUR OWN RISK. However, we will not provide extended support regarding such and it is up to YOU, the end user to make your reports in the appropriate thread for X kernel, not in this thread.
Obtaining root
Let it be known that we will not assist anyone with bug reports until they have disabled all modules and restored to the default, unpatched kernel that is shipped with the ROM!
Root can be obtained by either one of the following methods.
1. Download the Magisk.apk on your pc (you can change the file extension to .zip if you wish, though it is not required.
2. Reboot to recovery.
3. Navigate to Apply update -> Apply from ADB.
4. adb sideload magisk.apk (replace "magisk" with actual filename).1. Download the full rom.zip from post #2 of this thread.
2. Download payload-dumper-go that corresponds to the architecture of your pc.
3. Run payload-dumper-go against the rom.zip.
4. Grab boot.img from the extracted folder and transfer it to your device.
5. Patch boot.img with the magisk application and transfer the patched image to your pc.
6. Reboot to bootloader.
7. fastboot flash boot boot.img (replace "boot.img" with actual filename).
When an OTA update is available, let it download and install. Before rebooting simply open Magisk Manager and click on the first "install" button and select "install to inactive slot". Once it's done, reboot and enjoy.
Reporting bugs and submitting logs
In most cases logs should be provided when reporting bugs. This can be done by enabling USB debugging in developer options of the device, connecting it to your PC and running one of the following cmds depending on the type of bug/issue while reproducing it:
General system log
adb logcat > logcat.txt
Kernel log
adb shell su -c dmesg > dmesg.log
Please provide a detailed description of the bug/issue as well as link/upload the log you had taken.
There are exceptions to this as some issues are unable to be caught in logs. In this case, it is expected that users provide clear and accurate steps to reproduce the issue.
Getting involved in the development
Build guide:
Compiling Evolution X 8.x for currently supported tensor-based Google Pixel devices
Compiling Evolution X 8.x for currently...
gist.github.com
Device and ROM source changes can be submitted on github to the appropriate repositories by making pull requests via comparing forks. Please follow the google patch format for commits and triple check your changes by compile testing and verifying they're correct. Please retain proper authorship if you are not the author!
10February patch builds for Oriole, Raven and bluejay now available via OTA
#KeepEvolving10WOW, I just read through this entire forum thread, every page, word for word (to get up to speed with my PX6Pro) before I flashed it. I did this so I don't have to come here and re-ask the same damn question (a 100th time), instead I RESEARCH it prior!
I have to say, I am always amazed to see how many greedy, selfish, and unthankful people there are in this world. Us DEVS do this on our OWN time, yet some of you think we OWE it to you. We waste our time to deliver custom ROMs, apps, scripts, ETC., to users with asking for ANYTHING in return. This time could be better spent with our families, or work, or having fun, so NO, we don't owe you a damn thing! This post isn't pointed to any one person, so no one take offense per se, BUT COME, show a little gratitude, or thanks, instead of all the pointless BS! WE need to be kissing the devs butts, to have them continue to bake the ROMs for us. I won't do it anymore, I gave up years ago, after baking ROMs since ICS, but I could NOT HANDLE the attitudes of the users. The demands, demands, demands, with little to no thanks, and getting back NOTHING but grief, so please be careful. If we lose this dev, we won't have this ROM anymore. I am just asking users to wake up and be polite, use a little common courtesy, do some research PRIOR to asking, and do NOT demand, but be thankful!
THANK YOU AnierinB, I APPRECIATE your time!!! This ROM is amazing!!!
