Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* 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 ROM
* 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.
*
*/
Red Wolf Recovery is custom recovery based on TWRP source code however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.
Based on TWRP version: 3.2.1
For devices: Natrium
Authors build: yshalsager
Developers: @ATG Droid & @Dadi11
Thanks: z31s1g (for the base of his theme), Ray Li (For his useful advice in the beginnings), osm0sis (for his image scripts), etc.
Features:
Code:
[B]Translated to EN & CZ [/B]
- Password protection
- Flashlight
- MIUI Incremental OTA Support
- Built-in latest Magisk, SuperSU & AromaFM
- Support two screenshot GUI actions - Power+VolDown to save screenshot in to the internal storage &
Power+VolUp to save screenshot in to the external storage (Will be automatically saved in to the internal in case
that external storage doesn't exist).
- Support automatic reboot after the restore process
- Recovery can automatically modify some props in the ROM directly during the installation
- Some built-in scripts from community
- Tap to wake support
- Advanced deactivation of the stock recovery
- Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- Support "set on boot" settings.
[B]* Changes for security reasons *[/B]
- ADB isn't starting automatically at the start of the recovery. You have to activate it in recovery
- MTP isn't starting until user enter correct password
- Deactivated TWRP theme engine
[/URL]
Some differences to the official version:
Code:
[COLOR="red"]- get out of here if you are pirating apps. this recovery is not for you[/COLOR]
- always up-to-date with the latest TWRP changes
- compiled on omnirom-7.1 source
- kernel compiled inline with the recovery
- There isn't bug with reboot from recovery to recovery
- more languages
- other improvements from Features and Changelog lists
Changelog:
Code:
RedWolf-V3.2_026
- This is just a quick bug fix release for MIUI users. So is highly recommend to update to this build if you are using MIUI.
RedWolf-V3.2_025
- Fixed crash of the recovery while running OTA_RES.. (So MIUI OTA is now working again)
- General bug fixes and improvements
- Fixed bug with MIUI Updater app showing error that installation failed after installation of full ROM
- Deactivation process is now called only when it's really needed
- Updated kernel
RedWolf-V3.2_024
- Fixed GUI color glitch while starting Aroma Installer update-binary
- Optimized pigz runtime process
- Updated recovery base to the AOSP 8.1.0 & TWRP 3.2.1
- Highly improved signature verification for Incremental packages so now we can be really sure if the package is compatible with the ROM.
- Introduced a file based backup/restore engine. Expect it to be improved with the next builds...
- Improved security related to the password protection
- Fixed loading of the AromaFM config file
- System survival process for Incremental packages is now set by default
- Code optimizations
- Removed the dumwolf process
- Added signature check for incremental OTA survival so we won't be unnecessarily creating a new one if it's signed under the same access key
- Magisk updated to the version 15.1
- Added Indonesian language
- Fixed issues with Chinese characters...
- Governor which is changed by the action in the recovery GUI is now automatically set for all cores instead of only four.
RedWolf-V3.2_023
- Updated recovery base to the TWRP version 3.2.0
- Fixed issue with recovery sometimes showing "NO-OS" page even when OS is installed
- Merged: Fstab V2, minui updates, Keymaster 3.0 support, ADB updates, fixes related to the compiling errors...
- Added patch against the pirating applications
RedWolf-V3.1_022
- Small improvements in the installation process
- Recovery will now automatically warn the user in case that user selected to install the zip which contain a bootloader
- You can now wipe installed substratum overlays directly from the "advanced wipe" section
RedWolf-V3.1_021
- Automatically return install error if there is any issue with Incremental OTA Survival
- Added option to also backup system partition for Incremental OTA Survival (It's not always needed, but just in case it's better to backup it.)
- Added support for the compatibility verification of the Incremental Package
- Rebuilded & improved installation process
- Fixed starting process not being disabled correctly in case that we are running ORS
- Translation update
- Added support for devices with 2GB RAM or less... (Check installation process of this build for more info)
- Added checkbox for activation/deactivation of the boot check (Disable only if you really need to).
- Fixed booting problems on some custom ROMs which don't have gzip compressed ramdisk
- Removed bookmark feature
- Added ability to unzip files using the stock filemanager.
- Added search selection for the stock filemanager.
- Fixed 'No OS' on system image restore after wipe
- Merged some latest commits from TWRP gerrit
RedWolf-V3.1_020
- Fixed flashing of the images in the previous 018 build
- Added back support for unpacking of the LZ4 compressed ramdisk
- Fixed bookmark feature
RedWolf-V3.1_019
- Disable TWRP installation directly during the first boot
- Default time zone was set to CEST
- Use military time as default time.
- Support of the custom themes was completely removed from the installation process
- Few fixes & improvements in the strings.
- Default value of the RedWolf specific vibrations was slightly increased
- Improved saving/loading of the AromaFM config file.
- User can now select if recovery should disable stock recovery when system is mounted as read-only.
- Default color of the recovery was set to red.
- Fixed automatic reboot if the installation process was unsuccessful
- Center time in the statusbar as default
- Show CPU temp in statusbar as default
- Added "Red Wolf No-OS search engine". Enable this if you are sometimes getting No-OS installed error even when OS is installed.
- Added back support for extra languages
- Added support for Talian language
- Updated Chinese (simplified) translation of the AromaFM by LiuNian and Pzqqt
- Fixed displaying of the extra languages
- Improved mounting of the partitions during the applying of set on boot values
- Fixes with "stuck at unmounting"
- Highly improved speed of the recovery while setting up a new password, changing accent color or setting a new splash screen
- Magisk updated to the V14.3
- Recovery now won't allow the user to enter special characters while entering the password (Causing issues...)
- Few improvements with the Android Oreo installation
- Updated kernel
- Added ability to select if recovery should automatically disable forced encryption in the ROM
- Recovery will now automatically rename scripts in the system if the "Aggresive stock recovery deactivation" is enabled
- Added ability to select if recovery should automatically enable/disable USB Debugging in the ROM
- Removed some useless files to save the space
- Added support for saving the set on boot values also during the automatic reboot
- Redesigned flashlight icon
- Recovery now won't allow the user to enter the space in to the backup name
- Improved support of the last status checking of the MIUI ROM
- Recovery now won't show any button after the cancelled reboot action untill the sleep action won't be running anymore
- You can now select if recovery should also automaticaly reboot after the successfuly finished restore process
- Recovery will now hide the automatic backup feature if the system partition is mounted as read-only
- Updated recovery base to the AOSP 8.0.0
- Updated image drivers
- Added ability to select if recovery should automatically enable/disable "ro.adb.secure" property in the ROM
- Recovery will now automatically disable starting of the flash_recovery service if the "Aggresive stock recovery deactivation" is enabled (this process is also compatible with the backup of the init.rc by Magisk or SuperSU).
- Added new section called "Special Actions" in to the advanced menu
- Updated & optimized flashlight drivers
- Added ability to select if recovery should automatically enable/disable "ro.secure" property in the ROM
- Added ability to select if recovery should automatically enable/disable "ro.allow.mock.location" property in the ROM
- Highly improved support of the Incremental Package installation, detection etc.
- Updated Chinese (simplified) translation of the recovery by LiuNian and Pzqqt
- Added support for the complete deactivation of the secure boot in the MIUI based ROMs
- ADB is now automatically starting as root
- Added support for the RedWolf update package
- Default theme of the AromaFM was changed to holo black with the sense icons and automount turned on
- SuperSU Updated to the 2.82 SR5
- Updated ramdisk cleaner & added support for more kernels (thanks to @MOVZX's kernel installation scripts...)
- Small fixes with the /WOLF folder in the PartitionManager
- Highly improved speed of the reboot
- 'Deactivation process' is now automatically called during the installation instead of the reboot
- Imroved deactivation of the leds after the installation / backup / restore process.
- Fixed bug with recovery showing on the governor page that the active governor is "Interactive" even when user selected performance/powersave mode.
- Removed some GUI messages while we are installing built-in zips.
- And many other things which i don't remember anymore...
RedWolf-V3.1_018
- Fixed bugs with MIUI OTA Support to make sure that it will work even with newest beta builds of the MIUI
- Updated Polish translation by Daviteusz
- Fixed bugs in the Polish strings & edited the scale of the Russian strings
- Recovery will be now more aggressive if the process of the stock recovery doesn't want to be disconnected (Sometimes happen on some MIUI ROMs).
- Added detection of the installed ROM
RedWolf-V3.1_017
- Magisk updated to the V13.6
- SuperSU updated to the 2.82 SR3
- Added ability to automatically flash SuperSU config before the SuperSU - https://forum.xda-developers.com/apps/supersu/2017-08-13-supersu-config-t3655754
- Deactivated hw keys
- Added some missing back buttons
- Attempted to fix encryption
- Attempted to fix MIUI OTA installation - needs testing
- Removed extra languages (were not displayed properly)
- Small update which fixed deactivation of the dm-verity & forced encryption. Now you really don't have to flash the lazyflasher everytime when you are installing the MIUI ROM.
RedWolf-V3.1_016
- Fixed feature "Backup wifi, bluetooth & hosts" not to work if the user wiped the data partition using the "factory reset".
- TWRP source code was updated to the Aug 15, 2017
- Fixed recovery remembering the wipe list after setting a new gui page.
- Improvements with the mounting of the partitions during the boot
- Fixed led drivers on mido
- Fixed ability to set custom backup folder name & ADB ID
RedWolf-V3.1_015
- Updated with the latest TWRP changes
- Added flashlight switch on mido
RedWolf-V3.1_014
- Fixed recovery not deactivating the dm-verity, forced encryption, & stock recovery if the OS was detected as not installed. This issue was often happening on some MIUI ROMs.
- Improvements with the OTA update system of the MIUI.
- Fixed wrong reboot for some users.
- Added support for automatic deactivation of the dm-verity, forced encryption & stock recovery after finishing the OpenRecoveryScript process.
- Fixed recovery not deactivating the dm-verity & forced encryption during the automatic reboot after the finished installation.
- Better explain the current situation if the OS was detected as not installed.
- osm0sis's scripts "unpackbootimg" & "mkbootimg" can now be easily called from the script or terminal
- Improved the speed of the reboot
- Updated the community script "Fingerprint scanner fix" by Magua. It's now working again!
- Added NTFS & exFAT support
- Added more languages and updated Polish RedWolf translation by @Daviteusz
- Added FGO patch - https://goo.gl/GBkhMN
RedWolf-V3.1_013
- Slightly improved deactivation of the stock recovery during reboot after the zip installation
- Added ability to flash boot logo in the recovery
- Fixed firmware restoring issues
RedWolf-V3.1_012
- added F2FS support for mido
- added Night Mode (kcal) support for mido
RedWolf-V3.1_011
- Updated Polish translation by @Daviteusz
- Added few missing strings from the latest TWRP source
[Red Wolf] Install TWRP and root your device without breaking incremental OTA's!
Known Bugs:
- Flashlight is not working.
Downloads:
Latest build for Xiaomi Mi 5s Plus (natrium)
RedWolf-Unofficial-natrium.img
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery. But your device can be still reinstalled using fastboot or Miflash.
XDA:DevDB Information
[ABANDONED][NATRIUM] Red Wolf Recovery Project, Tool/Utility for the Xiaomi Mi 5s Plus
Contributors
yshalsager, ATG Droid, Dadi11
Source Code: https://github.com/RedWolfRecovery
Version Information
Status: Abandoned
Created 2018-02-21
Last Updated 2018-02-24
Sources:
Recovery: https://github.com/RedWolfRecovery/rw_recovery
Device tree: https://github.com/RedWolfRecovery-Xiaomi-Devices/android_device_xiaomi_natrium
Screenshots: Here
Looks good! Password protection is a feature I've wanted for a long time. It's a shame twrp themes aren't compatible, though
After installing this recovery on device with rr6, when trying reboot to recovery, it's showing start screen (with logo) and reboots to system.
QuiseShampe said:
After installing this recovery on device with rr6, when trying reboot to recovery, it's showing start screen (with logo) and reboots to system.
Click to expand...
Click to collapse
New build:
Please test
https://www.androidfilehost.com/?fid=962187416754462278
QuiseShampe said:
After installing this recovery on device with rr6, when trying reboot to recovery, it's showing start screen (with logo) and reboots to system.
Click to expand...
Click to collapse
I have the same problem. I also have the RR 6, and when trying to restart in Recovery, the Red Wolf appears but only briefly, and restarts the system. Says installation using the application Official TWRP. I do not know how to install otherwise because I do not know which option to choose when installing the image.Thank you very much for your work, I have long wanted to put a password on TWRP.
yshalsager said:
New build:
Please test
https://www.androidfilehost.com/?fid=962187416754462278
Click to expand...
Click to collapse
No more splash screen. Black screen. No boot to recovery. You're using 3.2.1.0? If yes, it's will not work properly. Only 3.2.1.1 working properly with latest 8.1 ROMs.
QuiseShampe said:
No more splash screen. Black screen. No boot to recovery. You're using 3.2.1.0? If yes, it's will not work properly. Only 3.2.1.1 working properly with latest 8.1 ROMs.
Click to expand...
Click to collapse
I used official twrp tree
If you have stable tree link, please give me and I'll make another build.
yshalsager said:
New build:
Please test
https://www.androidfilehost.com/?fid=962187416754462278
Click to expand...
Click to collapse
New build is booting but not working correctly.
If I boot to recovery (power and vol+) the recovery is loading, but the touch is not working at all.
If I then reboot to recovery again (with power and vol+) the touch is working.
No idea why it is not working on first try. But I have tried a couple of times so it seems to be not a one time issue.
If you need further information feel free to ask
mue91 said:
New build is booting but not working correctly.
If I boot to recovery (power and vol+) the recovery is loading, but the touch is not working at all.
If I then reboot to recovery again (with power and vol+) the touch is working.
No idea why it is not working on first try. But I have tried a couple of times so it seems to be not a one time issue.
If you need further information feel free to ask
Click to expand...
Click to collapse
Same thing with me! Just load the Wolf network image and reboot the system. I really liked it, but it's a pity I can not use it yet.
What's the matter of Recovery password, if FastBoot is not password-locked?
ras4lenenka said:
What's the matter of Recovery password, if FastBoot is not password-locked?
Click to expand...
Click to collapse
Exactly.
Sent from my Xiaomi MI 5s Plus using XDA Labs
New build:
https://www.androidfilehost.com/?fid=818070582850494669 @mue91 Can you test?
Okay, even I don't have a device to test, I got many requests to make this recovery and I did, but unfortunately, It can't boot well!
Basically, It MUST work as I used TWRP official trees. But It seems like there's something wrong.
So, this project is ABANDONED now.
Sources are in this post if anyone decided to continue
Thread Closed!
Lineage-16.0
SM-T580/585 (32-Bit)
lineage-16.0-20181008-UNOFFICIAL-gtaxlwifi.zip
lineage-16.0-20181008-UNOFFICIAL-gtaxllte.zip
SM-T580/585 (64-Bit)
64_lineage-16.0-20181008-UNOFFICIAL-gtaxlwifi.zip
64_lineage-16.0-20181008-UNOFFICIAL-gtaxllte.zip
Known issues:
- AdvancedDisplay (Samsung) is not working and has been taken out.
- Pls use latest Magisk version (v17.x) - on earlier versions you may get bootloop. (maybe it's booting twice - don't panic)
Camera:
- Google Camera app is not working correctly - and is not tested ! -> Pls do not install yet !
- Normally if you install Google Camera app via gapps you remove the built-in camera app - pls take care yourself !
- The Lineage built-in Camera app works fine - except for rear camera video recoding. (720p)
- OpenCamera app works fine too - also no rear camera video recoding.
- Footej Camera app works fine too - rear camera video recoding is working in this app too !
Changes:
lineage-16.0-20181008
- Google security fixes -> October 2018
- Fix for Doze
- fix for KeyDisabler
- Latest kernel security updates -> thanks to @cschsz
lineage-16.0-20180926
- Fix for Bluetooth
- Change for camera
- Fix for some 32-Bit apps
lineage-16.0-20180924
- Added NavBar
- Added new Android Pie gestures for NavBar (settings->system->gestures)
- Removed SELINUX warning at boot (red warning at left top corner)
- minor changes
lineage-16.0-20180923
- initial release
Installation:
1. Boot into TWRP
2. Wipe system, cache and dalvik and data
3. Install ROM.zip
4. install opengapps
5. install Magisk.zip
6. Reboot into system
Upgrade:
1. Boot into TWRP
2. Install ROM.zip
3. Wipe cache and dalvik
4. Reboot into system
- Please install Magisk.zip yourself.
- If you face any strange issues, pls do a factory reset via TWRP first.
DOWNLOAD:
https://drive.google.com/drive/folders/1uZ4DZ1wN8dpY-AnJhCirr6RsL02PVMrE
TWRP:
Based on OMNI sources .. https://forum.xda-developers.com/showpost.php?p=76564831&postcount=213
https://forum.xda-developers.com/showpost.php?p=75483069&postcount=237
https://forum.xda-developers.com/showpost.php?p=77000830&postcount=401
https://forum.xda-developers.com/showpost.php?p=77340691&postcount=433
twrp-3.2.3-0-gtaxlwifi-OMNI.img
twrp-3.2.3-0-gtaxllte-OMNI.img
SOURCES:
https://github.com/followmsi/manifests/tree/gtaxl-lineage-16.0
Big thanks to @Valera1978 for all his work !
Only the SM-T580 versions have been tested .. tested with Magisk 17.2 and Opengapps.
Enjoy
XDA:DevDB Information
[ROM][SM-T580][SM-T585][UNOFFICIAL][Lineage-16.0], ROM for all devices (see above for details)
Contributors
followmsi
ROM OS Version: 9.x Pie
Version Information
Status: Stable
Created 2018-10-08
Last Updated 2018-10-08
A new fresh thread / project for Lineage-16.0 .. and I did mess up XDA
SM-T580/585 (32-Bit)
lineage-16.0-20181008-UNOFFICIAL-gtaxlwifi.zip
lineage-16.0-20181008-UNOFFICIAL-gtaxllte.zip
SM-T580/585 (64-Bit)
64_lineage-16.0-20181008-UNOFFICIAL-gtaxlwifi.zip
64_lineage-16.0-20181008-UNOFFICIAL-gtaxllte.zip
Changes:
lineage-16.0-20181008
- Google security fixes -> October 2018
- Fix for Doze
- fix for KeyDisabler
- Latest kernel security updates -> thanks to @cschsz
Enjoy
{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS) we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q with a base of AOSP repositories and some additions from LineageOS for device specific repositories.
If there are any bugs, either we will sort them out, if it concerns our code base. This ROM isn't LineageOS supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
GZOSP team
LineageOS & CM (R.I.P.) team
@maxwen and the rest of the OmniRom team
DU team
Resurrection Remix team
AOSiP team
Community
...
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 15.0
AICP 15 rosy - Unofficial
Google Apps
- Open GApps
Only Pico/Nano are the recommended Open GApps packages
Please check Open GApps Package Comparison for full details
- Flame GApps
Only Basic is the recommended Flame GApps package
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Google Apps:
(link the best one for your device, there are several variants out there right now, nano/micro GApps from opengapps.org is almost always a good choice though)
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP. Custom ROMs modify the framework a lot, so Xposed can cause a ton of issues on custom ROMs. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. Information about Xposed, EdXposed or Riru Core can be obtained from the XPosed General forums .
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is the usual behaviour on flashing a new official build by (or using) the build-in updater service.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution and reboot. Or just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash and reboot afterwards.
Using the ROM:
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Q. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, and Data (you might need to format the data partition!).
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work), GApps are already included for some a/b devices.
6. Reboot and set up your device, enable developer settings and in them OEM unlock/Advanced reboot/USB tethering.
7. Reboot back into TWRP recovery.
8. Flash the root solution of your choice (optional).
9. Reboot your device.
The procedure may vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 20.3 don't usually need to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
TWRP recovery is needed to be able to flash using the built-in OTA app.
Please make sure that you are on the latest TWRP recovery, keep in mind that this could also be an unofficial version!
On encrypted devices you will have to enter your PIN/password in TWRP before the process starts.
If you want to contribute to AICP, or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Contributors:
(mention all the devs who have contributed to your device tree, kernel, vendor, etc,
only mention the main ones though, probably the top four or so, otherwise this list will be a mile long xD)
You want to see a "normal" night at the "DEV office", click here!!
Flashing Instructions:
You need to flash manually via recovery because OTA update doesn't seem to work with twrp/orangefox.
Clean Flash
• Downloaded the new rom build to your phone using the direct link or XenonOTA app
• Reboot to recovery
• Take full backup in twrp
• Wipe (system, vendor, data, cache, dalvik)
• Flash the new build
• Flash GApps package
• Reboot - The first boot can take up to 5 minutes
Dirty Flash
• Downloaded the new rom build to your phone using direct link or updater app
• Disable Magisk modules if you're using any
• Reboot to recovery
• Take full backup in twrp
• Wipe (system, vendor, cache, dalvik)
• Flash the new build
• Flash GApps package
• Reboot
What's working:
• Audio
• Bluetooth
• Call recording
• Camera/Camcorder/Flash
• Charging/Offline-charging
• Cast
• Doze/Deep-sleep
• Fingerprint
• FM radio
• Google voice assistant
• GPS - With location services
• Hotspot/Tethering
• IR
• Sensors
• Torch
• RIL (Calls, SMS, Data)
• VoLTE
• Wi-Fi
SELinux Status:
• Enforcing [without neverallows]
Known issues:
• GPS - Without location services
Untested:
• Device Encryption
Notes:
• ROM built with doge kernel, so report bugs only if you're using doge kernel
• Join, Telegram Group for support
Necessary config changes for gcam:
1) Video recording resolution should be set to 1080/720p
2) HDR mode should be turned off for selfie cam
Device Source:
• Kernel Source
• Device Source
• Vendor Source
XDA:DevDB Information
AICP, ROM for the Xiaomi Redmi 5
Contributors
xDoge
Source Code: https://github.com/AICP/
ROM OS Version: Android 10
ROM Kernel: Linux 3.18.x
ROM Firmware Required: Oreo
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 15
Created 2020-05-17
Last Updated 2020-09-21
ChangeLog
20200921
Code:
[COLOR="DimGray"][B]ROM Changes[/B]
• September security patch[/COLOR]
20200826
Code:
[COLOR="DimGray"][B]ROM Changes[/B]
• August security patch
• Doze changes
[B]Kernel Changes:[/B]
• Revert - Possible fix for "touch screen not responding for few seconds"
• Fixed idle battery drain. [Thanks to @Vishalcj17][/COLOR]
20200716
Code:
[COLOR="DimGray"][B]ROM Changes[/B]
• July security patch
[B]Kernel Changes:[/B]
• Possible fix for "touch screen not responding for few seconds"[/COLOR]
20200609
Code:
[COLOR="DimGray"][B]ROM Changes[/B]
• June security patch
• FM radio fixed[/COLOR]
20200517
Code:
[COLOR="DimGray"][B]ROM Changes[/B]
• Initial unofficial build
• Enforcing selinux[/COLOR]
FAQ
1) When official?
I haven't decided if I want to go official or not.
2) Will there be regular updates?
Atleast once/month, usually after aosp security patch is merged.
Apart from that, Ill release a new build in case of major bugs that breaks the ROM to be used as daily driver.
3) Reporting bugs
DO NOT Report bugs if
• if you didn't perform a clean install.
• if you're running a custom kernel.
• if you've installed Xposed.
• if you're using battery/thermal mods.
4) How to report bugs?
• Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
• Mention what custom stuffs you've installed in the rom, like Magisk modules, etc.
• If the problem disappears after disabling selinux, disable SELinux and grab logs using SysLog app.
• If its a random reboot, grab dmesg. [Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless.]
5) Disabling SELinux
Needs root. You can disable SELinux via the following options.
• SELinux Mode Inverter Magisk module
• SELinuxModeChanger App
• Terminal Emulator App
To disable SELinux using a terminal emulator, run the following commands
Code:
> su
> setenforce 0
6) Taking Logs
Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.
• Using adb
• Using MatLog app
• Using SysLog app for audit logs
mine
the recorder can input audio internal?
Best Q rom for rosy, thanks dev for your work.
Hope you will maintain update this rom.
Battery
Thanks for the rom but i have problem with the battery and some ghost touches here and there. You planning any update in near future? Thanks
New build is up.
20200609
Code:
[COLOR="DimGray"][B]ROM Changes[/B]
• June security patch
• FM radio fixed[/COLOR]
Ryiiiiii said:
the recorder can input audio internal?
Click to expand...
Click to collapse
AFAIK, yes.
tridi001 said:
Best Q rom for rosy, thanks dev for your work.
Hope you will maintain update this rom.
Click to expand...
Click to collapse
Yes, Ill maintain this ROM. Thanks.
nokiagye said:
Thanks for the rom but i have problem with the battery and some ghost touches here and there. You planning any update in near future? Thanks
Click to expand...
Click to collapse
What issue with battery? Ghost touches are known issue. Blame xiaomi for releasing broken kernel source.
New build is up.
20200716
Code:
[COLOR="DimGray"][B]ROM Changes[/B]
• July security patch
[B]Kernel Changes:[/B]
• Possible fix for "touch screen not responding for few seconds"[/COLOR]
Anyone guide me to set fingerprint? I cant find option for this
New build is up. Clean flash "necessary".
20200826
Code:
[COLOR="DimGray"][B]ROM Changes[/B]
• August security patch
• Doze changes
[B]Kernel Changes:[/B]
• Revert - Possible fix for "touch screen not responding for few seconds"
• Fixed idle battery drain. [Thanks to @Vishalcj17][/COLOR]
navinmholkar said:
Anyone guide me to set fingerprint? I cant find option for this
Click to expand...
Click to collapse
Settings -> Security -> Fingerprint.
LinuxPanda said:
New build is up. Clean flash "necessary".
20200826
Settings -> Security -> Fingerprint.
Click to expand...
Click to collapse
Can't find option in security. I checked fingerprint sensor via app and it's shows "fingerprint is not available or using by another app"
navinmholkar said:
Can't find option in security. I checked fingerprint sensor via app and it's shows "fingerprint is not available or using by another app"
Click to expand...
Click to collapse
Did you clean flash and using Oreo firmware? If so, then please give logs.
dirty flash all is ok
thanks
navinmholkar said:
Can't find option in security. I checked fingerprint sensor via app and it's shows "fingerprint is not available or using by another app"
Click to expand...
Click to collapse
I clean flashed it, but before that i am on havoc os so that is issue? Can i flash oreo firmware zip now and then flash new update? Sorry for bad english.
---------- Post added at 12:10 PM ---------- Previous post was at 12:08 PM ----------
LinuxPanda said:
Did you clean flash and using Oreo firmware? If so, then please give logs.
Click to expand...
Click to collapse
I clean flashed it, but before that i am on havoc os so that is issue? Can i flash oreo firmware zip now and then flash new update? Sorry for bad english.
tridi001 said:
dirty flash all is ok
thanks
Click to expand...
Click to collapse
I had issues in settings with dirty flash and D2TW setting disappeared, so said that clean flash is necessary. Thanks for the feedback.
navinmholkar said:
I clean flashed it, but before that i am on havoc os so that is issue? Can i flash oreo firmware zip now and then flash new update? Sorry for bad english.
Click to expand...
Click to collapse
I'm not sure if that could be the issue.
But flashing firmware zip won't cause any issue even if you're flashing firmware after flashing ROM. You may try flashing the correct firmware as they're are global & Chinese firmware. Thanks.
New build is up.
20200921
Code:
[COLOR="DimGray"][B]ROM Changes[/B]
• September security patch[/COLOR]
Great rom very stable
When A11 version ??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Code:
/*
* Your warranty is now maybe 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.
*
*/
LineageOS 20.0 for Xiaomi Redmi 5 (rosy)
Installation
1. If you're coming from another ROM or performing a clean flash:
Reboot to Recovery
Backup any important data
Format Data partition
Wipe Dalvik, Cache, System, Vendor
Flash the ROM
Flash GApps (optional)
Reboot to System
2. If you're updating the ROM or performing a dirty flash:
Reboot to Recovery
Flash the ROM
Wipe Cache
Reboot to System
Downloads
ROM: lineage-20.0-20230623-UNOFFICIAL-rosy.zip
Recovery: TWRP (Recommended)
GApps: NikGapps (Optional)
OTA Updates
Once an update is available in System settings, download the update package and select Install. The device will restart itself and install the update.
Consider enabling auto-delete in Updater settings, since each OTA package can take up a significant amount of storage space.
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel, have installed Magisk, or have made modifications to read-only partitions (with GApps being the only exception).
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
Remember to provide as much info as possible, including the necessary steps to reproduce your issue. The more info you provide, the more likely that the bug will be solved.
Credits
LineageOS, AOSP, CAF, Google, Xiaomi
Sources: https://github.com/LineageOS
Rom Information
LineageOS 20.0, ROM for the Xiaomi Redmi 5
Contributors
baunilla
Source Code: https://github.com/baunilla
ROM OS Version: Android 13
ROM Kernel: Linux 4.9.x
ROM Firmware Required: Latest
Based On: LineageOS
Version Information:
Status: Stable
SELinux: Enforcing
Encryption: FBE
Created 2022-09-01
Last Updated 2023-06-23
Changelog
2023-06-23
Code:
• Switched to AOSP stock camera
• Updated Prima WLAN kernel driver
Code:
• Android 13 QPR3 (Quarterly Platform Release)
• June security patch 13.0.0_r52
• Updated GPS HAL LA.UM.10.6.2.r1-02500-89xx.0
• Enabled Lineage Health HAL
• Added assisted GPS (AGPS) options
• Added charging control options
• Added lockscreen shortcuts options
Code:
• Kernel tag LA.UM.10.6.2.r1-02500-89xx.0
• Kernel upstreamed to 4.9.337
Spoiler: Changelog history
Code:
2023-05-27
• Removed headset requirements for FM Radio
• Updated audio-kernel codec drivers
2023-05-05
• May security patch 13.0.0_r43
• Updated AOSP timezone DB (tzdb 2023a)
• Updated Audio HAL for msm8953
• Updated ALSA PCM/control interfaces
• Disabled Android Rescue Party
2023-04-30
• Disabled per-cgroup memory pressure tracking
2023-04-11
• April security patch 13.0.0_r41
• Merged CAF fixes for GPU kernel driver
• Fixed FM Radio notification icon
• Removed deprecated Bluetooth configs
2023-03-26
• Android 13 QPR2 (Quarterly Platform Release)
• March security patch 13.0.0_r35
• Blobs updated from FP3 (2023-02-05)
2023-02-16
• February security patch 13.0.0_r30
• Dynamic app icons for Clock & Calendar
• Fixed stock camera frame drop issue
2023-01-22
• Merged Kernel ipset/ipv6 upstream bug fixes
• Switched HAL Virtual displays to GPU fallback
• Switched 3GP codec parser to AOSP fallback
• Disabled Media transcoding feature (unsupported)
• Disabled Bluetooth Hearing Aid profile (unsupported)
• Disabled Wifi EXTScan feature (unsupported)
2023-01-10
• January security patch 13.0.0_r20
• Kernel upstreamed to 4.9.337
• Updated blobs from FP3 (8901.4.A.0019.2)
• Updated Vendor SPL (2022-12-05)
2022-12-26
• Fixed dual-sim data switching issue
• Added support for Wifi Aware data-path
• Upgraded Radio config to v1.1
• Fixed potential VADC issue breaking suspend
• Enabled speed-profile filter for system-server
• Reduced ROM package size and RAM usage
2022-12-19
• Kernel upstreamed to 4.9.336
2022-12-11
• Android 13 QPR1 (Quarterly Platform Release)
• December security patch 13.0.0_r16
• Kernel upstreamed to 4.9.335
• Added Launcher icon size customizations
• Added boot image optimization profile
• Fixed speakerphone screen timeout issue
2022-11-30
• Kernel upstreamed to 4.9.334
• Addressed some selinux denials
• Fixed permissions for ipsec tunnel
2022-11-26
• Signed Bluetooth with new certificates
• Fixed GMS device-config permissions
• Bumped limit on sched-tune boost groups
• Migrated to cgroup task_profiles
• Disabled sched iowait_boost
• Fixed DM reads capped at max request size
• Fixed potential FS unmount issue
• Fixed FG Rslow charger compensation
2022-11-20
• Added AOSP FM Radio
• Addressed block discard selinux denials
2022-11-12
• Kernel upstreamed to 4.9.333
• Improved treble response from speaker
2022-11-09
• November security patch 13.0.0_r13
• Improved call volume adjustment range
• Improved echo cancellation for voice calls
• Restored mic mixer-paths from stock
2022-11-05
• Switched build type USERDEBUG -> USER
• Rolled back Audio ACDB blobs from stock MIUI
• Fixed poor low-end response from speaker
• Improved mic volume for dual mic use cases
2022-11-01
• Kernel upstreamed to 4.9.331
• Reduced kernel wakelocks from FuelGauge
• Bumped power-supply limit for pmic
• Fixed supply type probe issue at bootup
• Adjusted fp unlock animation
2022-10-25
• Fixed NPE when iterating power supplies
• Fixed potential bug in battery percentage
• Addressed surfaceflinger selinux denials
2022-10-20
• Updated blobs from FP3 (4.A.0017.3)
• Updated vendor SPL (2022-10-05)
• Dropped obsolete QCOM codec parsers
2022-10-12
• Fixed DAPM probe for external speaker
• Enabled LTE+ icon when available
• Switched to provided shim for ims-vt
• Removed unnecessary recovery libs
2022-10-05
• October security patch 13.0.0_r8
• Updated USB configurations
• Downgraded Radio HAL to v1.4
2022-09-30
• Kernel upstreamed to 4.9.330
• Fixed MT SMS sent during power off
• Fixed VoLTE ringback tone issue
• Fixed Browser storage permissions
• Enabled zygote critical window
• Added WLAN time-slice duty cycle
• Addressed linkerconfig denials
2022-09-26
• Re-Enabled OTA updates
• Disabled Kernel debug monitoring
• Adjusted privacy indicator
2022-09-23
• Android release 13.0.0_r6
• Kernel upstreamed to 4.9.329
• Enabled File-based encryption
• SELinux enforcing
• Updated Audio HAL to v7.1
• Switched to AIDL DRM HAL
• Updated Bluetooth configs
2022-09-07
• September security patch 13.0.0_r4
• Kernel upstreamed to 4.9.327
• Fixed WiFi interface scan errors
• Fixed WiFi Hotspot issues
• Fixed & enabled Setup Wizard
• Removed QTI BT Audio HAL
2022-09-03
• Fixed Bluetooth Audio issues
• Fixed Network access for 3rd party apps
2021-09-01
• August security patch 13.0.0_r3
• Kernel tag LA.UM.10.6.2.r1-02500-89xx.0
• Kernel upstreamed to 4.9.326
Reserved.
>>Flash GApps (optional)
What gapps are recommended to be installed?
gapps for android 13 exist?
Too much buggy
baunilla said:
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Code:
/*
* Your warranty is now maybe 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.
*
*/
LineageOS 20.0 for Xiaomi Redmi 5 (rosy)
Installation
1. If you're coming from another ROM or performing a clean flash:
Reboot to Recovery
Take a full backup (optional)
Format Data if encrypted
Wipe Dalvik, Data, Cache, System, Vendor
Flash the ROM
Flash GApps (optional)
Reboot to System
2. If you're updating the ROM or performing a dirty flash:
Reboot to Recovery
Flash the ROM
Wipe Cache
Reboot to System
Downloads
ROM: lineage-20.0-20220901-UNOFFICIAL-rosy.zip
Recovery: TWRP (Recommended)
Credits
LineageOS, AOSP, CAF, Google, Xiaomi
Sources: https://github.com/LineageOS
OTA Updates
Once an update is available in System settings, download the update package and select Install. The device will restart itself and install the update.
Consider enabling auto-delete in Updater settings, since OTA packages can take up considerable storage space.
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or any other modificattions.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
XDA:DevDB Information
LineageOS 20.0, ROM for the Xiaomi Redmi 5
Contributors
baunilla
Source Code: https://github.com/baunilla
ROM OS Version: Android 13
ROM Kernel: Linux 4.9.x
ROM Firmware Required: Latest
Based On: LineageOS
Version Information:
Status: Alpha
SELinux: Permissive
Created 2022-09-01
Last Updated 2022-09-01
Click to expand...
Click to collapse
you're best bro 1 dev for android 13 for rosy you are best bro
Let me tell the bugs ..
1. INTERNET DOSEN'T WORKING ( MOBILE DATA )
2. AUTO BRIGHTNESS MODE TOGGLE NOT WORKING
3. MIC ACCESS IS BUGGY ( NOT WORKING MIC )
4. UNABLE TO RESTORE THE CONTACTS.VCF FILE FROM FILE MANAGER INTO CONTACT
5. SETUP WIZERD IS MISSING
6. LTE+ NOT WORKING
& may be some other bugs can be find by the other users while using those particular works , I just used 15 minutes & in this short time Period of usage I found these bugs ... Hope these be fixed by the developer @baunilla sir
Thanks sir for this built ... I hope we will get regular update & these bugs will be fixed in future updates ..
Appreciate for your work @baunilla sir --- you gave a new life to my rosy
Sorry guys, disabling download link until internet access issue is fixed.
<Moderator Note>: Thread temporarily closed at OP's request.
Thanks, @baunilla! Just let us know when you're ready for us to reopen it.
Thread re-opened at OP's request.
Download link restored.
2022-09-02
Code:
• August security patch 13.0.0_r3
• Kernel tag LA.UM.10.6.2.r1-02500-89xx.0
• Kernel upstreamed to 4.9.326
Build re-uploaded to fix Internet access issues.
baunilla said:
Download link restored.
2022-09-02
Code:
• August security patch 13.0.0_r3
• Kernel tag LA.UM.10.6.2.r1-02500-89xx.0
• Kernel upstreamed to 4.9.326
Build re-uploaded to fix Internet access issues.
Click to expand...
Click to collapse
Also fix other bugs also please sir
Mainly fix - mic not working issue .. That would be pleasure
LGD Breath said:
Mainly fix - mic not working issue .. That would be pleasure
Click to expand...
Click to collapse
Mic is working for me. Can you be more specific?
When I turn on mic access , it still shows cross symbol on mic in status bar ... & people can't get my sound ... In sound recorder too my recorded voice is soundless .... I round back to 12.1 , there mic is working fine
& I unable to restore my contact.vcf from file manager ... It shows permission desable
Is I need to wipe everything while flashing ??? I mean internal storage ????
burchik.v said:
>>Flash GApps (optional)
What gapps are recommended to be installed?
gapps for android 13 exist?
Click to expand...
Click to collapse
Nikgapps for 13 are ready for various packages. Go or core is best for Rosy
baunilla said:
Download link restored.
2022-09-02
Code:
• August security patch 13.0.0_r3
• Kernel tag LA.UM.10.6.2.r1-02500-89xx.0
• Kernel upstreamed to 4.9.326
Build re-uploaded to fix Internet access issues.
Click to expand...
Click to collapse
Sir internet problem not fix internet working on only lineage os browser and magisk not working in Google play store chrome and other apps this work only in 1 app browser
I have just successfully flashed Lineage OS 20 with Nigapps Go. Internet works only with browser, GG Play store. Other apps: Ms Teams, YouTube, GG Photos, Zalo (Vietnam app, similar Whatsapp/Viber) show offline. Volte works.
One more thing: Netflix cannot be installed in Android 13. In previous Lineage OS 19.1, it runs smoothly
{
"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.
*
LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Githup repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP recovery in the installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
Installation Instructions:
Backup your data and see the next post below
Recommended TWRP Image:
twrp-3.7.0_9-0-kuntao.img
ROM Download Links:
Google Drive | SourceForge
Recommended Google Apps Package:
NikGapps-core-13
NikGapps-SetupWizard
NikGapps-AndroidAuto
Root Access:
Magisk v25.2
Source Code:
https://github.com/LineageOS
ROM Firmware Required:
Any version of stock 6.0. Recommended P2a42_S251_171107_ROW
Acknowledgements:
Thanks to all Lineage OS developers
Special thanks to @Astridxx & @XiaoAk for the device tree sources and to @Astridxx for (once again) helping me out
Important Notes:
As you can see from my profile, I'm not an experienced developer. I've made some builds as a considerable amount of users showed interest in having their devices updated with latest LineageOS code. Therefore, my main objective here is to bring the latest Android security patches to kuntao making monthly builds.
To be clear, I'm more in a situation of "user became builder" than of "ROM developer". Please, understand this.
Long live to our beloved kuntao!
XDAevDB Information
[ROM][13][UNOFFICIAL] LineageOS 20 for Lenovo P2
Contributors
@Astridxx ,@XiaoAk
ROM OS Version: 13.x
ROM Kernel: Linux 3.18.x
Based On: LineageOS
Version Information
Status: Stable
Created 2023-03-05
Last Updated 2023-04-20
Installation Instructions
Remember, making a backup of your data before proceeding is recommended
If you are coming from Stock ROM, please refer first to the instructions below:
Install LineageOS on kuntao
If you are coming from any version of LOS18.1 or LOS19.1 or from any ROM that isn't android 13 based, you must perform a clean flash:
0- Make a backup (optional, but recommended)
1- Reboot to recovery
2- Format data (will delete all your data!)
3- Reboot to recovery again
4- Wipe > Advanced Wipe:
- Dalvik
- System
- Vendor
- Data
- Cache
- Internal Storage (optional, but recommended)
5- Flash ROM ZIP, Gapps, Gapps add-ons, Magisk add-on, etc
6- Reboot to system
7- Wait until it boots for the first time (may take some minutes)
8- If Magisk is missing after finishing the setup wizard, please reboot to system
Update Instructions
For updating from one of my builds to another (aka dirty flashing), please do the following:
1- Download ROM ZIP and copy it to the phone
2- Reboot to recovery
3- Flash ROM ZIP
4- Clean cache
5- Reboot to system
Known Issues
- Storage encryption is broken ( FDE was deprecated in a13 )
- Network traffic monitoring ( 4.9 kernel required for this )
- GPU monitoring ( 4.9 kernel required for this )
ROM Doesn't Boot After Flashing
Make sure you formatted /data partition (see installation instructions step 2)
SafetyNet Status Fix Instructions
1- Make sure Magisk was properly installed
2- Open the Magisk App
3- Open App settings (wheel on the top right side of the screen)
4- Enable "Zygisk"
5- Enable "DenyList"
6- Open "Configure DenyList"
6.1- On "Google Play services": Enable "com.google.android.gms" & "com.google.android.gms.unstable"
6.2- On "Google Play Store": Enable "com.android.vending"
7- Click on the back arrow (on top left)
8- Reboot your system
9- Test again (now it should pass)
ROM Change logs
Code:
03/05/2023
- Initial release
03/30/2023
- Fetch latest Device Tree
-- Sepolicy:
--- Address sensor hal denials
--- Address launcher3 denials
--- Allow some apps to access debuggable prop
-- rootdir:
--- Create STSensorHAL folder on data
--- Restore iio sensor device6 on boot
--- Add cpuset for the camera daemon
-- overlays:
--- Disable IMS features for Turkiye networks
--- Enable voWIFI support
-- prop:
--- Disable Bluetooth APCF Extended features
--- Enable ro.hwui.render_ahead and set it to 20 frames
-- Enable selinux ignore never allow flag
-- Don't force enable ims features
-- Remove aptX(HD) encoder shared libs
-- vendorsetup.sh: Add Trebuchet patch
- Update LOS components
-- Manifest:
--- Sync x86_64 webview prebuilts again
--- March 2023 Quarterly Platform Release and Security update
--- gs101 March 2023 Quarterly Platform Release and Security update
-- Update zlib source
- Sync latest LOS sources
- Update platform to android-13.0.0_r35
- Merge March security patch
04/20/2023
- Fetch latest Device Tree:
-- Set default livedisplay mode to 0
-- vendorsetup.sh: Add DeskClock patch
-- trebuchet:
--- Make overview scrim transparent again
--- Kill haptics in recents
-- nfc: Fix Mifare Classic reading
-- sepolicy:
--- Silence suspend_control_service neverallow denial
--- Silence tracingproxy_service neverallow denial
--- Silence fsck_untrusted neverallow denial
--- Allow system_app to access storaged via IPC
-- overlay: Allow gms to access persistent data partition
-- props:
--- Silence ResourcesCompat spam
--- Remove hwui skia atrace properties
--- Disable virtual displays writeback
-- Revert "sepolicy: Allow some apps to access debuggable prop"
- Sync latest LOS sources:
-- lineage: Track the FMRadio App and dependencies
-- Move Trebuchet to default.xml
-- overlay:
--- Disable immersive mode confirmation
--- Move default status bar height to no-rro
-- soong: Bring bootloader_message_offset back
-- envsetup: aospremote: Take .gitupstream into account
- Update platform to android-13.0.0_r41
- Merge April security patch
ROM Screenshots
Attached below.
Great work! Will test it when I have time, been waiting for this..
Hi all. I read these P2 forums for long time, but never participated. I love our P2 phone, riding a P2 since the release date and never changed. Now I got a message from my bank that the android version is too outdated to use their banking app, and they want me to switch to a newer OS. I could have ditched the P2, but couldn't. Therefore....easiest solution was to buy a second one xD I will test on the backup unit some of the roms available here, probably starting from the roms of @leo_97 . I need a stable daily driver, thus when I find something that works for me I will freeze it there for some time. But, in the meantime, I can help out with testing, starting from mid April onwards thus, feel free to contact me, and I will be a bit more active (and not passive) here in XDA for the coming months.
Cheers to all, and thanks @leo_97 , @Astridxx, @XiaoAk (and @mikeioannina for all the past efforts on P2!).
Hi
I just tested it on a P2 for a few hours and it works great! Thanks!
Is there any way to get full device encryption to work?
If I understand correctly, someone can access the phone's files even if you have a pin or password as it is now.
MKbis said:
But, in the meantime, I can help out with testing, starting from mid April onwards thus, feel free to contact me, and I will be a bit more active (and not passive) here in XDA for the coming months.
Click to expand...
Click to collapse
I'll PM you right away.
Draywen said:
Hi
I just tested it on a P2 for a few hours and it works great! Thanks!
Is there any way to get full device encryption to work?
If I understand correctly, someone can access the phone's files even if you have a pin or password as it is now.
Click to expand...
Click to collapse
You are welcome
So, IFAIK we don't have a way to make FDE work on A13 ROMs, A13 moved to FBE (File Based Encryption) which is not supported by 3.18.x kernel and we don't have rn a patch available that could enable it on our kernel version.
Regarding data access, I believe so. Without storage encryption, booting into recovery will already give access to the files. IIRC to this date encryption is fully working only on A11-based ROMs and maybe on some A12 ones.
Okay, so I'm stuck in a boot loop. I flashed the ROM from the link above but the phone won't start up. I just get the Lineage booting screen with the circle moving right to left. I've left it for 15 minutes just in case the first boot was slow but nothing else happens. I've tried to restore my original backup which was Lineage 17.1. It seemed to work, no errors from TWRP but now i just get the Lenovo screen and then it boots to fastboot mode. I flashed Lineage 20 for a second time but the same happened. I tried a different backup from August last year, again it just boots to fastboot.
Any ideas?
Cheers, Si.
EDIT: I've just noticed that I missed out step 3, reboot to recovery between Data wipe and flash ROM.
Now it boots no problem.
Cheers, Simon.
EDIT AGAIN: I still can't revert to either of my previous backups of Lineage 17.1. I would really like to be able to do this. Can anyone suggest why it will only boot to fastboot mode after a seemingly successful restore?
Thank you,
Simon.
@simes303
Don't know what the problem is, but I'd flash stock via fastboot. Then reinstall TWRP and restore LOS.
When things go wrong it's better to start from scratch rather than tinkering around and doing temporary fixes.
how is the battry life anyone?
eried1 said:
@simes303
Don't know what the problem is, but I'd flash stock via fastboot. Then reinstall TWRP and restore LOS.
When things go wrong it's better to start from scratch rather than tinkering around and doing temporary fixes.
Click to expand...
Click to collapse
Hi,
How is this different from flashing stock with TWRP?
Cheers, Si.
Used briefly but battery life seems worse, its like draining. Using 12L Lineage os and its way better.
mahmutpekkara said:
Used briefly but battery life seems worse, its like draining. Using 12L Lineage os and its way better.
Click to expand...
Click to collapse
how long does it last
laggy_boy said:
how long does it last
Click to expand...
Click to collapse
Didn't test much but its way waay noticable, you wouldn't want to use when you see the difference (didn't differ with or without gapps)
btw thx to all devs, using lineage os a12.1 and its good on battery
Battery life for me is considerably better than the Lineage 17.1 that I was using before, no question. I'd estimate almost twice the duration. I'm very happy with this ROM, thanks to all involved in developing it.
Simon.
I've actually just bought a brand new 64 Gb Lenovo P2 pretty cheap from eBay and I will definitely be flashing this Rom onto it.
Thanks again,
Simon.
Hi,
Does this ROM have USB OTG support? I can't get the phone to connect to either my external SSD drive or my bicycle helmet camera since I flashed this ROM. Both these things connected via OTG cable to my phone when I was running Lineage 17.1 and they also connect to the new P2 that I bought recently that still has stock OS. I've tried three OTG checker apps which all state that my phone is OTG compatible.
Thanks, Simon.
March 30th 2023 Release
Changelog:
- Fetch latest Device Tree sources
- Update LOS components webview & zlib
- Sync latest LOS source
- Merge March security patch
- Many more changes
Full change log available on the bottom of this post
Download URLs: GDrive | SF
Enjoy!
simes303 said:
Hi,
Does this ROM have USB OTG support? I can't get the phone to connect to either my external SSD drive or my bicycle helmet camera since I flashed this ROM. Both these things connected via OTG cable to my phone when I was running Lineage 17.1 and they also connect to the new P2 that I bought recently that still has stock OS. I've tried three OTG checker apps which all state that my phone is OTG compatible.
Thanks, Simon.
Click to expand...
Click to collapse
Hello Simon,
Yes, it does have OTG support. IFAIK it should work correctly with both FAT32 and NTFS partition types on external storage devices.