Database Develop

[MOD] MultiROM for Xperia SP

{
"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"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.​
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
Installation
Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 2 parts you need to install + one optional (deprecated) :
MultiROM (multirom-YYYYMMDD-v33x-device.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (multirom-YYYYMMDD-recovery-fota-device.zip) - download the ZIP file from second post and use a recovery
to flash it into the FOTA partition (see TWRP 3 thread for more informations).
DEPRECATED: Patched kernel - You can use those kernels on most Marshmallow and Lollipop based primary ROMs to add kexec boot support.
Be aware that those patchers will be updated when possible after kernel sources updates
Kexec support no longer required thanks to the no-kexec workaround by nkk71.
For convenience reasons, I enabled the workaround by default if kexec is not found.
You current rom will not be erased by the installation.
Download links are in the second post.​
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Recommended values are :
Cache : Keep default value
Data : Minimum 4000
System : 1000 is enough for most installs
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Android to 4Gb image on a pretty fast USB drive takes about 20 minutes maximum.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
OPTIONAL: Reflash the kernel patcher to add kexec support
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.​
Source code
MultiROM - https://github.com/AdrianDC/multirom_core (branch master)
Modified TWRP - https://github.com/multirom-dev/Team-Win-Recovery-Project (branch master)
Device Tree - https://github.com/XperiaMultiROM/android_device_sony_huashan (branch master)​
MultiROM available for Huashan also thanks to :- [MENTION]Tasssadar[/MENTION]
- The XperiaMultiROM team
- The MultiROM HTC team
- [MENTION]Arvind7352[/MENTION]
- [MENTION]nkk71[/MENTION]​
XDA:DevDB Information
MultiROM for Xperia SP, Tool/Utility for the Sony Xperia SP
Contributors
Adrian DC
Source Code: http://forum.xda-developers.com/google-nexus-5/orig-development/mod-multirom-v24-t2571011
Version Information
Status: Stable
Created 2016-04-03
Last Updated 2017-06-07

Reserved
Downloads
1. Main downloads
Xperia SP (Huashan): https://mega.nz/#F!mpMATaJa!gGshpOwYueKdK0bu6YSNUg
MultiROM: multirom-2017MMDD-v33x-device.zip
Modified recovery (based on TWRP 3): multirom-2017MMDD-recovery-fota-device.zip
OPTIONAL: Kernel w/ kexec-hardboot patch (msm8960t Marshmallow based): kernel-2016MMDD-device.zip
If used, kernel with kexec-hardboot patched needs to be only in your primary ROM!
No longer required thanks to the no-kexec workaround.
OPTIONAL: MultiROM installed as a secondary "ROM": multirom-2016MMDD-recovery-secondary-device.zip
Mostly meant to be used for Stock ROMs users and devs. Only use as secondary ROM to flash.​
2. Third-party kernels with kexec-hardboot patch
* None, and do not use any that would have it until the kernel is ready
Nicely ask your kernel developer to merge kexec-hardboot patch.​
3. Uninstaller
MultiROM uninstaller: Unavailable due to the already considerable SONY ELF format port
Reflash a ROM or a boot.img without injection (or the v33x zip) to remove MultiROM bootimage from your device.
Then delete the "multirom..." folders from internal & external storages.
If you don't want MultiROM menus in recovery, re-flash a normal TWRP, but it is not needed,
those menus don't do anything if MultiROM is not installed.​
How to install for the first time
Flash the 2 MultiROM zips as explained
Reboot to the FOTA Recovery (Volume +)
In MultiROM TWRP, Add a ROM, set everything properly
Wait for the ROM to be installed (can take a while)
In MultiROM screen, choose the ROM location
For the concerned ROM, "Flash zip" for wished zips (GApps, SuperSU, Addons...)
Reboot the phone
Changelog
Code:
MultiROM v33x - TWRP 3.2.1 - 21/01/2018
=========================================
* Merged TWRP 3.2.1 updates into MultiROM TWRP
* Improvements for Android 8.1 support
* Improvements [URL="https://www.xda-developers.com/rest-in-peace-xda-recognized-developer-nkk71-has-passed-away/"]made with nkk71, RIP[/URL] >> [URL=https://www.xda-developers.com/rest-in-peace-xda-recognized-developer-nkk71-has-passed-away/#comment-3719128510]Comment[/URL]
MultiROM v33x - TWRP 3.1.1 - 01/11/2017
=========================================
* Improvements for Android 8.0 support
* Improvements for SDCardFS support
* Improvements from secondary ROMs handling
* Changes on the boot UI's Android ROM icons
MultiROM v33x - TWRP 3.1.1 - 07/06/2017
=========================================
* New implementation to handle external boot
on Ext4 / F2FS MicroSD or USB Drive in order
to allow access to the external storage for media,
through the storage 'external_multirom' path
MultiROM v33x - TWRP 3.1.1 - 17/05/2017
=========================================
* Include all recent improvements from TWRP 3.1.1
MultiROM v33x - TWRP 3.1.0 - 03/05/2017
=========================================
* Upstream updates from recovery and sources
* Fix for the offline charger detection mode
MultiROM v33x - TWRP 3.1.0 - 12/03/2017
=========================================
* Include all recent improvements from TWRP 3.1.0
MultiROM v33x - TWRP 3.0.3 - 05/03/2017
=========================================
* Built in a clean new tree of Android 7.1.1 (replaces 6.0)
* Multiple fixes to support 7.1 changes
* Include all recent improvements from TWRP 3.0.3
* Fix the 7.1 busybox cpio corruption, needed for MultiROM
MultiROM v33x - 18/12/2016
======================================
* Minor improvements of MultiROM
* Improved versioning with header showing build date
* libbootimg changes from my recent updates
MultiROM v33x - 17/10/2016
======================================
* Improve autobooting to external ROM (MicroSD / USB)
MultiROM v33x - 18/09/2016 - 24/09/2016
======================================
* Updated to no-kexec workaround v4 by nkk71
* Autoboot accessible for external / MicroSD
MultiROM v33x - 16/08/2016
======================================
* Add support for the new ramdisk structure with init.real
MultiROM v33x - 14/06/2016 - 15/07/2016
======================================
* Support for hardware keys (Volume +/- & Power)
MultiROM v33x - 06/06/2016
======================================
* Support for Stock SONY ROMs added
MultiROM v33x - 23/05/2016
======================================
* MultiROM UI dimensions completely fixed
* Access to MultiROM color themes and Shutdown
MultiROM v33x - 11/05/2016
======================================
* Support for no-kexec workaround to boot ROMs
MultiROM v33x - 15/04/2016 - 09/05/2016
======================================
* Improved UI with unified Internal / External ROMs in one tab
MultiROM v33x - 03/04/2016
======================================
* Initial release with full SONY ELF port and dual ramdisk support
Kernel patchers :
Code:
23/04/2016 - 06/06/2016
==========================
* Updated to latest sources, standalone kernel without modules
* Deprecated, releases abandoned.
06/04/2016 - 15/04/2016
==========================
* Updated to latest CM-13.0 & CM-12.1 stable kernel status
03/04/2016
==========================
* Initial huashan release, unstable kernel for the moment
Recent ROMs tested so far :
Code:
LineageOS 14.1 : OK (Primary & Second)
AOSP 7.1 : OK (Primary & Second)
AOSP 7.0 : OK (Primary & Second)
CyanogenMod 12.1 : OK (Primary & Second)
CyanogenMod 13.0 : OK (Primary & Second)
CyanogenMod 14.1 : OK (Primary & Second)
AICP Marshmallow : OK (Primary & Second)
AOSP-CAF Marshmallow : OK (Primary & Second)
AOSP-OMS Marshmallow : OK (Primary & Second)
AOSP-RRO Marshmallow : OK (Primary & Second)
Sony 4.3 based ROMs : Normally OK (Primary & Second)
eXistenZ Ultra 4.0.0 : OK (Primary & Second)
Warning : If using old ROMs as secondary, primary ROM
should not have F2FS filesystems for Data and Cache
Other ROMs : To confirm & report here

Reserved
FAQ and other notes
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.​
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.​
Why is my USB connection to computer not detected ?
Uncheck the "Enable ADB" option in MultiROM Settings.​
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive./external SD card. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.​
Can I have different versions of Android working alongside
Yes.​
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.​
The installation fails with "trampoline not found -1"
Often the issue appears because the ROM zip has a nested zip for rooting methods.
Best solution is to remove the root zip from the ROM and flash it separately later.​
Something wrong happened, I lost something or it's really laggy
You have been warned about making backups & the fact this is more experimental than stable.
You alone will be responsible for loosing data or having an usable ROM when you really needed it.
Everyone in this thread will try to help you, but we can't do backups of your data ourselves.
Thanks for your understanding, remember to read the previous comments and please try to help each other.​
Current local manifest of the MultiROM build
Code:
<!-- https://github.com/AdrianDC/multirom_development_sony -->

And no, this is not an april fools joke.

Clicking on that link for patched kernel, opens a google search page which shows links for AK kernel, is that what we're supposed to use??
STUPID QUESTION. NEVERMIND.

Whaaat ?
What the F#?+ !
Thank you thank you thank you.
Thats all i say !

WTF?! OMG! Thank you so much adrian!

Adrian >> Harry Potter
Sent from my Xperia SP using XDA-Developers mobile app

For People Using this MOD:-
Follow the Instructions carefully and try reporting which ROMs work with it. This would reduce Adrian's effort to list bootable ROMs. Hope almost all of the ROMs boot.
Congrats @Adrian DC :laugh: :highfive:

Thanks to AdrianDc
I've installed the cm-13.0-20160329 beside my AICP 10 (Lollipop).

Great! Please try to fix for .207
P.S. Remains only wait DT2W from you

-Mr.freeze- said:
Great! Please try to fix for .207
P.S. Remains only wait DT2W from you
Click to expand...
Click to collapse
Dont rush him or he'll personally send a assaniation pigeon from the other side of the world to your home

Primary: CM12.1 unofficial works great
CM13 Works great too
CM11 bugyusz didn't boot (because it use stock kernel)
AICP Works great
Sent from my Xperia SP

Furrydaus said:
Dont rush him
Click to expand...
Click to collapse
I'm not hurry him. This can be called wishes)

I installed cm13 and then wanted to flash AICP10 by twrp 3.0.1 r6, but encountered these errors (see the attached pix please)

desalt said:
I installed cm13 and then wanted to flash AICP10 by twrp 3.0.1 r6, but encountered these errors (see the attached pix please)
Click to expand...
Click to collapse
The rom is successfully installed. Nothing to worry about. I had also some days ago that error but the roms booted without a problem.
Sent from my A0001 using Tapatalk

darjwx said:
The rom is successfully installed. Nothing to worry about. I had also some days ago that error but the roms booted without a problem.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
tanx, but the Multirom menu doesn't appear and I have no choice to select AICP, moreover in the recovery there isn't any secondary ROM.

would you please see the following attached pix? do you see anything wrong?
the first one, says something (in mount menu) after failure in flashing the second rom.
and from the 2nd one, I guess my SD card is locked.
.

desalt said:
would you please see the following attached pix? do you see anything wrong?
Click to expand...
Click to collapse
First : Accept & set it to never ask again, it's ok.
Second : No. All storage devices are "block" based, doesn't mean anything related to the MicroSD being locked.
About old ROMs : No yet support nor known to work one day,
I'll get back to it soon enough but nothing sure yet.
Finally about latest CM12.1 / CM13 Beta releases : The newest MultiROM kernel patcher
can freely be used to test both ROMs as it has been updated to the same state.

I installed the proper Gapps for both cm12 and cm 13 without any problem when they were single Roms on my phone. but when I try to install each of them beside the other one as a secondary Rom , face to an error and installation process fails.

[ROM][SNAPSHOT][7.1] LineageOS 14.1 for Xperia TX

{
"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:
#include <std_disclaimer.h>
/*
* 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 LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.x (Nougat),
which is designed to increase performance and reliability over stock Android for your device.
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.
Official LineageOS website : http://lineageos.org​
Downloads Links
LineageOS 14.x (Unlocked Bootloader) :
Xperia TX (Hayabusa) - 14.1 : https://mega.nz/#F!O19HlahT!cY17UTilVThss5RD9TwSRQ
Google Applications (optional) :
OpenGapps : http://opengapps.org/ (Use packages for ARM, Android 7.x, Micro or Pico)
Information : Flash the GApps before the first boot. If not, a clean flash is recommended.
Recommended Recovery (optional) :
TWRP 3.0 : http://forum.xda-developers.com/xperia-t-v/t-development/recovery-twrp-3-0-0-touch-recovery-t3319588
Informations and references :
Kernel CVEs : Security patches status https://cve.lineageos.org/android_kernel_sony_msm8x60
About LineageOS updates : ChangeLog available on https://download.lineageos.org/hayabusa/changes/
About LineageOS device side : See my GitHub trees linked below​
Unification of the user partitions into UserData
Read more about the UserData unification :
- https://wiki.lineageos.org/devices/hayabusa/​
Flashing and updating
LineageOS clean install :
- (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool
- (Optional) Install TWRP Recovery to the FOTA partition (Read the TWRP thread)
- (Optional) Wipe the data & cache (Backup to make sure not to lose data)
- Flash the LineageOS ROM zip from the Recovery
- (Optional) Flash the GApps to have the Google Applications
- (Optional) Every additional zip you want to flash
- Reboot
LineageOS update / upgrade :
- (Information) Don't wipe anything unless you want to
- (CM / UNOFFICIAL) Nothing to wipe when switching
- (FUTURE RELEASES) Might need clean, informations will be updated
- Flash the latest LineageOS ROM zip from the Recovery
- (Optional) Flash the GApps on first install / upgrade. Not required later, but do update sometimes
- (Optional) Every additional zip you want to flash
- Reboot
LineageOS official upgrade from older builds :
- (Information) Read the following post : Update & Build Prep
- (Optional) Backup your applications and / or ROM
- (CM / UNOFFICIAL) Flash the EXPERIMENTAL migration build and reboot to Android
- Flash the latest LineageOS ROM and reboot to Android
LineageOS addonsu for root access :
- (Information) Read the Root section of the Q&A thread
- (Download) Download the addonsu for arm : LineageOS Downloads / Extras
- (Optional) Flash the zip on a working Lineage installation (once)
- (Information) Upon ROM updates, the addonsu is preserved
- Reboot​
About the builds
Device tree : https://github.com/LineageOS/android_device_sony_hayabusa
Common tree : https://github.com/LineageOS/android_device_sony_blue-common
Kernel sources : https://github.com/LineageOS/android_kernel_sony_msm8x60
Vendor blobs : https://github.com/TheMuppets/proprietary_vendor_sony​
Issues and reports
- Report issues only if you are using the ROM kernel
- If an additional mod is installed, make sure it's unrelated, and mention it
- Make sure the issue wasn't discussed earlier in the threads
- Share a log of the error with CatLog for example​
Q&A - FAQ
LineageOS 14.1 Hayabusa Regular Questions and Answers : Q&A Thread
About LineageOS Legal : http://lineageos.org/legal/
The LineageOS team would like to thank everyone involved
in helping with testing, coding, debugging & documenting! Enjoy!​
LineageOS available for Hayabusa also thanks to :
- The LineageOS Team
- The CyanogenMod Team
- Everyone involved in working and testing​
XDA:DevDB Information
LineageOS 14.1, ROM for the Sony Xperia T
Contributors
Adrian DC
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Snapshot
Created 2016-12-31
Last Updated 2020-08-15

Reserved
FEATURES AND ISSUES
Code:
- Boot : Ok
- GApps : OpenGApps Micro Ok
- Partitions (Data, Cache) : Ext4 and F2FS supported
- ROM Recovery : Broken for signed official (see below)
- FOTA Recovery : Ok (see below)
- WiFi : Ok (real SONY MAC address)
- Bluetooth : Ok (real SONY MAC address)
- WiFi Hotspot : Ok (2.4GHz and 5GHz)
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- Lights : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- AOSP sensors : Ok
- FM Radio : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & external audio : Ok
- Bluetooth audio : Ok
- NFC : Ok
- Kernel : Ok, Updating frequently based on Huashan kernel
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok (RTC real hardware clock, in TWRP recovery too)
- Powered-off alarm : Ok
- Offline Charging : Ok
- Encryption : Works but system gets slower
- UserData Unification : Ok
- SEPolicies : Fully enforced

Reserved
IMPORTANT FEATURES TO KNOW
Boot sequence : Once the LEDs light up :
- Press Volume - to open the ROM recovery,
- Press Volume + to open the FOTA recovery (TWRP usually) if available
Powered-off alarm : When you have set an alarm
- If you power down the device, it will wake automatically 5 minutes before
- If you let the device charge offline, it will automatically reboot 5 minutes before
Gestures : Events like hand-wave and pocket removal can be enabled in the Settings
Force reboot : You can reset the device by holding Power and Volume+ 5 seconds
Current local manifest of the ROM build
Code:
<!-- https://github.com/AdrianDC/laos_development_sony8960/blob/local_manifests/hayabusa.xml -->

What's new in 08.01 update? Where I can read about changes?

Missing root.. i have to flash it?

currently using this lineage-14.1-20170115-UNOFFICIAL-hayabusa.zip, and its really good
but what if i install stock rom gapps, is there any problem?
---------- Post added at 10:50 AM ---------- Previous post was at 10:10 AM ----------
Muhammad Amirul said:
currently using this lineage-14.1-20170115-UNOFFICIAL-hayabusa.zip, and its really good
but what if i install stock rom gapps, is there any problem?
Click to expand...
Click to collapse
not enough space?

Stock won't fit into the system partition.
I recommend micro (or pico if wished), additional apps you need are directly flashable and updated anyways by the Play Store.
Informations about root default removal will be shared soon.

Well, SuperSU flashes in systemless mode, and didn't work. What do we have to do to gain root access?

Lion_Heart9x said:
Well, SuperSU flashes in systemless mode, and didn't work. What do we have to do to gain root access?
Click to expand...
Click to collapse
Flash boot bridge with supersu

- UserData Unification no longer included inside the ROM release.
- New unify_userdata package generated to handle the same purpose
- restore_sdcard updated & both rehosted in a new folder
- Reliable CyanogenRecovery from Snapshot 13.0 kept online as safe working recovery
- Lineage Wiki informations updated and will be merged soon with the informations needed

Official Lineage releases are online and working fine so far.
Please read the informations I shared about the upgrade, migrations and the site post.
Also read the Features list, the ROM's Recovery is for now unable to flash our signed builds...

First I flash the rom, and i flash unify_userdata-20170128.zip. While flashing unify_userdata-20170128.zip, phone rebooted into CM recovery and showing error. And now, I have only 2GB usable. And when I try again to flash unify zip, it shows already unified and showing error 7. Any IDEAS????

Myo Thu Htet said:
First I flash the rom, and i flash unify_userdata-20170128.zip. While flashing unify_userdata-20170128.zip, phone rebooted into CM recovery and showing error. And now, I have only 2GB usable. And when I try again to flash unify zip, it shows already unified and showing error 7. Any IDEAS????
Click to expand...
Click to collapse
this might mean a lot of flashing, I would try:
1.fastboot flash recovery-13.0-20161220-SNAPSHOT-ZNH5YAO3XM-hayabusa.img
2.in CWM factory reset
3. install restore_sdcard-xxx.zip, follow instructions
4. reboot recovery
5. install unify_userdata-xxx.zip, follow instructions
6. fastboot flash twrp-3.0.2-20170108-boot-hayabusa.img
in TWRP look for partitions, if all is fine install rom and twrp.zip
else start over from 1

lobotron said:
this might mean a lot of flashing, I would try:
1.fastboot flash recovery-13.0-20161220-SNAPSHOT-ZNH5YAO3XM-hayabusa.img
2.in CWM factory reset
3. install restore_sdcard-xxx.zip, follow instructions
4. reboot recovery
5. install unify_userdata-xxx.zip, follow instructions
6. fastboot flash twrp-3.0.2-20170108-boot-hayabusa.img
in TWRP look for partitions, if all is fine install rom and twrp.zip
else start over from 1
Click to expand...
Click to collapse
where is the back key for CM recovery??
I followed your instructions and there still showing system partation has 14GB usage. Is that normal?? Can somebody show me screenshot( setting> storage) after unification.

Myo Thu Htet said:
where is the back key for CM recovery??
Click to expand...
Click to collapse
4 phones without hardware buttons the +++go back+++ item would have been nice ..., but you can always pull out the battery which has the advantage that you really reboot the bootloader
Myo Thu Htet said:
I followed your instructions and there still showing system partation has 14GB usage. Is that normal?? Can somebody show me screenshot( setting> storage) after unification.
Click to expand...
Click to collapse
I can't screenshot.
Unification still failed, you can check in twrp if you select storage, for example in install. You may add a factory reset in between 4-5.
Better first check the system space and if it's fine install the rom. Good luck!

This is the storage setting after clean flash and I cant install apps. Always showing storage is full. Plz Help. i did unification but the result is still the same. The storage are showing in TWRP. Any Idea???

Myo Thu Htet said:
This is the storage setting after clean flash
Click to expand...
Click to collapse
some general clarification, in the hope I got it right:
The unification just changes the amount of memory available to the system and data.
The rom will be stored in system, so what you see in (for example):
TWRP -> Install-> select storage-> Internal Storage
is the amount the user might use for apps and general usage, system will not appear.Your Phone has 16GB I would expect round about 10000MB, it's a guess as I have a different model out of the same family.
As long as there is something tiny it does not make much sense to install the rom as it's the wrong layout which will leave you with very little space to use.
So you will have to install the unification zip in TWRP.
If this fails CWM (1.) should help you out, first try if it can complete the unification - install unify_userdata from CWM.
If it reports the error 7 you will have to revert, to get rid of this error:
reboot CWM, factory reset, install restore_sdcard-xxx.zip, follow instructions, it will reboot itself. Afterwards reboot CWM again, factory reset, install unify_userdata, follow instructions, it will reboot itself.
Now unification should have succeeded.
Reboot into flashmode, flash twrp.img. Install the rom if storage has a reasonable value.
else try to fetch and tell what failed, the storage reported by the rom is calculated on the basis of a successful unification and therefore without any helpful information.

lobotron said:
this might mean a lot of flashing, I would try:
1.fastboot flash recovery-13.0-20161220-SNAPSHOT-ZNH5YAO3XM-hayabusa.img
2.in CWM factory reset
3. install restore_sdcard-xxx.zip, follow instructions
4. reboot recovery
5. install unify_userdata-xxx.zip, follow instructions
6. fastboot flash twrp-3.0.2-20170108-boot-hayabusa.img
in TWRP look for partitions, if all is fine install rom and twrp.zip
else start over from 1
Click to expand...
Click to collapse
That s work
Thanks sir

lobotron said:
some general clarification, in the hope I got it right:
The unification just changes the amount of memory available to the system and data.
The rom will be stored in system, so what you see in (for example):
TWRP -> Install-> select storage-> Internal Storage
is the amount the user might use for apps and general usage, system will not appear.Your Phone has 16GB I would expect round about 10000MB, it's a guess as I have a different model out of the same family.
As long as there is something tiny it does not make much sense to install the rom as it's the wrong layout which will leave you with very little space to use.
So you will have to install the unification zip in TWRP.
If this fails CWM (1.) should help you out, first try if it can complete the unification - install unify_userdata from CWM.
If it reports the error 7 you will have to revert, to get rid of this error:
reboot CWM, factory reset, install restore_sdcard-xxx.zip, follow instructions, it will reboot itself. Afterwards reboot CWM again, factory reset, install unify_userdata, follow instructions, it will reboot itself.
Now unification should have succeeded.
Reboot into flashmode, flash twrp.img. Install the rom if storage has a reasonable value.
else try to fetch and tell what failed, the storage reported by the rom is calculated on the basis of a successful unification and therefore without any helpful information.
Click to expand...
Click to collapse
Thanks sir, now unification is successful and I m enjoying LinageOS. Thank you very much

My Xperia TX LT29i don't wake up when it's idle for some time even power button don't do anything. I've tried both LineageOS and AOSP Nougat but I'm facing same issue. I've to remove battery each time which is very annoying.
Can anybody guide me to solve this issue?

[ROM][UNOFFICIAL] LineageOS 18.1 for Xperia 10 II [Gcam] [Performance]

{
"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:
#include <std_disclaimer.h>
/*
* 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 LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 11.x (R),
which is designed to increase performance and reliability over stock Android for your device.
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.
Official LineageOS website : http://lineageos.org
About LineageOS Legal : http://lineageos.org/legal/
Important Information
1. This ROM has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.
2. This ROM support Google Camera (GCam)! You need to flash Gapps at first.
3. You need to flash Stock Android 11 before flashing this ROM.
4. For VoLTE, you need to boot into stock firmware and enable it before flashing this ROM!
5.If you cam from SODP ROMs, you need to go back to official Android 11 firmware, and boot into launcher.
6.This ROM works fo both dual and single models.
Downloads Links
LineageOS 18.1:
Unofficial-build: Link
Recovery: Link
Google Applications (optional):
NikGapps, MindTheGapps. OpenGapps.
Information: Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
How to flash
Make sure you upgraded to Official Android 11.0 from Sony
Unlock bootloader is necessary.
Download latest platform-tools from google
1. Install fastbootd drivers, guidance
You can install google's usb debug drivers.
2. Download Lineage Recovery from AFH above.
3. Put your device into fastboot by volume up key.
4. Type the following command to flash the recovery:
Code:
fastboot flash recovery recovery.img
fastboot flash dtbo dtbo.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot reboot recovery
5. Sideload the ROM package.
6. If you are first time to flash LineageOS, Wipe data plz.
Gapps:
After flashing ROM via siddeload, Reboot to recovery, choose Apply from ADB, then sideload the gapps package on your PC with adb tool:
Code:
adb sideload <PATH OF GAPPS>
Never flash oem from SODP!!
If you flashed oem and meet any issues, I could only say you are a hanhan.
Root access:
Flash Magisk in recovery.
Twrp:
See this: Link
Gcam:
Recommond this one with my xml config.
Notice: You could only switch to front camera from telescope camera in Gcam.
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Share a log of the error with CatLog for example
Also thanks to:
Cubbins
The SDOP team
The LineageOS Team
The CyanogenMod Team
XDA:DevDB Information
Lineage-18.1 for Xperia 10 II, ROM for the Sony Xperia 10 II
Contributors
Sjll
Source Code:
https://github.com/sony-sm6125
Donation
https://paypal.me/sjllls
ROM OS Version: Android 11
ROM Kernel: Linux 4.14
Version Information
Status: Stable
Created 2021-01-16
Last Updated 2021-10-10

FEATURES AND ISSUES
Code:
- Boot: Ok
- Bluetooth: Ok
- WiFi: Ok
- WiFi Hotspot: Ok
- Wireless display: Ok
- RIL - Phone - Data: Ok
- VoLTE: Ok
- GPS: Ok
- Camera: Ok
- Camcorder: Ok
- Lights: Ok
- MicroSD: Ok
- Accelerometer: Ok
- Compass: Ok
- Gyroscope: Ok
- QTI sensors: Ok
- Touchscreen: Ok
- FM Radio: NA
- Fingerprint: Ok
- Vibrator: Ok
- Microphone: Ok
- Audio & music: Ok
- Bluetooth audio: Ok
- NFC: Not tested
- Kernel: Ok
- Graphics: Ok
- 3D Rendering: Ok
- Clock: Ok
- DRM: Widewine L3
- Offline Charging: Ok
- USB: Ok
- USB Tethering: Ok
- USB OTG: Ok
- Encryption: Ok
- SEPolicies: Enforce

Reserved

Will it work on the dual SIM version XQ-AU52?

ig2205 said:
Will it work on the dual SIM version XQ-AU52?
Click to expand...
Click to collapse
Of course.

i wish we can have it for our xperia 5ii lol

Any way of upgrading to this (ie dirty flashing) from your LineageOS 17.1 version? Or is it necessary to wipe and reinstall stock Android 10 first?

dreDREb13 said:
Any way of upgrading to this (ie dirty flashing) from your LineageOS 17.1 version? Or is it necessary to wipe and reinstall stock Android 10 first?
Click to expand...
Click to collapse
Flash directly, if you don't meet any issue, there is no need to wipe the data.
flyl0 said:
i wish we can have it for our xperia 5ii lol
Click to expand...
Click to collapse
Coming.

Sjll said:
Flash directly, if you don't meet any issue, there is no need to wipe the data.
Coming.
Click to expand...
Click to collapse
It would be even better Resurrection Remix
But I'm glad LOS 18.1 is coming, can't wait to try it!

Sjll said:
Flash directly, if you don't meet any issue, there is no need to wipe the data.
Click to expand...
Click to collapse
Sweet. This is great work, thanks so much!
Does the flashing have to be done through fastboot via the method described for initial install, or can adb sideload be used to install the zip package via recovery as an update instead?

erasing 'metadata'...
FAILED (remote: Erasing is not allowed for partition)
...
sending sparse 'system' 1/2
OKAY [ 21.700s]
writing 'system' 1/2...
FAILED (remote: No such partition.)
I have that every time. What to do in fastbootd mode?

dreDREb13 said:
Sweet. This is great work, thanks so much!
Does the flashing have to be done through fastboot via the method described for initial install, or can adb sideload be used to install the zip package via recovery as an update instead?
Click to expand...
Click to collapse
OTA package will remove vendor partition, I will provide OTA package until building vendor image Then we will go LineageOS official.
ig2205 said:
erasing 'metadata'...
FAILED (remote: Erasing is not allowed for partition)
...
sending sparse 'system' 1/2
OKAY [ 21.700s]
writing 'system' 1/2...
FAILED (remote: No such partition.)
I have that every time. What to do in fastbootd mode?
Click to expand...
Click to collapse
You should be in fastboot mode and not fastbootd mode,
If you are really in fastbootd mode and not work, try fastbootd mode in official recovery image.

Will this rom be rebased on the Android 11 stock ROM sources once we have them?

You should be in fastboot mode and not fastbootd mode,
If you are really in fastbootd mode and not work, try fastbootd mode in official recovery image.
Now it looks like this and I don't know whether to continue doing something?

KriiXOne said:
Will this rom be rebased on the Android 11 stock ROM sources once we have them?
Click to expand...
Click to collapse
Maybe, stock 10 blobs works fine on LineageOS 18.1. A
ig2205 said:
You should be in fastboot mode and not fastbootd mode,
If you are really in fastbootd mode and not work, try fastbootd mode in official recovery image.
Now it looks like this and I don't know whether to continue doing something?
Click to expand...
Click to collapse
LineageOS or stock Recovery?
If LineageOS Rec is broken, try stock rec plz.
BTW, also use latest adb fastboot tools from google.
FastbootD driver is also necessary.

Just wondering, how's the camera performance (in terms of start-up and focus speeds) in these custom ROM's compared to stock? Getting rather annoyed by the performance of the stock ROM / camera app.

Sjll said:
Maybe, stock 10 blobs works fine on LineageOS 18.1. A
LineageOS or stock Recovery?
If LineageOS Rec is broken, try stock rec plz.
BTW, also use latest adb fastboot tools from google.
FastbootD driver is also necessary.
Click to expand...
Click to collapse
The problem is with stock recovery.
I installed a new system, drivers, reinstalled programs, changed usb sockets and nothing. I have no idea anymore.

ig2205 said:
The problem is with stock recovery.
I installed a new system, drivers, reinstalled programs, changed usb sockets and nothing. I have no idea anymore.
Click to expand...
Click to collapse
Run
Code:
fastboot getvar all
Post the result here plz.

Sjll said:
Run
Code:
fastboot getvar all
Post the result here plz.
Click to expand...
Click to collapse
Is that the point?

So I installed and everything booted up fine, but I hit a couple snags.
One, it looks like Open GApps hasn't officially released Android 11.0 builds yet, so I had to find test versions through their sourceforge to run.
Two, upon booting I'm having trouble using a third party launcher (KISS Launcher) with gesture navigation. For some reason it won't recognize the multitasking/return to home feature along the bottom, though the side gestures work fine. Not sure if that's something to do with the test builds of GApps or not. I made sure all gestures were turned off to check if maybe it's a conflict but it still didn't work. And the launcher ran just fine on my 17.1 install, so not sure what the issue is.
Three, my wallpaper that I have set to the correct resolution of the phone is now zoomed in slightly. It looks like this is a feature of the new notification shade, as when I pull it down it zooms out my wallpaper to the correct size. However, I can't seem to find a way of turning this feature off or getting my wallpaper to fit properly.
EDIT: I rebooted again after first boot and my issues with the third party launcher and gesture navigation went away. After looking into it more it looks like that wallpaper zoom feature is apparently baked in to Android 11, so no way of disabling that at the moment. Hopefully there's a change that can come in to remove that feature...
All looks good otherwise and this is turning out great!

[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!!!