{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
GPL compliance:
Device tree source code: LineageOS/android_device_xiaomi_beryllium
Kernel source code: LineageOS/android_kernel_xiaomi_sdm845
Working:
Camera (and flashlight)
WiFi
Bluetooth
Telephony (Calls and Data)
IMS (RCS, VoLTE and WiFi Calling)
Audio (Record and Playback)
Video Playback
Sensors
GPS
Encryption (FBE)
WiFi Display
Broken:
Nothing (?)
Compatibility:
Compatible with all Xiaomi Poco F1 variants.Builds are based off the Xiaomi's Android 10 firmware with proprietary blobs from MIUI v12.0.3.0 global stable package.
Device wiki:
Official wiki link
Downloads:
Official download links
Installation:
Follow instructions found in the respective wiki page
Is this a System-Ext-Rom?
Chris_Kaos79 said:
Is this a System-Ext-Rom?
Click to expand...
Click to collapse
Yes
Read the upgrade instructions, had to sadly ignore them because i no longer have a cable/port/adb combo that allows adb to sideload successfully (i just get errors when he starts to transmit).
EDIT [i am lying, adb works but fastboot does not]
So i remained on the Reignz TWRP, and from a recent LOS 19.1:
- flash LOS 20
- flash MindTheGapps 13
- flash Magisk
- flash NGK kernel
- Wipe dalvik/cache
- reboot system
-> Bootloop. Well theoretically this must work, so maybe try less at once? I did see that Magisk re-flashed itself automatically in TWRP, so attempt 2:
- flash LOS 20
[Magisk automatically reflashes itself]
- flash MindTheGapps 13
- reboot system
Works now.. but i am always eager to ruin myself so i will try to reflash NGK now.
EDIT: Yup NGK+TWRP causes bootloop. I will reflash LOS20 again ... and try LOS recovery with NGK maybe.
EDIT2: LOS recovery with NGK bootloops also. Stock kernel it is.
EDIT3: Working good with stock kernel. Magisk works, camera works, banking and auth apps work. Thank you
Another oddity: The updater app immediatly came up and recommended i upgrade to the LOS20 i just flashed. Uh huh?
I updated to LOS 20 via dirty flash from LOS 19.1 (following the official procedure: https://wiki.lineageos.org/devices/beryllium/upgrade)
It worked flawlessly!
AtomicStryker said:
Read the upgrade instructions, had to sadly ignore them because i no longer have a cable/port/adb combo that allows adb to sideload successfully (i just get errors when he starts to transmit).
EDIT [i am lying, adb works but fastboot does not]
So i remained on the Reignz TWRP, and from a recent LOS 19.1:
- flash LOS 20
- flash MindTheGapps 13
- flash Magisk
- flash NGK kernel
- Wipe dalvik/cache
- reboot system
-> Bootloop. Well theoretically this must work, so maybe try less at once? I did see that Magisk re-flashed itself automatically in TWRP, so attempt 2:
- flash LOS 20
[Magisk automatically reflashes itself]
- flash MindTheGapps 13
- reboot system
Works now.. but i am always eager to ruin myself so i will try to reflash NGK now.
EDIT: Yup NGK+TWRP causes bootloop. I will reflash LOS20 again ... and try LOS recovery with NGK maybe.
EDIT2: LOS recovery with NGK bootloops also. Stock kernel it is.
EDIT3: Working good with stock kernel. Magisk works, camera works, banking and auth apps work. Thank you
Another oddity: The updater app immediatly came up and recommended i upgrade to the LOS20 i just flashed. Uh huh?
Click to expand...
Click to collapse
NGK has some problems for now, wait for update or use orange fox...
AtomicStryker said:
Read the upgrade instructions, had to sadly ignore them because i no longer have a cable/port/adb combo that allows adb to sideload successfully (i just get errors when he starts to transmit).
EDIT [i am lying, adb works but fastboot does not]
So i remained on the Reignz TWRP, and from a recent LOS 19.1:
- flash LOS 20
- flash MindTheGapps 13
- flash Magisk
- flash NGK kernel
- Wipe dalvik/cache
- reboot system
-> Bootloop. Well theoretically this must work, so maybe try less at once? I did see that Magisk re-flashed itself automatically in TWRP, so attempt 2:
- flash LOS 20
[Magisk automatically reflashes itself]
- flash MindTheGapps 13
- reboot system
Works now.. but i am always eager to ruin myself so i will try to reflash NGK now.
EDIT: Yup NGK+TWRP causes bootloop. I will reflash LOS20 again ... and try LOS recovery with NGK maybe.
EDIT2: LOS recovery with NGK bootloops also. Stock kernel it is.
EDIT3: Working good with stock kernel. Magisk works, camera works, banking and auth apps work. Thank you
Another oddity: The updater app immediatly came up and recommended i upgrade to the LOS20 i just flashed. Uh huh?
Click to expand...
Click to collapse
I know this is off-topic, but I guess you used Reignz V3.6.2 that he tested for A13 support?
Interesting that apparently A13 again uses other encryption than A12? I though now with A13 FBE would be the new standard but there is something new again?
So official 3.7.0 TWRP will not work with A13 I guess.
Looking forward to jump to A13 this weekend based on all the positive feedback so far - thank you bgcngm for your hard work!
hello there,
I've just dirty flashed LOS20, and I'm having problems connecting anything via bluetooth, any idea how to fix this without clean installing?
Another question, I'm using MindTheGapps 13 as recommended here, but I was looking for something the minimum google services, do you think I can use NikGapps?
Thanks
alright, I couldn't fix it, I had it reinstalled clean. Everything is working nicely and the new camera is a very welcome improvement.
I'm still facing issues with bluetooth though. I'm able to use it and connect normally, but when listening to audio, it seems that the connection is weak, and I can often hear cuts in the connection, or noise. Anyone having the same?
AtomicStryker said:
EDIT: Yup NGK+TWRP causes bootloop. I will reflash LOS20 again ... and try LOS recovery with NGK maybe.
EDIT2: LOS recovery with NGK bootloops also. Stock kernel it is.
Click to expand...
Click to collapse
This problem is a known issue since the day before yesterday. Several people are experiencing this with the upgrade from 19.1 to 20. For now, running the stock kernel should be fine.
Installation GuidesOfficial way of installation can be found at OP.
Installation Guides:
Clean Install via TWRP:
Backup your data to PC or SDCard if you have.
Downland:
Spoiler: These files
- TWRP by REIGNZ v2 [twrp-beryllium-v3.7.0-A12-V2.img] - [Current Bugs/Issues & Workarounds]
- Latest build of Official LineageOS ROM and optional LineageOS Recovery from the same link, if you want to flash that later.
- Optional A13 GApps of your choice.
Boot, flash and reboot to TWRP. [Check Install Custom Recovery Guide]
Select Wipe > Advanced Wipe -> Select Dalvik / ART Cache, System, System_EXT, Data, Internal Storage, Vendor, Cache and then Swipe to Wipe.
Reboot to recovery once again (needed due to a current issue with TWRP by REGINZ) and then Format data > type yes.
Transfer the files you previously downloaded into Internal Storage, while you are connected and into TWRP from PC to your Device. If you have SDcard or USB OTG you can also use that.
[TWRP by REIGNZ have an issue, if PC doesn't recognize the device, press in twrp menu, Advanced > File Manager > and find and select sdcard folder aka Internal Storage > go back and now your pc should be able to recognize the device]
Flash ROM > GApps. NOTE: ROM IS FORCE ENCRYPTED
[Optional] Flash LineageOS recovery by pressing "Install Image > Navigate and Select the LineageOS Recovery > Flash it to recovery partition.
Reboot and Enjoy!
[Optional] In case you want to change Kernel to NGK or SC [SE version - aka System_Ext], flash it after the first boot of the ROM.
[Optional] In you case you want Root, flash Magisk after the first boot of the ROM.
SafetyNet & Certified Play Store:
Official LineageOS doesn't pass SafetyNet or have certified Play Store by default. [Read here why]
Root your device with Magisk and Follow this Guide (or this) to pass SafetyNet and have certified Play Store. [YouTube Video Guide]
OTA Upgrade/Update:
Warning
Only use OTA if you are encrypted. Simply go to updater and press install, everything will be automatic.
Dirty Installation via TWRP:
{Manually Upgrade/Update the ROM}
Download:
Spoiler: These files
- TWRP by REIGNZ [twrp-beryllium-v3.7.0-A12.img] - [Current Bugs/Issues & Workarounds]
- Latest build of Official LineageOS ROM and optional LineageOS Recovery from the same link, if you want to flash that later.
- Optional A13 GApps of your choice.
Wipe System, System_Ext, Dalvik ART/ Cache, Cache, Vendor.
Flash ROM > GApps > [Optional]Magisk.
Reboot and Enjoy!
Notes:
If you want to flash DFE use TWRP by REIGNZ based on A9. (not A12) [Not recommended be decrypted]
If you encounter Fastboot issues read the guide/fix in my thread.
You can translate the ROM in Crowdin.
Check my threads:
Spoiler: My threads
- POCO F1 Ultimate Collection & Guides
- Android Ultimate Collection & Guides
- ReVanced & ReVanced Extended - Guides & Useful Links
- Windows Ultimate Collection & Guides
pmcmm said:
I'm still facing issues with bluetooth though. I'm able to use it and connect normally, but when listening to audio, it seems that the connection is weak, and I can often hear cuts in the connection, or noise. Anyone having the same?
Click to expand...
Click to collapse
I had to unpair my existing bluetooth devices and re-pair them, (presumably because the upgrade changed the phones bluetooth ID) but it seems to work perfectly for me.
- I am on this ROM since 01.01, no major issues so far.
- Just FYI, DFE zip (Disable Force Encryption) from Retrial collection doesn't seem to work on this ROM. For the sake of testing, I tried both A13 DFE and the older zip (which worked on LOS19.1) with clean installations. When I check in the settings, the phone was encrypted every time, no matter what I do.
- On the other hand, I can report that unofficial TWRP A12 by Reignz (twrp-beryllium-v3.7.0-A12.img) can decrypt storage on LOS20.
- One small glitch I found: If I lit up the screen (press power button) while charging, the phone stays on the lockscreen with the display on, never turning off by itself. Of course if I press power button or double tap I can turn it off. Also if I just disconnect power cable, display turns off in few seconds like it should. But if I just press power once and leave it, it will stay on the lockscreen forever.
- Bluetooth is fully working for me. I am using 2 different BT headsets for few hours every day. Not a single issue so far.
marsa47 said:
- Just FYI, DFE zip (Disable Force Encryption) from Retrial collection doesn't seem to work on this ROM. For the sake of testing, I tried both A13 DFE and the older zip (which worked on LOS19.1) with clean installations. When I check in the settings, the phone was encrypted every time, no matter what I do.
- On the other hand, I can report that unofficial TWRP A12 by Reignz (twrp-beryllium-v3.7.0-A12.img) can decrypt storage on LOS20.
Click to expand...
Click to collapse
The DFE not seem to working with the TWRP by REIGNZ based on A12. Instead you should try to flash DFE via TWRP by REIGNZ but based on A9.
The purpose of A12 based twrp is to decrypt A12+ encrypted ROMs. If you don't need encryption (which I recommend everyone to use encryption), then use TWRP by REIGNZ A9 and flash DFE.
any way to get F2FS working ? With flashed fstab i get recovery reboot and without i get a bootloop
Is it important to fastboot the required xiaomi firmware first? Coming from 19.1.
MagnesG said:
Is it important to fastboot the required xiaomi firmware first? Coming from 19.1.
Click to expand...
Click to collapse
I assume u already have it. No need.
noah001 said:
any way to get F2FS working ? With flashed fstab i get recovery reboot and without i get a bootloop
Click to expand...
Click to collapse
Flash a kernel with with f2fs support,
Do "long loading while taking picture from whatsapp-bug" still occurred????
123r4ka456 said:
Do "long loading while taking picture from whatsapp-bug" still occurred????
Click to expand...
Click to collapse
I get the following behavior:
1st try: click on photo button: nothing happens (but no hang)
2nd try: click on photo button: photo is immediately taken and can be sent, no hang
So: not really running without issues, but no hang
Maybe this is helpful
Related
ROM thread text:
This is crDroid for 5.5" Pixel XL [marlin]
crDroid Website: https://crdroid.net/
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. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"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"
}
Features
Click for feature list (helps shorten the OP.)
Always Have a full functional Backup. Just in case!
DOWNLOAD ROM
Vendor image for current build - OPM4 July vendor image - DOWNLOAD VENDOR
GAPPS: For now, open gapps unofficial, also courtsey @razorloves - DOWNLOAD GAPPS
OpenGapps: Not Supported anymore, use @razorloves gapps.
First time installing crDroid to your PixelXL, or coming from another ROM:
**NOTE** As you probably know by now, marlin (and sailfish) is weird. You must be on TWRP 3.2.0.0 to install this! 3.2.1.0 does not allow ROM installation. 3.2.0.0 does not encrypt properly, so you must remove your PIN/password before booting to and / or installing it. These installation instructions will assume you already know and have done that.
**NOTE** You are also able to use 3.2.1.-2 (3.2.0.0 or 3.2.1.-2)(Nothing in between)
** Make sure you're running a proper working Recovery (CWM or TWRP)
1) Copy crDroid zip, gapps zip & vendor img to your device
2) Boot into Recovery
3) Wipe cache, system, & data (or just cache & system for a dirty flash).
4) Flash ROM
5) Flash TWRP ***If you do not do this, you will lose TWRP!***
6) Reboot back into TWRP
7) Flash vendor image
7a) Mount vendor partition, navigate to vendor/overlay and delete that folder
8) Flash gapps
9) Boot up
For root, AFTER you boot into the ROM, you can go back to recovery and install Magisk 16.2
If you like music like I do and want to make it better, see post #3 for instructions on installing ViPER4Android.
Instructional Video
I Apologize about video quality, but this will help get you an idea of the steps involved.
Steps are the same for Marlin and Sailfish. Use corresponding files for device.
https://youtu.be/mmxIrp7BiRk
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
KNOWN ISSUES
None yet, If you find something that is consistently reproducible, do so and pull a log. Without logs, we cannot fix the bugs. Please report any that you run into, assuming you have tested on a clean install. :good:
NOTE ON SUBSTRATUM
We currently do not have substratum commits in the ROM because they have not updated their repos on git for Oreo. As such, if you want to use Substratum, you will be doing so by allowing root and using legacy mode. you -must- make sure whatever theme you try supports 8.1. Even some that say they support Oreo may only work with 8.0, not 8.1. I'd recommend the following:
Suggestion: whenever installing themes, remove your pin/password so you can get TWRP to mount data.
If you get in a FC/bootloop situation, boot to TWRP, mount data and remove the file /data/system/overlays.xml.
That should allow you to boot and uninstall the overlays without reinstalling anything.
Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed!
- have modified system files
Thanks to:
- @razorloves - Without his device tree and kernel bringup to work from, crDroid for marlin would not be possible at all. Apart from the ROM development itself (for which @neobuddy89 bears the largest burden, in addition to the great developers of LineageOS itself), credit for this ROM being able to even build goes to razorloves.
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
DONATE
crDroid G+ community
Source Code:
Device tree: https://github.com/razorloves/android_device_google_marlin
Kernel tree: https://github.com/razorloves/android_kernel_google_marlin
Vendor tree: https://github.com/razorloves/proprietary_vendor_google
Credit for all of those trees goes to @razorloves , without whose work crDroid for marlin would be a shell of itself!
XDA:DevDB Information
[ROM] [marlin] [8.1] [LOS-based] **crDroid**v4.7, ROM for the Google Pixel XL
Contributors
hokiealumnus, neobuddy89, BHermes21, razorloves
Source Code: https://github.com/crdroidandroid
ROM OS Version: 8.x Oreo
Version Information
Status: Nightly
Current Stable Version: v4.0
Stable Release Date: 2018-03-23
Beta Release Date: 2018-01-19
Created 2018-01-09
Last Updated 2018-10-12
I already said it in my post above, but feel it needs repeating. HUGE thanks to @razorloves , without whose marlin bring-up this ROM would still not be built.
*** NOTE - We cannot actively support audio (or any other) mods. I'm posting this because it works for me and I use it personally. This is not supported by our ROM team. Only the ROM / vendor / gapps and nothing else is supported by the crDroid development team. ***
If you like music as much as I do and prefer to use Viper4Android, install it as follows:
0) This requires Magisk; install Magisk 15.2 (as of 1/9/2018)
1) Using a root explorer (I prefer FX File Explorer), navigate to /system/system/priv-app/AudioFX and rename AudioFX.apk to AudioFX.BAK. Reboot.
2) Install three Magisk modules:
a) Magisk SELinux Permissive Script (Get it here: https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549)
b) Busybox for Android NDK v1.27.2 by osm0sis (Get it from Magisk downloads in the Magisk app)
c) ViPER4Android FX v2.8 by ahrion, zackptg5 (Also from Magisk downloads)
3) Reboot.
4) Enjoy your better music!
Sweet thanks
Awesome! I know I asked this on the nougat version, does the unlimited photo storage work? I noticed on the unofficial LOS rom by @razorloves it's been enabled, but I wanted to confirm. I'm still running nougat because I've been waiting for an oreo rom that has DUI.
hokiealumnus said:
This is crDroid for 5.5" Pixel XL [marlin]
If you're looking for the 5" Pixel [sailfish], it is not built yet; sorry.
Click to expand...
Click to collapse
Yet...... Hahaha there's still hope! Thanks for your work as always man. crDroid on N was solid as it gets!
Awesome thank you. Flashing now
Akomack said:
Awesome! I know I asked this on the nougat version, does the unlimited photo storage work? I noticed on the unofficial LOS rom by @razorloves it's been enabled, but I wanted to confirm. I'm still running nougat because I've been waiting for an oreo rom that has DUI.
Click to expand...
Click to collapse
It -says- it does in Photos. However, it said it did in Nougat, but never did actually work in any LOS / LOS-based ROM. It took up storage space even though the Photos app said back up all you want with Pixel. Therefore I can't promise full functionality. The app does say it works though.
thebigdonny said:
Yet...... Hahaha there's still hope! Thanks for your work as always man. crDroid on N was solid as it gets!
Click to expand...
Click to collapse
No promises on a time frame though I'm sorry to say!
hokiealumnus said:
No promises on a time frame though I'm sorry to say!
Click to expand...
Click to collapse
Soon TM
Added instructions for using Viper4Android in the 3rd post while they're still working on a functioning ARISE.
Works very good only one force close which I just uninstalled and reinstalled anyway been running du 12.0 nice change thanks
hokiealumnus said:
If you like music as much as I do and prefer to use Viper4Android, install it as follows:
0) This requires Magisk; install Magisk 15.2 (as of 1/9/2018)
1) Using a root explorer (I prefer FX File Explorer), navigate to /system/system/priv-app/AudioFX and rename AudioFX.apk to AudioFX.BAK. Reboot.
2) Install three Magisk modules:
a) Magisk SELinux Permissive Script (Get it here: https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549)
b) Busybox for Android NDK v1.27.2 by osm0sis (Get it from Magisk downloads in the Magisk app)
c) ViPER4Android FX v2.8 by ahrion, zackptg5 (Also from Magisk downloads)
3) Reboot.
4) Enjoy your better music!
Click to expand...
Click to collapse
Bruh, gimme the credit, if u want atmos and any other mod for 8.1 here's the link https://forum.xda-developers.com/pixel-xl/how-to/guide-ultimate-audio-battery-guide-t3727124/page1
kingbri said:
Bruh, gimme the credit, if u want atmos and any other mod for 8.1 here's the link https://forum.xda-developers.com/pixel-xl/how-to/guide-ultimate-audio-battery-guide-t3727124/page1
Click to expand...
Click to collapse
Why would I give you credit? I've never even seen that post.
Are there any custom kernels that will work with this ROM right now?
Sent from my Pixel XL using Tapatalk
@hokiealumnus After flashing Rom and Twrp, then I hit reboot to recovery, its says "No OS Installed" on the reboot screen. Is that normal?
*Update*
For those of you that get stuck at this point and run into bootloops, instead of Wiping Cache, System & Data manually, just simply hit "Factory Reset" instead. and continue with OP's flashing instructions and you should be good.
Thanks so much, Hokie! Packed with features, really appreciate all of the detailed instructions! Thank you!
Herk718 said:
@hokiealumnus After flashing Rom and Twrp, then I hit reboot to recovery, its says "No OS Installed" on the reboot screen. Is that normal?
Click to expand...
Click to collapse
Yes that is normal
Herk718 said:
@hokiealumnus After flashing Rom and Twrp, then I hit reboot to recovery, its says "No OS Installed" on the reboot screen. Is that normal?
Click to expand...
Click to collapse
Yep normal.
Reboot recovery. Flash gapps/vendor reboot.
Giving this a whirl. Thanks OP!!!
Herk718 said:
@hokiealumnus After flashing Rom and Twrp, then I hit reboot to recovery, its says "No OS Installed" on the reboot screen. Is that normal?
*Update*
For those of you that get stuck at this point and run into bootloops, instead of Wiping Cache, System & Data manually, just simply hit "Factory Reset" instead. and continue with OP's flashing instructions and you should be good.
Click to expand...
Click to collapse
Aye, that is normal. It just means you don't have vendor installed, which you can't do until rebooting back to TWRP (so it switches slots).
Factory reset does not wipe system partition. If you are coming from a different ROM, when you switch slots, you are leaving a different ROM on your inactive slot. Not a huge deal, but I don't recommend it.
Edit - The best way to avoid stressing about that is to allow the reboot, but interrupt boot (pwr + vol down), and go right to recovery from the bootloader.
BHermes211 said:
Are there any custom kernels that will work with this ROM right now?
Click to expand...
Click to collapse
Maybe? I haven't tried installing one yet. ElementalX has always worked well in the past, indeed I always built nougat crDroid with it. Just haven't tried it on Oreo.
If you want to try installing it, worst it will do is bootloop. Just dirty flash (wipe only cache/system, leave data, repeat normal install) back to the included kernel.
OrangeFox Recovery
Replace TWRP with OrangeFox once and you won't go back
Last update: 22 November 2020. Build 2
Changelog:
- Updated Magisk to 21.1 (now clicking install magisk after rom installation will install magisk 21.1)
- Update Magisk uninstaller to latest build
- fixed a bug where some people couldn't use flashlight option inside recovery
- fastened things up for faster installations and backup
- minor bug fixes
Contents:
Overview
Why OrangeFox?
Features
Screenshots
Links
Installation procedure
OVERVIEW:
Probably the most beautiful recovery out there.
Synced with the latest Teamwin changes.
Designed with latest Material design 2 guidelines.
Included customization.
Inbuilt patches, like Magisk and password reset patch.
Password protection.
Fully open-source.
Frequently updated.
Why OrangeFox?
OrangeFox has been operating for over two years. In that time OrangeFox have improved the quality, stability, and device support of the recovery. Today OrangeFox is the leader in stability, UI design, and UX. Installing OrangeFox means being with the latest code and fastest fixes.
:good: Treble & Non-Treble Support
:good: No compatibility.zip error while flashing OxygenOS
:good: A lot of customisations
:good: Extremely beautiful UI ready to please your eyes.
:good: Dev team is always ready to fix your problems
:good: F2FS support
There were previously 10.1 builds for these devices for these devices and this is how current build is different from them:
New, more modern UI.
Fixed F2FS support
Upstreamed to R11
and many more...
Note: Official soon I've applied for it.
Screenshots
Screenshots at https://imgur.com/a/Ai8KWX9 and on Sourceforge
Links:
Support group: https://t.me/orangefoxop5t
Download: https://github.com/Maitreya29/OrangeFox-OnePlus-5-T/releases
Installation procedure:
There are two methods to install OrangeFox
A) Via a recovery (for those with TWRP installed):
1. To install an OrangeFox zip, flash it with OrangeFox (or any TWRP-compatible custom recovery) without any wipes.
2. Do the same thing if you want to upgrade OrangeFox
3. When you flash an OrangeFox zip, there is no need to flash any DFE or any other such thing
4.To install an OrangeFox img file, boot into fastboot mode, and run the command: fastboot flash recovery OrangeFox-xyz.img
B) Via Fastboot (For those without a recovery):
You need a PC for this. If you do not have a PC, or access to a PC, then you are stuck!
1. Unlock your bootloader (if not already unlocked)
2. Install adb, fastboot and the relevant USB drivers onto your PCs)
3. Download the correct OrangeFox zip file to your phone, and to your PC
4. Extract recovery.img from the OrangeFox zip file, and copy recovery.img to your PC’s adb directory
5. Reboot your phone into fastboot/bootloader mode
6. Open up a command line window / terminal emulator on your PC
7. Change to the adb directory on your PC
8. Flash OrangeFox Recovery by using the fastboot flash recovery recovery.img command
9. Reboot into OrangeFox by pressing the power + volume down keys, until you see the OrangeFox splash screen
11. After OrangeFox has booted up, check that everything is working – eg, that it has mounted the data partition successfully, and that the touchscreen works.
12. Find and select the OrangeFox zip on your phone, tap on it, and swipe to install it (because OrangeFox Recovery needs some files from the zip)
After installation, the phone will automatically reboot into OrangeFox
Enjoy!
The download link at SourceForge is broken. It keeps redirecting to the devices folder.
sukesh1090 said:
The download link at SourceForge is broken. It keeps redirecting to the devices folder.
Click to expand...
Click to collapse
Thanks. Download link fixed.
Last update: 22 November 2020. Build 2
Changelog:
- Updated Magisk to 21.1 (now clicking install magisk after rom installation will install magisk 21.1)
- Update Magisk uninstaller to latest build
- fixed a bug where some people couldn't use flashlight option inside recovery
- fastened things up for faster installations and backup
- minor bug fixes
Last update: 22 November 2020. Build 2
Changelog:
- Updated Magisk to 21.1 (now clicking install magisk after rom installation will install magisk 21.1)
- Update Magisk uninstaller to latest build
- fixed a bug where some people couldn't use flashlight option inside recovery
- fastened things up for faster installations and backup
- minor bug fixes
Love the effort put into this! Fantastic choices for new and old users. Good job on the recovery. Looks stunning I'm sure you already knew that though.
Mr.Conkel said:
Love the effort put into this! Fantastic choices for new and old users. Good job on the recovery. Looks stunning I'm sure you already knew that though.
Click to expand...
Click to collapse
Haha thank you
Hello, does password encryption work with Android 11? Do you know or I should try and let you know? Recovery seems very nice. First time I changed from TWRP and I think I'll stay. Good Job!!
Edit: I know it says "Password Protection" in the main post. What I meant is can it decrypt with password?
deneimainoob said:
Hello, does password encryption work with Android 11? Do you know or I should try and let you know? Recovery seems very nice. First time I changed from TWRP and I think I'll stay. Good Job!!
Edit: I know it says "Password Protection" in the main post. What I meant is can it decrypt with password?
Click to expand...
Click to collapse
I have not tried it with a pin code but for me pattern encryption works it decrypts your device just fine.
Maitreya29 said:
Haha thank you
Click to expand...
Click to collapse
I wanted to mention that when fully customizing the recovery things can get really laggy making it difficult to use. I can't exactly tell the setting I had because I set everything to default for fluidity. However please work on the speed and smoothness!
Appreciate the work.
Mr.Conkel said:
I wanted to mention that when fully customizing the recovery things can get really laggy making it difficult to use. I can't exactly tell the setting I had because I set everything to default for fluidity. However please work on the speed and smoothness!
Appreciate the work.
Click to expand...
Click to collapse
Did you try rebooting into the recovery after you customised? I should also point out the recovery doesn't utilise a phone's complete power. It's limited so there are always no animations and everything feels sudden, that's a limitation for twrp Ofox and everything else I've used.
Maitreya29 said:
Did you try rebooting into the recovery after you customised? I should also point out the recovery doesn't utilise a phone's complete power. It's limited so there are always no animations and everything feels sudden, that's a limitation for twrp Ofox and everything else I've used.
Click to expand...
Click to collapse
Well yes, of course. Everything seems to work fine after a few minutes but still very laggy at start and that can be a bit annoying for things like pattern lock and such. I'm not runny any customizations as of now things work good.
Tried PIN and it doesn't decrypt. It's no problem, got used to it(lol) but I'm just letting you know.
deneimainoob said:
Tried PIN and it doesn't decrypt. It's no problem, got used to it(lol) but I'm just letting you know.
Click to expand...
Click to collapse
Only patterns work on Android 11. That's normal
Maitreya29 said:
Only patterns work on Android 11. That's normal
Click to expand...
Click to collapse
I wanted to consult your team and members about a possible OrangeFox Recovery and a Rom A10 or A11 for a seperate device not OnePlus 5T. If you are interested, Pm me. Or message me on Telegram @MrConkel Payment is available for this project but is very limited. More details can be discussed after you pm or message me. Appreciate your time..
I like this recovery. It works with encryption in android 10. However, it did not work with encryption in android 11! Is it only me?
Hello!
Received an Oneplus 5T from China a few days ago, (still) running OxygenOS 9.0.9 A5010_43_191008. Gonna install some custom ROM as usual, so just unlocked its bootloader.
Saw this post about OrangeFox recovery, and considering what I've been reading in the [OFFICIAL][RECOVERY] [TWRP] TWRP for OnePlus 5T thread I feel like I'm going to put my faith in this recovery.
I have a question, though. According to what I read in the TWRP thread, the custom recovery gets killed by the stock ROMs. Is this serious?
{
"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"
}
Just
curiosity. I guess that means I should straight install my custom ROM of choice just after the recovery, period.
Merry Christmas and Happy New Year, by the way.
P.S.: Just saw there's a more recent thread about this recovery, [RECOVERY] [OFFICIAL] OrangeFox Recovery for OnePlus 5T. Will more properly repost this there, sry.
{
"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.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Introduction
This is the official Lineage OS thread for the Motorola Moto X4, codename payton.
We support all the T-Mobile, International, and Project Fi variants, as their bootloaders are unlockable, while we can't support the Verizon and AT&T variants, as their bootloaders are permanently locked.
How to install via Lineage Recovery
Please follow the official instructions
Install LineageOS on payton | LineageOS Wiki
wiki.lineageos.org
HOW TO UPDATE LINEAGEOS WITH LINEAGE RECOVERY
Please follow the official LineageOS Wiki instructions for our device
Update LineageOS on payton | LineageOS Wiki
wiki.lineageos.org
How to install via TWRP
Boot the newest TWRP .img from the Official TWRP Project Site.
IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest weekly
(Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need to be re-installed every update), and has no addon.d-v2 persistence.
Click "Reboot", then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps
Reboot
How to upgrade from 17.1 via Lineage Recovery
Please follow the official instructions
Upgrade LineageOS on payton | LineageOS Wiki
wiki.lineageos.org
How to upgrade from 17.1 via TWRP
Boot the newest TWRP .img from the Official TWRP Project Site.
IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2
In TWRP, click "Wipe", then select "advanced" and select "cache" and wipe.
ADB sideload the newest weekly build or copy it to your device and install the zip
(Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need to be re-installed every update), and has no addon.d-v2 persistence.
Click "Reboot", then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps
Reboot
Notes
Official Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status. (Magisk works fine, though is not supported.)
Official Lineage OS builds ship with full treble compatibility, with VNDK runtime enforcement! This means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run any GSI (yes, even Pie!) without need for hacks or additional flashable zips. We relabeled /oem as /vendor (as /oem isn't used in custom ROM's anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image. Please don't report GSI bugs here, report them instead to the GSI's maker.
Download
Official:
LineageOS Downloads
download.lineageos.org
Unofficial test builds:
https://osdn.net/projects/lineageos-for-payton/releases/p17369
Google Apps (GApps)
MindTheGapps:
Codefire - Listing of gapps
GCam Mods
Wichaya GCam APKs - Google Camera Port
Modified Google Camera app by Wichaya.
www.celsoazevedo.com
XDA:DevDB Information
Lineage OS 18.1, ROM for the Moto X4
Contributors
erfanoabdi, ThE_MarD, Lineage Team
Source Code: https://github.com/LineageOS
ROM Firmware Required: Official Pie
Important extra links
Payton Stock firmware:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Copy partitions link for download can be found on the LineageOS Wiki install instructions for Payton page here:
Install LineageOS on payton | LineageOS Wiki
wiki.lineageos.org
Heyyo, a new test build is up! The link can be found on the first post under the unofficial test builds link. lineage-18.1-20210119-UNOFFICIAL-payton contains some audio tweaks for echo-reference, speaker volume boost as well, so please test all voice call and audio recording functions.
ThE_MarD said:
Heyyo, a new test build is up! The link can be found on the first post under the unofficial test builds link. lineage-18.1-20210119-UNOFFICIAL-payton contains some audio tweaks for echo-reference, speaker volume boost as well, so please test all voice call and audio recording functions.
Click to expand...
Click to collapse
For wifi display we can update wfd from caf
Seems works on other roms
Heyyo @dhinesh_cool , the CAF blobs you are referring to are from Board Support Packages, which do not have any transferrable rights as it isn't publicly available like a stock ROM for a device.
LineageOS does not allow blobs from BSP because of that, to avoid any potential legal issues.
So hopefully another solution presents itself... Or if we're lucky? A better solution replaces Miracast
ThE_MarD said:
Heyyo @dhinesh_cool , the CAF blobs you are referring to are from Board Support Packages, which do not have any transferrable rights as it isn't publicly available like a stock ROM for a device.
LineageOS does not allow blobs from BSP because of that, to avoid any potential legal issues.
So hopefully another solution presents itself... Or if we're lucky? A better solution replaces Miracast
Click to expand...
Click to collapse
Ahh that bad
Another question is offline charging works?
Offline charging works, but the animation is broken.
Edit: Is the selinux permessive?
@dhinesh_cool oh snap, offline charging animation is broken lol... We will have to check into that then.
@Sujanth the test builds I released are selinux enforcing. I did just try testing with permissive and it still failed, so the issue lies elsewhere... I'll try some stuff and see what we need to do to solve it
Ok. I played cod and scwitch to telelgram. Then I switch back to cod. But the game loads from the beginning. In other rom it doesn't happen. I think the ram management could be impoved.
Heyyo, another test build is going up! The upload should be done within 30 minutes of this post and link to test builds are in the first post. lineage-18.1-20210202-UNOFFICIAL-payton contains fixes for the offline charging animation and for WiFi hotspot with WPA2 (it isn't merged yet on LineageOS, but hopefully it does before we go official on 18.1).
There is also some echo-reference changes so if someone could please test it with VoIP apps and see if there's still echo or not
Audio from front facing video is working?
ThE_MarD said:
Heyyo, another test build is going up! The upload should be done within 30 minutes of this post and link to test builds are in the first post. lineage-18.1-20210202-UNOFFICIAL-payton contains fixes for the offline charging animation and for WiFi hotspot with WPA2 (it isn't merged yet on LineageOS, but hopefully it does before we go official on 18.1).
There is also some echo-reference changes so if someone could please test it with VoIP apps and see if there's still echo or not
Click to expand...
Click to collapse
Offline charging is working now. Thanks.I am testing the other fixes and write then back.
Edit: Hotspot with WPA2 also works with 2,4 GHz band. But with 5.0gHz band i can't find the hotspot. Need any logs?
I did also a whatsapp call, no echo or mic problems.
But volume of the speaker is low. Can you fix it?
And radio FM doesn't work.
When I want to call somebody, the telephone screen is not coming, but you hear the call tone.
How to upgrade to this ROM from Lineage 17.1? Thanks.
Heyyo @derienardani , yes that was fixed on 18.1 like it was on 17.1.
@Sujanth , WiFi Hotspot WPA2 on 5GHz works fine for me, albeit there's more changes coming to it so I'm unsure yet what will be the final form of it... I'll post a new build when it changes again.
As for speaker volume? It was increased from 32 to 34 and no plans to go higher as some users said at 36 they get distortion.
FM Radio is a known bug that we are still looking into.
For the telephone bug? Please ensure you have a default phone app selected
@artu72 the upgrade instructions for 18.1 are the same as 17.1 except for GApps MindTheGapps is the recommended one to use either addon-v2 or v3 is fine.
MindTheGapps - Google Drive
Heyyo, a new test build is going up! As always it is in the first post and is uploading meow so it'll be about 30 minutes. lineage-18.1-20210211-UNOFFICIAL-payton contains some perf fixes so that cpufreq also properly scales up and down.
ThE_MarD said:
Heyyo @derienardani , yes that was fixed on 18.1 like it was on 17.1.
@Sujanth , WiFi Hotspot WPA2 on 5GHz works fine for me, albeit there's more changes coming to it so I'm unsure yet what will be the final form of it... I'll post a new build when it changes again.
As for speaker volume? It was increased from 32 to 34 and no plans to go higher as some users said at 36 they get distortion.
FM Radio is a known bug that we are still looking into.
For the telephone bug? Please ensure you have a default phone app selected
@artu72 the upgrade instructions for 18.1 are the same as 17.1 except for GApps MindTheGapps is the recommended one to use either addon-v2 or v3 is fine.
MindTheGapps - Google Drive
Click to expand...
Click to collapse
I haven't installed any other phone apps. So i don't think I need to select it. Same bug also present in corvus a11.
Hi, first time using Lineage OS here. After sideloading LineageOS, i am just not able to install Gapps. Tried using MindtheGapps 11, tried sideloading, flashing, nothing happened. Either the phone starts to bootloop or it boots to recovery or it boots to Lineage OS without any google apps. Can someone please tell me where i am going wrong?
Edit: I realised i was flashing the wrong GApps, so i tried flashing ARM64 Android 10 nano pack. The screen gets stuck at the LOS boot logo before booting back to TWRP.
SOS
Heyyo @warhead1721972 , please ensure you are following the instructions. After flashing LineageOS ROM, you must reboot to recovery and then flash GApps.
A/B devices are different than traditional A-only devices as the ROM is always flashed to the inactive slot (IE, if A is active, the ROM will be flashed to B) so after the ROM flashes successfully it tells the bootloader that next reboot to switch slots. The reboot to recovery then switches to that slot (in our example, it switches to B) so that we can flash GApps on top of the newly flashed ROM.
Installing updates via the LineageOS Updater does use addon.d scripts to keep the installed GApps, but any manual flashing of ROM (either first time or manually upgrading) requires manually rebooting to recovery and flashing GApps as it does not use addon.d scripts.
ThE_MarD said:
Heyyo @warhead1721972 , please ensure you are following the instructions. After flashing LineageOS ROM, you must reboot to recovery and then flash GApps.
A/B devices are different than traditional A-only devices as the ROM is always flashed to the inactive slot (IE, if A is active, the ROM will be flashed to B) so after the ROM flashes successfully it tells the bootloader that next reboot to switch slots. The reboot to recovery then switches to that slot (in our example, it switches to B) so that we can flash GApps on top of the newly flashed ROM.
Installing updates via the LineageOS Updater does use addon.d scripts to keep the installed GApps, but any manual flashing of ROM (either first time or manually upgrading) requires manually rebooting to recovery and flashing GApps as it does not use addon.d scripts.
Click to expand...
Click to collapse
First i sideload the rom zip in slot A along with TWRP and then i reboot to the recovery to set the current slot to B and then flash GApps. On flashing it, there are no errors, but on booting up the system for the first time, i get redirected to TWRP. Is something wrong with my phone?
Till now i have been using ViperOS for quite some time, until i wanted to try something new. Really wanna give LOS a try.
@warhead1721972 , just to check since you're using TWRP, when you switched ROMs are you wiping Dalvik, cache, data and system?
Also, are you reinstalling TWRP after flashing LOS? Because if you are, you must use the TWRP installer zip and not flash the TWRP image as that kernel isn't compatible with the ROM.
{
"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.1/README.mkdn
Flashing Instructions:
Pre-installation:
Recovery (from download page, recovery button)
NikGapps core (Download from here - note that you may also need setup wizard addon if you rely on Google restore)
Magisk root (after first boot)
First time installation:
Backup your data to PC, OTG flash drive
Boot to fastboot and flash recovery
Code:
fastboot flash recovery recovery.img
Now boot to recovery by holding VOL UP + POWER
Navigate to Factory reset and format data, wipe cache and wipe system
Now reboot to recovery
Navigate to Apply update and choose from adb (if you have crDroid.zip on external sdcard, you may choose this option and navigate to where the zip is)
Now sideload crDroid zip
Code:
adb sideload crDroid.zip
If you are running with gapps, choose again to apply from adb and sideload gapps.zip
Reboot to system
Update installation:
Via recovery
Boot to recovery
Navigate to Apply update and choose from adb (if you have crDroid.zip on external sdcard, you may choose this option and navigate to where the zip is)
Now sideload crDroid zip
Code:
adb sideload crDroid.zip
Via OTA:
Go to Settings -> System -> Updater and download latest build
Choose install and let it finish
Reboot
Do note that crDroid 8 is encrypted by default, so if you want to run decrypted, you'll need to sideload dfe.zip
Sources:
ROM: https://github.com/crdroidandroid
Kernel source: https://github.com/crdroidandroid/android_kernel_xiaomi_sdm845
Download:
ROM https://crdroid.net/beryllium
Known isues:
- none critical
Visit official website @ crDroid.net
crDroid Poco Telegram
crDroid Community Telegram
If you like my work, consider a donation > My Paypal
The installation worked liked charm. Thank you so much!!
Thanks for your work Gabriel! Wonderful, I'm glad the ROM is finally encrypted by default
Bug: Bluetooth is trying to turn on and off, repeatedly.
Overall, it feels like a LOS developer build with unlocked features.
HI GWOLFU TNX IN ADVANCE
im not be able to root
flash latest magisk apk or zip no difrens beetwin apk and zip
Sia_scazy said:
HI GWOLFU TNX IN ADVANCE
im not be able to root
flash latest magisk apk or zip no difrens beetwin apk and zip
Click to expand...
Click to collapse
Needs magisk canary
That has support for A12
a9k1t said:
Bug: Bluetooth is trying to turn on and off, repeatedly.
Overall, it feels like a LOS developer build with unlocked features.
Click to expand...
Click to collapse
Aware from telegram chat
Will try to fix with next update
Thanks
Best rom.
Thanks gwolfu! I'd love to upgrade this week, but I've got a few questions first:
Is a dirty flash upgrade from crDroid 7 supported?
I had issues with nikgapps before, with the signal app not receiving any messages unless I open the app (nikgapps specific issue). I'd like to try bitgapps instead. your rom should also work well with that gapps pack, right?
I use encrypted f2fs data partition right now. is that also supported by this crdroid 8 build? or do I have to update the fstab again?
Does it pass safetynet (with/without magisk)?
Oehr said:
Thanks gwolfu! I'd love to upgrade this week, but I've got a few questions first:
Is a dirty flash upgrade from crDroid 7 supported?
I had issues with nikgapps before, with the signal app not receiving any messages unless I open the app (nikgapps specific issue). I'd like to try bitgapps instead. your rom should also work well with that gapps pack, right?
I use encrypted f2fs data partition right now. is that also supported by this crdroid 8 build? or do I have to update the fstab again?
Does it pass safetynet (with/without magisk)?
Click to expand...
Click to collapse
1. Not possible to dirty flash
2. Should work with other gapps (I just shared what I used, however not tested by me)
3. F2FS data is not added yet due to some bug I've noticed
4. Passed SN out of the box even without magisk
Build 20200124 is up
Changelog
- Fixed bluetooth issues
There is an issue with the recovery: it does not automount the micrsod card. manually mounting using adb shell works, but as I am not sure where to mount it, I have no means of applying the update from the microsd card.
P.S. I am using a 1TB microSD card with a single exfat partition
gwolfu said:
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:
Recovery (here)
NikGapps core (Download from here)
Magisk root (after first boot)
First time installation:
Backup your data to PC, OTG flash drive
Boot to fastboot and flash recovery
Code:
fastboot flash recovery recovery.img
Now boot to recovery by holding VOL UP + POWER
Navigate to Factory reset and format data, wipe cache and wipe system
Now reboot to recovery
Navigate to Apply update and choose from adb (if you have crDroid.zip on external sdcard, you may choose this option and navigate to where the zip is)
Now sideload crDroid zip
Code:
adb sideload crDroid.zip
If you are running with gapps, choose again to apply from adb and sideload gapps.zip
Reboot to system
Update installation:
Boot to recovery
Navigate to Apply update and choose from adb (if you have crDroid.zip on external sdcard, you may choose this option and navigate to where the zip is)
Now sideload crDroid zip
Code:
adb sideload crDroid.zip
Do note that crDroid 8 is encrypted by default, so if you want to run decrypted, you'll need to sideload dfe.zip
Sources:
ROM: https://github.com/crdroidandroid
Kernel source: https://github.com/crdroidandroid/android_kernel_xiaomi_sdm845
Download:
ROM https://crdroid.net/beryllium
Known isues:
- none critical
Visit official website @ crDroid.net
crDroid Poco Telegram
crDroid Community Telegram
If you like my work, consider a donation > My Paypal
Click to expand...
Click to collapse
Bug bluetooth.....not working
wladoom said:
Bug bluetooth.....not working
Click to expand...
Click to collapse
Works fine for me with Build 20200124:
gwolfu said:
Build 20200124 is up
Changelog
- Fixed bluetooth issues
Click to expand...
Click to collapse
gwolfu said:
1. Not possible to dirty flash
2. Should work with other gapps (I just shared what I used, however not tested by me)
3. F2FS data is not added yet due to some bug I've noticed
4. Passed SN out of the box even without magisk
Click to expand...
Click to collapse
as for bitgapps: doesn't work. It fails mounting the vendor partition. tried nikgapps now and receiving message in signal seems to work for now. only time will tell!
as for f2fs, the mounting parameters for encryption differ. I didn't check out the fstab yet, but for crdroid 7, I had to remove the ext4 mount for /data and leave only f2fs with the following permissions in there:
Code:
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,background_gc=off,fsync_mode=nobarrier latemount,wait,fileencryption=ice,quota
And even then it was wonky: it only worked when the data partition was COMPLETELY empty, so that encryption was enabled on first boot. encrypting afterwards failed. Maybe that helps you in troubleshooting f2fs support for data.
P.S. Unless it goes mainline again, I'll stick with the current ext4 variant, as I had to patch fstab every time I updated the rom back with crdroid 7...
Hey, huge thanks for crDroid, currently on 7.13, will flash 8 this weekend. I've noticed that when hiding nav bar, the back gesture doesn't work anymore and haven't find out how to fix this (7.13 version though). Did I miss something ?
Oehr said:
Works fine for me with Build 20200124:
as for bitgapps: doesn't work. It fails mounting the vendor partition. tried nikgapps now and receiving message in signal seems to work for now. only time will tell!
as for f2fs, the mounting parameters for encryption differ. I didn't check out the fstab yet, but for crdroid 7, I had to remove the ext4 mount for /data and leave only f2fs with the following permissions in there:
Code:
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,background_gc=off,fsync_mode=nobarrier latemount,wait,fileencryption=ice,quota
And even then it was wonky: it only worked when the data partition was COMPLETELY empty, so that encryption was enabled on first boot. encrypting afterwards failed. Maybe that helps you in troubleshooting f2fs support for data.
P.S. Unless it goes mainline again, I'll stick with the current ext4 variant, as I had to patch fstab every time I updated the rom back with crdroid 7...
Click to expand...
Click to collapse
you can't encrypt afterwards
you either do it at first boot (does that automatically in crDroid 8), or you flash DFE and no encryption from there on
also no real benefits in F2FS imo
gwolfu said:
you can't encrypt afterwards
you either do it at first boot (does that automatically in crDroid 8), or you flash DFE and no encryption from there on
also no real benefits in F2FS imo
Click to expand...
Click to collapse
f2fs has been specifically developed for flash memory. it comes with fs-based wear leveling which is great for flash memory without a proper flash controller (microsd cards, emmc, etc.). Some more recent android phones (e.g. pixel 6, poco x3) use f2fs as its default fs for the data (and cache) partition.
Makigo123 said:
Hey, huge thanks for crDroid, currently on 7.13, will flash 8 this weekend. I've noticed that when hiding nav bar, the back gesture doesn't work anymore and haven't find out how to fix this (7.13 version though). Did I miss something ?
Click to expand...
Click to collapse
do not disable nav bar. switch to gesture bar and set its size to compact and/or disable navigation hint instead. i stumbled into the same "issue" in crdroid 8, until i figured out that I was doing it wrong. It is confusing, as all these options are split between basically three different screens.
Oehr said:
do not disable nav bar. switch to gesture bar and set its size to compact and/or disable navigation hint instead. i stumbled into the same "issue" in crdroid 8, until i figured out that I was doing it wrong. It is confusing, as all these options are split between basically three different screens.
Click to expand...
Click to collapse
Thanks, you made my day brighter
Unfortunately, I have the issue with receiving message in the Signal app again: After a while, especially while not charging, signal stops receiving messages on the phone unless I specifically open the signal app again...
I checked the usual culprits, such as battery optimization and such, but everything checks out... I had the issue before with crdroid back when I also tried nikgapps... There was no issue when I later switched to opengapps, but that is not possible for now.
Any clue as to how to fix this? I really don't want to check my signal app all the time
Oehr said:
Unfortunately, I have the issue with receiving message in the Signal app again: After a while, especially while not charging, signal stops receiving messages on the phone unless I specifically open the signal app again...
I checked the usual culprits, such as battery optimization and such, but everything checks out... I had the issue before with crdroid back when I also tried nikgapps... There was no issue when I later switched to opengapps, but that is not possible for now.
Any clue as to how to fix this? I really don't want to check my signal app all the time
Click to expand...
Click to collapse
issue is with nikgapps
should be fixed in latest build released today
if dirty flashing new gapps on top, do also clear app data of Google Play Services app and reboot after dirty flash done and booted
{
"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:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* 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.
*/
Pixys is a butter smooth Android aftermarket firmware. We handpicked the best features around and are adding our own juice into it.
Get ready to taste the unique features it brings with itself.
We aim to deliver an experience with original ideas and features along with the useful things the community is accustomed to.
@Subinsmani
@rahul9999
@@ki
@Shreejoy Dash
@kvijaya
@AxelBlaz3
@Psycho-Mods
@aswin_a_s
@Gero
@melvingarcia
Support Us if you like our work
Got an issue or suggestion? Reach us at
Telegram: https://telegram.me/pixysos_chat
Phone calls & messaging
Wi-Fi & Mobile data
VoLTE (but no icon in statusbar)
Fast charging
Dark theme, night mode
Fingerprint sensor
Face unlock
NFC
FM Radio
Wireless Bluetooth audio with AptX codec
and much more...
Less customizations but more stability...
Pixys: PixysOS
Pixys Device Sources: PixysOSDevices
NOTE: It is recommended to update your stock ROM to Android 10 before flashing this custom ROM.
IMPORTANT: If you want to use GAPPS build, it is necessary to resize system and vendor partition on your phone before flashing rom! This step will perform format of system and vendor partition and even userdata partition so make a backup if you don't want to lose your data!
If you downloaded VANILLA build, you can skip this step and if you want then you can flash gapps of your choice.
Please download this nice and user friendly Nokia Repartition Tool brought to you by Raghu Varma and look at this instructional video:
Just use the first option "3.5G S - 1G V" - it is enough for this rom.
NOTE: After resize your phone will be automatically booted to TWRP, but because this tool is intended for Nokia 6.1 Plus, this TWRP will refuse to flash ROM zip on 6.1. In this case just reboot to bootloader and download this TWRP for our Nokia 6.1, boot it and everything will be fine. Now you can begin flashing.
After booting to TWRP:
1) If you just resized your system and vendor partitions using Nokia Repartition Tool then you have already formatted userdata so you can skip this step, otherwise if you want to do a clean flash then please Format Data by typing yes, then go to the Bootloader and reboot TWRP. (For dirty flash use adb sideload method because TWRP can not decrypt Android 12 userdata partition.)
2) Flash latest ROM zip via TWRP
3) Switch to alternative slot (if you are on slot a switch to b if you are on b switch to a)
4) Reboot system
Now you are done!
SafetyNet on latest PixysOS builds passes out of the box, so you won't need root/Magisk anymore. Flash Magisk only in case that you really need to root your device.
ROM: Sourceforge download linkAt the download page, you can choose GAPPS build (with Google play store and other apps included) or VANILLA build, which contains only basic apps without Google play store (in this case you can flash gapps of your choice).
Wi-Fi Hotspot works only without password. FIXED
Custom statusbar icon pack is reverted back to default after device reboot.
Credits:
- Google for AOSP
- Dirty Unicorns
- Pixel experience
- AOSP extended
- LineageOS
- Superior OS
- Statix OS
- YAAP
- Krypton AOSP
- Project-Kaleidoscope
- AICP & POSP Team for thread template idea
- Also many pro developers who all help us to bring this rom to you...
- Please let us know if we forgot to mention your name in credits...
Contributors:
Big thanks to LineageOS developers and maintainers for Nokia 6.1 device and vendor tree on which this build is based!
Since PixysOS v5.1.5 thanks to Raghu Varma Android developer for new Nokia 6.1 device tree + vendor and kernel sources!
Kernel source:
https://github.com/LineageOS/android_kernel_nokia_sdm660
Kernel source since PixysOS v5.1.5:
https://github.com/RaghuVarma331/android_kernel_nokia_sdm660/tree/android-12.0-gcc
ROM OS Version: 12.1
ROM Kernel: 4.4.x
Based On: AOSP
Version Information
Status: Stable
Current Version: v5.1.5
Hey, really appreciate your work!) Specific bug for your rom is inability to setup magisk, because stock rom recovery "Failed to clear BCB message" error, adb sideload method doesn't works in it too. If i flash boot TWRP, then I can't boot rom, it stucks on boot logo. General bugs for all roms, such as hanging vibration (12.1 bug), gcam, that after some time of use can't take photos are here. Again. thanks for your work!!
Hi, thanks for your reply! Magisk works on this ROM, I just tested the version 24.3.
You need to boot into TWRP (twrp-3.4.0-0-PL2_sprout-11.0-20200909.img), select adb sideload option and flash latest Magisk zip. Then reboot and check the magisk app. Now you are successfully rooted. ;-)
Note: If you are installing Magisk right after flashing rom, don't forget to switch slot first!
I tried to install magisk right after I installed rom. For example now I am on a slot B, rom is installed on slot A. Magisk would setup on current slot, not as rom, that would setup on inactive slot -> I need go to the A slot to setup magisk. If I try to do that through stock rom recovery on slot A, I get error, because ADB sideload isn't working. If I try to "fastboot flash "twrp"" on slot A, then I can install magisk, but I am stuck on the rom boot logo. If I try to use twrp install.zip file from TWRP on slot B, then I get would the same problem (boot logo) on slot A. ADB sideload is installing magisk in current slot, that's why I can't do it from slot B to setup magisk on slot A. It's a bit sadly. And the second question to you, why our community vendor has general GCam problem, that is on all roms? Maybe you can contact to developers of it to fix that problem? Because it's really shame bug)
Just tell me about the experience you had with the Rom. is it smooth or not
Magisk must be installed in the same slot as the ROM. I ttied it and it works for me.
GCam problem is probably related to vendor or kernel source. Because I'm using Lineage trees to build this rom, It must be fixed by LineageOS developers.
My experience wih rom is very good, don't expect smoothness as stock, but the fact that this is an Android 12, result is really good. Small lags are ocassionally present.
Gcam not working fix it
Machi007 said:
Magisk must be installed in the same slot as the ROM. I ttied it and it works for me.
GCam problem is probably related to vendor or kernel source. Because I'm using Lineage trees to build this rom, It must be fixed by LineageOS developers.
My experience wih rom is very good, don't expect smoothness as stock, but the fact that this is an Android 12, result is really good. Small lags are ocassionally present.
Click to expand...
Click to collapse
I know that magisk have to be installed in the same as rom slot. That's why I had problems with that. If you would fix stock rom recovery, then there are no problems would be)) Yeah, rom is pretty smooth, on my opinion it works as the 10 stock, but of course android 11 custom roms work better and that's absolutely normal)
Rbargujar said:
Gcam not working fix it
Click to expand...
Click to collapse
If you tell me how to fix then I will do it. --- If you want perfect ROM then forget about custom and use stock.
FarLine99 said:
I know that magisk have to be installed in the same as rom slot. That's why I had problems with that. If you would fix stock rom recovery, then there are no problems would be)) Yeah, rom is pretty smooth, on my opinion it works as the 10 stock, but of course android 11 custom roms work better and that's absolutely normal)
Click to expand...
Click to collapse
I don't understand why to use stock recovery when we have TWRP.
Machi007 said:
If you tell me how to fix then I will do it. --- If you want perfect ROM then forget about custom and use stock.
I don't understand why to use stock recovery when we have TWRP.
Click to expand...
Click to collapse
Because if we try to use flash boot twrp on rom slot, then rom can't boot, it stuck on boot logo)
OK, I didn't try to flash Magisk zip right after ROM flashing... I have fully configured ROM with installed apps etc. and in this state I booted into TWRP flashed Magisk zip and ROM normally booted, I just found Magisk in apps and everything worked. This is my experience.
Machi007 said:
OK, I didn't try to flash Magisk zip right after ROM flashing... I have fully configured ROM with installed apps etc. and in this state I booted into TWRP flashed Magisk zip and ROM normally booted, I just found Magisk in apps and everything worked. This is my experience.
Click to expand...
Click to collapse
Maybe) In my experience, if I flash TWRP after flashing rom the rom doesn't boot, at all. Maybe I have done something wrong, but any way, if you will fix the stock recovery, it would be better!)
I need to clarify this: You are trying to flash TWRP using twrp-installer zip? If yes then this will not work on Android 12 ROM!
Do this to temporary boot TWRP (in download mode):
fastboot flash recovery twrp.img <----- this command returns error because our phone does not have the recovery partition, but it is mandatory to execute this command first --- then:
fastboot boot twrp.img <----- this command temporary boots TWRP on your Nokia 6.1 and now is the right time to install Magisk...
I recommend THIS TWRP version, just download the file and rename to twrp.img.
Machi007 said:
I need to clarify this: You are trying to flash TWRP using twrp-installer zip? If yes then this will not work on Android 12 ROM!
Do this to temporary boot TWRP (in download mode):
fastboot flash recovery twrp.img <----- this command returns error because our phone does not have the recovery partition, but it is mandatory to execute this command first --- then:
fastboot boot twrp.img <----- this command temporary boots TWRP on your Nokia 6.1 and now is the right time to install Magisk...
I recommend THIS TWRP version, just download the file and rename to twrp.img.
Click to expand...
Click to collapse
I tried to use twrp installer first, it did not worked for me, then I tried to use fastboot flash boot method, that is recommended for this TWRP. Using both flash recovery and boot method is new for me, so maybe it will be ok. But flash boot method doesn't work. And yeah, I used recommended from you Raghu's TWRP.
New build uploaded: PixysOS v5.1.3
- June security patch
- Fixed WiFi hotspot
- Google Camera should work much better now
- Build based on latest PixysOS sources with latest improvements and new functions added by ROM developers
And I would like to thank Raghu Varma which helped me a lot with fighting bugs!
Machi007 said:
New build uploaded: PixysOS v5.1.3
- June security patch
- Fixed WiFi hotspot
- Google Camera should work much better now
- Build based on latest PixysOS sources with latest improvements and new functions added by ROM developers
And I would like to thank Raghu Varma which helped me a lot with fighting bugs!
Click to expand...
Click to collapse
Maybe would try later, thanks for your work!)
Is anyone able to check if Duo Mobile 2fa is working?
I did all the steps, installed the rom, It siad "Fhasing A/B Zip to ianctive slot: B" after I try to change the slot and reboot, it says no OS installed... Is anyone else having this issue?
I did the Nokia Partition Tool, rebooted to bootloader, booted into the 3.4 TWRP it suggested and did the steps, It still said the error and rebooted back into TWRP*
EDIT: I was redoing it for the 3rd time as I typed this message and it magically worked.
Just a request, if it isn't too much to ask for...
Would it be possible to provide a vanilla build too? Perhaps then the installation would fit on the device without repartitioning -- I have made a couple of observations that have made me arrive at this conclusion:
My experience with LineageOS 19 is that the build + MindTheGApps package fits on the stock system partition without the need for repartitioning.
On the official PixysOS downloads page, I see that the size difference between Android 12 vanilla and GApps builds for one of the devices is something like 600 MB.
I am downloading the build at this instant, and I'm going to try fiddling around with the system image to make it fit on my PL2 before resorting to repartitioning (because we all know how much of a pain that can be ). I intend to install it later in the day, so I don't yet have feedback on the build itself.
Cheers! And thanks for your effort and time!
EDIT: I must also add that for a) people who prefer to use only core Google apps like GMS and Play Store (e.g. myself), and b) people who do not want to use even core Google services, a vanilla build would be ideal.
Vedanth Padmaraman said:
Just a request, if it isn't too much to ask for...
Would it be possible to provide a vanilla build too?
Click to expand...
Click to collapse
I'll consider it, maybe from the next build I'll provide both versions.