Develop Bugs

[PATCHER][APP] Dual Boot Patcher [OFFICIAL SNAPSHOT]

This tool/app will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary
Donators
A huge thanks goes out to all of the donators for supporting this project! I if forgot to add you (and you want to be added), please send me a quick PM.
See all of our supporters here: https://gist.github.com/chenxiaolong/3f3fb485cbd0cb77c4281941433ec54d
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot an EUI ROM, I highly recommend installing EUI as the primary ROM.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.​
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!​
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.​
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.​
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.​
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it ​
Downloads:
[LINK] Dual Boot Patcher (Snapshots) and DualBootUtilities recovery zip
Donations:
Donations are not required, but are greatly appreciated Donators will have their names listed in a nice big font on this post and will also be listed in the README file of the patcher.
Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Please note, any bugs regarding app itself can be created over at https://github.com/chenxiaolong/DualBootPatcher/issues
Any other device-specific stuff can be asked over here itself.
XDA:DevDB Information
Dual Boot Patcher, Tool/Utility for the LeEco Le 1S
Contributors
chenxiaolong, DroidThug, https://github.com/chenxiaolong/DualBootPatcher/graphs/contributors
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Snapshot
Current Beta Version: 9.2.0.r25.g0638efb
Beta Release Date: 2017-04-11
Created 2017-04-11
Last Updated 2017-04-11

FAQ
What does this do:
It allows you to multiboot between ROMs
What does it require:
It requires an unlocked bootloader, and root access
I have problems regarding this app:
1. Post the MultiBoot.log from your internal storage
2. Describe the problems with details such as which ROM, Kernel etc, and which variant of device you own (e.g x501, x507 etc.)
Does it support VoLTE:
This is not related to the tool. Do not ask for it
Help! I hardbricked/softbricked my device:
Sure, just describe what you did exactly
___ MORE TO COME
Any builds from and after 9.2.0.r25.g0638efb dated Mon, 10 Apr 2017 timed 19:57:27 should be okay to use for Le 1S

Can you make video how to install and run this app

sumitgp said:
Can you make video how to install and run this app
Click to expand...
Click to collapse
There are some out in youtube. But they are kinda outdated. Maybe someone will make it in the near future

DroidThug said:
There are some out in youtube. But they are kinda outdated. Maybe someone will make it in the near future
Click to expand...
Click to collapse
Your welcome bro
And ur contribution marvelous
Just keep going we are with u
Love u bhai thanks

is it work on LETV Le 1s x507
thanks for app
Iam asking because I dont understand LeEco 1S Products
Because LeEco 1s is X509
LETV 1S is x507
Is it also works on LETV Le 1s x507? please

fire3k said:
thanks for app
Iam asking because I dont understand LeEco 1S Products
Because LeEco 1s is X509
LETV 1S is x507
Is it also works on LETV Le 1s x507? please
Click to expand...
Click to collapse
Yes it work on le 1s x507

sumitgp said:
Yes it work on le 1s x507
Click to expand...
Click to collapse
Thnaku very much
then I'll try

fire3k said:
Thnaku very much
then I'll try
Click to expand...
Click to collapse
Thanku Very Much
I installed DualBootPatcher in My Le1S x507
and installed anlogside EUI, LineageOS 14.1 and Resurrection Remix 5.8.2 .
and they both working fine and installed gapps in both ROMS.
But 1 problem: that I installed SuperSu in LineageOS 14.1 and its working fine but when I try to install Supersu in Resurrection Remix 5.8.2, it installed perfectly there is no errors but when I open SuperSu app in Resurrection Remix 5.8.2 , It said that su binaries not installed
then I try to install Magisk12 in Resurrection Remix 5.8.2 and it gives some error.Please Giveme some Suggetion how to install magisk
Note: before install magisk, I already Patched it for RR 5.8.2

fire3k said:
Thanku Very Much
I installed DualBootPatcher in My Le1S x507
and installed anlogside EUI, LineageOS 14.1 and Resurrection Remix 5.8.2 .
and they both working fine and installed gapps in both ROMS.
But 1 problem: that I installed SuperSu in LineageOS 14.1 and its working fine but when I try to install Supersu in Resurrection Remix 5.8.2, it installed perfectly there is no errors but when I open SuperSu app in Resurrection Remix 5.8.2 , It said that su binaries not installed
then I try to install Magisk12 in Resurrection Remix 5.8.2 and it gives some error.Please Giveme some Suggetion how to install magisk
Note: before install magisk, I already Patched it for RR 5.8.2
Click to expand...
Click to collapse
Bhai check devloper option if there is any setting for root
If this will not work then try to share apps (super su app)
If above mentioned methods not work then try isu (higher version) of super su u can found it on los site
Thanks and warm regards

sumitgp said:
Bhai check devloper option if there is any setting for root
If this will not work then try to share apps (super su app)
If above mentioned methods not work then try isu (higher version) of super su u can found it on los site
Thanks and warm regards
Click to expand...
Click to collapse
Thanks for sugestion
but there is no option in Setting or devoloper option in Resurrection Remix 5.8.2 . only setting available in Magisk manager but it displays message that there is no root in system. Also tried chainfire Supersu. installs SuperSu App and when I tried to open it displays that There is no root binaries. Please help.
root is functioning in Resurrection Remix 5.8.2, when I install ROM without Dual Boot Patcher. but Only installs One ROM at a time no multiboot. Please any suggestion?

Thanks For Dual Boot Patcher
Atlast Solved
First I Flashed Chainfire SuperSu, then reboot then check root , it failed, and then I reboot and flash Magisk 12 and reboot. This Time All Ok Root Succeded

thanks for the updates!

If any one have le 1s related problem and solution or any one want to try new rom or kernal asap then all of u are welcome in our group on telegram so plz join with us
Requriemt
1. Download telegram from play store
2. Just click below link
https://telegram.me/LeSuperGroup
Thanks all of u

error
it shows error while booting 2nd rom

pravesh46 said:
it shows error while booting 2nd rom
Click to expand...
Click to collapse
What error? Be specific or give logs-,-

'have to try this! Thanks.
But, could this by any way interfer or get problem with F2FS formatted partitions (data,cache) ?

I'm also having some errors while installing the secondary rom...like extracting system errors

Hi! my Le1S gone in bootloop. Is there any solution to boot into the Primary ROM (i.e. eUI) via twrp? I have installed dual boot patcher & made eui as primary rom, lineage as secondary rom in "rrnougat" data slot & resurrection remix as secondary rom in " rrnougat2 " data slot.
From the past 2 weeks, I am using resurrection remix rom & sometimes eui. Today, I was on rr & my phone was hanging. So, I simply just restarted it & then, it gone in bootloop.
So, canI boot into my primary eui rom via twrp?, as dual boot patcher app cannot be accessed. Please help.

iamkamlesh said:
Hi! my Le1S gone in bootloop. Is there any solution to boot into the Primary ROM (i.e. eUI) via twrp? I have installed dual boot patcher & made eui as primary rom, lineage as secondary rom in "rrnougat" data slot & resurrection remix as secondary rom in " rrnougat2 " data slot.
From the past 2 weeks, I am using resurrection remix rom & sometimes eui. Today, I was on rr & my phone was hanging. So, I simply just restarted it & then, it gone in bootloop.
So, canI boot into my primary eui rom via twrp?, as dual boot patcher app cannot be accessed. Please help.
Click to expand...
Click to collapse
You can switch to other rom using dualbootutilities.zip. Just flash the zip . Then select ROM u want to switch & then select switch to..

[ROM][P905][UNOFFICIAL] Resurrection Remix 5.8.5 Android 7.1.2 20180118

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
This firmware was developed for the p905. It doesn't apply to the p905v at this time because it's bootloader locked and a custom recovery isn't possible.
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using nano gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Links
2: 20180118: remove Magisk, back su: https://drive.google.com/file/d/11V0Hmu9Jjib-oLERLXPNXbMMAie_iORq/view?usp=sharing
1: 20171231: https://drive.google.com/file/d/1m7t_7gntp9cDRRxGnJJqnwufnJxFVKUZ/view?usp=sharing
Gapps
http://opengapps.org/
Platform: ARM
Android: 7.1
Recovery
Official TWRP: http://forum.xda-developers.com/showthread.php?t=2706982
Sources
Sources: https://github.com/ResurrectionRemix/
Device: https://github.com/Valera1978/android_device_samsung_viennalte
Kernel: https://github.com/Valera1978/android_kernel_samsung_viennalte
Vendor: https://github.com/Valera1978/android_vendor_samsung_viennalte

Thanks again a lot for your work.
I wish you a happy new year!

@Valera1978
What such amazing gift for New Year!!!
Thanks for such awesome work my friend!

What is the different from this FW in compare to
https://forum.xda-developers.com/ga...-cyanogenmod-14-0-android-7-0-nougat-t3476335
? Does this thread continous the "old" one or it is a total other FW (other feature, Kernel .... ) ?

Mad07 said:
What is the different from this FW in compare to
https://forum.xda-developers.com/ga...-cyanogenmod-14-0-android-7-0-nougat-t3476335
? Does this thread continous the "old" one or it is a total other FW (other feature, Kernel .... ) ?
Click to expand...
Click to collapse
Hardware and config the same.
The idea is create another thread for custom firmwares, based on lineage\aosp.
Right now it's RR only, i'm working on OMNI rom, and later i'll build more firmwares.

please in other version don't insert the magisk.the rom to go in loop .and add in developer option the root gestion

Dagoncore93 said:
please in other version don't insert the magisk.the rom to go in loop .and add in developer option the root gestion
Click to expand...
Click to collapse
I'm taking a stab at what you are trying to express but the roms take 10 to 15 minutes to boot the first time because you are doing a full wipe. If you are not giving it at least that long magisk is not a likely cause.

Loakidog said:
I'm taking a stab at what you are trying to express but the roms take 10 to 15 minutes to boot the first time because you are doing a full wipe. If you are not giving it at least that long magisk is not a likely cause.
Click to expand...
Click to collapse
I received myself the error system ui crashed, and it got stuck on it.

Thanks Valera 1978, what a great new year gift!

I'm actually running Android 5.0.2, so is that Lollipop
Sent from my SM-G935F using XDA-Developers Legacy app

Albinoni said:
I'm actually running Android 5.0.2, so is that Lollipop
Click to expand...
Click to collapse
Yes

ralph_kl said:
I received myself the error system ui crashed, and it got stuck on it.
Click to expand...
Click to collapse
Send Valera1978 a bug report via Private Message. It is the only way developers can isolate the problem and fix it. In most Roms you can take a bug report via developer options.

help please Valera1978
i am updating from Resurrection Remix 5.8.5 version 20171231.
i wiped cache partitions
flashing rom 20180118 stuck on patching system unconditionally

theogalaxy said:
help please Valera1978
i am updating from Resurrection Remix 5.8.5 version 20171231.
i wiped cache partitions
flashing rom 20180118 stuck on patching system unconditionally
Click to expand...
Click to collapse
Try a full wipe magisk was removed with the latest version and super su added

A little help, please
Hello,
Sorry, but I need an help for understand.
How I can install this system?
I mean, can you explain to me what steps I need to do to install and which files to download?
sorry for my english, which is why I did not understand how to do it
Rosario
Valera1978 said:
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
This firmware was developed for the p905. It doesn't apply to the p905v at this time because it's bootloader locked and a custom recovery isn't possible.
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using nano gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Links
2: 20180118: remove Magisk, back su: https://drive.google.com/file/d/11V0Hmu9Jjib-oLERLXPNXbMMAie_iORq/view?usp=sharing
1: 20171231: https://drive.google.com/file/d/1m7t_7gntp9cDRRxGnJJqnwufnJxFVKUZ/view?usp=sharing
Gapps
http://opengapps.org/
Platform: ARM
Android: 7.1
Recovery
Official TWRP: http://forum.xda-developers.com/showthread.php?t=2706982
Sources
Sources: https://github.com/ResurrectionRemix/
Device: https://github.com/Valera1978/android_device_samsung_viennalte
Kernel: https://github.com/Valera1978/android_kernel_samsung_viennalte
Vendor: https://github.com/Valera1978/android_vendor_samsung_viennalte
Click to expand...
Click to collapse

Compability
It is can flash for SM-P091 ?

i want the S Pen features and UI of Galaxy Tab S3 on my Galaxy Note 12.1 Pro Wifi. Am I right here and if yes how to do it please?
In terms of the little RAM I have I will use on microSD card as a RAM alternativ. is this a good idea in combination with a custom Rom?
Thx!

[Rom] JAGUAR PIE OnePlus 5 OFFICIAL - Updated December 15

Official Telegram link: https://t.me/jaguar_Rom_Official
This is Jaguar Pie, a continuation of Jaguar Oreo. The project aims at hardening of Android and Linux kernel + performance. In addition to all familiar Pie features, Jaguar has:
1. Hardened bionic (which is responsible for C+/C++ portions of Android)
2. Hardened kernel (many features ported from 4.14 kernel)
3. Selinux replaced with Yama security
4. Various features, such as Alarm blocking and Wakelock blocker
5. Pie and Circle launchers
6. Force-encrypt FBE, as well as FDE options (starting from V2)
7. Various options from the top down starting from Status bar to Navigation bar.
8. Gestures, etc.
9. Fully working native call recording
10. Lawnchair Pie home
11. Omni theme engine
12. Kernel is based on Krieg with lots of security commits from Linux Hardened project
13. Overclocked big and little (in performance profile only)
14. Most runtime processes made read-only both in bionic and kernel
15. MicroG support
16. Qcomm's boost framework fully working (includes the fixed Qperformance blob)
and more...
Requirements: Unlocked bootloader, 9.0.2 firmware and TWRP capable of mounting/writing Vendor partition
Instructions: Detailed instructions are in post #3 together with future releases
Download Rom V-1 release: https://androidfilehost.com/?fid=11410963190603914968
Kernel Source EAS: https://github.com/AOSPME/JaguarPie-Kernel-for-Oneplus-5-5T
Kernel Source non EAS: https://github.com/optimumpr/android_kernel_oneplus_msm8998-1
Credits: AOSP, DU, OMNI, BENZO, LINEAGE, CARBON, XTENDED and everybody who contributed to Kernel (all listed in the link)
Also credit to @deletescape for Lawnchair V2

Screenshots:

This is where you get updates
If anyone is interested in locking bootloader on this rom and getting rid of any warning messages, i.e., you will have a boot like on stock OEM rom, contact me via PM.
Android 9 offers FBE (file based encryption forced) by default. Jaguar offers FDE (full disk encryption - not forced) by default with FBE as an option. Therefore, there are 3 choices users face: No encryption; FBE; or FDE. Jaguar, as mentioned above, by default, offers 'FDE, which is not forced, which means, you boot un-encrypted, but later, you can encrypt within Settings. That means, if you want to stay un-encrypted or encrypt within Settings, you don't need any extra steps. So, I am going to scream below, so that hopefully this time most would understand:
1. If you want no encryption, NO EXTRA STEPS REQUIRED, JUST FLASH THE ROM!
2. If you want FDE, NO EXTRA STEPS REQUIRED, JUST FLASH THE ROM! YOU CAN ENCRYPT WITHIN SETTINGS LATER! THE SAME APPLIES, IF YOU WERE ENCRYPTED FDE ON ANOTHER PIE ROM! IN THIS CASE, JUST BOOT, AS YOU ARE ALREADY FDE ENCRYPTED!
3. If you want FBE or already encrypted FBE on another Pie rom, EXTRA STEP IS REQUIRED: FLASH MY 'FBE FORCE-ENCRYPT' ADDON RIGHT AFTER THE ROM AND BEFORE REBOOT. YOU WILL HAVE TO FLASH THAT ADDON EVERY TIME AFTER UPGRADING AND BEFORE REBOOTING! IF YOU DON'T, YOU WON'T BOOT, BECAUSE SYSTEM EXPECTS FDE, BUT YOU ARE ON FBE! That's all.
TWRP BACKUP: Never backup and never restore System or Vendor IMAGES, backup and restore partitions/drives only. I don't know why images are shown in TWRP at all. If you restore system or vendor image, you will soft brick your phone, which may require flashing stock in EDL mode. Also, if you are FBE encrypted, never touch any lockscreen.db files in /data/system/. If you do, you will screw encryption.
Flashing Instructions.
1. Dirty flashing means flashing the rom without wiping anything. Normally, you don't need to do anything else, as both Magisk and Gapps have survival addons.
2. Clean flash means: wiping System/Vendor/Data/Dalvik/Cache; flashing rom; flashing Gapps (optional) and rebooting; then back to TWRP to flash Magisk (also optional).
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
December 15. Rom updated:
1. Fixed data disappearing after reboot and associated with it SystemUI crashes: this required rebuilding of the entire rom
2. Kernel to 4.4.206
Dirty flash is fine. Otherwise, see instructions
Download rom V15.1: https://androidfilehost.com/?fid=4349826312261675033
December 5. New release, V15
1. December security patches
2. Pie r51
3. Kernel to 4.4.205
4. Many updates taken directly from Android Master gerrit
5. Shutdown time reduced to 1-2 seconds
6. Updated Bromite Webview and Lawnchair
Dirty flashing is fine on top of previous release, otherwise, clean flash/read instructions
Download rom V15: https://androidfilehost.com/?fid=4349826312261653214
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
November 12. New release, V14
1. Many updates taken directly from Google Android Gerrit, master branch - updated as of November 11
2. Improvements in framework/base; framework/ave; framework/native and vulkan drivers
3. Kernel updated to 4.4.200, which includes the latest implementation of Spectre V1 and V2 patches (upstreamed just a few days ago)
4. Night light tint is incorporated in the rom (no need to flash a separate attachment)
5. November security patches
Dirty flash is sufficient. Otherwise, clean flash - see instructions above.
Download Rom V14: https://androidfilehost.com/?fid=4349826312261627158
______________________________________________________________________________________________________________________
October 12. New release V13
October security patches + internal improvements + updated kernel
Dirty flashing is fine on top of the previous release. Otherwise, clean flash, see instructions above.
Download rom V13: https://androidfilehost.com/?fid=1899786940962606952
______________________________________________________________________________________________________________
September 18. New release V12
1. September security patches
2. Major changes in kernel and rom - significant battery saving
3. Smart charging
4. Choice of backgrounds in Reboot menu
5. Toggle to disable Home key while ringing
and more
Dirty flashing is fine, if on the previous release. Otherwise, clean flash, see instructions
Download rom V12: https://androidfilehost.com/?fid=1899786940962588878
August 10. Small partial update to fix fingerprint spam while in a pocket and feature enabled in settings. Flash in TWRP and reboot:
Download partial update (this is not a rom): https://forum.xda-developers.com/attachment.php?attachmentid=4803640&d=1565323520
August 7. New release V11.
1. August security patches
2. Google release 46
Dirty flashing is fine, if on the previous release. Otherwise, clean flash. In either case read instructions.
Download rom v11: https://androidfilehost.com/?fid=6006931924117931413
July 10. New release.
1. Latest Google sources
2. July security patches
3. Lawnchair updated. Now, you will be able to updated yourself
Dirty flash on top of the previous release is fine. Otherwise, read instructions above.
Download Rom: https://t.me/jaguar_Rom_Official/3
AFH link: https://androidfilehost.com/?fid=6006931924117913953
Also, see the original post for the official Jaguar Channel on Telegram.
June 9. Kernel update - brings back display color calibration missing after switching to non-EAS kernel.
Unzip and flash in TWRP as image to boot partition.
Download updated kernel: https://forum.xda-developers.com/attachment.php?attachmentid=4774096&d=1560094674
June 6. New release V9
1. June security patches
2. Google release 41
3. Oneplus camera replaced with Snap
4. Updated Lawnchair
Could be flashed dirty, if on a previous release. Otherwise, clean flash. Read instructions
Download rom V9: https://androidfilehost.com/?fid=6006931924117889650
-------------------------------------------------------------------------------------------------------------------------------------------
May 17. Release 8.
1. New non EAS kernel
2. Big changes in frameworks: exec spawning function is severely restricted to all apps, i.e., only one instance is allowed
3. Most resources preloading for exec spawning is disabled. As a result, boot time is shorter, fewer background resources are loaded in ram, which translates into an overall smoother experience.
4. MusicFX/Equalizer is now themeable (you need to re-apply your selected theme)
Instructions:
1. Dirty flash, if on a previous release. For all others:
2. Clean flash. Clean flash requires wiping system/data/vendor/cache/dalvik. Read general instructions at the top of this post re encryption. Flash the rom, flash
Gapps and reboot. Then back to TWRP and flash Magisk.
If after applying Magisk the phone is stuck on bootanimation for more than 2 minutes, force-reboot with the power button.
Download rom V8: https://androidfilehost.com/?fid=1395089523397967819
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
May 12: To fix randomly disappearing contacts, flash this and reboot: https://forum.xda-developers.com/attachment.php?attachmentid=4757815&d=1557687807
May 11. New release V7.1: Issue with touches fixed + updated Lawnchair with many fixes
1. May security patches
2. Android Pie r37
3. Aggressive battery saving
4. Status bar burning protection
5. Media cover art filter (on lockscreen)
6. Lots of changes in kernel
7. Switched to Bromite system webview V74
8. Redone auto-brightness and ambient display
9. Added additional screen calibration features in OneplusExtras
10. Could be used with Oneplus latest firmware 9.05
11. Lawnchair upgraded (many fixes)
12. Cache automatically cleaned on dirty flash
Instructions:
1. Dirty flash on top of V7 is fine
2. If you are coming from a rom encrypted with FBE, you can preserve that encryption (if you wish) by flashing my force-encrypt addon. If not, then proceed below
3. TWRP-Clean flash: format System/Vendor/Data/Cache. Flash the rom, Gapps (optional), reboot. After that back to TWRP to flash Magisk (optional)
Download rom V7.1: https://androidfilehost.com/?fid=1395089523397963842
__________________________________________________________________________________________________________________
April 13. Rom updated
1. Lawnchair V2 now has Pie recents
2. Upstream commits
Instructions: Dirty flash (with dalvik/cache wiping) for those on the previous release. Clean flash for all others (see instructions about encryption choice)
Download rom release V6.1: https://androidfilehost.com/?fid=1395089523397943691
April 2. New release, V6
AOD IS WORKING NOW
If you are on April 2 release, just flash dirty and wipe cache/dalvik. When enabling AlwaysOn the first time, just use power buton a few times, after that, AOD will work (confirmed). If on March release, flash clean.
1. April security patches
2. Android pie r35
3. Up time and CPU sleep time since reboot in About Phone
4. Updated kernel (upstream and other commits)
5. Many other improvements
Instructions: Clean flash is required for everybody. Those, who are encrypted FBE, need to flash one of 2 fbe addons from post #4 (doesn't matter which one). Others just need a clean flash.
Download rom v6:https://androidfilehost.com/?fid=1395089523397932686
March 14. New release, V5:
1. Boot time reduced to 4-5 seconds (after initial logo), as a result of
2. Rom no longer relies on background compilation
3. Speed/performance significantly increased. As a side effect, system image is larger now
4. Many performance improving changes in kernel (see github)
Instructions:
1. If you are on a previous release, you may flash dirty (just flash one of FBE addons, if you are FBE encrypted) + wipe cache/dalvik. The first boot will take longer
2. Clean flash (wipe system/data/vendor/cache/dalvik); flash the rom (if you are FBE encrypted, flash appropriate FBE addon); flash Gapps (optional) and reboot; then back to TWRP and flash Magisk (optional)
Download rom V5: https://androidfilehost.com/?fid=1395089523397916259
March 5: New release V4
1. March security patches
2. Android Pie release 34
3. About phone - Jaguar version
4. Settings/Battery - dash charging indication
5. Sim preferences now survive reboot (in multi-sim)
6. Set text_show_password to false by default
7. Lineage root implementation (for those who don't want Magisk)
8. Possible fix for 'green screen', when connected to smart tv (needs confirming)
9. DocumentsUI/File manager is replaced with Simple File Manager (from F-Droid)
Clean flash REQUIRED due to changes in Settings.apk. OTHERWISE, you will have mismatched entries
Instructions: Clean flash (wipe system/data/vendor/cache/dalvik); flash the rom (if you are FBE encrypted, flash appropriate FBE addon); flash Gapps (optional) and reboot; then back to TWRP and flash Magisk (optional)
Download rom v4: https://androidfilehost.com/?fid=1395089523397908036
February 19: New release V3
1. Toggle to enable/disable captive portal detection (Settings/Network & Internet/Wifi/Wifi preferences/Advanced)
2. Ambient brightness fixed (now follows regular brightness)
3. Attempted fix for MicroG
Instructions: This version requires clean flash for everybody, due to changes in Settings.apk. If you flash dirty, you will have entries in Settings mismatched. If you are coming from Oreo and encrypted, full factory reset in TWRP is required.
Download rom V3: https://androidfilehost.com/?fid=1395089523397896850
February 13: Minor rom update V2-1
Overview buttons options are back. No other changes.
Instructions are the same, as in V2 below. Dirty flashing is fine on top of previous release
Download rom V2-1 release: https://androidfilehost.com/?fid=1395089523397892116
February 11: Rom updated
THIS VERSION IS FDE - ENCRYPTION NOT FORCED by DEFAULT. I have also posted 2 encryption addons (post #4) for those who want FBE enforced or not enforced. In any case, there is no need for 'no_verity' patch any longer.
1. February security patches
2. Fixed non-booting without magisk
3. FDE encryption (as opposed to FBE) - you don't need to flash 'No_Verity'
Instructions for V2:
9.0.2 or 9.0.3 firmware
1. If you are encrypted on Oreo, you must do factory reset in TWRP where you type 'yes' to confirm. After that reboot in TWRP again
2. Wipe System/Data/InternalSD/Cache/Dalvik/Vendor
3. If you want to stay de-crypted with an option to encrypt FBE later on: flash the rom; flash 'fbe-no-forced-encryption; Flash Gapps and Reboot.
4. If you want FDE or no encryption, follow the previous step, but skip flashing addon.
5. Back to TWRP and flash Magisk 18 or 18.1
You are not encrypted by default in this version. You don't need 'no verity'. You can encrypt FDE within settings
Download rom V2 encryptable with FDE (not forced): https://androidfilehost.com/?fid=1395089523397890806

Encryption addons:
1. FBE forced encryption
2. FBE no forced encryption
Flash right after the rom (before reboot). You don't need 'no-verity'.

3 points.
1. Would you be releasing with Feb Patch when the patch comes in on Wednesday?
2. Just something about the thread name. [ROM] Jaguar Pie OnePlus 5 Official. That looks really better. Just a suggestion from one English freak like me.
3. Which TWRP did you use?
BTW, 1st one to comment. and download maybe.

vdbhb59 said:
2 points.
1. Would you be releasing with Feb Patch when the patch comes in on Wednesday?
2. Just something about the thread name. [ROM] Jaguar Pie OnePlus 5 Official. That looks really better. Just a suggestion from one English freak like me.
BTW, 1st one to comment. and download maybe.
Click to expand...
Click to collapse
The edit function, for some reason, doesn't change to capital letters. Nor does the Development Project section properly work.
There will be a release with February patches, but those won't be published on Wednesday. Trust me. Google rarely does those on time.

when do you support 5t？I want to use Jaguar.

optimumpro said:
The edit function, for some reason, doesn't change to capital letters. Nor does the Development Project section properly work.
There will be a release with February patches, but those won't be published on Wednesday. Trust me. Google rarely does those on time.
Click to expand...
Click to collapse
Recently XDA has gone crazy. Yeah Google is **** anyways. The patch will anyways be dated 05022019. Be it released whenever. https://source.android.com/security/bulletin
What TWRP did you use? Give the link if possible? Also, I really love this ROM. Why don't you join Telegram. I have a chat for Jaguar, and I give out your updates on my OP5/T Channel in Telegram.
---------- Post added at 22:41 ---------- Previous post was at 22:40 ----------
losigep said:
when do you support 5t？I want to use Jaguar.
Click to expand...
Click to collapse
5T has Oreo. Pie I too ask him, as there are many wanting to use it.
---------- Post added at 22:44 ---------- Previous post was at 22:41 ----------
One last thing for downloads..
Download Rom V-1 release: https://androidfilehost.com/?fid=11410963190603914968
Kernel Source: https://github.com/AOSPME/JaguarPie-...r-Oneplus-5-5T
Please do not give AFH, as it sucks. For most of us it takes around 1 hour and more to download and it can break off anytime. Whether one uses ADM or any fast download manager, PC, or whatever. The speed of AFH is usually 90KBPS or even less..

No decryption support??
I am decrypted and I would Ike to try this rom... Any possibility??

SREEPRAJAY said:
No decryption support??
I am decrypted and I would Ike to try this rom... Any possibility??
Click to expand...
Click to collapse
This ROM is all about Encryption in security side. Why do you want to force decryption on it? Also, suggestion, go Encrypted with Jaguar, you wont face any issues.
Although I am decrypted on Oreo with it. It has decryption support, right @optimumpro
---------- Post added at 23:19 ---------- Previous post was at 22:48 ----------
BTW, waiting patiently for FDE. ?

SREEPRAJAY said:
No decryption support??
I am decrypted and I would Ike to try this rom... Any possibility??
Click to expand...
Click to collapse
vdbhb59 said:
This ROM is all about Encryption in security side. Why do you want to force decryption on it? Also, suggestion, go Encrypted with Jaguar, you wont face any issues.
Although I am decrypted on Oreo with it. It has decryption support, right @optimumpro
Click to expand...
Click to collapse
You should simply flash the latest No-verity patch right after flashing the rom and before reboot. This way, you will stay un-encrypted.

losigep said:
when do you support 5t？I want to use Jaguar.
Click to expand...
Click to collapse
Jaguar Oreo had very few downloads on 5T thread. I guess people are not interested. If there is more interest, I will do Pie for 5T.

vdbhb59 said:
This ROM is all about Encryption in security side. Why do you want to force decryption on it? Also, suggestion, go Encrypted with Jaguar, you wont face any issues.
Although I am decrypted on Oreo with it. It has decryption support, right @optimumpro
---------- Post added at 23:19 ---------- Previous post was at 22:48 ----------
BTW, waiting patiently for FDE.
Click to expand...
Click to collapse
As I have stated before, my main problem with Pie is that Google has removed the ability to encrypt the phone via adb or terminal. This is important for FDE, because on pre-Pie, you could have separate passwords one longer for boot and another shorter for screenlock. Not anymore. To make things worse, both FBE and FDE are encrypted with literally the words 'default_password', which is hard-coded in system and TWRP. That's why you boot without a prompt. Later, you can change that to whatever you want. However, if your new password is removed, system defaults to effing 'default_password'. So, right now, if an adversary gets your encrypted phone, he can boot into TWRP, delete /data/system/lockscreen files and reboot the phone without a prompt. This obviously defeats the entire purpose of encryption, but kids (users) are happy and Mother (agencies) approve. .
I can fix that for myself by hard-coding a different password, but it is impossible to do for others...
By the way, I use Blue_Spark's TWRP, the one for September 2018 - works fine (including decryption) on both Oreo and Pie.

optimumpro said:
Jaguar Oreo had very few downloads on 5T thread. I guess people are not interested. If there is more interest, I will do Pie for 5T.
Click to expand...
Click to collapse
Ok.... I am using crdroid5.1 but it is have some issue，such as my app always ANR.long time ago I have used Jaguar for 2 months.but I have been waiting for a long time, but it has not been updated.

Does Jaguar 9.0 support AOD?
Also - what is the process for updating from Jaguar Oreo? What TWRP version do you suggest?

Binary Assault said:
Does Jaguar 9.0 support AOD?
Also - what is the process for updating from Jaguar Oreo? What TWRP version do you suggest?
Click to expand...
Click to collapse
I am using Blue Spark TWRP dated September 2018 and it works for both Oreo and Pie. The rest is in instructions. Read about encryption: basically, if you are encrypted in Oreo, or in PIE FDE, you have to do full factory reset (in TWRP), which will erase encryption and both data and SD card. If not encrypted, then just do a clean flash. No need to wipe internal SD card. You will also need to flash 9.0.2 firmware.

Finally Pie Build! Thx
Inviato dal mio ONEPLUS A5000 utilizzando Tapatalk

Is this rom mainly focused on Security? What about performance? I mainly do gaming on my phone. So performance is what i need. The name "Jaguar" has made me curious! ?

ShiShTuBaBu said:
Is this rom mainly focused on Security? What about performance? I mainly do gaming on my phone. So performance is what i need. The name "Jaguar" has made me curious! ?
Click to expand...
Click to collapse
It is both. So go ahead blindly and play as many games as possible. ?

optimumpro said:
You should simply flash the latest No-verity patch right after flashing the rom and before reboot. This way, you will stay un-encrypted.
Click to expand...
Click to collapse
Like all the Roms on the other hand ...
I do not understand the above statement

[ROM] JAGUAR PIE OFFICIAL NON-TREBLE V6, updated August 7

Here is Jaguar Pie. In addition to familiar Pie features (all of them), you have:
Official Telegram Link: https://t.me/jaguar_Rom_Official
The main thing: Non-treble! So, your vendor is located in system partition, which is NOT available to the entire world, like in treble roms.
1. Hardened/fortified bionic (over 150 commits) to prevent bad behavior by system and third party apps
2. Most runtime processes are read only, which means they can't be exploited to take over the device. I am trying to attack the cause, rather than the symptoms (a specific exploit)
3. Many kernel security features activated, such as 'configuration_integrity', randomization; hardened user copy, etc. Impulse governor added
4. Yama security in kernel
5. Working msm hotplug, which actually plugs/unplugs CPU based on load
6. Wakelock blocker, Alarm blocker etc
7. Gestures, Omni Theming
8. Smart pixels
9. Offline charging
10. Utouch
11. AOD
12. No response to 'type zero' SMS
13. Boot time on a fully settled rom is about 4-5 seconds after Zuk logo
14. Qualcomm's boost framework
Many more features, which I am tired to list.
This is beta, because I don't have the device - relied on @Dr.07 @The.Night.King and @benedict97 - thanks for testing
INSTRUCTIONS:
1. Format System/Vendor (if you have it)/Data/Dalvik/Cache. If you are encrypted in Oreo or encrypted with FBE, you also need a format with factory reset to get rid of encryption. ALSO: FORMAT FACTORY partition, otherwise, you will have 2 sets of vendor blobs, which would create a mess on boot
2. Flash the rom, flash Gapps, reboot and let the rom run, then
3. Back to TWRP to flash Magisk (18.1 is working)
Rom download V1: https://forum.xda-developers.com/devdb/project/dl/?id=31427
This is the initial release. All future updates will be in post #3, as usual.
Credit: MrHacker (I used his device tree as a base) and many others who work on device tree and kernel and obviously AOSP, OMNI, DU, CopperheadOS, Carbon Rom, Xtended and Benzo
Also, credit for a Jaguar bootanimation to @Ashish9 and @The.Night.King who made a logo and header icon
If anyone is interested in Afwall with administrative option restored (app can't be uninstalled, unless confirmed by you): https://forum.xda-developers.com/attachment.php?attachmentid=4739733&d=1554836212
XDA:DevDB Information
[ROM] JAGUAR PIE NON-TREBLE 3.18 KERNEL OFFICIAL, ROM for the Lenovo ZUK Z2 (Plus)
Contributors
optimumpro
Source Code: https://github.com/optimumpr/kernel_zuk_msm8996
Sources for new (May 29) kernel: https://github.com/optimumpr/android_kernel_zuk_msm8996-1
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.1.x
Based On: AOSP, DU, Lineage
Version Information
Status: Beta
Current Beta Version: V1
Beta Release Date: 2019-04-05
Created 2019-04-05
Last Updated 2019-08-07

Screenshots
Some screenshots:

Updates in this post
Those who are coming from treble roms: you need to format Factory partition too, otherwise, you will have 2 sets of vendor blobs, in other words, MESS
August 7. New release.
1. August security patches
2. Google r46
3. Camera should have level 3 now + more
Dirty flashing is fine, if on the previous release. Otherwise, clean flash - wipe Vendor/Factory/System/Data/Cache/Dalvik
Download rom V6: https://forum.xda-developers.com/devdb/project/dl/?id=31753
July 30: New release V5.2 with fixed installation problems:
You could try dirty flash, but I installed clean, then flashed Opengapps, and Firefox installed without any problems, while it didn't on V5.1.
Download rom V5.2: https://forum.xda-developers.com/devdb/project/dl/?id=31733
July 27. New release, v5.1.
This will fix encryption.
The reason it didn't work was the official TWRP. The maintainer (a known pro) put in the wrong size of userdata partition. So, if you ever formatted data on official TWRP, especially with factory reset, your data partition is screwed for the purposes of encryption (no place for crypto footer). I had to install another version of TWRP, and after I did format there, encryption worked. So, I am attaching both the rom and unofficial TWRP by handibuddy. This is also a signed version (as well as the rom itself), so you can re-lock bootloader on this rom: I have been doing this for ages and long before Lineage came up with the idea (you can check my signing guide in Oneplus 5 thread).
Download Rom V5.1: https://forum.xda-developers.com/devdb/project/dl/?id=31727
Download signed TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=31728
Instructions: Rom could be flashed dirty over V5. TWRP could be flashed as image (to recovery) in your existing TWRP or via fastboot.
Just remember, if you want to relock bootloader, encrypt after locking.
July 25. New release, v5
1. July security patches
2. New Night Screen with configurable tint and brightness
3. Support for level 6-6.2 for AVC codecs
4. Option to disable proximity sensor during calls
5. In-CallUi is now themeable
6. Aggressive battery saving mode
7. Latest Lawnchair
Clean flash is required over V4 or if coming from a different rom, in which case you will also need to format vendor or factory partition.
DO NOT ENCRYPT YET!
Instructions:
1. Dirty flash, if already on Jaguar Pie
2. Clean flash, If coming from a different rom, also format vendor/factory/system/data/cache/dalvic
3. Flash the rom, flash GapDirty flash is fine, if on a previous release. Otherwise, clean flash.
Download rom V5: https://forum.xda-developers.com/devdb/project/dl/?id=31725
________________________________________________________________________________________________________
June 6. New release, V4:
1. June security patches
2. Pie r41
Dirty flash is fine, if on a previous release. Otherwise, clean flash.
Instructions:
1. Dirty flash, if already on Jaguar PieClean flash
2. If coming from a different rom, also format vendor/factory/system/data/cache/dalvic
3. Flash the rom, flash GapDirty flash is fine, if on a previous release. Otherwise, clean flash.
Instructions:
1. Dirty flash, if already on Jaguar PieClean flash
2. If coming from a different rom, also format vendor/factory/system/data/cache/dalvic
3. Flash the rom, flash Gapps, reboot, then back to TWRP to flash Magisk
ps, reboot, then back to TWRP to flash Magisk
Download rom V4: https://forum.xda-developers.com/devdb/project/dl/?id=31621
______________________________________________________________________________________________________________________
June 2. Lawnchair update to the latest. Flash in TWRP.
Download Lawnchair: https://forum.xda-developers.com/attachment.php?attachmentid=4770317&d=1559500522
May 31. Rom updated, V3:
1. Major kernel improvements - there is no reason to use my Oreo kernel or any other kernel
2. Flashlight works regardless of 'always on' or 'ambient display' (that required a clean flash)
Instructions:
1. Clean flash recommended - wipe system/data/cache/dalvik
2. If coming from a different rom, also format vendor/factory
3. Flash the rom, flash Gapps, reboot, then back to TWRP to flash Magisk
Download rom V3: https://forum.xda-developers.com/devdb/project/dl/?id=31612
_____________________________________________________________________________________________________________________
May 30. This is an updated version of the new kernel I posted earlier. This one contains my commits + reversed 'power saving' commits. Sometimes, you get things better by reversing.
Unzip, put on internal SD and flash either with TWRP (as image onto boot partition) or via fastboot.
Download new kernel: https://forum.xda-developers.com/attachment.php?attachmentid=4768179&d=1559177914
May 28. Lawnchair update. Flash in recovery:
Download Lawnchair: https://forum.xda-developers.com/attachment.php?attachmentid=4767269&d=1559060237
May 27. Updated release:
1. Fixed toggling flashlight in ambient display
2. Improvements in Qualcomm's boostframework
3. Contactsprovider updated (disappearing contacts)
Could be dirty flashed over V2. Otherwise, clean flash.
Download rom V2.1: https://forum.xda-developers.com/devdb/project/dl/?id=31602
May 25. New release, V2:
1. May security patches
2. Android Pie r37
3. Big changes in frameworks: exec spawning function is severely restricted to all apps, i.e., only one instance is allowed
4. Most resources preloading for exec spawning is disabled. As a result, boot time is shorter, fewer background resources are loaded in ram, which translates into an overall smoother experience.
5. Aggressive battery saving
6. Status bar burn protection
7. Media cover art filter (on lockscreen)
8. Switched to Bromite system webview V74
9. Redone auto-brightness and ambient display: ZukDoze removed, as Customdoze and Amibientdisplay are now builtin (Settings/Display)
10. Lawnchair upgraded: many fixes including Pie recents
11. MusicFX/Equalizer is now themeable
12. Zukparts removed, as spectrum profiles simply don't work, and KCAL could be done via Kernel Adiutor
13. Battery icon Q style
14. Wifi randomization working (Developer Settings)
15. Captive portal detection toggle (Settings/Wifi/Advanced - disable network connectivity check). You can now uninstall Captiveportal and have no 'x' in Wifi and Mobile icons
Instructions:
1. Clean flash required
2. Format system/vendor (or factory, depending on what you have)/data/dalvik/cache; if you were encrypted in Oreo or FBE in Pie, in addition, do factory reset
3. Flash the rom, flash Mind the Gapps or Nano Gaps, reboot. Then back to TWRP and flash Magisk
If your provider's APN is not on the list, set it up and enable. If data doesn't work, then change CDMA subscription in Mobile network to the alternative.
Download rom V2: https://forum.xda-developers.com/devdb/project/dl/?id=31591
__________________________________________________________________________________________________________________
April 9. New release. Lots of changes, mostly in kernel:
1. Inteli-thermal
2. Thermal-engine ported from Jaguar Oreo, so the rom runs about 3 degrees cooler
3. Substantially improved fluidity: according to testers, virtually no lag
Instructions:
1 If on a previous release, flash dirty and wipe dalvik/cache
2. if new, format system/vendor (or factory, depending on what you have)/data/dalvik/cache; if you were encrypted in Oreo or FBE in Pie, in addition, do factory reset
3. Flash the rom, flash Mind the Gapps, reboot. Then back to TWRP and flash Magisk
Download rom V1.1: https://forum.xda-developers.com/devdb/project/dl/?id=31467
_____________________________________________________________________________________________________________________
April 5. Here is the first update, kernel only. Speed improvement.
Just flash boot.img on top of the first release.
Download kernel: https://androidfilehost.com/?fid=1395089523397933955

Finally ?

@optimumpro Thank you. Respect?

Thanks for the work! ?

Woh!!!!...... Waiting for a detailed review by someone.....

Wow finally

vinay069 said:
Woh!!!!...... Waiting for a detailed review by someone.....
Click to expand...
Click to collapse
your prediction turned out pretty accurate about the release date lol

All right, boys and girls. First update: kernel only - speed improvement . Download (in post #3) and flash on top of the first release

Yess! The best! Gonna flash this aftermy exams!
By the way @optimumpro does this contain the dual audio mod which was in Oreo?
Also any screenshots?

GopalKaul said:
Yess! The best! Gonna flash this aftermy exams!
By the way @optimumpro does this contain the dual audio mod which was in Oreo?
Also any screenshots?
Click to expand...
Click to collapse
Screenshots posted. Stereo sound - not yet.

optimumpro said:
Screenshots posted. Stereo sound - not yet.
Click to expand...
Click to collapse
The 1st build is the one I'm using, right? The tweaked dalvik one, so should I flash only the kernel?
BTW can you add GPU driver 331 instead of 319? Since you're using 319 instead of 269, why not 313?

The.Night.King said:
The 1st build is the one I'm using, right? The tweaked dalvik one, so should I flash only the kernel?
BTW can you add GPU driver 331 instead of 319? Since you're using 319 instead of 269, why not 313?
Click to expand...
Click to collapse
Hey brother... Can u help me. ..?
Currently on aex 6.4 and done all this to flash aex..
Now what do i do to go back to beast jaguar?

Shubhi singhal said:
Hey brother... Can u help me. ..?
Currently on aex 6.4 and done all this to flash aex..
Now what do i do to go back to beast jaguar?
Click to expand...
Click to collapse
Just flash rom

The.Night.King said:
The 1st build is the one I'm using, right? The tweaked dalvik one, so should I flash only the kernel?
BTW can you add GPU driver 331 instead of 319? Since you're using 319 instead of 269, why not 313?
Click to expand...
Click to collapse
Kernel only.

venom0207 said:
Just flash rom
Click to expand...
Click to collapse
Seriously?.... Is my twrp correct and nothing to do with vendor and factory at all?

Shubhi singhal said:
Seriously?.... Is my twrp correct and nothing to do with vendor and factory at all?
Click to expand...
Click to collapse
@optimumpro animations r fekked

Shubhi singhal said:
Seriously?.... Is my twrp correct and nothing to do with vendor and factory at all?
Click to expand...
Click to collapse
It is non treble, factory or vendor have nothing to do with it, you can straight away flash the rom

Flashed the ROM.
It took a lot of time to boot.
Swipe up home screen is not showing any options
Recents is not pie recents
Very fast ROM
In some themes, the notifications are invisible

GSIs fixed builds for hi6250 (emui8)

Havoc 3.0 Q gsi fixed build for Huawei P10 Lite
About
Originally Havoc 3.0 Q gsi based on v204 compiled by ExpressLuke , but for Hi6250 some bugs persist , so I managed to fix them and repacked the IMG then highly compressed.
Fixed
* Camera * media ( sound , video , YouTube ..) * NFC * battery usage * auto brightness * phone Info's ( build number , model , manufacturer , device name .. ) * added Havoc bootanimation .
Bugs
* Offline charging ( requires permissive kernel , Labyrinth kernel 2.0 by Dil3mm4 tested * Blurry can be fixed in phh treble settings > Huawei features > 3rd option ( disabling hwcomposer ).
Installation
* Extract img from xz archive * go to TWRP and do a full wipe (system, data, cache, dalvik/art cache) * flash the image in system image partition * flash root (optional) NOTE1: If you are coming from Android 9 flashing root is a MUST DO ! NOTE2: Flash only the Magisk zip linked in this post ! * reboot to System * reboot to TWRP * flash gapps (optional) * Enjoy !!!
Download
https://mega.nz/#!2S4xxQ6C!f0KJlCA_9_yyJzWZAtlNYVJHktSuyyFY7p82kXK4caM
Twrp recommended ( by @Pretoriano80 ):
https://mega.nz/#!LLhBXSzY!3runNNoW9z1tOHSu-heIUhyy-4u8XHvc8rZMsn547so
Magisk.phh:
https://mega.nz/#!uX4k1KjS!2gnUV3IyLt8XXf4NO3RyZEJnt5YNJQ8tY9i11oGfKYM
Credits: @phhusson ExpressLuke @haky 86 @DarkJoker360 @Dil3mm4
Regards!
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui 8.x,bootloader unlocked and TWRP
Based On: AOSP
Version Information
Status: Stable
Created 2019-12-01

6 hrs SoT

Hami_Do said:
6 hrs SoT
Click to expand...
Click to collapse
Wow that's really impressive for a 3000 mAh device! Many people aren't getting that on the Note 10 Plus!

Hi! Thats nice, so basically Is a Kirin gsi? Are gapps included?

TureX said:
Hi! Thats nice, so basically Is a Kirin gsi? Are gapps included?
Click to expand...
Click to collapse
No, it's simply Havoc GSI with several fixes included especially for our device/platform and no, gapps are not included (you would have known if you read the first post more carefully )

TureX said:
Hi! Thats nice, so basically Is a Kirin gsi? Are gapps included?
Click to expand...
Click to collapse
For gapps , pico worked for me as it should , from here :
https://sourceforge.net/projects/opengapps/files/arm64/beta/20191114/

Hami_Do said:
For gapps , pico worked for me as it should , from here :
https://sourceforge.net/projects/opengapps/files/arm64/beta/20191114/
Click to expand...
Click to collapse
Hi! I Guess for Who hasn't a working twrp Is not possible to flash gapps. Thanks for your work and sorry for my english

TureX said:
Hi! I Guess for Who hasn't a working twrp Is not possible to flash gapps. Thanks for your work and sorry for my english
Click to expand...
Click to collapse
the suggested twrp in first post works perfectly on most hi6250 ( emui 8 ) , plus it has an option ( exclude OEM path from data wipe ) from there you don't need to format data & internal storage to boot any gsi/dssi AFAIK.
Only sometimes installing gapps requires resize system from advanced wipe menu.

thanks.. any build for havoc 2.9 ?

How can I remove the bottom pad that appears when I want to use the keyboard?

itsm03 said:
thanks.. any build for havoc 2.9 ?
Click to expand...
Click to collapse
the best 2.9 build here:
https://sourceforge.net/projects/ha...90912-phhgsi_arm64_a-Official.img.xz/download
1- wipe system data cache
2-flash havoc 2.9 and boot up to system
3- reboot to twrp and :
4- flash offline charger fix for pie
5- flash nfc patch for pie
6- flash hwcomposer ( follow instructions )
7- flash gapps and magisk ( optional )
Enjoy.
All flashable patches you find them here:
https://forum.xda-developers.com/p10-lite/how-to/gsis-manual-fixes-hi6250-devices-t3936745
ghassan haddad said:
How can I remove the bottom pad that appears when I want to use the keyboard?
Click to expand...
Click to collapse
Join https://t.me/hi6250group telegram group , there you can share your screenshots to understand the issue.

Hami_Do said:
Join https://t.me/hi6250group telegram group , there you can share your screenshots to understand the issue.
Click to expand...
Click to collapse
I Couldn't post pictures since new members need to wait, add to that I got only one answer telling me that it may not be possible.
I was referring to this pad in the picture

Now Gsi's based on v207 and later are stable , here you find latest Havoc Q gsi :
https://sourceforge.net/projects/expressluke-gsis/files/HavocOS/Ten/ARM64/A/
Probably only NFC patch is needed :
https://forum.xda-developers.com/p10-lite/how-to/gsis-manual-fixes-hi6250-devices-t3936745/page3
=========

No way to boot on my phone (WAS-LX1A)...stuck on boot, after some minutes its reboot, other minutes and then goes in erecovery.
I tried also a totally clean install starting with last firmware stock (WAS-LX1AC432B390) install (dload method) and then flashing Havoc 3.0 (based on v207) system file from fastboot.
Nothing to do and I came back beaten to Android 8.0
.....any help pls?
or maybe it is easier to buy a P30 lite
Tx
Toti

Achieve is currupt :-/

i get Error while flashing image, here is the log

Erro 255
I get error while flashing image here is the log

I have the saame problem on WAS-LX1
anvetoti said:
No way to boot on my phone (WAS-LX1A)...stuck on boot, after some minutes its reboot, other minutes and then goes in erecovery.
I tried also a totally clean install starting with last firmware stock (WAS-LX1AC432B390) install (dload method) and then flashing Havoc 3.0 (based on v207) system file from fastboot.
Nothing to do and I came back beaten to Android 8.0
.....any help pls?
or maybe it is easier to buy a P30 lite
Tx
Toti
Click to expand...
Click to collapse
Any help?
Help this guy and me, please!

From my experience with flashing this device it is most likely that either your device is still encrypted or there are magisk leftovers or data partition wasn't wiped correctly, that's causing rom not to boot. And always use pretoriano's twrp_0.5_test, works best. Sometimes it boots to erecovery, but you can try to reboot and it might work then.

NeoPreacher said:
From my experience with flashing this device it is most likely that either your device is still encrypted or there are magisk leftovers or data partition wasn't wiped correctly, that's causing rom not to boot. And always use pretoriano's twrp_0.5_test, works best. Sometimes it boots to erecovery, but you can try to reboot and it might work then.
Click to expand...
Click to collapse
I think you're right, I also think it's due to encryption or data partition (not magisk because I made a clean installation), because I had the same problem, stuck on boot, with all the Roms (PIE and Q) that require TWRP.
The only rom without problems was OpenKirin-OmniROM Pie Alpha 6.2 which does not require a custom recovery for installation !!
Do you have any operational suggestions to give me or I just have to try with pretoriano's twrp_0.5_test ??
What do you think if :
- In a stock recovery I do a factory reset
- From fastboot I do fastboot erase system, userdata and cache (or better to use format command for userdata?)
- the I flash system.img
- then I flash TWRP
- and then install magisk and gapps from TWRP?
TX