[OFFICIAL] TWRP 3.6.0_9-0 for osprey/merlin - Moto G 2015 Original Android Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/​
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. It's a full 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.
TWRP built for the 2015 Moto G / G turbo. It should work fine, but using it is a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery.
Flash through twrp or fastboot
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
Click to expand...
Click to collapse
To permanently flash it:
Code:
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Download (osprey)
Download (merlin)
XDA:DevDB Information
[OFFICIAL] TWRP 3.4.0.0 for osprey/merlin , ROM for the Moto G 2015
Contributors
althafvly, squid2
Source Code: https://github.com/TeamWin/android_kernel_motorola_msm8916
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.1.x
Version Information
Status: Stable
Created 2018-08-16
Last Updated 2020-10-24

Reserved

Is this treble something like custom recovery
Or anything else

@althafvly awsome work.
I have two question.
1. Can I flash normal ROMs with this recovery..
2. If I format /cashe as ext4 will be any problem when flashing normal ROM?
Thanks

Does F2FS work on this phone?

Deleted

I will try it out thanks for the port . It flashed good but when I check boxes that said get failed could it maby bad download

It is Woking fine and I installed los 15.1 by Ahmed hady. Thank you dev love you a lot

if old twrp is there
hey guys u dont have to go to the old method of installing the twrp again to the device . you can install this new twrp just from your old twrp . you can see an option call 'select img' in your twrp file location select it and thats it

Can we flash it through twrp using boot image?

I'm unable to decrypt data with this recovery. Data was encrypted with LineageOS 14.1.

shutdown -h now said:
I'm unable to decrypt data with this recovery. Data was encrypted with LineageOS 14.1.
Click to expand...
Click to collapse
Format data try again or return to stock decrypt when flashing twrp

NEW UPDATE
TWRP 3.3.1.0 for osprey
-Updated sources
-Squid twrp features
Download at OP

althafvly said:
NEW UPDATE
TWRP 3.3.1.0 for osprey
-Updated sources
-Squid twrp features
Download at OP
Click to expand...
Click to collapse
What's the difference from the official twrp 3.3.1.0?

Didn't find it out for merlin @althafvly
---------- Post added at 12:37 PM ---------- Previous post was at 12:37 PM ----------
Didn't find it out for merlin @althafvly

stukdev said:
What's the difference from the official twrp 3.3.1.0?
Click to expand...
Click to collapse
This version contains support for a separate vendor partition. If you do not know what that means or why you would need support for a separate vendor partition then use the official twrp version.
Sent from my Nvidia Shield Tablet using XDA Labs

jemail said:
...support for a separate vendor partition. If you do not know what that means or why you would need support ....then use the official twrp version....
Click to expand...
Click to collapse
i guess one can use this twrp or the official one to 'flash normal or any other roms'. could you / @althafvly / anyone else please mention 'roms with support for vendor partition' available for osprey atm.

There's no file for merlin
althafvly said:
TWRP built for the 2015 Moto G. It should work fine, but using it is a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery.
You can use this RECOVERY to flash normal or any other roms too..
Flash through twrp or fastboot
To temporarily boot this recovery:
Code:
To permanently flash it:
Code:
Download
After flashing:
-Go to wipe
-advance wipe
-select cache
-select file system -> ext4
-swipe
-Now u r good to go
XDA:DevDB Information
[UNOFFICIAL] TWRP 3.3.1.0 for osprey/merlin [SEPARATE VENDOR], ROM for the Moto G 2015
Contributors
althafvly, Ahmed Hady,squid2
Source Code: https://github.com/MOTO-M8916/twrp_recovery_manifest
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.1.x
Version Information
Status: Stable
Created 2018-08-16
Last Updated 2020-04-06
Click to expand...
Click to collapse
Bro I didn't find file for merlin

RehanS1 said:
Bro I didn't find file for merlin
Click to expand...
Click to collapse
New builds can be found here
https://sourceforge.net/projects/althafvly/files/twrp/

@althafvly @IronTechmonkey
I really like the green theme from squid2 for TWRP. Is there any way to use it on the newly released official TWRP 3.4 which is blue?
Edit: I noticed an unofficial 3.4 build was uploaded. But I would also like to use the theme on other devices if possible with a theme file.

Related

[ROM] [OFFICIAL] [7.1.2] [madOS] - Coolpad Note3 Lite (mt6735)

This is a Official Build of madOS ( based on AOSP N ) for Coolpad Note3 Lite with MTK 6735 SoC
madOS is based on pure A.O.S.P. with many additional customizations and MediaTek support.​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Installation Instructions:
Download ROM from here: https://www.facebook.com/MediatekAndroidDevelopers/
Boot to recovery
Wipe data if you are not coming from previous version of madOS already
Install rom and (optional) Gapps (Google Apps)
Reboot
Working:
Smartwake
RIL (Calls /SMS, Data connection)
Wifi
Bluetooth
Audio / Mediaserver
Sensors
Lights
Both storages & MTP
HW de/encoding
Camera
GPS
Audio recorder
Camcorder
Fm Radio
Not working:
VoLte
tell us
Contributors
superdragonpt, DerTeufel1980, fire855
Source Code: https://github.com/MediatekAndroidDevelopers
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.18.x
Based On: AOSP
Version Information
Status: Stable
Created 2017-07-17
Last Updated 2017-07-17
XDA:DevDB Information
madOS_coolpad_note3_lite, ROM for all devices (see above for details)
Contributors
DerTeufel1980, fire855, superdragonpt
Source Code: https://github.com/MediatekAndroidDevelopers
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: custom recovery installed
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 1.1
Stable Release Date: 2017-07-17
Created 2017-07-18
Last Updated 2017-07-18
Reserved
Volte:
we're working on it, and progress has been made already. As soon as it is working, we'll let you know.
We can't tell any date for it.
Click to expand...
Click to collapse
madOS TWRP:
http://www.mediafire.com/file/te583tm2fww0aca/cpn3_lite_recovery.img
Click to expand...
Click to collapse
maximum performance:
I suggest flashing twrp, then reboot to recovery and format data and cache to f2fs filesystem.
Attention! This is going to delete your internal sdcard as well. Please backup everything before.
After this, install rom and gapps as usual.
Of course, you can format back to ext4 or to f2fs at any time, but you'll again loose all files, stored on the phone.
Click to expand...
Click to collapse
Reserved
One more, just in case
*reserved*
Good Work.
Excellent work
i cant install any zip file why? its showing installation in complete but there is no effect
aslam31319 said:
i cant install any zip file why? its showing installation in complete but there is no effect
Click to expand...
Click to collapse
1. make sure you have mad twrp recovery.
2. if yes please format data partion(you have to clean install this )
3. still problems persist make sure you downloaded file correctly
4. Still problem appear pm me
Refer this link for proper installation. Even though this is for CPN3, it will work for lite as well.
https://forum.xda-developers.com/sho...php?p=72982948
problem with twrp provided by u
nervehammer said:
1. make sure you have mad twrp recovery.
2. if yes please format data partion(you have to clean install this )
3. still problems persist make sure you downloaded file correctly
4. Still problem appear pm me
Click to expand...
Click to collapse
i am not talking about your rom zip file its getting installed and working perfect but the bug is on twrp when i install any modes like xperia home or biohazard sound mode its showing a succesfull result but no effect on install ,after that i repeated install after mounting system then its worked on it but biohazrd faild even on that
aslam31319 said:
i am not talking about your rom zip file its getting installed and working perfect but the bug is on twrp when i install any modes like xperia home or biohazard sound mode its showing a succesfull result but no effect on install ,after that i repeated install after mounting system then its worked on it but biohazrd faild even on that
Click to expand...
Click to collapse
because this twrp doesn't have busybox and these mods uses busybox . Change busybox to toybox in updater scripts of these mods or flash another twrp for flashing mods
ok Google detection issue
OK Google detection is not working it says feature currently unavailable for device
Fingerprint?
Does Fingerprint sensor work well? Any bugs other than Volte? Thank for the rom!
vaidyavishnu said:
OK Google detection is not working it says feature currently unavailable for device
Click to expand...
Click to collapse
I can only test on normal note3. It's working there. Maybe gapps issue...
Gesendet von meinem H5000 mit Tapatalk
Is it necessary to root this rom after flashing??? And you said format data and cache to f2fs filesystem...how to do it bro..???
hagarwal27 said:
Is it necessary to root this rom after flashing??? And you said format data and cache to f2fs filesystem...how to do it bro..???
Click to expand...
Click to collapse
boot to twrp and go to wipe section
advance wipe->select dalvik art cache and data partition and click on " Repair and Change file System" tab -> Click on " change file system " and from that choose f2fs
Ez pz lemon squeezy !!
The Button Options in mados extras are not working
Eg. I can set Recents Long Press to Open/close menu but it actually never works..
good work team
vegeto1806 said:
The Button Options in mados extras are not working
Eg. I can set Recents Long Press to Open/close menu but it actually never works..
Click to expand...
Click to collapse
You need to change it, and leave the menu. Changes do not get applied immediately :/
Gesendet von meinem H5000 mit Tapatalk
I can't install zip it shows 11 errors

[RECOVERY][UNOFFICIAL][TWRP - 3.3.1-1][Xiaomi Redmi Note 7 PRO]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DISCLAIMER:​
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
INFORMATION:​
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system which are functions often unsupported by stock recovery images. It is, therefore, often installed when flashing, installing or rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Read more about TWRP here: https://twrp.me/about/​
FLASHING GUIDE​
Code:
[CENTER]Scene 1
: (When coming from MIUI this is necessary)
(You can do this when upgrading from old TWRP too)
. Reboot to fastboot
. fastboot flash dtbo dtbo.img
. fastboot flash recovery twrp.img
. fastboot erase userdata
Scene 2
: (When coming from old TWRP)
. Flash new Rom
. TWRP gets feked , but just flash new one (as dtbo is already updated by the new rom)
. fastboot flash recovery twrp.img[/CENTER]
DOWNLOAD LATEST BUILD : TWRP BUILD | DTBO IMG
CHANGELOG​
Code:
[CENTER]*Upstreamed to 3.3.1-1
* Support new Dtbo img[/CENTER]
BUGS
* MIUI Encryption
ANY HELP JOIN VIOLET SUPPORT GROUP ON TELEGRAM : HERE
KERNEL Link: android_kernel_xiaomi_sm6150
XDA:DevDB Information
Twrp Recovery for redmi note 7 pro, Tool/Utility for the Xiaomi Redmi Note 7 Pro
Contributors
Rasinsahaji, Dyneteve, merothh
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Stable Release Date: 2019-05-22
Created 2019-05-23
Last Updated 2019-05-23
Any mirror for users who don't use Telegram? Thanks in advance.
L.R. team has released a version of TWRP which support decryption for our device. Hope it can be supported by this recovery soon.
Link to their work (Chinese):
http://www.miui.com/forum.php?mod=viewthread&tid=24437570&extra=page=1&page=1&mobile=2
Unfortunately they didn't provide any source code.
what makes this build different than other unofficial twrp build for Violet?
Dwughjsd said:
L.R. team has released a version of TWRP which support decryption for our device. Hope it can be supported by this recovery soon.
Link to their work (Chinese):
http://www.miui.com/forum.php?mod=viewthread&tid=24437570&extra=page=1&page=1&mobile=2
Unfortunately they didn't provide any source code.
Click to expand...
Click to collapse
It's not their work. I've submitted wrapped-key FBE support for TWRP but hasn't been merged yet
https://gerrit.omnirom.org/#/c/android_bootable_recovery/+/34091/
https://gerrit.omnirom.org/#/c/android_bootable_recovery/+/34093/
They've just merged those commits into theirs and called them "their work". You could even see the 'author' of L.R. commenting under those patches. They've just pulled open-source work without credit.
Any of unofficial builders of TWRP can pull those commits ahead of TWRP official to get the encryption working for now. And also this one I've submitted that fixes decryption for any Pie ROM after the May 2019 security patches
https://gerrit.omnirom.org/#/c/android_bootable_recovery/+/34092/
PeterCxy said:
It's not their work. I've submitted wrapped-key FBE support for TWRP but hasn't been merged yet
https://gerrit.omnirom.org/#/c/android_bootable_recovery/+/34091/
https://gerrit.omnirom.org/#/c/android_bootable_recovery/+/34093/
They've just merged those commits into theirs and called them "their work". You could even see the 'author' of L.R. commenting under those patches. They've just pulled open-source work without credit.
Any of unofficial builders of TWRP can pull those commits ahead of TWRP official to get the encryption working for now. And also this one I've submitted that fixes decryption for any Pie ROM after the May 2019 security patches
https://gerrit.omnirom.org/#/c/android_bootable_recovery/+/34092/
Click to expand...
Click to collapse
Thank you for your explaination. But there is still a question: does it mean that I don't have to format /data to flash PixelExperience, LOS, etc. on TWRP with these commits when I'm on stock MIUI, or I have to wait until the ROM changes to support decrypting stock-encrypted /data partition?
Dwughjsd said:
Thank you for your explaination. But there is still a question: does it mean that I don't have to format /data to flash PixelExperience, LOS, etc. on TWRP with these commits when I'm on stock MIUI, or I have to wait until the ROM changes to support decrypting stock-encrypted /data partition?
Click to expand...
Click to collapse
CAF-based ROMs should use the same encryption scheme as MIUI, so it should work fine, though I've not tested transitioning personally. LOS is not on CAF though, but I have a build that ported those changes over to LOS. Check my threads you can find one.
Hi , direct link for all of above : https://drive.google.com/open?id=11oCgL7UB58wF-6oSyss3rjeNJHt1mN_A
Please update the info : Add that it deletes all your data !
Also write there not " fastboot erase userdata " but " fastboot format userdata " , cause erasing delete the partition !
Reporting bug- can't install Gapps Aroma. Getting error 255.

[RECOVERY][UNOFFICIAL]TWRP 3.3.1-0 Galaxy J8 J810M/F/FN/G/DS

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unofficial Release TWRP Recovery for Samsung Galaxy J8 MSM8953​
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What's new in 3.3.1-0:​
Code:
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
Bugs:​
If you find please report
Download:​
ANDROID FILE HOST
Source:​
Device Tree
TWRP
Kernel
Nice
after I flashed magisk and format data j810g the phone stock Samsung logo what I did wrong ?
android pie*
New Version Released!
Changelog:
- Update fstab to correct links;
- Fix system not boot with twrp flashed
The twrp flashed successfully but flashing the stable build of magisk(19.3) throws an error "Failed to mount /data(invalid argument)". I'm on android pie and my device is smj810f. Need help. Thanks in advance!
ilovecookieee said:
The twrp flashed successfully but flashing the stable build of magisk(19.3) throws an error "Failed to mount /data(invalid argument)". I'm on android pie and my device is smj810f. Need help. Thanks in advance!
Click to expand...
Click to collapse
Try to format data before flashing magisk
BadGuy said:
Try to format data before flashing magisk
Click to expand...
Click to collapse
Thank you! It works! But I'm stuck on splash screen. I think it's not TWRP related tho.
android version required
BadGuy said:
New Version Released!
Changelog:
- Update fstab to correct links;
- Fix system not boot with twrp flashed
Click to expand...
Click to collapse
i wanted to ask since on september the 5th an update for android 9 pie and i installed it tried flashing the custom recovery through odin it passed but nothing changed meaning the twrp didn't show up
so i wanted to ask which version of anroid should i install (8 or 9) and from which region (ie : india / nepal etc...) to ensure maximum compatibility with the custom recovery and also i'm new to rooting and stuff so i'm sorry if i'm being ignorant and in actuality installing twrp has nothing to do with the android version
hi, i have J810Y/DS, can i use this build ?
Existe alguma custom rom?
Bro I have galaxy j8 10g.
It runs on android pie
Should I try this recovery??
Sent from my SM-J810G using Tapatalk
---------- Post added at 06:42 AM ---------- Previous post was at 06:30 AM ----------
Bro I have galaxy j8 10g.
It runs on android pie
Should I try this recovery??
Sent from my SM-J810G using Tapatalk
badguy said:
new version released!
changelog:
- update fstab to correct links;
- fix system not boot with twrp flashed
Click to expand...
Click to collapse
fala irmão. O odin funcionou certinho e ao entrar no modo recovery, o twrp não aparece. O que pode ser?
How should I flash it. Please help!!!!....
BerserkBiel said:
Existe alguma custom rom?
Click to expand...
Click to collapse
I'm looking for it as well, buddy.
fala, brasileiro...
My TWRP installs normally on odin, but it deletes rom storage, causing bootloop, and I can't format anything from the device by twrp
Godinho77 said:
My TWRP installs normally on odin, but it deletes rom storage, causing bootloop, and I can't format anything from the device by twrp
Click to expand...
Click to collapse
It doesn't delete anything. You can't access storage because it's encrypted.
Nothing is preventing you from Formatting if you use the correct button. I. E. FORMAT DATA button.
Hello, i flash this recovery, after i format data and flash magisk 19.1, but after i have interminable boot.
no-verity-encrypt flashing with error -1 (all versions)
What i did wrong?
bublik2317 said:
Hello, i flash this recovery, after i format data and flash magisk 19.1, but after i have interminable boot.
no-verity-encrypt flashing with error -1 (all versions)
What i did wrong?
Click to expand...
Click to collapse
happened to me as well. i think when you flash the recovery you have to uncheck auto restart in Odin. After the recovery flash is done, restart the phone with VOLUME DOWN + POWER and imediately VOLUME UP + POWER to get in recovery and delete data + install MagisK. if the phone does not get in the recovery the first time the security fuse is blown and you have to flash a stock rom from sammobile.com and start again.
Hey guys, i wanted to try the gcam mod in my galaxy j8(j810-G). Has anyone tried it yet? If not should i try it? I don't want to root it cuz I'm scared if it doesn't work, as i haven't seen any roms or mods for j8 yet:crying:... There's literally nothing to do and I won't get ota too..
Sorry I'm a noobie and scared of things getting wrong
Thanks in advance!:good:
Could you help me try to make a twrp for a20s?
if you can join the group from telegram @ galaxyj6br to talk to the agent we really need your help !!

[RECOVERY][UNOFFICIAL[pyxis and vela][v2.9.0] Pitch Black Recovery [05/02/20]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.3.1
PitchBlack version: 2.9.0
For device: pyxis and vela
Maintainer/Authors build: @UnparallelSKY
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/Mashopy/android_device_xiaomi_pyxis-pbrp
PitchBlack Team: @rezaadi0105, @firewolfxda, @manjot.gni, @androiabledroid, Arbaz Khan
Features
Supports Treble and non-Treble ROMs
Up-to-date Oreo kernel, built from sources (Pie is on the way)
Full dark theme with changeable accents
Reorganized menus
MIUI OTA support
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions
From PC
Download vbmeta.img and pbrp-2.9.0-pyxis-vela.img
Reboot to fastboot, plug your phone to your PC and open powershell or cmd
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash recovery pbrp-2.9.0-pyxis-vela.img
Reboot to recovery
Enjoy
From previous version or other recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
The device will automatically reboot into PitchBlack Recovery after installation
Enjoy
Changelog
Code:
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Code:
05/02/20 Build
- Fix up mounting of data on some devices
- Fix ueventd.qcom.rc name (previously was ueventd.qcom.rc.rc)
15/01/20 Build
- Initial build
Downloads
vbmeta : https://github.com/Mashopy/android_.../releases/download/v2.9.0-05/02/20/vbmeta.img
recovery : https://github.com/Mashopy/android_...oad/v2.9.0-05/02/20/pbrp-2.9.0-pyxis-vela.img
Flashable zip
https://github.com/Mashopy/android_...lack-pyxis-2.9.0-20200205-1721-UNOFFICIAL.zip
Well done, looks good
Here some screenshots
i love it
Many thanks Bro.
Hey all,
Thanks for the amazing job done here!
I'm having issue to wipe devices data, when I try it gives me and error:
Failed to mount data, no such device.
Any idea?
Thanks
topfreitas said:
Hey all,
Thanks for the amazing job done here!
I'm having issue to wipe devices data, when I try it gives me and error:
Failed to mount data, no such device.
Any idea?
Thanks
Click to expand...
Click to collapse
I had same error and return to previous TWRP
Sent from my MI 9 Lite using Tapatalk
Which one are you using now? I'm having issues with like "Could not mount /data and unable to find crypto footer". I tried to wipe all data but i'm not able to format it, same issue.
any ideas?
Can this twrp bypass arb check on rom downgrade?
editheraven said:
Can this twrp bypass arb check on rom downgrade?
Click to expand...
Click to collapse
pyxis and vela doesn't have arb ;___;
topfreitas said:
Which one are you using now? I'm having issues with like "Could not mount /data and unable to find crypto footer". I tried to wipe all data but i'm not able to format it, same issue.
any ideas?
Click to expand...
Click to collapse
Try to switch to ext4
I don't know. I think it has.
I had miui global 11.3.5.0 PFCEUXM then I installed mi-globe.com_v11_pyxis_20.1.16 from miui rom builder site. I had a twrp backup of 11.3.5 and flashed it back. I had to pay an authorised account user to flash stable eu rom in edl mode. (no fastboot no recovery).
fastboot getvar anti returns value "1" so I thought it's ok.
I found another thread with a similar problem
https://forum.xda-developers.com/mi-cc9/help/bricked-cc9-anti-rollback-help-edl-t4019819
editheraven said:
I don't know. I think it has.
I had miui global 11.3.5.0 PFCEUXM then I installed mi-globe.com_v11_pyxis_20.1.16 from miui rom builder site. I had a twrp backup of 11.3.5 and flashed it back. I had to pay an authorised account user to flash stable eu rom in edl mode. (no fastboot no recovery).
fastboot getvar anti returns value "1" so I thought it's ok.
I found another thread with a similar problem
https://forum.xda-developers.com/mi-cc9/help/bricked-cc9-anti-rollback-help-edl-t4019819
Click to expand...
Click to collapse
Because you bricked ;__; and this device doesn't have arb enabled
UnparallelSKY said:
Because you bricked ;__; and this device doesn't have arb enabled
Click to expand...
Click to collapse
I bricked what?
editheraven said:
I bricked what?
Click to expand...
Click to collapse
Your phone, because you bought a authorized account for flash in edl
UnparallelSKY said:
Your phone, because you bought a authorized account for flash in edl
Click to expand...
Click to collapse
I bricked my phone after restoring an older twrp backup. But this is already offtopic I think.
It didn't work with the pixel experience GSI!
maosilva said:
It didn't work with the pixel experience GSI!
Click to expand...
Click to collapse
Then you did something wrong
Don't have arb but will brick if you flash 9 over 10 with easy or if you restore backup, flash some roms.. ??
Is there any way to backup-restore a fastboot rom with pattern encryption?
is it possible to backup with second space\dual app?

Development [ROM] [13.0] DerpFest Tango for Pixel 6a [OFFICIAL] [bluejay]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a small project based on AOSP. We try to be a platform for beginners and support the Custom ROM community with our own unique contributions as well. This ROM exists thanks to inspiration of AOSiP, Thank you! #StayDerped
Code:
/* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What is working:
Everything
If you want to report bugs, please send proper logs!
Installation:
Flash with "adb sideload ROM.zip" using recovery.
ROM Download
Testbuild Section
Screenshots
Kernel Source
If you like my work feel free to buy me some coffee HERE
Join our Derpfest telegram group here​
ROM OS Version: Android 13.0
ROM Kernel: Linux 5.10.149
Based On: AOSP
Version Information
Status: OFFICIAL
Current Build Version: 13.0
Build Release Date: 2023-05-10
I get this when i'm trying to flash. Can anyone help me?
jordan2333 said:
I get this when i'm trying to flash. Can anyone help me?
Click to expand...
Click to collapse
Did you flash boot and vendor_boot before sideload ?
I did a clean install with this way below:
(1) Extract boot.img, vendor_boot.img from payload.bin in ROM.zip
(2) fastboot flash boot boot.img
(3) fastboot flash vendor_boot vendor_boot.img
(4) reboot and goto recovery
(5) Factory reset -> Format data
(6) Install update -> ADB Sideload
(7) adb sideload ROM.zip
Derpfest Release Candidate
-Fixed Wifidisplay
-Launcher Optimizations
DOWNLOAD
E-sim is supported on this rom
Thanks
Thank you Derpfest for our Pixel 6a.
I installed 20230510 build (clean install, no restoration, completely newly seting up)
and then update to 20230522 build (dirty install),
and update to 20230524 build (dirty install)
3 days have passed since the 20230524 build, but there is no problem at all.
From the first time installation, there really is no problem, and it operates extremely smooth. Both of the 20230522 and 20230524 builds are also perfectly fine. Some bug fixes were done, but I didn't notice the bug itself.
klazyStrida said:
Thank you Derpfest for our Pixel 6a.
I installed 20230510 build (clean install, no restoration, completely newly seting up)
and then update to 20230522 build (dirty install),
and update to 20230524 build (dirty install)
3 days have passed since the 20230524 build, but there is no problem at all.
From the first time installation, there really is no problem, and it operates extremely smooth. Both of the 20230522 and 20230524 builds are also perfectly fine. Some bug fixes were done, but I didn't notice the bug itself.
Click to expand...
Click to collapse
How's your battery life compared to stock, vs. other roms? Just overall
mmead1143 said:
How's your battery life compared to stock, vs. other roms? Just overall
Click to expand...
Click to collapse
There's no problem in battery consamption.
It's not that Derpfest is good, but it's the same with Google's stock OS and other custom ROMs.
klazyStrida said:
There's no problem in battery consamption.
It's not that Derpfest is good, but it's the same with Google's stock OS and other custom ROMs.
Click to expand...
Click to collapse
Thanks a ton!
Hello! Dear developer, is there an "oriole" planned?
klazyStrida said:
Did you flash boot and vendor_boot before sideload ?
I did a clean install with this way below:
(1) Extract boot.img, vendor_boot.img from payload.bin in ROM.zip
(2) fastboot flash boot boot.img
(3) fastboot flash vendor_boot vendor_boot.img
(4) reboot and goto recovery
(5) Factory reset -> Format data
(6) Install update -> ADB Sideload
(7) adb sideload ROM.zip
Click to expand...
Click to collapse
1st newcomers should always make sure their on the latest official google firmware before flashing any custom rom.
Then the Dev could build with these commands and provide maximum compatibility for end user.
source build/envsetup.sh
Click to expand...
Click to collapse
Then
Brunch bluejay
Click to expand...
Click to collapse
This provides the Full OTA zip and is optimal in flashing via recovery, also provides a way for the Dev to develop his ota system. But if the dev doesn't clean his directory after it finishing brunch , would to be run these commands and build a full update image zip that's flash able via bootloader
croot
Click to expand...
Click to collapse
And then
m updatepackage
Click to expand...
Click to collapse
This builds the same identical builds , leaving end users better choices
maximusfoa said:
Hello! Dear developer, is there an "oriole" planned?
Click to expand...
Click to collapse
Not from me. I only build for devices i own.
pete80pro said:
Not from me. I only build for devices i own.
Click to expand...
Click to collapse
Ok, thnk

Categories

Resources