{
"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"
}
RevengeOS is an aftermarket firmware based on AOSP. We are dedicated to a beautiful, fast, stable and minimal customized ROM, honesty and communication with our users, and openness with our code, Hope you will enjoy.
Please feel free to look, build, and use our code at RevengeOS GitHub.
Also, we got our Telegram Group to talk about the ROM, share some love, ideas or even have fun with us
If you need help, don't hesitate to join our Telegram Group
Disclaimer: While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in Telegram Group
Get the latest build :
Here
Download patched Magisk here (optional)
Any Gapps of your choice (e.g. NikGapps, FlameGapps, BitGapps)
What's Working
RIL (Calls, SMS, Data) + Volte
Fingerprint
Wi-Fi
Bluetooth
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
GPS
Pixel Power + Thermal
BUGS:
Selinux Permissive
You tell me
Download the ROM
1. Backup your data to PC, OTG flash drive
2. Get a proper Recovery
3. Reboot to Recovery
4. Format data (f2fs for best performance)
5. Reboot again to recovery
5. Flash Revenge OS zip, reflash recovery
6. Reboot into recovery
7. Flash Gapps (+ optionally Magisk) and reboot to system
8. Profit
[First boot will take few minutes! Have patience]
Clean Flash is always recommended!
Device Tree: Here
Vendor Tree: Here
Kernel: Here
If you want any bug to be fixed please write here on xda in detail. Give Logcats, mention your device name, mention if any mods and kernels, if used and please be specific about it. By helping us, you are helping yourself too.
->How to take Logcats?
https://goo.gl/UcTM9 and https://goo.gl/J4CSEP
Join Our Device Specific Group
Poco X3 Support Group
XDA:DevDB Information
RevengeOS, ROM for the POCO X3
Contributors
P Sambit
Like my work? Buy me a beer !
Paypal
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Based On: AOSP
Hi, great ROM, everything working smoothly, please add ExFat support
i can't pass play protect. what should i do?
trai_th said:
i can't pass play protect. what should i do?
Click to expand...
Click to collapse
CTS Profile and "Device is not certified" FIX
1. Install MagiskHide Props Config module and reboot device
2. Install termux and write 'su' then 'props', wait for props to load
3. choose the option 'Edit device fingerprint' by writing the appropriate number
4. then choose the option 'pick a certified fingerprint'
5. choose the device 'POCO' by writing appropriate number
6. choose 'POCO X3 NFC Global' [It works for KARNA too]
7. it will ask to reboot, press 'y' to reboot.
let device reboot and check the device certification in playstore and cts profile in magisk. boom everything works....
Any idea when SELinux will be set to Enforcing? What needs to be fixed to enable Enforcing?
You'll be getting Enforcing build in future. Just wait and have patience.
Psambitk1 said:
CTS Profile and "Device is not certified" FIX
1. Install MagiskHide Props Config module and reboot device
2. Install termux and write 'su' then 'props', wait for props to load
3. choose the option 'Edit device fingerprint' by writing the appropriate number
4. then choose the option 'pick a certified fingerprint'
5. choose the device 'POCO' by writing appropriate number
6. choose 'POCO X3 NFC Global' [It works for KARNA too]
7. it will ask to reboot, press 'y' to reboot.
let device reboot and check the device certification in playstore and cts profile in magisk. boom everything works....
Click to expand...
Click to collapse
thx u
Hello! Long story short: I have a Poco X3 NFC and about 2 weeks ago I decided to install Pixel Experience. Because I am a beginner in this whole "world" of custom ROMs I didn't know what to look for when I chose PE. Due to the lack of customization, I thought about installing another ROM. I entered TWRP, I followed the steps for installing RevengeOS and when I had to reboot to system, it bootloops in the recovery mode (TWRP). I somehow managed to learn how flash the stock MIUI with MiFlashTool and now I am stuck with the MIUI beacause of the TWRP bootloop Please help me!
Thanks!
OctaSky28 said:
Hello! Long story short: I have a Poco X3 NFC and about 2 weeks ago I decided to install Pixel Experience. Because I am a beginner in this whole "world" of custom ROMs I didn't know what to look for when I chose PE. Due to the lack of customization, I thought about installing another ROM. I entered TWRP, I followed the steps for installing RevengeOS and when I had to reboot to system, it bootloops in the recovery mode (TWRP). I somehow managed to learn how flash the stock MIUI with MiFlashTool and now I am stuck with the MIUI beacause of the TWRP bootloop Please help me!
Thanks!
Click to expand...
Click to collapse
did you format data (yes) after installing RevengeOS? if not and you are using encrypted internal storage, format data (yes) is mandatory after installing a new custom rom
jeryll said:
did you format data (yes) after installing RevengeOS? if not and you are using encrypted internal storage, format data (yes) is mandatory after installing a new custom rom
Click to expand...
Click to collapse
Yes! I formatted it before and after installing it
jeryll said:
format data (yes) is mandatory after installing a new custom rom
Click to expand...
Click to collapse
OctaSky28 said:
I formatted it before and after installing it
Click to expand...
Click to collapse
As far as I know, you have to format it before installation, not after. If you format it after installation, you basically wipe part of the new installation.
Aki-to said:
As far as I know, you have to format it before installation, not after. If you format it after installation, you basically wipe part of the new installation.
Click to expand...
Click to collapse
and which part is that?
After I flashed RevengeOS, it directly booted in the ROM without doing any setup (add Google Account, load any backup etc.). Any idea?
OctaSky28 said:
After I flashed RevengeOS, it directly booted in the ROM without doing any setup (add Google Account, load any backup etc.). Any idea?
Click to expand...
Click to collapse
As I see, this ROM is Vanilla (without GApps), so u have to flash any GApps package after u flash the ROM.
Related
{
"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"
}
PixelExperience for Nexus 6P [angler]
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 9.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FMRadio
Fingerprint reader
NFC
Lights
Sound / vibration
Facelock
Known issues
Nothing
DON'T FLASH GAPPS, ALREADY INCLUDED
Download from Pixel Experience website
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
Android OS version: 9.0.0_r46
Security patch level: December 2019
Build author/Device Maintainer: PixelBoot
Device Source code: https://github.com/PixelExperience-Devices
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
XDA:DevDB Information
PixelExperience Pie, ROM for the Huawei Nexus 6P
Contributors
PixelBoot
Source Code: https://github.com/PixelExperience
ROM OS Version: 9.x Pie
ROM Firmware Required: TWRP, Unlocked bootloader
Based On: AOSP
Version Information
Status: Stable
Created 2018-11-22
Last Updated 2019-12-14
Installation Instructions:
Grab our recovery from the peripherals section and install it.
Through TWRP Recovery:
Install Zip > Install Image > Choose ‘recovery.img‘ > Select partition ‘Recovery’ > Swipe to confirm flash
Through Fastboot:
Code:
fastboot flash recovery recovery.img
Install the ROM and then wipe your internal data partition.
Through TWRP Recovery:
Wipe > Format data
Through Fastboot:
Code:
fastboot -w
Reboot into system and wait until the process finishes, it could take a little bit. After the installation is done, I suggest waiting before using the phone because it usually goes into thermal throttling after installing a ROM.
A few notes before you proceed:
Before going straight to the download section there’s something we would like to tell you. We have changed the default encryption method for the phone, migrating to File-Based Encryption (you can get more information from the official Google documentation page). In order to get this encryption mode working, you will need to use our custom recovery (compiled from the latest source) which is compatible with this encryption and, just for the first time, you will have to wipe your internal data, so backup your data before proceeding.
Peripherals:
FBE Recovery: TWRP
Nexus 6P PixelExperience Telegram Group: Join
Thread reopened and cleaned since builds are now stable!
Big thanks to StatiXOS team for the sources.
Check them out here: https://github.com/StatiXOS
Can we use stock TWRP instead of FBE version and skip encryption?
wizardwiz said:
Can we use stock TWRP instead of FBE version and skip encryption?
Click to expand...
Click to collapse
Regular TWRP will not work, and will result in bootloops, or infinite boot cycle.
Kindly take your time and flash the FBE version of TWRP.
In the long run, they're basically the same thing, so I don't see why not. ^^
PixelBoot said:
Regular TWRP will not work, and will result in bootloops, or infite boot cycle.
Kindly take your time and flash the FBE version of TWRP.
In the long run, they're basically the same thing, so I don't see why not. ^^
Click to expand...
Click to collapse
OK, thanks for the reply.
Is there an option to keep the file system un-encrypted or is it a must?
wizardwiz said:
OK, thanks for the reply.
Is there an option to keep the file system un-encrypted or is it a must?
Click to expand...
Click to collapse
I believe it's a must.
I know it sounds annoying in real-time but it is really handy in reality.
So far working well. Thanks
Someone who shows screenshots ..?
Hi, so I just installed the ROM and my phone has powered up now. The only issue that I'm facing is that I keep on getting an error saying "Bluetooth Keeps Stopping", what could be the issue? :/
Whats the default password for TWRP?
PixelBoot said:
Installation Instructions:
Note: If your phone only has 4 cores, download the BLOD patch (you can find it in the download section), flash our recovery.img from your working TWRP and then install the BLOD patch.
Grab our recovery from the peripherals section and install it.
Through TWRP Recovery:
Install Zip > Install Image > Choose ‘recovery.img‘ > Select partition ‘Recovery’ > Swipe to confirm flash
Through Fastboot:
Code:
fastboot flash recovery recovery.img
Install the ROM and then wipe your internal data partition.
Through TWRP Recovery:
Wipe > Format data
Through Fastboot:
Code:
fastboot -w
Reboot into system and wait until the process finishes, it could take a little bit. After the installation is done I suggest waiting before using the phone because it usually goes into thermal throttling after installing a ROM.
Click to expand...
Click to collapse
Nice to see you back again. I thought you forgot about us after the thread being closed. Thanks Dev
Gearswar said:
Nice to see you back again. I thought you forgot about us after the thread being closed. Thanks Dev
Click to expand...
Click to collapse
I cleaned it to get a fresh start!
Official Support is now out for Angler!
Get your hands on it now!
Google Nexus 6P (angler)
PixelBoot said:
I cleaned it to get a fresh start!
Click to expand...
Click to collapse
Thanks Dev @PixelBoot for your time and effort.
Will start happy flashing today
Thanks
@PixelBoot im getting Android setup keeps stopping error, any solution?
thanks
Cannot boot into rom, always reboots to recovery.
{
"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:
/*
* 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.
*/
What is ProjectTitanium?"ProjectTitanium is an GZOSP-Based-Custom Aftermarket Firmware Distribution for Android Devices. Our Goal is to Deliver Performance with many Features, Security, Cleanliness, and good Battery Life, Trying to make Something Unique than any other Android ROM. We Hope That you'll Love our Work, and help us in Making it even Better in the Future.
Features:Work In Progress
Featured Stuffs:
- TiPapers
- About ProjectTitanium
-WIP
And many more being added regulary! *soon
Installation:Make sure you have a custom recovery installed(TWRP is the preferred recovery)
Download the latest ProjectTitanium ROM & the latest GApps package
Boot into recovery
Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution
Flash ProjectTitanium ROM
Flash Google Apps package(Optional)
Flash Magisk Root(Optional)
First boot may take up to 10 minutes.
Downloads:A/B: PTi-Beta-0.5-GSI-ARM64-AB-OFFICIAL(update 02/07/2019)
Only A: PTi-Beta-0.5-GSI-ARM64-A-OFFICIAL (update 02/07/2019)
GApps
Source Code:ProjectTitanium
Credits:
-@XTutorials(Founder/Lead Developer)
-@DarkJoker360(Co-Founder/Lead Developer)
-@Thespartann(Senior Developer)
-@K3RN3L_P4N1C(Web Developer)
- Phhusson for Treble trees
- LineageOS
- GZOSP
REPORTING BUGS/PROBLEMS!
As soon as the problem occurs, feel free to tell me or, if possible, send me a logcat and I'll see what I can do!
Have a feature request? Don't spam here. Visit our Telegram group!
ProjectTitanium Official Website:
ProjectTitanium
ProjectTitanium Official Telegram group:
Telegram
Support us!
Hello, Gracious human! if you like our work, you may support us by donating:
PayPal
Note
This ROM is in Beta state for now, I uploaded it here mainly for testing purposes(not that it can't be used as a daily ROM, it can actually, it just doesn't have all the things the final 1.0 will have.
A/B one does not boot on Xiaomi Mi 9 (Vendor used: Xiaomi.eu 9.5.30)
all other GSIs do boot with exact same procedure.
Mohammed779 said:
A/B one does not boot on Xiaomi Mi 9 (Vendor used: Xiaomi.eu 9.5.30)
all other GSIs do boot with exact same procedure.
Click to expand...
Click to collapse
Ah, damn. Let me see what I can do. Thanks for the report.
Could you give me any log?
Mohammed779 said:
A/B one does not boot on Xiaomi Mi 9 (Vendor used: Xiaomi.eu 9.5.30)
all other GSIs do boot with exact same procedure.
Click to expand...
Click to collapse
Same issue for same device.....
I will test it on s9+ and let u know if it boots or no
Update coming this night fixing hopefully all boot issues, even though on some devices it boots...
Regards,
ARM 64 A Only build boots fine on ZTE Axon 7. I had a quick browse through Settings, seems very barebones. I don't blame ya, you said yourself it's in beta. I'll keep an eye out for when you've had a chance to update it
Booted on s9+ but the rom is like stock aosp no features or anything, maybe because it is still on beta
Update 02/07/2019!
Good Evening! I'm back as I said, and here is the update for this ROM.
Changelog:
-Boot issues fixed!
-Vendor fixed!
-New stock wallpaper
-Fixed build number bug
-Other miscellaneous fixes
Download:Only A:
PTi-Beta-0.5-GSI-ARM64-A-OFFICIAL
A/B:
PTi-Beta-0.5-GSI-ARM64-AB-OFFICIAL
Best Regards!
A/B Build added to the update reply, now since the builds should work our team is going to start working on actually bringing features to this.
Hopefully sooner than you think.
Regards,
Akhayev said:
Booted on s9+ but the rom is like stock aosp no features or anything, maybe because it is still on beta
Click to expand...
Click to collapse
Would you please tell the Firmware and Vendor you are on . Thank you !
fares70 said:
Would you please tell the Firmware and Vendor you are on . Thank you !
Click to expand...
Click to collapse
Brk3 vendor , and firmware use the one u already using ,
XTutorials said:
A/B Build added to the update reply, now since the builds should work our team is going to start working on actually bringing features to this.
Hopefully sooner than you think.
Regards,
Click to expand...
Click to collapse
Do you mean this ROM is intended to be feature-rich like Havoc, Liquid, PixelDust...?
Boots on Blu Vivo XI.
Hello Goodnight.
I previously installed GSI roms.
but now I try to install with the usual procedure
for my G9600 S9
but I can not get into the system
it always stays in the logo and never passes from there.
I already wait more than 25 minutes and nothing.
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be A-only_arm64 Variant)
Unpack it if it wasn't in .IMG format
Wipe DATA, and reboot in TWRP
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Install the kernel for GSI GSI Kernels
In TWRP mount System, then go to ADVANDED, File Manager, and delete this file: system/bin/rw_system.sh
Reboot system
What is wrong?
Technical said:
Do you mean this ROM is intended to be feature-rich like Havoc, Liquid, PixelDust...?
Click to expand...
Click to collapse
Well, we want to make something different from any other ROM, but yes, it will also have plenty of features enough to satisfy everyone, hopefully also reaching my intentions. We intent of bringing 1.0 this fall.
Regards,
hi Guys
I can not install a gapps twrp error 70 otherwise rome runs well and as always with my asus zenfone 5 ze620kl automatic brightness does not work ..
can you please build a rome with gapps.
Thank you
XTutorials said:
Well, we want to make something different from any other ROM
Click to expand...
Click to collapse
What do you mean?
Until May I was able to compile Bootleggers, Havoc and Liquid. Since then, sepolicy and other specific issues are blocking building or booting later. I like featured rich ROMs and I could help to compile Titanium, although my knowledge is not enough to help you, devs.
---------- Post added at 08:19 ---------- Previous post was at 08:14 ----------
barbaross said:
hi Guys
I can not install a gapps twrp error 70
Click to expand...
Click to collapse
In TWRP, just go to Wipe menu > Advanced Wipe > check System partition > Partition options > Resize FS. Then flash Gapps again.
Technical said:
What do you mean?
Until May I was able to compile Bootleggers, Havoc and Liquid. Since then, sepolicy and other specific issues are blocking building or booting later. I like featured rich ROMs and I could help to compile Titanium, although my knowledge is not enough to help you, devs.
Click to expand...
Click to collapse
Well, this ROM can be build as any other ROM, so anyone with some Linux knowledge should be able to build this, as any other ROM.
And soon accepting official maintenance!
mezacorleehone said:
Hello Goodnight.
I previously installed GSI roms.
but now I try to install with the usual procedure
for my G9600 S9
but I can not get into the system
it always stays in the logo and never passes from there.
I already wait more than 25 minutes and nothing.
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be A-only_arm64 Variant)
Unpack it if it wasn't in .IMG format
Wipe DATA, and reboot in TWRP
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Install the kernel for GSI GSI Kernels
In TWRP mount System, then go to ADVANDED, File Manager, and delete this file: system/bin/rw_system.sh
Reboot system
What is wrong?
Click to expand...
Click to collapse
First you need BRK3 vendor , and flash aosp kernel not gsi , the best kernel is Endurance-Kernel-AOSP-1.2.30.zip
First, wipe system data cache and then flash vendor then flash the rom then flash kernel the magisk then reboot ot will work fine , no need to delete rw_system or anything
{
"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"
}
OmniROM
About OmniROM
OmniROM is our Android custom ROM variant, feature-packed but always with stability as #1 priority in mind. Based on the Android Open Source Project (AOSP) and enriched by our developers with lots of custom enhancements, OmniROM has set out to give you a great Android experience on your mobile.
The core of Omni is the community, and we recognize that everyone has a role to play. So we have a number of ways for you to get involved:
Github – our codebase where we build from.
Gerrit – view our project at the code level with the ability to see what’s merged, what’s open and what’s in review.
Forum – participate in general discussion, Q&A, and Features Development on XDA. Also find device-specific builds in their relevant forums on XDA.
Telegram – get connected to the Omni community in realtime on Telegram
Bugs
- You tell me with logs and proper steps to reproduce
Downloads
Grab the latest builds from Official OmniServer
Flashing Instructions
- Boot into my TWRP recovery from here
- Backup each and every partition from TWRP Recovery
- Wipe all partitions as well as format data and internal storage partitions
- Flash OmniROM Package and latest Community Vendor
- Change to other slot
- Flash OmniROM and Community Vendor again
- Wipe Dalvik!
- Reboot to Recovery again and flash GAPPS! [OPTIONAL]
- Reboot to System
Clean Flash is always recommended!
XDA:DevDB Information
OmniROM, ROM for the Nokia 6 (2018)
Contributors
TheImpulson
Source Code: https://github.com/theimpulson/android_kernel_nokia_sdm660
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Must be on Community Vendor
Based On: AOSP
Version Information
Status: Beta
Stable Release Date: 2019-07-14
Created 2019-07-05
Last Updated 2019-08-04
Device Side Sources
PL2 device tree: https://github.com/omnirom/android_device_nokia_PL2
sdm660-common device tree: https://github.com/omnirom/android_device_nokia_sdm660-common
Kernel source: https://github.com/omnirom/android_kernel_nokia_sdm660
vendor source: https://github.com/DonkeyCoyote/proprietary_vendor_nokia
Reserved 2
Pushed a new build. Changelog:
- Enforced SELinux
- Removed OmniDisplayManager
Pushed a new build. Changelog:
- Compile qcacld as driver to drop wlan hacks in device tree
- Remove battery led customizations from OmniGears
- Remove dm-verity hacks
In case your device gives a warning on boot like dm-verity not started in restart mode, please wait 3 seconds before boot and all, remember to enforce it first before flashing this update.
adb reboot "dm-verity enforcing"
Click to expand...
Click to collapse
will do the job!
In case you get an error saying failed to authenticate bootimage or devices keeps looping after enforcing dm-verity, set an active slot again!
fastboot --set-active=a
Click to expand...
Click to collapse
for example will do the job.
Just posted a new build. You guys can check it out. Official weeklies will begin to roll out by weekend. You are also free to give response in our telegram groups.
Posted a new test build. Official builds will begin soon, we all are busy at the moment. Sorry for the delay.
Changelog:
- Enable stock nokia apps support from PlayStore (All credits to @Akilesh_15)
- Addressed a few SELinux denials
- Add common config.fs from CAF
Impressive. This is a great feat. Community should be happy that you put on the best ROM to Official status
Depending on how well this rom works I might just unlock my phone today. Does it have bugs? If so what are they? I'm willing to try it as long as the features I need work. Even if something is broken
Links for official build has been added in thread. Have fun!
zeft64 said:
Depending on how well this rom works I might just unlock my phone today. Does it have bugs? If so what are they? I'm willing to try it as long as the features I need work. Even if something is broken
Click to expand...
Click to collapse
Stable enough to be called as a daily driver I guess. Been using since few weeks, no issues. (Remember I am OP )
TheImpulson said:
Stable enough to be called as a daily driver I guess. Been using since few weeks, no issues. (Remember I am OP )
Click to expand...
Click to collapse
Okay bro. Well looks like I'm going to pay for this bootloader unlock then. Plus it's pretty dope that you gave us adaptable storage. Thanks man!
Can't use sd card.system can find the card, but the applications can't find it.
atmin said:
Can't use sd card.system can find the card, but the applications can't find it.
Click to expand...
Click to collapse
I forgot how to do it but edit your post and mention the dev so that he can see this and fix it. Also include a logcat. If you don't know how to do this you can look it up on YouTube. It's pretty easy.
Thanks very much for your great work on this ROM.
I am trying to install this ROM but receive:
Code:
"Failed to mount '/firmware' (invalid argument)"
This is what I did:
Unlocked bootloader.
Boot into TWRP.
Wiped partitions and format data and internal storage partitions.
Slot A: install OmniROM and Community Vendor.
Switch to Slot B: install OmniROM and Community Vendor then Wipe Dalvik.
But TWRP gives these errors when installing ROM and Vendor on Slot
Code:
"Failed to mount '/firmware' (invalid argument)"
Is this normal to receive this error on Slot B?
And in TWRP if I go into the Mount menu it won't let me select Firmware (if I am in Slot B).
Is it possible to mount /firmware on Slot B?
Mimsly said:
Thanks very much for your great work on this ROM.
I am trying to install this ROM but receive:
Code:
"Failed to mount '/firmware' (invalid argument)"
This is what I did:
Unlocked bootloader.
Boot into TWRP.
Wiped partitions and format data and internal storage partitions.
Slot A: install OmniROM and Community Vendor.
Switch to Slot B: install OmniROM and Community Vendor then Wipe Dalvik.
But TWRP gives these errors when installing ROM and Vendor on Slot
Code:
"Failed to mount '/firmware' (invalid argument)"
Is this normal to receive this error on Slot B?
And in TWRP if I go into the Mount menu it won't let me select Firmware (if I am in Slot B).
Is it possible to mount /firmware on Slot B?
Click to expand...
Click to collapse
Never got this. I hope you are using my TWRP from here. Just to make sure, I will repeat steps.
- boot into TWRP
- Wipe everything, format data afterwards
- Reboot into TWRP, flash vendor and ROM package
- Reboot into TWRP again but on other slot this time and flash back vendor and ROM package.
- Flash GAPPS if you want them else reboot into system.
Always use fastboot to change slot (`fastboot --set-active=a` for example) and adb sideload in TWRP to install any zip you want (`adb sideload omnixxxxx-2019xxx.zip` for example).
atmin said:
Can't use sd card.system can find the card, but the applications can't find it.
Click to expand...
Click to collapse
App name, steps to reproduce and logs please.
zeft64 said:
I forgot how to do it but edit your post and mention the dev so that he can see this and fix it. Also include a logcat. If you don't know how to do this you can look it up on YouTube. It's pretty easy.
Click to expand...
Click to collapse
All music applications can't scan sd card music, but the system can find those, and RE explore can find in Root mode.I will give you some screenshots tomorrow, thanks for your help.
atmin said:
All music applications can't scan sd card music, but the system can find those, and RE explore can find in Root mode.I will give you some screenshots tomorrow, thanks for your help.
Click to expand...
Click to collapse
Define All. I just tried 3 players namely Ganna, Phonograph and Poweramp and all worked fine.
Great Job bro..:good:make it monthly
{
"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:
We're not responsible for bricked devices, dead SD cards, thermonuclear war,
or you get 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 blame me in any way for what happens to your device, I will laugh at you.
BOOM! goes the dynamite
Oh… Really I need to introduce them! .
Team "MSM Xtended" is here with new era of Android.
They have tried their best to blend it with all available options, features and stability of different ROMs in to one for better user experience.
Here
MSM Team
If you like their work you can buy them a cup of coffee:
SuperDroidBond
MSM-Xtended Website
MSM-Xtended Blog
ROM Download
Gapps Download
Magisk Download
For better user experience, it's recommended to flash Nano Gapps only.
Clean Flash
The basic steps for flashing a GSI are:
1. Download the GSI file and uncompress the .7z archive
2. Uninstall Magisk if it was previously installed, by using its uninstaller and reboot the phone
3. Wipe Data, Dalvik, and Cache partitions
4. Flash the GSI to system partition, GApps, and maybe specific files for your phone (see post 2)
5. Boot and perform a minimal setup (enabling USB Debugging as a suggestion)
6. Reboot into recovery and flash Magisk
7. Reboot to system and #GetXtended.
There is more detailed information on GSI and how to flash it on phhusson’s wiki and in his thread here on xda. Also vince31fr brings useful info and workarounds.
Dirty Flash
1. Download the GSI file and uncompress the .7z archive to get the .img file
2. (Optional) Uninstall Magisk if it was previously installed, by using its uninstaller and reboot the phone
3. Wipe Dalvik and Cache partitions
4. Flash the GSI (.img file) to system partition, GApps, and maybe specific files for your phone (see post 2)
5. Boot and perform a minimal setup (enabling USB Debugging as a suggestion)
6. If you uninstall Magisk (step 2), reboot into recovery and flash Magisk
7. Reboot to system and #GetXtended.
If you fail to follow these instructions, please don't bother reporting any bugs
If you use Xposed, please don't bother reporting any bugs
MSM-Xtended Sources
We would like to give thanks to everyone in the Android community, big or small.
That said, we would like to thank all These Teams for their contribution to the Open Source Community.
LineageOS/Cyanogenmod
GZOSP
ColtOS Team & Specially @Rakesh.Batra
OmniROM
Nitrogen OS
AICP
crDroid
DirtyUnicorns
Screwd AOSP
CypherOS
Liquid Remix
Benzo ROM
BootLeggers ROM
AOSP Extended ROM
Syberia-Project
PixelDust Project
Pixel Experience
Contributors: Technical
ROM OS Version: Android 10
Created: 2020-06-21
Issues and workarounds:
1. Check your phone compatibility with Treble before following these instructions.
2. Generally, smart charging feature (Settings > Battery > Smart Charging) does not work on Treble. You can have the same functionality using Battery Charge Limit app.
3. Can't flash Gapps due to error 70 (insufficient storage space available in System partition)? In TWRP, just go to Wipe menu > Advanced Wipe > check System partition > Partition options > Resize FS. Then flash Gapps again. In other recoveries, the steps are similar.
4. To get Viper4Android working on GSI ROMs, please, thank here or the Magisk modules.
5. For RAW support on cameras: Settings > Phh Treble Settings > Misc features > and select Expose Aux cameras (Qualcomm) if possible.
6. You may need to flash the vbmeta.img file specific for your device (firmware) before you first boot the GSI. Discover your actual slot: check in TWRP reboot options or in fastboot mode: fastboot getvar current-slot. Then run in the same slot you're flashing the GSI image:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
7. If you lose Wi-Fi and/or Bluetooth, you should flash the dtbo.img file specific for your device (firmware). Discover your actual slot: check in TWRP reboot options or in fastboot mode: fastboot getvar current-slot. Then run in the same slot you're flashing the GSI image:
For A/B devices, run:
fastboot flash dtbo_a dtbo.img
or
fastboot flash dtbo_b dtbo.img
For A-only devices, run:
fastboot flash dtbo dtbo.img
8. Additional files as Permissiver v5 and DM-verity, forced encryption, and disc quota disabler must be needed to boot.
Thanks
Gheartxz2017 said:
Thanks
Click to expand...
Click to collapse
If it works, please, give me feedback
Hi, is based in phh v220?
Os_Herdz said:
Hi, is based in phh v220?
Click to expand...
Click to collapse
It has all the latest phh patches that I manage to apply without breaking the gsi. Shortly, yes.
Technical said:
If it works, please, give me feedback
Click to expand...
Click to collapse
Only stay in bootanimation I flash permissiver but doesn't work
Not boot[emoji24]
Gửi từ SM-G610F của tôi bằng cách sử dụng Tapatalk
Thanks for the feedback. I'll need to figure out what happened. It will take a while
No build with gapps installed?
Technical said:
It has all the latest phh patches that I manage to apply without breaking the gsi. Shortly, yes.
Click to expand...
Click to collapse
Bootloop in bootanimation, tried enforce, tried permissive and with magisk but no booted. The bootanimation is really good.
Stucks at bootanimation ! Waiting a boot fix ! I love Xtended ROM.
muhamet said:
No build with gapps installed?
Click to expand...
Click to collapse
Probably not, it takes a lot of space and time to build (compared to vanilla versions). I have limited resources and it's being very challenging even to boot Gapps are not the focus right now.
Technical said:
Probably not, it takes a lot of space and time to build (compared to vanilla versions). I have limited resources and it's being very challenging even to boot Gapps are not the focus right now.
Click to expand...
Click to collapse
Do you find a solution to boot please ?
Dan225 said:
Do you find a solution to boot please ?
Click to expand...
Click to collapse
Not yet. Trying not to give up
Technical said:
Not yet. Trying not to give up
Click to expand...
Click to collapse
No solutions?
Technical said:
Not yet. Trying not to give up
Click to expand...
Click to collapse
Hi got my device back from the dead after a long time (nubia z17 8gb128gb )but now the world got android 10 even my device (lineage os 17.1 offical) for me:good:
But i dont have even manage to get a gsi to boot (except android 11 R aosp) can you give me a tip?
Guys, I'm trying to bring back camera to work in crDroid and EvolutionX. Both are booting ok.
MSM-Xtended revelead a much more difficult ROM to build. If I find the way to bring back a working camera there, probably it'll be easier to move there. There is no features on MSM that are missing on EvolutionX, for instance.
And I won't have time and resources (disk space) for a 3rd GSI.
On latest Phh build?
Technical said:
MSM-Xtended revelead a much more difficult ROM to build. If I find the way to bring back a working camera there, probably it'll be easier to move there.
Click to expand...
Click to collapse
May be it will help - https://4pda.ru/forum/index.php?showtopic=892755&view=findpost&p=94999066
Quote from next message on 4pda:
Igor~s said:
ROM is built with the settings to increase the system speed and system services optimization.
Click to expand...
Click to collapse
{
"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/12.0/README.mkdn
Flashing Instructions:
Pre-installation:
gapps : Nikgapps and Flamegapps are both tested
Magisk 23.0 for root (after first boot) - (Download from here)
First time installation:
make use of 3.6.0_11-RedmiK30Pro_v3.0.3_A12-lmi-skkk_0b4ac24c.img or your preferred one
boot recovery
format & reboot recovery
flash Firmware (minimum requirement 12.5.3) (skip if you are on 12.5.3 or later)
flash crDroid
reboot recovery
(optional) flash Gapps
(optional) flash Magisk
boot system
Update installation: (if on cr8 already)
boot recovery
flash crDroid
boot system
Sources:
ROM: https://github.com/crdroidandroid
Device Trees: lmi + common
Kernel: Quantic kernel thx @GtrCraft
Download:
ROM: LMI
Changelog: LMI
LATEST BUILD AND INSTRUCTIONS
Known issues:
...
ROM OS Version: 12.0
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader, min. miu v12.5.x
Status: stable
Sec. Patches : 2023.03.05
Created : 2022.01.18
Last Updated : 2023.03.23
Thnx to :
@Schnedi
@Ayrton990
Visit official website @ crDroid.net
crDroid LMI Telegram
crDroid Community Telegram
crDroid Updates Channel
Donations are appreciated to continue development
Changelog: LMI
Thx boss !!!!!
This is one of the ROMs that I've been anticipating to have an A12 update. Thank you for keeping lmi alive!
Does VOLTE work here?
Can someone please confirm if the low microphone volume recording bug for WhatsApp voice notes etc is present on this rom, like it is for the A11 crdroid?
Hi to all of you!
Great ROM with all the great looks and feel but as in 7.13 version I am not able to get the mobile data to work...
Anyway, big thanks to the developers for all the effort!
lafa011 said:
Hi to all of you!
Great ROM with all the great looks and feel but as in 7.13 version I am not able to get the mobile data to work...
Anyway, big thanks to the developers for all the effort!
Click to expand...
Click to collapse
Have you tried manually setting up the APN in Settings?
I was looking forward to this update, Thanks for your hard work!
I'm facing a bootloop problem for some reasons...
I once successfully installed it, but realized NikkGapp didn't use my config, so I went back into TWRP to run it again and use my config.
I didn't realized it at this time (now I know), but TWRP didn't ask for any pattern unlock. The sd-card wasn't detected, so I tried a couple of things to solve it, and this is where it starts to get problematic. I did the sd-card switch from ext2 to ext4.
From that point, I got into a boot loop. I tried to flash the CrDroid rom again, but it won't work.
I then flashed the global original image to start fresh, but TWRP still won't ask for pattern to unlock, thus doing the flashing again didn't work...
Do you have any idea how I can fix it? I'm back on MIUI and I already miss CrDroid
woodencase01 said:
I was looking forward to this update, Thanks for your hard work!
I'm facing a bootloop problem for some reasons...
I once successfully installed it, but realized NikkGapp didn't use my config, so I went back into TWRP to run it again and use my config.
I didn't realized it at this time (now I know), but TWRP didn't ask for any pattern unlock. The sd-card wasn't detected, so I tried a couple of things to solve it, and this is where it starts to get problematic. I did the sd-card switch from ext2 to ext4.
From that point, I got into a boot loop. I tried to flash the CrDroid rom again, but it won't work.
I then flashed the global original image to start fresh, but TWRP still won't ask for pattern to unlock, thus doing the flashing again didn't work...
Do you have any idea how I can fix it? I'm back on MIUI and I already miss CrDroid
Click to expand...
Click to collapse
After getting bootloops from installing different roms I learned this: disable the screen lock (Settings->Security->Screen lock->None) before flashing anything. This way TWRP should be able to mount the partitions
thetta-reddast said:
After getting bootloops from installing different roms I learned this: disable the screen lock (Settings->Security->Screen lock->None) before flashing anything. This way TWRP should be able to mount the partitions
Click to expand...
Click to collapse
Thanks for your help.
I disabled the screen lock, but sadly it didn't work.
I get errors messages such as:
I:File Based Encryption is present
fscrypt_init_user0 returned fail
fscrypt_init_user0 returned fail
fscrypt_init_user0 returned fail
Unable to decrypt FBE device.
If your device is not encrypted, decrypting the FEB device will fail.
E:fde::get_crypt_ftr_and_key::Unexpected value for crypto key location:
E:Error getting crypt footer and keyE:Could not get footerDecrypt process ended with signal: 11
Failed to decrypt data.
Unable to decrypt with default password. You may need to perform a Format Data.
and
Android Rescue Party trigger! Possible solutions? Either:
1. Wipe caches, and/or
2. Format data, and/or
3. Clean-flash your ROM.
The reported problem is:
'set_policy_failed:/data/system'
Not sure what to do...
I tried changing the data format to ext4, then format it through ADB, didn't work.
My current error message is "init_user0_failed". I also still have the "Rescue Party trigger!" message.
EDIT:
I managed to boot by formatting DATA after flashing, but the OS seems to be missing a lot of stuff.
EDIT 2:
Ok, started the clean flashing process again, still got in bootloop. Tried formatting data again, and it worked!
batuken said:
Have you tried manually setting up the APN in Settings?
Click to expand...
Click to collapse
Thank you for your reply. I did not try changing the APN settings but tried MIUI stable 12.2.6.0 needed for flashing the 7.13 crDroid and it works there out of the box. Maybe changing the APN would work but I gave up and get back to EU version instead, which is ok for me except for custom launcher like Nova since I cannot get around the home buttons appearing/dissapearing when I use gestures with Nova launcher... That was the first thing that led me to trying crDroid
Спасибо за ROM!!!
----------
MOD EDIT: English Translation Below
Thanks for the ROM!!!
tell me from which version of MIUI you need to flash crdroid 8
Can anyone confirm wether crdroid has issues with high security apps requiring "official" builds?
For example the Danish verification service MitID (https://play.google.com/store/apps/details?id=dk.mitid.app.android)
App would open to only display that "device is rooted" on Spark A12 rom...
Lyngze said:
Can anyone confirm wether crdroid has issues with high security apps requiring "official" builds?
For example the Danish verification service MitID (https://play.google.com/store/apps/details?id=dk.mitid.app.android)
App would open to only display that "device is rooted" on Spark A12 rom...
Click to expand...
Click to collapse
I have the same problem with our COVID app, I simply flashed Magisk, then once I'm in the OS, you can install MagiskHide, it also works for Google Pay on rooted phones. Make sure to clear the app cache when activating MagiskHide, otherwise the message about the rooting will stay.
woodencase01 said:
I have the same problem with our COVID app, I simply flashed Magisk, then once I'm in the OS, you can install MagiskHide, it also works for Google Pay on rooted phones. Make sure to clear the app cache when activating MagiskHide, otherwise the message about the rooting will stay.
Click to expand...
Click to collapse
This was without root. Google Pay and other banking apps and such worked. But a few had some extra checks apart from SafetyNet and such.
I would rather not root and mess with magisk if it could be avoided.
I don't have any need for root and would rather not install too much third party stuff with potential security risks.
Did Google Pay not work for you without root and magisk hide either?
I'm currently using "NikGapps-full-arm64-12-20211227-signed" as GAPP, but sadly, chrome keeps freezing. I'm currently using a different browser. Has anyone a fix for this?
Lyngze said:
This was without root. Google Pay and other banking apps and such worked. But a few had some extra checks apart from SafetyNet and such.
I would rather not root and mess with magisk if it could be avoided.
I don't have any need for root and would rather not install too much third party stuff with potential security risks.
Did Google Pay not work for you without root and magisk hide either?
Click to expand...
Click to collapse
My device is rooted since day one. I don't know how to flash a custom ROM without first rooting.
But yes, without MagiskHide, I couldn't use Google Pay. Haven't found another way to make it work.