Unofficial TWRP for Oneplus X (Onyx)Additional Features over Official TWRP:
AROMA compatible/supported/working
Compatible with newer EMMC models
Encryption Support
NTFS Support
Fixed Date/Time
Better In-Recovery Power Management
Decreased Boot Time
Synced with latest TWRP Patches
OREO Images/ROMs support.
No SuperSU by default.
No TWRP app.
No HTC Dumlock cruft.
Updated pigz compressor (slightly faster and more tolerant of corruption).
Green Theme by Sultanqasim.
Fixed remote wipe process (Earlier remote wipe issued from play account wasnt processed due to twrp)
Remove android reboot during password check on multiple wrong inputs.
Switched to LZMA compression to decrease size.
Faster I/O performance.
Various twrp upstream patches and fixes.
Downloads: https://www.androidfilehost.com/?w=files&flid=177316
Flashing Instructions:
Using Existing TWRP:
Reboot to recovery > Click on Install > Install Image > recovery > select recovery image and flash > reboot to recovery
Other methods:
https://twrp.me/devices/oneplusx.html
Few Points to remember:
This Recovery should only be used for flashing when you are on New Bootloader
This recovery MUST NOT be used to flash a ROM that is based on old bootloader
Using this recovery, you may break the OTA. So it is advised that you should not flash OTA with this. Rather, Download OTA zip and then flash (Only if you know what you are doing)
Credits:
> TWRP Team
Known Issues:
> Reboot on installing aroma zip for the second time without rebooting recovery or system. [workaround: reboot recovery after flashing aroma zip if you want to flash it again/twice]
Kernel Source:
https://github.com/CheckYourScreen/Arsenic.Kernel-rebased/tree/twrp
XDA:DevDB Information
[RECOVERY][AROMA][UNOFFICIAL] TWRP-3.2.1-r16, Tool/Utility for the OnePlus X
Contributors
CheckYourScreen
Source Code: https://github.com/CheckYourScreen/android_bootable_recovery
Version Information
Status: Testing
Current Stable Version: r16
Stable Release Date: 2018-01-12
Current Beta Version: r1
Beta Release Date: 2017-05-03
Created 2017-05-03
Last Updated 2018-01-12
|| Changelogs ||
r16 -
Updated to TWRP-3.2.1 source
OREO Images/ROMs support.
No SuperSU by default.
No TWRP app.
No HTC Dumlock cruft.
Updated pigz compressor (slightly faster and more tolerant of corruption).
Green Theme by Sultanqasim.
Fixed remote wipe process (Earlier remote wipe issued from play account wasnt processed due to twrp)
Remove android reboot during password check on multiple wrong inputs.
Switched to LZMA compression to decrease size.
Faster I/O performance.
Various twrp upstream patches and fixes.
r1 -
* initial release
Hi Folks!
I generally dont prefer Original Dev. Section for making threads but this one is an Exception, dont want it to get buried under pages
Here's first public beta release of twrp with working AROMA, yep thats right.
You can flash any Aroma installer zip, one minor glitch is there (mentioned in known issues) which I'll fix after my exams are over.
Dont forget to report issues here if you find any!
Reserved
Nimit the God ✌?
We owe you our lives for the recovery finally we have aroma compatibility.
P. S first post ?
Now here is my totally useful comment:
Second
But actually, great work Nimit. Thanks for the time and effort you put into making onyx great again.
Good luck with your exams
Yes to the big dev for onyx
TNX! alot @CheckYourScreen
If we meet in Delhi.. You get a treat for sure.. Thanks
Sent from my ONE E1003 using XDA-Developers Legacy app
Great work .
Great work. thank
Great work again! And thank you. Again!
thank u so much, @CheckYourScreen
Wow wow wow! Thanks dev! All the best for your exams!
Big Thanks @CheckYourScreen ... nice!
I don't want to nitpick here , but the hardware buttons aren't working.
ChzeRub said:
I don't want to nitpick here , but the hardware buttons aren't working.
Click to expand...
Click to collapse
They were disabled intentionally in official twrp and I'd like to keep them as it is, disabled.
CheckYourScreen said:
[*]AROMA compatible
Click to expand...
Click to collapse
Can you explain what this means? I'm aware of what an aroma installer is, but do I gather that they don't work with stock TWRP?
Sorry its a bit of a noob question even though I don't consider myself a noob lol.
kgr said:
Can you explain what this means? I'm aware of what an aroma installer is, but do I gather that they don't work with stock TWRP?
Sorry its a bit of a noob question even though I don't consider myself a noob lol.
Click to expand...
Click to collapse
It means aroma zips will work
Sent from my ONE E1003 using Tapatalk
kgr said:
Can you explain what this means? I'm aware of what an aroma installer is, but do I gather that they don't work with stock TWRP?
Sorry its a bit of a noob question even though I don't consider myself a noob lol.
Click to expand...
Click to collapse
Corrected, it means Aroma installer works with this recovery. All other features listed in the first post are not present in official twrp.
Hi @CheckYourScreen, do u plan on updating this to 3.1.1?
Related
Samsung Galaxy Tab 2
AOSP - Project
This Rom is based on AOSP to give the user a pure AOSP feeling.
The builds only includes device specific changes to compile and get a booting AOSP!
Code:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modifications, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
Downloads:
ROM Downloads for all supported devices can be found here
(Those who have a repartitioned system partition use "not-block-based" builds! Other builds won't be flashable on those devices!)
[#DONATETOME]
FAQ
Q: Will there be any updates?
A: Yes, there will, but only if i can fix a bug or AOSP releases an Update - else there's no update needed.
Q: There's a nice feature in XXX-Rom and i like to have this included - ADD IT!
A: Sorry, i'lll keep this Rom Stock-AOSP as possible. Maybe XXX-Rom is a better choice for you, if you really need this feature.
Q: How to enable root?
A: This Rom doesn't have root included. Why? Because root isn't part of AOSP. You can find the way to SuperSU Thread from @Chainfire and download SuperSU as flashable-ZIP if you need root.
Q: Is it possible to overclock the kernel?
A: Yes and no. First of all you need root and a Kernel-App like KernelAdiutor. After that you can slight OC the CPU & GPU - this Rom includes latest SlimLP Kernel.
Q: I found a bug.
A: Nice finding my friend Please provide needed logs - ADB will be your best friend, if you are replying in a development thread
There's a lot of tutorials out on YouTube or XDA on how to setup and use ADB - it's really simple!
At least you should tell step by step how to reproduce the issue.
I started creating a gerneral FAQ on my github - it includes instructions how to flash a Rom, how to get proper logs, etc. etc. etc., you can find it here
Changelog
Code:
2015-11-08 It's stock AOSP as released by Google (Android 5.1.1 R29 LVY48I), only additions
- screenshot: quick delete action
- advanced reboot menu
- Launcher3 instead Launcher2
- BootMessage: Show each app name being optimized during boot
- Show application's package name in the "App info" screen.
- Open app when clicking on icon in App Info screen
(... forgot about the releases between ...)
2015-08-07 based on Android 5.1.1_r9
XDA:DevDB Information
[P31xx][5.1.1] Samsung Galaxy Tab 2 AOSP-Project, ROM for the Samsung Galaxy Tab 2
Contributors
Android-Andi
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2015-08-07
Last Updated 2017-04-30
Wow! Andi!
Nice to see that AOSP Lollipop came to us again! Great work dev, @Android-Andi ?
Sent from my GT-P3100 using Tapatalk
Amazing, pure LP AOSP for my tab 2.
I really appreciate it...
Is f2fs in Cache and Data supported in this ROM?
Sent from my GT-P3100 using Tapatalk
Bhaskara Rao said:
Is f2fs in Cache and Data supported in this ROM?
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
No, sry. Think it needs quite more changes than i would like to add... But i will take a closer look next time
Wow, this is awesome. Now I need to see if I can port Layers on top. Thanks Andi!!!
Sent from my Nexus 6 using Tapatalk
Thank you, Andi for the latest AOSP. No issues on clean installation. ROM is fluid. YouTube is not working. Logs attached.
Bhaskara Rao said:
Thank you, Andi for the latest AOSP. No issues on clean installation. ROM is fluid. YouTube is not working. Logs attached.
Click to expand...
Click to collapse
Thanks buddy I'll look into it next week, have some more time then
Clean install of latest AOSP (aosp_p3110-20150807.zip) with Dhollmen 3.0.101 kernel.
Youtube is working, but 720P videos do not work.
ilyichspb said:
Clean install of latest AOSP (aosp_p3110-20150807.zip) with Dhollmen 3.0.101 kernel.
Youtube is working, but 720P videos do not work.
Click to expand...
Click to collapse
Hey bruh @ilyichspb i also want to flash my kernel
I have tried but i softbricked my tab.
So,it will be great if you tell me the steps to flash a kernel.:laugh:
Aosp is smooth and lagfree.great work Andi.:fingers-crossed::good:
AFAIK Dhollmen Kernel doesn't have a fix for emmc bug. Only Android-Andi's ROMs and Recoveries have it. Take an informed decision before flashing custom kernels.
Sent from my GT-P3100 using Tapatalk
[email protected] said:
So,it will be great if you tell me the steps to flash a kernel.:laugh:
Click to expand...
Click to collapse
full wipe
install (via CWM)
AOSP
kernel
gapps
reboot
---------- Post added at 07:41 AM ---------- Previous post was at 07:39 AM ----------
Bhaskara Rao said:
AFAIK Dhollmen Kernel doesn't have a fix for emmc bug. Only Android-Andi's ROMs and Recoveries have it. Take an informed decision before flashing custom kernels.
Click to expand...
Click to collapse
Looks like you are right. I will keep an eye on that. So far everything is working fine.
Seems like google went to nightly builds, r12 source released
Thanks!, will try soon
What is the recommended recovery to install this rom. I'm still running old ketut's stock rom. Thanks
Android-Andi's latest TWRP.
https://www.androidfilehost.com/?w=files&flid=25704
Sent from my GT-P3100 using Tapatalk
Bhaskara Rao said:
Android-Andi's latest TWRP.
https://www.androidfilehost.com/?w=files&flid=25704
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
Whenevr i go to recovery i.e,twrp wipe>advance wipe>change system partition
Twrp says invalid partition select
I have tried this in both android andi's twrp and official twrp
I'm on p3100.
What to do.need help:victory:
I want to flash a rom withf2fs support thats why
[email protected] said:
Whenevr i go to recovery i.e,twrp wipe>advance wipe>change system partition
Twrp says invalid partition select
I have tried this in both android andi's twrp and official twrp
I'm on p3100.
What to do.need help:victory:
I want to flash a rom withf2fs support thats why
Click to expand...
Click to collapse
AOSP doesn't support f2fs.
About f2fs: take my twrp with "f2fs" in it's name. If you have more question about recovery then use the recovery thread pls.
Android-Andi said:
AOSP doesn't support f2fs.
About f2fs: take my twrp with "f2fs" in it's name. If you have more question about recovery then use the recovery thread pls.
Click to expand...
Click to collapse
Sorry! I got the sol of my problem
i didnt select cache and data before tapping on change partition
One question
Does Your latest recovery i,e. 2.8.7.1 supports f2fs.
i want to post this in recovery thread but xda said that u have less than 10 posts
RECOVERY
TWRP & CM-Recovery
Z00A/Z008 ( LP Bootloader)
Just as the title says these are unofficial recovery builds for Asus Zenfone 2 Z00A and Z008 models
These have been tested and confirmed functional. These are built from current CM devices trees, CM kernel source. Source links provided below. If you find any bugs please report with an attached recovery log.
DOWNLOAD
Current Versions provided for both devices
TWRP 2.8.7.3 (LP based)
TWRP 2.8.7.7 (M based)
CM-Recovery 9-28-15 (LP based)
CM-Recovery 12-22-15 (M based)
{ Cm-Recovery doesn't use "version" tags so using build date as a version # }
SOURCES
Recovery built in a CM-12.1/13.0 environment respectively using device trees/kernel
from our CM device trees/kernel CM-zenfone2 github
Z00A LP Tree HERE
Z008 LP Tree HERE
Z00A M Tree HERE
Z008 M Tree HERE
Kernel Source
CM-Recovery source from CM-recovery
TWRP source tyipically from Omnirom
HOWEVER 2.8.7.6 beta uses modified TWRP source from omnirom (and patched from thier gerrit) from
HERE
Code:
Changelog:
1-22-16:
TWRP 2.8.7.7
- fixed OTG & external SDCARD mount
- from TWRP: language support, code cleanup and minor fixes(see twrp github for full list)
- this is pre-release testing main ly for soon to be released TWRP 3.0
12-22-15:
* updated builds
* should fix backups in TWRP
* should fix issues flashing newer ROMS after 12-17-15
12-7-15
* 2.8.7.5 TWRP builds
* fixed opengapps flashing
12-6-15
* split into new thread
* Marshmallow based recoveries now live
* TWRP is WIP prior to next major official tag, new theme included for testing
Z00A/Z008 ( MM Bootloader)
Just as the title says these are unofficial recovery builds for Asus Zenfone 2 Z00A and Z008 models
These have been tested and confirmed functional. These are built from current CM devices trees, CM kernel source. Source links provided below. If you find any bugs please report with an attached recovery log.
DOWNLOAD
Current Versions provided for both devices
TWRP 3.0.2-M1 (MM based)
SOURCES
Recovery built in a Omnirom-6.0 environment respectively using device trees/kernel below
Z00A/Z008 MM Tree HERE
Kernel Source HERE
TWRP source tyipically from Omnirom
Code:
Changelog:
Initial source built MM bootloader friendly based recovery release
Z00D
Just as the title says these are unnoficial recovery builds for the Asus Zenfone 2 Z00D (ze500cl) model
These have been tested and confirmed functional. These are built from experimental devices trees, modified Stock kernel source. Source links provided below. If you find any bugs please report with an attached recovery log.
DOWNLOAD
Current Versions provided for both devices
TWRP 3.0.2-0
SOURCES
Recovery built in a omnirom environment respectively using device trees/kernel
from our my github
Device Tree
Kernel Source
Code:
Changelog:
5-3-16: Initial TWRP build
XDA:DevDB Information
Zenfone2 Recovery, Tool/Utility for the Asus ZenFone 2
Contributors
jrior001, crpalmer
Source Code: https://github.com/CM-zenfone2
Version Information
Status: Beta
Beta Release Date: 2015-12-06
Created 2015-12-07
Last Updated 2016-08-03
Niceeeeeeeeeeeeeeeee
Well this was unexpected, thank you so much for this!
Edit: Well I tried the MM version, and I must say I love the new look! It's kinda laggy, but that's very expected and I got a recovery log.
Aceofzeroz said:
It's kinda laggy, but that's very expected and I got a recovery log.
Click to expand...
Click to collapse
TWRP still uses some really old code for pixelflinger. We have been using a JB era patch from Intel to add x86 optimized acceleration, which Dees_Troy(TWRP dev) and the zenfone5/6 devs ported to KK & LP. I updated it for M, but this is about as good as it gets until TWRP overhauls that section of their code. Without this patch is basically unusable.
And yes the new theme is sexy It's months in the making from TWRP contributer @z31s1g and it's quite lovely.
jrior001 said:
TWRP still uses some really old code for pixelflinger. We have been using a JB era patch from Intel to add x86 optimized acceleration, which Dees_Troy(TWRP dev) and the zenfone5/6 devs ported to KK & LP. I updated it for M, but this is about as good as it gets until TWRP overhauls that section of their code. Without this patch is basically unusable.
And yes the new theme is sexy It's months in the making from TWRP contributer @z31s1g and it's quite lovely.
Click to expand...
Click to collapse
Ah, I understand the situation now and glad that the patch worked out for the time being. Definitely better than not having the latest TWRP to play with, so my highest gratitude for the amazing work bringing up Marshmallow in time for the holidays! :thumbup:
Sent from the Ace's MB865 using Tapatalk
This is a bit wonky with device encryption. It'll boot the recovery without a theme loaded and ask for my pattern (as expected). I'll put that in and it'll decrypt and mount storage, then the "put in your pattern" prompt comes up again (this time, with my twrp theme loaded). I can cancel that prompt just fine and it'll sit on the main screen and I can proceed from there, so it's not a showstopper at least.
This didn't happen on 2.8.7.3.
edit: on flashing opengapps 6.0 micro, I'm warned that the recovery is missing the xz binary and can't flash the zip (and told me to update to the latest recovery for my device, lol). I'll upload the generated log shortly.
edit edit:
Code:
# Begin Open GApps Install Log
-----------------------------------------------------------------------------
ROM Android Version | 6.0
-----------------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: The installer detected that your recovery does not support
XZ decompression. Please update your recovery or switch to another one like TWRP.
# Begin User's gapps-config
# End User's gapps-config
Fortunately, flashing my L-gapps seems to have worked fine (...seeeeeems to. I'll see if it works. The setup app did at least update itself, so there's that.)
Is there an easy way to update my TWRP? Any apps that can do this for me?
roach9 said:
Is there an easy way to update my TWRP? Any apps that can do this for me?
Click to expand...
Click to collapse
I know Flashify can do that in many devices, I am not sure about ours, I think best way would be to flash it using fastboot.
Marshmallow recovery can be used to flash lollipop Rom...??..and vice versa...??
Any difference for 2.8.7.4 vs .3 other than the look? Googled it and found nothing.
Sayan44 said:
I know Flashify can do that in many devices, I am not sure about ours, I think best way would be to flash it using fastboot.
Click to expand...
Click to collapse
Why not via TWRP itself? TWRP has a feature to flash an .img directly to boot or recovery.
Sent from my ASUS_Z00AD
I am on 2.8.7.3. I am thinking to flash cm13. Is it necessary to update twrp? Or I can flash cm13 using my old one?
Sent from my ASUS_Z00A using Tapatalk
rex_perfect said:
Marshmallow recovery can be used to flash lollipop Rom...??..and vice versa...??
Click to expand...
Click to collapse
Pretty much, LP version is stable and works for flashing M ROMs.
Sent from my ASUS_Z00A using Tapatalk
espeon said:
This is a bit wonky with device encryption. It'll boot the recovery without a theme loaded and ask for my pattern (as expected). I'll put that in and it'll decrypt and mount storage, then the "put in your pattern" prompt comes up again (this time, with my twrp theme loaded). I can cancel that prompt just fine and it'll sit on the main screen and I can proceed from there, so it's not a showstopper at least.
This didn't happen on 2.8.7.3.
edit: on flashing opengapps 6.0 micro, I'm warned that the recovery is missing the xz binary and can't flash the zip (and told me to update to the latest recovery for my device, lol). I'll upload the generated log shortly.
edit edit:
Code:
# Begin Open GApps Install Log
-----------------------------------------------------------------------------
ROM Android Version | 6.0
-----------------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: The installer detected that your recovery does not support
XZ decompression. Please update your recovery or switch to another one like TWRP.
# Begin User's gapps-config
# End User's gapps-config
Fortunately, flashing my L-gapps seems to have worked fine (...seeeeeems to. I'll see if it works. The setup app did at least update itself, so there's that.)
Click to expand...
Click to collapse
Will look into both issues, I am encrypted currently but without a pin/pattern and don't have that issue.
Sent from my ASUS_Z00A using Tapatalk
So what's the difference of this TWRP and TheSSJ TWRP?
jrior001 said:
Will look into both issues, I am encrypted currently but without a pin/pattern and don't have that issue.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
The 2nd one happened after I decrypted; I forgot to mention that. I don't think it actually happened when I was encrypted using the L-based recovery (I upgraded my recovery, then decrypted, then tried flashing the rom + gapps)
Thread moved to proper forum
jrior001 said:
Will look into both issues, I am encrypted currently but without a pin/pattern and don't have that issue.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Having the same issue actually, not encrypted, worked on .3 no pin or lock on screen either. Happened trying to install the latest Gapps package.
Heavybullets said:
Having the same issue actually, not encrypted, worked on .3 no pin or lock on screen either. Happened trying to install the latest Gapps package.
Click to expand...
Click to collapse
ended up fastboot installing the recovory, didnt work, factory reset, then try it, didn't work, fixing permissions, all that, nothing has worked for me, the latest .4 twrp still comes up with that "The installer detected that your recovery does not support
XZ decompression." Error.
Heavybullets said:
ended up fastboot installing the recovory, didnt work, factory reset, then try it, didn't work, fixing permissions, all that, nothing has worked for me, the latest .4 twrp still comes up with that "The installer detected that your recovery does not support
XZ decompression." Error.
Click to expand...
Click to collapse
well yeah when you have a missing binary reflashing it probably isn't going to do anything, assuming it didn't get corrupted
I'm pleased to present my MoDaCo Custom ROM for the Honor 6 H60-L04!
READ THIS WHOLE POST BEFORE YOU START! No, really, it contains everything you need to know.
About MoDaCo Custom ROMs
MoDaCo Custom ROMs are based on official ROMs. A MCR release is designed to feel like a stock Emotion UI ROM with optimisations, tweaks and complimentary additions that enhance the user experience. The aim of a MCR is to be ultra reliable for use on an everyday device.
This ROM is part of the 'Unified Honor ROM' project - ROMs with the same changes are available for all current Honor devices.
A MCR version with a more 'stock Android' like interface is under development.
Requirements
In order to use this ROM you must have a custom recovery (e.g. TWRP) installed. The ROM is installed at your own risk. A wipe IS recommended if coming from a ROM other than MCR or stock. BACK UP YOUR DEVICE BEFORE INSTALLATION!
Features
Based on the B820 custom ROM starter template (you may use MCR as a base for your own ROM)
ROM fully optimised with the unique MCR scripts
Updated power management policies to reduce instances of 'missing notifications'
All apps in ROM updates to latest versions (a considerable saving of over 1GB on /data!)
Busybox installed
sepolicy patched boot image ready for root
selinux permissive
Removed 'icons' from /system/themes (themes no longer need to include default icons again)
MoDaCo Custom Kitchen (coming soon!)
Multi user support
Multi window support
Preloaded Stockify theme stub
Numerous other small refinements - please see the gitlab commits for full details
This ROM is completely in version control at gitlab! https://gitlab.com/u/paulobrien/projects
Want more tweaks and changes? Post your requests in the support topic.
Changelog
Please see the post below this one for the changelog.
Installation
You should install this ROM on a device that has previously been updated to the B820 release.
To install this ROM:
Download the zip file from the links below and copy to your internal / external SD card.
Restart your device in recovery mode
PERFORM A BACKUP FROM THE MENU
Select the option to apply an update zip, and select the zip file you copied to the SD card.
Important Note: As this ROM is partially deodexed, first boot can take a long time. If you have not wiped, you can check for any issues with adb logcat. Be patient!
Downloads
Please do not mirror these downloads elsewhere.
DOWNLOAD - r7-modacocustomrom-honor-6-h60l04-mogolia-b820.zip [ROMRAID] MD5: 915537f165033704724152b81877763b
Support
If you have a general question, please post in the topic.
Thanks
It's impossible to mention everyone who contributes to the Android community by name, but to everyone out there who does great work and shares it with us all - you have my gratitude and respect.
Future Updates - READ THIS!
By providing this ROM I am not guaranteeing that future updates will follow. Due to limits on my time and the fact that I have a large number of devices for short periods of time, it isn't possible for me to continue providing ROM updates indefinitely.
And finally...
Enjoy!
P
Changelog
r7
Updated to bring ROM in line with other Honor devices, as part of unified ROM project.
Preparation for 'stock style' release
Application updates
r1
Initial release
Screenshots? ^^
Venipa said:
Screenshots? ^^
Click to expand...
Click to collapse
Yes we need some screenshots...
i'll try your rom next sunday
i flashed it via "mogolia" twrp and ain't changing. just rebooting to my latest rom
Hello,tell me please,this rom install on b822 normal?
/edit /
Future request
- dark theme
- working firewall, like afwall+
- custom softkey behavior, like longpress back to kill app or longpress home to switch to last app
Thanks for bringing up some custom rom for our H6. @paulobrien
leechseed said:
Same here.
Just some apps (not all cust) got installed and i lost root.
Future request, after its flashable
- dark theme
- working firewall, like afwall+
- custom softkey behavior, like longpress back to kill app or longpress home to switch to last app
Thanks for bringing up some custom rom for our H6. @paulobrien
Click to expand...
Click to collapse
Use the TWRP provided via Multitool. Worked absolutely fine here.
/edit/
My fault sorry.
i did the same. flashed via both twrps and wiped data. no changes
Rom is based on B820 dont expect any UI changes. Basicly tweaks for system and performance. Also updater is changed to MoDaCo updater to expect OTA updates.
Working on the next revision!
P
Sent from my VIE-L09 using Tapatalk
paulobrien said:
Working on the next revision!
P
Sent from my VIE-L09 using Tapatalk
Click to expand...
Click to collapse
Updates through the updater?
Unless emui is not out of the rom i will not use it..
Rakpere said:
Rom is based on B820 dont expect any UI changes. Basicly tweaks for system and performance. Also updater is changed to MoDaCo updater to expect OTA updates.
Click to expand...
Click to collapse
I flashed it and didn't notice even busybox installed
hello!!
how does the battery ........... !!!
kole_anba said:
hello!!
how does the battery ........... !!!
Click to expand...
Click to collapse
Battery absolutely fine on my end, rooted with L-Speed tweaker. Easily 2 days worth of juice for me
Use the latest TWRP 3.0.
very nice
paulobrien said:
Working on the next revision!
P
Sent from my VIE-L09 using Tapatalk
Click to expand...
Click to collapse
Is it possible to follow your progress?
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
DOWNLOAD: Fixed....
Things that are different from official build:
fixed wrong theme color in screenshots on OP6.
Add support for QCOM haptics vibrator. (fixed vibration)
BUGS:
mtp (causes kernel panics) (can add a test build if needed)
flashing aroma packages
If you have found a bug, please consider posting it to our github issues log and then I'll report to Dess_Troy. If you have a significant problem that cannot be answered in this thread, your best bet is to PM Dees_Troy directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDAevDB Information
[RECOVERY][enchilada] TWRP 3.2.3-0 Touch Recovery [UNOFFICIAL]
Contributors
Joemossjr
Dees_Troy
wuxianlin
@notsyncing on github for the fixes
Source Code: Github
ROM OS Version: 8.x Oreo
Version Information
Status: Testing
Created 2018-07-07
Last Updated 2018-08-01
Donation Link: Buy this man a beer
Thanks for this. Add the version that supports MTP. Will test and let you know!
It's definitely bugged lol but I'll add it tomorrow
Thank you very much!
joemossjr said:
It's definitely bugged lol but I'll add it tomorrow
Click to expand...
Click to collapse
I'm working with your 3.2.1 version since the beginning and except aroma absolut everything is working. Never had any issue with MTP. Always worked stable so far. I did countless restores and all worked flawless even with swipe code in place.
So thanks very much to provide us with the very first working TWRP for the OP6.
Regarding aroma support, would you agree to my feeling that this is not an issue to be solved in the twrp framework but probably being a bootloader or firmware issue?
Simple temporary fix to avoid kernel panic on mtp:
Do not connect usb cable
Toogle unmount mtp, wait few second and enable mtp again in mount menu in recovery. Connect usb.
xXx said:
I'm working with your 3.2.1 version since the beginning and except aroma absolut everything is working. Never had any issue with MTP. Always worked stable so far. I did countless restores and all worked flawless even with swipe code in place.
So thanks very much to provide us with the very first working TWRP for the OP6.
Regarding aroma support, would you agree to my feeling that this is not an issue to be solved in the twrp framework but probably being a bootloader or firmware issue?
Click to expand...
Click to collapse
I'll be getting logs tonight while flashing an aroma package to see what's needed lol I feel like it's something simple but we will see. Thanks for the support everyone I do this on my free time lol I'll post the mtp enabled here shortly
mtp has been added to the downloads folder and is specified in the name!
https://github.com/opengapps/opengapps/issues/493
seems like its a dead issue at the moment on twrp. aroma hasnt been updated in a while. I am in contact with a dev who may know how to fix it. Stay tuned
joemossjr said:
https://github.com/opengapps/opengapps/issues/493
seems like its a dead issue at the moment on twrp. aroma hasnt been updated in a while. I am in contact with a dev who may know how to fix it. Stay tuned
Click to expand...
Click to collapse
thanks, very much appreciated :highfive:
joemossjr said:
mtp has been added to the downloads folder and is specified in the name!
Click to expand...
Click to collapse
Yes I have tested it and can confirm it's working. Just make sure you unmount mtp and remount it before attaching the USB cable (thanks to @DocRambone for the tip)
DocRambone said:
Simple temporary fix to avoid kernel panic on mtp:
Do not connect usb cable
Toogle unmount mtp, wait few second and enable mtp again in mount menu in recovery. Connect usb.
Click to expand...
Click to collapse
This works, thanks!
It's not working for me both new versions. Boot looped.
Sent from my ONEPLUS A6003 using XDA-Developers Legacy app
mbr007 said:
It's not working for me both new versions. Boot looped.
Click to expand...
Click to collapse
Did you remember to flash magisk after reboot into twrp?
lollyjay said:
Did you remember to flash magisk after reboot into twrp?
Click to expand...
Click to collapse
Yeah you have to flash magisk if you already had it flashed before hand
joemossjr said:
mtp has been added to the downloads folder and is specified in the name!
Click to expand...
Click to collapse
I just flashed your new mtp enabled zip version and screen brightness went down considerably even it's on 100% already. Does anybody know a workaround to get it brighter again?
Can you add another mirror like androidfilehost please? Unable to access google drive...
xXx said:
I just flashed your new mtp enabled zip version and screen brightness went down considerably even it's on 100% already. Does anybody know a workaround to get it brighter again?
Click to expand...
Click to collapse
Seems to be a general problem. I've the same, but not only with this version of TWRP, also with the original version.
It starts by me sometimes flashing 3.2.1.0 if i remember right and I never found a solution to get the screen brightness full back again ?
adiher said:
Seems to be a general problem. I've the same, but not only with this version of TWRP, also with the original version.
It starts by me sometimes flashing 3.2.1.0 if i remember right and I never found a solution to get the screen brightness full back again ?
Click to expand...
Click to collapse
I can make a new build that's higher
joemossjr said:
https://github.com/opengapps/opengapps/issues/493
seems like its a dead issue at the moment on twrp. aroma hasnt been updated in a while. I am in contact with a dev who may know how to fix it. Stay tuned
Click to expand...
Click to collapse
Could this have anything to do with why aroma isn't working?
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page5
From the magisk 16.6 change log.
Note to ROM Developers
If you are embedding Magisk Zip into your ROM, and your ROM uses Aroma Installer, please be aware that on some devices (most likely Samsung devices), it is possible that the installation process of Magisk could break Aroma. Please test flashing your ROM zip before releasing to your users. If you found out you are the few unfortunate devices, unzip the Magisk zip, and do the following changes and re-zip the installer:
Code:
# Remove or comment out these 2 lines in META-INF/com/google/android/updater-script eval $BOOTSIGNER -verify < $BOOTIMAGE && BOOTSIGNED=true $BOOTSIGNED && ui_print "- Boot image is signed with AVB 1.0"
The reason why Aroma Installer breaks is unknown. Maybe consider letting the project that's abandoned for nearly 5 years go?
Dragonfly Kernel v1.5 for the LG G8 Korean / US
Introduce
First of all, I'd like to thank Metaphysics team for giving the first custom kernel of G8 USA. Unfortunately I'm using G8 - Korean and they haven't released version for the Korean variant yet. I had to learn how to build a kernel for myself based on their kernel source. However, I want to learn more so I decided to compile the kernel from LGE open source. Now, my kernel is quite stable to be released and shared to the G8 community. You can call it the Dragonfly kernel.
Main Features:
- Based on LGE open source LMG820N_Android_Q_v20r: http://opensource.lge.com/osSch/list?types=NAME&search=g820n
- Linux-Stable-Upstream included to latest 4.14.205
- Next-Gen CAF-Tag LA.UM.8.11.r1-02600-NICOBAR.0 merged
- Regular CAF-Tag for SD855 merged LA.UM.8.1.r1-16200-sm8150.0
- Compiled by ProtonClang 12.0.0 with -O3 speed optimizations
- No VLAs
- Magisk included
- F2FS support
EAS related features:
- EAS implementation patched up to latest CAF state
- Disable autogroups and use cgroups for more efficient task placement
- CPU input boost
File System related features:
- Include rapid GC by @arter97
Network related features:
- Wireguard Support (Details)
- Add new TCP congestion algorithm: BBR2, agilesd
Memory related features:
- Include zstd
Wakelock Blocker:
- Add Boeffla Wakelock Blocker v1.1.0
- The most common and safe wakelocks are blocked by default: qcom_rx_wakelock;wlan;wlan_wow_wl;wlan_extscan_wl;netmgr_wl;NETLINK
How to flash the Kernel:
- You can flash the kernel zip file via TWRP or Magisk
- You can also extract the new_boot.img to flash it via fastboot mode
Known bugs:
- You tell me
DOWNLOAD:
Download is located always in
https://github.com/anht3889/LGE_G820_Kernel_Caf/releases
Important: Read after Download
Be sure to turn off Secure start-up before flash this kernel
Credits:
- Metaphysics kernel team: https://github.com/KamioRinn/Metaphysics_LGE_G820_Kernel
- SGCMarkus for his guide of building kernel and TWRP
- Erick G for bringing new TWRP to G8 which supports F2FS
- Jean Carlos Bencosme for adding / picking kernel features
- Kirisakura for his great kernels
- Sultanxda for his simple_lmk
- LGE for the kernel open source
- All other great kernel devs
Contributors
quantan
Source Code: https://github.com/anht3889/LGE_G820_Kernel_Caf
XDA:DevDB Information
Dragonfly, Kernel for the LG G8
Contributors
quantan
Kernel Special Features:
Version Information
Status: Stable
Created 2020-09-16
Last Updated 2020-11-14
Previous versions, e.g. v1.4, don't work with the new TWRP 3.4. Therefore, I use Anykernel from v1.5. I recommend you follow the steps below:
1. Install magisk patched stock boot.img
2. Install new TWRP 3.4 from Magisk Manager
3. Reboot to TWRP
4. Install Magisk and reboot to TWRP
5. Install Disable Verity zip file and reboot to TWRP
6. Install my kernel Dragonfly v1.5
For newer version, i.e. v1.6, you don't need to repeat all steps above. You just want to flash thew newest Dragonfly.
And good news to you guys, TWRP 3.4 supports F2FS so I decided to enable F2FS support in my kernel as well. To make F2FS, please follow these steps:
1. Install my kernel v1.5
2 .Reboot to TWRP 3.4
3. Change file system of /data to F2FS
4. Replace the attached modified fstab to support F2FS of /data
5. Reboot
Note: You will lose your data.
In case you don't know:
- TWRP-3.4.0.0-G820N.zip and fstab.alphaplus for G8 Korean
- TWRP-3.4.0.0-G820UM.zip and fstab.alphalm for G8 US
Give credits to Erick G and @SGCMarkus for bringing TWRP to our phones.
Changelog:
v1.5:
- Fix touch issues for TWRP
- Add Kcal
- Add KLapse v5.0
- Update to 4.14.205
- Update lze and add lzo-lre for Zram
- Use Anykernel
v1.4:
- Import LGE v20r open source changes
- Upstream to linux-stable v4.14.203
- Upstream CAF LA.UM.8.1.r1-16200-sm8150.0
- Fix audio and OK Google hot word issues
- Improve schedutil
- Power saving workingqueues enabled by default
- Change various drivers ( MM, audio) to user power efficient workingqueues. Thanks to @Freak07 's commits
- Update sdcardfs
v1.3:
- Merge tag 'LA.UM.8.11.r1-04300-NICOBAR.0'
- Add ntfs and exfat support
v1.1 - v1.2 - Intial kernel
Good work ...mostly. Huge showstopper is the missing support for exfat/ntfs with sdcard. With USB exfat is working. Only fat32 formatted sdcards are working. But this is a nogo with files > 4GB
tron1 said:
Good work ...mostly. Huge showstopper is the missing support for exfat/ntfs with sdcard. With USB exfat is working. Only fat32 formatted sdcards are working. But this is a nogo with files > 4GB
Click to expand...
Click to collapse
Thank your for pointing it out. I just add exfat and ntfs support to v1.3. Enjoy it
tron1 said:
Good work ...mostly. Huge showstopper is the missing support for exfat/ntfs with sdcard. With USB exfat is working. Only fat32 formatted sdcards are working. But this is a nogo with files > 4GB
Click to expand...
Click to collapse
Which exact Model do you use? Is there a specific german Model nesessary?
Deutschmann said:
Which exact Model do you use? Is there a specific german Model nesessary?
Click to expand...
Click to collapse
It doesn't work on any LG g8s models...
@quantan Could you make it compatible with LG G8s models? LM-G810 is the model code
Hi Guys. The new v1.4 is just released. I have been quite busy due to family and work stuff. Here is the changelog:
- Import LGE v20r open source changes
- Upstream to linux-stable v4.14.203
- Upstream CAF LA.UM.8.1.r1-16200-sm8150.0
- Fix audio and OK Google hot word issues
- Improve schedutil
- Power saving workingqueues enabled by default
- Change various drivers ( MM, audio) to user power efficient workingqueues. Thanks to @Freak07 's commits
- Update sdcardfs
Eduxki said:
@quantan Could you make it compatible with LG G8s models? LM-G810 is the model code
Click to expand...
Click to collapse
I'll check if I can make a version for LG G8s tomorrow. However, I can't guarantee that it will work for G8s or not since I don't have that phone. @Eduxki Give me your model, e.g. LMG810EA, and your operator / country as well. Is Android 10 available for your phone now since this kernel is for Android 10
quantan said:
Hi Guys. The new v1.4 is just released. I have been quite busy due to family and work stuff. Here is the changelog:
- Import LGE v20r open source changes
-...
Click to expand...
Click to collapse
thanks for your hard work! i just installed it on my G820N with latest 20s-fw... seems to be working fine so far.
PS: installed it via TWRP, and had twrp re-inject itself into the boot-img afterwards again.... => would be nice if your prepared installer zip-file would not just include magisk, but also twrp (just as a safety-measure to not loose twrp when installing your kernel.
PPS: after your src rebase/update to that 20r kernel source drop, "dragonfly" is working with my 20s-fw image again!! your previous version with only 20a kernel src only worked until 20m (march sec-patch) firmware, neither 20o nor 20s could run stable on that 20a-kernel. gui hung, apps didn't respond etc... thankful that 20s-fw finally runs stable so far on those 20r-kernel updated version.
kimba99 said:
thanks for your hard work! i just installed it on my G820N with latest 20s-fw... seems to be working fine so far.
PS: installed it via TWRP, and had twrp re-inject itself into the boot-img afterwards again.... => would be nice if your prepared installer zip-file would not just include magisk, but also twrp (just as a safety-measure to not loose twrp when installing your kernel.
PPS: after your src rebase/update to that 20r kernel source drop, "dragonfly" is working with my 20s-fw image again!! your previous version with only 20a kernel src only worked until 20m (march sec-patch) firmware, neither 20o nor 20s could run stable on that 20a-kernel. gui hung, apps didn't respond etc... thankful that 20s-fw finally runs stable so far on those 20r-kernel updated version.
Click to expand...
Click to collapse
Thank you for your feedback. Actually in Dragonfly v1.3 I did lots of changes to schedultil based on Pixel 4 XL kernel. However it didn't work well. Sorry about that. In the v1.4, I revert the changes and make other improvement to schedutil gov.
I'll look into the TWRP injection and hopefully it will be available in v1.5 or 1.6. Any other features you guys want, please let me know.
quantan said:
Thank you for your feedback. Actually in Dragonfly v1.3 I did lots of changes to schedultil based on Pixel 4 XL kernel. However it didn't work well. Sorry about that. In the v1.4, I revert the changes and make other improvement to schedutil gov.
I'll look into the TWRP injection and hopefully it will be available in v1.5 or 1.6. Any other features you guys want, please let me know.
Click to expand...
Click to collapse
as for TWRP integration: keep in mind that there are also separate versions for INTL vs KOR edition of TWRP, just like with the kernel itself!
further ideas? :cyclops: ... fix touchscreen in recovery => code fixes already exist, check here:
https://github.com/ErickG233/LMV500-sm8150_kernel/commit/1b5b93d72ec87054ef2d80c8d955dcdaa40d4332
if i come up with additional ideas i'll let u know.
PS: it's been a while since i last modded/hacked/upgraded android kernels :good:
PPS: maybe sth like the ooooold "crossbreeder" mod =>
https://github.com/f1vefour/CrossBreeder ... but i'm unsure if this is still relevant and or working on "10"... as the original code is rather... dated
Thank you for your efforts. Is there a GSI suitable for g820?
kimba99 said:
as for TWRP integration: keep in mind that there are also separate versions for INTL vs KOR edition of TWRP, just like with the kernel itself!
further ideas? :cyclops: ... fix touchscreen in recovery => code fixes already exist, check here:
https://github.com/ErickG233/LMV500-sm8150_kernel/commit/1b5b93d72ec87054ef2d80c8d955dcdaa40d4332
if i come up with additional ideas i'll let u know.
PS: it's been a while since i last modded/hacked/upgraded android kernels :good:
PPS: maybe sth like the ooooold "crossbreeder" mod =>
https://github.com/f1vefour/CrossBreeder ... but i'm unsure if this is still relevant and or working on "10"... as the original code is rather... dated
Click to expand...
Click to collapse
- The fix for touchscreen in recovery is added to my kernel.
- I currently have no idea about TWRP. I have ramdisk with TWRP but no magisk. Can you install TWRP and Magisk then export boot.img and give it me? I will extract ramdisk from it then integrate the ramdisk to my kernel.
lufan said:
Thank you for your efforts. Is there a GSI suitable for g820?
Click to expand...
Click to collapse
Havoc, Bliss, Lineageos GSI should be good.
quantan said:
- The fix for touchscreen in recovery is added to my kernel.
- I currently have no idea about TWRP. I have ramdisk with TWRP but no magisk. Can you install TWRP and Magisk then export boot.img and give it me? I will extract ramdisk from it then integrate the ramdisk to my kernel.
Havoc, Bliss, Lineageos GSI should be good.
Click to expand...
Click to collapse
It can be used, but it can't double-click the wake-up screen, the display after the screen is not turned off, and the vibration intensity is not adjustable. I backup the g820 boot through twrp, which contains magisk. I hope you can use it
https://drive.google.com/file/d/17I-m9QdmOzn7CXH3hOl-c04Jnvd7GC3P/view?usp=sharing
wrote you a PM quantan, with my backup stuff in it likewise.
cheers and best regards =)
lufan said:
It can be used, but it can't double-click the wake-up screen, the display after the screen is not turned off, and the vibration intensity is not adjustable. I backup the g820 boot through twrp, which contains magisk. I hope you can use it
https://drive.google.com/file/d/17I-m9QdmOzn7CXH3hOl-c04Jnvd7GC3P/view?usp=sharing
Click to expand...
Click to collapse
kimba99 said:
wrote you a PM quantan, with my backup stuff in it likewise.
cheers and best regards =)
Click to expand...
Click to collapse
Could you guys test the kernel v1.5 with TWRP to make sure it work. Thank you.
https://github.com/anht3889/LGE_G820_Kernel_Caf/releases/tag/v1.5-test
quantan said:
Could you guys test the kernel v1.5 with TWRP to make sure it work. Thank you.
https://github.com/anht3889/LGE_G820_Kernel_Caf/releases/tag/v1.5-test
Click to expand...
Click to collapse
I saw this link in TG channel. It has been tested. Twrp can't access it
@lufan Have you tried it. If not please try it to double check. The ramdisk from KR boot is working.