{
"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"
}
First I'm not the developper of this rom and just share it here
credits go to @NeoArian
Be aware that it's a provisory thread and the dev will create his own when he decide ....
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
@NeoArian made a flashable zip for having MIUI camera on LOSHere is the camera..I repeat Im not the creator of this file, you must thank @NeoArian for this and his perfect rom
LineageOS 19.1 for Xiaomi M2101K9G (renoir)
Build date: 2022-11-01
Security patch: 2022-10-05
Variant: GMS
Changelog (https://www.lineageoslog.com/19.1/renoir)
Download
lineage-19.1 (https://download.lineageos.org/devices/renoir/builds)
lineage-19.1 MicroG (https://download.lineage.microg.org/renoir/renoir/)
⛭ GitHub release / additional files
Build date: 2022-09-27
Spoiler
Security patch: 2022-09-05
Variant: VANILLA
changelog
Download
lineage-19.1 (https://github.com/arian-ota/ota/re...f/lineage-19.1-20220927-UNOFFICIAL-renoir.zip)
⛭ GitHub release / additional files (https://github.com/arian-ota/ota/releases/tag/19.1-renoir-3746432f)
SHA-256 checksum
3746432fe6134e94aabfb1efad645aec882da1ddba48b39c70b5548a0abd3120
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++===========================================================================================
Build date: 2022-09-25
Security patch: 2022-09-05
Variant: GMS
changelog
Download
lineage-19.1 (https://github.com/arian-ota/ota/re...neage-19.1-20220925-UNOFFICIAL-GMS-renoir.zip)
⛭ GitHub release / additional files (https://github.com/arian-ota/ota/releases/tag/19.1-renoir_gms-4eab216d)
SHA-256 checksum
4eab216d294330b851005b8166d3e356e41e72729831b696d915f026027133e6
Spoiler: Earlier versions
Build date: 2022-08-29
Security patch: 2022-08-05
Variant: GMS
Changelog
Download
Lineage 19.1
⛭ Github release/additional files
SHA-256 checksum
b5b38148be07ed66d614dfada0acc2587420f2a763c36fd6d8647db6eb0c903f
Credits and thanks to @NeoArian
Installation Instructions:
Lineage Os Installation:
1- Install LOS Recovery: With the phone in FASTBOOT mode in the Platform-tool folder and the necessary files, open the CMD
2- Next we place in the window: fastboot flash boot_ab boot.img and then fastboot flash vendor_boot_ab vendor_boot.img to finish fastboot reboot recovery
3- The cell phone will restart in recovery mode with LOS recovery already installed (it is managed with the volume and power keys)
4- Perform Format Data (do not restart again)
5- Give Apply Update and then Apply Update from SDcard1 and look for the ROM
6- Then Reboot System Now (WILL INITIATE THE ROM)
7- Force restart in recovery to install Gapps (PICO Recommended)
8- Apply Update, Apply update from SDcard1 choose the gapps
9 Reboot System Now and enjoy XD
ALTERNATIVE WAY OF FLASHING THE ROM see post 2
ALTERNATIVE WAY OF FLASHING THE ROM
For those like me who have issue with flashing this rom here i what I do to bypass recovery issue..
after flash boot+vendor and start on LOS recovery and format data, I click update but I haven' apply update from sdcard1 but justapply from ADB..in advanced settings, there isn't such option....so I installed with ADB sideload
that what I do, and after 1 error I tried again and got error when I command adb reboot that system was not installed but I'm now on your rom....only issue is with my sdcard not recognized...have to backup on pc, format and recopy back, but certainly error on my side when I flash back miui rom.......
Install Custom ROM with ADB sideload
What is Android Debug Bridge?
ADB is a command-line tool included in the Android SDK development kit. It is used to communicate with any device that runs the Android operating system. You can use the ADB commands to perform various operations on your Android device.
With the help of the Android Debug bridge, you can install custom ROMs, mods, GApps, backup Android, flash official stock firmware, and install Android apps. Besides, you can also use ADB to uninstall bloatware without Root, downgrade an app, etc.
What is ADB Sideload?
ADB sideload, a command that transfer and install a zip file on an Android device from the PC. This command is handy for a custom ROM developer to push and install any installation zip file directly on a device.
The sideload feature was introduced with the Android Jelly bean recovery. Most importantly, this sideload mode requires a TWRP recovery version 2.3 or higher. Besides, it is also essential to install the latest ADB binaries on your PC.
How to Flash Custom ROM using ADB and Fastboot
Are you ready to use ADB and Fastboot for flashing custom firmware on your Android phone? Then let’s get started.
Warning
Ensure to install the right custom ROM on your Android phone. Do NOT proceed if the firmware is incompatible with your phone model number.
Requirements
A Windows PC and a standard USB cable.
Charge your device to a minimum of 50%.
Install mobile USB drivers on your computer.
Enable USB Debugging mode from your device settings.
Also, enable the OEM unlocking and Advance reboot mode.
Moreover, unlock your device bootloader.
Install TWRP 2.3 or higher on your Android device.
(Optional) Temporarily disable antivirus and firewall on your PC.
Steps to Install Custom ROM using ADB Sideload
Follow these step-by-step instructions to sideload the zip file on your Android phone.
1. Download Custom ROM
At first, download the mobile-specific Android custom ROM on your PC.
Ensure that the ROM file is in zip format.
Also, download the correct firmware that is compatible with your device’s model number.
2. Install ADB and Fastboot drivers
Download and install the latest ADB drivers on your computer.
Make sure that the ADB version is 1.0.29 or higher.
3. Transfer Custom ROM to ADB folder
Copy the downloaded custom ROM and paste it into the ADB folder.
The folder default location will be C:\Program Files\Minimal ADB and Fastboot.
4. Boot Android phone into Recovery mode
Switch off your Android phone.
Now, restart it into recovery mode.
Every device has different methods to boot into recovery.
You can either Google it or use the Recovery reboot app from Play Store.
5. Set the device into ADB sideload mode
As soon as you enter the recovery mode, click on the Advanced button.
On the next screen, click on the ADB sideload option.
6. Connect Android phone to PC
Now, connect your Android device to the computer using a USB cable.
Keep the device as it is in sideload mode.
After a successful connection, tick the Wipe Davik Cache and Wipe Cache options.
Then, swipe right on your device to start sideload.
7. Launch CMD window
Open the ADB folder, hold your keyboard’s Shift button, and right-click.
From the list of options, tap on the Open command window here option.
This will open the command prompt window on your PC.
8. Confirm the ADB connection
Furthermore, type the below command in the cmd window and press the enter key:
adb devices
You’ll see some random numbers with a ‘List of devices attached’ message.
This will confirm that your Android device is successfully connected to the PC.
9. Flash Custom ROM with ADB sideload command
To flash the custom ROM zip package file, enter the below command in the CMD:
adb sideload LineageOS18.zip
Make sure to type the exact name of the custom ROM file.
Also, don’t forget to add the zip extension at the end.
Here, I’m flashing LineageOS18 custom ROM.
Finally, hit the enter key to begin the ROM flashing process.
10. Reboot Android phone
On the installation finishes, your device will show a message saying, ‘ADB sideload complete.’
Tap on the Reboot System option to restart your device.
or those who don't know how to use ADB sideload here is a tuto you can read
How to Flash Custom ROM using ADB sideload [Easy Steps]
Flash Custom ROM zip file with ADB and Fastboot commands on any Android phone. Install Custom Firmware without TWRP recovery using CMD.
How to use adb
Attachments
Mind sharing the device, kernel and vendor trees used to build this ROM? I want to build and try it out myself. Thank you and @NeoArian for the hard work btw.
calputer said:
Mind sharing the device, kernel and vendor trees used to build this ROM? I want to build and try it out myself. Thank you and @NeoArian for the hard work btw.
Click to expand...
Click to collapse
The trees and kernel are available on GitHub.com/renoir-development
The vendor repository can be extracted with extract-files.sh from the renoir tree. To do so, download the lineage zip, then cd to device/xiaomi/renoir and run "./extract-files.sh /path/to/lineage.zip".
I don't see a vendor_boot.img in the github release page but there's a dtbo.img file. What do we do with this file? Also I don't think TWRP for renoir is working with Android 12 am I right?
Sa
calputer said:
I don't see a vendor_boot.img in the github release page but there's a dtbo.img file. What do we do with this file? Also I don't think TWRP for renoir is working with Android 12 am I right?
Click to expand...
Click to collapse
Same here. Where can i download boot_ab boot.img and vendor_boot_ab vendor_boot.img ?
I tested the rom and managed to install. attached image with the command needed. It work after I tried to puzzle the correct way to install. PS (if don't work try install LineageOS 18 as base to start, this is how I done). [after <<fastboot reboot recovery>> command, your smartphone will go in recovery mode from that -reset data- and -apply update-].
source of files used <<github.com/ arian-ota/ota/releases/tag/19.1-renoir_gms-b5b38148>>
wanna ask to dev or expert: if this change about use of -dtbo- instead -vendor_boot- is android 12 new design fault (google)?
PS: the devs have some grudge against users for lacking info about rom installation? This is my first LineageOS custom rom, kinda hard to install.
So I flashed the rom using files from the git release and vendor_boot.img from MIUI13. And one problem is that the wallpaper preference in setting is not working. So I just decided to go back to MIUI 13 global and somehow twitter and reddit scrolling is smooth and does not stutter anymore. Interesting cause it was stuttering on every AOSP I've tried.
calputer said:
So I flashed the rom using files from the git release and vendor_boot.img from MIUI13. And one problem is that the wallpaper preference in setting is not working. So I just decided to go back to MIUI 13 global and somehow twitter and reddit scrolling is smooth and does not stutter anymore. Interesting cause it was stuttering on every AOSP I've tried.
Click to expand...
Click to collapse
vendor_boot from MIUI13 OTA or FASTBOOT? for odd reason my LIneage os 19 work even without installing it
Testing the ROM, it cannot read sd card in exfat, ntfs or ext3 file system, it always ask me to format in fat32. there's a workaroud? fat32 limit is annoying, and pretty sure original MIUI have support for exfat.
Ranball said:
vendor_boot from MIUI13 OTA or FASTBOOT? for odd reason my LIneage os 19 work even without installing it
Click to expand...
Click to collapse
From Fastboot zip. And the vendor_boot.img from Pixel Experience site also has the same size (98,304 KB), so I figured I could use it without any modifications.
Any news about update??
jellybean 4.1 said:
Any news about update??
Click to expand...
Click to collapse
no, not yet
I bought my mom a new Xiaomi Redmi Note 11 lite 5G. Before she has used the Xiaomi Redmi Note 8T, which now will be dedicated for banking apps or as Navigation device.
The Xiaomi RN 8T had some issues on a custom Rom, especially with the microphone on some Apps.
Now i consider to let the Xiaomi RN 11L on Stock ROM, to not disturb her phone experience. I'm a fan of the work of all the Custom ROM Creators and use it on all my own devices. But which one of the Custom ROMs does work properly and would you prefer, for daily use and a bigger amount of Gapps?
MonoPro9 said:
I bought my mom a new Xiaomi Redmi Note 11 lite 5G. Before she has used the Xiaomi Redmi Note 8T, which now will be dedicated for banking apps or as Navigation device.
The Xiaomi RN 8T had some issues on a custom Rom, especially with the microphone on some Apps.
Now i consider to let the Xiaomi RN 11L on Stock ROM, to not disturb her phone experience. I'm a fan of the work of all the Custom ROM Creators and use it on all my own devices. But which one of the Custom ROMs does work properly and would you prefer, for daily use and a bigger amount of Gapps?
Click to expand...
Click to collapse
Pixel Experience best stability for now, then this Lineage 19.1.
razor_1911 said:
Pixel Experience best stability for now, then this Lineage 19.1.
Click to expand...
Click to collapse
Thank you for the conclusion.
She want to stay with MIUI at least till the guarantee.
The Redmi Note 8T will be my next Toy
razor_1911 said:
Pixel Experience best stability for now, then this Lineage 19.1.
Click to expand...
Click to collapse
For renoir is the rom discontinued =(
@NeoArian made an update of his LOS with Gapps and Vanilla version.....I have flashed both and its working great....
thanks to him
Related
Credits
Moto X4 is getting some custom rom love, because @erfanoabdi worked in BEAST mode and created the trees for this device, even though he does not own the device.
Obligatory Warning: This guide and ROM assumes you know the fundamentals of fastboot, flashing TWRP, and running a flash all. Your warranty is voided because of the unlocked bootloader. This is a Third Party ROM. Things may not work as expected compared to stock (for better or for worse).
Warning 2: If you can't do fastboot commands, do a flash all, root your device or flash TWRP/ROM, please do not ask for help here. If you cannot flash all back to stock, please stay stock for everyone's sake.
Warning 3: if you don't flash the firmware zip so both slots have the firmware, when you boot after flashing, you WILL have a bootloop or even a brick.
Warning 4 : This is an Engineering build, which means it's pre rooted and all apps have access to root. Only the SU binary is missing.
Warning 5 : Kernel is permissive.
This is an initial release and it WILL have bugs. If your phone is a daily, and you cannot afford downtime or random reboots then please do not flash.
I am new to this, DO NOT expect fixes on the fly. Post logcats and I will see what I can do.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About Carbon ROM :
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Not Working :
[*] Engineering Build - you will get a strict mode red-rectangle flash.
no moto onenav gestuers
You tell me
How to Boot into fastboot/bootloader mode
1. Reboot phone, and keep volume down pressed while device is rebooting until you see bootloader mode screen.
2. While phone is off, press volume down and then press power button. Keep holding both until you see bootloader mode screen.
How to Install
Video is for LineageOS, but process is same for Carbon ROM as well.
Video
Moto X4 A/B Slots Explained
Steps
1. Download the ROM, TWRP (zip and Image), Gapps (optional) from Downloads section. Place TWRP image zip in same folder as where you have fastboot.
2. Prepare your phone for AOSP style ROMs. (download one of the firmwares depending on your model). Boot into bootloader mode.
Flash the firmware with the flash_all.bat (Windows) file or the flash_all.sh (Linux & Mac) (See links on Post #2).
Windows
Code:
flash_all.bat
Mac/Linux
Code:
./flash_all.sh
Tested only on XT1900-1 on Android 8.0 model for now. Feel free to try on other models. Check for any errors in the process, DO NOT proceed if you have any errors. Once flashed successfully, reboot into Android to make sure all is well.
Windows
Code:
fastboot reboot
Mac/Linux
Code:
./fastboot reboot
3. Wipe internal data. Reboot back into bootloader mode and run the command "fastboot -w" (this will erase EVERYTHING from your phone, even internal SD, but is needed to have these ROMs work). Make sure to remove your external sdcard before doing this. Once done, REBOOT into Android to make sure all is well. Skip all the setups.
Windows
Code:
fastboot -w
Mac/Linux
Code:
./fastboot -w
4. Transfer ROM zip and TWRP zip to internal memory of device. Reboot device into bootloader mode.
5. Boot to TWRP using fastboot. Using command prompt/terminal navigate to folder where fastboot is.
Windows
Code:
fastboot boot twrp-3.2.1-1-payton.img
Mac/Linux
Code:
./fastboot boot twrp-3.2.1-1-payton.img
5. Once booted into TWRP, click on Install - and select TWRP zip transferred in Step 1. Once done, Reboot back into system to check all is well.
6. Boot into TWRP again (reboot device, keep volume down pressed while device is rebooting. When you see bootloader mode, let go of volume down. Press volume up until you see recovery mode, press power button to select. Now you will boot into TWRP recovery).
8. Once in TWRP. Go to Wipe and swipe to factory reset. Go back, select Install and select Linage OS Rom zip, also add the TWRP zip file and click on install. Once done, wipe cache/dalvik.
Do note, recovery is built into kernel with our device so flashing any rom or kernel will result in TWRP being overwritten. DO NOT flash Magisk (any root package) or Gapps. Once ROM (and optional TWRP) have flash successfully, go to main menu :-
Now you have two options. If you WANT gapps do step 9. else go to 10. If you install gapps after booting into rom, gapps will crash. So, make your choice now.
9. Go back to TWRP main menu. Click on reboot, note down the slot you are on and select recovery.
You will now boot back into TWRP recovery. Click on reboot, and you should be on the other slot. Go back to main menu, transfer the gapps package to internal memory and install gapps.
10. Go back to TWRP main menu. click on reboot and select bootloader.
11. Once in bootloader mode. issue below command.
Windows
Code:
fastboot -w
Mac/Linux
Code:
./fastboot -w
Once done, reboot.
Windows
Code:
fastboot reboot
Mac/Linux
Code:
./fastboot reboot
11. To ROOT, booting into Android once is necessary whether you want gapps or not. After booting into Android once reboot back into TWRP, and then flash your root package zip, reboot and enjoy.
How to Update
Transfer rom, gapps and twrp zip to internal storage.
Boot to TWRP.
flash Rom + TWRP zip
Boot back to TWRP recovery
Flash GApps
Wipe Cache + Dalvik
Reboot to System
Coming from Another custom ROM, have already flashed firmware zip
Transfer rom, gapps and twrp zip to internal storage.
Boot to TWRP.
Wipe -> Swipe to factory reset
flash Rom + TWRP zip
Boot back to TWRP recovery
Flash GApps
Wipe Cache + Dalvik
Reboot to System
How to go back to stock
Support :
1) Search. Search, search, search. If you make the effort of reading atleast 5 pages back, most if not all your questions will be answered. I personally, will ignore any questions, if I know they have been answered in the last 5 pages. Not being rude, but please read.
2) If you can't find answers in last 5 pages, ask here, be respectful and have a good time.
Downloads :
TWRP (Zip + Image, Download 3.2.1-1): TWRP for Payton
ROM : Unofficial Carbon ROM (payton)
Gapps : OpenGapps
Magisk : Stable Magisk
Notes :
Only Clean Installation Please
Bug Report Without logs means nothing
3rd PARTY ADDONS/MODS :
While we have no issues with people using supersu/magisk/xposed/custom kernels/etc, we can't provide support for users who have them installed.
This thread is not the right place to discuss about mods/addons.
Reporting Bugs :
DO NOT Report bugs if you installed Xposed.
DO NOT Report bugs about Magisk Modules.
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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
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 above may be ignored.
Sources :
Carbon ROM
Device tree :
moto-sdm660-common
payton
Kernel :
moto-msm8998
Vendor tree :
moto-sdm660-common
payton
XDA:DevDB Information
Unofficial Carbon ROM cr-6.1 for Payton, ROM for the Moto X4
Contributors
erfanoabdi, mightysween, gee one, Lineage Team, Carbon Team
Donations
Donate to Carbon ROM
Buy me Coffee.
ROM OS Version: 8.1.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: No Requirements
Based On: AOSP
Version Information
Status: Testing
Created 2018-06-13
Last Updated 2018-06-17
Firmwares
Firmwares
https://forum.xda-developers.com/showpost.php?p=76775043&postcount=2
mine002
Changelog
17th June 2018
* fixed FM radio
* userdebug build (no more red border) Thanks again @erfanoabdi
Excellent work. What would you say are the main differences between Carbon and Lineage?
sizz-lorr said:
Excellent work. What would you say are the main differences between Carbon and Lineage?
Click to expand...
Click to collapse
Lineage is pure stock android, whereas Carbon offer some customizations! I have not tried the ROM yet, i am on RR right now! But as far as I know, it is going to be stable! :fingers-crossed:
I would like to try this ROM, however, I'm hesitant to due to I have the TWRP v 3.2.1-0 which doesn't make nandroid backups that can be restored.
Does the posted TWRP version (3.2.1-1) make restorable nandroid backups?
------------
NetSpeedZ said:
I would like to try this ROM, however, I'm hesitant to due to I have the TWRP v 3.2.1-0 which doesn't make nandroid backups that can be restored.
Does the posted TWRP version (3.2.1-1) make restorable nandroid backups?
------------
Click to expand...
Click to collapse
I've restored from a nandroid on the newest twrp and haven't had an issue. Just remove any pin or lockscreen security before buying into twrp or you can't decrypt.
brandontowey said:
I've restored from a nandroid on the newest twrp and haven't had an issue. Just remove any pin or lockscreen security before buying into twrp or you can't decrypt.
Click to expand...
Click to collapse
Copy that. I don't have lock screen enabled, just the 'screen saver' that shows when phone senses motion nearby and shows the clock, etc.
Appreciate the clarification.
------------
New build is up.
Changelog in post 2.
brandontowey said:
I've restored from a nandroid on the newest twrp and haven't had an issue. Just remove any pin or lockscreen security before buying into twrp or you can't decrypt.
Click to expand...
Click to collapse
Follow-up question to your reply:
When you made your backup, did you include System Image? If so, when you restored did you enable Boot, Data, System and/or System Image?
------------
NetSpeedZ said:
Follow-up question to your reply:
When you made your backup, did you include System Image? If so, when you restored did you enable Boot, Data, System and/or System Image?
------------
Click to expand...
Click to collapse
I did whatever the default in TWRP was, backup and restore. I googled what I should do but there wasn't anything definite. I did get an error 255 from resting the Bluetooth thing so i just omitted it.
I'm on the fence looking at these new custom ROMs available for our X4, so please help me clarify a few points:
1) does Lineage have the option to set navigation bar height? If I'll take the plunge I'm interested in having a navigation bar narrower than Android' standard;
2) is it possible to tweak the kernel with Kernel Adiutor or something similar?
3) is it possible to install and use Moto Display in some way?
Thanks!
P.S. Plese bear with me as I'm asking the same questions all over the three custom ROMs threads.
One button navigation
Is one button navigation still not working on this rom?
superj1018 said:
Is one button navigation still not working on this rom?
Click to expand...
Click to collapse
not yet.
{
"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"
}
ViperExperience 12L GSI for U12+
"Choose your flavor! - The next Generation Viper ROM"
Dear Community,
Venom ROMs takes the next big step for your HTC, as well as other Treble A/B devices out there! You want Android 11, but don't want to miss out on the hardware benefits of your HTC U12+? Or you want to enjoy all of your beloved HTC Apps on another OEM? Then we have the best of both worlds for you today (or very soon)! Decide for yourself between an Android Stock Experience, or an HTC Sense Experience by choosing between Pixel Launcher and HTC Sense 10 UI Launcher. On your HTC U12+ you can in addition continue to use your popular HTC features like HTC Edge Sense, HTC FaceUnlock and the HTC Camera!
We at Venom ROMs are using the AOSP GSI based on Android 11 to bring you the best HTC features paired with the latest Android AND Pixel experience from Android 10.
Thanks to @phhusson for his Treble experimentations repos, @JEANFRIVERA, @5m4r7ph0n36uru, @Captain_Throwback, @MassStash, @donmarkoni for all tests you did for me to make this ROM.
mikalovtch
Must have unlocked bootloader from htcdev.com or factory S-OFF
Download Viper Experience 11 GSI from Androidfilehost.com
Download „vbmeta_noverity.zip“ from Androidfilehost.com
Download latest TWRP from #2 post or Download latest PBRP from here: PBRP
Boot your Device in Bootloader Mode
Boot to TWRP or PBRP, using the following command:
Code:
fastboot boot nameoftwrpimage.img
Rename „vbmeta_noverity.zip“ to „update.zip“ and place it inside your adb/fastboot folder
Push „update.zip“ to your device, using the following command:
Code:
adb push update.zip /update.zip
Make sure you are on slot A on reboot page of TWRP or PBRP if not switch to slot A and fasboot boot twrp.img again
Flash „update.zip“ from recovery UI
Reboot to Download from recovery UI
Erase userdata and system using the following commands: (THIS WILL FORMAT INTERNAL STORAGE!)
Code:
fastboot erase userdata
and:
Code:
fastboot erase system
Flash Viper Experience 10 GSI, using the command:
Code:
fastboot flash system nameofimage.img
Rebootyour device, using the command
Code:
fastboot reboot
Setup and enjoy an mew ROM on your HTC U12+!
XDA:DevDB Information
12-04 - ViperExperience Beta 12 | Android 12L | April 2022 Security Patch |GSI , ROM for the HTC U12+
Contributors
mikalovtch, JEANRIVERA
Source Code: https://github.com/phhusson/treble_experimentations
ROM OS Version: Android 12L
ROM Kernel: Linux 4.x
ROM Firmware Required: Android 9 Pie
Based On: AOSP HTC Sense
Version Information
Status: Beta
Beta Release Date: 2020-12-22
Created 2020-03-07
Last Updated 2020-12-22
Prerequisites
PIE_noverity_vbmeta_both_slots-TWP.zip: This zip patches the stock vbmeta for BOTH slots to ensure the device will boot after flashing the GSI. The zip in the OP only patches slot A, so you would have to ensure you are on slot A when flashing the system image. This zip allows either slot to be used. Thanks @The_Walking_Playground for posting the updated zip!
Fixes
UPDATE-BeyondStock™_U12+_Exodus_Vendor_Fixes-CPTB-signed.zip: This zip patches the vendor partition on U12+ and Exodus devices to fix Bluetooth streaming/headset compatibility, and enables exFAT support with the stock and BeyondStock™ kernels (NOTE: The exFAT portion of this fix is no longer needed, but has no negative side effects).
Patches
UPDATE-BeyondStock™_Header_Patch_U12+_Exodus-CPTB-signed.zip: This zip patches the boot.img header of the installed kernel so that decryption will work in permanently installed TWRP. This zip should be used if you're using a custom kernel that doesn't require patching for touch.
UPDATE_BeyondStock™_U12+_Exodus_Remove_Forced_Encryption_CPTB_signed.zip: This zip disables forced encryption on the device so that it doesn't automatically get encrypted after Formatting Data in TWRP.
Custom Recovery
Official TWRP for U12+: This is the recommended TWRP version to use with the ROM, with full Android 11/12 decryption support.
Kernels
UPDATE-BeyondStock™-Kernel-Pie-v0.02-U12+_Exodus-signed.zip: This zip installs the BeyondStock™ kernel which has patched touch for permanently installed TWRP older than 3.4.0, and patches the boot.img header so that decryption will work. It also supports the stock exFAT implementation.
UPDATE-BeyondStock™-Kernel-Pie-v0.02-U12+_Exodus_TWRP_3_4_0_CPTB.zip: This zip installs the BeyondStock™ kernel which has patched touch for permanently installed TWRP 3.4.0 (and higher), and patches the boot.img header so that decryption will work. It also supports the stock exFAT implementation.
[MANUAL] Fix CTS Profile Mismatch
Initial situation: most GSIs are rooted to a certain extent. This also applies to the AOSP GSI, which is the basis of our ViperExerience ROM.
Precondition: To correct the CTS mismatch, it is necessary that Magisk is installed.
If the precondition is fulfilled, proceed as follows:
Install the Magisk modules "Busybox" from Osmosis, and "MagiskHide Propst Config" from Didgeridoohan
After a device restart, open a Terminal App on your HTC U12+ and go through the following steps
Request root privileges by typing
Code:
su
Start the Props module by typing
Code:
props
Type
Code:
1
to set a new fingerprint for the device
Follow the instructions in order by selecting
Code:
f
and
Code:
7
(for HTC).
finally type
Code:
4
(for U12+ Pie).
How to permanently flash TWRP via the TWRP.img file inside TWRP
1. Make sure you have a working fastboot and adb environment! Your device´s bootloader must be unlocked!
2. Download the twrp.img file from here: https://github.com/CaptainThrowback/android_device_htc_ime/releases
3. Boot to TWRP. Navigate to Advanced -> Install Recovery Ramdisk -> Choose the twrp.img downloaded earlier. Wait for the flash to be completed successfully and do either
4. Download BeyondStock™-Kernel This zip installs the BeyondStock™ kernel which has patched touch for permanently installed TWRP, and patches the boot.img header so that decryption will work. It also supports the stock exFAT implementation.
5a. If you want to be rooted flash the magisk.zip
5b. If you don't want to be rooted navigate to Advanced -> Fix Recovery Bootloop to be able to boot into system
Thanks to @JEANRIVERA
reserved
reserved3
reserved4
reserved5
reserved6
Support
Hi users, I was a noob once too, believe it or not I had questions & stupid questions too but I was never afraid to ask, in my way to be part of this amazing team I have known all kind of Devs, with different levels of friendliness , but being honest in some way or another I have learned from all of them a little something, Now I want to give back to the community as much as I can, I am no Dev, but I do know a trick or two, if I don't know the answer to your questions, I will try my best to get an answer for you from the Team.
The instructions in the OP have been updated for better understanding and corrected some points, if anyone has tried unsuccessfully to flash this ROM please follow the updated instructions, if anyone have trouble or not booting device please feel free to ask, I will try to guide anyone as much as I can and as friendly as possible. I see there is 73 downloads on AFH of the ROM but only few users reported their experience here, maybe if you are afraid to ask, don't be, if you navigate through the thread you will see only friendly responses, and I will try my best to keep it that way, don't be afraid to tag me for support
And I'll take this one, just for the kicks.
I am running android 8 with viper 2.0 and i tried to update to this but ADB says that my file system is read-only. What is the recommended course of action?
Code:
adb: error: failed to copy 'update.zip' to '/update.zip': couldn't create file: Read-only file system
I read elsewhere that 'adb root' would be needed but i figured it would be better to ask here instead of following some random post about a somewhat similar situation.
First off: don't install this ROM on Android 8 firmware. It's an Android 10 GSI and all development an testing has been done on the latest EMEA firmware.
So the way to go from ViperU12+ would be to go back to full stock unsung a RUU and upgrade to Android Pie. This is to make sure you start from the correct base and environment. Then boot the device and copy the vbmeta zip onto /sdcard. Then reboot to bootloader and boot to TWRP, and follow the instructions from post #1 to the point.
Use the latest TWRP from @Captain_Throwback, found here: https://github.com/CaptainThrowback/android_device_htc_ime/releases/tag/3.3.1-2
Sent from my Pixel 4 XL using XDA Labs
it should be: 9 Reboot to Download from TWRP UI not
9 Reboot to bootloader from TWRP UI
on Production Units in Bootloader you get an error:
FAILED (remote: Erase is not allowed on PRODUCTION device)
This ROM is been running quite fantastic for me, I am so excited to help test and get this released for everybody to use! Can't believe we have Android 10 on this u12 plus Beast, it's so amazing! LOL thank you so much @mikalovtch, @JEANRIVERA, @Captain_Throwback, &
Sent from my HTC U12+ using Tapatalk
Oh man, you`ve done brilliant work:highfive::good:
it is almost perfect, butter smooth and fully functional except few bugs.
some issues are:
1. time and date automatically reset to 2020.03.07 4:47 after reboot, which can be quite annoying.
2. edgesense squeeze gesture feedback is weird. it`s not like the feedback of power btn but vibrating.
3. edgesense setting does not show in the settings.
some Pro tips:
1. flash system.img via twrp or via usb under DOWNLOAD mode. you can not flash it under BOOTLOADER mode.
2. you can access edgesense settings by this method:
goto Setting.Apps, show all system Apps and find out edgesense service app. In the detail screen(where you can clear the cache and force stop, idk the exact term), tap Advanced, Additional settings in the app.
3.kirisakura kernel tested, all good.
btw i use China version u12+, hope this will help you.
Thanks you bro!
issue has been fixed
JEANRIVERA said:
without the vbmeta.zip the ROM will not boot at all, the instructions fail to specify you must be on slot A to flash the vbmeta.zip and ROM, instructions will be updated soon, if you are on slot B another vbmeta zip should be used.
Click to expand...
Click to collapse
thank you! but i still boot without flashing vbmeta.
neoncloud4399 said:
thank you! but i still boot without flashing vbmeta.
Click to expand...
Click to collapse
is your device S-OFF? that would be the only possible reason it boots
JEANRIVERA said:
is your device S-OFF? that would be the only possible reason it boots
Click to expand...
Click to collapse
no, it still s-on.
i followed this procedure:
clear system, flash system, clear userdata under twrp
flash vbmeta.zip under twrp By sideload
reboot, failed to boot, show warning messages.
run fastboot oem rebootRUU to ruu flash mode and downgrade to 1.21
fastboot erase persist
boot to 1.21 China then upgrade to PIE.
boot to DOWNLOAD, erase system, userdata, flash system both system_a and system_b and it boots.
{
"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 11, 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. 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.
DISCLAIMER: LineageOS Legal
Requirement: Oneui 3.0 (DTL1).
Instructions:
Flash Lineage Recovery or grab the files from the download below and use the instruction from there to flash it
Format Data/Factory Reset
Flash the build (Use adb sideload, or push the file to sdcard with mtp)
Reboot
Notes:
VoLTE, IMS, and other samsung specific stock rom features wont be ported or fixed.
Download:
r5q 18.1
r5q recovery
Support Group: Telegram
Reporting Bugs
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 /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
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:
I do this kind of stuff on my free time. If you like my work, please consider buying me a drink (donation) by clicking the link below.
Paypal
Archive link: Github Releases
Kernel source: Github
hell of a ride to install this. nearly impossible to make recovery work (its because oneui 3 update i read somewhere?? problems with booting in newly installed recovery after using odin....damn)
my steps to get a proper recovery and this build running
- installed samsung android 11 / oneui3
- patched boot.img and rooted the rom
- installed twrp manager app
- put the twrp img on handy, installed it via twrp manager app
- tataa twrp installed
- had problems to decrypt handy (fixed after i wiped internal storage only)
- installed lineageos via twrp
rom works good so far. all i need works. so i use it as my daily driver. thanks for your work
immerblind said:
hell of a ride to install this. nearly impossible to make recovery work (its because oneui 3 update i read somewhere?? problems with booting in newly installed recovery after using odin....damn)
my steps to get a proper recovery and this build running
- installed samsung android 11 / oneui3
- patched boot.img and rooted the rom
- installed twrp manager app
- put the twrp img on handy, installed it via twrp manager app
- tataa twrp installed
- had problems to decrypt handy (fixed after i wiped internal storage only)
- installed lineageos via twrp
rom works good so far. all i need works. so i use it as my daily driver. thanks for your work
Click to expand...
Click to collapse
I think i had to mention this, booting recovery now requires you to have usb plugged in while you're punching the recovery combo to enter recovery.
Also, i've fixed the lineage recovery yesterday, sorry for the hassle.
New release are up! New release have a new repo right here https://github.com/mainey/r5q-archive/releases , hopefully this would be less confusing for the end users to find files needed. The old repo would now only releases new vendor updates from samsung.
New build: https://github.com/mainey/r5q-archive/releases/tag/ROM-20210121
note: i might or might not announce new builds in the future all the time, if you want to be notified when releases are published, make sure to click the watch button on the top right on the github repo page
What's handy?
How did you patch boot.img and root the ROM?
Is there a how-to for noobs? I guess all my knowledge on how to flash custom ROMs from 2 years ago are completely useless after all.
Thanks!
immerblind said:
hell of a ride to install this. nearly impossible to make recovery work (its because oneui 3 update i read somewhere?? problems with booting in newly installed recovery after using odin....damn)
my steps to get a proper recovery and this build running
- installed samsung android 11 / oneui3
- patched boot.img and rooted the rom
- installed twrp manager app
- put the twrp img on handy, installed it via twrp manager app
- tataa twrp installed
- had problems to decrypt handy (fixed after i wiped internal storage only)
- installed lineageos via twrp
rom works good so far. all i need works. so i use it as my daily driver. thanks for your work
Click to expand...
Click to collapse
Ok, I found the instructions for patching boot.img:
[HOW-TO-ROOT] [G770F/DS] Galaxy S10 Lite International Model
Models: SM-G770F or SM-G770F/DS Frequently used key combinations keys: FORCE REBOOT: Hold "Volume Down" and "Bixby/Power" button. DOWNLOAD MODE: With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via...
forum.xda-developers.com
darth.cabs said:
What's handy?
How did you patch boot.img and root the ROM?
Is there a how-to for noobs? I guess all my knowledge on how to flash custom ROMs from 2 years ago are completely useless after all.
Thanks!
Click to expand...
Click to collapse
Got new account nice to be here too..
Vaughnn said:
我想我不得不提一下，启动恢复现在需要您在插入恢复组合以进入恢复时插入USB。
另外，我昨天修复了血统恢复，很抱歉给您带来麻烦。
Click to expand...
Click to collapse
Vaughnn said:
LineageOS是免费的，社区构建的Android 11售后固件发行版，旨在提高设备的现有Android的性能和可靠性。
LineageOS基于Android开源项目，并得到了Android社区中许多人的额外贡献。无需安装任何Google应用程序即可使用它。下面链接的是一个来自另一个Android项目的程序包，这些程序可以还原Google部件。LineageOS仍然包含各种特定于硬件的代码，无论如何它们也正在缓慢地开源。
LineageOS的所有源代码都在LineageOS GitHub中提供。如果您想为LineageOS做出贡献，请访问Gerrit Code Review。您还可以查看更改日志以获取更改和功能的完整列表。
要求： Oneui 3.0（DTL1）。
指示：
Flash Lineage Recovery或从下面的下载文件中获取文件，然后使用此处的说明对其进行刷新
格式化数据/恢复出厂设置
刷新构建（使用adb侧载，或使用mtp将文件推送到sdcard）
重启
笔记：
请勿使GAPP闪烁，这包括最小的GAPP。我将发布带有gapps的版本，直到gapps程序包足够适合我的需求为止。
VoLTE，IMS和其他三星特定的rom功能将不会移植或修复。
在使用指纹之后或之前，屏幕有时会闪烁，这只是免责声明，如果有人使用此版本的癫痫病患者，我将不承担任何责任
错误：
接近度（可能无法在某些应用程序上运行）
5Ghz热点
下载：
r5q 18.1
r5q恢复
支持小组： 电报
报告错误
如果您正在运行自定义内核或已安装Xposed，请不要报告错误
问题发生后立即拿起logcat。（除非您知道自己在做什么，否则请至少包括日志的几页，而不仅仅是最后几行。）
如果是随机重新引导，请抓住/ proc / last_kmsg。（除非您在重新启动之前就可以获取它，否则不要费心获取一个logcat。重新启动之后的logcat是没有用的）
如果从根shell运行“ setenforce 0”后问题消失了，请抓住/data/misc/audit/audit.log
Code:
您的-
LineageOS版本：
LineageOS下载网址：
Gapps版本：
你是否 -
擦拭：
使用钛备份还原：
出现问题后重新启动：
你正在用吗 -
任务杀手：
非库存内核：
其他修改：
根据需要提供任何其他信息（观察/问题发生的频率/它工作的最新版本/等）：[/ CODE]
[B]我会在业余时间做这种事情。如果您喜欢我的工作，请考虑通过单击下面的链接为我买一杯饮料（捐赠）。[/B]
[URL='https://www.paypal.com/donate/?cmd=_donations&[email protected]']贝宝[/URL]
存档链接：[URL='https://github.com/mainey/release-r5q/releases']Github版本[/URL]
内核来源：[URL='https://github.com/mainey/android_kernel_samsung_r5q']Github[/URL]
[/QUOTE]
Hello, I would like to ask how my phone is currently Android 10 and One ui is 2.1. I want to change to LineageOS.
[/QUOTE]
Click to expand...
Click to collapse
immerblind said:
hell of a ride to install this. nearly impossible to make recovery work (its because oneui 3 update i read somewhere?? problems with booting in newly installed recovery after using odin....damn)
my steps to get a proper recovery and this build running
- installed samsung android 11 / oneui3
- patched boot.img and rooted the rom
- installed twrp manager app
- put the twrp img on handy, installed it via twrp manager app
- tataa twrp installed
- had problems to decrypt handy (fixed after i wiped internal storage only)
- installed lineageos via twrp
rom works good so far. all i need works. so i use it as my daily driver. thanks for your work
Click to expand...
Click to collapse
Hello, I would like to ask how my phone is currently Android 10 and One ui is 2.1. I want to change to LineageOS.
Rom is fine. There's simply not much to tell about. It runs runs runs. No problems at all. Twrp or lineageos recovery....whatever. all good
Would it be possible to have a version without Gapps?
Vaughnn said:
New release are up! New release have a new repo right here https://github.com/mainey/r5q-archive/releases , hopefully this would be less confusing for the end users to find files needed. The old repo would now only releases new vendor updates from samsung.
New build: https://github.com/mainey/r5q-archive/releases/tag/ROM-20210121
note: i might or might not announce new builds in the future all the time, if you want to be notified when releases are published, make sure to click the watch button on the top right on the github repo page
Click to expand...
Click to collapse
Is your lineageos 19 beta google-free?
Hi. Can anyone confirm if [BETA] Lineage 19 20220307 Beta 4 is stable enough as daily ROM?
Banking apps work? OIS+EIS during video recording?
Thank you.
Vaughnn said:
Requirement: Oneui 3.0 (DTL1).
Instructions:
Flash Lineage Recovery or grab the files from the download below and use the instruction from there to flash it
Format Data/Factory Reset
Flash the build (Use adb sideload, or push the file to sdcard with mtp)
Reboot
Click to expand...
Click to collapse
First of all thank you for your time and energy.
I'm having problem flashing latest beta 4.
I'm coming android 11 Oneui 3.1. My device is was rooted with unlocked bootloader.
1. I've flashed the lineage recovery via odin (Including vbmeta_disable) and upon reboot (it needed 2 boots to get into recovery) I chose factory reset of the device.
2. I've enabled developer options and saw my bootloader was unlocked.
3. I've booted into recovery
4. I've flashed the lienage os 19 beta 4 with google apps
I keep getting status error 2 and installation is aborted :O(
{
"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, 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.
Instructions:
Follow the instructions here
Downloads:
Builds: https://exynoobs.github.io/OTA/
GApps: MindTheGapps
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
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
josip-k
Linux4
Synt4x.93
Source Code: Exynoobs
Kernel source: https://github.com/Exynoobs/android_kernel_samsung_universal9810
Requirements:
Latest firmware
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata 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 + Volume Up 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 demand you format userdata, 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, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage 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
Boot lineage 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,
immediately hold Volume Up, Bixby and Power to boot recovery
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and magisk by repeating above step
with their zip/apk
This build does not use the stock vendor, instead it's built on top of new trees, which have been worked on for some time. The source is on our github, link in OP. You also get a few neat features like fingerprint gestures, and bixby button that actually works with both normal and long press.
I suggest using OpenCamera since stock one has some issues with flash.
These builds are signed with our release keys.
star2lte and crownlte support will come a bit later as i don't own the devices, but they will be supported eventually.
THESE BUILDS HAVE FORCE ENCRYPTION ENABLED, AND ONLY LINEAGE RECOVERY IS SUPPORTED. THESE THINGS WILL NOT CHANGE. IF YOU DON'T USE LINEAGE RECOVERY, AND SUFFER FROM DATA LOSS, DON'T COMPLAIN HERE.
how to restore to TWRP recovery, when flashed lineage recovery
Thank you for your hardwork!!! <3
Does banking apps work with this rom
lythongac said:
how to restore to TWRP recovery, when flashed lineage recovery
Click to expand...
Click to collapse
just Odin + TWRP (in tar) on rebooted Download mode
@DeHuMaNiZeD
Good work ! Work very well !
Is it possible to Add Dual Sim (crownlte) ?
My 1 week review as daily use :
1. smooth, stable (uptime 122h)
2. Wifi, bluetooth OK (no problem)
3. battery ok, nothing special, at the end of the day, with call and nomal usage (3-4h screen on with youtube (on browser) and video call with jitsi) >50%
4. (i don't use anything from google)
just perfect for me !
thank you @DeHuMaNiZeD very good job !
I am struggling to flash "Flash lineage recovery" .
I am trying to flash recovery.img before which it has to be added to .tar. But the tar file that i am creating using 7zip is not working. Can you please guide how to create tar file from recovery.img to be flashed through ODIN.
sherry9oct said:
I am struggling to flash "Flash lineage recovery" .
I am trying to flash recovery.img before which it has to be added to .tar. But the tar file that i am creating using 7zip is not working. Can you please guide how to create tar file from recovery.img to be flashed through ODIN.
Click to expand...
Click to collapse
if you have TWRP you can just flash lineage recovery via twrp, no PC needed.
Any way to activate the dual sim ?
root > edit a file ?
New build is up
DeHuMaNiZeD said:
New build is up
Click to expand...
Click to collapse
Thank you for the effort!
I had a boot loop when I updated to this build.
I tried to reflash through ADB twice, but still boot-looping. Had to go back to build 20220219.
Any suggestions?
I did not flash the recovery partition again - is it necessary?
EGYLOGGEF said:
Thank you for the effort!
I had a boot loop when I updated to this build.
I tried to reflash through ADB twice, but still boot-looping. Had to go back to build 20220219.
Any suggestions?
I did not flash the recovery partition again - is it necessary?
Click to expand...
Click to collapse
I did not have any issue when replacing stock fw with this latest build. Used Lineage recovery to clear data/cache and installed via adb. No boot-loops. Very smooth.
loci said:
I did not have any issue when replacing stock fw with this latest build. Used Lineage recovery to clear data/cache and installed via adb. No boot-loops. Very smooth.
Click to expand...
Click to collapse
Same here, can confirm. Only problem i got was flashing lineage recovery with odin ( unrooted stock fw ), so i flashed twrp and then from twrp flashed lineage recovery . This is one snappy motherflicker
E2001: Failed to update odm image :/
Can you provide a local_manifest to build yourself for crownlte (19, 19.1) please?
Thanks..
Is it possible to get an answer here?
...
How to use SPen with this rom ?
dr_root85 said:
How to use SPen with this rom ?
Click to expand...
Click to collapse
Samsung proprietary feature. Wont work on AOSP ROMs. There are patched apks available for Samsung health and Wearable but not for S-Pen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for Xiaomi MIX 4 [odin]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 13
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Downloads available here
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
Android OS version: 13.0
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
Build author/Device Maintainer: Inkypen
Kernel Source code: https://github.com/Inkypen79/kernel_xiaomi_odin
Official TWRP thread:
https://forum.xda-developers.com/t/recovery-11-official-teamwin-recovery-project.4374117
My unofficial TWRP build:
Updated to handle A12+ encryption.
https://sourceforge.net/projects/xiaomi-odin/files/odin-twrp-3.7.0_12-1.img/download
My unofficial OrangeFox recovery:
Updated to handle A12+ encryption.
This is in the form of a flashable zip, boot into TWRP first and then install/sideload
https://sourceforge.net/projects/xi...eFox-A12.1-R11.1-Unofficial-odin.zip/download
Installation:
Install TWRP and reboot to recovery
Either copy zip to internal storage and install OR use adb sideload
Format data (wiping is not sufficient, formatting requires you to type "yes")
Reboot
Important notes:
Formatting data (all user data is wiped, including internal storage) is a must if MIUI was previously installed and device was encrypted.
MIUI 13 firmware is included in ROM zip, no need to flash it seperately.
Other notes:
The default camera in these builds is ANX camera. Everything is working (including 108mp mode) apart from HDR/Slowmo video recording.
Awesome!
求快更新，谢谢
Quick update
The current version 0517 is great, no obvious bugs, the system is quite stable, minor issues with the ANX camera can wait for subsequent updates.
If any newcomer has finished brushing this rom, I would like to give some advice on how to improve the battery life.
After brushing.
1. modify the wifi detection parameters, you can solve the problem that when there is no WIFI outside the wall, the system will automatically switch to the phone network from the WIFI inside the wall.
adb shell settings put global captive_portal_mode 0
adb shell settings put global captive_portal_https_url https://www.google.cn/generate_204
2. it is recommended to install fridge (icebox), black threshold type of software, suppress the domestic software's self-start and background behavior, standby time will be significantly improved. I installed icebox, must be installed after the brush, through the device owner can be installed successfully, do not need to root. if you have been using a period of time, even if you delete a variety of accounts, you can no longer through the device owner way, at this time, only recovery restore the original factory, can be installed successfully.
3. display settings, select 60HZ refresh rate, and then install S20 Refresh Rate Control, mix4 can be used, set to 90HZ refresh rate, as opposed to 120HZ, in the experience of smooth picture at the same time, can save a little is a little.
btw, mix4 is really power hungry. 888 is the Fire Dragon.
Thank you! This Rom Runs very smooth, but how i get he Pedometer works ?
Unfortunately I am unable to install this rom. I'm installing twrp and going to recovery. The computer does not see the phone to be able to throw the rom.
At the moment, I have a stable miui 13
kasia19 said:
Unfortunately I am unable to install this rom. I'm installing twrp and going to recovery. The computer does not see the phone to be able to throw the rom.
At the moment, I have a stable miui 13
Click to expand...
Click to collapse
Try it this way:
1 First enter FASTBOOT mode
2 Run: fastboot boot twrp-3.6.1-odin.img
3 When the TRWP page appears, Advanced, ADB Sideload
4 Run: adb devices, if it goes well, you can see your mix4 now
6 Run: adb sideload PixelExperience....zip
Enjoy the ROM~
Unfortunately, the message is still present in the photo
In my Case, this was the only possible Methode..
1. Backup all Ur Data
2. Reflash MIUI V12 Fastboot
3. Set Up MIUI without Password Finish.
4.Settings ->developer Mode ->secure Boot disable.
5. Reboot Fastboot and flash Twrp.img via Fastboot Boot Twrpingname.img
6. Mtp activate and Transfer the Rom and the orange fox Recovery
7. Flash Orange Recovery
8. Reboot in Orange Recovery( it does auto load)
9. Flash the Rom
10. Delete Data With "yes"
11. Reboot
12. Finish
In my Case the only possible way
kasia19 said:
View attachment 5635055
Unfortunately, the message is still present in the photo
Click to expand...
Click to collapse
Just Developer Mode and Select ADB via USB Enable
Neosux said:
In my Case, this was the only possible Methode..
1. Backup all Ur Data
2. Reflash MIUI V12 Fastboot
3. Set Up MIUI without Password Finish.
4.Settings ->developer Mode ->secure Boot disable.
5. Reboot Fastboot and flash Twrp.img via Fastboot Boot Twrpingname.img
6. Mtp activate and Transfer the Rom and the orange fox Recovery
7. Flash Orange Recovery
8. Reboot in Orange Recovery( it does auto load)
9. Flash the Rom
10. Delete Data With "yes"
11. Reboot
12. Finish
In my Case the only possible way
Click to expand...
Click to collapse
Thank you for your help. I see the rom does not support 5G network
Edit seems to Work so far..
New build with June security patch is up.
Anyone having problems installing should check the extended update instructions in my LineageOS thread
[ROM][13.0][UNOFFICIAL] LineageOS 20.0 for Xiaomi MIX 4
LineageOS is a free, community built, aftermarket firmware distribution of Android 12 (S), which is designed to increase performance and reliability over stock Android for your device. #include /* * Your warranty is now void...
forum.xda-developers.com
kasia19 said:
Thank you for your help. I see the rom does not support 5G network
Click to expand...
Click to collapse
It most definitely supports 5G, I have 5G service on my device right now lol. Check your SIM card, I had a bug report about 5G working on MIUI but not on my ROMs, turns out that user didn't have a 5G compatible SIM card and MIUI was fake reporting 5G support.
What is updated with this release？
Which is the best way to Update this Rom without delete Storage?
Just sideload ZIP and flash?
Thanks
I've built TWRP 3.6.2 A12 branch and decryption is working. Untested other than making sure it boots and decrypts internal storage correctly. Use fastboot boot to run it and Advanced/Flash current TWRP to actually install it. If you find any bugs feel free to report them but bear in mind the whole TWRP A12 branch is currently WIP.
https://sourceforge.net/projects/xiaomi-odin/files/odin-twrp-3.6.2_12-0.img/download
I've been using this ROM for about a week. This is the ROM that should had been included as stock for this phone!!! Great job!!
New builds are up. Download
Changelog:
Kernel version 5.4.203
July security patch
Fixed Wifi Display
Fixed physical screen size properties (this caused tiiny images in apps like reddit)
Fixed Netflix not detecting widevine L1 correctly
Added high touch poll rate for you gamers out there
Enabled multi threaded render engine (improves UI smoothness)
Enabled some power saving tweaks for Wifi/Bluetooth
Some other minor tweaks and improvements
Also got an updated TWRP A12 build for you here: Download
Touchscreen now works properly on MIUI based ROMs
TWRP settings are now saved properly and are persistent across reboots
TWRP settings are now saved in /data/recovery rather than /sdcard/.twrps (some apps look for the .twrps folder and then declare your device is rooted even if it isn't)