Pitchblack 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"
}
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.
*
*/
PitchBlack is a TWRP based on TWRP 3.2.3 developed by Reza Adi, maintained by Manjot Sidhu and Mohd Faraz and themed by FireWolf.
For devices (OFFICIAL) : https://sourceforge.net/projects/pitchblack-twrp/files/
Authors build : @Reza_adi, Mohd Faraz
Developers : @Reza_adi, Mohd Faraz
Thanks : @Reza_adi P - Indonesia (Owner / Lead Developer PBRP), George Pasakalis (G.M.L) - Greece (UI Developer), FirewolfXDA - Bangladesh (UI Developer), Manjot Sidhu - India (Source Maintained), Mohd Faraz - India (Co-Lead Developer, Source Maintained), Arbaz Khan - India (Source Maintained), PitchBlack Recovery, @ATG Droid & @dadi11 (Redwolf Developer) for MIUI OTA Support, @arra_quen for Helping and Uploading @faizhifzhan for layout to sourceforge, All Maintainer and User PBRP.
DOWNLOAD :
Recovery zip
BUGS:
When booted while charging, battery level shows 0%.
If you find any other bugs please let me know and i'll try to address them or update this section of the thread to let the bug be publicly known.
F2FS filesystem format is limited to 4GB for some reason so don't use it for /data ( I currently use /cache and /system as f2fs instead of EXT4 with no issues )
INSTALLATIONS :
Flash Zip file as if it were a ROM in TWRP, or you can flash the Recovery.img as you would TWRP (adb commands, apps such as flashify, kernel auditor/mtweaks, terminal dd commands, or using TWRP under Install > install image > recovery )
If using installing the Zip file through TWRP or other custom recovery, it will reboot automatically to recovery. If using the recovery.img method, reboot into recovery as you normally would.
Enjoy
XDA:DevDB Information
PitchBlack Recovery Project, Tool/Utility for the LG K20 Plus
Contributors
Travisholt92,
Deadman96385 (helped to provide bandwidth and the Q6 Stock Oreo kernel which my Oreo+ builds and this project utilize)
Source Code: [url]https://github.com/PitchBlack-Recovery[/URL]
Version Information
Status: Official
Current Version: 2.9.0
Release Date: 2019-02-05
Created 2019-02-03
Last Updated 2019-02-07
My to do list for tonight, update the Fstab to properly support F2FS filesystem format and address the filesystem error.
I should have a new official build up tonight.
I must say this recovery is ? % awesome. I like the extra features that include the options to install/uninstall SuperSU and/or magisk and various more. I think twrp has met it's match.
kieffey said:
I must say this recovery is ? % awesome. I like the extra features that include the options to install/uninstall SuperSU and/or magisk and various more. I think twrp has met it's match.
Click to expand...
Click to collapse
And that's why I went for Official PBRP before official TWRP, to get people to at least give it a try. Its based on the latest TWRP so it has all of the features TWRP users love with quite a few extras.
will this work on stock rom
chacon16 said:
will this work on stock rom
Click to expand...
Click to collapse
It should, I haven't tested. The only reason to stay on stock is VoLTE.
chacon16 said:
will this work on stock rom
Click to expand...
Click to collapse
It works fine in stock. It works with every flavor of ROM out for the K20 Plus.
Sent from my LG K20 Plus using XDA Labs
New build up today that addresses the issue with rebooting to recovery from within recovery.
Screenshots
ROMs?
I read earlier that "every flavor of K20 Plus" will work with PB, so I just want to make sure I am 100% clear and sure I understand before I **** up (another) phone...
I am using a Rooted LG K20 Plus with the Resurrection Remix OS ROM and Pitch Black recovery. The only problem is that my phone has no audio function. Mic, and Speakers are nonfunctional. It won't play videos, make or receive calls, play music, or even the background sound on Games. It is my understanding that this is a common bug with Resurrection Remix ROM, so I'd like to just put a new OS. I just need to know if any OS will work as long as its compatible with the K8+ or if it has to be tailored/compatible for PB as well?
CrookedYoungHeretic said:
I read earlier that "every flavor of K20 Plus" will work with PB, so I just want to make sure I am 100% clear and sure I understand before I **** up (another) phone...
I am using a Rooted LG K20 Plus with the Resurrection Remix OS ROM and Pitch Black recovery. The only problem is that my phone has no audio function. Mic, and Speakers are nonfunctional. It won't play videos, make or receive calls, play music, or even the background sound on Games. It is my understanding that this is a common bug with Resurrection Remix ROM, so I'd like to just put a new OS. I just need to know if any OS will work as long as its compatible with the K8+ or if it has to be tailored/compatible for PB as well?
Click to expand...
Click to collapse
This phone is not compatible with k8 at all. I released lineage 15.1 and it is currently the only stable Oreo rom for this device
Travisholt92 said:
This phone is not compatible with k8 at all. I released lineage 15.1 and it is currently the only stable Oreo rom for this device
Click to expand...
Click to collapse
Whoopee, where it says K8+ on my post is a typo, idk why but my boyfriend was under the impression initially that this K20+ was a K8, I still get confused and mixed up, especially since I also tinker with an LG K4 Rebel lol. But the phone I am using/inquiering about is indeed the LG K20+.
P. S do you have any input/suggestions/advice about the Resurrection ROM 8I can just 7 send 8tnti you
leave your /system partition formatted as ext4
Flashing this ROM uses block-based patching; instead of copying the necessary files to the filesystem, it copies blocks to the disk. These blocks are data representations of files as they were expressed on the filesystem they originate from, thus copying blocks from an ext4 filesystem to any other filesystem will corrupt it.
Since this is my first post I cannot post the pictures I took of PBRPs output after flashing the ROM to both f2fs and ext4 filesystems and then running e2fsck. On f2fs, the partition is recognized as ext4 after the flash, and e2fsck.f2fs fails as the partition is corrupt beyond repair. On ext4, e2fsck executes as expected. You can also search "block-based OTAs" to find the entry on the AOSP website for more information.
dode417 said:
Flashing this ROM uses block-based patching; instead of copying the necessary files to the filesystem, it copies blocks to the disk. These blocks are data representations of files as they were expressed on the filesystem they originate from, thus copying blocks from an ext4 filesystem to any other filesystem will corrupt it.
Since this is my first post I cannot post the pictures I took of PBRPs output after flashing the ROM to both f2fs and ext4 filesystems and then running e2fsck. On f2fs, the partition is recognized as ext4 after the flash, and e2fsck.f2fs fails as the partition is corrupt beyond repair. On ext4, e2fsck executes as expected. You can also search "block-based OTAs" to find the entry on the AOSP website for more information.
Click to expand...
Click to collapse
Only /cache and /system will currently work with F2FS which needs to be formatted that way before install and only my Lineage 15.1 supports f2fs filesystem format. I have tested and confirmed it works at the time of implementation. Formatting /data as F2FS limits the partition to 4GB for some reason i have yet to figure out. I hope this bit of information helps.
CrookedYoungHeretic said:
Whoopee, where it says K8+ on my post is a typo, idk why but my boyfriend was under the impression initially that this K20+ was a K8, I still get confused and mixed up, especially since I also tinker with an LG K4 Rebel lol. But the phone I am using/inquiering about is indeed the LG K20+.
P. S do you have any input/suggestions/advice about the Resurrection ROM 8I can just 7 send 8tnti you
Click to expand...
Click to collapse
RR 8.1 was a total flop. I built it once and it had so many ROM source related bugs from no longer being supported by the RR team that i just gave up on it. More or a variety of ROMs will come after i get pie working.
Travisholt92 said:
Only /cache and /system will currently work with F2FS which needs to be formatted that way before install and only my Lineage 15.1 supports f2fs filesystem format. I have tested and confirmed it works at the time of implementation. Formatting /data as F2FS limits the partition to 4GB for some reason i have yet to figure out. I hope this bit of information helps.
Click to expand...
Click to collapse
I'm not saying it doesn't boot, only informing everyone that the f2fs partition is corrupted by the flashing process and cannot be repaired with fsck. I'm honestly not sure of the total effect of this, but those who are cautious may be thankful for this information.
I can flash the recovery.img for PBRP after doing bootloader unlock via fastboot correct? I don't need to flash TWRP and do all the flashing steps under "How to Disable encryption and flash super su [Install Root]" in the TWRP v3 thread to get PBRP and Magisk on my device? Eventually plan on putting LOS 15.1
SomeDooD123 said:
I can flash the recovery.img for PBRP after doing bootloader unlock via fastboot correct? I don't need to flash TWRP and do all the flashing steps under "How to Disable encryption and flash super su [Install Root]" in the TWRP v3 thread to get PBRP and Magisk on my device? Eventually plan on putting LOS 15.1
Click to expand...
Click to collapse
That is correct, you can use PBRP for those steps.
@Travisholt92 I am trying to flash PBRP and i can only find the .zips linked above. I have tried flashing the .zips in TWRP 3.2.1 . I am failed with "Invalid zip file format" . What am i doing wrong?
chugs said:
@Travisholt92 I am trying to flash PBRP and i can only find the .zips linked above. I have tried flashing the .zips in TWRP 3.2.1 . I am failed with "Invalid zip file format" . What am i doing wrong?
Click to expand...
Click to collapse
You have to unzip the file and fastboot flash recovery.IMG or install the image through twrp under install image
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"
}
Elite TWRP Project
For P9 Lite
DONOT COPY MY WORK, Ask for Permissions or Gather it yourself,,,
This ROM is only for Firmwares based on EMUI 5.X only...
Code:
/*
* 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 finger at me for messing up your device, i will laugh at you.
*
*/
Elite TWRP 3.2.1-0 for Huawei P9 Lite
Additional Features:
*Latest TWRP 3.2.1-0
*Added Support for All Partitions Like Cust, Data, Vendor, Product, System, Version
*Image install Support in Cust, System, Product, Vendor, System & Version
*Backup Facility for all Partitions including, Boot, Cache, Data, Product, Cust, Vendor, System, Version and OEMinfo
*Compatible to install Each and Every ROM including Elite ROMs, AOSP Based ROMs...
*Mount Support for Cust, Data, Product, Vendor, Version & System
*Decryption Support (Thanks to Meticulus)
*Red Color for Stock and Elite ROMs, Blue Color for AOSP Based ROMs....
Installation Instructions:
1.) Download the Elite TWRP from the 2nd Post...
2.) Install Image with other TWRP or go to Fastboot mode and use command, Fastboot flash recovery EliteTWRP_3.2.1-0.img
3.) Reboot Recovery with Pray.... ENJOY
Hit Thanks and Support me if you Like and get help from this thread...Thank you...
Take Permission before sharing links or copying to other Forums....
If something is not working and you need support from me, then upload recovery.log of your problem,,, i wont considered your problem as a real problem without log,,, because others saying this as working!!
Source Codes: https://github.com/HassanMirza01/
XDA:DevDB Information
Elite TWRP Project, Tool/Utility for the Huawei P9 Lite
Contributors
HassanMirza01, Meticulus
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Current Stable Version: 3.2.1-0
Stable Release Date: 2018-01-19
Created 2018-01-10
Last Updated 2018-01-19
Download Links:
2018-01-16 Elite TWRP Project 3.2.1-0 by HassanMirza01
Elite TWRP Project 3.1.1-1
Changelog:
2018-01-19
*Stock ROMs Decryption 100% Fixed, Working & Tested...
*Red Color for Elite/Stock ROMs, and Blue Colored for AOSP Based ROMs...(Thanks to Meticulus)
2018-01-16
*Fixed Stock Decryption (thanks to @paulobrien)
*Changed Resolution to FHD
*Cust Partition removed as storage (it was not necessary)
Press Thanks and donate if you like it
Just flashed it to my L21... Thanks... =)
404 not found please fix link
micbanand said:
404 not found please fix link
Click to expand...
Click to collapse
There were some options missing... Uploading again... Now Light gone... Hope so will upload within half hour...
status testing for now
You rescued my phone
OMG
Thnx, this was it.
For 2 weeks i tried to fix my bricked huawei p9 lite L31C432
It running smooth for so far.
Thank you very mutch for this working rom.
Finaly.
Greetings from The Netherlands.
Mount
Decrypt Data
Enter Password??
Huawei P9 Lite
VNS-L21C432B388
Stock ROM Android 7.0
Profifa12 said:
Mount
Decrypt Data
Enter Password??
Huawei P9 Lite
VNS-L21C432B388
Stock ROM Android 7.0
Click to expand...
Click to collapse
Use old twrp, 3.1.1.1 and do clean flash again.
Great work as always! Going to test once it is deemed stable enough to be used on a daily basis.
uberstar100 said:
Great work as always! Going to test once it is deemed stable enough to be used on a daily basis.
Click to expand...
Click to collapse
Its stabled now... Uploaded new version on same link...
why when i reboot in recovery mode , your TWRP ask me Password to Decrypt Data ??? I dont know what is the password ... help me pls
Download Links:
2018-01-16 Elite TWRP Project 3.2.1-0 by HassanMirza01
Changelog:
2018-01-16
*Fixed Stock Decryption (thanks to @paulobrien)
*Changed Resolution to FHD
*Cust Partition removed as storage (it was not necessary)
Press Thanks and donate if you like it
HassanMirza01 said:
Download Links:
2018-01-16 Elite TWRP Project 3.2.1-0 by HassanMirza01
Changelog:
2018-01-16
*Fixed Stock Decryption (thanks to @paulobrien)
*Changed Resolution to FHD
*Cust Partition removed as storage (it was not necessary)
Press Thanks and donate if you like it
Click to expand...
Click to collapse
Will this work on P9 Lite 2017 PRA-LX1?
rubentkato77 said:
Will this work on P9 Lite 2017 PRA-LX1?
Click to expand...
Click to collapse
Yes mostly all hi6250 devices are supported only a few doesn't work
Hi, I'm having trouble with this on an VNS-L22. If I install this TWRP (either from another TWRP or from ADB), it wont go past the "your device is booting now" message after booting, and wont get into the actual TWRP. Also I tried installing other TWRPs after that using "fastboot flash recovery path/to/TWRP.img" and had the same problem with this other twrp. Then I did "fastboot flash recovery recovery.img" and it installed the previous TWRP I had on my phone (Meticulus's twrp for Beanstalk OS). Is there some way to change that (I'm gessing internall) "recovery.img" from the last command for the EliteTWRP_3.2.1-0.img? Or how could I ever get this twrp working for me?
Thanks a lot!
NachoAbarca said:
Hi, I'm having trouble with this on an VNS-L22. If I install this TWRP (either from another TWRP or from ADB), it wont go past the "your device is booting now" message after booting, and wont get into the actual TWRP. Also I tried installing other TWRPs after that using "fastboot flash recovery path/to/TWRP.img" and had the same problem with this other twrp. Then I did "fastboot flash recovery recovery.img" and it installed the previous TWRP I had on my phone (Meticulus's twrp for Beanstalk OS). Is there some way to change that (I'm gessing internall) "recovery.img" from the last command for the EliteTWRP_3.2.1-0.img? Or how could I ever get this twrp working for me?
Thanks a lot!
Click to expand...
Click to collapse
I assume that you are on emui4 because you are on "Beanstalk OS". You need to upgrade to emui5 to use this recovery and roms. This is based on emui5 and old Meticulus recovery is emui4. Different android version.
Babile said:
I assume that you are on emui4 because you are on "Beanstalk OS". You need to upgrade to emui5 to use this recovery and roms. This is based on emui5 and old Meticulus recovery is emui4. Different android version.
Click to expand...
Click to collapse
Ha basic. Thanks a lot!! I'll upgrade and see what happens. Thanks again!
if anyone gets password on twrp startup, PM me ASAP http://t.me/HassanMirza01
Download Links:
2018-01-16 Elite TWRP Project 3.2.1-0 by HassanMirza01
Changelog:
2018-01-19
*Stock ROMs Decryption 100% Fixed, Working & Tested...
*Red Color for Elite/Stock ROMs, and Blue Colored for AOSP Based ROMs...(Thanks to Meticulus)
Press Thanks and donate if you like it
{
"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.
*
* 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 TREBLE
* SUPPORT 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.
*
*/
What is Project Treble:
Project Treble basically partitions your device into two separate partitions, a system and a vendor: system contains your generic system image, while vendor partition has your device specific files required for booting and running your phone. This way we can easily change the system image and be able to run our device on different system images with the same kernel and vendor partition
Read more about Project Treble
What's a GSI?:
A GSI literally means Generic System Image. It is a general system image meant for no specific device. Treble enabled devices have the capability to run a GSI. You can find a GSI here: Phh-Treble
Xiaomi Redmi 4A hardware vs Treble implementation:
Our Redmi 4A is an A-only device. This means that regarding the GSI images (GSI = Generic System Image) to be used, you need to get ARM64 and A-Only system images
How to report bugs:
Logcat, a simple description of the bug, kmsg or dmseg depending on the bug
What's Packaged in the zip:
A boot image (kernel)
A compressed vendor image (cust partition)
How to use:
Reboot to recovery (Custom TWRP recovery for Redmi 4A - Direct link)
Format /system, /data and /cache
Install Treble flashable zip package (Project Treble flashable for Redmi 4A - Direct link)
Install the GSI system image you wish to use (How to flash a Generic System Image (GSI) on Project Treble supported devices - Direct link)
Reboot
Important notes:
Current minimal * required * firmware version is MIUI 8.3.29 Global dev, otherwise installation could have issues. Download the latest dev fastboot package directly from Xiaomi and flash it prior to installing LineageOS or, alternatively, download and install one of the latest custom packages containing firmware only (at your own risk).
GApps can only be flashed on clean installs.
Formatting data (all user data is wiped, including internal storage) is a must if MIUI was previously installed and device was encrypted.
Screenshots:
Broken:
WIFI MAC address gets randomly generated (only once, you will keep the same as long as you are on LOS)
Encryption (format data or remove encryption when coming from a non-treble rom)
Sepolicy is still permissive
Nothing else? Otherwise please report it!
Working:
Camera (and flashlight)
WiFi
Bluetooth
Telephony (Calls and Data)
Audio (Record and Playback)
Video Playback
Sensors
GPS
VoLTE (AOSP doesn't have the needed patches to get it working, but most other GSIs have them)
Credits & collaborations:
This work is due to efforts from RedmiDevs founding members that did the full device bring-up. Huge thanks to @xboxfanj for all the help during that bring-up.
Finally, all RedmiDevs & LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
And I would give a special thanks to Baron Bronson for providing his device for developing!
Device wiki:
Unofficial wiki link
XDA:DevDB Information
Project Treble, ROM for the Xiaomi Redmi 4A & 5A
Contributors:
33bca
ROM OS Version: 8.1 Oreo
ROM Kernel: Linux 3.18.71
ROM Firmware Required: MIUI 8.4.12 dev
Version Information
Status: Beta
Created 2018-05-13
Last Updated 2018-05-24
You like my work? Feel free to donate here.
Changelog:
V1 - 13.05.2018
- Initial Release
V2 - 24.05.2018
- Unified with Redmi 5A from now on!
- Added full RGB LED (It's slow while selecting the colors, but I'll improve the HAL soon)
- Added new poweroff charging animations (Yay, it even shows percentage)
- Fixed calls over bluetooth
- Updated screen off gestures ( Added some new goodies)
- Updated Camera to the latest CAF tag
- Updated Kernel to the latest CAF tag
Reserved #3
Finally a treble support for rolex. Thank you for make it happen.
Reserved.
Dang, you really did it! Thanks a ton for supporting our device. ?
There seems to be no option in TWRP to flash the system image, only for boot and recovery. Do we flash it via fastboot?
Do we need any special version of TWRP for this ?
Rajat14801 said:
Do we need any special version of TWRP for this ?
Click to expand...
Click to collapse
I want to know it too.
MaxisMan said:
There seems to be no option in TWRP to flash the system image, only for boot and recovery. Do we flash it via fastboot?
Click to expand...
Click to collapse
Yes, that's what I did.
Is this a ROM or a file
Update
Unified with Redmi 5A from now on!
Added full RGB LED (It's slow while selecting the colors, but I'll improve the HAL soon)
Added new poweroff charging animations (Yay, it even shows percentage)
Fixed calls over bluetooth
Updated screen off gestures ( Added some new goodies)
Updated Camera to the latest CAF tag
Updated Kernel to the latest CAF tag
You can find the remaining bugs in the OP.
Due to my broken Redmi 4A I can't deliver that many and bigger updates. I should receive the replacement parts in about a month. (I didn't find any faster delivery at a reasonable price..)
Grab the update here!
BTW: You will need a TWRP with custom vendor support like this one.
MaxisMan said:
There seems to be no option in TWRP to flash the system image, only for boot and recovery. Do we flash it via fastboot?
Click to expand...
Click to collapse
Rajat14801 said:
Do we need any special version of TWRP for this ?
Click to expand...
Click to collapse
BTomiii said:
I want to know it too.
Click to expand...
Click to collapse
You will need at least a recovery with vendor partition support, you can check this one out: https://androidfilehost.com/?fid=818222786056029479
rseragon said:
Is this a ROM or a file
Click to expand...
Click to collapse
A flashable ZIP that contains the vendor and boot image.
Does this work on any custom ROM or only los
I am using aex 5.5 will it work on it
Any fix for decryption failure?
BTomiii said:
Any fix for decryption failure?
Click to expand...
Click to collapse
Not yet
Sent from my Redmi 4A using XDA Labs
Does the decryption issue just mean when flashing to treble that the device must be unencrypted or that I also can't encrypt after flashing a GSI? If only the former then it's annoying but not too bad. If the later, I hope it can be fixed soon as I like device security.
cant flash gapps on dotos gsi
How do I go back to the stock MIUI ROM after following the given steps and installing a Generic System Image?
Can all of this be reverted by installing a MIUI ROM via Mi Flash?
{
"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"
}
About Lineage OS:
Lin·e·age
/ˈlinēij/
noun
lineal descent from an ancestor; ancestry or pedigree.
a sequence of species each of which is considered to have evolved from its predecessor.
Disclaimer:
LineageOS (Lineage Android Distribution) members or anyone else on this website is 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 the products you find here 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. Your warranty will be void if you tamper with any part of your device / software.
Warning:
This ROM will not work on devices that have not installed the O bootloader and appropriate modem package below. Also does any build from now on require a vendor partition, by doing this you will lose the ability to flash official builds provided by ZTE. Any failure in this process of flashing or repartitioning could lead to an unrecoverable bricked device.
What's not working:
SELinux is permissive
Instructions:
Attention! The bootloader needs to be unlocked!
Attention! You'll need a vendor partition!
1. Install the Universal bootloader and your model specific modem. Download
2. Flash vendor creation tool. Download (unnecessary, if done already)
* On first flash the device will reboot, just reboot to recovery and reflash the zip.
3. Update your version of TWRP. Download
4. Perform a backup of your current ROM. (optional)
5. Wipe system,data and cache (optional) [Needed if coming from another rom!; always good to avoid bugs]
6. Install the ROM. Download
7. Install GApps. (optional) [Recommended -> Open GApps (arm64) (9.0)]
8. Reboot.
What is CAF?
Code Aurora, a Linux Foundation Collaborative Project, hosts tested open source software code needed to provide upstream enablement for innovative, performance optimized, network connectivity and related ecosystems to support system on a chip (SoC) products. It also serves as a staging area for open source code that is submitted to various upstream projects such as the Linux kernel and Android. CAF also mirrors key upstream projects for use by the community.
Sources, Changes, & Wiki:
Source | Changes | Axon 7 Wiki | Lineage OS
Credits:
@Unjustified Dev
@DrakenFX
XDA:DevDB Information
[UNOFFICIAL] LineageOS 16.0 for ZTE Axon 7, ROM for the ZTE Axon 7
Contributors
OrdenKrieger, Unjustified Dev
Source Code: https://github.com/OrdenKrieger/android_kernel_zte_msm8996
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: O bootloader + region modem
Based On: LineageOS
Version Information
Status: Testing
Created 2018-08-19
Last Updated 2019-07-28
Some features of LineageOS are missing, but they will be merged in future builds.
Some features may or may not work, sometimes also differently. Feel free to ask
any question.
UwU neat p finally
Nice.But its unclear for me...is gapps inbuild android 9 or we still need gappas package? And we can also use b12 0 bootstack from Nfound,correct?
Predatorhaze said:
Nice.But its unclear for me...is gapps inbuild android 9 or we still need gappas package? And we can also use b12 0 bootstack from Nfound,correct?
Click to expand...
Click to collapse
Read the instructions, they are there for a reason.
OrdenKrieger said:
Read the instructions, they are there for a reason.
Click to expand...
Click to collapse
Los 15 is abandoned I assume?
And 16 besides nfc and volte is functional?
Thanks for contributing.
wow. It is all happening very fast.
Thanks
OrdenKrieger said:
Read the instructions, they are there for a reason.
Click to expand...
Click to collapse
lmao,i did.There is nothing mentioned we can use nfound bootstack and it says Gapps is optionally,it doesnt say gapps is inbuild. So what do you mean with optionally? I just ask this so people are not confused,and i am one of them that is confused. OPS in threads can be a mess,or have things missed that can be important
Predatorhaze said:
lmao,i did.There is nothing mentioned we can use nfound bootstack and it says Gapps is optionally,it doesnt say gapps is inbuild. So what do you mean with optionally? I just ask this so people are not confused,and i am one of them that is confused. OPS in threads can be a mess,or have things missed that can be important.You also say its optional to wipe system data cache if come from other rom,but in fact its REQUIRED to wipe system data if you come from other rom
Click to expand...
Click to collapse
GApps is always optional because some people want them and some don't. If you read carefully, on LOS 15.1 is the same.
I have heard Android Pie got GAPPS inbuild and i believe that because google dont want microg users.So its not true...
Predatorhaze said:
lmao,i did.There is nothing mentioned we can use nfound bootstack and it says Gapps is optionally,it doesnt say gapps is inbuild. So what do you mean with optionally? I just ask this so people are not confused,and i am one of them that is confused. OPS in threads can be a mess,or have things missed that can be important
Click to expand...
Click to collapse
Why should I mention other stuff if I already provide a working bootstack. Why would I give a download link for Gapps and add the the optionally tag, if they would be build in.
thnx @OrdenKrieger and all others involved :good:
Nice build - working smooth, no lag
DT2W ok
Used bitgapps as a starter
At last NO echo and incall volume adjustable
FP working
Hotspot OK
camera pics ok, recording crashes when saving - on both pics and video lag on movement
usb preferences work
afaik there is no way in settings to reverse softkeys so i used mine : https://androidfilehost.com/?fid=3700668719832237510 (be sure to be rooted and mount system/vendor)
Notifications work - on lockscreen and leds ok
EDIT : after testing a bit, definitely more heating and i mean a lot, more cpu load (f.e. as on the PPR1 img )..... could not stabilize temp on cpu 92C ! Only after applying powersave in EXKM...definitely something to look into (only Wifi on, no BT, no specific apps running....only the basic stuff to test your build )
EDIT2 : fast charging way more heat on battery - also battery drain too fast even with no cpu load
Will test further
Has anyone tried recording a video using the camera on a clean flash? Does the camera app freeze or crash?
2000impreza said:
Has anyone tried recording a video using the camera on a clean flash? Does the camera app freeze or crash?
Click to expand...
Click to collapse
yep, tried recording now and crashes when saving. Also lag on movement.
I try to flash but brick.
I download the bootloader and modem and Twrp and install them.
TWRP from OP did not see vendor Partition.
After flashing the Rom, no Twrp booting, no System booting...just fastboot working.
Hellsbend said:
I try to flash but brick.
I download the bootloader and modem and Twrp and install them.
TWRP from OP did not see vendor Partition.
After flashing the Rom, no Twrp booting, no System booting...just fastboot working.
Click to expand...
Click to collapse
So, the OP says "FOR NOW THIS BUILD ONLY WORKS ON DEVICES WITH A VENDOR Partition". Did your device have a vendor partition before flashing this one?
ttkian said:
So, the OP says "FOR NOW THIS BUILD ONLY WORKS ON DEVICES WITH A VENDOR Partition". Did your device have a vendor partition before flashing this one?
Click to expand...
Click to collapse
Yes of course, I was running ray steffs LineageOS 16 Treble bevor
Hellsbend said:
Yes of course, I was running ray steffs LineageOS 16 Treble bevor
Click to expand...
Click to collapse
Hi mate!
You shouldnt have used another BL nor twrp if you were on Nfounds and twrp3.2.18.Just flashed this rom and rebooted would have been fine.
Try to revert back to where you came from, at least flash his twrp3.2.18 and do a restore if you can.
raystef66 said:
Hi mate!
You shouldnt have used another BL nor twrp if you were on Nfounds and twrp3.2.18.Just flashed this rom and rebooted would have been fine.
Try to revert back to where you came from, at least flash his twrp3.2.18 and do a restore if you can.
Click to expand...
Click to collapse
Thank you very much, I am on the other LineageOS again.
Flashing Nfounds Twrp through fastboot, than O Bootstack again and I could restore my backup
Maybe they should point on that in the OP here.
I will try again in a minute and report back.
Thank you again!
---------- Post added at 07:26 PM ---------- Previous post was at 06:35 PM ----------
raystef66 said:
Hi mate!
You shouldnt have used another BL nor twrp if you were on Nfounds and twrp3.2.18.Just flashed this rom and rebooted would have been fine.
Try to revert back to where you came from, at least flash his twrp3.2.18 and do a restore if you can.
Click to expand...
Click to collapse
That work's just fine.
I just tried this new build now, but it's just the same as the build you posted earlier today.
The only difference in this build....
Device information now shows Axon7 U
Same small bugs as in the other LineageOS 16 GSI plus wifi bit bugy
Signature spoofing is broken
Not worth it jet setting it up all new again.
I went back to my backup again.
Thank you again.
Edit
Of course, it's easier to flash because Post 1,2 and 3 are "included" now.
So it's quicker to flash.
Hellsbend said:
Thank you very much, I am on the other LineageOS again.
Flashing Nfounds Twrp through fastboot, than O Bootstack again and I could restore my backup
Maybe they should point on that in the OP here.
I will try again in a minute and report back.
Thank you again!
---------- Post added at 07:26 PM ---------- Previous post was at 06:35 PM ----------
That work's just fine.
I just tried this new build now, but it's just the same as the build you posted earlier today.
The only difference in this build....
Device information now shows Axon7 U
Same small bugs as in the other LineageOS 16 GSI plus wifi bit bugy
Signature spoofing is broken
Not worth it jet setting it up all new again.
I went back to my backup again.
Thank you again.
Click to expand...
Click to collapse
Not quite. Mine was derived from Redmi Note 4. It looks the same for sure but devs have done some adjustments as to ECHO, dt2w working, notifications, ....
BUT my LOS16 build had no heating, nice CPU load and no battery drain and no heating when charging at all but had the annoying echo as we know it on other gsi builds and no dt2w, no notifications working on lockscreen, no led...
So there are definitely pros from this build and pros from mine.
Hope they can manage heating.
Also back on AEX as the heating (in my case) was too heavy. Dont want to ruin anything now
{
"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"
}
Welcome to Liquid Remix! Liquid Remix is a new ROM of today, and I'm bringing it to everyone! I hope everyone in the ZTE Axon 7 community can enjoy this ROM to it's max!
Liquid Remix is a New age mix of all the best ROMs of today with added essence from the older days. Android 9.0 project based from the old lead dev of Liquid smooth, Liquid0624, along with VenkatVV, and community contributors! All features are open source and will stay that way as the community is the most important thing to our project!
Our Android Development Team is very end user oriented; we care about what you want and bringing it to you. We do as much as we can to keep our users happy while primarily focusing the aims on stability, speed, optimizations, other additions and features that complement the ROMs as well as some frequently requested user add-ons.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
[/CENTER]
Even though the ROM is tested beforehand, I cannot guarantee anything that may happen to your device. I am not responsible for anything that happens to your device.
ROM - DownloadOpen Gapps - Download
Clean flash is recommended:
Unlock the Bootloader first , and flash universial bootstack and modem before anything
1. Go to TWRP
2. Wipe System, Vendor, Data, Cache, and Dalvik Cache. Internal Storage wipe is not needed
3. Flash Kranoner's vendor or Nfound vendor (Recommended vendor) or flash another vendor of your choice. LineageOS vendor and anything based on LineageOS, like DotOS vendor will not work.
4. Extract the ROM .zip file to get system.img , flash it in system partition. , Boot and check the ROM
5. Reboot to recovery after flashing ROM and then Factory reset then flash Opengapps. Nano or below is recommended
6. Reboot to system
7. After first boot, you will need to flash NFC/Hotspot fix by @raystef66 and @kountry83 .
8. DONE! Enjoy!
ROM - LiquidRemix
Device Tree - Phh Device
Google (for AOSP)
Lineage OS (Rom Base)
@phhusson for his great work in treble development.
@yshalsager for his treble build guide.
@Unjustified Dev
@DrakenFX
@Kranoner & @NFound
special thanks for all testers in Axon7 TG group
XDAevDB Information
Unofficial LiquidRemix, GSI for ZTE Axon 7
ROM OS Version
ROM : 10.0.5
Security Patch : 5 FEB.
Status:Unofficial
Created 2018-12-11
Last Updated 2019-2-15
ComboFix that will flash NFC/Button Swap/overlay fix/magisk in one go
Aroma Combo Fix
Thanks to @raystef66
What doesn't work/bugs:
Navigation Gesture
Network Traffic will reboot system UI / crash settings but the chosen option will be applied
VOLTE , WFC
maybe other custom settings ?
What works:
- Pretty much everything else
changelog:
14-2-2019
12-1-2019
22-12-2018
FAQ
Why GSI not a normal ROM ?
- The sources are still not available/stable so the only way to get new Pie ROMs for our device is by using GSI.
TWRP says no OS after flashing system.img ?
-Thats normal , just reboot and it should boot
Phone shows the following message after every reboot "Internal problem detected..."
-That's a vendor issue, it does not do anything just press OK.
Screen freeze or unresponsive ?
-Flash the NFC/Hotspot fix.
Which vendor is recommended ?
- NFound v1.1 has less amount of issues.
Some customization options does not work ?
-Restart system UI and/or Reboot system.
Themes are broken (Dark/Black) ?
- wipe clean everything (including vendor) and use NFound vendor , follow the instructions.
Substratum does not work ?
- use this apk key and install it as normal apk
Option XYZ does not work ?
- Post your setup with detailed description and of course a LOG.
I want XYZ feature ?
- I'm only a builder not a dev, so no promises.
How stable is this ROM ?
- the ROM is very stable and can be used as daily driver.
Very interested in this ROM, will try it out
Thanks for your great efforts, buddy.
I am going to try it out.
Which universial bootstack do you recommend?
Can you kindly make a link to it?
Thanks in advance.
samichiban said:
Thanks for your great efforts, buddy.
I am going to try it out.
Which universial bootstack do you recommend?
Can you kindly make a link to it?
Thanks in advance.
Click to expand...
Click to collapse
use this one here https://androidfilehost.com/?fid=11410932744536985259
anyway if you are in official LOS15.1and its working fine you don't need to flash bootstack/modem , just follow the instructions and it should boot fine
NOTE : WIPE THE VENDOR & FLASH ANOTHER ONE OTHER WISE IT WONT BOOT.
Nice!
Glad that my guide helped
king1990 said:
use this one here https://androidfilehost.com/?fid=11410932744536985259
anyway if you are in official LOS15.1and its working fine you don't need to flash bootstack/modem , just follow the instructions and it should boot fine
NOTE : WIPE THE VENDOR & FLASH ANOTHER ONE OTHER WISE IT WONT BOOT.
Click to expand...
Click to collapse
Thanks for quick reply, king1990. Much appreciated.
My mobile is Axon7G model, and ATM Nfound's AospExtended ROM v5.8 (Rom 8.1) running.
Your ROM zip title indicates A-only but will it work fine with my Axon7G?
yshalsager said:
Nice!
Glad that my guide helped
Click to expand...
Click to collapse
Your guide was huge help , without it this ROM would never happen
samichiban said:
Thanks for quick reply, king1990. Much appreciated.
My mobile is Axon7G model, and atm Nfound's AospExtended ROM v5.8 (Rom 8.1) installed.
Your ROM zip title indicates A-only but will it work fine with my Axon7G?
Click to expand...
Click to collapse
Flash LOS15.1 and it should create vendor partition to allow you to install this ROM
it will work in both G & U models
You post a GSI in axon 7 forums,why if i may ask? This is a GSI for treble A phones,i think this should be in the treble forums only?
Predatorhaze said:
You post a GSI in axon 7 forums,why if i may ask? This is a GSI for treble A phones,i think this should be in the treble forums only
I was happy when i saw LiquidRemix,the happynes didnt last long when ive read GSI
Click to expand...
Click to collapse
Those of us who initially tested this GSI did not think it was ready for other devices outside of the Axon 7 community, as it will not boot on LOS based vendors. @king1990 built this for our community, and it was just way too good of a ROM to keep from sharing on XDA.
Once again, thanks for your opinion. /S
EBeatFLA said:
Those of us who initially tested this GSI did not think it was ready for other devices, as it will not boot on LOS based vendors. @king1990 built this for our Axon 7 community, and it was just way too good of a ROM to keep from sharing on XDA.
Once again, thanks for sharing your opinion. /S
Click to expand...
Click to collapse
My opinion is that this is a GSI for a treble devices,so thats why i thought this should be in the treble forum.
And yes im avoiding treble system for my axon 7 because its a mess.
My opinion is this ROM is hands down, THE best GSI I've used in all of my testing, and by a long shot. Seeing as how this is only the first build, I'm excited to see how future builds will improve.
The difference between using this ROM with it's suggested installation, and other ROMs of the past is like night and day, including pre-treble ROMs. This is definitely the whole package when it comes to custom ROMs. Full of options, that work, and a UI that flies with no lag, without compromising battery life.
See screenshots of estimated 6 hours SOT, almost 2 hours of which I was on a Viber phone call through Bluetooth headphones while at the same time using my phone to message on Telegram.
Where others came up short, Liquid Remix just works. I'm sure there will be many other posts like mine, giving praises to this ROM. @king1990 Thank you again, so much for building this for us. It was a much needed relief from many headaches of searching and testing and fixes and testing... Lol
XDA only rendering 1 of 2 screenshots. Here is the second one.
Followed the installation guide:
Clean flash is recommended:
Unlock the Bootloader first , and flash universial bootstack and modem before anything
1. Go to TWRP
2. Wipe System, Vendor, Data, Cache, and Dalvik Cache. Internal Storage wipe is not needed
3. Flash Kranoner's vendor (Recommended vendor) or Nfound vendor or flash another vendor of your choice. LineageOS vendor and anything based on LineageOS, like DotOS vendor will not work.
4. Extract the ROM .zip file to get system.img , flash it in system partition. , Boot and check the ROM
5. Reboot to recovery after flashing ROM and then Factory reset then flash Opengapps. Nano or below is recommended
6. Reboot to system
7. After first boot, you will need to flash NFC/Hotspot fix by @raystef66 and @kountry83 .
8. Install Magisk 18.0
However, every time boots into system, it shows error:
Android System
There's internal problem with your device. Contact your manufacturer for details.
Does it mean Vendor Partition is not right?
ccfly888 said:
However, every time boots into system, it shows error:
Android System
There's internal problem with your device. Contact your manufacturer for details.
Does it mean Vendor Partition is not right?
Click to expand...
Click to collapse
This is a false error, and is very common when using a GSI. There is nothing wrong and it affects nothing. It is a minor annoyance to click OK, only on boot.
Sometimes this will go away depending on what vendor or kernel you are using. Hopefully it may go away in the future with a better vendor or if a future Liquid build works with other vendors.
ccfly888 said:
Followed the installation guide:
Clean flash is recommended:
Unlock the Bootloader first , and flash universial bootstack and modem before anything
1. Go to TWRP
2. Wipe System, Vendor, Data, Cache, and Dalvik Cache. Internal Storage wipe is not needed
3. Flash Kranoner's vendor (Recommended vendor) or Nfound vendor or flash another vendor of your choice. LineageOS vendor and anything based on LineageOS, like DotOS vendor will not work.
4. Extract the ROM .zip file to get system.img , flash it in system partition. , Boot and check the ROM
5. Reboot to recovery after flashing ROM and then Factory reset then flash Opengapps. Nano or below is recommended
6. Reboot to system
7. After first boot, you will need to flash NFC/Hotspot fix by @raystef66 and @kountry83 .
8. Install Magisk 18.0
However, every time boots into system, it shows error:
Android System
There's internal problem with your device. Contact your manufacturer for details.
Does it mean Vendor Partition is not right?
Click to expand...
Click to collapse
Ignore it! It's nothing serious. And yes it's the vendors fault. Our vendor is a mess!
EBeatFLA said:
This is a false error, and is very common when using a GSI. There is nothing wrong and it affects nothing. It is a minor annoyance to click OK, only on first boot.
Sometimes this will go away depending on what vendor or kernel you are using. Hopefully it may go away in the future with a better vendor or future GSI build.
Click to expand...
Click to collapse
Thanks for the quick reply.
Indeed, I clicked OK and it just moves on. But it shows up on every reboot. Kind of annoying.
ccfly888 said:
Thanks for the quick reply.
Indeed, I clicked OK and it just moves on. But it shows up on every reboot. Kind of annoying.
Click to expand...
Click to collapse
Sorry, bad wording, i should have said "on boot", not "on first boot". You get used to it.
EBeatFLA said:
Sorry, bad wording, i should have said "on boot", not "on first boot". You get used to it.
Click to expand...
Click to collapse
It is minor issue. I certainly can live with that.
{
"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:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
How to Flash :
Download the twrp image
Open terminal/cmd in the folder where u have downloaded the twrp image
Connect your phone to pc and enter fastboot mode (press power and volume button together)
type in terminal : fastboot flash recovery twrp_lavender.img
Reboot to system by typing : fastboot reboot or reboot to recovery by holding power and volume up button
Bugs :
Encryption (MIUI)
Download Link :
Click Here
XDA:DevDB Information
[RECOVERY][UNOFFICIAL] TWRP-3.3.0 [Lavender], ROM for the Xiaomi Redmi Note 7
Contributors
letsmakecakes
Source Code: https://github.com/TeamWin
ROM OS Version: 4.2.x Jelly Bean
Version Information
Status: Testing
Created 2019-04-23
Last Updated 2019-04-24
MOD EDIT by @gregbradley
There is never a need to quote the whole OP
dude, you rock bro
maintaining both LOS and this
Thank you and others for the work. Can't wait for unlock to try all these
every time I want to enter recovery always asks for a password and decrypt data?
BungSandz said:
every time I want to enter recovery always asks for a password and decrypt data?
Click to expand...
Click to collapse
Me too
Thanks. If I undesrstand well, we have to set encryption off before we flash it for the first time to get it work?
BungSandz said:
every time I want to enter recovery always asks for a password and decrypt data?
Click to expand...
Click to collapse
The OP said that there is a bug with encryption. That is what you are experiencing. You either have to wait until the encryption issue is solved, or, you have to format your data partition (which, of course, means that you will lose all the contents of your internal storage).
BungSandz said:
every time I want to enter recovery always asks for a password and decrypt data?
Click to expand...
Click to collapse
Well yeah , if you are on miui it will keep asking for password to decrypt data...
For now what you can do is , put ur stuffs that u wanna flash on sd card while on a rom and then reboot to twrp and flash it...
Unless the rom has decryption method , all roms will have similar issues with this twrp
Issue 1-1
DarthJabba9 said:
The OP said that there is a bug with encryption. That is what you are experiencing. You either have to wait until the encryption issue is solved, or, you have to format your data partition (which, of course, means that you will lose all the contents of your internal storage).
Click to expand...
Click to collapse
Thank you man i waiting for OrangeFox recovery for redmi note 7 by you
I love you OrangeFox
hussein1 said:
Thank you man i waiting for OrangeFox recovery for redmi note 7 by you
I love you OrangeFox
Click to expand...
Click to collapse
Well, we don't have the device. But if you are feeling brave and would like to test some beta builds, let me know by PM.
@letsmakecakes is on fire this time, go ahead brah ?
Hallo,
I install twpr, all succesfull. But I reboot Volume + and power boot only Redmi recovery 3.0. Thank you for help. Redmi Note 7 Global
If you install recovery on stable build of miui you will lost twrp after reboot. You have to flash custom rom like xiaomi.eu rom right after flashing twrp
This twrp https://forum.xda-developers.com/re...overy-unofficial-twrp-touch-recovery-t3921637 works after flashing on stable rom. Tested.
Julex said:
This twrp https://forum.xda-developers.com/re...overy-unofficial-twrp-touch-recovery-t3921637 works after flashing on stable rom. Tested.
Click to expand...
Click to collapse
+1
Worked fine for me, currently on the stable rom, while this one were erased at each reboot.
TWRP has been updated with fixed encryption.
feels risky to use ROM created by someone who states "Never trust anyone too much, remember the devil was once an angel." in his signature..
kennyk09 said:
feels risky to use ROM created by someone who states "Never trust anyone too much, remember the devil was once an angel." in his signature..
Click to expand...
Click to collapse
Trust issues. Lol!
[removed]