Develop Bugs

[ROM][OFFICIAL][11] crDroid v7.11 for Samsung Galaxy S10E/S10/S10+

{
"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 requirements:
Make sure you are on any Q firmware
Q TWRP (by corsicanu) Make sure to follow the instructions here carefully.
Recommended NikGapps R (optional) (Download from here)
Magisk (optional) - (Read here for installing)
Installation:
If you are coming from Stock Firmware and have encryption enabled, format DATA
Wipe CACHE, DALVIK/ART CACHE and SYSTEM.
Flash crDroid 7.x zip
If you want to have GApps flash them right after flashing the ROM before first boot.
Sources:
ROM: [url]https://github.com/crdroidandroid[/URL]
Kernel: Kernel Source
Download:
Download for S10e
Download for S10
Download for S10+
Working and Known issues:
Working:
- Wifi
- Sound
- mali drivers
- USB tethering
- Video Playback
- Fingerprint Sensor
- Ril (Mobile data,calls, sms and stuff)
- Sensors
- Bluetooth
- Wifi HotSpot
- MTP
- 2D and 3D gpu acceleration
- HW encoding/decoding
- GPS
- Cameras (All of them)
- HWcomposer (HWC)
- Signal indicator
- Double tap to wake
- Wireless PowerShare
Not Working
- VoLTE and VoWiFi will not be implemented (for now) as they heavily depend on samsungs framework
Visit official website @ crDroid.net
ExpressLuke 9820 Telegram
crDroid Community Telegram
Donate to help our team pay server costs
Donate to ExpressLuke

Changelog :
7.1 View changelog
7.2 View changelog
7.4 View changelog
7.5 View changelog
Current changelog View changelog
Detailed installation procedure :
If you are coming from Stock Firmware and have encryption enabled, format DATA
Wipe CACHE, DALVIK/ART CACHE and SYSTEM.
Flash crDroid 7.x zip
Flash nick gapps basic
Reboot system
First boot
Flash magisk image from Ivan'slink (select flash image in twrp and flash. img file to "boot")
Reboot system
Open magisk and follow the wizard
Hit the thx button and donate if you can
Important notes :
MAGISK : never update magisk when the app asks you to. Instead wait for Ivan to upload the new boot image
ONEUI3: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up, Bixby and Power.
FAQ :
Q: My device is in bootloop, I can't acces download mode or recovery, no combo works, how do I get out ?
A: You can try following:
- Plug your phone in the PC with the USB cable. Then press/hold Bixby + Volume Down and hopefully it will boot to download-mode.
Otherwise try (still plugged in) force shutdown/restart by pressing/ holding Volume Down + Power - as soon as the screen turns off shift to pressing/ holding Bixby + Volume Down for download-mode. Try it at few times as its all about timing.
- If still no luck, unplug your phone and let the battery run out. Then press/hold Bixby + Volume Down and plug in to get to download-mode. This may take some time as the phone needs to recharge a little before it reacts.
- Once in download-mode flash your software before the update via Odin - I would use Home_CSC first trying to save your data.
Q: I lost root after proceeding with latest OTA update. What do I do?
A: flash magisk boot image again just like you did on the first flash (see procedure above).
Q: How do I update magisk ?
A: Wait for Ivan to upload the new boot image here then flash according to the detailed steps above
Q: Can I update Magisk from within the Magisk manager app or by flashing updated magisk .zip ?
A: No. Doing this would create a bootloop, Instead wait for Ivan to upload the new boot image here
Q: Dialer not appearing, no possibility to pick up calls or hang up
A: not related to rom (it's a nick gapps issue)
There's a fix : flash nick gapps "basic" and no other flavor

mastawindu said:
Thx for the ROM, can you confirm the android version?
Click to expand...
Click to collapse
The number 11 in the thread title stands for the Android version.
@turbolukex5 thanks a lot for this rom!

Can i just update from Crdroid 10 to 11 by flashing the rom and new gapps and magisk or do i need to to do a full wipe?

catormeme said:
Can i just update from Crdroid 10 to 11 by flashing the rom and new gapps and magisk or do i need to to do a full wipe?
Click to expand...
Click to collapse
+1
Sent from my [device_name] using XDA-Developers Legacy app

catormeme said:
Can i just update from Crdroid 10 to 11 by flashing the rom and new gapps and magisk or do i need to to do a full wipe?
Click to expand...
Click to collapse
I would recommend a clean flash. I don't know if it's possible to update - and it may cause unknown issues if you do.

HI @turbolukex5,
Thank you for the ROM, nice to see some 11 custom flavor, busy testing, so far looking good! Thank you very much, also to Ivan.
Good going guys!

turbolukex5 said:
I would recommend a clean flash. I don't know if it's possible to update - and it may cause unknown issues if you do.
Click to expand...
Click to collapse
I tried dirty flash nut no luck! Now i wiped and everything is ok...
Happy flashing
Sent from my [device_name] using XDA-Developers Legacy app

did anyone get magisk to work?

catormeme said:
did anyone get magisk to work?
Click to expand...
Click to collapse
Will not install , but phone is rooted [emoji848]
Sent from my [device_name] using XDA-Developers Legacy app

It's working great for me thanks for this. The issues I had were when using the stock gapps package. If it overwrites the one included in the rom the phone won't work. Wiping and flashing rom with basic Niki gapps resolved the issue though in case anyone else gets that issue.

Running great so far! Only one bug:
When always on display is turned off, unlocking the devices takes an extra second. When the always on display is on, it unlocked instant. Hope that can be fixed.
Somehow it's fixed now, I don't know what caused it, changed a lot of settings

Thank you for this great rom @turbolukex5 no bugs so far working great. Is there any way to change fingerprint icon in your rom?

FreeRunner2017 said:
Thank you for this great rom @turbolukex5 no bugs so far working great. Is there any way to change fingerprint icon in your rom?
Click to expand...
Click to collapse
It's possible you may be able to use this app with Magisk root to change your fingerprint icon. By default you can't change it in the rom.
https://pixeldrain.com/u/93zUJ6PG

turbolukex5 said:
It's possible you may be able to use this app with Magisk root to change your fingerprint icon. By default you can't change it in the rom.
https://pixeldrain.com/u/93zUJ6PG
Click to expand...
Click to collapse
Thanks @turbolukex5, how do I install this?

FreeRunner2017 said:
Thanks @turbolukex5, how do I install this?
Click to expand...
Click to collapse
Install magisk via instructions in original post and then install the apk and launch it from the link

hello super rom! i have a problem with my sd card with this rom! any idea please?

Juni3769 said:
hello super rom! i have a problem with my sd card with this rom! any idea please?
Click to expand...
Click to collapse
Next build will have this resolved

J_Dutch said:
The number 11 in the thread title stands for the Android version.
@turbolukex5 thanks a lot for this rom!
Click to expand...
Click to collapse
I kinda know... Hence the question

turbolukex5 said:
Next build will have this resolved
Click to expand...
Click to collapse
okay thank you so much

[ROM] DivestOS 14.1 for maguro/toro/toroplus

{
"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"
}
DivestOS is a more private and more secure aftermarket system.
Galaxy Nexus Notes:
- GPS works on these builds!
- I wouldn't be surprised if there are radio issues on toro/toroplus.
edit: I managed to place a call in 2022(!) on my toroplus
Features:
- strong focus on FOSS
- various system hardening
- various privacy enhancements
- automated removal of unnecessary proprietary blobs
- automated kernel hardening and CVE patching
- ability to relock bootloader on supported devices
- verified boot on supported devices
- no root support
- SELinux always enforcing
- encrypted by default
- monthly updates
- OTA delta updates
- OTA updates over Tor (optional)
- F-Droid included
- hardened system WebView with rapid updates: https://divestos.org/misc/ch-dates.txt
Extra Features (not installed by default & also compatible with all systems):
- Mull, our hardened fork of Fenix with rapid updates: https://divestos.org/misc/ffa-dates.txt
- Hypatia, our real-time malware scanner
- Extirpater, our free space eraser
Links:
- Website: https://divestos.org
- Onion: http://divestoseb5nncsydt7zzf5hrfg44md4bxqjs5ifcv4t7gt7u6ohjyyd.onion
- Downloads: https://divestos.org/index.php?page=devices&base=LineageOS#device-maguro
- Changelogs: https://divestos.org/index.php?page=news
- Project History: https://divestos.org/index.php?page=history
- Known Issues: https://divestos.org/index.php?page=broken#maguro
- Screenshots: https://divestos.org/index.php?page=screenshots
- Security Patching Overview: https://divestos.org/index.php?page=patch_levels
- About + Credits + Notices: https://divestos.org/index.php?page=about
- Donate: https://divested.dev/donate
- Source Code: https://github.com/divested-mobile or https://gitlab.com/divested-mobile
- XMPP Chat Room: xmpp:[email protected]
Device Specific Links
- Device Tree: https://github.com/Galaxy-Nexus/android_device_samsung_tuna, https://github.com/Galaxy-Nexus/android_device_samsung_maguro, https://github.com/LineageOS/android_device_samsung_toro, https://github.com/LineageOS/android_device_samsung_toroplus
- Kernel: https://github.com/Galaxy-Nexus/android_kernel_samsung_tuna
- Kernel CVE Patches Applied: https://github.com/Divested-Mobile/...1/CVE_Patchers/android_kernel_samsung_tuna.sh
Other Bits:
- Good and bad feedback is welcomed. Else how can we improve?
- If you find a bug, please report it below or via GitHub/GitLab.
- Testing/Translations/Code contributions are gratefully appreciated.
Important Notes for New Users:
- Please make a backup of your device and copy it to another computer.
- You must wipe before installing this OS.
- This OS has userdata encrypted by default
- You are intended to relock your bootloader with this OS (if your device is marked supported for that).
DivestOS does *not* support the following:
- Google Apps (OpenGAPPS)
- DRM (Widevine)
- alternative recoveries (TWRP)
- root (Magisk)
- runtime modification frameworks (Xposed or theme engines)
All downloads are GPG signed with the following key:
Code:
#B874 4D67 F9F1 E14E 145D FD8E 7F62 7E92 0F31 6994
-----BEGIN PGP PUBLIC KEY BLOCK-----
mDMEXupIxBYJKwYBBAHaRw8BAQdAC1RiTvrqJaAQ4FIHsxX+gzEgdT4mspISS+p0
y847Nge0SERpdmVzdE9TIFJlbGVhc2UgU2lnbmluZyAoMjAyMCAjMSkgPHN1cHBv
cnQrcmVsZWFzZXNpZ25pbmdAZGl2ZXN0b3Mub3JnPoiQBBMWCAA4FiEEuHRNZ/nx
4U4UXf2Of2J+kg8xaZQFAl7qSMQCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA
CgkQf2J+kg8xaZR1BgEAwwLVVsG7kbp8M3GTV987XpVl5cZeTtDc/g+66briCHUB
APiuH/dk8eRnhFnq4Up2/j7uD/8FtSvxPbHiz6t1MdgB
=VzP2
-----END PGP PUBLIC KEY BLOCK-----

Thank you for updating this old device. I want to use Anydesk app in this rom to control it remotely. but in remote PC or phone it shows a message: "Connected! Waiting for image"

[email protected] said:
Thank you for updating this old device. I want to use Anydesk app in this rom to control it remotely. but in remote PC or phone it shows a message: "Connected! Waiting for image"
Click to expand...
Click to collapse
Likely will not work on DivestOS:
AnyDesk/TeamViewer accomplishes that by having “add-on” apps. Each app requests the INJECT_EVENTS permission.
However INJECT_EVENTS has a protectionLevel of signature meaning only apps signed with the releasekey of the system image can request it. If you take a look some of the add-on apps you’ll see that they are actually signed by each manufacturer.
jarsigner -verify -verbose -certs x.apk
Seems they managed to get a ton of manufacturers to sign their helper apps.
I have no intent on signing any proprietary software with my signing keys to grant such permissions.

Ok keep going on and keep DivestOS safe. thanks for quick replay

Thank you for supporting old devices like mine. Sadly this one (as well as all the other AOSP variants) I've tried fail to provide a working camera.
"Camera is not available".
I'm not sure you are familiar with zeelogs unofficial 7.1.2 build: https://zeelogkang.blogspot.com/2017/05/lineageos-141-unofficial-712-gnex-tuna.html + https://github.com/zeelog
This is the only rom so far that manages to give me a consistently working and responsive device. Everything (but GPS) just works. Sadly he's since moved on to other devices and is no longer updating it and thus we no longer get any security updates.
I've tried to build that rom myself with the plan to backport security fixes but so far I've failed even building a stable version.
Any advice/help/ideas?

entux said:
Thank you for supporting old devices like mine. Sadly this one (as well as all the other AOSP variants) I've tried fail to provide a working camera.
"Camera is not available".
Click to expand...
Click to collapse
Camera does work on this.
I think you might need to update your firmware maybe?
Try flashing the bootloader and radio partition again from here: https://developers.google.com/android/images#yakju
If that doesn't fix it, please upload a logcat:
adb logcat -b all -d | grep -i -e dlopen -e audit
at the minimum

So I am not entirely sure what "fixed" it. Either a combination of things or one specific thing of the following:
Update Firmware
Cleared cache and rebooted
Added location permissions
Not sure when the issue will arise again but it seems to work for now.

Hey there!! I super appreciate you building this; holy moly. That being said -- are you.... "backporting" things back to LineageOS 14.1 somethow?
The reason I ask is I want to run Android 7.x with the FDroid and Aurora app stores... but also have Magisk for things like force-enabling VoLTE on Sprint as well as messing around with the HSPAP settings on the i9250... and as far as I can tell yours is the ONLY OS that has these.
I know this is a dumb question because the whole point of your OS is for it to be secure. That being said, I'd like to run it on one device and have an insecure second. Or be able to use Magisk. Or something.
IDK I'm rambling. But you rock and are awesome.
DivestOS based on Oreo time? (JKJKJK)

EirikrHinnRauthi said:
Hey there!! I super appreciate you building this; holy moly. That being said -- are you.... "backporting" things back to LineageOS 14.1 somethow?
The reason I ask is I want to run Android 7.x with the FDroid and Aurora app stores... but also have Magisk for things like force-enabling VoLTE on Sprint as well as messing around with the HSPAP settings on the i9250... and as far as I can tell yours is the ONLY OS that has these.
I know this is a dumb question because the whole point of your OS is for it to be secure. That being said, I'd like to run it on one device and have an insecure second. Or be able to use Magisk. Or something.
IDK I'm rambling. But you rock and are awesome.
DivestOS based on Oreo time? (JKJKJK)
Click to expand...
Click to collapse
Nougat not Oreo

DrTrax said:
Nougat not Oreo
Click to expand...
Click to collapse
What is the questions?

SkewedZeppelin said:
What is the questions?
Click to expand...
Click to collapse
User asked way down below whether it's based on Oreo...

Thank you for keeping our beloved nexus alive.

Hi I have read that it does not support gapp, is there any other package that supports it?

Narcoticx said:
Hi I have read that it does not support gapp, is there any other package that supports it?
Click to expand...
Click to collapse
Google Apps are *not* supported.

After CyanogenMod Android v4.4.4 KitKat stopped working, my Galaxy Nexus was restored to the stock JellyBean 4.3 and put away. Then, owing to house painting, I lost track of where it was. Out of sight, followed by 2 years of a hermit existence with only 2 trips away from the house for vaccinations, I have spent most of my time fixing things including roof leaks, car, computer, air conditioners, microwave, I came across my dear old friend and searched for newer custom firmware to revive it. Most ROMs from the active period for Nexus Maguro 5 - 6 years ago were no longer available for download. I had hoped for Marshmallow and would have been happy with Lollipop. Looking at firmware that was available for download, I was surprised to find DivestOS Nougat. Not expecting success, I decided that nothing would be lost but the time to try. I had reoccurring issues with the USB adb drivers and also could not get the divested-14.1-20220214-dos-maguro-recovery.img recovery file to work as required and started again with TWRP. I tried loading Open Gapps nano and SU, but found later that it was not successful. Nevertheless I was surprised that on rebooting after one try, I had DivestOS 14.1 / 7.1.2 Nougat running. Moreover everything worked after first boot, including WiFi, Bluetooth and Camera. The system is clean and fast, but I found no browser and installed Bromite. It's like having a new phone, which is especially pleasing since this phone is the one I had always loved most because of it's lack of bloatware. Thank you so much DivestOS, you made this old man very happy.

I have an old maguro device from my Son. It runs under TWRP Recovery and Lineage 13.0.
I dont know how to setup to yours.
Had I to change the recovery with fastboot like I installed the TWRP ?
And then installing the Rom after Wiping with the new recovery?
Or what else, the informations in this forum and on the DivestOS Homepage are not clear for me.
I have an interest to try this Rom witout Google.

ottomueller said:
I dont know how to setup to yours.
Click to expand...
Click to collapse
The steps are here: https://divestos.org/index.php?page=bootloader#fastboot

I followed these steps except 8 and 11 (not necessary here I guess). In step 12, my maguro will only display the boot animation forever, while getting warm. I waited 30 minutes and repeated, still no luck. Any pointers?

beepmod said:
I followed these steps except 8 and 11 (not necessary here I guess). In step 12, my maguro will only display the boot animation forever, while getting warm. I waited 30 minutes and repeated, still no luck. Any pointers?
Click to expand...
Click to collapse
Assuming you came from another OS, did you format data? And maguro is slow, but 15 minutes is more than enough for its first boot.

Coming from an already wiped Lineage I did wipe data volume again. To be sure after your post, I flashed TWRP and did "Format Data" (which to my knowledge is only needed when removing encryption) and made sure the partition is ext4. After that I followed the instructions from step 6 on: flashing divested recovery, sideloading system and doing a factory reset. Still the same, hangs at boot logo.
Thank you for your answer, I appreciate the help. I don't really need the phone or anything, just wished to try out divestos.

Development [ROM][Android 12L][UNOFFICIAL][OTA] LineageOS 19.1 for Redmi Note 9 5G and Redmi Note 9T

{
"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 12.1 (S), 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.
Downloads:
- Here
Flashing instructions
- Here
Bugs:
- Backlight does not turn off on offline charging
Notes:
- SELinux is enforcing
- SafetyNet passes by default
- Custom recoveries, like TWRP and OFRP, are not supported
- Custom kernels, like Eva Kernel, are not supported
- OTA support is present
- Kernel is prebuilt from stock since Xiaomi has not released the source code for cannon-s-oss (Taken from cannong 13.0.3.0)
Required firmware:
- MIUI 13 based (Up to MIUI 13.0.3.0. MIUI 12.x is not supported)
Sources:
- LineageOS
- Device sources
Telegram group:
- Here
Happy modding!

Reserved

Thank you for awesome work!

tried this, sim card stopped working

jokemaster21 said:
tried this, sim card stopped working
Click to expand...
Click to collapse
Send logs and check the reporting issues section of the guide
Also make sure you're doing everything properly, as I describe, since I haven't seen anything similar myself or in some other tester.

LinkBoi said:
Send logs and check the reporting issues section of the guide...
Also make sure you're doing everything properly, as I describe, since I haven't seen anything similar myself or in some other tester.
Click to expand...
Click to collapse
where do I find my logs
edit nvm I'll report the problem properly according to your guide

LinkBoi said:
Send logs and check the reporting issues section of the guide...
Also make sure you're doing everything properly, as I describe, since I haven't seen anything similar myself or in some other tester.
Click to expand...
Click to collapse
here are the logs
Edit also it keeps bootlooping when I insert an sd card

jokemaster21 said:
here are the logs
Edit also it keeps bootlooping when I insert an sd card
Click to expand...
Click to collapse
See below:

LinkBoi said:
Okay. Try one thing first. Flash from recovery the package that I've attached, it will make your SELinux be permissive.
PS: Consider joining Telegram for more direct communication
Click to expand...
Click to collapse
Also I will need boot logs just to be sure. You can get them by rebooting your device and when you see the bootanimation do the following:
- adb root
- adb shell
- logcat -b all > /cache/logcat-boot.log
Wait a little while and press control+C to stop the process
Afterwards, send me the file from the /cache partition. You can reboot to recovery and use 'adb pull' to grab it in your PC like this:
- adb pull /cache/logcat-boot.log

LinkBoi said:
Also I will need boot logs just to be sure. You can get them by rebooting your device and when you see the bootanimation do the following:
- adb root
- adb shell
- logcat -b all > /cache/logcat-boot.log
Wait a little while and press control+C to stop the process
Afterwards, send me the file from the /cache partition. You can reboot to recovery and use 'adb pull' to grab it in your PC like this:
- adb pull /cache/logcat-boot.log
Click to expand...
Click to collapse
here you go,
btw since I don't have a sim card to use atm I can't use telegram

jokemaster21 said:
here you go,
btw since I don't have a sim card to use atm I can't use telegram
Click to expand...
Click to collapse
Which stock MIUI were you using before flashing LineageOS?

LinkBoi said:
Which stock MIUI were you using before flashing LineageOS?
Click to expand...
Click to collapse
13.0.3.0 I believe. I tried flashing 13.0.2.0, but it kept giving me an error that the SPL would be a downgrade and it wouldn't allow me to flash

jokemaster21 said:
13.0.3.0 I believe. I tried flashing 13.0.2.0, but it kept giving me an error that the SPL would be a downgrade and it wouldn't allow me to flash
Click to expand...
Click to collapse
You should flash 13.0.2.0 from fastboot. You need to download the full fastboot ROM for your specific model and then flash it from fastboot by running flash_all.bat or flash_all.sh (Depending on your OS)

LinkBoi said:
You should flash 13.0.2.0 from fastboot. You need to download the full fastboot ROM for your specific model and then flash it from fastboot by running flash_all.bat or flash_all.sh (Depending on your OS)
Click to expand...
Click to collapse
ok tried flashing it and it said it was successful, but when I tried booting it up it got completely bricked

jokemaster21 said:
ok tried flashing it and it said it was successful, but when I tried booting it up it got completely bricked
Click to expand...
Click to collapse
Check a couple of things:
- If your device powers up in any way, see if you can go into fastboot. If your device, on the splash screen says something like 'vbmeta verification failed, press the power button to continue', just press the power button to proceed (this would be due to AVB checks)
- If your device does not power up, then try plugging it in to your computer and see if it gets detected in any way
If it does, send a screenshot of Device Manager (Windows) or 'lsusb' (Linux)
Also, do you have the Global model or the Chinese one? I assume you got the Chinese one since 13.0.3.0 is not out for Global yet.
Either way, your issues before most likely stem from using newer firmware than the one I recommend.
PS: You should already have some technical knowledge to resolve such issues yourself if you're flashing custom ROMs and also keep in mind that 'bricked' says pretty much nothing (You must be more detailed when mentioning your phone's behaviour, like if it boots but stays on the splash screen, if it boots but stays on the boot animation etc)

LinkBoi said:
Check a couple of things:
- If your device powers up in any way, see if you can go into fastboot. If your device, on the splash screen says something like 'vbmeta verification failed, press the power button to continue', just press the power button to proceed (this would be due to AVB checks)
- If your device does not power up, then try plugging it in to your computer and see if it gets detected in any way
If it does, send a screenshot of Device Manager (Windows) or 'lsusb' (Linux)
Also, do you have the Global model or the Chinese one? I assume you got the Chinese one since 13.0.3.0 is not out for Global yet.
Either way, your issues before most likely stem from using newer firmware than the one I recommend.
PS: You should already have some technical knowledge to resolve such issues yourself if you're flashing custom ROMs and also keep in mind that 'bricked' says pretty much nothing (You must be more detailed when mentioning your phone's behaviour, like if it boots but stays on the splash screen, if it boots but stays on the boot animation etc)
Click to expand...
Click to collapse
it doesn't turn on in anyway, when I plug it into my computer it makes the windows sound that it's connected, but shows nothing on the device manager. it's a brick now

jokemaster21 said:
it doesn't turn on in anyway, when I plug it into my computer it makes the windows sound that it's connected, but shows nothing on the device manager. it's a brick now
Click to expand...
Click to collapse
You can recover anything on MTK anyways. Check mtkclient and this link for more info.

New LineageOS 19.1 Update // cannon and cannong // 27.08.22
Download:
- GitHub Releases
Changelog:
- Fixed minimum brightness issue (Thanks to @ganomin for finding out)
Bugs:
- None that I know of
Notes:
- Selinux is enforcing
- SafetyNet passes by default
- Custom recoveries, like TWRP and OFRP are not supported
- Custom kernels, like Eva Kernel, are not supported
- OTA support is present

LinkBoi said:
You can recover anything on MTK anyways. Check mtkclient and this link for more info.
Click to expand...
Click to collapse
no idea how to use this, too technical for me. maybe I could bring it into a repair shop.

[ROM][13][UNOFFICIAL][DAISY][BETA][OTA] CrDroid 9.x

{
"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"
}
CrDroid 9.x for daisy​(Mi A2 Lite)​
Code:
I am not responsible for your brick devices.
The firmware is fully working and has been tested.
If you encounter a problem, write here, maybe they will help you.
Before you accuse me of doing something wrong, take a look at how you use your smartphone.
You don't need to blame me for turning your device into a brick with my firmware, it's not my fault.
Working:
- Wifi
- Sound
- mali drivers
- USB tethering
- Sensors
- Bluetooth
- Wifi HotSpot
- MTP
- 2D and 3D gpu acceleration
- Charging with device powered off
- Stuff I didn't test yet
- Camera
- GPS
- Fingerprint Sensor
- VoLTE
end .etc.
Not Working
- none
- Download ROM
- Wipe dalvik/art cache, cache, data, and data for yes.
- Flash ROM
- Flash recovery (This must be done!)
- After install magisk gapps, etc. if you need it
- Delete bootanimation.zip along the path /system/product/media/bootanimation.zip
If this is not done, the ROM will not start. You need to mount the system
- Reboot into the system
Install gapps right after installing the rom itself don't try to boot to system before that if you want to use gapps (Or wipe data before installing them)
For 13 - NikGApps.
Releases (all devices)
24.10.2022 (13)
md5: 77897b0b9c6c50a8641fc7eb2cf560c2
Github
Spoiler: old version
none
Version Information
Status: Beta
ROM OS Version: Android 13
ROM Kernel: linux 4.9
Based On Android 13/T
24.10.2022
- Add OTA update
- Initial build
- Vanilla build
- Synchronized with the latest sources
- Security patch for October 2022
- Other minor useful fixes
- Changelog 9.0
Spoiler: old changelog
none
Information:
CrDroid 9.x | A13 for Daisy, ROM for the Xiaomi Mi A2 Lite
Contributors
Furry__wolf aka WolfAURman (telegram)
Credits
Credit's list | thx for tree @GiovanniRN5
​All your donations go to the server rental, and my time spent!​
PayPal: http://paypal.me/rozenov
Also if you want you can use QIWI if possible:
QIWI: https://qiwi.com/n/OPPLA249
Device tree:
https://github.com/ItsVixano/android_device_xiaomi_daisy
https://github.com/ItsVixano/android_device_xiaomi_msm8953-common
https://github.com/ItsVixano/android_device_xiaomi_sakura-common
Kernel:
https://github.com/ItsVixano/android_kernel_xiaomi_msm8953
Vendor:
https://gitlab.com/ItsVixano/android_vendor_xiaomi

Great work I'll test it as soon as I get a time. Thanks you.

I don't understand deleting the bootanimation.zip file... boot stuck at the crDroid logo...

NiKabir said:
I don't understand deleting the bootanimation.zip file... boot stuck at the crDroid logo...
Click to expand...
Click to collapse
Михаил | WolfAURman in WolfAURman discussion | ROM's
/save how_to_delete_bootanimation - After installing the ROM, reboot the device back into recovery - After mount the system (in different recovery it is done differently) - Then go to the path /system/product/media and delete the file bootanimation.zip
t.me

The link for the ROM is version 8.1, not 9, or i'm seeing wrong?

ee99161 said:
The link for the ROM is version 8.1, not 9, or i'm seeing wrong?
Click to expand...
Click to collapse
Oops, my mistake. Fixed

i have deleted bootanimtion.zip file and it still stuck at boot animation...
upd: solved, my internal memory was encrypted

TheHeretic said:
i have deleted bootanimtion.zip file and it still stuck at boot animation...
upd: solved, my internal memory was encrypted
Click to expand...
Click to collapse
How:'s your experience with this ROM? Would you mind to share your thoughts? Thanks in advance

BiG_FooT said:
How:'s your experience with this ROM? Would you mind to share your thoughts? Thanks in advance
Click to expand...
Click to collapse
switched to this rom after ArrowOS 12.1 (whis is a great rom too).
good experiance so far (3 days) the only issues i witnessed are:
- can't set up notification lights blink lenght and speed, it either doesnt blink or just is on without blinking, like during charge.
- sometimes status bar and expanded QS duplicate battery, date and signal, but it's not critical.
Network settings section crashed a couple of times, but still work overall.
Also do not forget to switch of VoLTE, cause daisy doesn't support it, and you will not receive any calls.
This rom has very good tweaks, you can change number of coloumns in QS, which is best for me.
And if you like new features in A13, this rom is a very good choice, also updates via OTA.
3 days in normal run as a daily driver. hope that helps

Very good ROM, I hope it goes official!

crDroid paste - share logs, bugs, code and whatever else remains in plan text
paste.crdroid.net
Some apps crash on startup, like tiktok.
A similar situation on firmware from other maintainers, based on android 13. I do not advise you to switch to android 13 yet.
Any suggestions?

..are updates still to be expected?

Can we have this with biogenesis kernel?

eagerly waiting for a update

NiKabir said:
eagerly waiting for a update
Click to expand...
Click to collapse
new Daisy update was released yesterday...

cappuccini said:
new Daisy update was released yesterday...
Click to expand...
Click to collapse
Is it working properly??
sadly i stuck in bootloop.. can't find a way to solve.

NiKabir said:
sadly i stuck in bootloop.. can't find a way to solve.
Click to expand...
Click to collapse
did you follow the installation guide?
maybe that could be the reason:
Delete bootanimation.zip along the path /system/product/media/bootanimation.zip
If this is not done, the ROM will not start. You need to mount the system

NiKabir said:
Is it working properly??
sadly i stuck in bootloop.. can't find a way to solve.
Click to expand...
Click to collapse
Yes I confirm it bootloops after applying OTA update 2023-01-14

cappuccini said:
did you follow the installation guide?
maybe that could be the reason:
Delete bootanimation.zip along the path /system/product/media/bootanimation.zip
If this is not done, the ROM will not start. You need to mount the system
Click to expand...
Click to collapse
Yes, i tried this also for few times... and successfully wasted my 3 hours.. now shifted to Syberia 6.2

cappuccini said:
did you follow the installation guide?
maybe that could be the reason:
Delete bootanimation.zip along the path /system/product/media/bootanimation.zip
If this is not done, the ROM will not start. You need to mount the system
Click to expand...
Click to collapse
I confirm that deleting the bootanimation.zip file does not fix the bootlooping of the OTA update 2023-01-14
Onto LineageOS 20 UNOFFICIAL it is then...

[ROM][13][UNOFFICIAL] Palyrim OS [S10/S10+/S10 5G/E]

{
"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"
}
PalyrimOS is a LineageOS-based rom that keeps the original idea of a simple user interface with useful additions and light customization.
We focus on performance and adding optimizations that make the user experience better.
All the source code for PalyrimOS is available in the PalyrimOS Github repo.
Instructions:
Pre-Install Instructions (coming from OneUI locked bootloader)
Warning: The following instructions will unlock the bootloader and wipe all data on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Bixby and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will inform you to format data, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About" menu
Installing Palyrim OS for the first time
Flash a supported recovery (i.e TWRP, Pixel Experience recovery, crDroid recovery)
If using Odin rename the supported recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Instructions for installing TWRP can be found here
Boot recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds, then immediately hold Volume Up, Bixby and Power to boot the recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
If using TWRP, select wipe > Format Data
Sideload PalyrimOS by enabling sideload via Apply Update -> Apply from ADB (if not using TWRP)
Then run adb sideload <path to your lineage.zip> on your PC
Downloads:
Samsung Galaxy S10e (beyond0lte)
Samsung Galaxy S10 (beyond1lte)
Samsung Galaxy S10+ (beyond2lte)
Samsung Galaxy S10 5G (beyondx)
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs while having Magisk installed (especially with Zygisk enabled)
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
MODEDGES
ExpressLuke for helping fix bugs
Ivan for Kernel/Device Trees
Source Code: https://github.com/PalyrimOS
Kernel source: https://github.com/SealsPlayground/android_kernel_samsung_exynos9820Samsung Galaxy S10

Good job!

applesucksLmao said:
Good job!
Click to expand...
Click to collapse
Thank You!

if i have some time, i can try to find bugs for you if you want me to

applesucksLmao said:
if i have some time, i can try to find bugs for you if you want me to
Click to expand...
Click to collapse
Yes please that would be great

Hey bro nice post, great work on the rom looks great!

Hi
I'm glad to see this! Could you tell me in which is based?

[email protected] said:
Hi
I'm glad to see this! Could you tell me in which is based?
Click to expand...
Click to collapse
If Im not mistaken I think it's AOSP.

FreeRunner2017 said:
If Im not mistaken I think it's AOSP.
Click to expand...
Click to collapse
That's correct

Project Awaken [Discontinued]
Replaced
PalyrimOS [New Rom]

Is it work SM-G975N

DEAD LINKS

Ghoostow said:
DEAD LINKS
Click to expand...
Click to collapse
February Patch
All Links Updated
Please if the rom does not boot head back to recovery and change data partition to EXT4 do not use f2fs as it will bootloader cheers
Kernel Upstream thanks to luke

Just tried, no beyond1, says no longer available?

[email protected] said:
Just tried, no beyond1, says no longer available?
Click to expand...
Click to collapse
All fixed cheers

Rough round the edges, but I'd say this is a pretty decent stock AOSP ROM. Though there's not much inbuilt customization options like on other roms. Nothing that a few magisk modules can't fix. Though one bug I encountered when I was on the rom was that while changing settings like display font size, the settings app bugged out, nothing major tho.

Bluetooth Tissue said:
Rough round the edges, but I'd say this is a pretty decent stock AOSP ROM. Though there's not much inbuilt customization options like on other roms. Nothing that a few magisk modules can't fix. Though one bug I encountered when I was on the rom was that while changing settings like display font size, the settings app bugged out, nothing major tho.
Click to expand...
Click to collapse
Thank you for letting me know about this and yes!, their will be customization soon

MODEDGES said:
Thank you for letting me know about this and yes!, their will be customization soon
Click to expand...
Click to collapse
All good , looking forward to that!

Does fingerprint work

Beytullahhere said:
Does fingerprint work
Click to expand...
Click to collapse
Yes