{
"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/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (here)
NikGapps core (Download from here)
Magisk 21 or newer for root (after first boot) - (Download from here)
First time installation:
Backup your data to PC, OTG flash drive
Flash recovery and boot to recovery
Wipe system, data, cache and format data, then reboot to recovery
Copy crDroid and Gapps to internal memory then flash them in TWRP in same order
Reboot and enjoy
*Optional reboot again after first boot to flash Magisk for root
Update installation:
Boot to recovery and make a backup
Wipe system and cache
Flash updated crDroid and Gapps (and Magisk if you had this as root method)
Reboot and enjoy
Do note that crDroid doesn't encrypt your device, so there is no need to flash DFE or any similar stuff that can cause issues!
Sources:
ROM: https://github.com/crdroidandroid
Kernel source: https://github.com/crdroidandroid/android_kernel_xiaomi_sdm845
Download:
ROM https://crdroid.net/beryllium#crDroid-v7
Changelog: https://github.com/crdroidandroid/android_vendor_crDroidOTA/blob/11.0/changelog_beryllium.txt
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
ROM OS Version: Android 11
ROM Kernel: Linux 4.9
Encrypt data
As crDroid doesn't enforce encryption, you'll have to flash a special flashable zip in recovery in order to run encrypted
Please follow steps below
Warning Warning Warning --- This works only on clean flash
1. Flash crDroid.zip in recovery
2. Mount vendor partition in recovery (for some reason is not mounting with newer TWRP)
3. Flash encrypt zip
4. Reboot to system
Note:
The encrypt zip needs to be flashed after every update
So flash crDroid zip and follow with encrypt zip
Note2:
Recovery that is able to decrypt data is required in order to see data while booted to recovery
Official TWRP should be alright
Recommended Gapps?
I used NikGapps and it didn't let me restore my backup.
Well gapps for A11 are not quite ready
You'll have to seek a different version of gapps on the web
Note that unofficial opengapps turned to bootloop for me due to some missing permissions
The one posted in op is working but might miss some stuff as it's core version
Until a later date when gapps for a11 are more stable, you'll just have to play and install different versions for your needs
Thanks bro for releasing a11 version...awesome
gwolfu said:
Well gapps for A11 are not quite ready
You'll have to seek a different version of gapps on the web
Note that unofficial opengapps turned to bootloop for me due to some missing permissions
The one posted in op is working but might miss some stuff as it's core version
Until a later date when gapps for a11 are more stable, you'll just have to play and install different versions for your needs
Click to expand...
Click to collapse
There's a bug with the Gapps release. Need to setup everything and then restore from the settings.
Will give a brief review after done with the setup.
Thanks dev!
Please add signature spoofing support.
Is Live Display present with Display profiles?
udayan.divakaran said:
Is Live Display present with Display profiles?
Click to expand...
Click to collapse
only color calibration for now
Which TWRP we need to use to flash, the one which supports FBE or FDE?
keep the one from Android 10
we don't enforce encryption and FBE TWRP is kinda buggy
Good work on first release with most of customisation.
Does app migrate of backup and restore work here?
I have strange problem of any ROM working on custom kernel only, stock kernel fc all app after migrate restore!
What version of gcam works on this firmware?
I found, that Bluetooth Audio does not work.
Audio output will not switch to a BT device, once it gets connected.
If you have a media playback in your notifications, you get an Option, to select another output device there. When I select my BT headphones, it does nothing and the BT settings will say, that the connection to the BT device can't be established.
I tested this with multiple BT headphones and a BT speaker.
Can confirm that Bluetooth connection does not work. Also, did anyone else have their recovery changed to Lineage recovery?! Flashed using TWRP and now it's Lineage recovery. How do I change it back? Guess I'll be Googling.
monkeymagic2178 said:
Can confirm that Bluetooth connection does not work. Also, did anyone else have their recovery changed to Lineage recovery?! Flashed using TWRP and now it's Lineage recovery. How do I change it back? Guess I'll be Googling.
Click to expand...
Click to collapse
Can't confirm BT yet, the LOS recovery thing happened though. Just use fastboot from pc and flash it again if you don't have root on the device otherwise you can use the twrp app or an app like flashify. A custom kernel or magisk should make twrp stick. You simply can't flash twrp or basically anything through LOS recovery.
After "Preparing your phone..." and full white screen appears and i'm blocked. Anyone experienced this issue?
---------- Post added at 09:17 AM ---------- Previous post was at 09:10 AM ----------
Another issue I noticed is that the ROM doesn't recognize my SD-Card. I came from ReloadedOS there works, maybe dev can check commits from them? But if you manage to get into the OS, it is super fast!
speter2 said:
After "Preparing your phone..." and full white screen appears and i'm blocked. Anyone experienced this issue?
---------- Post added at 09:17 AM ---------- Previous post was at 09:10 AM ----------
Another issue I noticed is that the ROM doesn't recognize my SD-Card. I came from ReloadedOS there works, maybe dev can check commits from them? But if you manage to get into the OS, it is super fast!
Click to expand...
Click to collapse
I'm not sure if you mean external SD or internal SD, but for me on stock kernel it recognizes both. My internal SD and my 128gb Samsung micro SD card.
Twrp/fastboot corrupted after installation
Installed the rom and it replaced my twrp recovery. Now i am unable to change the recovery from neither recovery nor fastboot. Whenever i try to sideload any other file, it shows me the following error
"E:footer is wrong
E:Signature verification failed
E: error:21"
MrEvilPanda said:
Installed the rom and it replaced my twrp recovery. Now i am unable to change the recovery from neither recovery nor fastboot. Whenever i try to sideload any other file, it shows me the following error
"E:footer is wrong
E:Signature verification failed
E: error:21"
Click to expand...
Click to collapse
What I did to get back twrp was the following:
Downloaded the latest official twrp.
Downloaded Minimal fastboot&adb and extracted it.
Copyed the recovery.img to the folder where i extracted fastboot.
Rebooted phone into bootloader.
I typed the following command: 'fastboot boot recovery.img' and i got back into twrp where I used the 'Install Image' to install recovery.
I hope this helps
---------- Post added at 04:24 PM ---------- Previous post was at 04:24 PM ----------
JD. A said:
I'm not sure if you mean external SD or internal SD, but for me on stock kernel it recognizes both. My internal SD and my 128gb Samsung micro SD card.
Click to expand...
Click to collapse
My external SD Card appears as corrupted, even tho in recovery it works fine and when I install other roms i can read/write from/to it without problems.
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 Honor View 10 [berkeley]
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 features for the proper functioning of the device
Based on Android 9.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
NFC
Lights
Sound / vibration
Facelock
Known issues
Nothing
DON'T FLASH GAPPS, ALREADY INCLUDED
Download from my mirror
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Telegram channel
Stay tuned
XDA:DevDB Information
PixelExperience Pie, ROM for the Honor View 10
Contributors
Codebucket, jhenrique09, GtrCraft
Source Code: https://github.com/PixelExperience
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader, EMUI 9
Based On: AOSP
Version Information
Status: Stable
Created 2018-11-14
Last Updated 2019-07-13
DON'T FLASH IF YOU ARE ALREADY ON EMUI 9, IT WON'T BOOT!!
IMPORTANT!
Before you start flashing, make sure you are using a version of TWRP with encryption disabled, otherwise you might end up using eRecovery to rescue your device from a bootloop!
You can also use official TWRP, but it will only work until you have not flashed the ROM!
Unofficial TWRP: https://storage.codebucket.de/public/twrp-3.2.2-0-berkeley.img
(That's not mine actually, I found that on Telegram and uploaded it to my mirror)
Flashing instructions from stock EMUI
Make sure you have TWRP installed and working!!
Reboot phone into recovery mode
Go to "Wipe" and select "Format data", then confirm with yes (some devices might require to disable encryption, see post #54)
Then go to "Advanced" and select /system, /data, /cache and Dalvik-cache for wipe
Copy ROM zip over to your phone (use whatever works for you, I personally use adb push)
Go to "Install" and select the ROM zip (and Magisk if you want), swipe to flash
Done! You can now reboot to system.
Update instructions
Simply go to TWRP and wipe /system, /cache and Dalvik-cache, then flash the update ROM zip and all additional stuff you need.
I also recommend having a backup of boot ramdisk to install Magisk again on a stock boot ramdisk.
Where is the source code of the device tree?
I combined all commits needed to run this ROM into one organization, you can inspect the source code here:
https://github.com/berkeley-pie
Device tree used for this ROM: https://github.com/divadsn/android_device_huawei_berkeley
My submitted patches: https://gerrit.pixelexperience.org/#/q/topic:huawei-derps+(status:open+OR+status:merged)
Special thanks go to @flex1911, @sirhc and @LuK1337 for your hard work, without your commits I wouldn't be able to get this ROM booting for the Honor View 10!
Where are the experimental builds gone?
They are still available on my mirror: https://mirror.codebucket.de/pixelexperience/berkeley/experimental/
But please be aware that those aren't official and you will loose OTA support!
Screenshots
Tried downloading about 6 times with different browsers. Fails at about 80m or so.
thecdn said:
Tried downloading about 6 times with different browsers. Fails at about 80m or so.
Click to expand...
Click to collapse
Try downloading using a download manager, Cloudflare sometimes looses connections.
Hi, is there a guide to follow for installing this rom? I read aosp and i thought to flash system.img through fastboot with stock recovery but i found many files and system is a .br file. Do i need twrp?
Thanks
How do you get this to boot? I have L09 and have wiped all partitions via twrp and stock recovery yet still bootlooping. I have even tried adb sideload and nothing.
passion8059 said:
How do you get this to boot? I have L09 and have wiped all partitions via twrp and stock recovery yet still bootlooping. I have even tried adb sideload and nothing.
Click to expand...
Click to collapse
You need to format data and remove encryption. The procedure is as follow: Download stock firmware using eRecovery, flash TWRP, format data in wipe, reboot TWRP and flash ROM.
Will include some instructions to the #2 post soon.
Codebucket said:
Flashing instructions
Reboot phone into recovery mode
Go to "Wipe" and select "Format data", then confirm with yes
Then go to "Advanced" and select /system and /data for wipe
Return back to home and go to "Settings" to enable "Remove instead formatting"
Go back to "Wipe" => "Advanced" and select /cache and Dalvik-cache to wipe
Reboot to recovery and connect to your PC via USB
Select "Advanced" and "Adb Sideload" to start flashing
On your PC open a terminal and type "adb sideload update.zip", hit enter
Now repeat that procedure if you want to flash Magisk
Done! You can now reboot to system.
Click to expand...
Click to collapse
So dalvik/art cache are to be removed and data and system are formatted?
'update.zip' is the generic name for your rom?
Do the rom and magisk have to be sideloaded? They can't be flashed via twrp?
thecdn said:
So dalvik/art cache are to be removed and data and system are formatted?
'update.zip' is the generic name for your rom?
Do the rom and magisk have to be sideloaded? They can't be flashed via twrp?
Click to expand...
Click to collapse
Update.zip is the placeholder, you have to type the path yourself to the downloaded file. Also sideload is a feature in TWRP.
Codebucket said:
IMPORTANT!
Before you start flashing, make sure you are using a version of TWRP with encryption disabled, otherwise you might end up using eRecovery to rescue your device from a bootloop!
Unofficial TWRP: https://storage.codebucket.de/public/twrp-3.2.2-0-berkeley.img
(That's not mine actually, I found that on Telegram and uploaded it to my mirror)
Flashing instructions
Reboot phone into recovery mode
Go to "Wipe" and select "Format data", then confirm with yes
Then go to "Advanced" and select /system and /data for wipe
Return back to home and go to "Settings" to enable "Remove instead formatting"
Go back to "Wipe" => "Advanced" and select /cache and Dalvik-cache to wipe
Reboot to recovery and connect to your PC via USB
Select "Advanced" and "Adb Sideload" to start flashing
On your PC open a terminal and type "adb sideload update.zip", hit enter
Now repeat that procedure if you want to flash Magisk
Done! You can now reboot to system.
Click to expand...
Click to collapse
but it keeps rebooting brother
Install Question
Very much curious, why couldn't we simply flash the rom through TWRP? Why through ADB Sideload? Just curious, since I've only ever used sideload for official ROMs, but never for custom ones Will try this out soon though! Love Pixel Experience ROMs! Thank you for the hard work!
Is volte working in this Rom?
Gesendet von meinem BKL-L09 mit Tapatalk
mgs250 said:
Very much curious, why couldn't we simply flash the rom through TWRP? Why through ADB Sideload? Just curious, since I've only ever used sideload for official ROMs, but never for custom ones Will try this out soon though! Love Pixel Experience ROMs! Thank you for the hard work!
Click to expand...
Click to collapse
You flash the ROM using ADB Sideload because the TWRP I have used has not working MTP, therefore I have no other way to copy the ROM over. But if you have a version of TWRP which works with Pie and has working MTP then go ahead
Tk19882401 said:
Is volte working in this Rom?
Gesendet von meinem BKL-L09 mit Tapatalk
Click to expand...
Click to collapse
No, there is no fix for that yet.
Ashinnazer said:
but it keeps rebooting brother
Click to expand...
Click to collapse
Have you formatted data and removed encryption?
Update available!
This is hopefully the last unofficial build, as I have pushed the patches made by flex1911 to PixelExperience Gerrit, so we can apply for official device status.
Oh and this build has fixed a derp I made when I cherry-picked a patch, sorry
Download: https://mirror.codebucket.de/pixele...nce_berkeley-9.0-20181116-0926-UNOFFICIAL.zip
Changelog: https://mirror.codebucket.de/pixele...ey-9.0-20181116-0926-UNOFFICIAL-Changelog.txt
(I also tweaked around with some NGINX settings to improve download stability )
Does this ROM work on BKL09 with EMUI Oreo 8.0?
sbtourist said:
Does this ROM work on BKL09 with EMUI Oreo 8.0?
Click to expand...
Click to collapse
Should work, but I can't guarantee, I use a BKL-L04.
Does wifi hotspot work?
Nice work! Working great on BKL-L04 flashed on top of GPU Turbo update.
Next update, should disable nav bar when registering fingerprint. Part of my thumb keeps hitting the home button.
Edit- after registering FP in security settings, device went black and became unresponsive.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About Us:
Dirty Unicorns is an AOSP based project built to enhance the stock Android experience.
Our focus has been and is always to contribute back to the community. That is ultimately why we do what we do.
We DO NOT accept, nor ask, for donations. We do not believe in that. Everything that is necessary to keep this project going comes out of our own pocket. This includes, but is not limited to; Devices, Gerrit, our websites and services, etc.. The only thing that we ask in return is that you have patience, search the thread for answers prior to posting, read diligently, and try to enjoy the process with us!
Kernel Source:
https://github.com/DirtyUnicorns/android_kernel_google_marlin
Flashing Instructions:
If you have a device that uses TWRP
Verify that you're using the latest version of TWRP
Perform a FULL WIPE: (A full wipe is when you wipe system/data/cache/dalvik)
Flash the latest version of this ROM
Flash vendor image (once only to both slots if coming from another ROM) via bootloader:
Code:
fastboot flash --slot all vendor vendor.img
Reboot and ENJOY!
If you have a device that does not use TWRP
Download boot.img and ROM zip from DU server
Reboot into bootloader and flash the boot.img
Code:
fastboot flash --slot all boot boot.img
Reboot to recovery
Go to recovery select factory reset
Select Apply update from ADB to flash the zip
Code:
adb sideload nameofbuild.zip
Flash vendor image (once only) via bootloader:
Code:
fastboot flash --slot all vendor vendor.img
Reboot and ENJOY!
If you're just updating DU on a device without TWRP
Download ROM zip from DU server
Reboot into recovery and select Apply update from ADB to flash the zip
Reboot system now and ENJOY!
**All bugs and feature requests must be reported to JIRA**
**If you use Xposed, please don't bother reporting any bugs**
**If you use another kernel, please don't bother reporting any bugs**
**If you fail to follow these instructions, please don't bother reporting any bugs**
Download Links:
Build(s) - Marlin
Other Links:
ROM Source - https://github.com/DirtyUnicorns
Gerrit - http://gerrit.dirtyunicorns.com
Crowdin (translations) - https://crowdin.net/project/dirtyunicorns
JIRA (Bug Reporting / Feature Requests) - http://jira.dirtyunicorns.com/
Telegram - https://t.me/dirtyunicorns / https://t.me/DirtyUnicornsSupport
XDA:DevDB Information
Dirty Unicorns, ROM for the Google Pixel XL
Contributors
NYCHitman1
Source Code: https://github.com/DirtyUnicorns
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 14.7
Stable Release Date: 2020-09-13
Created 2020-08-08
Last Updated 2020-09-13
one of the BEST ROMS for Marlin, loving it
imna357 said:
one of the BEST ROMS for Marlin, loving it
Click to expand...
Click to collapse
Is it available for Sailfish or can this build can be flash on Sailfish
rom
thanks
kiran8631 said:
Is it available for Sailfish or can this build can be flash on Sailfish
Click to expand...
Click to collapse
Sorry, Marlin only.
Cool beans.....
Tried a few rom from other developers but the battery drains fast. This one have no problem. Thanks for good rom.
Was anyone able to install Magisk?
Whenever I try to install Magisk I get stuck in a Bootloop at the Google Logo.
Doesn't matter if I do KEEPFORCEENCRYPT=true & KEEPVERITY=true in the .magisk for or false.
Wanted to test disable DM-Verity but TWRP is unable to mount /system_root (Neither TWRP 3.4.0.0 or 3.3.1 work)
My Phone has an encrypted Storage if that helps narrowing down the issue
Darthsternie said:
Was anyone able to install Magisk?
Whenever I try to install Magisk I get stuck in a Bootloop at the Google Logo.
Doesn't matter if I do KEEPFORCEENCRYPT=true & KEEPVERITY=true in the .magisk for or false.
Wanted to test disable DM-Verity but TWRP is unable to mount /system_root (Neither TWRP 3.4.0.0 or 3.3.1 work)
My Phone has an encrypted Storage if that helps narrowing down the issue
Click to expand...
Click to collapse
Try using the orangefox recovery when flashing the magisk, never had this issue
Ok this looks sick. Gunna flash tonight.
Darthsternie said:
Was anyone able to install Magisk?
Whenever I try to install Magisk I get stuck in a Bootloop at the Google Logo.
Doesn't matter if I do KEEPFORCEENCRYPT=true & KEEPVERITY=true in the .magisk for or false.
Wanted to test disable DM-Verity but TWRP is unable to mount /system_root (Neither TWRP 3.4.0.0 or 3.3.1 work)
My Phone has an encrypted Storage if that helps narrowing down the issue
Click to expand...
Click to collapse
Magisk 19.3 installed without any issue using twrp 3.4.0.0
bhaskarjyotisarmah51 said:
Magisk 19.3 installed without any issue using twrp 3.4.0.0
Click to expand...
Click to collapse
So you have TWRP permanently installed on Android 10? I can't get it to work
GalaxyWhy said:
So you have TWRP permanently installed on Android 10? I can't get it to work
Click to expand...
Click to collapse
download both files, twrp.img and the twrp.zip, fastboot boot twrp.img then once in TWRP flash the twrp.zip...note, make sure to remove any PIN, password or any security on the ROM first, or else it will not decrypt:good:
GalaxyWhy said:
So you have TWRP permanently installed on Android 10? I can't get it to work
Click to expand...
Click to collapse
No TWRP permanently installed. Temporary boot into TWRP using fastboot flashed magisk.
Magisk 19.3 or 20.4 both work
Just don't set any pin/password lock on the rom
imna357 said:
download both files, twrp.img and the twrp.zip, fastboot boot twrp.img then once in TWRP flash the twrp.zip...note, make sure to remove any PIN, password or any security on the ROM first, or else it will not decrypt:good:
Click to expand...
Click to collapse
Does that mean that you actually managed it to install TWRP permanently on a Pixel XL running the latest version on any Android 10 ROMs?
And what about when there's an OTA available. Do you have to reflash it then?
I'm seriously impressed, because TWRP themselves said flashing TWRP on Android 10 wouldn't be possible yet (at least on Marlin)
And last, but not least, can I put the pin/password/safety features back to activation after I installed TWRP?
Help The Peace said:
Does that mean that you actually managed it to install TWRP permanently on a Pixel XL running the latest version on any Android 10 ROMs?
And what about when there's an OTA available. Do you have to reflash it then?
I'm seriously impressed, because TWRP themselves said flashing TWRP on Android 10 wouldn't be possible yet (at least on Marlin)
And last, but not least, can I put the pin/password/safety features back to activation after I installed TWRP?
Click to expand...
Click to collapse
How you mangaed to install TWRP on Android 10?
When I flashed TWRP after installing custom rom my phone won't boot. I have to flash a stock image to make it boot.
Help The Peace said:
Does that mean that you actually managed it to install TWRP permanently on a Pixel XL running the latest version on any Android 10 ROMs?
And what about when there's an OTA available. Do you have to reflash it then?
I'm seriously impressed, because TWRP themselves said flashing TWRP on Android 10 wouldn't be possible yet (at least on Marlin)
And last, but not least, can I put the pin/password/safety features back to activation after I installed TWRP?
Click to expand...
Click to collapse
Yup, I'm on Bliss rom right now, tried all except GSI treble. When I'm doing update, I reboot to TWRP and wipe system and cache then flash the new update afterwards flash TWRP.ZIP again.
Can't install TWRP permanently, you need to flash it everytime you are doing an upgrade, that's just me
GalaxyWhy said:
So you have TWRP permanently installed on Android 10? I can't get it to work
Click to expand...
Click to collapse
Head back over to the TWRP screen on your phone and swipe the slider that says "Swipe to Allow Modifications" if needed. Now you should be sitting on the TWRP main menu where you can then go into the "Advanced" section. From there, tap the "Install Recovery Ramdisk" option, and finally, navigate to the "Download" folder where you copied the TWRP image file.
Tap the image file once to bring up the "Install Recovery" main screen and check the "Back up existing image first" option to backup your current recovery for safekeeping. Now slide the "Swipe to Install" button at the bottom to begin installing the permanent version of TWRP onto your system partition. After it finishes installing, press the home button, go to "Reboot," then "Recovery".
Help The Peace said:
Does that mean that you actually managed it to install TWRP permanently on a Pixel XL running the latest version on any Android 10 ROMs?
And what about when there's an OTA available. Do you have to reflash it then?
I'm seriously impressed, because TWRP themselves said flashing TWRP on Android 10 wouldn't be possible yet (at least on Marlin)
And last, but not least, can I put the pin/password/safety features back to activation after I installed TWRP?
Click to expand...
Click to collapse
Yep i got it working, had to flash "twrp-pixel-installer-marlin-3.3.0-0.zip" and not the latest... dunno why but hey, it works!
rodken said:
Head back over to the TWRP screen on your phone and swipe the slider that says "Swipe to Allow Modifications" if needed. Now you should be sitting on the TWRP main menu where you can then go into the "Advanced" section. From there, tap the "Install Recovery Ramdisk" option, and finally, navigate to the "Download" folder where you copied the TWRP image file.
Tap the image file once to bring up the "Install Recovery" main screen and check the "Back up existing image first" option to backup your current recovery for safekeeping. Now slide the "Swipe to Install" button at the bottom to begin installing the permanent version of TWRP onto your system partition. After it finishes installing, press the home button, go to "Reboot," then "Recovery".
Click to expand...
Click to collapse
Does this work with latest TWRP as of june?
*EDIT*
Doesn't but "twrp-3.3.0-0-marlin.img" works following rodken's guide. Cheers!
https://mobile.twitter.com/_DirtyUnicorns_/status/1300601420903854080
[ROM][11.0][4.9][AOSP][SUZU] Explosive Lobster
SUZU F5121 and F5122
Hi! Just wanna share with you Android 11 ROM builded for Sony Xperia X (will never die)
Many Thanks for development @Cubbins
I'm not responsible for any damage caused with your device after flashing this ROM. Flash only on your own risk.
This ROM bring us Treble support ( ARM64 A/B ) structure for all GSI images based on 11 Android. Just flash any GSI at System partition after it.
How to Install:
1) Copy ROM to SD card and flash with recovery
2) Download SW_BINARIES_FOR_XPERIA_ANDROID_9.0_2.3.2_V9_LOIRE.ZIP, unzip and copy image to sdcard too
3) Flash Binaries with recovery to OEM/ODM partition
4) reboot
5) After reboot we need to flash/format userdata partition. So, download it and flash with ADB: fastboot flash userdata userdata.img or fastboot erase userdata
6) reboot.
Warning:
We use /cache partition at thid ROM as a /vendor, so if you format /cache partition on recovery - you'll catch a bootloop.
Features:
Working:
- Wi-Fi
- Bluetooth
- Fingerprint
- Sensors
- Camera
- Calling
- Music Playing
- GPS
- Encrypting Data
Not Working:
You tell me
Sources:
build ROM sources:
github.com/ExplosiveLobster
kernel sources:
github.com/ExplosiveLobster/kernel_sony_msm-4.9
bug reports:
github.com/ExplosiveLobster/bug_tracker/issues
Screenshots:
{
"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"
}
Download:
Google Drive
Explosive Lobster - Google Drive
drive.google.com
Mega
3.11 GB folder on MEGA
12 files and 3 subfolders
mega.nz
Great work!
Nice work dude. I am yet to flash but I appreciate your efforts. But I am using a custom rom already. Do I need to reflash stock rom before flashing your rom ? Is there any way to flash without sd card by using adb?
GOrMHATRe said:
Do I need to reflash stock rom before flashing your rom ? Is there any way to flash without sd card by using adb?
Click to expand...
Click to collapse
No, you don't. You can try flash from internal storage, but you can't flash rom with adb
@lubik It looks like there is an issue with calls. I can't hear a companion and companion can't hear me. Microphone and speakers work correctly if you try Google search...
pitfallykmr said:
@lubik It looks like there is an issue with calls. I can't hear a companion and companion can't hear me. Microphone and speakers work correctly if you try Google search...
Click to expand...
Click to collapse
Tomorrow I will build a new version with a fix, latest sources and kernel security patch.
Updated.
Changelog:
1) Fixed Calling
2) Fixed Music Playing
3) Fixed recovery (bug with AOSP recovery installing after reboot)
4) Latest Sources and security patch
Awesome work dude, never thought android R making it's way to xperia X..
Amazing, I never thought I will ever experience android 11 on this device. Thank you
Good job guys! Thank you!
I would be coming from Q TWRP 3.3.1, but selecting the zip to install gives E1001: failed to update system image. Is there something I am forgetting? (it already has the ODM partition flashed for Q)
You can try TWRP 3.4. It works fine for me.
pitfallykmr said:
You can try TWRP 3.4. It works fine for me.
Click to expand...
Click to collapse
Thank you it works with that.
Which gapps do you recommend? I tried NikGapps full but fingerprint unlock seems to be missing, also I couldn't encrypt the phone. It fails to mount userdata on next boot, and causes a bootloop on zygote. Also I have noticed a changed behavior with the new ODM partition, if the charger is connected it comes up on reboot in some factory flashing mode (just reports android in usb descriptor, and there is no fastboot or adb, and nothing on the screen)
Update: Fingerprint just works slightly differently, but works OK. Encrypt is the next to tackle.
Update2: So interestingly fingerprint unlock works, but use biometry option is missing from the apps. Is it related the device not being encrypted?
tamisoft said:
Which gapps do you recommend? I tried NikGapps full but fingerprint unlock seems to be missing, also I couldn't encrypt the phone. It fails to mount userdata on next boot, and causes a bootloop on zygote. Also I have noticed a changed behavior with the new ODM partition, if the charger is connected it comes up on reboot in some factory flashing mode (just reports android in usb descriptor, and there is no fastboot or adb, and nothing on the screen)
Click to expand...
Click to collapse
You can try Flamegapps.
New build is up!
Changelog:
1) Added Calculator as system app
2) Fixed offline charging and wake up when charging in offline mode
3) Added F5122 variant on download repository
On next build:
1) Fix userdata earlymount (changed to late mount state)
2) Fix for Data Encrypting/Decrypting (same on TWRP)
3) Support EL for Kugo device
4) Support for old TWRP's
5) GPS upgrade
lubik1 said:
On next build:
1) Fix userdata earlymount (changed to late mount state)
2) Fix for Data Encrypting/Decrypting (same on TWRP)
Click to expand...
Click to collapse
What do you think about everyday usage and battery drain?
I ask that because switching from Omnirom 7 to 8, battery sucking was a disaster.
Will this update solve my recovery 3.3.1 error 1 problem?
Twrp 3.4 doesn't work for me, I guess because I bought my device with Android 7 and the bootloader from 8 is required?
Or to put it another way: Will installing stock android 8 first solve my problem?
MichaBit said:
What do you think about everyday usage and battery drain?
Click to expand...
Click to collapse
It's not a SODP-based ROM, it's a clean AOSP build. Any another custom ROM on this forum based on SODP or on the Stock fw, thats why it's a unical ROM with low battery consumption (like on a stock 8.0, maybe 5-15% more becouse of Android version and more optimisation by Sony's developers)
MichaBit said:
Will this update solve my recovery 3.3.1 error 1 problem?
Click to expand...
Click to collapse
Yep, next update of this ROM will be compatible with old versions of TWRP recovery, becouse Pavel @Cubbins did a trick with symlinking new bootloader location with "ln" command to old bootloader path: /dev/block/bootdevice/by-name.
MichaBit said:
Twrp 3.4 doesn't work for me, I guess because I bought my device with Android 7 and the bootloader from 8 is required?
Click to expand...
Click to collapse
Yes you right. For any new ROM (begining from 9 Android) you need new bootloader on your device. It will be automaticaly update if you flash a stock 8.0 ROM with Emma or FlashTool
MichaBit said:
Or to put it another way: Will installing stock android 8 first solve my problem?
Click to expand...
Click to collapse
Yes it did.
Hello @lubik1 . Does your rom suffer from the kernel panics that cause the random reboot problems or since it's pure Aosp it doesn't have it?
Thanks for your hard work!
zaqm said:
Hello @lubik1 . Does your rom suffer from the kernel panics that cause the random reboot problems or since it's pure Aosp it doesn't have it?
Thanks for your hard work!
Click to expand...
Click to collapse
Sometimes you can get kernel panic when you turn on the device. But while using android, I didn't observe kernel panic, but I have not run any stability tests yet, so everything is possible. I'm working on it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're 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 us for messing up your device, we will laugh at you.
*/
Introduction
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
TWRP version: 3.5.2_11
For device: gta4lwifi
Device Tree: https://github.com/juic3b0x/twrp_android_device_samsung_gta4lwifi
Maintainer/Authors build: ragarcia87
Installation Instructions
If TWRP Already Installed
Download recovery.img from below
Copy recovery.img to device
Install > Install Image > recovery.img to Recovery
Reboot > Recovery
Enjoy
From PC
Download Odin Flashable Tar from bellow
Put tablet into Odin Download Mode
Flash Blank vbmeta via Userdata
Flash Odin Flashable Tar via AP
Enjoy
Working
ADB
MTP
Everything, except decryption of internal data (havent tested)
Bugs
(My tablet is already decrypted so haven't tested this, please advise)
OS-encrypted storage (Internal Data) not able to be decrypted in TWRP.
Downloads
recovery.img
https://mega.nz/file/bkcimDCK#tkv6ATvxx_gEUJJ4OD2WQ1WsRPTINRZCc2hTFPg62aY
Blank vbmeta
https://mega.nz/file/74dAUBSQ#w_XN49p8TRppiOVEvI_eGXkzf6jgZWXarN4Qi6BFr-4
Odin Flashable Tar
https://mega.nz/file/C0NgmD6S#lWD70RUXsXs_sv-0E5BOHPoitQc8keyorarW0xtXV-4
Thanx a lot bro. was looking for it. working fine. is there any custom or modified samsung rom without bloat sothat we can use this recovery for that.
Glad it's working well for you. And to be honest, I've tried a few GSI roms and they work well, like crDroid GSI and CAOS GSI... I've been trying to cook up my own port of a few ROMs also to no avail yet but soon...
ragarcia87 said:
Glad it's working well for you. And to be honest, I've tried a few GSI roms and they work well, like crDroid GSI and CAOS GSI... I've been trying to cook up my own port of a few ROMs also to no avail yet but soon...
Click to expand...
Click to collapse
How do I install the GSI ROMs because I only get Boot Recovery dtbo vbmeta_samsung VBMeta and Super (system vendor odm product)
EdwardTCM said:
How do I install the GSI ROMs because I only get Boot Recovery dtbo vbmeta_samsung VBMeta and Super (system vendor odm product)
Click to expand...
Click to collapse
You have to use a patch called DynaPatch v1.5. It patches TWRP to be able to install individual images to the super dynamic partition... I don't know if I can post a link but if you Google DynaPatch v1.5 you'll be able to find it, just flash via TWRP and then reboot to Recovery and it will show system, vendor, product etc in the install
ragarcia87 said:
You have to use a patch called DynaPatch v1.5. It patches TWRP to be able to install individual images to the super dynamic partition...
Click to expand...
Click to collapse
Oh alright thanks
ragarcia87 said:
You have to use a patch called DynaPatch v1.5. It patches TWRP to be able to install individual images to the super dynamic partition... I don't know if I can post a link but if you Google DynaPatch v1.5 you'll be able to find it, just flash via TWRP and then reboot to Recovery and it will show system, vendor, product etc in the install
Click to expand...
Click to collapse
I got the file but nothing happened
Edit: Never mind I fixed it
Enter TWRP recovery
Select Install – select DynaPatch-v1.5.zip, Swipe to confirm Flash
Select Reboot – Recovery or Turn Power off
One time only to flash this patch except you reflash the TWRP recovery
The images attached are to show that it works.. I show a before the patch is installed and then after its installed... make sure you follow the directions above.
Aight, after i unlocked the bootloader, everytime i try to flash the vbmeta or even the twrp, it fails. any idea why?
"Only official released binaries are allowed to be flashed(vbmeta)"
Liloabouu said:
Aight, after i unlocked the bootloader, everytime i try to flash the vbmeta or even the twrp, it fails. any idea why?
"Only official released binaries are allowed to be flashed(vbmeta)"
Click to expand...
Click to collapse
After unlocking, did you re-enable Dev mode and check OEM?
Could you please refresh your device tree on GitHub with the changes you made for Android 11?
Magendanz said:
Could you please refresh your device tree on GitHub with the changes you made for Android 11?
Click to expand...
Click to collapse
I can certainly try, lol... Been super busy lately, 7days a week, two jobs no time off till after the new year lol... I'll keep ya posted
I'm having a problem with stock recovery overwriting TWRP. I have the latest stock, BUJ1, installed. I flash vbmeta and recovery with Odin and boot into TWRP. Format data and reboot recovery. Everything works fine. Reboot to system and go through the setup, make sure developer mode still enabled. Again, everything appears to work. Download the DynaPatch and copy it to the T500 SD card. Turn off the tablet and attempt to boot TWRP. It's gone. Back to stock recovery. What am I doing wrong????
read post below... sorry ... tried to edit and it double posted...
lewmur said:
I'm having a problem with stock recovery overwriting TWRP. I have the latest stock, BUJ1, installed. I flash vbmeta and recovery with Odin and boot into TWRP. Format data and reboot recovery. Everything works fine. Reboot to system and go through the setup, make sure developer mode still enabled. Again, everything appears to work. Download the DynaPatch and copy it to the T500 SD card. Turn off the tablet and attempt to boot TWRP. It's gone. Back to stock recovery. What am I doing wrong????
Click to expand...
Click to collapse
Thats my bad, youll want to use the multidisabler to fix that.. I have added it to the twrp.. once twrp is installed go to Advanced > Terminal and then type multidisabler then press enter. This will disable the stock recovery restoration.
What if I don't have TWRP installed yet but the tablet is rooted with Magisk? Is it okay to flash TWRP from within a running system?
ragarcia87 said:
Thats my bad, youll want to use the multidisabler to fix that.. I have added it to the twrp.. once twrp is installed go to Advanced > Terminal and then type multidisabler then press enter. This will disable the stock recovery restoration.
Click to expand...
Click to collapse
Thanks. That worked but I flashed DynaPatch and then lineage-19.0-20211216-UNOFFICIAL-treble_a64_bvS-vndklite.img in super and it bootloops. Any ideas? Of course this was after format of data and factory reset wipe.
lewmur said:
Thanks. That worked but I flashed DynaPatch and then lineage-19.0-20211216-UNOFFICIAL-treble_a64_bvS-vndklite.img in super and it bootloops. Any ideas?
Click to expand...
Click to collapse
You'll have to reflash stock super or extract the stock super img and flash vendor, product, odm, then the lineage to system
Also @lewmur will need the lineage-19.0-20211216-UNOFFICIAL-treble_arm64_bvS-vndklite.img variant. Not a64
paziusss said:
Also @lewmur will need the lineage-19.0-20211216-UNOFFICIAL-treble_arm64_bvS-vndklite.img variant. Not a64
Click to expand...
Click to collapse
paziusss said:
Also @lewmur will need the lineage-19.0-20211216-UNOFFICIAL-treble_arm64_bvS-vndklite.img variant. Not a64
Click to expand...
Click to collapse
Thanks. Got LOS 19 to boot. Do you know what gapps to use with it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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