Database Info

[Recovery] Official TWRP for the OnePlus 3 & 3T

Team Win Recovery Project 3.0.4-1 (unreleased)
Notice #1: Please don't wipe your data partition if TWRP cannot decrypt it. Instead, make an effort to gather logs to help solve the issue!
Notice #2: Themes from 3.0.0 to 3.0.3 are incompatible with 3.0.4. Sorry! (small theme engine changes regarding backlight control)
This is a unified build for both the OnePlus 3 and the OnePlus 3T!
WARNING: The OnePlus 3 & 3T stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below, in order, to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/oneplusthree.html
Use 3.0.4-1 for now, rather than the builds on twrp.me until an official release happens. You will have problems with 3.0.3 on Nougat!
For now, please download the build from:
https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-1-oneplus3.img
Officially 3.0.4 has not been released yet, but it has critical fixes for this device on Nougat, so please be patient.
There is a download link there, as well as instructions on how to flash it.
You can find up to date fastboot & adb binaries here!
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
Extract/install adb & fastboot to your computer.
{
"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"
}
Download TWRP for OnePlus 3 & 3T (oneplus3).
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Reboot your device into fastboot mode. To do this, select reboot from the power menu and hold the [Volume Up] + [Power] buttons while your device reboots or boots from power off.
Once you're in fastboot mode, you need to unlock your bootloader. To do this, run the command:
fastboot oem unlock
WARNING: Unlocking your bootloader will erase all userdata on the device! Your device will be completely reset to factory defaults!
Once your bootloader is unlocked, you're ready to flash TWRP. To do this, run the command (replacing twrp.img with the actual image name):
fastboot flash recovery twrp.img
Once the image is flashed, you should use your volume keys to navigate to RECOVERY and the press the power key to select it.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If your device asks for a password to mount internal storage, and your password doesn't work or you haven't set one, see below under known issues for a fix!
If you want to be rooted with SuperSU:
Download the latest SuperSU Stable by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
---or (not both) ---
If you want to be rooted with something else or just want a bootable system:
Download the latest dm-verity and forced encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
This will also allow you to use [Format Data] to completely disable your encryption if desired.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up. (SuperSU will reboot you a few times)
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
UPDATING TWRP
To update TWRP, simply download the new twrp.img on your phone, then boot into your current TWRP and flash it.
To flash a twrp.img, navigate to [Install] -> [Flash Image] -> select your twrp.img -> [x] Recovery -> Flash!
After that, just use [Reboot] -> [Recovery] to reboot into the updated TWRP.
CHANGES
v3.0.4-1 (build.nethunter.com) - Fix crash when trying to reboot that resulted in TWRP restarting, CAF kernel updates
v3.0.4-0 (build.nethunter.com) - Capability restoration for Nougat, F2FS backport support, EXT4 decryption support
v3.0.3-0 (twrp.me) - Same as 3.0.3-1-rc2. In sync with the OnePlus 3T device tree (3.0.3-1).
v3.0.3-1-rc2 (build.nethunter.com) - Redo the device tree for OOS 4.0, including dynamic encryption support (pull libs from ROM)
FEATURES
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
Allows OnePlus full OTA flashing
KNOWN ISSUES
F2FS takes a long time to boot, see below.
If your device is taking more than 10 minutes to boot, you probably have a misc flag enabled that disables passing cmdline, see below.
Reboot buttons don't work in TWRP (restarts TWRP) - disable Ask to install TWRP App on settings page, fix on the way. - fixed in 3.0.4-1
WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Personally, I'd have tried this after 15 minutes.
WHY DOES F2FS MAKE TWRP SO SLOW?
When TWRP boots up or wipes partitions and a few other scenarios, it checks each partition to see how much disk space is used. Ext4 handles disk usage calls quite efficiently and will finish this very fast. F2FS on the other hand is very slow when it comes to checking disk usage. We're unsure why this is. Every file on the F2FS formatted partition adds a little more time, and a device that is 30 GB full could take up to 10 minutes to boot TWRP!
I suggest switching your data partition to ext4 - all the f2fs hype is merely from benchmarks that don't actually represent real world use (ie. you're not writing thousands of files per second)
For someone who doesn't do lots of write access to their data partition, ext4 can actually be advantageous (it has faster access times and reads!)
WHY WON'T MY DATA DECRYPT / WHY IS MY PASSWORD INVALID IN TWRP?
In order for encryption to work in TWRP, it must pull the encryption libraries from your current ROM. It does this during TWRP boot logo. If you have no ROM installed, then it will fall back to the default OxygenOS 4.0.2 encryption libraries included in the TWRP image.
The crypto daemon in recovery will not be able to decrypt unless the version of the encryption key matches the version of the libraries. This is an unusual restriction that was added by OnePlus.
You can usually fix this by simply booting into your ROM and changing your boot up password. You can change it back or remove it if you want immediately after. This will generate a new crypto key which should be compatible when you next enter TWRP.
HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?
To get logs while in TWRP, you should connect your device to your PC and use adb.
adb pull /tmp/recovery.log
adb exec-out dmesg > dmesg.log
This will create 2 files in the directory your shell is currently in, recovery.log and dmesg.log. You will need to upload these somewhere such as a pastebin or Google Drive. You can also attach it to your XDA post (recommended!)
If you are having an operating system boot issue, you should gather a ramoops log instead. Do this while in TWRP after the failed boot:
adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-7.1)
Device tree: https://github.com/TeamWin/android_device_oneplus_oneplus3 (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_oneplus_msm8996 (twrp-7.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project for the OnePlus 3 & 3T, Tool/Utility for the OnePlus 3
Contributors
jcadduono, Team Win
Source Code: https://github.com/jcadduono/android_device_oneplus_oneplus3
Version Information
Status: Stable
Current Stable Version: 3.0.4-1
Stable Release Date: 2017-01-21
Created 2017-01-23
Last Updated 2017-02-07

Reserved
ONEPLUS FULL OTA ZIPS
You can flash these zips in TWRP to update your device or save yourself from a broken or soft-bricked state.
They are official zips distributed by OnePlus.
For the OnePlus 3 only:
OxygenOS 3.2.8: http://s3.amazonaws.com/oxygenos.on...6_OTA_017_all_1611182000_fbe1471194d64b3e.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...en_16_OTA_035_all_1612310359_e10cadfb2af7.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...n_16_OTA_037_all_1701041839_aa64b084a40a4.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...16_OTA_039_all_1701140133_89fcc9baba94e4c.zip
OxygenOS 4.0.3: http://otafsc.h2os.com/patch/amazon...ygen_16_OTA_041_all_1702081756_0f1e56a75f.zip
For the OnePlus 3T only:
OxygenOS 3.5.3: https://s3.amazonaws.com/oxygenos.o...8_OTA_027_all_1611222319_884473ff95304c30.zip
OxygenOS 3.5.4: http://oxygenos.oneplus.net.s3.amaz...8_OTA_029_all_1612131737_17e7161d2b234949.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...ygen_28_OTA_037_all_1701041831_a2ba632ce9.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_039_all_1701140132_400a7.zip
OxygenOS 4.0.3: http://otafsc.h2os.com/patch/amazon...3TOxygen_28_OTA_041_all_1702081824_e3a712.zip
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full OTA zips in recovery.

jcadduono said:
Team Win Recovery Project 3.0.4-0 (unreleased)
Click to expand...
Click to collapse
Nice mate as always.
Pm: you might need yo check the format of the first post, everything is written 3 times. :laugh:

peshellas said:
Nice mate as always.
Pm: you might need yo check the format of the first post, everything is written 3 times. :laugh:
Click to expand...
Click to collapse
Never quote full op, this is spamming.
For 3 times same content, open xda in browser, it's xda app bug.

RohanAJoshi said:
Never quote full op, this is spamming.
For 3 times same content, open xda in browser, it's xda app bug.
Click to expand...
Click to collapse
You re Right mate, i know, i have been here since the very old days, I thought i had deleted ot, and continued, apparently not. Thanks for the tip, didn't know about the bug.

ext4 decrypted fine on OnePlus 3 OOS 4.0.2.

Is flashing twrp-data-fstype-swap-x.x.zip still necessary when switching between f2fs and ext4?
The instructions and the link are not stated in OP anymore.

fbf2201 said:
Is flashing twrp-data-fstype-swap-x.x.zip still necessary when switching between f2fs and ext4?
The instructions and the link are not stated in OP anymore.
Click to expand...
Click to collapse
Both EXT4 and F2FS should work out of the box now.
No flashing needed.

Hello and thanx for the hard job.
I wanted to try a clean install starting from stock, hoping to correct my issue with twrp black screen.
I need your help. Here is what I've done :
- Restore stock with the unbrick tool
- Update to Nougat 7.0 and OOS4.0.2 via oneplus update
- Unlock bootloader
- Flash twrp 3.0.4-0 via fastboot
- Flash no-verity-opt-encrypt-5.0
- Flash RR rom
- Wipe data and Dalvik
- Reboot.
This is the first time it made it to me. It ask me a password when it boot. I saw a lot of post about that, but I can't understand how to solve it.
Can someone help me please ? My phone is OP3T

Hello, thanks for the super-useful tool. TWRP has been my goto recovery for as long as I have been rooting (days of htc-hd2). I am experiencing the following issues with v3.0.2-1 (all my checkpoint backups are in that version).
* Device = op3
* If it helps, this was a OOS 4.0.1 backup. I was trying to restore it because of a 4.0.2 upgrade failure attempt
* restore hangs at 100% after the backup is complete.
* After waiting for nearly 15 mins, I used the power down to restart the phone - i had lost recovery
* tried to re-install recovery. but when twrp boots - it doesn't get to main menu
* Oddly enough op recovery installs and boots into fine. Which is what I am on.
I am currently on stock recovery without root unable to restore backup ups in twrp and in titanium backup
any thoughts?

Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?

ScratMan38 said:
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
Click to expand...
Click to collapse
Its a unified version

ScratMan38 said:
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
Click to expand...
Click to collapse
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.

cultofluna said:
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
Click to expand...
Click to collapse
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything

cultofluna said:
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
Click to expand...
Click to collapse
it's unified. even if it says op3 it will work for the 3t. read the op. a lot of 3t stuff baked in. works fine. only issue now is the black screen with LED light when booting into recovery. at least for me

Renosh said:
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
Click to expand...
Click to collapse
Thanks your reply was really helpful:laugh:

the 3.0.4.0 is recommend version or have some problem must need? for now i'm use 3.0.3.1 is good with f2fs data partition, OS version is RR-N-v5.8.0-20170117-oneplus3t-Official, i want to dirty flash update to RR-N-v5.8.0-20170122-oneplus3t-Official, i need update TWRP to 3.0.4.0 first? or i can keep use 3.0.3.1?

Renosh said:
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
Click to expand...
Click to collapse
Abaddon said:
it's unified. even if it says op3 it will work for the 3t. read the op. a lot of 3t stuff baked in. works fine. only issue now is the black screen with LED light when booting into recovery. at least for me
Click to expand...
Click to collapse
There was two links in the OP, one for 3.0.3-1 mentioning "unified", and one for 3.0.4 with only "oneplus3".
As I knew the dev was working on both version and still supplies 3.0.3-1 test releases in Op3T thread that were newer than the 3.0.4 he built ; and as the changelog did not mention the unification for 3.0.4, for sure, OP was not clear at all.

Is this 3.0.3.x or 3.0.4.0 backward compatible with Marshmallow ROMs?

chancex said:
the 3.0.4.0 is recommend version or have some problem must need? for now i'm use 3.0.3.1 is good with f2fs data partition, OS version is RR-N-v5.8.0-20170117-oneplus3t-Official, i want to dirty flash update to RR-N-v5.8.0-20170122-oneplus3t-Official, i need update TWRP to 3.0.4.0 first? or i can keep use 3.0.3.1?
Click to expand...
Click to collapse
You want to update a custom rom which by definition has no issue with dm-integrity (only present in stock boot image), so if you don't have any issue keep your recovery.
It seems though that latest version has a minimized risk of issues with f2fs so why not updating it?
cultofluna said:
Thanks your reply was really helpful[emoji23]
Click to expand...
Click to collapse
He was right, the thread's title says clearly 3 and 3T.

[TWRP 3.2.1-1] [ROOT] A8+ sm-a730f - 21/01/2018

Unofficial release -TWRP recovery for the Galaxy A8+ - SM-A730F, EXYNOS 7885
{
"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"
}
TWRP 3.2.1-0 Released
Dec 9, 2017
TWRP 3.2.1-0 is out now for most currently supported devices.
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot
Update 21/1/2017
TWRP 3.2.1-1 NN build released.
Current status: beta
Features:
MTP >> to be confirmed
ADB working >> to be confirmed
SEANDROID warning fix
TWRP and Kernel built from latest source
Raw SYSTEM image backup
NTFS support
F2FS support >> To be added
Twrp app support
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SamMobile or updato.com in case of problems. This will trip the knox counter.
Instructions:
Flash with odin in the AP slot.
Put your device in DOWNLOAD MODE. (POWER +VOL DOWN +VOL UP)
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + VOL DOWN
As soon as the screen goes blank change to POWER + VOL UP
You should now see TWRP recovery.
FAILURE TO FOLLOW THE ABOVE STEPS WILL RESULT IN TWRP BEING REPLACED BY STOCK RECOVERY
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.2.1-1_sm-a730f_210117
To Root:
Flash the latest SuperSU or Magisk release with TWRP:
SUPERSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
MAGISK - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption and mount internal storage (/DATA):
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
DONATE ME HERE IF YOU WANT TO BUY ME A BEER/COFFEE OR HIT THE THANKS BUTTON IF I HELPED YOU

NOTE:
This may be a dead duck in the water before it even installs due to the fact Samsung currently seem to be locking bootloaders on all recent devices even devices with previously unlocked bootloaders.
BEFORE attempting to install this software please ensure you have the stock firmware available (this can be found on updato.com) and that you are able to flash it with Odin.
.

1.1k views, 120 downloads and not one report or tap of a thanks.
XDA truly is about community spirit.
Cheers guys.

If you do one for the the a530f i would be glad to test it ! (if there's no risk of complete brick of course)

tibey said:
If you do one for the the a530f i would be glad to test it ! (if there's no risk of complete brick of course)
Click to expand...
Click to collapse
No risk as long as you've got the firmware handy.

ashyx said:
1.1k views, 120 downloads and not one report or tap of a thanks.
XDA truly is about community spirit.
Cheers guys.
Click to expand...
Click to collapse
It's amazing.
I would very much like to know if this is locked from factory, but no one reports if it can be flashed or not :/

Guide on TWRP recovery for A8
ashyx said:
Unofficial release -TWRP recovery for the Galaxy A8+ - SM-A730F, EXYNOS 7885
TWRP 3.2.1-0 Released
Dec 9, 2017
TWRP 3.2.1-0 is out now for most currently supported devices.
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot
Update 21/1/2017
TWRP 3.2.1-1 NN build released.
Current status: Testing stage
NOTE: THIS IS AS YET UNTESTED. IF YOU DECIDE TO TRY THIS OUT PLEASE REPORT ANY ISSUES WITH DETAILS. POSTS LIKE 'NOT WORKING' WILL BE IGNORED
Features:
MTP >> to be confirmed
ADB working >> to be confirmed
SEANDROID warning fix
TWRP and Kernel built from latest source
Raw SYSTEM image backup
NTFS support
F2FS support >> To be added
Twrp app support
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with odin in the AP slot.
Put your device in DOWNLOAD MODE. (POWER +VOL DOWN +VOL UP)
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + VOL DOWN
As soon as the screen goes blank change to POWER + VOL UP
You should now see TWRP recovery.
FAILURE TO FOLLOW THE ABOVE STEPS WILL RESULT IN TWRP BEING REPLACED BY STOCK RECOVERY
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.2.1-1_sm-a730f_210117
To Root:
Flash the latest SuperSU or Magisk release with TWRP:
SUPERSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
MAGISK - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption and mount internal storage (/DATA):
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
DONATE ME HERE IF YOU WANT TO BUY ME A BEER/COFFEE OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Hello @ashyx, I have made a guide based on your thread: http://techbeasts.com/install-twrp-recovery-root-galaxy-a8-plus-2018/
Just wanted to notify.

Sucks that no one is reporting anything, but tbh in europe it seems that only the A8 (A530f) has been released so far.
Do you think it would be easy to port for that model ? I think there's a couple of us waiting for this port, would be much appreciated and would test it asap.

tibey said:
Sucks that no one is reporting anything, but tbh in europe it seems that only the A8 (A530f) has been released so far.
Do you think it would be easy to port for that model ? I think there's a couple of us waiting for this port, would be much appreciated and would test it asap.
Click to expand...
Click to collapse
It will be ready at some point today.

@tibey
Here you go, good luck: https://androidfilehost.com/?fid=746010030569951180
.

ashyx said:
@tibey
Here you go, good luck: https://androidfilehost.com/?fid=746010030569951180
.
Click to expand...
Click to collapse
Seems to work great on a530f ! Just followed the instructions (had just a minor issur with MTP not working in TWRP)
Thanks a lot :good:
Edit : Guess you should post it there : https://forum.xda-developers.com/ga...18-roms-kernels-recoveries--other-development (damn that forum is invisible in search)

tibey said:
Seems to work great on a530f ! Just followed the instructions (had just a minor issur with MTP not working in TWRP)
Thanks a lot :good:
Edit : Guess you should post it there : https://forum.xda-developers.com/ga...18-roms-kernels-recoveries--other-development (damn that forum is invisible in search)
Click to expand...
Click to collapse
Yep it seems Samsung are forcing the use of their own MTP driver in the kernel as I couldn't disable it.

And it continues, now 2.2k views and 199 downloads and still not one downloader could be bothered to post.

ashyx said:
And it continues, now 2.2k views and 199 downloads and still not one downloader could be bothered to post.
Click to expand...
Click to collapse
Well samsung mtp isn't in a8+ defconfig i just looked. So post your device tree and the partition layout and fstab from stock kernel and I will see if I can help.

travis82 said:
Well samsung mtp isn't in a8+ defconfig i just looked. So post your device tree and the partition layout and fstab from stock kernel and I will see if I can help.
Click to expand...
Click to collapse
I know it isn't which is why it isn't included.
Seems like they are forcing their own driver.
There is probably a way to fix it by modifying the make files, but I won't spend any more time on it until people can be bothered to take the time to respond.

Not working
ashyx said:
Unofficial release -TWRP recovery for the Galaxy A8+ - SM-A730F, EXYNOS 7885
TWRP 3.2.1-0 Released
Dec 9, 2017
TWRP 3.2.1-0 is out now for most currently supported devices.
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot
Update 21/1/2017
TWRP 3.2.1-1 NN build released.
Current status: Testing stage
NOTE: THIS IS AS YET UNTESTED. IF YOU DECIDE TO TRY THIS OUT PLEASE REPORT ANY ISSUES WITH DETAILS. POSTS LIKE 'NOT WORKING' WILL BE IGNORED
Features:
MTP >> to be confirmed
ADB working >> to be confirmed
SEANDROID warning fix
TWRP and Kernel built from latest source
Raw SYSTEM image backup
NTFS support
F2FS support >> To be added
Twrp app support
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SamMobile or updato.com in case of problems. This will trip the knox counter.
Instructions:
Flash with odin in the AP slot.
Put your device in DOWNLOAD MODE. (POWER +VOL DOWN +VOL UP)
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + VOL DOWN
As soon as the screen goes blank change to POWER + VOL UP
You should now see TWRP recovery.
FAILURE TO FOLLOW THE ABOVE STEPS WILL RESULT IN TWRP BEING REPLACED BY STOCK RECOVERY
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.2.1-1_sm-a730f_210117
To Root:
Flash the latest SuperSU or Magisk release with TWRP:
SUPERSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
MAGISK - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption and mount internal storage (/DATA):
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
DONATE ME HERE IF YOU WANT TO BUY ME A BEER/COFFEE OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Not Working Properly its give bootloop
i try according to this method but not working it restart after the first logo of the phone.
odin show passed message but phone get bootloops

akshaygpt2 said:
Not Working Properly its give bootloop
i try according to this method but not working it restart after the first logo of the phone.
odin show passed message but phone get bootloops
Click to expand...
Click to collapse
.
What are your phone specs and build number?

ashyx said:
.
What are your phone specs and build number?
Click to expand...
Click to collapse
Android 7.1.1
Galaxy A8 plus
Sent from my SM-A730F using Tapatalk

akshaygpt2 said:
Android 7.1.1
Galaxy A8 plus
Click to expand...
Click to collapse
I need your firmware build.

ashyx said:
I need your firmware build.
Click to expand...
Click to collapse
Build Firmware -
NMF26X.A730FXXU1ARAC
Sent from my SM-A730F using Tapatalk

[RECOVERY][UNOFFICIAL][excalibur][v3.0.0] Pitch Black Recovery [30/07/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.4.0
PitchBlack version: 3.0.0
For device: excalibur
Maintainer/Authors build: @TheMalachite
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/TheMalachite/android_device_xiaomi_excalibur
Kernel: Prebuilt kernel from MIUI V11.0.2.0.QJXINXM
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
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 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
From PC
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by fastboot flash recovery.img
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
Device Changelog
Code:
2020-07-30
- Initial unofficial release
PBRP Changelog
Code:
v3.0.0
- Fully Redesigned UI
- Added new Keychecks While Flashing PBRP or recovery.img or Ramdisk
- Fully Redesigned Website https://pitchblackrecovery.com
- New Android like Power Menu (Activated via power key hold)
- Flashlight toggled by Vol up(+) on hold
- New Scrollable Advanced menu
- Totally Redesigned Icons
- Removed old unnecessary Theming Stuff
- Tested on almost all handy Resolutions
- Flashlight toggle on Lockscreen
- More checks for SAR/Non-SAR
- New Navbar
- Support on almost all Android version (5.0+)
- Update ozip decrypt
- Fix up ozip print logs & take all paths
- Update FUNDING.yml
- Fixed encrypted removal checks & buttons
- Add Flag for disabling treble compatibility by default
- Is_Data_Wiped: Simplify function signature
- Unified AB_OTA_UPDATER
- Change AB device log storage to /data/recovery
- Delay start if specified in board
- Optimize touchscreen driver initialization delay.
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Downloads
Flashable zip
https://drive.google.com/file/d/18MzNCTExOWLiu9ZUD3A7SXlD4QY2grrZ/view?usp=drivesdk
XDA:DevDB Information
PitchBlack Recovery Project, Tool/Utility for the Redmi Note 9 Pro Max
Contributors
TheMalachite, Reza Adi, Shovon, Manjot Sidhu, Mohd Faraz, Sagar
Version Information
Status: Stable
Current Stable Version: 3.0.0
Stable Release Date: 2020-07-30
Created 2020-07-30
Last Updated 2020-07-30

Bugs: You tell me

Reserved #2

thank you sir..... for providing this recovery and opportunity to test your initial relese

Good but when other custom rom for redmi note 9 pro max

[email protected]@ said:
Good but when other custom rom for redmi note 9 pro max
Click to expand...
Click to collapse
When their will be dev who wanna build custom rom for it

Flashed it via fastboot from Platform Tools folder. Rebooted into recovery mode. And Pitch Black was installed successfully. Then transferred the pitchblack zip folder to sd card. And installed it through pitchblack. Rebooted to system.
After the system reboot, again switched off phone and entered recovery mode, only to find that the pitchblack was overwritten by system recovery.
tried wiping data second time, after installing pitchblack. Again it was overwritten by system recovery.
Do I need to do any additional steps within pitchblack, before rebooting to system?
Or install any ROM?
My final aim is to install LineageOS, which currently isn't available for this devise..
Any help is greatly appreciated...

Vijo123 said:
Flashed it via fastboot from Platform Tools folder. Rebooted into recovery mode. And Pitch Black was installed successfully. Then transferred the pitchblack zip folder to sd card. And installed it through pitchblack. Rebooted to system.
After the system reboot, again switched off phone and entered recovery mode, only to find that the pitchblack was overwritten by system recovery.
tried wiping data second time, after installing pitchblack. Again it was overwritten by system recovery.
Do I need to do any additional steps within pitchblack, before rebooting to system?
Or install any ROM?
My final aim is to install LineageOS, which currently isn't available for this devise..
Any help is greatly appreciated...
Click to expand...
Click to collapse
I am waiting for my bootloader time 133 hours provided by MI. I will flash and provide feedback on 13 August.

kannss said:
I am waiting for my bootloader time 133 hours provided by MI. I will flash and provide feedback on 13 August.
Click to expand...
Click to collapse
Ok. Never go back to 'Mi Unlock Status' under Developer Options to add ur device again...
I did that mistake and my wait time got reset to give me new wait time.
Also don't log out of Mi account or play with 'Find Device' settings.
U may know already. But im just saying..
If u face any driver related issues, then in the Mi Unlock Tool itself, they have provided a way to install it, if u check their settings...
Good Luck

Vijo123 said:
Flashed it via fastboot from Platform Tools folder. Rebooted into recovery mode. And Pitch Black was installed successfully. Then transferred the pitchblack zip folder to sd card. And installed it through pitchblack. Rebooted to system.
After the system reboot, again switched off phone and entered recovery mode, only to find that the pitchblack was overwritten by system recovery.
tried wiping data second time, after installing pitchblack. Again it was overwritten by system recovery.
Do I need to do any additional steps within pitchblack, before rebooting to system?
Or install any ROM?
My final aim is to install LineageOS, which currently isn't available for this devise..
Any help is greatly appreciated...
Click to expand...
Click to collapse
Enable DM VERITY

MaheshTechnicals said:
Enable DM VERITY
Click to expand...
Click to collapse
Will it keep PB Recovery form overwritten?
Because, ppl try to disable DM verity, so im asking.
Also, I managed to root my Pro Max using Magisk manager. But a lack of custom recovery always hurts.
So how do i Enable DM verity now?

I'm on rooted (magisk), device with xposed installed and working BUT stock recovery. waiting for you to successfully stick the tarp and I'll follow. Kindly keep updating results and steps tried by you.
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
Vijo123 said:
Will it keep PB Recovery form overwritten?
Because, ppl try to disable DM verity, so im asking.
Also, I managed to root my Pro Max using Magisk manager. But a lack of custom recovery always hurts.
So how do i Enable DM verity now?
Click to expand...
Click to collapse
I'm on rooted (magisk), device with xposed installed and working BUT stock recovery. waiting for you to successfully stick the tarp and I'll follow. Kindly keep updating results and steps tried by you.

I'm currently using SD Maid app (Pro version) to remove all unnecessary bloatwares. Works like a charm.
And IMO, also works better than Termux or any other debloater. Although debloating is just one of the function of termux, but if u r using it just to debloat, then better go for SD Maid ?

UPDATE : i installed as per instructions for installation from PC, first recovery.img and then flashed whole zip. Worked great. after rebooting device twice manually,, recovery sticks,, and its a great one. excellent work done.
just one question, what does magisk manager installation in recovery do ? (Specials>tools>magisk manager)

coolvipcandy said:
UPDATE : i installed as per instructions for installation from PC, first recovery.img and then flashed whole zip. Worked great. after rebooting device twice manually,, recovery sticks,, and its a great one. excellent work done.
just one question, what does magisk manager installation in recovery do ? (Specials>tools>magisk manager)
Click to expand...
Click to collapse
Did u wipe data or dalvik etc. Because mine got overwritten by system recovery.
Can u please tell how did u do, STEP BY STEP?
Maybe my adb fastboot tools were outdated??

Vijo123 said:
Will it keep PB Recovery form overwritten?
Because, ppl try to disable DM verity, so im asking.
Also, I managed to root my Pro Max using Magisk manager. But a lack of custom recovery always hurts.
So how do i Enable DM verity now?
Click to expand...
Click to collapse
Vijo123 said:
Did u wipe data or dalvik etc. Because mine got overwritten by system recovery.
Can u please tell how did u do, STEP BY STEP?
Maybe my adb fastboot tools were outdated??
Click to expand...
Click to collapse
i did as mentioned in first post,, as i was already root, i first flashed recovery.img and then from recovery, flashed the whole zip archive. thats all.
then.booted to system,, again booted manually to recovery and it was there,, and checked twice again, recovery was there.
---------- Post added at 05:25 AM ---------- Previous post was at 05:24 AM ----------
i didnt mess with dm verity,,

Working fine in my device. Successfully rooted and installed Edxposed. Everything working fine.

how to wipe "system" partition, there's no option for that ??
wipe > Advance > ???

Format data option
---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------
Do not install inbuilt magisk from this recovery. It gives bootloop, download from github or xda and flash zip manually

Stuck on fastboot mode
PLEASE HELP
i installed twrp recovery in my redmi note 9 pro max and install magisk , now my device is stuck on fastboot.
---------- Post added at 05:22 AM ---------- Previous post was at 05:18 AM ----------
kannss said:
Working fine in my device. Successfully rooted and installed Edxposed. Everything working fine.
Click to expand...
Click to collapse
bro when i installed i got stuck in fastboot
what should i do now ...? should i install custom rom or not

[RECOVERY][OFFICIAL][Cereus][v3.0.0] Pitch Black Recovery [TWRP 3.4.0]

{
"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.4.0
PitchBlack version: 3.0.0
For device: Cereus
Maintainer/Authors build: Erwin Abs
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Kernel: https://github.com/xiaomi-mt6765
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
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 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
From PC
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by fastboot flash recovery.img
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
Changelog
PBRP Side Changelog
Code:
v3.0.0
- Fully Redesigned UI
- Added new Keychecks While Flashing PBRP or recovery.img or Ramdisk
- Fully Redesigned Website https://pitchblackrecovery.com
- New Android like Power Menu (Activated via power key hold)
- Flashlight toggled by Vol up(+) on hold
- New Scrollable Advanced menu
- Totally Redesigned Icons
- Removed old unnecessary Theming Stuff
- Tested on almost all handy Resolutions
- Flashlight toggle on Lockscreen
- More checks for SAR/Non-SAR
- New Navbar
- Support on almost all Android version (5.0+)
- Update ozip decrypt
- Fix up ozip print logs & take all paths
- Update FUNDING.yml
- Fixed encrypted removal checks & buttons
- Add Flag for disabling treble compatibility by default
- Is_Data_Wiped: Simplify function signature
- Unified AB_OTA_UPDATER
- Change AB device log storage to /data/recovery
- Delay start if specified in board
- Optimize touchscreen driver initialization delay.
v3.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Device Side Changelog
Code:
Bugs
- You tell me!
Downloads
Flashable zip
https://pitchblackrecovery.com/cereus
XDA:DevDB Information
PitchBlack Recovery Project, Tool/Utility for the Xiaomi Redmi 6
Contributors
Erwin Abs
Version Information
Status: Stable
Created 2020-10-29
Last Updated 2020-10-30

Notes: specifically in miui based on android 9!! (not recommended on oreo base firmware)
If you were on Twrp before Just Install flashable zip and press volume up for automatic reboot

I want process to flash the recovery to my device. My phone got Hard bricked because of arb protection. Can i get help? Please

Aadharsh.1 said:
I want process to flash the recovery to my device. My phone got Hard bricked because of arb protection. Can i get help? Please
Click to expand...
Click to collapse
Flash recovery.img stock miui oreo from fastboot

Erwin Abs said:
Flash recovery.img stock miui oreo from fastboot
Click to expand...
Click to collapse
No. I mean that i got hard bricked. No recovery, no fastboot, dead screen with constantly vibration (non stop). I got repaired my phone from the service centre since edl was blocked. I want do not want to get bricked again. I just want to know how do you flash it. Some says to flash it normally (fastboot flash recovery.img), some says to flash dummy.img for arb bypass, some says to boot the recovery(fastboot boot recovery.img) and flash the recovery from the recovery itself. I am just confused here. I don't want to get bricked again. I just want to know how did you flash without any problem. ARB protection is the main problem here. I tried to flash PB recovery. The fastboot command says it was successful and when i reboot to recovery, only stock recovery was there. So i tried to flash twrp(official one from twrp page), i got bricked cause of arb.

Can I install twrp on miui 11.0.5.0 android 9. I am afraid the phone will get bricked

sayad1 said:
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.2.3
PitchBlack version: 2.9.0
For device: tulip
Maintainer/Authors build: @rezaadi0105 @sayad1
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/rezaadi0105/android_device_xiaomi_tulip-twrp
[*]Kernel: Give kernel link here, remove this line if you are using prebuilt kernel
[*]PitchBlack Team: @rezaadi0105, @firewolfxda, @manjot.gni, @androiabledroid, Arbaz Khan
Features
Installation Instructions
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
from PC (Windows & Linux)
Download PBRP PC Installer zip from bellow
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP PC installer zip & copy the flashable zip to the installer folder
Goto fastboot mode in your device
Windows users open pbinstaller.bat file
Linux users execute pbinstaller.sh in a terminal
Follow the introductions on the installer from there
Enjoy
(LInux users will need unzip, adb & fastboot installed on their system)
changelog
Code:
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
flashable zip
download link here
2019.1.27
https://sourceforge.net/projects/pi...lip-2.9.0-20181211-1618-OFFICIAL.zip/download
Telegram :- https://t.me/tulipofficial
pC INSTALLER
https://sourceforge.net/projects/pi...ller/PB_Installer_20181014_ALPHA.zip/download
Click to expand...
Click to collapse
Erwin Abs said:
Flash recovery.img stock miui oreo from fastboot
Click to expand...
Click to collapse
Erwin Abs said:
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.4.0
PitchBlack version: 3.0.0
For device: Cereus
Maintainer/Authors build: Erwin Abs
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Kernel: https://github.com/xiaomi-mt6765
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Installation Instructions
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
From PC
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by fastboot flash recovery.img
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
Changelog
PBRP Side Changelog
Code:
v3.0.0
- Fully Redesigned UI
- Added new Keychecks While Flashing PBRP or recovery.img or Ramdisk
- Fully Redesigned Website https://pitchblackrecovery.com
- New Android like Power Menu (Activated via power key hold)
- Flashlight toggled by Vol up(+) on hold
- New Scrollable Advanced menu
- Totally Redesigned Icons
- Removed old unnecessary Theming Stuff
- Tested on almost all handy Resolutions
- Flashlight toggle on Lockscreen
- More checks for SAR/Non-SAR
- New Navbar
- Support on almost all Android version (5.0+)
- Update ozip decrypt
- Fix up ozip print logs & take all paths
- Update FUNDING.yml
- Fixed encrypted removal checks & buttons
- Add Flag for disabling treble compatibility by default
- Is_Data_Wiped: Simplify function signature
- Unified AB_OTA_UPDATER
- Change AB device log storage to /data/recovery
- Delay start if specified in board
- Optimize touchscreen driver initialization delay.
v3.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Device Side Changelog
Code:
Bugs
- You tell me!
Downloads
Flashable zip
https://pitchblackrecovery.com/cereus
XDA:DevDB Information
PitchBlack Recovery Project, Tool/Utility for the Xiaomi Redmi 6
Contributors
Erwin Abs
Version Information
Status: Stable
Created 2020-10-29
Last Updated 2020-10-30
Click to expand...
Click to collapse
Please reply soon for my problem i have posted already. I am depending on your method

Aadharsh.1 said:
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.2.3
PitchBlack version: 2.9.0
For device: tulip
Maintainer/Authors build[email protected]
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/rezaadi0105/android_device_xiaomi_tulip-twrp
Kernel: Give kernel link here, remove this line if you are using prebuilt kernel
PitchBlack Teamrezaadi0105, @firewolfxda, @manjot.gni, @androiabledroid, Arbaz Khan
Features
Installation Instructions
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
from PC(Windows & Linux)
Download PBRP PC Installer zip from bellow
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP PC installer zip & copy the flashable zip to the installer folder
Goto fastboot mode in your device
Windows users open pbinstaller.bat file
Linux users execute pbinstaller.sh in a terminal
Follow the introductions on the installer from there
Enjoy
(LInux users will need unzip, adb & fastboot installed on their system)
changelog
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.4.0
PitchBlack version: 3.0.0
For device: Cereus
Maintainer/Authors build: Erwin Abs
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Kernel:https://github.com/xiaomi-mt6765
PitchBlack Teamrezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Installation Instructions
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
From PC
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by fastboot flash recovery.img
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
Changelog
PBRP Side Changelog
Please reply soon for my problem i have posted already. I am depending on your method
Click to expand...
Click to collapse
Just install zip, only for firmware miui Pie

tranluc123 said:
Can I install twrp on miui 11.0.5.0 android 9. I am afraid the phone will get bricked
Click to expand...
Click to collapse
This has been tested on Miui Pie firmware

Aadharsh.1 said:
No. I mean that i got hard bricked. No recovery, no fastboot, dead screen with constantly vibration (non stop). I got repaired my phone from the service centre since edl was blocked. I want do not want to get bricked again. I just want to know how do you flash it. Some says to flash it normally (fastboot flash recovery.img), some says to flash dummy.img for arb bypass, some says to boot the recovery(fastboot boot recovery.img) and flash the recovery from the recovery itself. I am just confused here. I don't want to get bricked again. I just want to know how did you flash without any problem. ARB protection is the main problem here. I tried to flash PB recovery. The fastboot command says it was successful and when i reboot to recovery, only stock recovery was there. So i tried to flash twrp(official one from twrp page), i got bricked cause of arb.
Click to expand...
Click to collapse
if you are on twrp LR mod just install zip and press volume up to reboot into auto recovery

Erwin Abs said:
Flash recovery.img stock miui oreo from fastboot
Click to expand...
Click to collapse
Erwin Abs said:
if you are on twrp LR mod just install zip and press volume up to reboot into auto recovery
Click to expand...
Click to collapse
I am on stock rom. Does nothing happenes if i just flash normally? Also do i need to flash any zips like disable force encryption, lazyflasher,etc after successfully flashed PB

Erwin Abs said:
This has been tested on Miui Pie firmware
Click to expand...
Click to collapse
Then can you root android 9 miui 11.0.5.0?

Beta Build UP
Changelog:
- Initial Unified Redmi 6/6A
- Add Arm64 Support
- Drop Critical Partitions
- Based on TWRP 3.5.2
- Decrypt Need TEST.
https://sourceforge.net/projects/pbrp/files/cactus/PBRP-cactus-3.1.0-20210817-0331-BETA.zip/download

Aadharsh.1 said:
No. I mean that i got hard bricked. No recovery, no fastboot, dead screen with constantly vibration (non stop). I got repaired my phone from the service centre since edl was blocked. I want do not want to get bricked again. I just want to know how do you flash it. Some says to flash it normally (fastboot flash recovery.img), some says to flash dummy.img for arb bypass, some says to boot the recovery(fastboot boot recovery.img) and flash the recovery from the recovery itself. I am just confused here. I don't want to get bricked again. I just want to know how did you flash without any problem. ARB protection is the main problem here. I tried to flash PB recovery. The fastboot command says it was successful and when i reboot to recovery, only stock recovery was there. So i tried to flash twrp(official one from twrp page), i got bricked cause of arb.
Click to expand...
Click to collapse
I also facing this issue now. I flash two different ROMs and no one boot up, so i think if it is related to recovery issue, and i downloaded twrp.img and flash it via PB and restart to new recovery. And now it keeps vibration. I'll try to find a way to maye it survive, but i cant stop it from vibrating. its really noisy.

Jackboy2 said:
I also facing this issue now. I flash two different ROMs and no one boot up, so i think if it is related to recovery issue, and i downloaded twrp.img and flash it via PB and restart to new recovery. And now it keeps vibration. I'll try to find a way to maye it survive, but i cant stop it from vibrating. its really noisy.
Click to expand...
Click to collapse
Even when I flashed twrp in Redmi Y2/S2, the phone got bricked. But the phone can boot twrp successfully. So i just flashed a custom rom.
Anyways, i gave up both the phones and bought a new one. I flashed xiaomi.eu and I'm satisfied with that.

Jackboy2 said:
I also facing this issue now. I flash two different ROMs and no one boot up, so i think if it is related to recovery issue, and i downloaded twrp.img and flash it via PB and restart to new recovery. And now it keeps vibration. I'll try to find a way to maye it survive, but i cant stop it from vibrating. its really noisy.
Click to expand...
Click to collapse
Well, idk but i think the only way to revive the phone is to flash the rom in edl mode with sp flash tool. Just remove your back cover, disconnect the fingerprint and battery. Now open the sp flash tool and select the rom to be flashed and it will wait for the device to connect.
Now hold volume down and connect the usb to enter into edl mode.
But the problem is, Xiaomi blocked the access for edl flashing. You'll require an auth file and authorised mi account.
I tried this tutorial a way long back. Maybe now there could be a way to bypass with a modified auth file.

Jackboy2 said:
I also facing this issue now. I flash two different ROMs and no one boot up, so i think if it is related to recovery issue, and i downloaded twrp.img and flash it via PB and restart to new recovery. And now it keeps vibration. I'll try to find a way to maye it survive, but i cant stop it from vibrating. its really noisy.
Click to expand...
Click to collapse
There was a crack available for snapdragon phones which disables mi account to flash the rom.
But the mediatek phones are hopeless. You have to take it to the service centre.

Aadharsh.1 said:
There was a crack available for snapdragon phones which disables mi account to flash the rom.
But the mediatek phones are hopeless. You have to take it to the service centre.
Click to expand...
Click to collapse
Something interesting, after it vibrate til battery dead, i connect it to PC and try to flash it via SP, and it boot up, also can go to fastboot.
So i flash PB back and flash Los, now its working perfectly.
Thanks for your reply

[ROM][UNOFFICIAL][13] LineageOS 20 for Xperia X Compact

{
"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 <std_disclaimer.h>
/*
* 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.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.​​LineageOS is based on the Android Open Source Project, with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.​​All the source code for LineageOS is available in the LineageOS GitHub organization.​And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.​You can also view the changelog for a full list of changes & features.​​Official LineageOS website : http://lineageos.org​About LineageOS Legal : http://lineageos.org/legal​
Important Information
1. This ROM operates without ODM images, just follow the installation instructions.​2. This ROM does not intended to support Google Camera, but you can try to play with some mods.​
About FDE and FBE​Full-disk encryption (FDE) has been completely deprecated since Android 13, and now we use software implementation of File-based encryption (FBE).​​FDE and FBE methods are incompatible with each other. FBE cannot decrypt data encrypted with FDE and cannot encrypt existing files. That's why you need to perform factory reset/format data (not just "wipe data") before switching between ROM's with different encryption methods.​​To make it a bit clear:​- FDE (e.g. stock, LineageOS-16/19) -> FBE (LineageOS-20) -> NOT POSSIBLE! Format data is required.​- FBE -> FBE -> POSSIBLE! You can update/upgrade using "dirty" installation as before, in case if encryption methods are the same​​Moreover, to work with new encryption you need a recovery with appropriate support.​​Downloads Links
LineageOS 20:​Unofficial: https://sourceforge.net/projects/loire-development/files/lineageos-20/kugo​​Google Applications (optional):​MindTheGapps: https://androidfilehost.com/?w=files&flid=322935 (Android 13.0 -> arm64)​XDA post about GApps: https://xda-developers.com/download-google-apps-gapps​​Recommended Recovery (optional):​TWRP 3.x: https://forum.xda-developers.com/-/-t3793837​
Flashing and updating
Before installation, please make sure you have read and understood everything correctly about FDE and FBE encryption methods.​​LineageOS clean install:​
Download the latest build of LineageOS ROM
Full wipe and factory reset (recommended / backup to make sure not to loose data)
Flash the LineageOS ROM zip from the Recovery
Flash the GApps to have the Google Applications (optional)
Every additional zip you want to flash (optional)
Reboot
LineageOS update/upgrade:​
Download the latest build of LineageOS ROM
Wipe cache and dalvik cache
Flash the latest LineageOS ROM zip from the Recovery
Every additional zip you want to flash (optional)
Reboot
You can also update using the built-in Updater (requires at least TWRP 3.6.x or LineageOS Recovery)​
About the builds:
Kernel sources: https://github.com/Chippa-a/android_kernel_sony_msm8956​
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0
(Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Also thanks to:
The LineageOS Team
The SODP Team
Everyone involved in working and testing
Contributors
Chippa_a
ROM OS Version: 13.x
ROM Kernel: Linux 4.9.x
Version Information
Status: Beta

FEATURES AND ISSUES
Boot: Ok
Bluetooth: Unknown
WiFi: Ok
WiFi Hotspot: Unknown
RIL - Phone - Data: Ok
GPS: Ok
Camera: Unknown
Camcorder: Unknown
Lights: Ok
MicroSD: Ok
Accelerometer: Ok
Compass: Ok
Gyroscope: Ok
QTI sensors: Ok
Touchscreen: Ok
FM Radio: N/A
Fingerprint: Ok
Vibrator: Ok
Microphone: Ok
Audio & music: Ok
Bluetooth audio: Ok
NFC: Unknown (HCE: Unknown)
Kernel: Ok (WIP)
Graphics: Ok
3D Rendering: Ok
Clock: Ok
DRM: Unknown
Offline Charging: Ok
USB: Ok
USB Tethering: Unknown
USB OTG: Ok
Encryption: Ok
SEPolicies: Enforcing

It's amazing bro, i can't bealive my device got A13

It seems the device is working again - post removed

soomon said:
I installed this system, and at the 2nd reboot my phone is dead. completely dead. seems it has been bricked before I even could log into my google account.
It doesnt even react to power any more.
Of course the phone is old and wasnt used for a long time, so I dont know if it got bricked by the OS or the hardware.
but it's dead.
be careful people!
Click to expand...
Click to collapse
It's almost impossible to brick this device completely just by ROM, unless you're doing something very unusual or developer-related.
This ROM has been tested by user for more than two weeks and everything was fine. It also been tested by Xperia X users since March, there was nothing like that either... and there never was actually.
Anyway, there is no specific in your message, except "It doesnt even react to power any more". Try to get adb/fastboot modes, charge or flash stock firmware. If no luck, I'm pretty sure it's a hardware issue, probably battery or something else.

I was also thinking about this and it was hard for me to believe the custom OS could actually damage the hardware.
I am happy to report it seems to be the device itself that caused the issue and not the rom. Today it was working Since it is an old device I'm assuming it was a hardware issue, so I deleted my old post.
It's working perfectly now. thank you so much!

I'll install this asap. Cant belive that this device is live again. Im using it as main phone. Gonna post my experience with rom here. Cheers
Edit: Cant seems to make it work . i was on latest stock, did full wipe , installed clean los20 , no gapps no additional zipps . it goes past sony logo shows black screen and immediately restarts on that black screen . Any suggestions ?
Edit 2 : I could not boot to twrp , i needed to install it again after los20 zip, like there is no recovry ? Is that normal ?

After install this rom i found bugs on this rom A13 LOS 20:
-WIFI
-HOTSPOT
-TAP TO WAKE NOT WORK
- GPS can't lock
- NFC
Edit : after reinstall from Lineage 19 to Lineage 20 , Wifi , hotspot , Gps , working fine
Thanks for @Chippa_a and team , share and build rom for x compact

Deep sleep pretty good , keep it up

shandu98 said:
Edit 2 : I could not boot to twrp , i needed to install it again after los20 zip, like there is no recovry ? Is that normal ?
Click to expand...
Click to collapse
Do you have the latest TWRP offered on the other thread? If you get a boot loop back into TWRP you can try tapping restart to system which is an option within TWRP. If you still have problems after with a boot loop try a clean install by wiping dalvik, cache, system, internal storage, followed by formatting data, then reboot to TWRP flash the build and tap restart to system when finished.

my device sony x compact is stuck on twrp logo, is there any solution to fix it?
Note: before stuck on twrp logo, i want to downgrade to A12. but after I entered recovery by (power + vol-) the device was stuck at the twrp logo

Tri Akbar Fitriana said:
my device sony x compact is stuck on twrp logo, is there any solution to fix it?
Note: before stuck on twrp logo, i want to downgrade to A12. but after I entered recovery by (power + vol-) the device was stuck at the twrp logo
Click to expand...
Click to collapse
The same here. The solution for me: i flash stock Rom then Twrp and then los20. After flash los20 twrp stuck on logo, but i can use Los20. Many thanks for los20. Its a great rom.

Asta01 said:
The same here. The solution for me: i flash stock Rom then Twrp and then los20. After flash los20 twrp stuck on logo, but i can use Los20. Many thanks for los20. Its a great rom.
Click to expand...
Click to collapse
if I flash it to stockrom, does it need a TA file? because my TA file is missing.

Tri Akbar Fitriana said:
if I flash it to stockrom, does it need a TA file? because my TA file is missing.
Click to expand...
Click to collapse
I flash Stockrom with flashtool. I dont need TA file.

Tri Akbar Fitriana said:
if I flash it to stockrom, does it need a TA file? because my TA file is missing.
Click to expand...
Click to collapse
No.
Try lineage recovery it works for me, with twrp i get black screen

Chippa_a said:
Moreover, to work with new encryption you need a recovery with appropriate support.
Click to expand...
Click to collapse
For those who have issues with recovery after this ROM.
Please make sure you have installed latest unofficial version (3.7.0_12+) with support for the new FBE encryption method, as stated in OP. Older versions cannot decrypt data encrypted with this method!

Chippa_a said:
For those who have issues with recovery after this ROM.
Please make sure you have installed latest unofficial version (3.7.0_12+) with support for the new FBE encryption method, as stated in OP. Older versions cannot decrypt data encrypted with this method!
Click to expand...
Click to collapse
Thanks,with twrp 3.7.0_12 is twrp working.

Thank you chippa _a. The rom is amazing. I haven't found any bugs so far, and it's incredibly fast. A new life for the Xperia x compact. Thanks alot.

Thanks a lot for this rom! I running it for a few days and no bugs so far
I'm wondering which cam app is the best to use?
And I have one app which doesn't run because my phone is rooted, is there a solution for that?

SietZ said:
Thanks a lot for this rom! I running it for a few days and no bugs so far
I'm wondering which cam app is the best to use?
And I have one app which doesn't run because NY phone is rooted, is there a solution for that?
Click to expand...
Click to collapse
For me is Google cam port "MGC_8.2.204_Parrot043_V1" working perfect.