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?
Related
FEEL FREE TO DONATE US FOR ALL WE'RE DOING FOR YOU!
For general discussions, bug reports and FAQ, write HERE!
Credits:
MoltenMotherBoard team!
Downloads:
CWM Recovery | Code.Google
Full sources:
MoltenMotherBoard sources: MoltenMotherBoard | Github
CyanogenMod sources: CyanogenMod | Github
Kernel: lge-kernel-p880 | Github
Changelog:
20131126
Associated to Power Button the action SELECT_ITEM
From 6.0.4.4 to 6.0.4.5
Code updates from CyanogenMod, Google
20131120
First release
Issues:
Do you want to report an issue? Do it here!
In order to do it, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue.
Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different
kernel, mod, plugins and dependencies we didn't tell to use).
General Questions: MoltenMotherBoard Projects | General Questions and Info
Official Mantainer(s): Mackief, ItachiSama, p4c0
Installation guide:
[Method 1° ~ fastboot]
Code:
$ adb reboot oem-unlock
$ fastboot flash recovery /PATH-TO-THE-IMG-FOLDER-ON-YOUR-COMPUTER/cwm.img
$ fastboot reboot
[Method 2° ~ adb] (put the recovery.img in your sdcard)
Code:
$ adb shell
$ su
# cat /sdcard/cwm.img > /dev/block/mmcblk0p1
# sync
# exit
$ exit
With CyanDelta work?
negativman said:
With CyanDelta work?
Click to expand...
Click to collapse
Obviously it does. In fact, CyanDelta only make a flashable package, that you have to install manually from recovery. Then, yep.
BTW, now want also to make for you a Touch version of this CWM.
mackief said:
Obviously it does. In fact, CyanDelta only make a flashable package, that you have to install manually from recovery. Then, yep.
BTW, now want also to make for you a Touch version of this CWM.
Click to expand...
Click to collapse
cyandelta installs the zip automatically too, if the recovery supports openrecovery script. TWPR does, and so does the CWM based recovery in CM sources. the original CWM from rom manager does not work properly AFAIK
gandhar said:
cyandelta installs the zip automatically too, if the recovery supports openrecovery script. TWPR does, and so does the CWM based recovery in CM sources. the original CWM from rom manager does not work properly AFAIK
Click to expand...
Click to collapse
It could be that CWM from Rom-Manager is out-to-date.
The only way it could not work, is because thi updated CWM still need some merging and commits by the team. Just try and let us know!
mackief said:
It could be that CWM from Rom-Manager is out-to-date.
The only way it could not work, is because thi updated CWM still need some merging and commits by the team. Just try and let us know!
Click to expand...
Click to collapse
i had last tried a long time back, don't know and don't care about the current condition
i like TWRP much more.
just saw your post on g+ about a ubuntu touch port, any progress on that? i am very interested in that.
mackief said:
Obviously it does. In fact, CyanDelta only make a flashable package, that you have to install manually from recovery. Then, yep.
BTW, now want also to make for you a Touch version of this CWM.
Click to expand...
Click to collapse
Will another Nightly today or tomorrow, check whether a set CyanDelta!
Oh yes, the touch recovery - it would be very great. TWRP I personally do not like it. And the one that I have now for our smartphone is locked Rom Manager!
gandhar said:
i had last tried a long time back, don't know and don't care about the current condition
i like TWRP much more.
just saw your post on g+ about a ubuntu touch port, any progress on that? i am very interested in that.
Click to expand...
Click to collapse
About Ubuntu, it's not that simple.
It seems 4X kernel from CM team does not load into the system.
Unfortunately, I cannot debug which is the problem surely: but I'm sure I'll return on it in a week at least. I've some thoughts about how to make it loading and booting next to the kernel!
negativman said:
Will another Nightly today or tomorrow, check whether a set CyanDelta!
Oh yes, the touch recovery - it would be very great. TWRP I personally do not like it. And the one that I have now for our smartphone is locked Rom Manager!
Click to expand...
Click to collapse
As I understood CWM Touch is buildable only through clockworkmod-builder, and I'll do it. The only problem is that in that site, the sources are out-to-date, linked to 4.3 branches.
So, we have to wait, till CWM will update the sources linked in the site to build a 6.0.4.4 touch recovery.
mackief said:
As I understood CWM Touch is buildable only through clockworkmod-builder, and I'll do it. The only problem is that in that site, the sources are out-to-date, linked to 4.3 branches.
So, we have to wait, till CWM will update the sources linked in the site to build a 6.0.4.4 touch recovery.
Click to expand...
Click to collapse
Do not quite understand! Surely there's a new CWM 6.0.4.4. You can unlock it from Rom Manager? http://forum.xda-developers.com/showthread.php?t=2523732
Hey.
Just built a new build of CWM, now coded 6.0.4.5.
In this new release, CM team has apported an important fix - as also TWRP team has done - that avoid any issue while flashing some of KitKat based roms.
BTW, made a test build of CM11, gonna test it
mackief said:
Hey.
Just built a new build of CWM, now coded 6.0.4.5.
In this new release, CM team has apported an important fix - as also TWRP team has done - that avoid any issue while flashing some of KitKat based roms.
BTW, made a test build of CM11, gonna test it
Click to expand...
Click to collapse
Feel free to take us alpha testers
Sent from my Optimus 4X HD using XDA Premium 4 mobile app
[email protected] said:
Feel free to take us alpha testers
Sent from my Optimus 4X HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just pulled a log, as it does not boot.
Having some issues related to gralloc. Need to debug!
mackief said:
[...]
So, we have to wait, till CWM will update the sources linked in the site to build a 6.0.4.4 touch recovery.
Click to expand...
Click to collapse
Just take a look at my sig we already have 6.0.4.4 touch
laufersteppenwolf said:
Just take a look at my sig we already have 6.0.4.4 touch
Click to expand...
Click to collapse
Oh, marvolous!
But how can I build it? Is it buildable from source?
If you don't want me to build it, just update your port to 6.0.4.5. Ty, dude!
laufersteppenwolf said:
Just take a look at my sig we already have 6.0.4.4 touch
Click to expand...
Click to collapse
When he unlocked from Rom Manager?
mackief said:
Oh, marvolous!
But how can I build it? Is it buildable from source?
If you don't want me to build it, just update your port to 6.0.4.5. Ty, dude!
Click to expand...
Click to collapse
I will update it ASAP
negativman said:
When he unlocked from Rom Manager?
Click to expand...
Click to collapse
Not at all, as only official device maintainers can. And as I am not a maintainer, I can't
Just released new build of CWM.
Changelog:
Associated to Power Button the action SELECT_ITEM
From 6.0.4.4 to 6.0.4.5
Code updates from CyanogenMod, Google
Follow us on Google+, Facebook & Twitter!
Cheers.
We recently changed our Issue Tracker URL.
If you want to report a bug, please, follow the new instructions:
· Issue Tracker URL: Issues | Github
· Important notes: go to the linked URL, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue. Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different kernel, mod, plugins and dependencies we didn't tell to use).
Development for this project has been totally and officially stopped, as no more needed.
Greetings,
MoltenMotherBoard team.
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: https://dl.twrp.me/gts210vewifi
BUGS:
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.
XDA:DevDB Information
[RECOVERY][T813] TWRP 3.3.0-0 Touch Recovery [OFFICIAL], ROM for the Samsung Galaxy Tab S2
Contributors
LuK1337, luca020400, Olivier
Source Code: https://github.com/TeamWin
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Testing
Created 2017-01-24
Last Updated 2019-04-15
Wonderful to see this official! Just great!
Flashed!!
It works nicely and looks very good!
Thanks for this beautiful present
link dont work....pls reup...thy
hasbai said:
link dont work....pls reup...thy
Click to expand...
Click to collapse
Is it good now?
yes...the link works...can u make to a TWRP flash mod?
hasbai said:
yes...the link works...can u make to a TWRP flash mod?
Click to expand...
Click to collapse
Flash mod?
Can't you just flash it with heimdall?
sry...i mean twrp zip
hasbai said:
sry...i mean twrp zip
Click to expand...
Click to collapse
Use heimdall or flash the image in twrp ( there's a switch on the bottom I think ).
Hi,
Thanx a lot to bring some love to our Value Edtion :good::fingers-crossed:
Dumb question maybe but when I click on the link it takes me "TWRP for gts210vewifi". Thought this was for the SM-T813 9.7" tablet???
pastorbob62 said:
Dumb question maybe but when I click on the link it takes me "TWRP for gts210vewifi". Thought this was for the SM-T813 9.7" tablet???
Click to expand...
Click to collapse
Yes, that's the codename of it.
Just two things I would like to report:
Brightness level doesn't work. It's always max.
Second, not sure if this is a recovery issue, I made a backup of the stock rom. The rom was pin protected, but after restoring it the pin was not recognized. So I had to reset device in order to use the back up. It erased my sd card too, but I had another external backup up of the data, so it was safe
New twrp!!! Flashing it now!!!
varben said:
Just two things I would like to report:
Brightness level doesn't work. It's always max.
Second, not sure if this is a recovery issue, I made a backup of the stock rom. The rom was pin protected, but after restoring it the pin was not recognized. So I had to reset device in order to use the back up. It erased my sd card too, but I had another external backup up of the data, so it was safe
Click to expand...
Click to collapse
>Brightness level doesn't work. It's always max.
I forgot to fix that yesterday, I'll get that sorted out today ~ https://gerrit.twrp.me/#/c/2078
hmm, maybe I did something stupid here. Flashed the new twrp 3.0.3-2 through twrp and the tablet boots only in twrp now... the only selection I saw on which partition to flash was "boot"... so it boots only in recovery now
varben said:
hmm, maybe I did something stupid here. Flashed the new twrp 3.0.3-2 through twrp and the tablet boots only in twrp now... the only selection I saw on which partition to flash was "boot"... so it boots only in recovery now
Click to expand...
Click to collapse
Oh wow, I forgot to add /recovery to fstab. Thanks for reporting this issue...
LuK1337 said:
Oh wow, I forgot to add /recovery to fstab. Thanks for reporting this issue...
Click to expand...
Click to collapse
So, if I reflash the rom now without wipes, will it be ok to reboot to system?
varben said:
So, if I reflash the rom now without wipes, will it be ok to reboot to system?
Click to expand...
Click to collapse
Yes.
So, for the moment, who wants to flash this needs to use the official twrp app from play store.
https://play.google.com/store/apps/details?id=me.twrp.twrpapp&hl=en
Edit: @LuK1337 is so fast!!! A new fixed TWRP now! Forget the above...
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?
All discussions will now be held in the Pixel XL thread as the kernel is fully unified!
Reserved
You may notice the feature list is a little bare. I wanted to get a nice solid base formed first then add features in as requested. Please read the thread before requesting a feature; if it is already present, just press thanks.
In theory, this should work on P as I have merged the source in. I have only tested on Oreo though.
Feel free to join Telegram for beta builds and hanging out https://t.me/joinchat/C1UAJ0OCAoJtDRo-hhkjhw
That's awesome
I think today or tomorrow, depending on my commitments, I'll flash P dp2 with this kernel and report if it's working or not.
Many thanks!
Yes, I confirm it's working perfectly with P, also using magisk 16.4, everything's fine :good:
TENN3R said:
Yes, I confirm it's working perfectly with P, also using magisk 16.4, everything's fine :good:
Click to expand...
Click to collapse
Would you mind share your TWRP version and your flash procedure? I flashed the kernel with boot_twrp 3.2.1-2 and then magisk 16.4, got bootloop.
Thanks.
Queentus said:
Would you mind share your TWRP version and your flash procedure? I flashed the kernel with boot_twrp 3.2.1-2 and then magisk 16.4, got bootloop.
Thanks.
Click to expand...
Click to collapse
Of course. First, you have to start with a clean install. A lot of people are experiencing bootloops with a dirty flash.
So first flash factory image performing wipe. Don't set a lockscreen, I got data unable to decrypt on latest twrp 3.2.1-2 (in oreo worked).
Then fastboot boot twrp. You can choose to flash or just boot twrp, your choice.
If you want to flash twrp:
- flash twrp zip
- reboot recovery
- flash Flash kernel
- flash magisk 16.4 (16.0 stable doesn't work on P)
If you don't want twrp to stick, just:
- flash Flash kernel
- flash magisk 16.4
Reboot. Done.
Thanks @nathanchance ! Been reading your thread in the Marlin section and I'm glad you're adding kcal. Just updated to Android P yesterday and will flash yours when I can.
I have a question though, I flashed some kernels on Android P, clean flash the factory image in-between every time. Some of them every time you reboot you'll be greeted with a message that says to contact my device manufacturer because there's an internal issue. You could press ok and the mess goes away.this happens precisely before the Android beta message pops up when system loads. So some kernels has that error message and some doesn't, does flash kernel act this way?
Arju said:
Thanks @nathanchance ! Been reading your thread in the Marlin section and I'm glad you're adding kcal. Just updated to Android P yesterday and will flash yours when I can.
I have a question though, I flashed some kernels on Android P, clean flash the factory image in-between every time. Some of them every time you reboot you'll be greeted with a message that says to contact my device manufacturer because there's an internal issue. You could press ok and the mess goes away.this happens precisely before the Android beta message pops up when system loads. So some kernels has that error message and some doesn't, does flash kernel act this way?
Click to expand...
Click to collapse
Fortunately this doesn't, only beta popup :good:
TENN3R said:
Fortunately this doesn't, only beta popup :good:
Click to expand...
Click to collapse
Thank you for the answer ?
Arju said:
Thanks @nathanchance ! Been reading your thread in the Marlin section and I'm glad you're adding kcal. Just updated to Android P yesterday and will flash yours when I can.
I have a question though, I flashed some kernels on Android P, clean flash the factory image in-between every time. Some of them every time you reboot you'll be greeted with a message that says to contact my device manufacturer because there's an internal issue. You could press ok and the mess goes away.this happens precisely before the Android beta message pops up when system loads. So some kernels has that error message and some doesn't, does flash kernel act this way?
Click to expand...
Click to collapse
My guess is other kernels are universally disabling verity; I only disable verity on custom ROMs: https://github.com/nathanchance/AnyKernel2/blob/marlin-flash-8.1.0/anykernel.sh#L64-L80
Good, thanks
Update!
Remember any and all bug reports need to include logs and clear steps to reproduce (see the info in the OP). You should also know what version it started with. If you want to be a tester and get builds before they are released here or just hangout, feel free to stop by Telegram!
Short changelog
Add the following features:
Backlight dimmer
Color control
HBM
Sound control
USB fast charging
Wake gestures
Wakelock blocking
Add kernel hardening from CopperheadOS
Convert several systems to use power efficient workqueues
Add upstream CFQ improvements
Some small performance/power savings commits
WireGuard snapshot 0.0.20180513
Downloads
Primary: http://nchancellor.net/downloads/kernels/marlin/8.1.0/stable/
Mirror: https://github.com/nathanchance/fk-zips
Commits
Kernel: https://github.com/nathanchance/marlin/commits/oreo-m4
Here's my SOT using this kernel on Android P. Browsed the web/social media, YouTube, watched latest episode of fear the walking dead and some other stuff, so medium usage I would say. I'm really happy with this kernel. Sorry for the language being in Swedish but I'm sure you'll recognize what's SOT and what's not, which is 3h 46min with 50% battery left.
Arju said:
Here's my SOT using this kernel on Android P. Browsed the web/social media, YouTube, watched latest episode of fear the walking dead and some other stuff, so medium usage I would say. I'm really happy with this kernel. Sorry for the language being in Swedish but I'm sure you'll recognize what's SOT and what's not, which is 3h 46min with 50% battery left.
Click to expand...
Click to collapse
Getting similar results here, about 2 hours chrome, 1 hour YouTube and the rest juice ssh. Got about 6hr total which is great for me. Great work @nathanchance!
Hi, thnx for the great kernel. Runs great on P dp2.
Would it be possible to implement double tap 2 sleep along with the rest already existing wake gestures? TIA
Cheers
Sent from my Google Pixel using XDA Labs
Sgace said:
Hi, thnx for the great kernel. Runs great on P dp2.
Would it be possible to implement double tap 2 sleep along with the rest already existing wake gestures? TIA
Cheers
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
I have never heard of double tap to sleep being a kernel feature.
nathanchance said:
I have never heard of double tap to sleep being a kernel feature.
Click to expand...
Click to collapse
Damn, never mind. Misread myself on another thread, sorry about that:silly:
Thnx for you're reply.
Cheers
Sent from my Google Pixel using XDA Labs
Final stats. Really pleased with how smooth this kernel runs and that the device doesn't run hot. The SOT is awesome especially considering that this is the Sailfish.
Arju said:
Final stats. Really pleased with how smooth this kernel runs and that the device doesn't run hot. The SOT is awesome especially considering that this is the Sailfish.
Click to expand...
Click to collapse
Those are some impressive stats! Question - did you change any of the kernel settings?
Who are we?YAAP is a project founded by Adhitya Mohan (@poad42) and Ido Ben-Hur (@idoybh) with the goal of staying close to AOSP in design goals, offer a clean interface, do as much as original development as possible and avoid becoming a kitchen sink and cherry picked mess.
Bug reporting:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
DownloadsMi A1Flashing ProcedureInstall Latest Custom Recovery (This is recommended)
Coming from a different rom / OS you'll need to clean flash:
1. Wipe data (Factory reset)
(1.1.) If coming from stock OS you may need to format internal storage
2. Flash rom
(2.1.) After Flashing rom Flash Twrp (dont reboot without installing it)
(2.2)After Flashing Twrp go back to main menu and go to Reboot menu and select Reboot to Recovery Again
(2.2)Flash Gapps (This Recommended) For Root We Suggest Use Magisk Canay Builds (check below for download link)
3. Rejoice
For dirty flash just skip step 1, 1.1
and possibly 2.1 if your mods support addon.d (ex: Magisk)
It does not matter when you flash the firmware zip, and you only need to flash it once per firmware version
XDA:DevDB Information
Yet another AOSP project, ROM for the Mi A1
Contributors
murtaza1326
Source Code: [url]https://github.com/yaap[/URL]
Device Tree: [url]https://github.com/yaap/device_xiaomi_tissot[/URL]
Common Device Tree: [url]https://github.com/yaap/device_xiaomi_msm8953-common[/URL]
Vendor Tree: [url]https://github.com/yaap/vendor_xiaomi[/URL]
Kernel Source Code: [url]https://github.com/yaap/kernel_xiaomi_tissot[/URL]
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
ROM Firmware Required: v10.0.24.0 (Pie) (August)
Based On: AOSP
Version Information
Status: Alpha
Created 2020-09-20
Last Updated 2020-10-06
Working:
Camera/Video/Mic
Fingerprint
GPS
IMS (VoLTE)
RIL
Video playback
Wi-Fi
NightLight
CTS
Broken:
WFD
Bubbles
Switching back to wifi after using hotspot
(need to reboot to use wifi again)
Note: The ROM Does Not Include Gapps Feel Free to flash any gapps of your likings Nik Gapps are Recommended
For Root Magisk Canary Build(Compatible with R Only) is Working Fine This Works Perfectly (Do Not Update it)
Here
Credits Section
I am not alone to bring it up to you guys alone there are many many and many people who helped me to achive this
and i would like to mention them
First I would like to thanks
@abhinavagrd_1129 even tho me and him started bringing up trees differently he was always there to guide me
& i would like to tell you that his Aosp Beta 3 Rom Inspired me to try to bringup trees
@poad42 (Our Lead Dev of Project Yaap is the one who helped me alot to fix many bugs including the lags we were facing he pointed out fix to me
@SagarMakhar he is the one who fixed my noobish mistake i made everytime (also helped me to fix ril in the previous version)
@gotenksIN a guy who also stucked with his own bringup as well i was, we disscussed about bugs and different things together
@shivatejapeddi thanks to him VNDK29 issues were solved
@Lostark13 pointing and hinting me out for diffrent smaller things
Vince Device Devs (i picked there fixes thanks alot guys )
my mates in tissot maintainer TG group
also my testers ( i uslly do my own testing but at some point they helped me to too thanks alot guys)
if i miss anyone from the list do let me know :laugh:
New Changelogs :-
Code:
Device Side:-
Enforcing Now
CTS Passes Without Root(Tissot FP No More Pixel Props)
Fixed USB Teathering
Source Side:-
Merged Latest ASB (October)patch r5
Added Q/S Customisations
Added Clocks In Styles & wallpaper app
Added DT2W & DT2Sleep Gestures
Added Brightness Slider Customization
Added Custom Footer Text Support
Old Changelogs :-
Code:
Fixed Night Light
Fixed 3rd Party Apps Not Detecting Fingerprint
Fixed Wifi & Wifi Hotspot Toogle
Fixed CTS (With Root (No More Pixel Props Needed))
Xiaomi Parts Removed Vibration Controls Completly
Xiaomi Parts (New Adaptive Icons will match other android R icons)
Source side features will be added soon
Piru?
Congratulations ??
Harvey_Spectar said:
Piru
Congratulations ??
Click to expand...
Click to collapse
tnq sar
Good to See on 11 too..
Weww.. A11 going lit ??
Pro!!!! Nice work bruh!
Gawd
Sent from my Mi A1 using Tapatalk
What is the mean of "ROM Firmware Required: 10.0.24 (August)"?
Where can I found the ROM firmware?
There is some " must" to install it?
I am sorry if these are silly questions
sergiobh said:
What is the mean of "ROM Firmware Required: 10.0.24 (August)"?
Where can I found the ROM firmware?
There is some " must" to install it?
I am sorry if these are silly questions
Click to expand...
Click to collapse
sorry for inconvenience updated info
edit: i have added links for required firmware there shouldnt be a issue to find it somewhere else
Hi, @murtaza1326, thanks for your great work!
Nice to see that you're working on 11
I flashed YAAP and I found that fingerprint sensor is getting harder to detect fingertips (much less sensible, perhaps?).
Also, I see that if I just flash or update Official Magisk Canary, after device reboots, it goes to Fastboot mode and never boots System. I found that a solution was flashing that "MagiskR" zip, found at the other Android 11 ROM, but once installed, I have to avoid updates... otherwise, problem will appear.
?
KaaMyA said:
Hi, @murtaza1326, thanks for your great work!
Nice to see that you're working on 11
I flashed YAAP and I found that fingerprint sensor is getting harder to detect fingertips (much less sensible, perhaps?).
Also, I see that if I just flash or update Official Magisk Canary, after device reboots, it goes to Fastboot mode and never boots System. I found that a solution was flashing that "MagiskR" zip, found at the other Android 11 ROM, but once installed, I have to avoid updates... otherwise, problem will appear.
Click to expand...
Click to collapse
it could be different sensor like fpc ? i will see and i will fix it thanks for informing about magisk
KaaMyA said:
Hi, @murtaza1326, thanks for your great work!
Nice to see that you're working on 11
I flashed YAAP and I found that fingerprint sensor is getting harder to detect fingertips (much less sensible, perhaps?).
Also, I see that if I just flash or update Official Magisk Canary, after device reboots, it goes to Fastboot mode and never boots System. I found that a solution was flashing that "MagiskR" zip, found at the other Android 11 ROM, but once installed, I have to avoid updates... otherwise, problem will appear.
Click to expand...
Click to collapse
i need more details on your sensor type if you can provide me
check this screenshot it has Fingerprint model stated that can you tell us what it shows there for you because as far as i and my tester tested this has blazing fast Fingerprint sensor
murtaza1326 said:
i need more details on your sensor type if you can provide me
check this screenshot it has Fingerprint model stated that can you tell us what it shows there for you because as far as i and my tester tested this has blazing fast Fingerprint sensor
Click to expand...
Click to collapse
Friend, your screenshot seems to have been deleted
Well, while that, all I could tell is I'm coming from DerpFest, I have changed back to that ROM because I need to use my phone everyday. In that ROM fingerprint if easier to detect fingerprints.
murtaza1326 said:
i need more details on your sensor type if you can provide me
check this screenshot it has Fingerprint model stated that can you tell us what it shows there for you because as far as i and my tester tested this has blazing fast Fingerprint sensor
Click to expand...
Click to collapse
Hello prosur!
KaaMyA said:
Friend, your screenshot seems to have been deleted
Well, while that, all I could tell is I'm coming from DerpFest, I have changed back to that ROM because I need to use my phone everyday. In that ROM fingerprint if easier to detect fingerprints.
Click to expand...
Click to collapse
You can still check which fingerprint sensor your device have
Takeshiro04 said:
You can still check which fingerprint sensor your device have
Click to expand...
Click to collapse
Don't know how. Screenshot would have helped me, but was deleted. Please tell me how to check that.
KaaMyA said:
Don't know how. Screenshot would have helped me, but was deleted. Please tell me how to check that.
Click to expand...
Click to collapse
Install Device info apk and check the fingerprint sensor
murtaza1326 said:
i need more details on your sensor type if you can provide me
Click to expand...
Click to collapse
Mr Magneto said:
Install Device info apk and check the fingerprint sensor
Click to expand...
Click to collapse
I have installed "Device Info HW" app and it tells that my sensor variant is "goodix".