{
"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"
}
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features.
Your warranty is now void, or not... I have no idea it depends...
・ I'm not responsible for bricked devices, thermonuclear war or alarm app fails.
・ If it's your first time or you're unexperienced with flashing ROMS, please do some search before flashing!
・ YOU are choosing to make these modifications, you're the only responsible guy for messing up if you do so.
Build Date : 28th of November 2022
ROM Developer : Hungphan2001
Maintainer : kota
Latest v4.2 Sources.
Selinux State : Enforcing
Running latest Security patch! (November)
Passes CTS by default.
Donations : Here!
Used Kernel : Here!
・ WIFI
・ RIL
・ Mobile Data
・ GPS
・ Camera
・ Flashlight
・ Camcorder
・ Bluetooth
・ FM Radio
・ Fingerprint Reader
・ Face Unlock
・ NFC
・ Lights
・ Sound / vibration
You tell me!
Initial flash :
・ Make sure that you are on MIUI 13.0.X or an A12 AOSP, MIUI 12.x or any A11 AOSP will just EDL Brick.
・ Reboot to Bootloader and follow the next steps! (They're different if you have TWRP)
・ Flash the Boot Image you downloaded by doing "fastboot flash boot_ab boot_cherish.img". (Recovery)
・ Reboot into Recovery Mode by doing this command "fastboot reboot recovery".
・ Once in Recovery, go into "Format Data/Factory Reset". (DOING THIS STEP WILL WIPE YOUR DATA)
・ Then go back into the main menu, and go into Apply Updates -> Apply from ADB.
・ Check if the device is connected by doing "adb devices", it should be in Sideload Mode.
・ Finally, Sideload your ROM by performing this command : "adb sideload cherish_rom_name.zip" and reboot.
Sideload Update : (dirty flashing)
・ Make sure that you're not making a downgrade! 🙈
・ Reboot into Recovery Mode and select Install Update -> ADB Sideload.
・ Once done, Sideload your ROM by performing this command : "adb sideload cherish_rom_name.zip" .
・ Finally, Quit Sideload Page and reboot. Enjoy the new release!
You also want to root? Here are some steps.
Installing Magisk : (optional)
・Download the latest provided boot image to your Internal Storage on your device.
・Second, download and install Magisk. Once done, Click Install and patch the image you downloaded.
・Then send the new magisk image (that should be in /Downloads) to your ADB directory in your PC.
・Finally, reboot to Fastboot Mode and perform this command : "fastboot flash boot magisk_file.img"
ROM : Click me!
Boot Image : Here!
Follow @CherishOS
Join @CherishOS_Chat
Have a nice day!
Lets quacking go, congrats dude
the official ROM and output but impossible to install.
Are we supposed to flash the linked boot image if we come from your last unofficial version?
I only sideloaded the new update and it's working great. Wonder if I need to "update" the boot image as well... (since the image name is different, cherish13 now vs cherish11 before)
And if so, do we need to factory reset?
Hi, I´m on the last unofficial release and flashed the new boot.img. Then I tried to sideload the new release but I always get the error
"adb: failed to read command: No error"
How to solve this ? It´s the same fastboot/adb that I used before successfully ......
muellerdeluxe said:
Hi, I´m on the last unofficial release and flashed the new boot.img. Then I tried to sideload the new release but I always get the error
"adb: failed to read command: No error"
How to solve this ? It´s the same fastboot/adb that I used before successfully ......
Click to expand...
Click to collapse
I have no idea why this gitch happens :/, the two versions should be compatible. Try updating ADB!
Eidenz said:
Are we supposed to flash the linked boot image if we come from your last unofficial version?
I only sideloaded the new update and it's working great. Wonder if I need to "update" the boot image as well... (since the image name is different, cherish13 now vs cherish11 before)
And if so, do we need to factory reset?
Click to expand...
Click to collapse
No need to factory reset, you can normally sideload to official from the last recovery. The jump from 11 to 13 i skipped releasing one build on XDA. If you encounter any issue, try updating your ADB Version or switching to the boot_cherish13 recovery provided!
muellerdeluxe said:
Hi, I´m on the last unofficial release and flashed the new boot.img. Then I tried to sideload the new release but I always get the error
"adb: failed to read command: No error"
How to solve this ? It´s the same fastboot/adb that I used before successfully ......
Click to expand...
Click to collapse
I had the same issue when trying to sideload on Linux. Switched to my windows installation and it worked without error this time...
kotalol said:
I have no idea why this gitch happens :/, the two versions should be compatible. Try updating ADB!
Click to expand...
Click to collapse
Yes, a different version works now Thank you !
I´m using now that version: https://www.techmesto.com/download-minimal-adb-and-fastboot-latest/
muellerdeluxe said:
Yes, a different version works now Thank you !
I´m using now that version: https://www.techmesto.com/download-minimal-adb-and-fastboot-latest/
Click to expand...
Click to collapse
Better using Google's version!
kotalol said:
Better using Google's version!
Click to expand...
Click to collapse
okay, googles latest version 33.0.2 is also working fine with the official ROM
(https://developer.android.com/studio/releases/platform-tools)
I used an older version for almost 2 years but now there must be some changes.....
Does status bar have icon limit setting ?
Sometimes I see "traffic indicators", sometimes I don't
ayamgoreng said:
Does status bar have icon limit setting ?
Sometimes I see "traffic indicators", sometimes I don't
Click to expand...
Click to collapse
Probably because the auto-hide option is activated by default
Looking forward for further update. Thank you for the build. Its performance is great
Updated Official ROM: Cherish-OS-v3.8-20220627-1429-venus-OFFICIAL-GApps.zip
changelog:
Etude kernel: Op.12 Op.2 bringup :
The kernel source has been rebased and cleaned up!
Click to expand...
Click to collapse
Merged LA.UM.9.14.r1-19800-LAHAINA.QSSI13.0
Click to expand...
Click to collapse
Has been built with Prelude Clang based on the latest LLVM Clang 15 source.
Click to expand...
Click to collapse
Enabled ThinLTO, CFI, and Shadow Call Stack.
Click to expand...
Click to collapse
Fixed lots of warnings from Clang 15.
Click to expand...
Click to collapse
Introduced a page_alloc fix from upstream that may help alleviate memory pressure.
Click to expand...
Click to collapse
Imported Wireguard kernel driver 1.0.20211208.
Click to expand...
Click to collapse
Backported lz4’s fast decompress loop from upstream lz4 1.9.3, which offers more than 10% throughput incrUpdated vendor blobs from MIUI Stable V13.0.12.0 for Mi 11 Ultra/Pro and MIUI Stable V13.0.8.0 for Mi 11ease in zram decompression
Click to expand...
Click to collapse
Fixed a potential lz4 out-of-bound read.
Click to expand...
Click to collapse
Imported the latest exFAT kernel driver backport from mainline kernel. OTG USB drive with exFAT filesystem should work now.
Click to expand...
Click to collapse
Vendor changes :
Removed included firmware, to minimize a maximum EDL bricking chances.
Click to expand...
Click to collapse
Updated display blobs from LA.UM.9.14.r1-19300.01-LAHAINA.QSSI12.0
Click to expand...
Click to collapse
Updated the display HAL from LA.UM.9.14.r1-19200-LAHAINA.QSSI12.0
Click to expand...
Click to collapse
Other fixes/improvements :
Device Tree Cleanup + fixing typos.
Click to expand...
Click to collapse
Optimized native executables for Cortex-A55
Click to expand...
Click to collapse
Synced some telephony packages and properties with QSSI
Click to expand...
Click to collapse
GNSS improvements :
Updated GNSS HAL to LA.UM.9.14.r1-19800-LAHAINA.QSSI13.0
Click to expand...
Click to collapse
Synced some GPS configs with stock
Click to expand...
Click to collapse
Picked a few NTP servers that can respond closer to your location, so your time synchronization takes less time which leads to faster location fix.
Click to expand...
Click to collapse
LZ4 :
Switched zram compression algorithm from lzo-rle to lz4lz4 with my fast decompress loop backport offers higher throughput and lower latency than lzo-rle does
Click to expand...
Click to collapse
lz4’s compression ratio is slightly less than lzo-rle, but Mi 11’s 8GB/12GB RAM does not encounter memory pressure very frequently, so memory bandwidth and latency is more preferable than compression ratio (quotes from jjpprrrr)
Click to expand...
Click to collapse
Most changes made to this CherishOS build wouldn't have been possible without jjpprrrr's work!
Can i flash dirty? I am on the latest cherish 3.8?!
xXSkylinexX said:
Can i flash dirty? I am on the latest cherish 3.8?!
Click to expand...
Click to collapse
hello if you are on the latest cherish os 3.8 official yes you can
Battery on this rom is good ?
xXSkylinexX said:
Can i flash dirty? I am on the latest cherish 3.8?!
Click to expand...
Click to collapse
Yup, every build of CherishOS can be upgraded on dirty flash
Fresh install from last update.
After flashing magisk 25.1, touchscreen issue when i want to unlock the phone.
So going to format data again but how to solve magisk problem ?
Related
MI MAX 2
Android 11 by DJsmk123
1.INTRODUCTION
Well, Android 11, Google’s 11th iteration looks similar to Android 10 but with a handful of new features and changes. The update brings notification history, Chat bubbles, Conversation notifications, screen recorder, new media controls, smart device controls, one-time permission, improved dark theme with the scheduling system, app suggestions, wireless android auto, and many more....
2.Installation Guide
1.First Download AOSP11.zip
2.Now From Any recovery backup your device
Note:Recommended Recovery Orange Fox Recovery
3.Now Wipe all Partition except internal storage
4.Now Install AOSP11.zip
5.if during installation of AOSP11.zip its stuck and reboot to fastboot then try again install without wiping system its will works.
6.Reboot To System and Your Android 11 is Ready to go...
3.Workings
WiFi, Bluetooth, RIL, etc
4.Known Issues
Camera,Flashlight,Fingerprint[Major Issue but i am trying to resolve them]
5.Download Link: https://www.mediafire.com/file/b6v8nilxctnfkf5/aosp11.zip/file [Gapps Included]
6.Source
1.Rom source: https://github.com/phhusson/treble_experimentations/releases
2.Kernel Source:
https://forum.xda-developers.com/t/gsi-vendor-for-mm2-oxygen-by-team-o-8322.4139599/
as this post do not contain Kernel Source so i do not have kernel source....
Note: There is some three Major Bugs camera , Fingerprint And Flashlight and I am trying to resolve them but as i am not developer so its not easy for me
here i will provide log-cat error behind these errors and any one who is interested to resolve them his help will be appreciated as far as these errors the rom is perfect to use in daily life.....
{
CANNOT LINK EXECUTABLE "/system/vendor/bin/mm-qcamera-daemon": library "libgui.so" not found: needed by /vendor/lib/libmmcamera2_stats_modules.so in namespace (default)
CANNOT LINK EXECUTABLE "/vendor/bin/hw/[email protected]": library "libgui.so" not found: needed by main executable
CANNOT LINK EXECUTABLE "/vendor/bin/hw/[email protected]": library "libkeystore_aidl.so" not found: needed by main executable
}
Warning:I am not responsible to anything happen with your device if you are come here then you know what are you doing...
{
"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"
}
Nice to see A11 booted on Mi max 2. Fingerprint for mido A11 is working. The same fix used for mm2 for A10 may be it works for A11 too. Trying aosp-phh now..
Kunal panchal said:
Nice to see A11 booted on Mi max 2. Fingerprint for mido A11 is working. The same fix used for mm2 for A10 may be it works for A11 too. Trying aosp-phh now..
Click to expand...
Click to collapse
Thankyou...
I will try this.
DJsmk123 said:
Thankyou...
I will try this.
Click to expand...
Click to collapse
You should also check Mi Max2 telegram channel, there are newer kernels and roms. Perhaps you can find necessary libs from them.
DJsmk123 said:
Thankyou...
I will try this.
Click to expand...
Click to collapse
I tried your A11 with mochi fix. Fingerprint works perfectly.
Release GF3258-FP Fix · Jebaitedneko/mochi-porter
This patch ports over Vince HALs and some modded ones to other devices with Goodix-GF3258 fp sensor to enable fp functionality. Should work till A10. Take backup of /vendor before flashing. NOTE: T...
github.com
asdfg34 said:
I tried your A11 with mochi fix. Fingerprint works perfectly.
Click to expand...
Click to collapse
Pls provide me this fix link
DJsmk123 said:
Pls provide me this fix link
Click to expand...
Click to collapse
I edited my previous message.
I love my Mi Max 2 (currently with EvoX 4.7) and it's great to see ongoing development . Looking forward to trying a future release - thank you
Thats so satisfying hearing about A11 for our XIAOMI MI MAX 2.... thanks to you for working hard to give our community a good bugless rom for our MAX 2.
Hey man how are , i flashed the rom doing all the wipping , but after boot logo it says , file ayatem corrupt asking for password . I have entered the password , it says system files damaged or corrupt. What can i do
enius6 said:
Hey man how are , i flashed the rom doing all the wipping , but after boot logo it says , file ayatem corrupt asking for password . I have entered the password , it says system files damaged or corrupt. What can i do
Click to expand...
Click to collapse
I think you should try orange fox recovery and wipe all partition except internal storage now install asop11.zip
It may be go fastboot do not worry go again recovery flash asop11.zip without mount and dismount partitions.
If you find error again then send me screenshot of the error..
DJsmk123 said:
I think you should try orange fox recovery and wipe all partition except internal storage now install asop11.zip
It may be go fastboot do not worry go again recovery flash asop11.zip without mount and dismount partitions.
If you find error again then send me screenshot of the error..
Click to expand...
Click to collapse
I have done it like you said , wiped all tha partitions expect internal , clean flash using orange recovery i got this error . I have flashed again without wiping just like as you saying and got the rror again. It hasn't stuck at boot loader . I will try again and send you the screenshot
enius6 said:
I have done it like you said , wiped all tha partitions expect internal , clean flash using orange recovery i got this error . I have flashed again without wiping just like as you saying and got the rror again. It hasn't stuck at boot loader . I will try again and send you the screenshot
Click to expand...
Click to collapse
Try to flash firmware first then OS
enius6 said:
I have done it like you said , wiped all tha partitions expect internal , clean flash using orange recovery i got this error . I have flashed again without wiping just like as you saying and got the rror again. It hasn't stuck at boot loader . I will try again and send you the screenshot
Click to expand...
Click to collapse
It is because of Android security, you have to format internal sd to avoid this error.
enius6 said:
I have done it like you said , wiped all tha partitions expect internal , clean flash using orange recovery i got this error . I have flashed again without wiping just like as you saying and got the rror again. It hasn't stuck at boot loader . I will try again and send you the screenshot
Click to expand...
Click to collapse
Plz provide me screenshot as well as if possible logcat
DJsmk123 said:
MI MAX 2
Android 11 by DJsmk123
1.INTRODUCTION
Well, Android 11, Google’s 11th iteration looks similar to Android 10 but with a handful of new features and changes. The update brings notification history, Chat bubbles, Conversation notifications, screen recorder, new media controls, smart device controls, one-time permission, improved dark theme with the scheduling system, app suggestions, wireless android auto, and many more....
2.Installation Guide
1.First Download AOSP11.zip
2.Now From Any recovery backup your device
Note:Recommended Recovery Orange Fox Recovery
3.Now Wipe all Partition except internal storage
4.Now Install AOSP11.zip
5.if during installation of AOSP11.zip its stuck and reboot to fastboot then try again install without wiping system its will works.
6.Reboot To System and Your Android 11 is Ready to go...
3.Workings
WiFi, Bluetooth, RIL, etc
4.Known Issues
Camera,Flashlight,Fingerprint[Major Issue but i am trying to resolve them]
5.Download Link: https://www.mediafire.com/file/b6v8nilxctnfkf5/aosp11.zip/file [Gapps Included]
6.Source
1.Rom source: https://github.com/phhusson/treble_experimentations/releases
2.Kernel Source:
https://forum.xda-developers.com/t/gsi-vendor-for-mm2-oxygen-by-team-o-8322.4139599/
as this post do not contain Kernel Source so i do not have kernel source....
Note: There is some three Major Bugs camera , Fingerprint And Flashlight and I am trying to resolve them but as i am not developer so its not easy for me
here i will provide log-cat error behind these errors and any one who is interested to resolve them his help will be appreciated as far as these errors the rom is perfect to use in daily life.....
{
CANNOT LINK EXECUTABLE "/system/vendor/bin/mm-qcamera-daemon": library "libgui.so" not found: needed by /vendor/lib/libmmcamera2_stats_modules.so in namespace (default)
CANNOT LINK EXECUTABLE "/vendor/bin/hw/[email protected]": library "libgui.so" not found: needed by main executable
CANNOT LINK EXECUTABLE "/vendor/bin/hw/android.hardware.[email protected]": library "libkeystore_aidl.so" not found: needed by main executable
}
Warning:I am not responsible to anything happen with your device if you are come here then you know what are you doing...
View attachment 5159823View attachment 5159825View attachment 5159827View attachment 5159829View attachment 5159837View attachment 5159833View attachment 5159835
Click to expand...
Click to collapse
New patchs for fingerprint
1.For Goodix Fingerprint flash Mochi-fix.zip
2.For FPC First flash Mochi-fix.zip and then fpc.fix
for Camera stay tune...
Some Android 11 Rom on the way...
DJsmk123 said:
New patchs for fingerprint
1.For Goodix Fingerprint flash Mochi-fix.zip
2.For FPC First flash Mochi-fix.zip and then fpc.fix
for Camera stay tune...
Some Android 11 Rom on the way...
Click to expand...
Click to collapse
I don't know what the problem might be with the camera but do you have any idea when that might be fixed please?
Thanks for your work.
thewizardoz said:
I don't know what the problem might be with the camera but do you have any idea when that might be fixed please?
Thanks for your work.
Click to expand...
Click to collapse
This vendor image based on android 9 and android 10(Not perfectly) so all libs of camara not working perfectly with android 11 system libs and for updating libs I have to find them and link to system.
Actually i am working on this phone it's sad that I have no extra phone for my personal use.
I can't say how much time...
Thanks for your appreciation
[delete]
{
"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"
}
YAAP is a project founded by Adhitya Mohan (@poad42) and Ido Ben-Hur (@idoybh) with the goal of staying close to AOSP in design goals, offer a clean interface, do as much as original development as possible and avoid becoming a kitchen sink and cherry picked mess.
Bug reporting:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
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 dmesg . (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.
Downloads
OTA Package | Fastboot Package
Follow us on Telegram for updates and faster(?) responses
Chat
Updates
How to flash using Fastboot or ADB sideload:-
Fastboot
Download Fastboot package
reboot to bootloader
Factory reset in the included recovery, if you are flashing for the first time
Reboot and enjoy YAAP
ADB Sideload
Download the OTA package
Reboot to recovery and use adb sideload to flash
Factory reset in the included recovery, if you are flashing for the first time
Reboot and enjoy YAAP
Note: This is a unified build for both the OnePlus 9R and 8T
ROM OS Version: Android 11
XDA:DevDB Information
Yet Another AOSP Project, ROM for the OnePlus 8T/9R
Contributors
OmkarTheAndroid, idoybh, poad42
Source Code: https://github.com/yaap
ROM OS Version: Android 11
ROM Kernel: Linux 4.19.x
ROM Firmware : OOS 11 Global Stable
Based On: AOSP
Version Information
Status: Stable
18-06-2021
Changelog:
ROM:
• Add support for wiping dynamic partitions in recovery
• Make flashing progress notifications persistent in OpenDelta
• Remove local file flash switch in OpenDelta
• Other layout and bugfuxes for OpenDelta
• Adjust biometric promopt for FOD devices
• Fix clock icon in Kai & Victor icon packs
• Various other optimizations and bugfixes.
Device:
• Initial unified build for OnePlus 8T/9R
• Fixed issues with NFC
• Switched to YAAP kernel
• Reworked DeviceSettings
• Added color modes from stock
• Updated blobs from OnePlus9ROxygen_13.I.04 & LA.UM.9.12.r1-10800-SMxx50.0
Awesome! Downloading now.
8t not found
The builds are unified, 8t and 9R have the same build.
kuto232 said:
8t not found
Click to expand...
Click to collapse
Initial thoughts:
Clean and speedy!
All the features appear to work great.
Status bar icon padding isn't mangled.
Fingerprint works really fast and is just like stock.
No issues with Magisk and SafteyNet. Widevine L1 is active!
There's no "Check proximity sensor before wake" option.
When charging with AOD option on, it doesn't show the batter % at the bottom (or anywhere). This is just a minor gripe. Fixed in 6/24 build!
poad42 said:
The builds are unified, 8t and 9R have the same build.
Click to expand...
Click to collapse
is this confirmed?
Does this include gapps? and should I unzip the fastboot zip and use the recovery from there to flash this?
Snekxs said:
Does this include gapps? and should I unzip the fastboot zip and use the recovery from there to flash this?
Click to expand...
Click to collapse
Gapps are included (looks like Nano/Micro). You can unzip and either flash each image to the appropriate partition or use one fo those ROM installer batch files, that basically does the same thing:
Code:
:choice
set /P c=Do you want to install ROM ( Reccomended )[Y/N]?
if /I "%c%" EQU "Y" goto :continue
if /I "%c%" EQU "N" goto :exit
goto :choice
:continue
:continue
goto :exit
:exit
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
ECHO FLASHING DONE.......
ECHO CLICK ENTER RECOVERY
ECHO WIPE DATA/FACTORY RESET
ECHO REBOOT SYSTEM
vnayrp said:
is this confirmed?
Click to expand...
Click to collapse
Duh, why else would I say it.
Snekxs said:
Does this include gapps? and should I unzip the fastboot zip and use the recovery from there to flash this?
Click to expand...
Click to collapse
Just do fastboot update fastabootoackagename.zip
xocomaox said:
Initial thoughts:
Clean and speedy!
All the features appear to work great.
Status bar icon padding isn't mangled.
Fingerprint works really fast and is just like stock.
No issues with Magisk and SafteyNet. Widevine L1 is active!
There's no "Chock proximity sensor before wake" option.
When charging with AOD option on, it doesn't show the batter % at the bottom (or anywhere). This is just a minor gripe.
Click to expand...
Click to collapse
You can thank OnePlus for breaking the time to full code in kernel, thus breaking indication stuff in userspace(notice how everything works when using a normal charger, but breaks when using dash). That said, there is a hacky workaround from los "that works". So will pick that for the next build.
poad42 said:
Duh, why else would I say it.
Click to expand...
Click to collapse
;-) apologies if i offended you you are the uploader!! I realize it... lol.
by the way guys.... this is a great rom. tried it and am using it since last night.. hopefully, wont change it for a week atleast. except for the camera app. very basic and I fail to receive how the 48mp option isn't opening up for most roms yet.
All the best to all you devs. ;-) thanks for the options and your efforts.
vnayrp said:
;-) apologies if i offended you you are the uploader!! I realize it... lol.
by the way guys.... this is a great rom. tried it and am using it since last night.. hopefully, wont change it for a week atleast. except for the camera app. very basic and I fail to receive how the 48mp option isn't opening up for most roms yet.
All the best to all you devs. ;-) thanks for the options and your efforts.
Click to expand...
Click to collapse
It is an incredibly good ROM. Worth leaving OOS for. Please use GCam and not that awful stock cam!
poad42 said:
You can thank OnePlus for breaking the time to full code in kernel, thus breaking indication stuff in userspace(notice how everything works when using a normal charger, but breaks when using dash). That said, there is a hacky workaround from los "that works". So will pick that for the next build.
Click to expand...
Click to collapse
Ah, of course! I didn't even test with a normal charger...
xocomaox said:
It is an incredibly good ROM. Worth leaving OOS for. Please use GCam and not that awful stock cam!
Ah, of course! I didn't even test with a normal charger...
Click to expand...
Click to collapse
Can I use any gcam or is there a specific one that's made for the 8t?
Snekxs said:
Can I use any gcam or is there a specific one that's made for the 8t?
Click to expand...
Click to collapse
Use 8.1 Wichaya
EDIT: There is newer GCam available. Old still works but there may be problems like shooting Video.
25-06-2021
ROM:Fix issues for slower brightness ramp ratesRevert "display: Don't animate screen brightness when turning the screen on" as this causes some issues with AoDDevice:Debloated init from useless services and oneplus additionsUpdate init from LA.UM.9.12.r1-11800-SMxx50.QSSI12.0Build nfc stack from sourceRemove Oneplus framework stuffDrop unused pixelworks halFix charging time in lock screen while dash chargingUpdate audio fx blobs from LA.UM.9.12.r1-10800-SMxx50.0
OTA Package Fastboot Package
{
"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"
}
CyanogenMod 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. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
We need testers! Join to our Discord server!
Join the J110H Android Development Discord Server!
Check out the J110H Android Development community on Discord - hang out with 3 other members and enjoy free voice and text chat.
discord.gg
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Installation:
- Reboot to TWRP (if you don't have it yet, view my threads!)
- Wipe data,system,cache,dalvik
- Install the ROM
- Reboot!
What does work:
- Audio
- Flashlight
- ADB
- Sensors
- RIL
- Camera (use OpenCamera)
- ART + Dalvik support
What does partially work:
- GPS
What doesn't work:
- WiFi
- Bluetooth
- RIL
- File Manager can't detect external/internal storage
- MTP
- FM Radio (removed from ROM)
Won't fix:
- WiFi
- Bluetooth
- RIL
Download: https://androidfilehost.com/?fid=14655340768118447620
Kernel source: https://opensource.samsung.com/uploadSearch?searchValue=J1
Credits:
@TriDiscord , @mozzafar alali , @Pixi_Vision , @SoumyajitGiri for testing my roms
@TriDiscord (& me) again for his work
me for the idea to resurrect this device
CyanogenMod
OmniROM
XDA: DevDB Information
CyanogenMod 11, ROM for Samsung Galaxy J1 Ace DUOS
Contributors
ROM OS Version: 4.4.4 Kitkat
ROM Kernel: Linux 3.10x
Version Information
Status: Unstable
Created: 04-04-2022
Last Updated: 04-04-2022
Great job.
notnoelchannel said:
Installation:
- Reboot to TWRP (if you don't have it yet, view my threads!)
- Wipe data,system,cache,dalvik
- Install the ROM
- Reboot!
Click to expand...
Click to collapse
I believe I have successfully flashed the ROM with TWRP after wiping ^ but my j1 ace is
puking same red exclamatory mark on left corner and getting struck on boot logo
calling it a day now, will tinker tomorrow.
this warning might be stock sambung bootloader teasing (-_-
btw /data partition seems to be empty after flashing, ideal? dmesg and recovery logs from twrp
displ .nl/xd/samtwrp_dmesg.log.txt
displ .nl/xd/samtwrp_recovery.log.txt
Hisacro said:
I believe I have successfully flashed the ROM with TWRP after wiping ^ but my j1 ace is
puking same red exclamatory mark on left corner and getting struck on boot logo
calling it a day now, will tinker tomorrow.
Click to expand...
Click to collapse
flash this boot.img on twrp and reboot
notnoelchannel said:
flash this boot.img on twrp and reboot
Click to expand...
Click to collapse
success! I was able to boot this rom but the prompt
> Unfortunately, phone has stopped (button - ok)
keeps on popping, I played fast console tapping game to move past initial setup but this
prompt persists even after reboot
in a way it's a step forward (?)
-x-x-
can confirm working
- audio (used alarm)
- flashlight
- ADB
- Sensor (auto orientation)
btw mind knowing where did cmboot.img come from? is it dedicated bootloader for cynanogenmod?
Hisacro said:
success! I was able to boot this rom but the prompt
> Unfortunately, phone has stopped (button - ok)
keeps on popping, I played fast console tapping game to move past initial setup but this
prompt persists even after reboot
in a way it's a step forward (?)
-x-x-
can confirm working
- audio (used alarm)
- flashlight
- ADB
- Sensor (auto orientation)
btw mind knowing where did cmboot.img come from? is it dedicated bootloader for cynanogenmod?
Click to expand...
Click to collapse
Normally it should not be named CMBOOT under any circumstances, but it was named CMBOOT beacuse well... "CyanogenMod Boot (Image)"
It would normally be named something like boot_cyanogenmod.img but oh well
TriDiscord said:
Normally it should not be named CMBOOT under any circumstances, but it was named CMBOOT beacuse well... "CyanogenMod Boot (Image)"
Click to expand...
Click to collapse
does `CMBOOT` mean something else? web searches of it doesn't bring up anything related to bandroid
TriDiscord said:
It would normally be named something like boot_cyanogenmod.img but oh well
Click to expand...
Click to collapse
pardon my ignorance, does /boot partition needs to flashed with custom bootloader for custom roms to be seen or just the case for this sambung?
from my glances of cyberspace (mis?)info, doesn't unlocking stock bootloader enough to recognize?
Hisacro said:
does `CMBOOT` mean something else? web searches of it doesn't bring up anything related to bandroid
pardon my ignorance, does /boot partition needs to flashed with custom bootloader for custom roms to be seen or just the case for this sambung?
from my glances of cyberspace (mis?)info, doesn't unlocking stock bootloader enough to recognize?
Click to expand...
Click to collapse
cmboot is the stock kernel i just named it cmboot because..why not?
notnoelchannel said:
cmboot is the stock kernel i just named it cmboot because..why not?
Click to expand...
Click to collapse
o_0 haha
Hisacro said:
> Unfortunately, phone has stopped (button - ok)
keeps on popping, I played fast console tapping game to move past initial setup but this
prompt persists even after reboot
Click to expand...
Click to collapse
bump ^
Hisacro said:
o_0 haha
bump ^
Click to expand...
Click to collapse
Remove Phone.apk and telephony stuff..that worked for me
thought Phone as literal phone
notnoelchannel said:
Remove Phone.apk and telephony stuff..that worked for me
Click to expand...
Click to collapse
affirmative. Phone, bluetooth & simtoolkit
Hello, @notnoelchannel Remember me I have successfully installed your rom no popups like system stopped but wifi is not working the main thing is not working GPS not working, and Bluetooth, ril already mention they won't be fixed but WiFi must be fixed pls
SoumyajitGiri said:
Hello, @notnoelchannel Remember me I have successfully installed your rom no popups like system stopped but wifi is not working the main thing is not working GPS not working, and Bluetooth, ril already mention they won't be fixed but WiFi must be fixed pls
Click to expand...
Click to collapse
Those won't be fixed until sources are provided by original authors of the ROMs
this rom is awesome, absolutely no drain of battery! (been at 96% since last week haha)
Hisacro said:
this rom is awesome, absolutely no drain of battery! (been at 96% since last week haha)
Click to expand...
Click to collapse
No drain of battery because RIL is not working...
TriDiscord said:
No drain of battery because RIL is not working...
Click to expand...
Click to collapse
suee suee don't spill it
TriDiscord said:
Those won't be fixed until sources are provided by original authors of the ROMs
Click to expand...
Click to collapse
original authors?
came across these past works (anything related?)
android_device_samsung_j1pop3g/ril/SamsungSPRDRIL.java at cm-12.1-test · ahmedgamal17/android_device_samsung_j1pop3g
Contribute to ahmedgamal17/android_device_samsung_j1pop3g development by creating an account on GitHub.
github.com
Hisacro said:
original authors?
came across these past works (anything related?)
https://github.com/ahmedgamal17/and.../blob/cm-12.1-test/ril/SamsungSPRDRIL.java[/U
Click to expand...
Click to collapse
the ROM has been ported from J100H and the device tree you linked is invalid so it won't help us
SoumyajitGiri said:
Hello, @notnoelchannel Remember me I have successfully installed your rom no popups like system stopped but wifi is not working the main thing is not working GPS not working, and Bluetooth, ril already mention they won't be fixed but WiFi must be fixed pls
Click to expand...
Click to collapse
hey! why did you ignore me if I can ask?
RIL n bluetooth might be fixed but ... I can't fix WiFi due to different drivers.
These are the solutions for WiFi:
a) you make a custom kernel also a custom wifi driver from scratch
b) you compile from source with j13g's device tree
c) use stock sprdwl.ko (Won't work)
Tri's solution:
a) read that it won't be fixed
b) make logcats if you want the not working thing fixed
c) or don't download the rom........
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OrangeFox Recovery is one of the most popular custom recoveries, with amazing additional features, fixes and a host of supported devices.- Warnings :
Your warranty is now void, or not... (i have no idea bruh)
・ I'm not responsible for bricked devices, thermonuclear war or alarm app fails.
・ If it's your first time or you're unexperienced with flashing ROMS, please do some search before flashing!
・ YOU are choosing to make these modifications, you're the only responsible guy for messing up if you do so.
- Informations :
- Was built on the 11th of September 2022.
- Maintained by kota. (me)
- Used Kernel : Here!
- What's broken ?
- The Status Bar can now be totally seen but doesn't totally fit.
- Vibration still doesn't work normally (there have been changes to it tho)
- Please report anything else if you do find an issue!
- Installation Guides :
- Notes :
A glitch may happen where booting it via fastboot makes touch doesn't work sometimes.
To fix that, i also provided a flashable zip via sideloading (tested on TWRP) that directly installs it.
- First way to install : (Casual way, if touch works okay | .img )
1 · Reboot into bootloader and boot OrangeFox by using this command : fastboot boot OrangeFox.img
2 · Once the Recovery boots up, go to 4th menu (3 lines), and on it, click "More".
3 · Then click More, and Flash Current OrangeFox Recovery, then swipe and reboot!
- Second way : (More tricky, but always works out fine | .zip )
1 · Reboot into Recovery Mode with TWRP installed.
2 · Prepare an ADB Session on your PC and add to it the .zip version of OrangeFox.
3 · Get into Sideload Mode and do this command on adb : adb sideload OrangeFox_Name_Example.zip
- You're now done with flashing!
- Download Links :
- OrangeFox Folder (ZIP + IMG version) : Here!
- End :
Well, here it is! Real working OrangeFox for Mi 11.
At first it was just a random idea that went threw my head two month ago.
Now it's a real thing, it was really time consuming and head scratching but it was all worth it!
Enjoy and have a nice day!
By kota.
Please note!
For the second flashing method, TWRP isn't really "required", it's more to assure that your recovery let's you sideload any unsigned packages. You should be able to flash from some recoveries such as Pixel Experience and ArrowOS recovery.
As for unsupported ones such as CherishOS, RiceDroid, etc... They'll probably throw an Error 21 when trying to sideload any unsigned packages. (in this case, Orangefox but could also be Magisk) For them, simply use TWRP.
Reserved! #2
does this allow full backup and restore of the ROM?
Sage said:
does this allow full backup and restore of the ROM?
Click to expand...
Click to collapse
The "quick backup" (whatever it is) provides a backup of data and boot partitions. I'm not totally sure that the quick backup option is related to the one on main screen tho
Hello, thanks for your work, this recovery is amazing !
Appreciate the great work!
Is this recovery working fine for A12 custom roms? (In terms of data/internal storage decryption)
bongmeiister said:
Appreciate the great work!
Is this recovery working fine for A12 custom roms? (In terms of data/internal storage decryption)
Click to expand...
Click to collapse
Yup it works, at least with Pixel Experience it works. You just have to type in your code because the partition is encrypted
Nysioko said:
Yup it works, at least with Pixel Experience it works. You just have to type in your code because the partition is encrypted
Click to expand...
Click to collapse
Great, currently I'm running Evolution X with newest TWRP and there the recovery has problems with decrypting the internal storage - no matter what I try. I think it was not made for Android 12. https://wiki.orangefox.tech/en/guides/encryption Android 12 Custom Recoveries
What code do you mean to decrypt the partition? - Thanks for your response
bongmeiister said:
Great, currently I'm running Evolution X with newest TWRP and there the recovery has problems with decrypting the internal storage - no matter what I try. I think it was not made for Android 12. https://wiki.orangefox.tech/en/guides/encryption Android 12 Custom Recoveries
What code do you mean to decrypt the partition? - Thanks for your response
Click to expand...
Click to collapse
The code to decrypt the partition is the same you had to put in to lock your phone. Say you have a pin code of 3926, just type 3926 to unlock the score from orangeFox
bongmeiister said:
Appreciate the great work!
Is this recovery working fine for A12 custom roms? (In terms of data/internal storage decryption)
Click to expand...
Click to collapse
Of course it's made for A12
First link is dead
Nysioko said:
First link is dead
Click to expand...
Click to collapse
Oops! Fixing that
kotalol said:
Oops! Fixing that
Click to expand...
Click to collapse
Thanks
Excellent, working perfectly!
(other than vibration, which is very weird indeed!)
Hoping you will continue your great work, and build for A13...
nelvinchi said:
Excellent, working perfectly!
(other than vibration, which is very weird indeed!)
Hoping you will continue your great work, and build for A13...
Click to expand...
Click to collapse
Yep, A13 is coming soon...
With A13 decryption support, fix trial to vibration, removal of flashlight button, base on latest sekaiacg TWRP and much better holepunch handle!
Does it recognize and mount USB OTG? So I can do backups to USB storage?
seemebreakthis said:
Does it recognize and mount USB OTG? So I can do backups to USB storage?
Click to expand...
Click to collapse
Not yet because of the used kernel in pre-release, the next version will probably support ExFat USB OTG.
Hi, does anyone knows that this recovery works for Xiaomi EU roms ? Thank you !
epcwong said:
Hi, does anyone knows that this recovery works for Xiaomi EU roms ? Thank you !
Click to expand...
Click to collapse
It does!
{
"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"
}
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
DO NOT USE ORANGEFOX FOR THIS !!! YOU WILL REGERET. ANDROID 12 AND ABOVE BREAK OLD RECOVERYS!!! Due to Platform Changes.
PLS UPGRADE TO TWRP 3.7 before installing the ROM https://drive.google.com/u/0/uc?id=1IDFv-vrfFu0cysHPzXoT8Mf21z4ZLp99&export=download
What works :
-you tell me
Bugs :
Camera 1080p video recording lag
not working codec2: (disabled)
no working gps
no working Bluetooth headset mic in calls
no working fingerprint
vsync is in the future
selinux permissive
broken drm (widevine)
Keep in mind that some LineageOS features have not been completed yet this is not a device bug and please do not report those
in this rom thread, also do not post bug reports for known issues or bug reports without proper
a) Logcat
b) proc/last_kmsg (or proc/kmsg)
c) data/tombstones
d) dmesg
0. [RECOMMENDED] Make sure you have an Oreo bootloader and modem before installing this. (ie : you have been in stock oreo once)
1. [RECOMMENDED] Do a good backup first
2. [ONCE] Make sure you did flash the inital Astrako's repartition script (https://forum.xda-developers.com/t/tool-a320fl-f-y-repartition-script-for-vendor-support.3951105/) to create a vendor partition.
Flashing this script will install (an old) TWRP.
3. Make sure you are using TWRP 3.7.0 (mentionned below)
4. [OPTIONAL/ONCE] Flash my custom repartition script (https://t.me/debieLineageOS/180) to shrink partition sizes, then format data.
6. [CLEAN FLASH] In recovery wipe everything except SD and OTG.
7. Flash LineageOS.
8. [OPTIONAL] Flash MindtheGApps .
9. [OPTIONAL] Flash Magisk.
10. Reboot. Booting should take less than 3 mins.
Generally it's ok to dirty flash, but if you encounter issues a clean flash should be the first thing on your mind.
Note : Flashing a repartition script should only be done once (unless you flash stock or the pit file which revert them) unless a release not say so.
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)
Download :
androidfilehost
Made by : @Flominator Astrako and @GonicTEAM @TheObcd
Device trees : https://github.com/samsungexynos7870/android_device_samsung_a3y17lte/tree/lineage-19.1-oss_bsp-vndk
ROM OS Version : Android 12.1
Kernel : 3.18
Telegram Support Group
Thank you for this work. I have started to test it, and I have 2 feedback. First it does not include fingerprint unlocking. Second, it is a major bug, I cannot enter any more into recovery, it gives a loop on Orangefox screen. Any solution?
Bernique said:
Thank you for this work.
Click to expand...
Click to collapse
that wasn't me
Bernique said:
I have started to test it, and I have 2 feedback. First it does not include fingerprint unlocking. Second, it is a major bug, I cannot enter any more into recovery, it gives a loop on Orangefox screen. Any solution?
Click to expand...
Click to collapse
report bugs to @Flominator
F-Google said:
that wasn't me
Click to expand...
Click to collapse
Why do you create a thread then ? Since it is Flominator work, he could choose to or not to share his work here. What is the goal to share the work of another person without being able to help ?
Bernique said:
I cannot enter any more into recovery, it gives a loop on Orangefox screen.
Click to expand...
Click to collapse
It works fine with TWRP6.X .Flominator told us to use TWRP in telegram .
TheObcd said:
It works fine with TWRP6.X .Flominator told us to use TWRP in telegram .
Click to expand...
Click to collapse
yes, use twrp 3.70 from @Batuhantrkgl
Bernique said:
Thank you for this work. I have started to test it, and I have 2 feedback. First it does not include fingerprint unlocking. Second, it is a major bug, I cannot enter any more into recovery, it gives a loop on Orangefox screen. Any solution?
Click to expand...
Click to collapse
DO NOT USE ORANGEFOX FOR THIS !!! YOU WILL REGERET. ANDROID 12 AND ABOVE BREAK OLD RECOVERYS!!! Due to Platform Changes.
PLS UPGRADE TO TWRP 3.7 before https://drive.google.com/u/0/uc?id=1IDFv-vrfFu0cysHPzXoT8Mf21z4ZLp99&export=download
@F-Google Pls add this as a waring in:
DO NOT USE ORANGEFOX FOR THIS !!! YOU WILL REGERET. ANDROID 12 AND ABOVE BREAK OLD RECOVERYS!!! Due to Platform Changes.
PLS UPGRADE TO TWRP 3.7 before installing the ROM https://drive.google.com/u/0/uc?id=1IDFv-vrfFu0cysHPzXoT8Mf21z4ZLp99&export=download
- put (Beta) in thread title
this build has still a lot of bugs:
Camera 1080p video recording lag
not working codec2: (disabled)
no working gps
no working Bluetooth headset mic in calls
no working fingerprint
vsync is in the future
selinux permissive
broken drm (widevine)
- add bugs to buglist.
Initialy this was the reasone why I didnt post on xda yet.
- add step by step guide install instructions from stock rom to this for newbies like:
1. ...
2. ...
3. ...
as the install process is more way more complex than on other devices.
- provide a link of mindgapps mirror as they are reccomended by LineageOS themselves
-give astrako and gonic credits
best regards Flominator
Bernique said:
Thank you for this work. I have started to test it, and I have 2 feedback. First it does not include fingerprint unlocking. Second, it is a major bug, I cannot enter any more into recovery, it gives a loop on Orangefox screen. Any solution?
Click to expand...
Click to collapse
sorry to you, but the only fix is to reflash the recovery with pc.
Flominator said:
sorry to you, but the only fix is to reflash the recovery with pc.
Click to expand...
Click to collapse
Thank for your thoughts, but I was somehow aware of the risk, especially when there is no comment on the status of the development.
Thanks to all for the new TWRP, I missed this information
@F-Google thx for updateing the thread
F-Google said:
0. [RECOMMENDED] Make sure you have an Oreo bootloader and modem before installing this. (ie : you have been in stock oreo once)
1. [RECOMMENDED] Do a good backup first
2. [ONCE] Make sure you did flash the inital Astrako's repartition script (https://forum.xda-developers.com/t/tool-a320fl-f-y-repartition-script-for-vendor-support.3951105/) to create a vendor partition.
Flashing this script will install (an old) TWRP.
3. Make sure you are using OrangeFox R11.0 (https://forum.xda-developers.com/t/...f-y-orangefox-recovery-project-r11-0.4032121/) (or TWRP 3.6+ (https://t.me/debieLineageOS/1766) in case you use LineageOS18+).
4. Download the Lineage build (https://t.me/debieLineageOS/172), optionally GApps (https://opengapps.org/) and Magisk (https://github.com/topjohnwu/Magisk/releases).
5. [OPTIONAL/ONCE] Flash my custom repartition script (https://t.me/debieLineageOS/180) to shrink partition sizes, then format data.
6. [CLEAN FLASH] In recovery wipe everything except SD and OTG.
7. Flash LineageOS.
8. [OPTIONAL] Flash GApps (arm64, pico or nano only).
9. [OPTIONAL] Flash Magisk.
10. Reboot. Booting should take less than 3 mins.
Generally it's ok to dirty flash, but if you encounter issues a clean flash should be the first thing on your mind.
/!\ OTA builds do NOT guarantee dirty flashing will work fine. (Magisk can cause issues for instance)
Note : Flashing a repartition script should only be done once (unless you flash stock or the pit file which revert them) unless a release not say so.
Click to expand...
Click to collapse
May you not blindly copy past what I wrote in telegram ? This tutorial is about the LineageOS17 releases I share on github/telegram. Some sentences are not appropriated here. I let you correct them. Furthmore you're free to use control + k to insert link .
About OTA, I am not aware of Flominator doing so (but I may be wrong).
TheObcd said:
May you not blindly copy past what I wrote in telegram ? This tutorial is about the LineageOS17 releases I share on github/telegram. Some sentences are not appropriated here. I let you correct them. Furthmore you're free to use control + k to insert link .
About OTA, I am not aware of Flominator doing so (but I may be wrong).
Click to expand...
Click to collapse
corrected wrong and outdated things
F-Google said:
corrected wrong and outdated things
Click to expand...
Click to collapse
Still some work to do...
@roirraW "edor" ehT please can you close the thread, the rom is WIP again @Flominator will post when it's done
F-Google said:
@roirraW "edor" ehT please can you close the thread, the rom is WIP again @Flominator will post when it's done
Click to expand...
Click to collapse
Thread has been closed on request of OP!
@F-Google Just a remark: The best, most efficient and fastest way to get such requests accomplished is to alert the moderators team via the report function instead of posting the request and pinging a moderator. Please be aware, with 75M+ posts in 3.5M+ threads were unable to monitor posts. And moderators are spread all over the globe and due to different timezones pings might not be noticed for many hours or for days/weeks in case of a moderator's absence. Contrary, a report will alert "the moderator on duty".
Regards
Oswald Boelcke
Senior Moderator
CC: @roirraW "edor" ehT