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][LineageOS15.1][Oreo][Android 8.1.0] NightOwl Beta3

{
"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"
}
This is the NightOwl LineageOS 15.1 Android 8.1.0 Beta3 built from source for the Galaxy Note 1 GT-N7000/GT-N7000B
This LineageOS 15.1 based ROM is in Beta state and not ready for all day usage.
The main functions are working but there will be bugs!
Code:
Use my Roms only if you are sure about the risks of flashing custom Roms/Kernel to your device. I'm not responsible for any damage caused by using one of my files.
NOTE:
Because of the Rom Size and the ART runtime since Android 5 all Apps will need more space. If you want to install the rom together with Gapps you need to repartition your internal storage.
You can find more informations in the Howto Install section.
Changes:
Beta3:
* Updated los sources
* August security patches
* Fix mic-gain when multiple input streams are used
* Go settings without lowram flag set
* Acelerometer fixed
Older Changes:
Alpha2:
* Updated los sources
* April security patches
* First start wizard is working with installed gapps
* Youtube is working
* Added power profile settings
* Video playback mostly working
* Whatsapp videocalls working
Alpha1:
* First public release
Known Bugs Beta3:
* Installed gapps will cause a battery drain about 10%/h in standby
A part of the battery drain is caused by Wifi scanning which keeps Wifi always active.
Turn Wi-Fi Scanning off here: Settings -> Security & Privacy -> Location -> Scanning ->Wi-Fi scanning
This will reduce the battery drain but still something other (Ril?) is draining the battery too.
* If you get asked to instal/fix root/supersu in the recovery select no!
* Usb dialog not working. you can enable mtp mode in the developer settings
* Adoptable storage is not working (don't format your sdcard as internal!)
* Because of the rom size you need to repartition your /system and /data partition if you want to install gapps
How to Install:
If you are running a custom Kitkat(4.4) or newer Rom:
1. Copy Rom + Google Apps + recovery-twrp3.1.0-build2-isorec-n7000.zip + lanchon-repit-20170115-system=1536M+keep-data=6G+keep-sdcard=max+keep-preload=same+keep-n7000.zip to your external sdcard
2. Boot into recovery
3. Factory Reset + Format the /system partition
4. Flash the Rom zip file (without gapps in this step)
5. Flash recovery-twrp3.1.0-build2-isorec-n7000.zip
6. Reboot the recovery to enter the twrp isorec recovery
7. Flash lanchon-repit-20170115-system=1536M+keep-data=6G+keep-sdcard=max+keep-preload=same+keep-n7000.zip (Read the instructions in How to repartition your device!)
8. Flash gapps
9. Reboot
The steps to install it from an stock samsung rom are:
If you have already an samsung 4.1.x running you can skip step 1
1.flash N7000ZSLR1_N7000OZSLR1_BRI (or any other other 4.1.2) stock rom using odin
2.Copy Rom + Google Apps + recovery-twrp3.1.0-build2-isorec-n7000.zip + lanchon-repit-20170115-system=1536M+keep-data=6G+keep-sdcard=max+keep-preload=same+keep-n7000.zip to your external sdcard
3.flash PhilZ-cwm6-XXLT6-XSA-5.06.1.tar.md5 (https://www.androidfilehost.com/?fid=745425885120702299) to get cwm recovery with odin
4. boot into recovery
5. flash this kernel http://forum.xda-developers.com/devdb/project/dl/?id=20863 to get an updated recovery
(this step will make your old rom unbootable stuck in the n7000 screen but you can boot into recovery with press and hold "home" and "volume+" buttons and power on your phone)
6. you need to reboot! your device now to recovery
7. you are now in the updated recovery and you need to do a factory reset + format the /system partition
8. Flash the Rom zip file (without gapps in this step)
9. Flash recovery-twrp3.1.0-build2-isorec-n7000.zip
10. Reboot the recovery to enter the twrp isorec recovery
11. Flash lanchon-repit-20170115-system=1536M+keep-data=6G+keep-sdcard=max+keep-preload=same+keep-n7000.zip (Read the instructions in How to repartition your device!)
12. Flash gapps
13. Reboot
Updating If you are running an earlier NightOwl LineageOS 15.1 alpha version:
1. Copy Rom + recovery-twrp3.1.0-build2-isorec-n7000.zip + lanchon-repit-20170115-system=1536M+keep-data=6G+keep-sdcard=max+keep-preload=same+keep-n7000.zip to your external sdcard
2. Boot into recovery
3. Flash recovery-twrp3.1.0-build2-isorec-n7000.zip
4. Reboot the recovery to enter the twrp isorec recovery
5. Flash lanchon-repit-20170115-system=1536M+keep-data=6G+keep-sdcard=max+keep-preload=same+keep-n7000.zip (Read the instructions in How to repartition your device!)
6. Flash the Rom zip file
7. wipe dalvik cache
8. Reboot
How to repartition your device:
Because of partition size limitations you need to repartition your device to fit the rom together with gapps on the /system partition.
My example repit file (in the Downlodas section) will also enlarge the /data partition because the default size is to small for android 5+ if you want to install some apps.
Lanchon has made a tool which makes it possible to repartition your device in the recovery without loosing your data
https://github.com/Lanchon/REPIT
You need to have a working TWRP Recovery (CWM and Philz will not work)!
Make sure that you have at least 5GB free space on your internal sdcard0 before you start!
Make sure that your battery is charged and connect your device to the charger because repartitioning can take some time!
Installing the repit zip from the sdcard will fail the first time (because the sdcard is in use and can't unmounted) but the file gets copied to /tmp in this step.
After this select the repit zip to install from /tmp again and it should work
How to enable root:
1. Go to Settings-System-About phone and tip 7 times on Build number to enable the Developer options
2. Go to Settings-Developer options-Root access and set it to Apps and ADB
Don't install supersu (it will give you a boot loop!)
Downloads:
LineageOS 15.1 Beta3:
https://www.androidfilehost.com/?fid=3700668719832239373
Google Apps for lineage 15.1 (Use only after you have repartitioned your device! Suggested versions: micro, nano or pico):
http://opengapps.org/?arch=arm&api=8.1&variant=nano
Recovery flashable TWRP 3.1.0-0 build2 recovery (IsoRec)
https://www.androidfilehost.com/?fid=11050483647474832011
lanchon-repit-20170115-system=1536M+keep-data=6G+keep-sdcard=max+keep-preload=same+keep-n7000.zip
https://www.androidfilehost.com/?fid=11050483647474832009
Older Versions:
LineageOS 15.1 Beta2:
https://www.androidfilehost.com/?fid=11050483647474833224
LineageOS 15.1 Beta1:
https://www.androidfilehost.com/?fid=11050483647474832010
LineageOS 15.1 Alpha2:
https://forum.xda-developers.com/devdb/project/dl/?id=29271
LineageOS 15.1 Alpha1:
https://forum.xda-developers.com/devdb/project/dl/?id=29024
A big THX to:
LineageOS Team
rINanDO (Many parts in this Rom are based on his work for the i9100)
forkbomb444
XDA:DevDB Information
[ROM][LineageOS15.1][Oreo][Android 8.1.0] NightOwl Beta3, ROM for the Samsung Galaxy Note GT-N7000
Contributors
bauner
Source Code: https://github.com/bauner
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Kitkat(4.4) or newer compatible custom recovery
Based On: LineageOS
Version Information
Status: No Longer Updated
Current Beta Version: Beta3
Beta Release Date: 2018-08-12
Created 2018-03-30
Last Updated 2019-03-07

Awesome news incredible history. Many thanks Dev @bauner
Sent from my Redmi 4X using XDA Labs

Thanks a lot for the Rom @bauner
Clean flashed it on my GT-N7000 now and so far couldn't find any bugs that aren't known yet
Since it's my 2nd Phone I can't test anything RIL related but I'll try to check for any other bugs.
Do you know if we'll ever be able to install Magisk to our Note / What's the reason that we can't install it? I've read something about our Devices Ramdisk being different.

Dear bauner
Wow! Thank you so much!
Sincerely

Oh my!!! @bauner you're an absolute legend! Can't thank you enough for giving us the opportunity to try out the latest and greatest version of Android on our beloved Galaxy note!
I'll give it a try in a few days. I'm so excited. Thanks so much.
Cheers ?

whew my eyes...
btw first time trying f2fs installation on n7000, and it booted (unexpected as I see most of n7000 rom thread wrote nothing on f2fs support) gonna try it out
phone seems couldn't power on while charging with this kernel. Nice charging screen tho, love it
Thanks Bauner
EDIT: It seems won't boot (stuck at the charging screen) only if the battery is too low.
EDIT 2 : I don't know whether this is because of f2fs or what, I can feel that it performs much better than nougat (i mean on first boot of both rom)

Kiddos like screenies ~ :3
The lines in screenshot only applies to screenshot file - see statement by OP in first post

Thank you Bauner!

Thank you alot Bauner❤❤❤

Bugs I've seen so far since yesterday
•Youtube video playback broken (i can watch youtube on gello)
•Split screen
•occassional signal loss which requires reboot to be back again
•camera picture settings
•no signal sometimes whenwver i reboot, i have to reboot again for the aignal to come back

haveyouseenthisboi said:
Bugs I've seen so far since yesterday
•Youtube video playback broken (i can watch youtube on gello)
•Split screen
•occassional signal loss which requires reboot to be back again
•camera picture settings
•no signal sometimes whenwver i reboot, i have to reboot again for the aignal to come back
Click to expand...
Click to collapse
The youtube video problem is known
The rom is a android go build which does not support split screen
Can you reproduce the signal loss or will it happen randomly?
Which camera setting will not work for you?

Can't test it in this level (Daily phone and all)
just wanted to say thank you Bauner for supporting Note!

haveyouseenthisboi said:
Bugs I've seen so far since yesterday
•Split screen
Click to expand...
Click to collapse
Split screen works perfectly, but to use split scrren, you need to set the low ram flag in build.prop to false
*You will notice a slight change in ui such as recents and screen off animation

Oh i found out that it was not really a signal loss but a random no simcard. It is random everytime i reboot the phone. I have to reboot again for the system to "detect" the sim again

haveyouseenthisboi said:
Oh i found out that it was not really a signal loss but a random no simcard. It is random everytime i reboot the phone. I have to reboot again for the system to "detect" the sim again
Click to expand...
Click to collapse
Welp I also face this problem since months ago (during last year, running rros nougat)... Tried several time of clean install of nougat but didn't help, even with a different sim. Hopefully as for now the issue has not come back again for me on los15.
I tot I'm the only one facing this issue ._. as I'm expecting this is hardware related problem. I'm highly confident this is not software related. My sis and my mom they both using n7000 as daily driver with rros nougat running since clean install during earlier last year, and they didn't hv this/any problem until now. (My mom make many phone calls everyday. ) Guess should be due to the worsening condition of the modem chip, maybe is because of the heat released from CPU is too much?

Interestingly I only got the no sim bug on bauner's cm12 and los15.1

Seems like it was unable to boot sometimes, when the phone is charging, even when it already charged full. Best to remove charger and boot. Else sometimes it will stuck at charging screen, then will need to reboot by long pressing the power button.
Sometimes shutdown or reboot, it will like stuck for a moment before reset.(should be kernel related?) Like if in TWRP, if press reboot, it will stuck there for around 5 seconds or more, in my case 15 seconds longest, before it really reset.
There's no thermal sensors detected. Can't see the temperature of system.
Until today still smooth like hell. No idea why haha I'm using lowram flag = false.
Surprisingly there aren't any MTP Host related FC Dialog anymore 0.0 I will try out MTP soon.
Overall, what a legend! Thanks OP! It seems like it is a joke to tell people that note 1 is running Oreo :laugh:
But not.

Is there any way to get trusted face without mano gapps

ritik jaiswal said:
Wanted to flash nano gapps
In Pico no voice assistant, no voice unlock, no face unlock
Neither the Google app
Is there any way
Click to expand...
Click to collapse
With the default /system partition size you will not have enough free space to install nano gapps.
To fit bigger gapps as pico with lineage 15.1 you need to repartition the /system partition too.
https://forum.xda-developers.com/showpost.php?p=66341193&postcount=2071

bauner said:
With the default /system partition size you will not have enough free space to install nano gapps.
To fit bigger gapps as pico with lineage 15.1 you need to repartition the /system partition too.
https://forum.xda-developers.com/showpost.php?p=66341193&postcount=2071
Click to expand...
Click to collapse
Thank you for this.
Anyways, my internal storage shows as corrupted in 8.1.0. Not able to access it. Did I miss something?
Apart from this, everything is working great! Thank you once again for keeping this phone alive @bauner.

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