Database Info

[Rom] Official Lineage OS 14.1 for Falcon

Lin·e·age
/ˈlinēij/
noun
1.lineal descent from an ancestor; ancestry or pedigree.
2.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.
Download & Install
LINKs:
Rom
Changelog
OpenGapps choose ARM>7.1>micro/nano/pico (micro might still be too big... unless you use the custom install options that allows you not to install everything from the package)
REMEMBER:
ONLY use TWRP 3.0.2-1 or up​HOW TO INSTALL
Requirements: Unlocked Bootloader, a Nougat compatible Custom Recovery and the Downloaded Zips.
1.Place the rom and other like Gapps on the internal Storage or on a USB OTG
2.Reboot to recovery using the hotkey ( PowerOff+Vol- => With Vol- Go to Recovery => Select the recovery option with Vol+ )
3.Do Wipes (Data, Cache, Dalvik and System partitions) if you are in a different ROM.
4.Select the Zips
5.Swipe to install (if using TWRP)
6.Reboot and wait 2-3 min​
Flash This to have system root access
READ POST 2 BEFORE FLASHING
XDA:DevDB Information
[Rom] Lineage OS 14.1 for Falcon, ROM for the Moto G
Contributors
Allstargaurav
Source Code: https://github.com/lineageos
ROM OS Version: 7.x Nougat
ROM Firmware Required: CyanogenMod13
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2017-01-21
Last Updated 2017-01-26

HOW TO DIRTY UPDATE
1.Download the rom zip
2.Reboot to recovery using the power menu or the hotkey ( PowerOff+Vol- => With Vol- Go to Recovery => Select the recovery option with Vol+ )
3.Do Wipes (Cache, Dalvik)
4.Flash the Zip(No Need To flash Gapps)
5.Reboot and wait 2-3 min
HOW TO CLEAN UPDATE :
1.Download the rom zip and make sure you have gapps zip on your device
3.Reboot to recovery using the power menu or the hotkey ( PowerOff+Vol- => With Vol- Go to Recovery => Select the recovery option with Vol+ )
5.Format /system, /cache and /dalvik-cache (advance format in wipe menu of TWRP); do NOT Wipe DATA
6.Install zip
7.Reboot and wait 2-3 min
EXPERIMENTAL:-This build will allow you to ‘upgrade’ from CM to the signed LineageOS weekly
How To install EXPERIMENTAL
1.Download experimental and nightly zip
2.Boot into Recovery
3..Install experimental migration build on top of cm-14.1 build
4.Reboot
5.Install LineageOS weekly build
6.Reboot
7.Re-setup your application permissions

You might want to state that this is not the official version. There might be a bit of confusion otherwise because official builds will be available this weekend.

ahmad.o said:
You might want to state that this is not the official version. There might be a bit of confusion otherwise because official builds will be available this weekend.
Click to expand...
Click to collapse
Is it Better Now

It's better to put unofficial tag in title too. Not just as announcement. People might not notice it.
Edit: Just saw your edit.

Please ask a moderator to post it on the android development, doesn't belong here.

Aayushya said:
Please ask a moderator to post it on the android development, doesn't belong here.
Click to expand...
Click to collapse
I will make this Offical Lineage thread as soon as weekly starts rolling

Lineage based on aosp?

Any screenshoots?

Pierre2324 said:
Lineage based on aosp?
Click to expand...
Click to collapse
its more cm based

Great?

Testing. So far so good.

Just installed on xt1032 and looks amazing! Does this get OTA? Or do I have to flash new roms?

What about ram usage Nougat seems bad always low ram on every rom

Pierre2324 said:
What about ram usage Nougat seems bad always low ram on every rom
Click to expand...
Click to collapse
to me is about 240 mb free, anyway nougat runs very well

Wifi sometimes turn down. This is unique bug I found

Working without issues here. :good::good::good:

fix for bluetooth pairing?

Reserved...

Is the op actually a contributor or just putting the thread up?

[Latest][MT6582]TWRP 3.1.1-0 For Micromax Unite 2 (Stable)

HTML:
* 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 Recovery
* 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.
Changelog :-
Based On Omni Sources
Fixed Invert Touch & Invert Screen
Fixed Late Wipe Cache
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Downloads :-
TWRP 3.1.1-0 (Flashable Zip)
Flashing instructions :-
Reboot Into you installed Custom Recovery.(for e.g TWRP,CTR,CWM,PHILZ)
Select "TWRP_3.1.1_Compiled_Fixed_.zip" and Flash.
Reboot into Recovery to see newly Installed TWRP Recovery
Done .
Device Tree :- https://github.com/EndLess728/TWRP_Miromax_Unite_2.git
XDA:DevDB Information
TWRP 3.1.1-0 For Micromax Unite 2 (A106)
Contributors
EndLess, manjot.gni, Anurag D'Cruz ,Divyrajsinh Jadeja
Source Code: https://github.com/omnirom/android_bootable_recovery
Kernel Special Features: Fixed Invert Touch & Invert Screen
Version Information
Status: Stable
Current Stable Version: TWRP 3.1.1-0
Stable Release Date: 2017-07-01
Created 2017-07-01
Last Updated 2017-07-01

Awesome Bro

Thanks, found an issue - there is no option to boot into bootloader

mGforCe said:
Thanks, found an issue - there is no option to boot into bootloader
Click to expand...
Click to collapse
our device dont have bootloader thats why i removed it

EndLess said:
our device dont have bootloader thats why i removed it
Click to expand...
Click to collapse
But other recoveries have same and using that we can boot into fastboot mode!

mGforCe said:
But other recoveries have same and using that we can boot into fastboot mode!
Click to expand...
Click to collapse
i removed that option to reboot in to bootloader beacause in this device it doesnt support

After flashing and booting into recovery the screen goes black and reboot to system

Mukesh kalaga said:
After flashing and booting into recovery the screen goes black and reboot to system
Click to expand...
Click to collapse
Same here , i even tried Flashify which shows Error and Rashr showed Success , but after rebooting to recovery , it boots back to system.

its working fine on me. but could you please update to latest version with otg support.

[rom][treble][9.0][huawei p9]

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.
/*
* 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.
*/
Requiriments:
Stock EMUI 8.0
STOCK RECOVERY_RAMDISK
STOCK RAMDISK
THIS ROM WORKS WITH HI3650 DEVICES AND HI6250 DEVICES (WITH TREBLE)
Working:
*All* *Apart Camera*
FLASH LKT IN MAGISK FOR FIX UI MICRO-LAGS
Bugs:
Camera (Working on it)
When the rom boot shows a error but nothing important (For now no)
Installation:
Flash Stock EMUI 8.0
Don't setup anything
Flash stock ramdisk
Now flash this twrp: https://mega.nz/#!xUcBxKLZ!MJv5xk86GAJOEKl1KRS-tKr5wvkBFTOI0DgosaEUkXA
Select English language
Go to Wipe-Advanced Wipe-And wipe only system
Now copy the rom to SD CARD OR Internal Storage
Flash the rom
NOW FLASH STOCK RECOVERY_RAMDISK (VERY IMPORTANT)
Reboot to Emui recovery
Wipe cache
Wipe data (if the recovery fails its normal)
Now reboot to system
Setup what do you want
----------------------------------------------------------------------GAPPS---------------------------------------------------------------------------------
FIXED:MAKE SURE THE ROM BOOTED
NOW DOWNLOAD THE NANO PACKAGE OF GAPPS
REBOOT TO MY TWRP : https://mega.nz/#!xUcBxKLZ!MJv5xk86GAJOEKl1KRS-tKr5wvkBFTOI0DgosaEUkXA
FLASH GAPPS
IF TWRP SAYS UNABLE TO MOUNT SYSTEM ITS NORMAL JUST REBOOT
ENJOY GOOGLE APPS
Link: https://opengapps.org/
Select arm64 9.0 nano
---------------------------------------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------LINKS-----------------------------------------------------------------------------------
Rom:
MEGA: https://mega.nz/#!MRthiAhJ!nxDU4O1rxEoLoYo1r_n0gaZodwKB4KAcV25mej7gh_g
GOOGLE DRIVE: https://drive.google.com/open?id=111OfwRDG09uAbG-RPDv8xijt9JxVdeB9
---------------------------------------------------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------Magisk-------------------------------------------------------------------------------------
DON'T FLASH NORMAL MAGISK BECAUSE CAUSES BOOTLOOP
FLASH IANMACD MAGISK
MEGA: https://mega.nz/#!oEdjHaRB!MdqyZvgk4lvkkfOOVk16vEeqAH5Uc7v_fjzVvSoXEk8
IF AFTER INSTALLATION YOU SEE UNABLE TO MOUNT SYSTEM OR SOMETHING LIKE THIS IS NORMAL
IF AFTER INSTALLATION AND REBOOTED TO SYSTEM YOU DON'T SEE MAGISK MANAGER IS NORMAL JUST REBOOT TO RECOVERY AND
FLASH IT AGAIN
---------------------------------------------------------------------------------------------------------------------------------------------------------------
I HAVE UPLOADED SCREENSHOTS
--------------------------------------------------------------------------Credits-------------------------------------------------------------------------------------------
@Tecalote 
 @korom42
 @ianmacd
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
XDA:DevDB Information
LineageOS 16, ROM for the Huawei P9
Contributors
sasi2006166
ROM OS Version: 9.x Pie
Version Information
Status: Beta
Created 2019-01-20
Last Updated 2019-01-20

ScreenShots:
https://imgur.com/a/bhUJe1y

Deleted
Post #2 for screenshots

sasi2006166 said:
...
Requiriments:
Stock EMUI 8.0
...
THIS ROM WORKS WITH HI3650 DEVICES AND HI6250 DEVICES (WITH TREBLE)
...
Installation:
Flash Stock EMUI 8.0
...
Now flash this twrp: https://mega.nz/#!xUcBxKLZ!MJv5xk86GAJOEKl1KRS-tKr5wvkBFTOI0DgosaEUkXA
...
Now copy the rom to SD CARD OR Internal Storage
Flash the rom
....
REBOOT TO MY TWRP : https://mega.nz/#!xUcBxKLZ!MJv5xk86GAJOEKl1KRS-tKr5wvkBFTOI0DgosaEUkXA
...
LineageOS 16, ROM for the Huawei P9
...
Click to expand...
Click to collapse
Is this TWRP-8.0.0-EVA-DECRYPTION SUPPORT.img your port of TWRP, and is it based on TWRP 3.1.1 or newer?
When you say it is for P9 EVA with stock EMUI 8.0.0, does it mean that this TWRP works with EVA-AL10c00b535 as obtained by rebranding P9 L09/L19 with HWOTA7 method
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
By its name, Decryption Supported, does it really mean that this TWRP can access Internal memory and Data partition under P9 stock Oreo?
Btw, Huawei P9, EVA, comes with HiSilicon Kirin 955, but you refer above HI3650 and HI6250 - so is this TWRP really for Huawei P9 EVA with stock Oreo (EMUI 8.0.0)?

This TWRP from China does not have decryption support
@zgfg to answer some of your questions:
1) "MY TWRP" - which is mentioned in OP is not correct because it is a TWRP from China - that means it is not developed by @sasi2006166
2) You can not flash this TWRP because the name contains a space: TWRP-8.0.0-EVA-DECRYPTION SUPPORT.img - if you want to test, you must first rename it.
3) This TWRP does not have decryption support. Decryption support means that it would be possible to access the encrypted internal storage without the need to format data. This is not the case, the internal memory has 0 MB and no content.
4) This TWRP has version 3.2.1.0 and it's not that bad - but it has bugs. I tested it a few months ago, in October 2018. I tested all features and found that partitions recovery is not working properly
→ For this reason, I have to say that the TWRP developed by @Pretoriano80 which we use, is much better. Everything works, except that it does also not have access to the encrypted internal storage: https://androidfilehost.com/?fid=1322778262903998750
→ But we would not say it has decryption support, when it is not the case.
5) Huawei P9 HiSilicon Hi3650 (Kirin 950/955/) is correct.

Tecalote said:
1) "MY TWRP" - which is mentioned in OP is not correct because it is a TWRP from China - that means it is not developed by @sasi2006166
2) You can not flash this TWRP because the name contains a space: TWRP-8.0.0-EVA-DECRYPTION SUPPORT.img - if you want to test, you must first rename it.
3) This TWRP does not have decryption support. Decryption support means that it would be possible to access the encrypted internal storage without the need to format data. This is not the case, the internal memory has 0 MB and no content.
4) This TWRP has version 3.2.1.0 and it's not that bad - but it has bugs. I tested it a few months ago, in October 2018. I tested all features and found that partitions recovery is not working properly
→ For this reason, I have to say that the TWRP developed by @Pretoriano80 which we use, is much better. Everything works, except that it does also not have access to the encrypted internal storage: https://androidfilehost.com/?fid=1322778262903998750
→ But we would not say it has decryption support, when it is not the case.
5) Huawei P9 HiSilicon Hi3650 (Kirin 950/955/) is correct.
Click to expand...
Click to collapse
Thanks for testing and elaborating.
I tried also now this TWRP (it says developed by www.7to.cn) and indeed it cannot read Internal memory, neither Data partition (showing both as empty).
Hence the claim about installing LOS ROM from External SD or Internal memory (post #1 above) is wrong, this TWRP also can only read (and install something) from External SD, not from Internal memory
Btw, this TWRP is based on 3.2.1.0, just like TWRP from Pretoriano80, but this one has non-standard, more colourful UI
(Didn't test does it correctly support recovery ramdisk partition)
PS: OpenKirin ROMs should be flashed by Fastboot, not from TWRP (it doesn't work from TWRP, even when TWRP finds OK ROM img on External SD)
I'm also wondering is this really here a new Treble LOS ROM, or just the one from OpenKirin team (for which other users also reported some problems with camera upon rebooting or so)
https://forum.xda-developers.com/p9/development/roms-openkirin-aosp-collection-t3828806
https://openkirin.net/user_guide/openkirin-rom-installation-instructions/

Great work and thank you .hope the bugs will be fixed soon!

The TWRP is ONLY for Huawei p9
The rom is a fleshable zip
This ROM supports hi6250 and hi3650 devices
The twrp is modified by me for working decryption
For working decryption you have to follow the instructions for installing the rom

Tecalote said:
@zgfg to answer some of your questions:
1) "MY TWRP" - which is mentioned in OP is not correct because it is a TWRP from China - that means it is not developed by @sasi2006166
2) You can not flash this TWRP because the name contains a space: TWRP-8.0.0-EVA-DECRYPTION SUPPORT.img - if you want to test, you must first rename it.
3) This TWRP does not have decryption support. Decryption support means that it would be possible to access the encrypted internal storage without the need to format data. This is not the case, the internal memory has 0 MB and no content.
4) This TWRP has version 3.2.1.0 and it's not that bad - but it has bugs. I tested it a few months ago, in October 2018. I tested all features and found that partitions recovery is not working properly
→ For this reason, I have to say that the TWRP developed by @Pretoriano80 which we use, is much better. Everything works, except that it does also not have access to the encrypted internal storage: https://androidfilehost.com/?fid=1322778262903998750
→ But we would not say it has decryption support, when it is not the case.
5) Huawei P9 HiSilicon Hi3650 (Kirin 950/955/) is correct.
Click to expand...
Click to collapse
Don't use Pretoriano TWRP it causes bootloop
This twrp works very well
And the decryption works

sasi2006166 said:
The TWRP is ONLY for Huawei p9
The rom is a fleshable zip
This ROM supports hi6250 and hi3650 devices
The twrp is modified by me for working decryption
For working decryption you have to follow the instructions for installing the rom
Click to expand...
Click to collapse
Maybe you uploaded the not modified TWRP?
Because it's absolutely the same TWRP which I tested in October 2018 for P9.
It has absolutely the same md5 checksum as the one you have uploaded.
If it would be modified, the md5 checksum would be different.
On EMUI Decryption is not working. I tested it yesterday and @zgfg too.
For this reason I can't imagine that decryption would work after flashing your Rom.
When you say "copy Rom to the internal storage" - we couldn't do this with this TWRP, because it is not accessible.
What's your understanding of "Decryption is working"?
If you mean in your Install Guide to format data (instead of wipe data) then data would be decrypted.
But this is not the sence of "working decryption" and can also be done with TWRP by Pretoriano.

Tecalote said:
Maybe you uploaded the not modified TWRP?
Because it's absolutely the same TWRP which I tested in October 2018 for P9.
It has absolutely the same md5 checksum as the one you have uploaded.
If it would be modified, the md5 checksum would be different.
On EMUI Decryption is not working. I tested it yesterday and @zgfg too.
For this reason I can't imagine that decryption would work after flashing your Rom.
When you say "copy Rom to the internal storage" - we couldn't do this with this TWRP, because it is not accessible.
What's your understanding of "Decryption is working"?
If you mean in your Install Guide to format data (instead of wipe data) then data would be decrypted.
But this is not the sence of "working decryption" and can also be done with TWRP by Pretoriano.
Click to expand...
Click to collapse
I'm my case the decryption works
You need to go to advanced fix decryption

sasi2006166 said:
I'm my case the decryption works
You need to go to advanced fix decryption
Click to expand...
Click to collapse
That Advanced Fix for decryption works only for Lineage or also for stock Oreo?

zgfg said:
That Advanced Fix for decryption works only for Lineage or also for stock Oreo?
Click to expand...
Click to collapse
In lineage works
I haven't tried on oreo
Whatever I need help for fixing camera
On hi6250 the camera works
Oy on hi3650 series doesnt work

For Working decryption on LineageOS 16
Flash the Chinese TWRP in fastboot
Reboot to recovery
Go to wipe advanced wipe and wipe ONLY system
Now go to wipe and select FORMAT DATA and type YES
Now flash ONLY the rom (no google apps or anything)
When the rom is flashed reboot to fastboot
Flash stock emui recovery
Reboot to emui recovery
DO first wipe cache, then wipe data
Now boot the rom
Setup what do you want
Now reboot to fastboot
Flash the Chinese TWRP
Now flash gapps (see the decryption in working)
Flash magisk (read OP #1)
Reboot to system
Enjoy

@zgfg Fix decryption alone does not work on EMUI (because I have tested too in October 2018) - EMUI doesn't work properly if data is formatted and @sasi2006166 it works on Lineage only because of FORMAT data - don't know if combination with Fix decryption is necessary.

Tecalote said:
If you mean in your Install Guide to format data (instead of wipe data) then data would be decrypted.
Click to expand...
Click to collapse
sasi2006166 said:
Flash the Chinese TWRP in fastboot
Reboot to recovery
Go to wipe advanced wipe and wipe ONLY system
Now go to wipe and select FORMAT DATA and type YES
Now flash ONLY the rom (no google apps or anything)
When the rom is flashed reboot to fastboot
Flash stock emui recovery
Reboot to emui recovery
DO first wipe cache, then wipe data
Now boot the rom
Setup what do you want
Now reboot to fastboot
Flash the Chinese TWRP
Now flash gapps (see the decryption in working)
Flash magisk (read OP #1)
Reboot to system
Enjoy
Click to expand...
Click to collapse
In this guide you never use Advanced Decryption fix option from TWRP?
Also, once you do Format Data then Encryption is gone, isn't it - as @Tecalote previously commented
For camera - did you try / look into OpenKirin LOS, RR or Omni Pie, they have integrated GApps and camera, but they don't provide source code for their Treble ROMs

I have tried with emui 8 stock camera
And also with openkirin omnipie camera but nothing

sasi2006166 said:
I have tried with emui 8 stock camera
And also with openkirin omnipie camera but nothing
Click to expand...
Click to collapse
You can try this, User tested it also on P9 and told it would work.
https://forum.xda-developers.com/p10/themes/google-camera-kirin-t3771927

could someone test this? https://forum.xda-developers.com/pr...opment/kirin-huawei-camera-android-p-t3840110
and does 4g lte work?

kristiansja said:
could someone test this? https://forum.xda-developers.com/pr...opment/kirin-huawei-camera-android-p-t3840110
and does 4g lte work?
Click to expand...
Click to collapse
So far I understand @sasi2006166 has already tried this camera and it does not work.
LTE I don't know, because I haven't currently not tested the Rom

[RECOVERY][OFFICIAL][TWRP - 3.3.1-0][Xiaomi Redmi Note 7 PRO]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DISCLAIMER:​
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.
*/
INFORMATION:​
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 which are functions often unsupported by stock recovery images. It is, therefore, often installed when flashing, installing or rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Read more about TWRP here: https://twrp.me/about/​
NOTE : ​
This build of TWRP is based on the kernel source code and no prebuilt kernel was used for building. Because, it is the first build, testers are very welcome for providing feedback regarding the build. ​
CHANGELOG (3.2.3.0) :​
WHAT'S NEW?
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files​
CHANGELOG (3.3.0.0) :​
WHAT'S NEW?
* Merge AOSP 9.0 r3 (Dees_Troy)
* Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)
* Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)
* vold decrypt updates (CaptainThrowback and nijel8)
* Support vibration on LED class devices (notsyncing)
* Metadata decrypt support for Pixel 3 (Dees_Troy)
* Support rotating the display via build flag (vladimiroltean)
* Reboot to EDL mode button (mauronofrio)
* Support MTP on FFS devices (bigbiff)
* Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
* Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
* Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
* TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
* Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
* Use magiskboot to allow repacking boot images for installing TWRP (Dees_Troy with thanks to topjohnwu of course)​
* Also, there was a major bug with the previous build which prevented the flashing of any file because of the "digest-verification" has been fixed with this release. Enjoy!
CHANGELOG (3.3.1-0) :
WHAT'S NEW?
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff​
DOWNLOAD :​
You can download the latest build of the TWRP from the official site here:​
TWRP(Official)​
BUGS:​
Encryption (for MIUI)
INSTRUCTIONS :​
Download the recovery image and place it in some folder on your desktop and open the Terminal/Command Prompt/Powershell in the said folder.
Connect your device to the PC and boot into the fastboot mode using H/W keys or by typing :
Code:
adb reboot bootloader
Now, type :
Code:
fastboot flash recovery twrp-3.3.0-0-violet.img
OR,
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
Download the recovery image from the link.
Reboot to TWRP.
Hit Install and tap the "Images..." button in the lower right
Browse to the location of the TWRP image on your device and select it.
Select recovery from the partition list and swipe to flash.
For users who are running MIUI : ​
Thanks to Snehashis Sarkar for a short tutorial.
Your data will get wiped before flashing the recovery so take a backup of the internal storage.
Reboot to fastboot.
Wipe the Userdata via fastboot.
Flash this recovery.
Boot into the recovery and format the data (just format it, don't go for the "advanced wipe" section .
Flash this image file: Patched fstab + vbmeta + thermal configs for better performance
Reboot and enjoy.
CREDITS: ​
TwrpBuilder for trees​
Kernel Source : ​
Link: android_kernel_xiaomi_sm6150
XDA:DevDB Information
[RECOVERY][OFFICIAL][TWRP - 3.3.1-0][Xiaomi Redmi Note 7 PRO], Tool/Utility for the Xiaomi Redmi Note 7 Pro
Contributors
Doomsday101
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-05-11
Current Beta Version: 3.3.0-0
Beta Release Date: 2019-04-03
Created 2019-04-02
Last Updated 2019-05-23

Reserved

Not able to Boot.
1. Fastboot boot twrp_violet.img not working.. Phone reboots normally.
2. So booted TWRP manually (Volume Up + Power) And Phone stuck on TWRP Logo Screen.
See the attachments for more info.

Thank you for your build !
Do you know if someone started to work on porting ROMs ?

diamantik said:
Thank you for your build !
Do you know if someone started to work on porting ROM's ?
Click to expand...
Click to collapse
I don't know if someone is working on ROMs but it is likely because of the unreliable kernel source ATM by Xiaomeme.

Vatumb said:
Not able to Boot.
1. Fastboot boot twrp_violet.img not working.. Phone reboots normally.
2. So booted TWRP manually (Volume Up + Power) And Phone stuck on TWRP Logo Screen.
See the attachments for more info.
Click to expand...
Click to collapse
Can you send me the logcat of the kmsg file present in the /proc directory using adb shell when the twrp is stuck on bootlogo?

Doomsday101 said:
I don't know if someone is working on ROMs but it is likely because of the unreliable kernel source ATM by Xiaomeme.
Click to expand...
Click to collapse
Ok thank you
I had order my device , when i will receive it , i will try to help the community with what i can , i will be glad to test things , and develop them , hopefully we can get more devs , and together we can maintain the development for RN7 Pro alive

diamantik said:
Ok thank you
I had order my device , when i will receive it , i will try to help the community with what i can , i will be glad to test things , and develop them , hopefully we can get more devs , and together we can maintain the development for RN7 Pro alive
Click to expand...
Click to collapse
Sure thing ?

It will boot, try fastboot erase userdata, but you can't flash any ROM (MIUI) atm, as it has encryption bug, which needs to be fixed by the OP!
Vatumb said:
Not able to Boot.
1. Fastboot boot twrp_violet.img not working.. Phone reboots normally.
2. So booted TWRP manually (Volume Up + Power) And Phone stuck on TWRP Logo Screen.
See the attachments for more info.
Click to expand...
Click to collapse

Has anyone else tested this and does it seem to be working fine? I'm quite scared in flashing recoveries :/
---------- Post added at 09:28 PM ---------- Previous post was at 08:34 PM ----------
twrp's stuck on the twrp logo btw

moriyaprateek said:
Has anyone else tested this and does it seem to be working fine? I'm quite scared in flashing recoveries :/
---------- Post added at 09:28 PM ---------- Previous post was at 08:34 PM ----------
twrp's stuck on the twrp logo btw
Click to expand...
Click to collapse
The recovery has the encryption bug atm as stated by @talk2indrajit in the last post. So, you will have to erase userdata via fastboot first. I suggest you take a backup, get rid of Miui and continue with the said process and flash the newly built LOS16 by @Dyneteve (if you seek to flash a custom ROM).

Can anyone update the twrp to 3.0.3?

Not able to flash vbmeta.img fastboot mode..
Is any other way to flash vbmeta without fastboot mode because my platform tools fastboot not work gives error unknown fastboot command.. Please replay..

Aj51 said:
Is any other way to flash vbmeta without fastboot mode because my platform tools fastboot not work gives error unknown fastboot command.. Please replay..
Click to expand...
Click to collapse
Download latest adb from here
https://developer.android.com/studio/releases/platform-tools

When can it decrypt /data?

Vatumb said:
Not able to Boot.
1. Fastboot boot twrp_violet.img not working.. Phone reboots normally.
2. So booted TWRP manually (Volume Up + Power) And Phone stuck on TWRP Logo Screen.
See the attachments for more info.
Click to expand...
Click to collapse
Same problem happen with me

kishangupta009 said:
Same problem happen with me
Click to expand...
Click to collapse
Don't use this command, it was mentioned somewhere, it doesn't work for now, you need to flash it , fastboot flash recovery recname.img.

Guys this TWRP is not working , gets stuck at TWRP logo !
Try the another : https://forum.xda-developers.com/re...ficial-3-2-3-redmi-note-6-pro-violet-t3912400

ok, so here's an anecdote.
when i flashed it for the first time using fastboot command, i got it stuck on the logo as well. then i looked it up, and i found this vbmeta thing, which i don't really know what is. got it to flash using platform tools (vbmeta), then flashed the other twrp on this site, and booted into it. (went with the other twrp because that is what the youtube video was using as well, and i just wanted to get over the loop, didn't think to test out)
so, successfully booted into twrp(OTHER)
from there i had to flash the lineage vendor patch cuz can't load any roms (that i tried) without it. tried flashing rom and gapps, worked. this works, no problem. (maybe some of you might want to check if the vbmeta thing was required, or if you can straight flash the older twrp from commands.)
then i went back, wiped out stuff (cache,dalvik, system and data, NOT vendor) and i flashed twrp(THIS) using twrp(OTHER), just to see
got twrp(THIS) to boot successfully.
problem here now is that it spits an error on fkin digest verification for any rom. if i can't even flash a rom, i can't get beyond that. error being "digest verification failed" or something like that.
im tired of this twrp, someone should maybe test things out further, idk where to go from here. this just flat out doesn't work.

kuhru said:
ok, so here's an anecdote.
when i flashed it for the first time using fastboot command, i got it stuck on the logo as well. then i looked it up, and i found this vbmeta thing, which i don't really know what is. got it to flash using platform tools (vbmeta), then flashed the other twrp on this site, and booted into it. (went with the other twrp because that is what the youtube video was using as well, and i just wanted to get over the loop, didn't think to test out)
so, successfully booted into twrp(OTHER)
from there i had to flash the lineage vendor patch cuz can't load any roms (that i tried) without it. tried flashing rom and gapps, worked. this works, no problem. (maybe some of you might want to check if the vbmeta thing was required, or if you can straight flash the older twrp from commands.)
then i went back, wiped out stuff (cache,dalvik, system and data, NOT vendor) and i flashed twrp(THIS) using twrp(OTHER), just to see
got twrp(THIS) to boot successfully.
problem here now is that it spits an error on fkin digest verification for any rom. if i can't even flash a rom, i can't get beyond that. error being "digest verification failed" or something like that.
im tired of this twrp, someone should maybe test things out further, idk where to go from here. this just flat out doesn't work.
Click to expand...
Click to collapse
Thank you for trying it out previously. I have released a new build today with the latest TWRP version (3.3.0.0) and now the "digest-verification" bug has been fixed.

[Q][TREBLE VENDOR][J4CORELTE][PROJECT TREBLE VENDOR FOR J4CORELTE V2]

/*
* 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.
*
*/
Hi everyone i want to share a gsi vendor image that boots most Q and P roms for the samsung galaxy j4 core.
How to install:
reboot to twrp go to format data type yes *this will format all your data*
go back to wipe and select system,vendor,cache,data and dalvik then swipe to wipe
go to install click on install image select the gsi image file then swipe to flash
now select install zip and click on the vendor image you have downloaded and swipe to flash
finally you can flash gapps if your gsi doesn't include them *note: if you dont have enough space to install gapps to to wipe select system and select repair or change file system click on resize system then swipe to reisze*
and if you are into rooting flash magisk zip file
note try to not install gsi roms that aren't over 1.2gb lineageos 17.1 and dotos are prefered
BUGS:
none
What works:
-boots
-offline charging
-sound
-wifi
-gps
-bluetooth
-mtp
-RIL
if you want to report a bug be sure to include logcat
After this thread started to gain downloads, i decided pushed another update with improved peformance!
Download:
V2 Google drive: https://drive.google.com/file/d/1z-OrGTjv9HD9SL2j30EYyUA__xjmhIaR/view?usp=sharing
V1 Google drive: https://drive.google.com/file/d/14-XNmD_19Mt-dFSReBZk8luoeY2ZoD9r/view?usp=sharing
Credits:
@leohiper10 for the sources and allowing me to use his vendor image from his lineageos 16 build (doesnt use his vendor build anymore with V2).
myself for taking my time to test and fix the bugs
XDA: DevDB Information
Fggevhy Vendor for galaxy j4 core
ROM OS Version: 10 Q
ROM Kernel: Linux 3.x
ROM Firmware Required: latest bootloader and dtbo
Based On: Project Treble
Version Information
Status: Stable
Current Stable Version: V2.0
Current Beta Version: V2.0
Stable Release Date: 2021-11-08
Created 2021-09-20
Last Updated 2021-11-08

happy flashing!

Forgot to mention that the gsi image must be arm Aonly i will add that later

Changelog: 08/11/2021
-.img format instead of flashable zip
-Set screen density to 411
-Fixed pretty much all bugs in the older release
-Fixed Unknown baseband bug and unkown imei with old version on j410f
-Better peformance!
Changelog: 22/10/2021
-baked custom kernel onto it
-fixed call audio
-fixed crashing issue of qcrilmsg (responsable for ril)
-fixed wifi issue on j410F
-fixed dual sim on J410F/DS

How u fixed call audio ?

I tried flashing lineage and aosp. With both after going through the process, when I reboot system in twrp, it always reboots to download mode.
Device model: sm-j410f

NsovoXD said:
I tried flashing lineage and aosp. With both after going through the process, when I reboot system in twrp, it always reboots to download mode.
Device model: sm-j410f
Click to expand...
Click to collapse
try with orangefox
also if you have issues flash the first release of the vendor then update to v2

Has anyone tried this /vendor with a Lineage 18.1 GSI? Asking for a friend.

LegoLivesMatter said:
Has anyone tried this /vendor with a Lineage 18.1 GSI? Asking for a friend.
Click to expand...
Click to collapse
should work!