Pitchblack2.8.0 Twrp3.2.1.0(mido) - Xiaomi Redmi Note 4 Guides, News, & Discussion

TWRP PitchBlack 2.8.0
3.2.1..0
https_%2F%2Favatars2.githubusercontent.com%2Fu%2F37493898_s=280&v=4
TWRP (Team Win Recovery Project) PitchBlack is a TWRP developed by Reza Adi, maintained by Manjot Sidhu and Mohd Faraz and themed by FireWolf.
Is based on TWRP 3.2.1-0
COMPILED BY IUME TEAM
PitchBlack-TWRP
Brought to you by: androiabledroid, firewolfxda, manjotsidhu, pitchblack, rezaadipangest
Treble spported recovery for mido
This is not my build I am just shire. I am not
responsible your break device.your own risk flash
DOWNLOD >
https://sourceforge.net/projects/pitchblack-twrp/
Installation guide:
If you also want the tools available in TWRP PitchBlack:
(SuperSU, Unroot SuperSU, Unroot Magisk, FP Scanner, RM Subs Overlays, Enable HAL3, MTP Fix, Lazy Flasher, Magisk, Aroma FM, Pin / Pass Remover, RM All Subs Overlays, Delete App)
1. Copy the "Zip Installer" to your Micro SD Card.
2. Install it by clicking on Install » Select Storage » Mircro SD Card and select the TWRP PitchBlack zip, do a swipe, the installation will be automatic, you will automatically find yourself in the new TWRP.
If you do not want the tools in TWRP PitchBlack:
(SuperSU, Unroot SuperSU, Unroot Magisk, FP Scanner, RM Subs Overlays, Enable HAL3, MTP Fix, Lazy Flasher, Magisk, Aroma FM, Pin / Pass Remover, RM All Subs Overlays, Delete App)
1. Download the "recovery.img" in your PC.
2. Open ADB & Fastboot Minimal. [DOWNLOAD]
3. Type
Code:
fastboot flash recovery
5. Click space and drag the TWRP PitchBlack downloaded into the fastboot window.
Requirements:
Bootloader unlocked
FRP Unlocked
Status: Stable, only bug is backup of F2FS

I cleaned the thread up for you and moved it to the discussion section where "shares" go. :good:

Related

[Treble][Rom]Lenovo zenui 5.0 for redmi note 6 pro

I found our device is treble supported type-A partition
So here i found (gsi) zenui 5.0 need to test
INSTALL
* Enable Treble > Flash a Fully-Trebled 8.1 ROM or just wipe data,cache,system
Mount the system, go to the system / etc directory backup selinux folder
Flash fbe disabler and permissiver
Wipe everything except vendor
Flash zui system flashme . zip
Mount system and vendor
Flash all patches
Flash sound fix
Mount the system to copy the selinux folder backed up in advance to the /system/etc directory.
Flash magisk if u need
* first reboot may take some time
Bootloop Fix:
- If you still have bootloop or systemui fc format data
Bugs:
- Nothing
(I'm not developer)
Android Version
- 8.1 Oreo
DOWNLOAD
https://mega.nz/#F!af4xQIKa!Ffz3u-9MOtFmxbDFUk9ZZg
PATCHES
https://share.weiyun.com/5khJ8F9
Thanks for sharing
thank for shearing but do you install it (screenshot?)

[GUIDE] Run OEM GSI on Xperia X Performance

I tested some OEM GSI of Erfan, I give a list which GSI could run on our device.
Download Link
If you meet random reboot when booting, try to flash Treble files(boot.img vendor.img) again.
V2.0 is the most stable Treble version, I tested on it.
These GSI could run on V2.0 :
Flyme-Aonly-9-20190702-ErfanGSI
HydrogenOS-Aonly-9-20190614-ErfanGSI
MIUI-Aonly-9-20190529-ErfanGSI
OxygenOS-Aonly-9-20190701-ErfanGSI
ZUI-Aonly-9-20190617-ErfanGSI
How to flash​
1.Flash treble files.(See Readme.txt)
2. Flash GSI.
3 Make sure your data partition is not encrypted.(Format in twrp)
4.Get adb permission.
5 Flash treble TWRP and flash Magisk.
6. Reboot.
How to get ADB permission​1. Our treble TWRP V2 doesn't support MTP, so we need V1 to access Data partition.
2. After you flashed and boot into treble TWRP V1, You need to make sure your data partition is not encrypted. So you need to format data partition.
3. Enable adb before boot using this command in TWRP:
Linux/mac :
Code:
adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys
Win :
Code:
adb push C:\Users\[COLOR="Red"]<userName>[/COLOR]\.android\adbkey.pub /data/misc/adb/adb_keys
4.Reboot, you will get adb permission.
How to kill[ Notch/B]​
1. Move fxxknotchv6.apk to /system/product/overlay
2. Set permission 0664
3.Reboot
Attention​1. HydrogenOS-Aonly-9-20190614-ErfanGSI will failed at Setup guide. You can run these commands to disable Setup guide.
Code:
adb shell
settings put global device_provisioned 1
settings put secure user_setup_complete 1
reboot
You can go into desktop. Then delete SetupWizard.apk.
2. MIUI will cost a long time on booting. If you can't enter desktop, try to showdown with power + vol up, then boot again.
3. OxygenOS need to flash OOSHDRfixAonly after flashing system image.
You can download it from Here.
@Sjll so do you think it's OK for daily use? thx.
f870103 said:
@Sjll so do you think it's OK for daily use? thx.
Click to expand...
Click to collapse
No,there still are some hugs.
Anyone installed one UI in our treble build? Does it work?

[SOLVED]9t - stuck in the bootloop with bad magisk module

[Android10 + MIUI 11]
1. Trying to add new module (extra power menu) and... kaboom - phone stuck at boot.
1a. I'm flashing orginal boot.img
2. No working^ TWRP for me - bootloop and/or data folder mounted in the read only mode or listed as complete mess. No chance for removing bad module.
3. ADB method for removing module - not working under Android 10 :/
4. The situation: no magisk, no root, no GPay
The question: is there anyway to prepare magisk boot image w/o modules loading?
https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
garett76 said:
[Android10 + MIUI 11]
1. Trying to add new module (extra power menu) and... kaboom - phone stuck at boot.
1a. I'm flashing orginal boot.img
2. No working^ TWRP for me - bootloop and/or data folder mounted in the read only mode or listed as complete mess. No chance for removing bad module.
3. ADB method for removing module - not working under Android 10 :/
4. The situation: no magisk, no root, no GPay
The question: is there anyway to prepare magisk boot image w/o modules loading?
Click to expand...
Click to collapse
Use TWRP, its File Manager.
Navigate to /data/adb/modules
Each installed module has its folder - recognize by name which folder corresponds to your errant module.
Put an empty file disable (for disabling) or remove (for removing) into that folder
Reboot but with the patched boot - on that next booting Magisk will find the file and disable or remove the given module
OtangeFox or certain unofficial TWRPs , or modules for TWRP also help to disable or remove Magidk modules by the same mechanism (leaving the file there for Magisk to find on next boot) - this way you can do it manually, not depending on additional tools and knowing how and why it actually works
zgfg said:
Use TWRP, its File Manager.
Navigate to /data/adb/modules
(cut)
Click to expand...
Click to collapse
Thank you!
Solved.
In the /data/adb/ was some folders with unreadable names. But only one included only 3 files, which is the number of my installed magisk modules. After removing them with TWRP file manager and sending patched magisk img phone booted succesfuly. Thank you!
garett76 said:
Thank you!
Solved.
In the /data/adb/ was some folders with unreadable names. But only one included only 3 files, which is the number of my installed magisk modules. After removing them with TWRP file manager and sending patched magisk img phone booted succesfuly. Thank you!
Click to expand...
Click to collapse
Ok, glad you solved.
But if you have stock MIUI 11, then official TWRP (3.4.0)
https://dl.twrp.me/davinci/
or 3.4.0.2 by brigudav (I prefer since it supports backup/restore for practically all partitions):
https://forum.xda-developers.com/showpost.php?p=83090455&postcount=1
should properly see all files and folders on Data and Internal memory.
Don't know for EEA weekly builds or if you flashed DFE (IMO, then specially shouldn't be a problem with unreadable names)

[11] [GSI] [OFFICIAL] AOSP Q Mod //CAOS

C A O S​(Note, I did not make this rom. This is a Generic System Image (GSI) made by Caos' devs. so it is not specifically built for the A51, but it's really stable and I am using it now. ALL CREDIT GOES TO CAOS' DEVS!)
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​​
CAOS (Custom AOSP OS) is a project which is based on @phhusson's Treble GSI AOSP 10. CAOS' devs began it because ASOP has stability, speed and support but also some issues and limitations - pure AOSP's code has some bugs and it doesn't have much useful things and it's hard to pull it. So CAOS' devs did this fork. System can run with SELinux enforced state, as an original Phh AOSP GSI. Fully compatible with PHH-Treble patches exclude few low level changes: no root app, no "su" binary in system; by default exist file /system/phh/secure (for Google Certification PASS), so if you can boot AOSP GSI, but can't boot CAOS - try to removing that file
UPDATE VERSION
latest build: 2020.10.29
treble patches: v222+
SPL: 5 Oct 2020
File Downloads/Installation​THINGS THAT YOU NEED ON YOUR WINDOWS COMPUTER.​
Odin
Unzip the file. There is a EXE file in it. Double click it to launch. There will be a pop up, just press ok.
FILES THAT YOU NEED TO FLASH THE ROM.​The rom itself
Make sure you have 7-zip installed. Right click it and click extract files. Go into the unzipped folder and rename the file inside to "system.img"
TWRP Decrypter
Just leave this file as a zip. Don't unzip it.
ChonDoe Flasher
Just leave this file as a zip, Don't unzip it.
INSTALL RECOVERY AND UNLOCK BOOTLOADER (SKIP THIS PART IF YOU ALREADY HAVE TWRP.)​I have made a reddit post on twrp. DO NOT DO THE MAGISK PART.
FLASHING THE FILES​Go into TWRP. Press wipe and go into format data. Type in yes and wipe your data. Press the home button in your nav bar and go back into Wipe. Press advanced wipe, tick "data", "Dalvik / ART cache" and "Cache". Format it.
Press the home button in the nav bar again. Now, go into reboot and click recovery. Don't do anything. Once it's back into TWRP, plug your phone into the pc if you haven't already.
On your Windows PC, go into File Explorer, This PC, A515F and then internal storage. Take the "system.img" file and drag it into there. Do the same with "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip" and "ChonDoe_Flasher.zip"
Once all of them are copied, go onto your phone. Click install and you should see your files. If you don't, go into /sdcard. Flash "ChonDoe_Flasher.zip". Once it's done, flash "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip". Press "Reboot System" once "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip" is installed.
If this looks really confusing to you, there is a tutorial for this. However, it's for HavocOS. But everything is the same except the rom. But the steps are the same. Watch it here.​
Congrats! You have installed Caos!​
CONTACTS
> telegram group
> project page
KNOWN BUGS:
• excluding fixes, the same as on AOSP Quack (in some cases doesn't work: broadcasting on TV, calls via BT; offline charging does not work normally fingerprint doesnt work; problems with GPS etc etc)
NOTE: always test ROM first without Magisk (with clean boot ramdisk). and don't send me bug reports if you have:
a) Magisk installed​b) modified/custom vendor or kernel​c) dirty flashing rom without wiping data​
CREDITS
persons: @phhusson
projects: TrebleGSI • BlissROMs • crDroid • PixelExperience • ION • neon-OS • Havoc-OS • LineageOS • Evolution-X • LiquidRemix • ExtendedUI • GrapheneOS • abc rom

[GUIDE] Make microG work on Visible's Oneplus 8 (IN2015 Instantnoodle IN68CE)

Before following this guide, you'll want to grab the MSM unbricking tool, specifically for this device (not the global or other Oneplus 8 versions). Use it if you brick yourself.
Here's how I got microG to work on my Visible Oneplus 8 running Oxygen OS 11:
Unlock the boot loader and flash Lineage's instantnoodle recovery (The small recovery image ~96MB, not the large rom file)
Reboot into recovery and adb sideload the Magisk zip file, from the recovery's 'Apply Update'.
Follow this guide to enable signature spoofing, but with the following few changes:
Place this specialized hook services file ( 11-hook-services-OxygenOS.jar.dex ) in the same folder as 11-hook-services.jar.dex.
When you get to the `java -jar` command in the guide, do this instead:
Code:
java -jar dexpatcher-1.8.0-beta1.jar -a 11 -M -v -d -o ./ services.jar 11-hook-services-OxygenOS.jar.dex 11core-services.jar.dex
Do not install the microG provided in the guide! But go ahead and install your `spoof_AVDapi30.zip` through magisk as the guide says.
Confirm that signature spoofing is working (you can download Signature Spoofing Checker from F-droid)
Inside the magisk app, search for and install the plugin "microG installer Revived". Reboot.
Grant microG all the permisisons that you can in microG settings' Self-Check.
Tap and install GmsCore.apk located at '/system/priv-app/GmsCore/". You need to do this step even though its already installed because until you do this, it will only be installed as a system app. Doing this installs it as a user app, which fixes the location permission issue (somehow this issue is encountered). If it doesn't fix it right away you may need to reboot.
Open the microG settings again, and give yourself the location settings (and SMS if still needed)
I hope this helps someone. I know I had a lot of frustration because so much that works for other instantnoodles simply doesn't work on this device. Instantnoodle custom roms like lineageOS (as of writing this) and automated patchers like smali and nanodroid don't work, so at least we have this one option.
Ciao @Calebdvn
Trying to apply this fix on OP6 OOS11.1.2.2 but nothing happends
trying the standard method I were stuck at bootlogo, using this file the system volta, but, signature spoofing Is not working
Caould you kindly support me ?

Categories

Resources