Related
Hi,
{
"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"
}
DarkJoker360 AOSP 10 for Huawei P10 Lite
*** Stable Version ***
About
Code:
[CENTER]Android is an open source software stack for mobile devices and a corresponding open source project led by Google. This site and the Android Open Source Project (AOSP) repository offer the information and source code needed to create custom variants of the Android stack, port devices and accessories to the Android platform, and ensure devices meet the compatibility requirements that keep the Android ecosystem a healthy and stable environment for millions of users.
This rom has been edited by DarkJoker360 with some additions such as:
* Pixel UI
* Theme picker
* Fruity pebble v2.0
* AospExtended's material icons
* Google bootanimation
[/CENTER]
Working
Code:
[CENTER]* Touchscreen
* Adb / Mtp
* Audio
* Boot
* Bluethoot
* Internal/External storage
* Sensors
* Wifi
* RIL
* Camera
* Android 10 gestures
* NFC
* FP gestures
[/CENTER]
Not Working
Code:
[CENTER]* Offline charge (It works by switching to permissive selinux)
[/CENTER]
Installation
Code:
[CENTER]* you must also have this recovery version installed : [URL="https://forum.xda-developers.com/p10-lite/development/recovery-twrp-huawei-p10-lite-t3953890"]TWRP[/URL]
* go to TWRP and do a full wipe (system, data, cache, dalvik/art cache) !
* reboot to bootloader
* extract AOSP 10 zip
* run: fastboot flash system <drag system.img here>
* reboot to TWRP
* flash root(optional)
NOTE: If you are coming from Android 9 flashing root is a MUST DO !
NOTE2: Flash only the Magisk zip linked in this post !
* reboot to System
* reboot to TWRP
* flash gapps (optional)
* reboot to System
* reboot to TWRP
* flash patch_r2.zip
NOTE: this zip is needed for having working NFC and overlays. DO NOT IGNORE IT !
* reboot system
* Enjoy !!![/CENTER]
Update
Code:
[CENTER]* extract the new update of AOSP
* reboot device to : TWRP
* wipe cache & dalvik cache
* reboot to bootloader
* run: fastboot flash system <drag system.img here>
* reboot to TWRP
* install gapps(optional)
* reboot to System
* reboot to TWRP
* install patch_r2.zip
* NOTE: this zip is needed for having a working NFC and overlays. DO NOT IGNORE IT !
* reboot to System
* Enjoy !!![/CENTER]
Download
Code:
[CENTER][URL="https://sourceforge.net/projects/darkjoker360-developements/files/Huawei/P10%20Lite/Android-10/"]DarkJoker360 AOSP 10 and patch_r2 fix[/URL]
[URL="https://opengapps.org/"]Gapps[/URL]
[URL="https://forum.xda-developers.com/attachment.php?attachmentid=4882825&d=1574332554"]Magisk Phh v19.3[/URL][/CENTER]
Credits:
@phhusson
@flex1911
@haky 86
@Dil3mm4
@Hami_Do
Please support my work, it's very important! Thanks
DONATIONS
Regards !
XDA:DevDB Information
Android Open Source Project, ROM for the Huawei P10 Lite
Contributors
DarkJoker360
Source Code: [url]http://github.com/DarkJoker360[/URL]
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui 8.x,bootloader unlocked and TWRP
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 10
Stable Release Date: 2019-11-24
Created 2019-11-24
Last Updated 2020-01-02
FAQ.
Gapps
The recommend package at the moment is this:OpenGapps_arm64-BETA
* Flash this after first boot(with patch zip flashed) and ignore Setup Wizard errors
* Open Play Store and Log in
If you get some errors about Play Services make sure it has full permissions.
Aosp has "ugly" ui
I am sorry for giving you AOSP, hi6250 sources aren't good for other rom actually. As soon as I am able to fix these issues with other custom roms I will provide them, otherwise I will customize it starting from next build by bringing pixel styles and new apps with recent ui look.
NOTE: while inatalling gapps you can may face error 70 insufficient space error, just resize system and if the problem persist flash pico gapps !
Thanks for developer
I'm testing it right now. Flashing runs flawless. Rom runs well so far. ... More later.
First of all, I'm glad that I can use a pure aosp on this phone now. It can be used as daily driver. A cool thing is that I only needed to set device fingerprint to p8lite in magiskhideprops to fully pass safetynet. now it only needs nfc working, but I guess we need to wait for phh and his updates for now.
Two things I recognized pretty fast are GPS needs little help to get a fix, first fix needed nearly 4 minutes but then it gets fast fix but always with support (used gpstest from f-droid store) and downloads via wifi are generally (quite) slow.
Also I can't copy stuff from intern to ext sdcard.
This is not a real "bug report" as it is possible that I did something wrong, you'll never know. Just talking and see if anyone has the same issues. Cheers
Added new gapps and steps for their installation in OP and 2nd post.
NeoPreacher said:
I'm testing it right now. Flashing runs flawless. Rom runs well so far. ... More later.
First of all, I'm glad that I can use a pure aosp on this phone now. It can be used as daily driver. A cool thing is that I only needed to set device fingerprint to p8lite in magiskhideprops to fully pass safetynet. now it only needs nfc working, but I guess we need to wait for phh and his updates for now.
Two things I recognized pretty fast are GPS needs little help to get a fix, first fix needed nearly 4 minutes but then it gets fast fix but always with support (used gpstest from f-droid store) and downloads via wifi are generally (quite) slow.
Also I can't copy stuff from intern to ext sdcard.
This is not a real "bug report" as it is possible that I did something wrong, you'll never know. Just talking and see if anyone has the same issues. Cheers
Click to expand...
Click to collapse
Thanks for reviewing, I forget to include GPS stuff, in next build it will be fixed !
Nfc is almost fixed, we got it enabling at the moment.
For sd card I will take a look.
Here's a working fix to get nfc option (but no tile): https://forum.xda-developers.com/showpost.php?p=81021365&postcount=26
Q looks promising for our chipsets.
I am working on to include everything in the system.img without using another zip. Do you want gapps included too?
For this time i preferred to use .img instead of a .zip format because most of TWRPs have some flashing issues. Do you want back the zip or no? I prefer no tbh, dunno about you. Let me know
DarkJoker360 said:
I am working on to include everything in the system.img without using another zip. Do you want gapps included too?
For this time i preferred to use .img instead of a .zip format because most of TWRPs have some flashing issues. Do you want back the zip or no? I prefer no tbh, dunno about you. Let me know
Click to expand...
Click to collapse
It is a good decision to leave it as system.img, you mentioned it already, no flashing issues. Included gapps would shorten the flashing procedure a little, so I would also prefer this too.
PS: i just shared the fix to simply spread the ongoing progresses a little more. A working Q build that's now passing safetynet easily and already has working nfc (temporary with fix). That's huge progress. I'm really excited of what comes up the next weeks (not to hurry )
NeoPreacher said:
It is a good decision to leave it as system.img, you mentioned it already, no flashing issues. Included gapps would shorten the flashing procedure a little, so I would also prefer this too.
PS: i just shared the fix to simply spread the ongoing progresses a little more. A working Q build that's now passing safetynet easily and already has working nfc (temporary with fix). That's huge progress. I'm really excited of what comes up the next weeks (not to hurry )
Click to expand...
Click to collapse
Thanks so much for beliving in me, cool stuff is coming really soon. Including a newer decent ui
Great work. .. waiting for new release.
Finally oreo vendor is getting some love and a taste of android 10... Please keep up the good work man... And thank you
Does ''offline charge not working'' mean that we aren't able to charge the phone while it is turned off or when it is locked?
I installed this ROM on my Mate 10 Lite. Works awesome but i cant get GApps working from the 2nd Post. I didnt get the Option to enter the Email and Password. Settings already set. Any Ideas ?
ghassan haddad said:
Does ''offline charge not working'' mean that we aren't able to charge the phone while it is turned off or when it is locked?
Click to expand...
Click to collapse
When it's turned off it won't charge, your phone will instead completely boot up.
---------- Post added at 12:12 PM ---------- Previous post was at 12:11 PM ----------
Copkiller2010 said:
I installed this ROM on my Mate 10 Lite. Works awesome but i cant get GApps working from the 2nd Post. I didnt get the Option to enter the Email and Password. Settings already set. Any Ideas ?
Click to expand...
Click to collapse
Tried a factory reset from twrp?
NeoPreacher said:
When it's turned off it won't charge, your phone will instead completely boot up.
---------- Post added at 12:12 PM ---------- Previous post was at 12:11 PM ----------
Tried a factory reset from twrp?
Click to expand...
Click to collapse
I have a question, the charge of 9watts are working?
Hey,
I own a Huawei P10 Lite (WAS-LX1A, non-rebranded), and I followed your steps, using Askuccio's TWRP v1.0. I got it up and running, and I installed Magisk and the Android Patch, however, when I was figuring what worked and what didn't work, I took a screenshot and it said it couldn't due to storage issues, or something like that, which raised a red flag, and made me go and check how the file manager reported space, and sure enough it was reporting the +-32GB the phone had, however it was encrypted, which justified the storage issues. I did forget the GApps, which I'll install shortly to see if that was the problem. I also suspect that it can be related to the fact that I set the PIN without having used it to log in, so I'll reboot and test that out.
EDIT: Rebooted the device, entered pin, data is still encrypted
FranckTheMiner said:
Hey,
I own a Huawei P10 Lite (WAS-LX1A, non-rebranded), and I followed your steps, using Askuccio's TWRP v1.0. I got it up and running, and I installed Magisk and the Android Patch, however, when I was figuring what worked and what didn't work, I took a screenshot and it said it couldn't due to storage issues, or something like that, which raised a red flag, and made me go and check how the file manager reported space, and sure enough it was reporting the +-32GB the phone had, however it was encrypted, which justified the storage issues. I did forget the GApps, which I'll install shortly to see if that was the problem. I also suspect that it can be related to the fact that I set the PIN without having used it to log in, so I'll reboot and test that out.
EDIT: Rebooted the device, entered pin, data is still encrypted
Click to expand...
Click to collapse
Same, add to that inability to sign in to Google Services. Were you able to sign in?
ghassan haddad said:
Same, add to that inability to sign in to Google Services. Were you able to sign in?
Click to expand...
Click to collapse
I did get to that point, however I noticed on the 9.0 ROM the internal/external storage is featured as a working feature, so @DarkJoker360 it would be pretty helpful to new users to state that the internal storage isn't working, while the external does
FranckTheMiner said:
I did get to that point, however I noticed on the 9.0 ROM the internal/external storage is featured as a working feature, so @DarkJoker360 it would be pretty helpful to new users to state that the internal storage isn't working, while the external does
Click to expand...
Click to collapse
The internal storage is working good !
{
"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"
}
This is Candy ten for the Moto G7. Built straight from source with commits from a variety of different Sources/ROMS. We wanted to give the users a fun, fully customisable ROM, with regular updates and security patches.
We do this as a hobby, and we happily share the Candy of our toils with the custom ROM community, for free. We use what we share on our own devices, most as Daily Drivers, so you can be confident that problems will be promptly addressed.
Thanks for your support and camaraderie. Special thanks to GZOSP, GZR-ROMs, LineageOS, SlimRoms, OmniROM, AOSiP, DU and the innumerable rest who make their source open. We can't do all of this on our own!
Donations are appreciated, but NEVER expected.
Stay tuned for more Candy!
Special thanks to GZOSP, GZR-ROMs, LineageOS, SlimRoms, OmniROM, AOSiP and all the rest who make their source open. We can't do all of this on our own.
@gimmeitorilltell
@NoSpamDan
@kdp162
@chadouming
@Nick_gunale
@Yaznas
@bhi244
@rajatgupta1998
@miju12
Looking forward to be a device maintainer? Read about the requirements here.
ROM: CandyRoms Github
Kernel Source for Moto G7
Device specific sources: CandyDevices Github
Gerrit Review [url]https://gerrit.bbqdroid.org[/URL]
CandyShop:
SYSTEM
Volume buttons up/down for Do Not Disturb
Swap volume buttons on rotation
Long press volume playback control
Screen off power button torch (double press and long press)
Show app icons in toasts
LOCKSCREEN:
Double tap to sleep on lock screen
Face auto unlock
FP unlock without PIN/password
Quick PIN unlock
Disable QS when locked
Hide lockscreen power menu
Hide or show custom bottom shortcuts
Clock styles
Date styles
STATUS BAR
Clock options:
Alignment
Display seconds
AM/PM & Date display and format
Battery settings:
Battery icon style
Show percentage in Status bar
Network Traffic indicator
Quick settings:
Brightness slider icon (for Auto/Manual)
Bottom brightness slider
Custom number of rows/columns with Quick add (one click)
Quick pulldown (right)
Control status bar items
NAVIGATION
Navbar options:
Stock navbar
Hardware keys:
WIP
STOCK ROOM
Three finger screen shot gesture
Screenshot shutter sound
GENERAL
Rootless Substratum support
Night light
Prevent accidental wake up via proximity sensor
Candy Sweetener Device theme (Substratum if installed, Pixel, Stock)
SystemUI Tuner
Battery stats reset option
More to come, we are never done...
NO ETA REQUESTS!
Disclaimer:
CandyRoms is not responsible for any bricks you may obtain. Please follow the thread rules and steps and everything will be gravy. Remember, backing up before flashing is always recommended.
* See Post #2 for Downloads
* See Post #3 for FAQ/Known issues
Note:
If you are coming from stock you need to flash copy_partitions.zip just after flashing twrp, else you might face a hard brick.
Do not wipe or format data in TWRP, use fastboot -w instead after flashing the ROM, as mentioned below.
1. If you're coming from another ROM:
Official TWRP is recommended.
Boot into TWRP
Flash ROM (link in 2nd post)
Flash TWRP Installer
Reboot to Recovery
Flash OpenGApps
Flash the latest stable Magisk
No 3rd party mods are supported. (Like Xposed Framework or shady Magisk Modules)
Reboot to bootloader
Perform a factory reset using:
Code:
fastboot -w
Reboot to system
2. If you're updating the ROM:
Reboot to recovery
Flash Substratum rescue zip if you have a theme applied
Flash ROM
Flash TWRP Installer
Reboot to recovery
Flash OpenGApps
Flash Magisk
Reboot to bootloader
Perform a factory reset using:
Code:
fastboot -w
Reboot to system
NOTE:
If you have issues with Settings or Play Services force-closes you need to clean flash.
Please give first boot several minutes.
New additions and fixes being added constantly
If you have any other issue, please let us know in proper bug reporting fashion as indicated below.
Do NOT Report bugs if you're running a custom kernel or you installed other shady mods.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
ROM version and build date
Gapps version:
Did you--
wipe:
restore with titanium/swift backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed.
Also please let us know how to reproduce the particular issue.
Please, DO NOT complain about problems and offer nothing to help fix it. We reserve the right to ignore you for not following instructions.
Checkout our website (WIP): [url]http://candyroms.org[/URL]
Come visit us on Telegram: @CandyRoms
CandyRoms Telegram Release Channel: @CandyRoms_Channel
CandyRoms on SourceForge: SourceForge Project
Other Credits:
TeamReviver
@erfanoabdi
@vache
@Jleeblanch
@SyberHexen
Lukk1337, Luca Stefani and other LineageOS Devs
All the people responsible behind Motorola SDM632 bringup and development.
XDA:DevDB Information
Candy Ten for river, ROM for the Moto G7
Contributors
rajatgupta1998
Source Code: [url]https://github.com/CandyRoms[/URL]
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2020-03-15
Created 2020-03-15
Last Updated 2020-04-12
See Post #3 for a list of what is working or not if you have concerns.
ROM:
Latest Release: Candy-river-10.Stable-Official-20200315-1932.zip
Other Releases: river
GApps
Open GApps nano is preferred.
Recovery
Official TWRP
Firmware
<>
What's not working:
Jio VoLTE
Navigation Gestures on first boot, until you select in settings.
Notes:
Changelog
15 March 2020
Initial build
I've never heard of CandyROM before and am currently running lineageOS 16 so I'm curious as to what the differences are in terms of customization and general feel of the interface.
Also does candy ten mean this is an android 10 build or is it just the versioning?
Wanna try it out regardless but I'm hoping these questions get answered before I get a chance to ?
rajatgupta1998 said:
This is Candy ten for the Moto G7.
Click to expand...
Click to collapse
Do this also work with G7plus?
the_Pan said:
Do this also work with G7plus?
Click to expand...
Click to collapse
Nope the G7 plus and the G7 are different devices hence their ROMs are also different
---------- Post added at 10:14 PM ---------- Previous post was at 10:13 PM ----------
FlashyWatermelon said:
I've never heard of CandyROM before and am currently running lineageOS 16 so I'm curious as to what the differences are in terms of customization and general feel of the interface.
Also does candy ten mean this is an android 10 build or is it just the versioning?
Wanna try it out regardless but I'm hoping these questions get answered before I get a chance to ?
Click to expand...
Click to collapse
Based on the screenshots Rajat posted on Twitter,it seems to be android 10
jontyfernz97 said:
Nope the G7 plus and the G7 are different devices hence their ROMs are also different
---------- Post added at 10:14 PM ---------- Previous post was at 10:13 PM ----------
Based on the screenshots Rajat posted on Twitter,it seems to be android 10
Click to expand...
Click to collapse
Just checked the telegram channel. It is indeed android 10. Happy to finally be able to move on from pie!
EDIT: I suppose I could just read the full post and see that it says android 10, but that'd be too easy...
So far the only bug I encountered it's some choppiness on the animations especially on the recents menu going in and out of some applications, but this happens every time with a new version of Android regarding custom roms, I remember the same thing happening with oreo and pie, aosp or one ui, it's a little bit annoying but totally forgivable since everything else is fine as hell, thank you very much my dude, awesome job.
rajatgupta1998 said:
1. If you're coming from another ROM:
Official TWRP is recommended.
Boot into TWRP
Flash ROM (link in 2nd post)
Flash TWRP Installer
Reboot to Recovery
Click to expand...
Click to collapse
Hi, everyone. Tried to install Candy from stock ROM. After theese steps my phone has bricked. No reaction on buttons, when linked to PC by cable it looks like "qualcomm hs-usb qdloader 9008" in the device Manager.
What was my mistake?
anri_dedis said:
Hi, everyone. Tried to install Candy from stock ROM. After theese steps my phone has bricked. No reaction on buttons, when linked to PC by cable it looks like "qualcomm hs-usb qdloader 9008" in the device Manager.
What was my mistake?
Click to expand...
Click to collapse
You weren't mistaken, as you followed the instructions the OP provided. The same happened to me and after digging a bit I found out that when you're coming from stock you have to flash a file called "Copy Partitions Zip" before trying to install any custom roms. I know this can easily be our fault but at least he should've written clear and COMPLETE instructions.
I'm going to try unbricking the phone, I'll let you know if I come to any useful conclusion. Thanks OP.
OP thanks for making an Android 10 for the G7! Rom appears to be quite smooth and rung great. However, half my apps (even current up to date versions) seem to crash on it. Cant find a Gcam build that will run on it. That makes it unusable for me at the moment. Totally clean flash per directions with stock (Fi) kernel. Am I doing something wrong?
Great work on the rom! Doesn't even lag ,haven't faced any issues till now or encountered any bugs. I wish I could use Smart Reply anyway . Everything works just great
---------- Post added at 10:17 AM ---------- Previous post was at 10:05 AM ----------
In case you guys are having difficulty flashing candy rom on G7,follow the instructions below,that's how I install custom roms
Just backup or move everything to your PC,sync photos and contacts.
Here we are supposed to wipe internal storage in order to clean flash the rom.
+Boot into twrp,Format user data > yes
+Boot into twrp,wipe Data,Internal Storage,System,Dalvik/ART cache.
+Boot into twrp,flash copypartitions.zip
+Boot into twrp,flash candyrom.
+Now,from twrp,Boot into bootloader
+Boot into twrp,flash ARM64 10.0 Nano Gapps.
+Wipe Dalvik cache after flashing Gapps,powerOFF.
+Boot into System.
Incase if you want to permanently install TWRP on Candy rom and Root.
+Enable USB Debugging
+run command : adb reboot bootloader
+Boot into twrp,flash copypartitions.zip
+Flash twrpinstaller.
+Now,from twrp,Boot into recovery.
+Flash magisk.
+Reboot or manually powerOFF+ON.
I cant get data with this rom. I am on sprint network...
That fixed that issue. I have been getting now like flashing screen sometimes when pulling down the status bar to see notifications. Any fix for that? thanks
Thanks!
Thank a ton dude, this rom rocks. Better than lineage 16 for g7 haven't found a single bug. Speed is much better than lineage. Surprisingly awesome. Great work. Kudos!
@elboss Here's a test build. All others on Sprint (also if CDMA), Verizon please test if the calling/mobile data/volte works accordingly or not.
Candy-river-10-Stable-TESTING-20200402-1100.zip
Good morning guys. I am about to take this custom build. Coming from stock w/ Magisk. Super excited. Following the steps before actually doing the install, I didn't see the location to the "copy_partitions.zip" - can someone please provide a link or show me where I missed it please.
---------- Post added at 04:08 AM ---------- Previous post was at 03:42 AM ----------
located the copy partitions over on the LinageOS install page here:
https://www.cyanogenmods.org/forums/topic/download-lineageos-16-for-moto-g7/
Direct link:
https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view
rajatgupta1998 said:
@elboss .......please test if the calling/mobile data/volte works accordingly or not.......
Click to expand...
Click to collapse
No VoLTE love on Fi
Does Candy ROM have fingerprint?
Hi, I downloaded this Candy Rom for Moto G7 and it has been doing GREAT! Thanks. Just a question. When I try to use Terminal Emulator to edit device fingerprint. But this option is disabled?! Is it because this ROM does not have fingerprint? or how can I enable it? Can you please help? Thanks
------> under Terminal Emulator
------> type "SU"
------> Type "props".
Then the option is given
1 - edit device fingerprint (disable) Below photo is what it should be. But my device is showing (Disabled)
2........
I have a little question. Sorry, I'm new in this stuff.
Is there any method to install ROM without having a computer?
{
"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"
}
About Us (Quoting the DU Team):
Dirty Unicorns is an AOSP based project built to enhance the stock Android experience.
Our focus has been and is always to contribute back to the community. That is ultimately why we do what we do.
We DO NOT accept, nor ask, for donations. We do not believe in that. Everything that is necessary to keep this project going comes out of our own pocket. This includes, but is not limited to; Devices, Gerrit, our websites and services, etc.. The only thing that we ask in return is that you have patience, search the thread for answers prior to posting, read diligently, and try to enjoy the process with us!
About This Unofficial Build:
Majority of the credit for this ROM goes to the Dirty Unicorns team.
Since this is an unofficial build, do not expect any support from the DU team.
Builds will follow the official Dirty Unicorn ROM releases
Unless otherwise specified, the features in the ROM will be functionally identical to the official Dirty Unicorns ROM releases. No device specific feature requests will be accepted.
My time is fairly limited, so, while I will respond to posts/PMs, it might occasionally be a few days before I respond.
Kernel Source:
https://github.com/DirtyUnicorns/android_kernel_google_bluecross
Flashing Instructions:
Flashing DU
Download boot.img and ROM zip
Reboot into bootloader and flash the boot.img
Code:
fastboot flash --slot all boot boot.img
Reboot to recovery
Go to recovery select factory reset
Select Apply update from ADB to flash the zip
Code:
adb sideload nameofbuild.zip
Reboot and ENJOY!
Updating DU
Download ROM zip
Reboot into recovery and select Apply update from ADB to flash the zip
Code:
adb sideload nameofbuild.zip
Reboot system now and ENJOY!
**This IS NOT an officially supported device. Support is not promised or guaranteed**
**If you use Xposed, please don't bother reporting any bugs**
**If you use another kernel, please don't bother reporting any bugs**
**If you fail to follow these instructions, please don't bother reporting any bugs**
Download Links:
Build(s) - Sargo
Other Links::
ROM Source - https://github.com/DirtyUnicorns
Device Source - https://github.com/craigacgomez/du_android_device_google / https://github.com/craigacgomez/android_vendor_google
Gerrit - http://gerrit.dirtyunicorns.com
Crowdin (translations) - https://crowdin.net/project/dirtyunicorns
Changelogs - https://github.com/DirtyUnicorns/android_packages_apps_DU-Changelog/tree/jsons/official
XDA:DevDB Information
Dirty Unicorns, ROM for the Google Pixel 3a
Contributors
craigacgomez, NYCHitman1, jbats
Source Code: https://github.com/DirtyUnicorns
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 14.7
Stable Release Date: 2020-09-14
Created 2020-08-08
Last Updated 2020-09-14
Thanks for the great work
I can't wait to flash this and try it out!
Does anyone have any information about the battery life on DU compared to stock or another rom?
Also, is it rooted by default?
Thanks for bringing this rom to the Pixel 3a!
k4zz said:
Does anyone have any information about the battery life on DU compared to stick or another rom?
Click to expand...
Click to collapse
Battery life is subjective and depends on too many variables. That being said, battery life on DU is leat least quivalent, but should be better than stock.
k4zz said:
Also, is it rooted by default?
Click to expand...
Click to collapse
It's not rooted by default, but you may use Magisk if you want root.
craigacgomez said:
Battery life is subjective and depends on too many variables. That being said, battery life on DU is leat least quivalent, but should be better than stock.
It's not rooted by default, but you may use Magisk if you want root.
Click to expand...
Click to collapse
Thank you very much for the prompt response. I'm excited to try this one out. Is there a feature list posted somewhere for this ROM, or DU in general?
Thanks again for your work and support
Sent from my Pixel 3a using Tapatalk
k4zz said:
Thank you very much for the prompt response. I'm excited to try this one out. Is there a feature list posted somewhere for this ROM, or DU in general?
Thanks again for your work and support
Click to expand...
Click to collapse
A few core features
1. Customisable Active Edge support
2. Themes (accents, fonts, icon shapes, schedules, backup/restore)
3. Lock screen clock formats
4. Advanced power menu
5. Heads-up notifications and screen off animations
6. Battery icons and percentage
7. Status bar clock, icon and carrier label customisation
8. QS customisations
9. Traffic indicators
10. Navigation customisation (arrow keys, long press/swipe, pulse graphical equaliser)
11.. HW buttons playback controls
12. Upstream 4.14 kernel
And a whole lot of optimisations and fixes over AOSP (https://github.com/DirtyUnicorns/android_packages_apps_DU-Changelog/tree/jsons/official)
craigacgomez said:
Flashing Instructions:
If you have a device that uses TWRP
Verify that you're using the latest version of TWRP
Perform a FULL WIPE: (A full wipe is when you wipe system/data/cache/dalvik)
Flash the latest version of this ROM
Reboot and ENJOY!
Click to expand...
Click to collapse
I see you list instructions for flashing with a device with TWRP, does this mean if I flash back to Android 9 and install TWRP, that I can then run this ROM and TWRP even though its based on Android 10?
Joe333x said:
I see you list instructions for flashing with a device with TWRP, does this mean if I flash back to Android 9 and install TWRP, that I can then run this ROM and TWRP even though its based on Android 10?
---------- Post added at 01:11 AM ---------- Previous post was at 01:03 AM ----------
I see you list instructions for flashing with a device with TWRP, does this mean if I flash back to Android 9 and install TWRP, that I can then run this ROM and TWRP even though its based on Android 10?
Click to expand...
Click to collapse
No. That is only intended for devices that have TWRP support for Android 10.
craigacgomez said:
No. That is only intended for devices that have TWRP support for Android 10.
Click to expand...
Click to collapse
Damn thanks was hoping! I dont want to give up TWRP!
Hey thanks.
When I fastboot flash the boot.img, can I just initially use the magisk-patched version you've provided in your files there, in lieu of the plain boot.img? Would that save me some effort of setting up magisk afterwards, and I could boot into an already-rooted ROM?
blksith0 said:
Hey thanks.
When I fastboot flash the boot.img, can I just initially use the magisk-patched version you've provided in your files there, in lieu of the plain boot.img? Would that save me some effort of setting up magisk afterwards, and I could boot into an already-rooted ROM?
Click to expand...
Click to collapse
For the first flash / clean flash, don't use the Magisk patched boot image. Let the device boot up once after the sideload. You can reboot before running the setup and flash the Magisk patched boot image and then continue the setup. And you'll have to install MagiskManager after the device setup. It will ask you to reboot once.
For updates / dirty flash, you can sideload the ROM, reboot to bootloader and flash the Magisk patched boot image and then reboot to retain Magisk
This may be a very dumb question, but in terms of raw code, what is the difference between a rom for the Pixel 3a / Pixel 3a XL? Except the screen and the battery, the devices do not differ...wouldn't the DU Pixel 3a XL rom work as well?
Thanks for the rom - downloading it right now
Edit: I seem to have an issue with the first time wizard - it finds my wifi, but is somehow stuck. I've skipped it, but can't restore anything from my google backups...
ROM seems to be running quite good however
david320te said:
This may be a very dumb question, but in terms of raw code, what is the difference between a rom for the Pixel 3a / Pixel 3a XL? Except the screen and the battery, the devices do not differ...wouldn't the DU Pixel 3a XL rom work as well?
Thanks for the rom - downloading it right now
Edit: I seem to have an issue with the first time wizard - it finds my wifi, but is somehow stuck. I've skipped it, but can't restore anything from my google backups...
ROM seems to be running quite good however
Click to expand...
Click to collapse
The devices are nearly identical, and ROMs are likely mostly cross-compatible, but there are subtle differences like some of the configs... Screen and power to name a few.
The setup wizard works fine on both WiFi and mobile data. But I also don't know what you mean by "stuck". Does it connect to your WiFi networks? Have you tried it with your mobile data?
It just stays at the initial "Checking for Updates...". Yes, both LTE and WiFi are connected and i've tried it with both. I can just skip all of it and have been able to restore a backup afterwards
I have to say, it's a pretty amazing rom...i've got roughly 7 hours of SoT, a ton of standby, reception is good (i wish it would stay a bit longer on LTE, before switching over to Edge)
david320te said:
It just stays at the initial "Checking for Updates...". Yes, both LTE and WiFi are connected and i've tried it with both. I can just skip all of it and have been able to restore a backup afterwards
I have to say, it's a pretty amazing rom...i've got roughly 7 hours of SoT, a ton of standby, reception is good (i wish it would stay a bit longer on LTE, before switching over to Edge)
Click to expand...
Click to collapse
I've fixed the WiFi issue. I will post the update soon.
New build date 2020-08-16 uploaded. This fixes the WiFi issue where the device sometimes does not connect to a WiFi network and hangs. No other changes since the 2020-08-08 build.
Thank you for keeping the 3a alive with a custom rom!
craigacgomez said:
New build date 2020-08-16 uploaded. This fixes the WiFi issue where the device sometimes does not connect to a WiFi network and hangs. No other changes since the 2020-08-08 build.
Click to expand...
Click to collapse
craigacgomez said:
New build date 2020-08-16 uploaded. This fixes the WiFi issue where the device sometimes does not connect to a WiFi network and hangs. No other changes since the 2020-08-08 build.
Click to expand...
Click to collapse
@craigacgomez what was the change? I want to apply it to my personal build.
craigacgomez said:
New build date 2020-08-16 uploaded. This fixes the WiFi issue where the device sometimes does not connect to a WiFi network and hangs. No other changes since the 2020-08-08 build.
Click to expand...
Click to collapse
Thanks, will wipe the device in the next few days and try the setup again
david320te said:
Thanks, will wipe the device in the next few days and try the setup again
Click to expand...
Click to collapse
No need to wipe. You can just update like normal and it'll work fine
{
"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"
}
Resurrection Remix Q
Code:
[SIZE="4"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.
Install the stock recovery.img if you have previously installed twrp.
1. Extract the zip to your adb/fastboot directory, reboot to bootloader and open a CMD window.
2. Reboot your device into fastbootd mode.
Code:
fastboot reboot fastboot
3. Flash boot, system, product, and vbmeta images.
Code:
[/B][/CENTER]
[B][CENTER]fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
4. Wipe userdata.
Code:
fastboot -w
5. Reboot, Profit.
(OPTIONAL)
6. If you want to install TWRP/gapps/magisk, do so after you continue through the installation steps to the home screen.
If you have the Moto G8/G Fast and your display cutout is not right, enable the overlay via ADB:
Code:
adb shell cmd overlay enable org.omnirom.overlay.moto.rav
ROM Download
GApps
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
AICP
Crdroid
AOSIP
DU
Xtended
Evolution X
Bliss
Omni Team
And Of Course To All The Supporters, Donators And Users
Join our Telegram channel : https://t.me/resurrectionremixchat
1. Starting screen casting/mirroring causes a reboot.
2. The in-built screen recorder also causes a reboot when started.
Dodgy Screen Recorder Fix :laugh:: Download and install the attached apk below, change the quick setting tile to the new one at the bottom of the list, and you should be able to record. (Its the screen recorder app from BlissRom, nothing malicious )
3. Let me know :good:
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.
To update to the latest version without wiping:
UPDATING FOR GAPPS/MAGISK USERS
1. Install the images as usual in fastbootd
2. Power off and boot to TWRP
3. Install GAPPS and/or Magisk
4. Reboot, profit.
UPDATING FOR NON GAPPS/Magisk USERS
Skip steps 2. and 3. from above.
Cant figure out which drive i uploaded the old files to at the moment
But heres the 8.6.9 May security patch update.
Not much new, added a KCAL enabled kernel as default, and added a color control app (root needed), fixed face unlock (g power) and added the moto clock widgets.
RR - May Patch - Google Drive
drive.google.com
TWRP zip and fastboot d images, no gapps only. Theres also some flame gapps in the folder too that i use and work well.
I have a moto g stylus and the phone does not have fastbootd mode, i dont think.
gking707 said:
I have a moto g stylus and the phone does not have fastbootd mode, i dont think.
Click to expand...
Click to collapse
it does but you have to boot into recovery to enter fastbootd mode
MadMan29729 said:
it does but you have to boot into recovery to enter fastbootd mode
Click to expand...
Click to collapse
Or you can boot into fastbootd by using adb in fastboot mode and typing "fastboot reboot fastboot"
Thanks op for my favorite rom RR.
Only issue is whats reported in the o.p.
Not really a problem since regional models have faceunlock, but faceunlock feature not operable.
I noticed any of the custom roms faceunlock feature works on them. only the stock rom... hope thers a fix. A Motorola update has some bug fixes stock build retus dated 11/16/2020.
I also love how the stock moto camera works by downloading the apk from the playstore (moto camera2)
The stock camera has action cam which i use.
I don't use screen recording anyways.
Great job!!! I appreciate your work.
I cant find the three finger screenshot.
I did see a setting in RR settings but only to use volume keys or drag option. the drag option screenshot works but i cant get the volime key combo to work.
jhjhjhjhjhjh said:
Thanks op for my favorite rom RR.
Only issue is whats reported in the o.p.
Not really a problem since regional models have faceunlock, but faceunlock feature not operable.
I noticed any of the custom roms faceunlock feature works on them. only the stock rom... hope thers a fix. A Motorola update has some bug fixes stock build retus dated 11/16/2020.
I also love how the stock moto camera works by downloading the apk from the playstore (moto camera2)
The stock camera has action cam which i use.
I don't use screen recording anyways.
Great job!!! I appreciate your work.
I cant find the three finger screenshot.
I did see a setting in RR settings but only to use volume keys or drag option. the drag option screenshot works but i cant get the volime key combo to work.View attachment 5153117
Click to expand...
Click to collapse
Thank you for the nice comment.
For the three finger screenshot, its in Settings/Resurrection Tools/Interface/Miscellaneous.
And the volume keys option doesnt seem to work, but power and volume down works as usual
Beetle84 said:
Thank you for the nice comment.
View attachment 5153183
For the three finger screenshot, its in Settings/Resurrection Tools/Interface/Miscellaneous.
And the volume keys option doesnt seem to work, but power and volume down works as usual
[/QUOTE
Thanks yes volune down and power works
Click to expand...
Click to collapse
just fyi the oden.zip kernel works pretty good on RR. the one fron the havoc rom.
I flahsed it in twrp..touchscreen now works in twrp.
jhjhjhjhjhjh said:
just fyi the oden.zip kernel works pretty good on RR. the one fron the havoc rom.
I flahsed it in twrp..touchscreen now works in twrp.View attachment 5154753
Click to expand...
Click to collapse
You wouldnt have needed the odin kernel.zip, its included as the default kernel now.
jhjhjhjhjhjh said:
just fyi the oden.zip kernel works pretty good on RR. the one fron the havoc rom.
I flahsed it in twrp..touchscreen now works in twrp.View attachment 5154753
Click to expand...
Click to collapse
But after flashing it twrp is working fine now? Weird
RR updated.
Version bump to 8.6.5
Added OPScreenRecorder.apk as system app.
Removed built-in Screen Recorder QS Tile. (only the working one appears now)
Removed Recorder app as it links to in-built broken screen recorder.
Added HavocOS audio recorder app.
Added update steps to post #2.
what is the recommend gapps?
Beetle84 said:
RR updated.
Version bump to 8.6.5
Added OPScreenRecorder.apk as system app.
Removed built-in Screen Recorder QS Tile. (only the working one appears now)
Removed Recorder app as it links to in-built broken screen recorder.
Added HavocOS audio recorder app.
Added update steps to post #2.
Click to expand...
Click to collapse
Again thanks ..
Question. hope you can answer.
The gapps package inside the rom zip when extracted, has apps in .lz format. I tried to re-zip the gapps and size is 1.2GB and I also get the error package "corrupt"
The apps in .lz format has android auto in which I'm trying to get working on custom roms rather than just stock.
I believe the gapps package that is small enough to flash is nano and pico nano like 200mb and pico like 91mb.They both lack android auto support.
Per the gapps page only "super and stock gapps zips" contain android auto support.
For some reason twrp won't let me sideload via cpu. Soon as I swipe to start sideload mode it immediately says failed.
Also twrp on this rom won't let me resize the /system/data partion to gather enough space to flash a large gapps package.
523MB of space on the /system after flashing the rom.
How do I get the gapps package you included flashed?
MadMan29729 said:
what is the recommend gapps?
Click to expand...
Click to collapse
Is that you Lane ?
Open gapps pico is what i use mate
Beetle84 said:
Open gapps pico is what i us
Click to expand...
Click to collapse
I ended up installing nano gapps
MadMan29729 said:
what is the recommend gapps?
Click to expand...
Click to collapse
i always use pico
Micro g signature spoofing works.
You rock beetle84!!
Dude, @Beetle84 !! The only reason I got this damned phone was so that I could build an RR for it and you ninjad me!!
No, I'm just kidding. I only have a dual core Pentium with 6 gigs ram atm and would lose my mind tryin to build with it. I friggin love this phone but I was kinda disappointed with the ROMs. Hell, I was about to go back to stock when I saw this, my favorite. And I haven't noticed a bug nor had an unexpected reboot in the 4 or so days since I've been running it and my favorite screen recorder app is working just fine in it as well. It is now the best, and most stable ROM we've got, and ROMs don't get better than RR, IMHO....Check out my homescreen with the only wallpaper I've used since booting my 1st RR like 5 years ago....its from the RR 5.1.1 PitchBlack Theme. Yeah I know. I need an icon pack....I'm on it.....Thanks for my favorite ROM on my favorite phone, Sir. It's outatanding!
And here's that wall, if anyone wants it.
{
"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"
}
Project Elixir for the Poco F3 [alioth]
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
"This is a user-friendly thread, all your suggestions, and proper bug reports are important to us but don't be disrespectful to anyone here. Your suggestions and proper bug reports will be taken into consideration.."
Project Elixir is another aftermarket AOSP ROM which basically offers minimal UI enhancement & close to Stock Android ROM with great performance, security and stability. Most of the OEMs' these days will provide slow and untimely updates, but we don't do that here. We closely follow Google to bring the latest updates to our users, and even prolong support for devices that have been declared obsolete by OEMs. Our ROMs' source code is open-source, secure, stable, and outstanding. Your experience while using Project Elixir will be butter smooth without compromising the quality of the Android experience. In short, it's perfectly balanced between Great Performance, Security, stability, minimal UI & awesome features including pixel goodies So do not hesitate anymore, join us now and start enjoying the beauty of stock Android. Download and enjoy Project Elixir on your respective devices!
- Saurav - Founder / lead Developer
- Nishant - Co-lead Developer / Team
- [/SIZE]And Also Our Hardworking Maintainers
// Checkout the latest changes you get //
Spoiler: Click Here to see
Latest Changelog: https://projectelixiros.com/changelog
NOTE : In Project Elixir you get all the useful features and with updating source every month it's hard to keep all the threads updated everytime everywhere so kindly visit our website for latest changes and screenshots.
// A screenshot is worth of thousand words //
Spoiler: Click Here to see
Latest Screenshots : https://projectelixiros.com/gallery
NOTE : In Project Elixir you get all the useful features and with updating source every month it's hard to keep all the threads updated everytime everywhere so kindly visit our website for latest changes and screenshots.
--------- > OFFICIAL Download Server < ---------
NOTE: Please keep in mind that these are Gapps Builds and there is no vanilla build of this rom available.
--------- > Visit Our OFFICIAL Website < ---------
NOTE: It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine. If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
CLEAN FLASH (Moving From A12 to A13)
- Download the latest build
- Take a backup for safe side
- Boot to Recovery
- Flash Recommended Firmware
- Flash Rom
- Flash Current Recovery
- Reboot To Recovery
- Formate Data
- Reboot System
(Note: The ROM uses vendor_boot-as-recovery, so either keep using the ROM's own Recovery, or flash a vendor_boot Recovery; don't flash a standard Recovery)
What works?
Wifi | RIL | Mobile data | GPS | Camera
Flashlight | Camcorder | Bluetooth | Fingerprint reader | Lights | Sound | vibration
Almost everything
What doesn't work? or Any Bug ?
You tell me!
BUG REPORT !!
As soon as the problem occurs, take a logcat and please inform us via Telegram or XDA.
for more READ THIS
- Android Open-Source Project
- Pixel Experience
- LineageOS
- Proton AOSP
- Arrow OS
XDA Banner and Template Credit goes to Amaan
- Others, I may have forgot to mention
- Android OS version: 13.0
- Security patch: April 2023
- Build author/Device Maintainer : AbrarNoob
- DEVICE: Poco F3
- DEVICE CODENAME: alioth
---- Sources and Documentation ----
-- ROM Source Code --
-- Kernel Source --
-- Documentation & Maintainership --
-- OFFICIAL Website and Telegram Support --
-- Visit our OFFICIAL Website --
-- Device Update Telegram Channel --
-- Support/Discussion Telegram Group --
// Giving a little can HELP a lot //
- As you know build is free but building ROM needs server and in order to maintain the source, we need High-End Servers that are generally very expensive and need to be renewed every single month and as a student its quite difficult. To meet with our technical expenses, a cup of coffee, and the efforts of the developers we need your monetary support!
- Do consider donating or buying me a coffee on Paypal or join us on Patreon for sustainable support and rewards if you want to appreciate our work.
- Thank you for your support !
This ROM uses vendor_boot-as-recovery. It would be helpful to document this.
DarthJabba9 said:
This ROM uses vendor_boot-as-recovery. It would be helpful to document this.
Click to expand...
Click to collapse
Thanks for the info, it didn't on previous versions when I tried it a few month ago. Thanks to you I won't brick my phone xD
nicky69100 said:
Thanks for the info, it didn't on previous versions when I tried it a few month ago. Thanks to you I won't brick my phone xD
Click to expand...
Click to collapse
You're welcome. But it shouldn't brick your device - as long as you don't try to re-flash a standard recovery after flashing the ROM. The problem is that you won't know that you should avoid doing that if you don't know that it is a vendor_boot-as-recovery ROM.
That is why I am trying to encourage devs who release vendor_boot-as-recovery ROMs to label them clearly as such, so that users will know what they're dealing with, before flashing the ROM.
god project，i will flash it
DarthJabba9 said:
This ROM uses vendor_boot-as-recovery. It would be helpful to document this.
Click to expand...
Click to collapse
Thanks for this. I have documented this .
After the screen is locked, the screen cannot be turned on
liut2020 said:
After the screen is locked, the screen cannot be turned on
Click to expand...
Click to collapse
Flashing steps you did?
Hasin Abrar Haque said:
Flashing steps you did?
Click to expand...
Click to collapse
1. format data（twrp）
2. flash elixir （twrp）
3. reboot to recovery
4. flash magisk26.1.apk
5. reboot to system
Hello, the setting-Security always loading
so the fingerprint does not work
Great ROM. I just flashed it, and it feels smooth and nice. I found a few small issues though.
- Before I had a PIN lock screen, after a reboot the UI felt sluggish. This went away when I think I toggled the camera option off or went into the Leica app. (Can no longer test this as I now have a lock screen and the issue doesn't seem to happen anymore)
- Camera2 API does not work, and therefore the CameraX library doesn't work either. When I opened my own camera app that uses CameraX, I only got a black screen.
- Snapchat camera is not found, only a black screen.
Some errors that come up (not sure how relevant/if you want the full logcat instead):
`Session 0: Failed to create capture session; configuration failed`
`Failed to find sync for id=0`
`Unable to match the desired swap behavior.`
`CameraCaptureSession.onConfigureFailed() RELEASED`
is an error that comes up. CameraX is reporting the camera as opened though, but then closes and reopens again in a loop:
Recalculating open cameras:
Camera State
-------------------------------------------------------------------
[email protected][id=1] UNKNOWN
[email protected][id=0] OPEN
-------------------------------------------------------------------
After unplugging from a USB charger, thre still shows up text that says `99% charging slowly` from when I was plugged into a PC usb port.
I experienced some issues with the included Leica camera too, although I'm not sure if those should be reported here.
Also, why does Shell request SU permissions when plugging in my USB cable and enabling USB Debugging?
I can't install any zip via twrp without getting bootloop, even if I update the kernel or install magisk the rom will crash.
DarthJabba9 said:
You're welcome. But it shouldn't brick your device - as long as you don't try to re-flash a standard recovery after flashing the ROM. The problem is that you won't know that you should avoid doing that if you don't know that it is a vendor_boot-as-recovery ROM.
That is why I am trying to encourage devs who release vendor_boot-as-recovery ROMs to label them clearly as such, so that users will know what they're dealing with, before flashing the ROM.
Click to expand...
Click to collapse
hihi, sorry but can you explain what do you mean vendor_boot-as-recovery rom. is it that once you flash project elixir, the recovery is build inside the .zip rom file. and if I flash twrp after flashing this rom, i would brick the device? because i was initially using elixir 3.5, then tried to dirty flash to 3.7 but it bricked.. so i had to do a hard reset from fastboot then i flashed 3.7 and then twrp again.. will i brick my device if i dirty flash to 3.8 (when it comes out)? thanks alot!
otahboi said:
hihi, sorry but can you explain what do you mean vendor_boot-as-recovery rom. is it that once you flash project elixir, the recovery is build inside the .zip rom file. and if I flash twrp after flashing this rom, i would brick the device? because i was initially using elixir 3.5, then tried to dirty flash to 3.7 but it bricked.. so i had to do a hard reset from fastboot then i flashed 3.7 and then twrp again.. will i brick my device if i dirty flash to 3.8 (when it comes out)? thanks alot!
Click to expand...
Click to collapse
Read the first two posts in this thread:
Vendor_Boot ROMs
1. We are beginning to see the release of new Android 13 ROMs for Alioth, that use "vendor_boot-as-recovery" ("vendor_boot") instead of the standard "boot-as-recovery". 2. A "vendor_boot" ROM has its recovery resources in the "vendor_boot"...
forum.xda-developers.com
white5pirit said:
Great ROM. I just flashed it, and it feels smooth and nice. I found a few small issues though.
- Before I had a PIN lock screen, after a reboot the UI felt sluggish. This went away when I think I toggled the camera option off or went into the Leica app. (Can no longer test this as I now have a lock screen and the issue doesn't seem to happen anymore)
- Camera2 API does not work, and therefore the CameraX library doesn't work either. When I opened my own camera app that uses CameraX, I only got a black screen.
- Snapchat camera is not found, only a black screen.
Some errors that come up (not sure how relevant/if you want the full logcat instead):
`Session 0: Failed to create capture session; configuration failed`
`Failed to find sync for id=0`
`Unable to match the desired swap behavior.`
`CameraCaptureSession.onConfigureFailed() RELEASED`
is an error that comes up. CameraX is reporting the camera as opened though, but then closes and reopens again in a loop:
Recalculating open cameras:
Camera State
-------------------------------------------------------------------
[email protected][id=1] UNKNOWN
[email protected][id=0] OPEN
-------------------------------------------------------------------
After unplugging from a USB charger, thre still shows up text that says `99% charging slowly` from when I was plugged into a PC usb port.
I experienced some issues with the included Leica camera too, although I'm not sure if those should be reported here.
Also, why does Shell request SU permissions when plugging in my USB cable and enabling USB Debugging?
Click to expand...
Click to collapse
Thanks for this! I was hoping I wasn't the only one experiencing in-app camera issues. Any ideas on the fix? Or do I just downgrade and wait for the next update?
DarthJabba9 said:
Read the first two posts in this thread:
Vendor_Boot ROMs
1. We are beginning to see the release of new Android 13 ROMs for Alioth, that use "vendor_boot-as-recovery" ("vendor_boot") instead of the standard "boot-as-recovery". 2. A "vendor_boot" ROM has its recovery resources in the "vendor_boot"...
forum.xda-developers.com
Click to expand...
Click to collapse
thank you. does that mean if i just flash a vendor boot rom without trying to replace the recovery to OF or TWRP, there will be no chance of bricking?
otahboi said:
thank you. does that mean if i just flash a vendor boot rom without trying to replace the recovery to OF or TWRP, there will be no chance of bricking?
Click to expand...
Click to collapse
Well, you won't get a brick caused by flashing the wrong recovery. But nobody can promise you a "no chance" of bricking when flashing anything.
DarthJabba9 said:
Well, you won't get a brick caused by flashing the wrong recovery. But nobody can promise you a "no chance" of bricking when flashing anything.
Click to expand...
Click to collapse
alls good. i dirty flashed from elixir 3.7 to 3.8 and the elixir recovery replaced my twrp without bricking my device.
Hasin could you write the changelog of every update since you lead this project?
Last update about it is at 3.4
Also, what camera does it have?
Hey all,wanted to share my experience with this ROM
This is among the best ROMs for our F3,everything(almost) works:LDAC,face detection,face based screen rotate,screen retension,AOD while charging,and much more,great job Dev!
theres just some bugs that need squashing and this would be solid as (something very solid):
1-in ambient display the charging information refreshes absurdly fast,like 2-3 times per second
2-USB tether doesn't work
3-sometimes there are HUGE lags,its like input lag coupled with low refresh rate
4-QR scanner in quick settings stuck on updating and doesn't work
BTW i especially liked the battery settings menu ,very nice
thank you for this ROM,will continue using it