Database Develop

[ROM][OFFICIAL][enchilada][10.0]crDroid Android[v6.27]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
crDroid is built on top of LineageOS, and is designed to increase performance and reliability over stock Android for your device, while also attempting to bring many of the best features in existence today.
Features
A quick glossary and primer on slots for A/B devices (like ours):
Spoiler: Show/Hide
- "Clean flash": Removing device protection & clearing user settings before installing a bootable system install zip (usually by either wiping or formatting data, see below).
- "Dirty flash": Flashing a ROM zip (usually upgrading to new version, sometimes just re-flashing the existing one) without wiping data or anything first.
- "Wipe data": Synonymous with "factory reset", accomplished from TWRP recovery by selecting "Wipe", then performing the "Slide to factory reset". Clears user data without erasing any partitions, removing encryption, or deleting contents of internal storage.
- "Format data": Formats the data partition itself, resets all file-based encryption keys, loses all contents of internal storage, and in fact deletes all "user 0" directories (this has some implications for internal storage before & after first boot).
- "User 0" directories are a series of directories that store userdata for the primary user, "Owner", and get created in various places throughout the filesystem on first system boot if they don't exist already. Anything you copy to "internal storage" while booted in recovery after "formatting data" will actually be copied to /data/media/ instead of /data/media/0/, and will become invisible to regular file browsing after first boot once the system has created /data/media/0, since the system will prefer to use that path for internal storage from then on (so you'll need a root file browser to delete things from /data/media, or just ADB sideload things instead of copying after formatting but before booting).
- "OTA package": Originally an abbreviation for "over the air", referring to how a software update could be delivered (as opposed to having to take your phone to a carrier's store for a firmware update via serial/USB connection). The common usage in Android circles is any installation zip file that actually includes a bootable system.
- Some partitions are duplicated (system, vendor, boot, and probably a couple others, but not data) and have a "slot A" & "slot B" copy.
- "Slot A" and "slot B" are absolute designations, but most installer zip scripts use the relative designations: "active" and "inactive". Whichever slot you're booted from currently is "active", and the other one is "inactive".
- Installing a zip file that's flagged as being an OTA package will 1) install the contents to the "inactive" slot, and then 2) flag the bootloader to switch which slot is considered "active" (and booted from) and "inactive" upon next reboot.
- The OxygenOS full OTA zip files and all custom ROM installer zip files are considered "OTA packages" and will trigger a slot switch on next boot after installation.
- You can install multiple OTA zip packages one after the other without rebooting in TWRP; they will all get installed into the correct partitions in the "inactive" slot, one on top of the other, and then it will swap active & inactive upon reboot.
Prerequisites:
- Make sure your bootloader is unlocked (and don't plan on relocking it ffs).
- Make sure you have a reasonably-current, working installation of android platform tools (adb & fastboot command line binaries & necessary drivers) on your computer, with a known-good USB cable (see links in post #2).
- Make sure you've downloaded the most recent full Android 10 OxygenOS OTA installer zip (10.3.12), crDroid zip, matching crDroid boot.img, official TWRP 3.5.2_9-0 installer zip and bootable img, and whatever Magisk/GApps/microG installation packages you want to use to your computer (see links in post #2).
- Make sure you've backed up whatever data you want to keep to somewhere that's not on your phone; for a new install, we're going to format the data partition and you're going to lose everything from internal storage.
Let's get started!
Updating firmware (if already on crDroid):
- Reboot to bootloader (with no USB cable connected).
- Open a terminal on your computer, and run `fastboot flash boot path/to/boot.img`, substituting in the path & filename for the current crDroid boot.img that you downloaded as part of the prerequisites.
- Reboot to bootloader again (actually loads new bootloader that you just flashed).
- Use Vol +/- buttons to select "Recovery mode" and press Pwr button to boot into the built-in TWRP recovery. The device's internal storage should now be available for read/write on the computer via MTP.
- Copy the official OxygenOS 10.3.12 full OTA zip & latest crDroid zip into the device's internal storage, then choose "Install", select the current crDroid zip, choose "Add more zips", and crDroid installer zip, then swipe to confirm flash. No TWRP zip required, since it's built in to the boot.img that gets installed.
- Reboot recovery, then choose "Install", and select the OOS zip, then select "Add more zips" and choose the crDroid zip, and swipe to confirm flash again.
- Reboot recovery, and re-flash magisk/gapps if needed.
- Wipe dalvik.
- Reboot system.
First time installing crDroid to your OP6, coming from stock OxygenOS or another ROM (will also update firmware while we're at it):
- Reboot to bootloader, then `fastboot boot path/to/twrp.img` to start up into TWRP recovery.
- Mount System partition read-write, use file manager to delete the /system/addons.d/ directory if it exists, unmount System.
- Choose Wipe > Format data, type "yes" and hit enter to nuke everything in the data partition and clear encryption.
- Choose Advanced > ADB sideload (don't worry about selecting cache/dalvik wipe options yet) and then on the computer, do `adb sideload path/to/OxygenOSOTA.zip` to flash the OxygenOS 10.3.12 full OTA installation zip & make sure you're on the latest Android 10 firmware.
- Go get a drink, this'll be a bit.
- When that's done, hit "back" in TWRP and start ADB sideload again, and this time send the crDroid installation zip (includes TWRP built-in, so don't need separate zip for that at this point).
- Reboot to recovery (this will switch the active slot to use the system partition you just installed those zip files into).
- Wipe data (Wipe > "Slide to factory reset" in TWRP).
- That was so much fun, let's do it again! ADB sideload OxygenOS full OTA zip.
- ADB sideload crDroid zip.
- Reboot to recovery (switches slots again, now we have latest OxygenOS firmware plus crDroid populated in both sets of partitions and won't have to do that again).
- Flash Magisk (if desired).
- Flash GApps or microG package (if desired).
- Wipe dalvik.
- If you copied anything to internal storage instead of flashing it via ADB sideload, delete it now before first boot.
- Reboot system.
- Go through setup wizard.
- Reboot system (for reasons I don't comprehend, it never shows "OnePlus Settings" in the Settings app top level menu on a fresh install until after rebooting once).
- It's gonna harass you to finish setup, go ahead and customize everything to your heart's content.
Updating crDroid from TWRP (preferred):
You don't need to remove device protection; it works fine with PIN. Be sure you have a PIN set, or have looked up whatever that arcane chart of pattern > numeric incantations in case of pattern unlock. It's awful.
- Boot into TWRP recovery.
- Choose install, then select OOS firmware OTA (if needed), then choose select additional zips, then select crDroid.zip, slide to confirm flash.
- Reboot recovery.
- Choose install, then select Magisk zip (if using), select additional zips, choose GApps/microG (if using), slide to confirm flash.
- Please keep off of the grass, shine your shoes, wipe your... dalvik.
- Reboot system.
Updating crDroid from Updater app:
Warning: I don't remember if crDroid 6 even *has* the built-in Updater app function or not, or how well it handles addon.d survival scripts. Use with caution.
- Install update in built-in Updater app (Settings > System > Updater), do NOT reboot yet.
- Go to Magisk app home, click "Install" next to Magisk, and choose the "Install to Inactive Slot (After OTA)" method.
- For GApps/microG: If you use GApps/microG that needs to be re-flashed to /system (as opposed to magisk module GApps/microG), reboot *recovery* at this point, mount the system partition in TWRP, and dig around with the File Manager in system/priv-app/ & system/product/priv-app/ to make sure that everything you expect was copied over to the now-currently-active slot, and if need be re-flash your installer zip, or else your world will be pain when you boot normally. Yes, I expect you to know what your preferred package installs & to keep the zip handy.
- NOW you can reboot to system.
Reporting bugs:
I'm a parent of three young kids whose industry disappeared in the pandemic and is now full-time house husband & parent-in-charge while my wife is teaching full-time, I'm trying to save my small live-event-turned-streaming-studio company in my spare time. I'm doing in-home caregiving for a family member overnight one day a week. This is the back-up spare-spare-time hobby. I'm not a software developer nor do I know any programming languages, I just wanted a ROM with signature spoofing support and more customization than the unofficial microg-compatible LineageOS builds. So if there are bugs or feature requests, I go over to the crDroid dev chat and ask if someone has time to hold my hand & help. Don't make me get yelled for annoying them, mmkay? That said...
- Logs/screenshots/recordings or it didn't happen. Syslog (free, open source, available on Play store and F-droid) is your friend.
- I try to keep an organized notebook of roadmap, feature reqeusts, bug reports, etc. I won't always be able to fix it, but I'll at least look and do my best to ask the actual devs.
- I don't sign into XDA much, so if I haven't said anything, check out the Telegram group. Lots of helpful folks there.
- Please keep your questions in this thread instead of PMing me with them directly, so that the entire class can benefit from the discussion and you can find out if it's just you or if this is a widespread issue.
It's your device to use the way you want of course, and I use Magisk & microG and like to tweak things myself. But don't expect much support if you:
- didn't do a clean flash.
- aren't using the built-in kernel.
- are using extensive modifications (besides Magisk) like Xposed/Riru, Dolby Atmos, Viper4A, etc.
- immediately start using "finalize.zip" or flashing migrate restore zips instead of following the actual instructions.
- are running decrypted.
Donate - Support development!
crDroid Website - Download here!
Telegram Oneplus6/6t group - Share your best cat pictures!
Source Code:
- Device tree: https://github.com/crdroidandroid/android_device_oneplus_enchilada/tree/10.0
- OP6/6T Common device tree: https://github.com/crdroidandroid/android_device_oneplus_sdm845-common/tree/10.0
- OnePlus Common device tree: https://github.com/Terminator-J/crdroid_device_oneplus_common/tree/10.0-test
- Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sdm845/tree/10.0

Notes:
- Yes it supports package signature spoofing permission for microG compatibility out of the box (but will work without ANY GApps/microG implementation installed as well).
- Aux camera doesn't work correctly due to framework issues beyond my control/comprehension. So, still no portrait mode in OnePlusCamera in cr6. But 60fps video recording in OOSCam works great; huzzah!
- Doesn't pass safetynet out of the box, despite many tests with different fingerprints/props. Just use Magisk & enable the Zygisk DenyList & kdrag0n's "safetynet-fix" module and be happy. If your bank's app doesn't work, switch to a local credit union and stop feeding the bougie bankers. Smash capitalism!
- Maintainer does not use GApps, so cannot answer questions about which packages work best from firsthand experience. In general, go with the smallest package you can and then install other Google apps from the Play Store. Please note that if you replace the stock dialer with Google Dialer, you may lose access to the Phone Info menu (*#*#4636#*#*) until you install another dialer. For recommendations, see https://wiki.lineageos.org/gapps.
- Requires OOS 10.3.12 OOS firmware.
- Includes built-in TWRP, pulled from official 3.5.2_9-0 ramdisk, works well.
- Tested against latest Magisk canary (with zygisk instead of magiskhide), works well.
- No there won't be official builds with inline GApps; please don't ask.
crDroid 6.27 - February 2022 ASB release notes/known issues:
Changelog since v6.23 release:
- Merged Android Security Bulletins through February 2022 from upstream.
- Whatever changed upstream in the ROM proper (not likely much; they want to freeze it besides security updates).
- Reimplemented DeviceSettings based on crDroid 7 version (no more greyed-out things that don't actually work in Android 10).
- Backported updated display panel handling in device tree and kernel to match crDroid 7 (panel color modes are in LiveDisplay now). FOD on fajita is still kinda crap with OOS 10 firmware, but oh well.
- Little more tidying/tightening in device tree & kernel for moving to maintenance-only releases.
- Imported current wireguard VPN kernel-mode driver.
Known issues:
- Some screen-off gestures may not work, due to limitations beyond my control; don't use those gestures. Sorry.
- You tell me! With logs!
Other stuff:
- At this point, any little feature bugs will be considered "can't fix/won't fix"; I can't keep working on this one, I'm going to try to only do security-update-only releases of crDroid v6.
- Where do bad rainbows go? Prism. It's a light sentence.
Helpful links:
Download ROM
TWRP (use old official v3.5.2_9-0)
(TWRP is built-in to the crDroid 6 zip, but you might need the img or standalone installer zip in order to get to that point)
Magisk (use latest)
OxygenOS 10.3.12 Full OTA
MSMTool (oh now you're in trouble - use latest unless you have a good reason to intentionally downgrade)

Thanks dev. This is a great ROM
When you say latest fw, you are talking about OOS Pie or H2OS Q?

firebird11 said:
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
To be defined
First time installing crDroid to your Op6, or coming from another ROM:
- Be on the latest firmware
- Make sure you're running latest TWRP
- Copy GApps and crDroid zip to your internal storage
- Disable your screenlocks
- Boot into Recovery
- Wipe cache,data
- Flash crDroid zip
- Flash TWRP zip
- Reboot to recovery
- Flash GApps zip
- Flash Magisk zip
- Reboot system
Don't expect any support if you:
- are not running stock crDroid-kernel
- have installed any mods such as Xposed!
- have modified system files
DONATE
crDroid Website
Telegram Oneplus6/6t group
XDA:DevDB Information
crdroidandroid, ROM for the OnePlus 6
Contributors
firebird11, neobuddy89, gwolfu
Source Code:https://github.com/crdroidandroid
Source Code Kernel:https://github.com/crdroidandroid/android_kernel_oneplus_sdm845
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: LOS
Version Information
Status: Testing
Created 2019-10-16
Last Updated 2019-10-16
Click to expand...
Click to collapse
Any bugs or something not working?
Will try this weekend.

Thank you dev

Hello, I flashed rom yesterday.
I've got 1 issue. Fingerprint unlock doesn't work. I mean fingerprint sensor works because I can set up a fingerprint. But when phone is locked (screen on or off) I can't unlock it.
Maybe this is Gapps related? (I used Nano beta from october). Not rooted
Rom is fast and responsive. No other bug/ lag or freezes so far.
If anyone can help me with fingerprint unlock it would be much appreciated.
Have a nice day.

veronesi.n said:
Hello, I flashed rom yesterday.
I've got 1 issue. Fingerprint unlock doesn't work. I mean fingerprint sensor works because I can set up a fingerprint. But when phone is locked (screen on or off) I can't unlock it.
Maybe this is Gapps related? (I used Nano beta from october). Not rooted
Rom is fast and responsive. No other bug/ lag or freezes so far.
If anyone can help me with fingerprint unlock it would be much appreciated.
Have a nice day.
Click to expand...
Click to collapse
Same here, I think new magisk 20 breaks it , because with 19.4 working fine

savinjo22 said:
Same here, I think new magisk 20 breaks it , because with 19.4 working fine
Click to expand...
Click to collapse
Sorry I said not rooted ?... I wanted to say that magisk wasn't installed.

i tryed this rom on my htc m8 and i love it and i will try it again on oneplus 6

Is this also implemented already in android 10? TIA

tiga016 said:
View attachment 4847745
Is this also implemented already in android 10? TIA
Click to expand...
Click to collapse
Yes there's some customization settings.

dev i tried to flash this rom but it says failed because the file for oneplus 5 not oneplus 6 could you check the download link?

backtrack292 said:
dev i tried to flash this rom but it says failed because the file for oneplus 5 not oneplus 6 could you check the download link?
Click to expand...
Click to collapse
I assume you used the 'Green Box' link in Sourceforge? That always trips people up. That link is the latest ROM across all crDroid devices. (Currently the OP5 'Cheeseburger') Or next time actually read the file name before flashing.
Ignore that Green Box. Just pretend it doesn't exist. Use the links underneath to get the Enchilada downloads.

a new v6 build is up !
october security and statusbar padding are new

firebird11 said:
a new v6 build is up !
october security and statusbar padding are new
Click to expand...
Click to collapse
does it supports signature spoofing?

just tried moving from havoc 2.9 (pie) to crd6 (q), but unfortunately at this point no twrp can handle Q OOS flashing (to bring firmware to up to Q levels), latest available twrp is Mauronofrio's 3.3.1.4 so if anyone succeeds in flashing stock followed by CrD6 on a later/another twrp, would love to hear the success story...
for now, someone suggested only a local upgrade route within ota, but you end up without a functioning twrp environment which is probably too much hassle for most, so we will wait on the sidelines for a bit longer.
hope this helps!

What the latest fw is required pie or Q beta 1?
---------- Post added at 08:03 PM ---------- Previous post was at 08:02 PM ----------
ewong3 said:
just tried moving from havoc 2.9 (pie) to crd6 (q), but unfortunately at this point no twrp can handle Q OOS flashing (to bring firmware to up to Q levels), latest available twrp is Mauronofrio's 3.3.1.4 so if anyone succeeds in flashing stock followed by CrD6 on a later/another twrp, would love to hear the success story...
for now, someone suggested only a local upgrade route within ota, but you end up without a functioning twrp environment which is probably too much hassle for most, so we will wait on the sidelines for a bit longer.
hope this helps!
Click to expand...
Click to collapse
There is a way to have a twrp on open beta 1.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-update-to-android-10-beta-1-twrp-t3987041
---------- Post added at 08:04 PM ---------- Previous post was at 08:03 PM ----------
ewong3 said:
just tried moving from havoc 2.9 (pie) to crd6 (q), but unfortunately at this point no twrp can handle Q OOS flashing (to bring firmware to up to Q levels), latest available twrp is Mauronofrio's 3.3.1.4 so if anyone succeeds in flashing stock followed by CrD6 on a later/another twrp, would love to hear the success story...
for now, someone suggested only a local upgrade route within ota, but you end up without a functioning twrp environment which is probably too much hassle for most, so we will wait on the sidelines for a bit longer.
hope this helps!
Click to expand...
Click to collapse
There is a way to have a twrp on open beta 1.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-update-to-android-10-beta-1-twrp-t3987041

meistr91 said:
What the latest fw is required pie or Q beta 1?
---------- Post added at 08:03 PM ---------- Previous post was at 08:02 PM ----------
There is a way to have a twrp on open beta 1.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-update-to-android-10-beta-1-twrp-t3987041
---------- Post added at 08:04 PM ---------- Previous post was at 08:03 PM ----------
There is a way to have a twrp on open beta 1.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-update-to-android-10-beta-1-twrp-t3987041
Click to expand...
Click to collapse
thank you for the suggestion... gone well beyond the link's status by the time i read this (on oos from local update), so may just wait it out for a working twrp solution - been too long since last used OOS anyway!

new v6 builds are up !

firebird11 said:
new v6 builds are up !
Click to expand...
Click to collapse
Can be flashe with oos 10 base ?

[RECOVERY][RMX2061][Unofficial]TeamWin Recovery Project [3.5.X]

TeamWin Recovery Project
{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.​
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
TWRP is FREE SOFTWARE​Two versions: for RUI1 (Android 10) and for RUI2 (Android 11)
Features:
• Fastbootd is working;
• Decryption is working
• Using custom themes and fonts (special thanks to [email protected])
• Added custom patches in the Advanced settings (special thanks to [email protected]):
- SafetyNet fix patch
- Google Pay fix patch
- Patch for mount System and Vendor as r/w
• AVB2.0 (vbmeta) disabling special (thanks to [email protected] for his patch)
• Fix stock .ozip installation
• Patch to conversion of dynamic partitions to r/w (special thanks to @lebigmac for his script. Original thead)
• Patch to fix Magisk on RUI2
Download:
From Google Drive https://drive.google.com/drive/folders/1xerR8NmCNEoR1afh4dfbyrLz0ZOuWZPp?usp=sharing
Spoiler: Screenshots
Spoiler: Guides
Spoiler: Convert any ROM to r/w
How to convert ROM to R/W
The process below describes how to transfer the entire firmware to R/W (the ability to change/delete/add files in the system partitions: system, vendor and others ..).
All actions are carried out in TWRP itself i.e. on "live".
Your data is not affected.
Required for a successful conversion:
* free space on the internal memory of at least 25GB.
* charged battery (preferably at least 40%)
The process itself is not complicated:
1. Make
backup a Super partition (optional)
2. Go to the "Advanced" section and select "Convert ROM to RW".
3. In the next window, confirm with a swipe.
4. That's it, we are waiting ... about 5 minutes ...
5. After all the actions, the device will reboot itself into the system ...
6. Go to the explorer with root rights and delete the /data/local/tmp/makesysrw_[version] (/data/media/makesysrw_[version] for Android 11) folder, or do it in the TWRP explorer
To access the system partitions, respectively, you need root rights and a file manager with the ability to mount partitions in r/w.
The test was conducted on RealmeUI 1 A.45 and RealmeUI 2 C.15. But there is no difference, it is possible to convert any Android 10-11 ROM to r/w.
Changelog - current version (Android 11):
• Fixed decryption /data on realmeUI 2.0 (all versions)
• Enabled some patches in the Advanced section
• Updated Magisk and some patches
• Edits in the TWRP interface by @brigudav
• Removed the code that could break the formatting /data
• Updated sources
• And other changes that I forgot...
INSTALLATION
via TWRP-based recovery:
Download the TWRP IMG file to your device
Reboot to your custom TWRP-based recovery
Install the TWRP img file as image in recovery partition
Reboot into recovery after installation
Enjoy!
via fastboot:
Download the TWRP IMG file to your PC
Reboot your device to fastboot mode
Install the TWRP image with command:
Code:
fastboot flash recovery [image name].img
Reboot to recovery with the command:
Code:
fastboot reboot recovery
Enjoy
Notes:
• Installation of OTA packages not working
• ADB doesn't work in fastbootd mode only
CREDITS
• TeamWin - for TWRP
• brigudav - for his TWRP customization
• @lebigmac - for his makeSystemRW script
Version Information
Status: Stable
Current version: 3.5.2_10-1 (Android 10) / 3.5.2_1011-3 (Android 11)
Created 2021-03-18
Last Updated - 2021-09-03

CHANGELOGS
Spoiler: Android 11
Spoiler: 2021-09-03 (3.5.2_1011-3)
• Fixed decryption /data on realmeUI 2.0 (all versions)
• Enabled some patches in the Advanced section
• Updated Magisk and some patches
• Edits in the TWRP interface by @brigudav
• Removed the code that could break the formatting /data
• Updated sources
• And other changes that I forgot...
Spoiler: 2021-05-03 (3.5.2_1011-2)
• Fixed the installation of some ROMs
• Fixed fastboot (it was broken in the last build)
Spoiler: 2021-05-01 (3.5.2_1011-1)
• Disabled non-working patches in the Advanced section
• Enabled the install/remove Magisk feature in the Advanced section
• Added a boot repackaging patch with an oplus.fstab fix for Magisk (now after applying this patch, Magisk booted correctly on RUI 2)
• A small fix under the hood
Spoiler: 2021-04-29 (3.5.2_1011-0)
• Initial build
Spoiler: Android 10
Spoiler: 2021-04-23 (3.5.2_10-1)
• Universal patch disabling vbmeta by [email protected] (thanks to him for the patch)
• Now the internal storage after formatting /data is available without rebooting
• Minor changes in device tree (some libs are now taken from sources, small changes in the fstab, unnecessary system.props and flags are removed, edits in translation)
• Updated and fixed the script for converting firmware to R/W (now temporary files are deleted automatically when the conversion is successful)
• Added logcat copying
• Updated magisk to Canary 22104 (21) in which the SafetyNet check works correctly.
• Languages: Added Indonesian language [android_bootable_recovery]
• Change the missing logical partitions from LOGERR to LOGINFO [android_bootable_recovery]
Spoiler: 2021-04-05 (3.5.2_10-0)
• The list of Firmware-Update partitions for backup is finally changed (It is recommended to delete old "Firmware" backups and make new ones #2)
• Fix a regression error for digest checking [android_bootable_recovery]
Spoiler: 2021-03-30 (3.5.1_10-1)
• Added conversion of dynamic partitions to r/w (see Guides). Special thanks to @lebigmac for his script. Original script thead
• In the Mounting settings you can now mount System and Vendor r/o and r/w (if the partitions are in r/w). Taken fromTWRP by brigudav for Poco X3
• Returned the reboot menu from TWRP 3.3.x. Taken from TWRP by brigudav for Poco X3
• Changed the list of partitions for Modem backup. It is recommended to delete old backups and make new ones
• Changes in languages
• Other changes under the hood
Spoiler: 2021-03-18 (3.5.1_10-0)
• Initial version

Reserved

Can i use this recovery for Flash Android 11 custom roms?

Ayushmak said:
Can i use this recovery for Flash Android 11 custom roms?
Click to expand...
Click to collapse
Yes, if you already have installed the RUI1 or ROM's based on RUI1.
You cannot boot the TWRP if you on RUI2 or ROM based on RUI2

Somebody knows on which RUI is based RR from this thread? There is only "Based on: AOSP". So can I install this twrp or not?
[ROM][10.0] Resurrection Remix v8.6.3 [RMX206X, UNOFFICIAL]
Please Give Update A11 based RROS...
forum.xda-developers.com

Yes you can install it... 'cause i would try.. on RR rom

Zgadnijcie said:
Somebody knows on which RUI is based RR from this thread? There is only "Based on: AOSP". So can I install this twrp or not?
[ROM][10.0] Resurrection Remix v8.6.3 [RMX206X, UNOFFICIAL]
Please Give Update A11 based RROS...
forum.xda-developers.com
Click to expand...
Click to collapse
All Android 10 Custom ROMs based on RUI1. Yes, you can install TWRP

Good job Ctarchik!
If anyone is looking for more information about my make system RW script here is the official project thread

lebigmac said:
Good job Ctarchik!
If anyone is looking for more information about my make system RW script here is the
Click to expand...
Click to collapse
Hi, I took this patch from TWRP by brigudav. I didn't find any mention of the creators anywhere other than brigudav, just "Make System to RW for Poco X3". I am always for the preservation of copyright and always indicate the developers of the program. I apologize to you for not finding your original official project thread. I would like to use your script for my recovery, of course, with the condition of saving the author and specifying a link to the original post...

Ctarchik please feel free to use latest version of my script in your project. The more people have system r/w access the better for the open source community.
@brigudav rather than hacking my update-binary and replacing my program's title (!!!) with your own meaningless words and torturing my script's comments section by modifying and removing the original script name, original author name, original version, link to original project homepage, disclaimer, credits, manual and automatic installation instructions, usage examples, (and much more...) I would suggest to try to improve the underlying algorithm of the script itself. And NO that does NOT mean simply renaming my variables and my functions and changing their order as well as injecting your bogus useless function that does absolutely nothing (...)
Please don't be such a lazy ruthless hacker without any morals or respect! Thank you! You have been caught red handed as a cyber thief and now the only right thing to do is to admit your guilt, beg for pardon and STOP IT! Please stop stealing my work and releasing as your own okay? That's just very very wrong on so many levels!
I clearly stated in my disclaimer that by using my script you agree to not abuse my work for criminal illegal purposes. And what you're doing is a perfect example of copyright infringement as well as intellectual property theft which is illegal even in Russia. Don't forget that!

Can you mod this twrp so I can use external sdcard to backup?
Thank you!
Super Partition backup fails when using FAT32 stick (exFAT works) · Issue #143 · TeamWin/android_bootable_recovery
I am running an official build of TWRP, downloaded from https://twrp.me/Devices/ I am running the latest version of TWRP I have read the FAQ (https://twrp.me/FAQ/) I have searched for my issue and ...
github.com

Ctarchik said:
Yes, if you already have installed the RUI1 or ROM's based on RUI1.
You cannot boot the TWRP if you on RUI2 or ROM based on RUI2
Click to expand...
Click to collapse
I had to google to know what RUI1 and RUI2 meant - RUI1 is Realme UI 1.0 which is based on Android 10 - RUI2 is Realme UI 2.0 based on Android 11

beaker2 said:
I had to google to know what RUI1 and RUI2 meant - RUI1 is Realme UI 1.0 which is based on Android 10 - RUI2 is Realme UI 2.0 based on Android 11
Click to expand...
Click to collapse
Yes, it is. I just shortened RealmeUI to RUI

The problem I have been having is when I previously installed TWRP on my phone using ADB to install- patched_vbmeta-2 and then TWRP. I could reboot from ADB into recovery to TWRP, but then when I tried to reboot into system I was in a boot loop and phone would only go back to the stock recovery . Then I had to re flash the stock rom to get out of the boot loop and be able to boot into system again.
So can I do the same install from ADB as before but when I reboot , from ADB, into TWRP then I can install this TWRP then I can have the ability to boot into the stock ROM system . Then I could go to recovery and TWRP will still be there so that I could install a custom ROM ?
Thanks in advance, I'm a noob with this phone and its partitioning

Well, I tried the installation described above, installed TWRP from ADB then when booted and rebooted into TWRP and flashed this version of TWRP, seemed fine no errors BUT... the phone just returned to the stock recovery .
Then I tried exactly as described in this thread no error message and all seemed to go smoothly BUT... The phones internal memory was unreachable from any file manager or computer and the stock recovery returned not TWRP. Had to re-flash the phone several times, 1. stock recovery 2.from update 3.from flash tool, to finally get the internal phone memory visible again.
My phones build number is RMX2061_11_A49. Has anyone successfully installed TWRP on this build ?
How?

1. Prevent replacing TWRP:
Flash this file in Advanced Menu in the first time you go in TWRP.
2. Decrypt userdata: do them in order
- Flash this file:
Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip | by Droidwin for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
- Wipe / Format Data / yes
- Reboot to TWRP again
- Advanced / Fix AVB
- Reboot to System
Done!
P.S.: You will lost all data after this.

No, that didn't work. Kept getting -twrp error 1- when flashing the Disable dm verity forceencrypt file.
Tried several times.
Tried reinstalling the stock boot.img then installing same error 1
Tried reinstalling the stock rom installing twrp then flashing disable varity same error 1
Tried ignoring the error and going to fix AVB still no luck
Everything I tried it still just returned to the stock recovery

beaker2 said:
No, that didn't work. Kept getting -twrp error 1- when flashing the Disable dm verity forceencrypt file.
Tried several times.
Tried reinstalling the stock boot.img then installing same error 1
Tried reinstalling the stock rom installing twrp then flashing disable varity same error 1
Tried ignoring the error and going to fix AVB still no luck
Everything I tried it still just returned to the stock recovery
Click to expand...
Click to collapse
Try flash magisk before reboot system

nttuan said:
Try flash magisk before reboot system
Click to expand...
Click to collapse
I gave up and installed Magisk 23 and rooted. I just decided to live with the stock rom (debloated) and the stock recovery

[ROM] [Xtended] [Unofficial] [A11 October 1 2021 Security Patch] For S9 and S9 Plus [Exynos]

I am not responsible if you brick your device installing this ROM, you are installing this at your own risk.
Downloads
Mod Edit: DL links removed.
Create device backup first:
1. 1. Boot TWRP/OrangeFox by pressing Bixby+VOL_UP+PWR as you are booting your device.
2. Go tho the backup tab of TWRP/OrangeFox
3. Backup Data, System, Cache, Boot, and System Image
4. Then backup the TWRP/Fox folder on your device to your computer just in case anything goes wrong.
How to install:
1. Boot TWRP/OrangeFox by pressing Bixby+VOL_UP+PWR as you are booting your device.
2. Go do the wipe tab of your recovery of choice, and wipe; DATA, CACHE, SYSTEM, and DALVIK CACHE.
3. Then flash the ROM you copied over to your device, or flash the ROM via ADB, it is up to you.
Reboot and enjoy!
Credits:
Thanks to the arrow-devices github community for the device sources for the S9 series of devices: Their Github Page
Samsung vendor (credit: Synt4x.93 (XDA) Synt4x93 (Github))
Galaxy S9 Plus device tree
Galaxy S9 device tree
Galaxy *9 Series kernel (credit: Synt4x.93 (XDA) Synt4x93 (Github))
Galaxy *9 Series common tree (credit: Synt4x.93 (XDA) Synt4x93 (Github))
Huge thanks to Baddar90 for fixing the battery drain issue this rom was having.
The fix source code: here
His Github: here
Gapps: (credits of the Flame Gapps Team. (Their website)
1.To flash Gapps first download Flame Gapps from here (full gapps package), here (basic gapps package)
2.Then boot TWRP/OrangeFox with the above method.
3. Find the Gapps zip you downloaded, tap on it, and swipe to flash.
4.Reboot and you should have Gapps!
How to get the out of box google setup experience when flashing Gapps (recommended):
1.After flashing the ROM reboot the device once to make sure the ROM boots.
2. On the home screen enter the power menu and then tap on "Reboot" then "Recovery.
3. Once your phone is in the custom recovery of choice, wipe the data partition.
4. Then flash Gapps again.
5. Reboot and you should have access to the the Gapps out of box setup experience!
For those of you who want to use MicroG I will not be covering it here. But the NoGoolag Telegram group as well as r/Privacy on Reddit should be able to help you if you would like to take that route.
r/privacy
NoGoolag Telegram Group
Other Telegram Groups:
(If you would like a Kernel that can help improve battery life you can ask about it here)
P.S Xtended is a great ROM, but it does have a few more bugs than other custom ROMS may have. Not enough to cause any issues but enough for you to notice the occasional hiccup here and there. This ROM is great for people who like A LOT of customizability though. By the way, bur is alos broken to and their is nothing I can do about that sorry. I'd recommend going to Display-Enable Blurs, and toggle it to off. After a device reboot at least you will get some transparency.
I hope you like it!
Also tell me if the ROM works on your S9 Plus as I can then remove that "Untested" badge from it.

Thread closed.

[ROM][12.1][UNOFFICIAL] Awaken OS V2.6 Eclipse [Redmi 7/Y3] [Onclite]

{
"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"
}
Awaken OS for Redmi 7/Y3 [onclite]​
#include <std_disclaimer.h>
/*
* Your warranty is void. Or...Valid? Probably?
*
* Project Awaken and its maintainers are not responsible for bricked devices,
* dead SD cards, data loss, thermonuclear war, or economic crisis caused by
* Awaken OS. YOU are choosing to make these modifications, and if you
* point your finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
Born different, Now Awaken
Awaken OS brings consistent, fluent, and smooth experience with all your must-have customizations, for you, for the community, and everyone.
- Project Awaken -
Saikiran
Ninad Patil [REIGNZ]
Mukul [undead]
- Designers -
Hugwalk
Jagadish
Glitch
Find me on Telegram! @tech_rom​
Awaken OS 2.6 Device Changelogs​
You may have a login problem in GApps, So that's why I have provided you with Vanilla Build ( ROM Side )​
First Time Install / Clean Flash
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Wipe Cache / Data / System
4. Flash ROM
5. Flash Gapps (optional)
6. Flash Magisk (optional)
7. Reboot to System and #beAwakened
Update / Dirty Flash
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Flash ROM
4. Wipe Cache
5. Reboot to System and #beAwakened​
Download Here / GApps / ScreenShots ( Use Telegram )
Reach Us
Official Channel / Official Discussion​
AwakenOS Official
Official Announcement / Official Community
Social Media - Tech Rom
Youtube / Telegram
Awaken Source Code
Rom Source / Github
Changelog:
• Initial Android 12.1 Rebase
• April Security Patch
• Pixel 6 Pro April Build Fingerprint
• Import XiaomiParts from sdm845-common
• Enable F2FS user data
• Enable vibration multiple intensities
• Don't write binary XML files
Redmi 7/Y3 Onclite Project
Device Source / Kernel Source / Vendor Source​
ROM Version: Android 12.1 - Eclipse 2.6
ROM Kernel: Linux 4.9.287
Based On: AOSP
Release Type: Stable

I updated your Rom. no matter the pure installation or dirty installation, they are all stuck in the boot screen and can not fully enter the system. Why is this? Would you please teach me?

Also, my red rice 7 works well in your version 2.1!

雪獒2021 said:
I updated your Rom. no matter the pure installation or dirty installation, they are all stuck in the boot screen and can not fully enter the system. Why is this? Would you please teach me?
Click to expand...
Click to collapse
Dude it’s a F2FS format
Just install awaken 2.2 as well you know
Then go to settings and select manage partition
Follow guide
1. Open manage partition
2. Click on data
3. Now change your data partition
4. Select F2FS and swipe
5. After complete, reboot now

Aniket Pro said:
Dude it’s a F2FS format
Just install awaken 2.2 as well you know
Then go to settings and select manage partition
Follow guide
1. Open manage partition
2. Click on data
3. Now change your data partition
4. Select F2FS and swipe
5. After complete, reboot now
Click to expand...
Click to collapse
Hello! Is your version 2.1 and 2.2 in f2fs format? I use the official twrp to install version 2.1 according to your tutorial. Whether it is dirty or pure, it works well. However, version 2.2, whether pure installation or dirty installation based on version 2.1, will be stuck in the boot screen and cannot enter the system!

雪獒2021 said:
Hello! Is your version 2.1 and 2.2 in f2fs format? I use the official twrp to install version 2.1 according to your tutorial. Whether it is dirty or pure, it works well. However, version 2.2, whether pure installation or dirty installation based on version 2.1, will be stuck in the boot screen and cannot enter the system!
Click to expand...
Click to collapse
Join my telegram dude i will give you proper guide

Aniket Pro said:
加入我的电报伙伴，我引导你适当的指导
Click to expand...
Click to collapse
Aniket Pro said:
Join my telegram dude i will give you proper guide
Click to expand...
Click to collapse
Thank you for your invitation. I don't understand English. I communicate with you here with the help of Google translation. The telegram doesn't have Chinese. I can't communicate with you. I'm sorry!

Aniket Pro said:
Join my telegram dude i will give you proper guide
Click to expand...
Click to collapse
Today, I tried other Android 12 threads of Hongmi 7 on XDA, which can run smoothly. Only your version 2.2 can not be installed and run smoothly. What did I do wrong?

雪獒2021 said:
Thank you for your invitation. I don't understand English. I communicate with you here with the help of Google translation. The telegram doesn't have Chinese. I can't communicate with you. I'm sorry!
Click to expand...
Click to collapse
I can understand your problem and I will try to guide you right here
Many people will think that why I have created f2fs build but would like to tell everyone that your recovery encryption problem will be fixed inside this build
First of all you have to follow some steps which is most important for you and can get your rom boot up
1. First of all format your device
2. After that click on advance in which you will see dalvik,cache,system,data,vendor fix all these and swipe to clear
3. After complete reboot your device in recovery again ( reboot - recovery)
4. When your device is in recovery mode again you have to flash Awakener 2.2 rom
5. After completion of flashing you do not have to reboot your device but go to the bag and format your device again by typing yes
6. After completing, you have to go to the recovery settings, where you will see Manage Partition
7. After clicking on manage partition, you will see the data option, after clicking on the data, the last option will be change fs or change format
8. After clicking on that option, there will be an option f2fs, you just have to click on it and swipe, after completing everything, you have to reboot your device and your device will take the boot up
Hope you will get proper knowledge

Bro boot looping after updating rom

Aniket Pro said:
I can understand your problem and I will try to guide you right here
Many people will think that why I have created f2fs build but would like to tell everyone that your recovery encryption problem will be fixed inside this build
First of all you have to follow some steps which is most important for you and can get your rom boot up
1. First of all format your device
2. After that click on advance in which you will see dalvik,cache,system,data,vendor fix all these and swipe to clear
3. After complete reboot your device in recovery again ( reboot - recovery)
4. When your device is in recovery mode again you have to flash Awakener 2.2 rom
5. After completion of flashing you do not have to reboot your device but go to the bag and format your device again by typing yes
6. After completing, you have to go to the recovery settings, where you will see Manage Partition
7. After clicking on manage partition, you will see the data option, after clicking on the data, the last option will be change fs or change format
8. After clicking on that option, there will be an option f2fs, you just have to click on it and swipe, after completing everything, you have to reboot your device and your device will take the boot up
Hope you will get proper knowledge
Click to expand...
Click to collapse
Hello, I'm disturbing you again! I can't do the sixth point you wrote. I can't find the option to manage partitions in my twrp. What should I do? I use twrp3 6.0-9. Does this version not have this option?

雪獒2021 said:
Hello, I'm disturbing you again! I can't do the sixth point you wrote. I can't find the option to manage partitions in my twrp. What should I do? I use twrp3 6.0-9. Does this version not have this option?
Click to expand...
Click to collapse
Try the orange fox recovery link: https://www.mediafire.com/file/qwzicg4vfrijcya/OrangeFox-onclite-beta%40R11.1.zip/file

Rashik lama said:
Bro boot looping after updating rom
Click to expand...
Click to collapse
First of all, you have to follow some steps which are most important for you and can get your rom bootup
1. First of all format your device
2. After that click on advance in which you will see dalvik, cache, system, data, vendor fix all these and swipe to clear
3. After complete reboot your device in recovery again ( reboot - recovery)
4. When your device is in recovery mode again you have to flash Awakener 2.2 rom
5. After completion of flashing you do not have to reboot your device but go to the bag and format your device again by typing yes
6. After completing, you have to go to the recovery settings, where you will see Manage Partition
7. After clicking on manage partition, you will see the data option, after clicking on the data, the last option will change fs or change format
8. After clicking on that option, there will be an option f2fs, you just have to click on it and swipe, after completing everything, you have to reboot your device and your device will take the boot up
Hope you will get proper knowledge

Aniket Pro said:
First of all, you have to follow some steps which are most important for you and can get your rom bootup
1. First of all format your device
2. After that click on advance in which you will see dalvik, cache, system, data, vendor fix all these and swipe to clear
3. After complete reboot your device in recovery again ( reboot - recovery)
4. When your device is in recovery mode again you have to flash Awakener 2.2 rom
5. After completion of flashing you do not have to reboot your device but go to the bag and format your device again by typing yes
6. After completing, you have to go to the recovery settings, where you will see Manage Partition
7. After clicking on manage partition, you will see the data option, after clicking on the data, the last option will change fs or change format
8. After clicking on that option, there will be an option f2fs, you just have to click on it and swipe, after completing everything, you have to reboot your device and your device will take the boot up
Hope you will get proper knowledge
Click to expand...
Click to collapse
Thanks for your help buddy . I am able to use awaken os 2.2 now

Hello, the latest (2.6) version can't log in to Google, and it doesn't work to hang a VPN. Google Suite doesn't run at all. What should I do?

Aniket Pro said:
Awaken OS for Redmi 7/Y3 [onclite]​
Born different, Now Awaken
Awaken OS brings consistent, fluent, and smooth experience with all your must-have customizations, for you, for the community, and everyone.
- Project Awaken -
Saikiran
Ninad Patil [REIGNZ]
Mukul [undead]
- Designers -
Hugwalk
Jagadish
Glitch
Find me on Telegram! @tech_rom​
Awaken OS 2.6 Device Changelogs​
You may have login problem in GApps, So that's why I have provided you with Vanilla Build ( ROM Side )​
First Time Install / Clean Flash
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Wipe Cache / Data / System
4. Flash ROM
5. Flash Gapps (optional)
6. Flash Magisk (optional)
7. Reboot to System and #beAwakened
Update / Dirty Flash
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Flash ROM
4. Wipe Cache
5. Reboot to System and #beAwakened​
Download Here / ScreenShots ( Use Telegram )
Reach Us
Official Channel / Official Discussion​
AwakenOS Official
Official Announcement / Official Community
Social Media - Tech Rom
Youtube / Telegram
Awaken Source Code
Rom Source / Github
Redmi 7/Y3 Onclite Project
Device Source / Kernel Source / Vendor Source​
ROM Version: Android 12.1 - Eclipse 2.6
ROM Kernel: Linux 4.9.287
Based On: AOSP
Release Type: Stable
Click to expand...
Click to collapse
Changelog:
• Initial Android 12.1 Rebase
• April Security Patch
• Pixel 6 Pro April Build Fingerprint
• Import XiaomiParts from sdm845-common
• Enable F2FS user data
• Enable vibration multiple intensities
• Don't write binary XML files
Bugs:
• You may have a login problem in GApps, So that's why I have provided you with Vanilla Build ( ROM Side )

Changelog:
• Initial Android 12.1 Rebase
• April Security Patch
• Pixel 6 Pro April Build Fingerprint
• Import XiaomiParts from sdm845-common
• Enable F2FS user data
• Enable vibration multiple intensities
• Don't write binary XML files
Bugs:
• You may have a login problem in GApps, So that's why I have provided you with Vanilla Build ( ROM Side )

Dear brother: Is there any plan to adapt to Android 13?

Great rom bro thanks for your updates and hope you will do better again and again .

[OFFICIAL][zippo] LineageOS 20 (Android 13) for the Lenovo Z6 Pro

{
"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 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 restores 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 our Gerrit Code Review.
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.
*/
SUPPORTED DEVICES
- zippo (L78051)
HOW TO INSTALL LINEAGEOS WITH LINEAGE RECOVERY
Please NOTE! As of LineageOS 19.1? We do NOT support bootloader locked! You MUST unlock your bootloader to use this version!
- Make sure your phone is running firmware from at least CN 12.5.332. If not? Please download and install it via recovery. It can be flashed before the ROM
If you want to follow the official instructions for bootloader unlock? Please go to the LineageOS Wiki here:
https://wiki.lineageos.org/devices/zippo/install
If you want to preserve a locked bootloader? Download and follow the instructions in this zip and then follow the official wiki instructions but skip the bootloader unlock section.
HOW TO UPDATE LINEAGEOS WITH LINEAGE RECOVERY
Please follow the official instructions on the LineageOS Wiki here:
https://wiki.lineageos.org/devices/zippo/update
HOW TO INSTALL LINEAGEOS WITH TWRP
Please NOTE! As of LineageOS 19.1? We do NOT support bootloader locked! You MUST unlock your bootloader to use this version!
- Make sure your phone is running firmware from at least CN 12.5.332. If not? Please download and install it via recovery. It can be flashed before the ROM
- Download the LineageOS and firmware zips. (see Downloads)
- Boot into TWRP.
- Copy the downloaded zip files to the internal storage of the device.
- Perform a backup of your current ROM. (Optional)
- RECOMMENDED: Do a factory reset (clean wipe)! No support if you didn't! (Wipe Dalvik, system, cache and format data)
- NOTE: If coming from stock ROM? You MUST format data (Wipe > tap "Format Data" button > type "yes" > keyboard checkbox)
- Flash firmware and LineageOS zips.
- Optional: Install the Google Apps addon package. (see Downloads)
- Reboot to system.
HOW TO UPDATE LINEAGEOS WITH TWRP
- Download the LineageOS zip(s). (see Downloads)
- Copy the downloaded zip files to the internal storage of the device.
- Reboot to TWRP.
- Flash LineageOS. (Wiping Dalvik and Cache is optional, but recommended)
- Reboot to system.
MAIN DOWNLOADS
TWRP for zippo: Official
Lenovo Z6 Pro
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Lineage:
- Official:
LineageOS Downloads
download.lineageos.org
- Unofficial:
Package lineage-20 - lineageos-for-zippo - OSDN
Package lineage-20 - lineageos-for-zippo #osdn
osdn.net
GOOGLE APPS (GAPPS) DOWNLOADS
- MindTheGapps:
http://downloads.codefi.re/jdcteam/javelinanddart/gapps
GOOGLE CAMERA (GCAM) DOWNLOADS
Google Camera:
Wichaya GCam APKs - Google Camera Port
Modified Google Camera app by Wichaya.
www.celsoazevedo.com
Recommended version:
https://www.celsoazevedo.com/files/android/google-camera/dev-wichaya/f/dl5/
Recommended config:
https://osdn.net/projects/lineageos-for-zippo/releases/76575
FIRMWARE DOWNLOADS
Minimum required versions:
- zippo (L78051) CN 12.5.365
https://osdn.net/projects/lineageos-for-zippo/releases/p17514
DEVELOPER RESOURCES
https://github.com/lenovo-sm8150/local_manifests/
GitHub - LineageOS/android_device_lenovo_sm8150-common
Contribute to LineageOS/android_device_lenovo_sm8150-common development by creating an account on GitHub.
github.com
GitHub - LineageOS/android_device_lenovo_zippo
Contribute to LineageOS/android_device_lenovo_zippo development by creating an account on GitHub.
github.com
GitHub - LineageOS/android_kernel_lenovo_sm8150
Contribute to LineageOS/android_kernel_lenovo_sm8150 development by creating an account on GitHub.
github.com
HOW TO CONTRIBUTE
Send your patches up for review: https://review.lineageos.org/
Read the guides on the LineageOS Wiki: https://wiki.lineageos.org/
Source Code: https://github.com/LineageOS
DONATIONS
Pay Marc Bourgoin using PayPal.Me
Go to paypal.me/ThEMarD85 and type in the amount. Since it’s PayPal, it's easy and secure. Don’t have a PayPal account? No worries.
www.paypal.com

KNOWN BUGS
Currently only works with bootloader unlocked
SafetyNet does not pass (Unfortunately, this is not possible as your SoC has hardware attestation... the workaround is to use unsupported mods like Magisk which tbh I haven't tried myself as I don't root my devices, but other users said that plus the SafetyNet Magisk mod works)
Fingerprint icon is too low compared to actual location of the scanner
Heyyo, allow me to introduce myself. I am Marc "ThE_MarD" Bourgoin and I maintain LineageOS and TWRP for the LeEco Le Max 2 (X2) and was crowdfunded a zippo which I will maintain LineageOS for (with selinux enforcing of course) and maybe assist with TWRP later. I also own a Motorola Edge 30 (dubai) which I maintain LineageOS for, Asus Zenfone 5z (Z01R), and I was also donated a Motorola Moto X4 (Payton) which I maintain LineageOS and TWRP for.
I'd like to take this moment to also thank anyone who donated to the crowdfunding campaign for my zippo! Without you? I wouldn't have this epic device in my hands to work on.
Also MAJOR thanks to Zhenxiang Chen (aka pasta_con_tonno, Lucchetto) for all the amazing work he has done on zippo.
Special thanks to Einar Gednochsson (aka kanstmablason, pete80pro) for organizing the crowdfunding campaign for my zippo and also a new one for KuranKaname so he can revamp our kernel.
Thanks also to hypnz, chema f, gawin and Lucky for also working in zippo and to HighwayStar who started the initial trees for heart (Lenovo z5 Pro GT) which zippo trees are based upon and Art_Chen for working on heart and zippo and also bringing us FOD Dimming and DC Dimming.
Thanks again to Zhenxiang and Chema f for figuring out and implementing the QFIL recovery and vbmeta while keeping the bootloader locked

Heyyo, LineageOS 20 official is out and the first build for zippo is up!

@ThE_MarD ,
Will you be including this commit the hardware fix/support for the camera (camera: Expose aux cameras in third party apps) from Chemas Evo build in your Lineage build? I'd rather not have google services installed to use GCAM in order to access the other lens' and the ZUI camera does not install correctly anymore for 13 (it did for 12, partially). There are other apps that don't rely on g-services that are able to access the hardware (HIDL?) switch to select which lens is used for image processing.

Heyyo @project_2501 , after checking with other devs about that commit and also how aux cameras are set up? I think for that we can just modify our props in the device tree tbh. The problem we currently have is we are limiting it to only a few app names. We could transition to an aux camera blacklist since there's probably only a handful of apps that would screw up (I can't remember if it was here or my Asus Zenfone 5z, but the Adobe Scan app would screw up and fail to initialize any camera) so we could just tackle a blacklist as crappy apps show up lol
As you can see here, we mainly expose aux cameras to a few apps and others have to essentially find out themselves like gcam mods
android_device_lenovo_sm8150-common/system.prop at lineage-20 · LineageOS/android_device_lenovo_sm8150-common
Contribute to LineageOS/android_device_lenovo_sm8150-common development by creating an account on GitHub.
github.com

@ThE_MarD ,
Will the blacklist instead of a whitelist be applied on the next scheduled build? Thank you for addressing it.

@project_2501 sorry not yet as I need to test it first and I haven't had time yet

Heyyo, lineage-20.0-20230122-UNOFFICIAL-zippo test build is going up! ! It has a new rebased kernel by MikeNG. Please test all functions. It also has a change to swap the aux camera allowed list to an aux camera exclude list to keep things easier and only exclude apps that don't play well with aux cameras so please test a lot of camera apps
Release lineage-20 lineage-20.0-20230122-UNOFFICIAL-zippo - lineageos-for-zippo - OSDN
Release lineage-20 lineage-20.0-20230122-UNOFFICIAL-zippo - lineageos-for-zippo #osdn
osdn.net
@project_2501 if you could please test this build. You can swap between unofficial and official builds at any time

Switching between the camera lens' works (still don't see 48mp for the main lens' resolution); install almost hanged on patching vendor which I found odd. Camera app believes there are six cameras for some odd reason and will crash if selecting the sixth camera, I'm guessing it's also referencing the video profile because it doesn't crash in video mode when selecting the sixth camera (dual lens for video or mixed up with front lens' maybe)? Can you provide a link to the source for the kernel?

@project_2501 which camera app are you trying btw?
Source code links are in the first post please check there

ThE_MarD said:
@project_2501 which camera app are you trying btw?
Source code links are in the first post please check there
Click to expand...
Click to collapse
Open Camera.
I'm unfamiliar with MikeNG and kernel modifications he may have committed when looking at the source code for the kernel, just wondering since you stated it was using a different kernel (than official LOS?).

@project_2501 oh, Open Camera does things a lot differently than other camera apps so tbh I don't think there's a way to configure it... So I'd recommend just sticking with Aperture or use a gcam mod... But from what you said Open Camera is now seeing more camera apps so the change in aux camera lists commit is working then?

@ThE_MarD , yes I can switch between all the lens'. System stability has not been jeopordized, the app will just crash if trying to process from the sixth camera ID. Do you remember what modes the ZUI camera app had? Was there a dual (both front and back camera) mode? Maybe the sixth profile is for the front camera and the app doesn't switch to it when cycling through the lens' (front camera can still be accessed with a different on screen UI switch anyways). The problem in itself is app related; regardless, the commit works and should be included in the next build for others like myself who enjoy a clean minimalist build with full access to the hardware.

Hi, i'm on firmware 11.0.405 ST.
Now i'm still waiting my SN from Lenovo to unlock bootloader.
Newbie question:
After installing TWRP --> Wipe > tap "Format Data" button > type "yes" > keyboard checkbox > Flash firmware CN 12.5.332 > reboot to recovery or reboot to system ?
Thanks a lot for the rom!

Heyyo @danz852, after doing the format data, flash firmware and flashing ROM? You can optionally install any addons (such as GApps) and then reboot to system or skip the addons and reboot to system.

ThE_MarD said:
Heyyo @danz852, after doing the format data, flash firmware and flashing ROM? You can optionally install any addons (such as GApps) and then reboot to system or skip the addons and reboot to system.
Click to expand...
Click to collapse
@ThE_MarD , thanks for the reply. Appreciated
I'm still waiting file from Lenovo to unlock bootloader.

Finally got the file to unlock bootloader.
I flashed twrp > shut down the phone > hold Volume Up + Power > but it cannot boot to recovery, only show fastboot/bootloader.
Then I tried I flashed twrp > shut down the phone > Volume Down + Power > fastboot mode > then i select recovery mode > phone restarted > only returned to fastboot mode again.
Any help to solve this problem? failed to flash twrp recovery.
Thanks in advance.

@danz852 just to check, you're flashing it to the recovery partition?
The TWRP website has the full instructions too
Lenovo Z6 Pro
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Code:
fastboot flash recovery twrp.img
Otherwise you can try first via Lineage Recovery and follow the LineageOS wiki instructions
Install LineageOS on zippo | LineageOS Wiki
wiki.lineageos.org

Hi, thanks for fast reply.
Yes i'm flashing it to the recovery partition (fastboot flash recovery twrp.img). The result was success. But still cannot boot to twrp.
FYI: I'm using file from this https://club.lenovo.com.cn/thread-7839615-1-1.html to unlock the bootloader because at least until now i didn't receive unlock file from Lenovo.
I tried to flash twrp-3.7.0_12-0-zippo then tried Lineage recovery , flashing was success but still cannot boot to recovery.
After that flashed TWRP 3.4.0 by @mauronofrio. this one is working and boot to twrp recovery. I proceed with Wipe Dalvik, system, cache and format data. Then ADB sideload firmware CN 12.5.332. Continue with ADB sideload LineageOS found no problem with the installation the proceed reboot to System (it's written No OS Installed!), I keep continue to reboot to System anyway. It stuck at Lenovo Logo the restart by itself back to Lenovo logo again and so on.
Maybe because TWRP 3.4.0 is not working for Android 13.
Now I'm trying to sideload firmware L78051_CN_11_5_229_Q_Stable_recovery., because i think it will be working with TWRP 3.4.0 but the result is the same, end up with Lenovo logo then it restart by itself again and again.

danz852 said:
Hi, thanks for fast reply.
Yes i'm flashing it to the recovery partition (fastboot flash recovery twrp.img). The result was success. But still cannot boot to twrp.
FYI: I'm using file from this https://club.lenovo.com.cn/thread-7839615-1-1.htmll to unlock the bootloader because at least until now i didn't receive unlock file from Lenovo.
I tried to flash twrp-3.7.0_12-0-zippo then tried Lineage recovery , flashing was success but still cannot boot to recovery.
After that flashed TWRP 3.4.0 by @mauronofrio. this one is working and boot to twrp recovery. I proceed with Wipe Dalvik, system, cache and format data. Then ADB sideload firmware CN 12.5.332. Continue with ADB sideload LineageOS found no problem with the installation the proceed reboot to System (it's written No OS Installed!), I keep continue to reboot to System anyway. It stuck at Lenovo Logo the restart by itself back to Lenovo logo again and so on.
Maybe because TWRP 3.4.0 is not working for Android 13.
Now I'm trying to sideload firmware L78051_CN_11_5_229_Q_Stable_recovery., because i think it will be working with TWRP 3.4.0 but the result is the same, end up with Lenovo logo then it restart by itself again and again.
Click to expand...
Click to collapse
UPDATE:
Finally it worked out:
I'm still using TWRP 3.4.0. Copy firmware L78051_CN_11_5_229_Q_Stable_recovery to internal storage then flash it. Reboot to System. It said my phone partition is corrupted .
Then i reboot the phone to Fastboot mode. I checked bootloader is Locked > proceed with fastboot flash unlock sn.img > fastboot oem unlock-go > reboot to system. After enable USB debugging in Developer Option > reboot to recovery > Wipe Dalvik, system, cache and format data > flash CN 12.5.332 and LineageOS. > reboot to system > Finally it booted to Lineage.
I'm happy. Thanks again @ThE_MarD for the rom!!!