{
"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
Related
{
"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 only for Huawei P9 (EVA)
Code:
OpenKirin presents unofficial TWRP for stock EMUI 5.x with decryption support.
Intended for usage on stock emui 5.x in combination with unlocked bootloader and
modded boot image with disabled dm-verity (depending on what you want to do).
Code:
[COLOR="red"][B]WARNING:[/B] since 3.1.0-2 update we've enabled image flashing to special partitions -
not just /recovery or /boot partition.
That means your device could be bricked in a few seconds if you do not pay attention
or don't know what you're doing. (Noobs please stay away out of this section!)[/COLOR]
Installation Instructions
Code:
1. Enter fastboot mode on unlocked device
2. flash recovery using the following command: fastboot flash recovery twrp-3.1.1-1-eva.img
3. reboot to recovery!
Rooting Methods
Code:
[B][U]1. Official SuperSU (not just 2.82+)[/U][/B]
1. Ensure you are running stock kernel from b380+
2. Tick the option "Keep vendor partition mounted" inside OpenKirin Settings
3. download and install [URL="www.supersu.com/download"]official SuperSU[/URL]
4. Enjoy!
[B][U]2. Custom SuperSU[/U][/B]
1. Make sure the device running stock EMUI 5.x boot.img
2. flash this modded SuperSU 2.79: [URL="https://drive.google.com/open?id=0BxWP2gF_0Bd_UmQ2Zm9ZRGxBTUE"]download here[/URL]
3. enjoy root :)
[COLOR="red"][B]NOTE:[/B][/COLOR] this is for every device (except kirin 960 based) running emui 5.x without loop support.
[B][U]3. Magisk[/U][/B]
1. ensure you are running a kernel from b380 or later
2. flash magisk
3. enjoy root & safetynet (read note)
[B][COLOR="red"]NOTE:[/COLOR][/B] Magisk Hide is a known problem on Huawei/Honor devices.
Make sure you are not rebooting/turning off your device with Magisk Hide enabled!
You may face a broken fingerprint scanner, do not worry,
simply disable magisk hide and reboot - fps works again!
Downloads
Code:
[LIST]
[URL="https://github.com/OpenKirin/android_device_huawei_eva/releases/download/3.1.1-1/twrp-3.1.1-1-eva.img"][U]download twrp-3.1.1-1-eva.img[/U][/URL]
[/LIST]
FAQ
Code:
Q: What's the code status?
A: 10. June 2017
Q: which P9 models are supported?
A: every model should be supported.
Q: Can i use this TWRP with decrypted /data?
yes, you can! (have a look at the instructions in FAQ)
Q: Can i install LOS or AOSP based roms with this TWRP?
yes, you can! (please follow the installing procedure in the corresponding rom thread)
Q: Can i install Magisk?
A: Every ROM based upon b380+ kernel should now include proper loop support.
Since 3.1.0-3 you are able to flash Magisk through TWRP (recovery kernel has been updated)
Q: Does official SuperSU work?
A: Yes, even though chainfire included a fix in his upcomming version,
you can use every version of it, just check the "Rooting Instructions" section.
Q: ETAs?
A: No.
Going back from decrypted -> encrypted?
Code:
1. Format /data inside of TWRP
2. Flash eRecovery & Kernel from your currently installed Stock ROM Build
3. Do a factory reset inside of eRecovery
5. Let device boot up
6. Install your current firmware hw_data package & SuperSU using TWRP again
Want to decrypt? No problem.
Code:
1. Format /data inside of TWRP
2. Flash a kernel with forceencrypt disabled
3. bootup your device
Special Thanks
Code:
* [URL="https://forum.xda-developers.com/member.php?u=2335078"]surdu_petru[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=7354786"]XePeleato[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=220328"]paulobrien[/URL]
XDA:DevDB Information
TWRP, Tool/Utility for the Huawei P9
Contributors
OldDroid, surdu_petru, XePeleato
Source Code: https://github.com/OpenKirin
Version Information
Status: Stable
Created 2017-03-01
Last Updated 2017-06-11
Changelog
Code:
[B]TWRP 3.1.1-0[/B]
* bump up TWRP version to 3.1.1
* fix backup of /version
* use device specific and updated prebuilts (+kernel)
* remove the ability to flash images to ext4 mounted partitions
[B]TWRP 3.1.0-3[/B]
* kernel updated for proper loop support
* magisk can now be installed and is supported by every rom running b380+ kernel (tested on b383)
* native_package.xml has been changed to device specific version
[B]TWRP 3.1.0-2[/B]
* Add support for NTFS formatted MicroSD cards or OTG drives
* Enabled direct image flashing to special partitions
(be careful when using it - one wrong klick means brick in a second!)
* TWRP is now compatible with AOSP based ROMS (LineageOS)
and decrypted Stock ROMS, transition from Stock to LOS is possible.
* Correct versioning - Device version is now comming from the common base.
* 3650-common: introduce init.recovery.hi3650.power.rc for better power handling
[B]TWRP 3.1.0-1[/B]
* proper handling of decryption (improves booting time by ~10 seconds)
* do not wipe /data/hw_init during /data wipe or factory reset to prevent system errors
* cleanup ramdisk, reduced image size by 10mb
[B]TWRP 3.1.0-0[/B]
* add the ability to format oem specific partitions
* add back f2fs support so we can format /data as f2fs
* bump up twrp version to 3.1.0
I have a p9 with b378 rooted and a working version of twrp (no data encryption), is it possible to install this thru my twrp?
frenzissi said:
I have a p9 with b378 rooted and a working version of twrp (no data encryption), is it possible to install this thru my twrp?
Click to expand...
Click to collapse
Yes, should be fine
Atarii said:
Yes, should be fine
Click to expand...
Click to collapse
I can confirm this works fine
Thanks
<<<by scaniathe>>>
Thank you for your effort. It installed flawless on my L19C432 with B378.
I tried to root it but it failed. Chainfire's latest zip rebooted my phone and phh's ended with error 1.
LE: I flashed @Atarii B378 img and now I am rooted. AdAway is working as expected. Thank you!
mihairimia said:
Thank you for your effort. It installed flawless on my L19C432 with B378.
I tried to root it but it failed. Chainfire's latest zip rebooted my phone and phh's ended with error 1.
Click to expand...
Click to collapse
You will still need to use my pre-rooted boot images, that's separate from TWRP. L19 is work in progress
mihairimia said:
Thank you for your effort. It installed flawless on my L19C432 with B378.
I tried to root it but it failed. Chainfire's latest zip rebooted my phone and phh's ended with error 1.
Click to expand...
Click to collapse
i will look into it today, could you link me the zip files you used for rooting? especially phhs version (supersu is not supported, thats why we removed it from the entire recovery ecosystem)
Regards
OldDroid said:
i will look into it today, could you link me the zip files you used for rooting? especially phhs version (supersu is not supported, thats why we removed it from the entire recovery ecosystem)
Regards
Click to expand...
Click to collapse
The one from here https://forum.xda-developers.com/p9/how-to/twrp-3-0-2-0-n-t3506947. Dont waste your time. Its working if B378 img from Atarii is flashed.
Atarii said:
You will still need to use my pre-rooted boot images, that's separate from TWRP. L19 is work in progress
Click to expand...
Click to collapse
L09 B378 img is ok for now. Still need to test if system apps uninstall. But I am happy Adaway is working!
Is somebody here to explain me (quick explain) what is encryption/decryption support?
And I never know... When I launch TWRP for the 1st time, we have to choose if we want to let the system untouched.
Must I let the system in "Read Only mode" or not? I don't understand what it can change (I didn't have to choose that on my previous (HTC) devices)...
Thanks.
Perfect!
Thanks
cbgti said:
Is somebody here to explain me (quick explain) what is encryption/decryption support?
And I never know... When I launch TWRP for the 1st time, we have to choose if we want to let the system untouched.
Must I let the system in "Read Only mode" or not? I don't understand what it can change (I didn't have to choose that on my previous (HTC) devices)...
Thanks.
Click to expand...
Click to collapse
Encryption/decryption support is related to the /data partition (where your user files are stored). The encryption scheme changed for Nougat, so this is the first TWRP that supports being able to read/write to that encrypted /data partition.
Read-only system mode (aka systemless mode) - some people do not touch the system partition, so they can later apply OTAs easier (as they perform a diff on system files)
good job OpenKirin team, thx a lot
So supersu from chainfire isn't working even on this, right?
@Atarii : Thanks!
After flashing ARISE Sound System dolby atmos (doesn't run) and viper (can't install driver) don't work Any solutions?
maliniaka said:
After flashing ARISE Sound System dolby atmos (doesn't run) and viper (can't install driver) don't work Any solutions?
Click to expand...
Click to collapse
Propably the script wont work on huawei, but we work on it.
will this TWRP work for the Honor 6x Nougat Beta too?
sassmann said:
will this TWRP work for the Honor 6x Nougat Beta too?
Click to expand...
Click to collapse
what does the title say, whats the name of the forum where this has been posted?
Hope this answers everything!
PS: Its comming soon for H6X.
{
"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"
}
For midoSupports all Roms (SHOULD)
NOTE:
Code:
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 Kernel
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 MultiRom?
MultiRom is one-of-a-kind multi-boot mod. It can boot any Android Rom as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our device. Besides booting from device's internal memory, MultiRom can boot from USB drive connected to the device via OTG cable. The main part of MultiRom is a boot manager, which appears every time your device starts and lets you choose ROM to boot. Roms are installed and managed via the modified TWRP recovery. You can use standard ZIP files to install secondary Android Roms, daily prebuilt image files to install Ubuntu Touch and MultiRom even has its own installer system, which can be used to ship other Linux-based systems.
I am not the developer of MultiRom. All Credits for it goes to Tasssadar, the actual developer of it.
Features:
MultiBoot any number of Android Roms
Restore Nandroid Backup as secondary ROM
Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting
Boot from USB drive Attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash Stock Rom zips again. Make backups. Always.
TESTED ON ROMS:
Test and Report
SUPPORTED DEVICES:
mido
Please Test it in other Similar SD Variants and Report it Below.
Bugs:
You tell me
SCREENSHOTS:
All Screenshots HERE
INSTALLATION INSTRUCTIONS:
Via The MultiRom Manager App:This is the easiest way to install everything MultiRom needs... Just follow the Below Instructions:
Install the app (Links Below)
Select MultiRom and Recovery on the Install/Update card.
Press "Install" on the Install/Update card to start the installation.
DONE! MULTIROM IS READY TO ROCK!
You current rom will not be erased by the installation.
Download link is in the second post.
Adding ROMs:
Android
Boot into MultiRom Recovery -> select MultiRom -> Add Rom -> Select the Rom's zip file and click Confirm.
Updating/changing ROMs:
1. Primary Rom (Internal)
Flash Rom's zip File as Usual, Do factory reset if needed (it won't erase secondary Roms)
Go to MultiRom in recovery and do Inject curr. boot sector.
2. Secondary Android Roms
If you want to change the Rom, delete it and add new one. To update the Rom, follow these steps:
Go to MultiRom -> List Roms and select the Rom you want to update.
Select "Flash zip" and Flash the Rom's zip File.
Explanation of recovery menus:
Main menu
- Add Rom - Add Rom to Boot
- List Roms - List Installed Roms and Manage Them
- Inject boot.img File - When you Download something, for example a Kernel, which is Distributed as a Whole boot.img (eg. Qassam Kernel), you have to use this option on it, otherwise you would lose MultiRom.
- Inject curr. boot sector - Use this option if MultiRom does not show up on boot, for example after Kernel Installation.
- Settings - Well, SETTINGS!
Manage Rom
- Rename, Delete - No Need to Explain this I Think!
- Flash Zip (Only Android Roms) - Flash zip to the Rom, for example GAPPS
- Add/Replace boot.img - Replaces boot.img used by this Rom, this is more like a Developer Option.
- Re-Patch init - This is available only for Ubuntu. Use it when Ubuntu cannot find the root partition, i.e. after apt-get upgrade which changed the init script.
GitHub Source Codes:
MultiRom Organization for Xiaomi Devicesmido MultiRom Device TreesMultiRom Manager App Source Codes
Current Status:
Test and Report...
CREDITS:
Rishabh Rao (ME) - For Porting MultiRom to kenzo/kate
Tasssadar - For his awesome MultiRom
nkk71 - For his No-KEXEC workaround
Version Information:
Status: Unofficial, IN TESTING, Version 33
ENJOY!:good:
XDA:DevDB Information
MultiRom For mido, Tool/Utility for the Xiaomi Redmi Note 4
Contributors
Rishabh Rao
Source Code: https://github.com/multirom-xiaomi
Version Information
Status: Testing
Current Beta Version: v33
Beta Release Date: 2017-03-29
Created 2017-03-29
Last Updated 2017-03-30
Download Links:
MultiRom Manager App 2.4-rishabhrao
1. Can I flash any Other Kernel?
- YES! You CAN flash ANY Kernel!!!
2. Can I Flash Roms to USB-OTG? How?
- Yes, You CAN Flash Roms to USB-OTG.
Follow these steps to do so:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on Add Rom.
4. Select the correct Location and Flash it...
Note: Flashing on a USB-OTG takes some Time, so be patient & Don't Worry!
3.Where to Find Roms Installed in my USB-OTG Drive? How to Boot into Them?
- After Flashing the Rom you will be Booted into the MultiRom Boot Menu.
All your Roms Flashed on the Internal Memory will be in Internal Tab.
All Others will be in the External Tab.
4. How to Rename/Remove/Delete/Wipe Dalvik Cache or Flash any Other zips to an Existing Rom?
- Follow these steps:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on the Rom which you want to Remove/Add zips.
You will find all the options you need there!
5. "Unable to Flash, I am getting Errors" / "Executing Updater Script Failed" / "Rom is not Booting". ANY HELP???
- Please Provide Logs. It will be located in /sdcard/multirom/error.txt OR if that's not present here: /proc/last_kmsg
It would be Great if you can Provide Some Screenshots.
Press Volume Down + Power Buttons Together to take Screenshots.
6. How to Disable Auto Boot / Change Rom Name / Hide Roms / Change Brightness of MultiRom Boot Menu?
- Follow these steps:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on the 3 Dots on the Top Right of the Screen.
4. Select Settings.
You will find all the Customizations of the MultiRom Boot Menu you need there!
7. What is the No-Kexec Workaround?
- The No-Kexec Workaround by @nkk71 allows you to use MultiROM without having to flash a Kexec Enabled Kernel.
Please read More about No-Kexec Workaround from the author words only (to avoid duplicity and to get the latest information), thanks to @nkk71 once again!
http://forum.xda-developers.com/showpost.php?p=68738134&postcount=4
Guys please test this in your mido and Please tell me how it works
How about the recovery? witch one we can use?
Question 1: what is to difference between multirom and dual boot?
Question 2: can I use miui as secondary ROM with aospe as first Rom?
Question 3: when will dual boot be available for rn4?
XMoDuLeSx said:
How about the recovery? witch one we can use?
Click to expand...
Click to collapse
It has it's own modified TWRP recovery
Sent from my LeEco Le 2 using XDA Labs
dragneelfps said:
Question 1: what is to difference between multirom and dual boot?
Question 2: can I use miui as secondary ROM with aospe as first Rom?
Question 3: when will dual boot be available for rn4?
Click to expand...
Click to collapse
1. MultiRom is a complete Multi Booting tool which has it's own Recovery, boot ui, etc.
2. Yeah i think so... You can.
3. Mido is rn4 only r8!
Also note that this is still in testing so please forgive me if you face any bugs. But it will be stable soon...
Sent from my LeEco Le 2 using XDA Labs
flashed miui 7.2.23 as second rom ..(aospe as first rom).
I open the app and try to boot into miui..it says No-Kexec kernel found and reboots to recovery.
---------- Post added at 01:50 PM ---------- Previous post was at 01:18 PM ----------
Now tried LOS as second rom. Couldnt even boot in my first rom. So deleted the second rom. Still couldnt boot in the first rom. (screen goes off after mi boot logo). Now restored the first rom nandroid backup. Working now.(first rom only).
dragneelfps said:
flashed miui 7.2.23 as second rom ..(aospe as first rom).
I open the app and try to boot into miui..it says No-Kexec kernel found and reboots to recovery.
---------- Post added at 01:50 PM ---------- Previous post was at 01:18 PM ----------
Now tried LOS as second rom. Couldnt even boot in my first rom. So deleted the second rom. Still couldnt boot in the first rom. (screen goes off after mi boot logo). Now restored the first rom nandroid backup. Working now.(first rom only).
Click to expand...
Click to collapse
I did the same thing and I'm having the same problem...
Only that I tried xenon HD instead of aospe
leo_pard2331 said:
I did the same thing and I'm having the same problem...
Only that I tried xenon HD instead of aospe
Click to expand...
Click to collapse
Let's see . op will fix the bug probably.
dragneelfps said:
Let's see . op will fix the bug probably.
Click to expand...
Click to collapse
I wiped everything and restored the backup and now I'm unable to install the multi rom
dragneelfps said:
flashed miui 7.2.23 as second rom ..(aospe as first rom).
I open the app and try to boot into miui..it says No-Kexec kernel found and reboots to recovery.
---------- Post added at 01:50 PM ---------- Previous post was at 01:18 PM ----------
Now tried LOS as second rom. Couldnt even boot in my first rom. So deleted the second rom. Still couldnt boot in the first rom. (screen goes off after mi boot logo). Now restored the first rom nandroid backup. Working now.(first rom only).
Click to expand...
Click to collapse
Hey u mentioned the screen goes off after mi boot logo
How much time did you wait after that happens?
Sent from my LeEco Le 2 using XDA Labs
leo_pard2331 said:
I wiped everything and restored the backup and now I'm unable to install the multi rom
Click to expand...
Click to collapse
What is happening when you try to install it?
Sent from my LeEco Le 2 using XDA Labs
dragneelfps said:
Let's see . op will fix the bug probably.
Click to expand...
Click to collapse
Definitely i will
Sent from my LeEco Le 2 using XDA Labs
Rishabh Rao said:
Hey u mentioned the screen goes off after mi boot logo
How much time did you wait after that happens?
Sent from my LeEco Le 2 using XDA Labs
Click to expand...
Click to collapse
actually 10-20 sec
Hey sir, Did u test this before posting in here? Do u own a mido? Just curious lol
Sarthak Narang said:
Hey sir, Did u test this before posting in here? Do u own a mido? Just curious lol
Click to expand...
Click to collapse
+1
Sarthak Narang said:
Hey sir, Did u test this before posting in here? Do u own a mido? Just curious lol
Click to expand...
Click to collapse
Hello Sarthak Sir
No i do not own a mido.
I approached in some TG, WhatsApp groups after i made this to get someone to test. But everyone got me to post it here
So i just posted it with the BIG Heading "TESTING".
Also just because I don't have this device, please don't think i will not fix this MultiRom.
I will work day and night to fix this lol:silly::fingers-crossed:
Now some guys at some TG group confirmed to me the following points:
1. MultiRom works through the app to dual boot.
2. Boot UI is messed up and needs fix. (Trying out different Pixel Formats now)
3. The Lockscreen and FP Bug exists just like some other devices like kenzo, s2, x2, etc. (Temporary fix: Disable your FP and Pattern before Installing any new Rom)
Now looking out for more testing and propably this thing will be ready to rock in a few days.
Sent from my LeEco Le 2 using XDA Labs
Edit: Just also added EXPERIMENTAL in the Title to show that this is just in the Alpha Stage till now
Rishabh Rao said:
Hello Sarthak Sir
No i do not own a mido.
I approached in some TG, WhatsApp groups after i made this to get someone to test. But everyone got me to post it here
So i just posted it with the BIG Heading "TESTING".
Also just because I don't have this device, please don't think i will not fix this MultiRom.
I will work day and night to fix this lol:silly::fingers-crossed:
Now some guys at some TG group confirmed to me the following points:
1. MultiRom works through the app to dual boot.
2. Boot UI is messed up and needs fix. (Trying out different Pixel Formats now)
3. The Lockscreen and FP Bug exists just like some other devices like kenzo, s2, x2, etc. (Temporary fix: Disable your FP and Pattern before Installing any new Rom)
Now looking out for more testing and propably this thing will be ready to rock in a few days.
Sent from my LeEco Le 2 using XDA Labs
Edit: Just also added EXPERIMENTAL in the Title to show that this is just in the Alpha Stage till now
Click to expand...
Click to collapse
Looking forward to it.
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
{
"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/
NOTE :
This build of TWRP is based on the kernel source code and no prebuilt kernel was used for building. Because, it is the first build, testers are very welcome for providing feedback regarding the build.
CHANGELOG (3.2.3.0) :
WHAT'S NEW?
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
CHANGELOG (3.3.0.0) :
WHAT'S NEW?
* Merge AOSP 9.0 r3 (Dees_Troy)
* Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)
* Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)
* vold decrypt updates (CaptainThrowback and nijel8)
* Support vibration on LED class devices (notsyncing)
* Metadata decrypt support for Pixel 3 (Dees_Troy)
* Support rotating the display via build flag (vladimiroltean)
* Reboot to EDL mode button (mauronofrio)
* Support MTP on FFS devices (bigbiff)
* Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
* Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
* Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
* TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
* Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
* Use magiskboot to allow repacking boot images for installing TWRP (Dees_Troy with thanks to topjohnwu of course)
* Also, there was a major bug with the previous build which prevented the flashing of any file because of the "digest-verification" has been fixed with this release. Enjoy!
CHANGELOG (3.3.1-0) :
WHAT'S NEW?
* 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
DOWNLOAD :
You can download the latest build of the TWRP from the official site here:
TWRP(Official)
BUGS:
Encryption (for MIUI)
INSTRUCTIONS :
Download the recovery image and place it in some folder on your desktop and open the Terminal/Command Prompt/Powershell in the said folder.
Connect your device to the PC and boot into the fastboot mode using H/W keys or by typing :
Code:
adb reboot bootloader
Now, type :
Code:
fastboot flash recovery twrp-3.3.0-0-violet.img
OR,
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
Download the recovery image from the link.
Reboot to TWRP.
Hit Install and tap the "Images..." button in the lower right
Browse to the location of the TWRP image on your device and select it.
Select recovery from the partition list and swipe to flash.
For users who are running MIUI :
Thanks to Snehashis Sarkar for a short tutorial.
Your data will get wiped before flashing the recovery so take a backup of the internal storage.
Reboot to fastboot.
Wipe the Userdata via fastboot.
Flash this recovery.
Boot into the recovery and format the data (just format it, don't go for the "advanced wipe" section .
Flash this image file: Patched fstab + vbmeta + thermal configs for better performance
Reboot and enjoy.
CREDITS:
TwrpBuilder for trees
Kernel Source :
Link: android_kernel_xiaomi_sm6150
XDA:DevDB Information
[RECOVERY][OFFICIAL][TWRP - 3.3.1-0][Xiaomi Redmi Note 7 PRO], Tool/Utility for the Xiaomi Redmi Note 7 Pro
Contributors
Doomsday101
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-05-11
Current Beta Version: 3.3.0-0
Beta Release Date: 2019-04-03
Created 2019-04-02
Last Updated 2019-05-23
Reserved
Not able to Boot.
1. Fastboot boot twrp_violet.img not working.. Phone reboots normally.
2. So booted TWRP manually (Volume Up + Power) And Phone stuck on TWRP Logo Screen.
See the attachments for more info.
Thank you for your build !
Do you know if someone started to work on porting ROMs ?
diamantik said:
Thank you for your build !
Do you know if someone started to work on porting ROM's ?
Click to expand...
Click to collapse
I don't know if someone is working on ROMs but it is likely because of the unreliable kernel source ATM by Xiaomeme.
Vatumb said:
Not able to Boot.
1. Fastboot boot twrp_violet.img not working.. Phone reboots normally.
2. So booted TWRP manually (Volume Up + Power) And Phone stuck on TWRP Logo Screen.
See the attachments for more info.
Click to expand...
Click to collapse
Can you send me the logcat of the kmsg file present in the /proc directory using adb shell when the twrp is stuck on bootlogo?
Doomsday101 said:
I don't know if someone is working on ROMs but it is likely because of the unreliable kernel source ATM by Xiaomeme.
Click to expand...
Click to collapse
Ok thank you
I had order my device , when i will receive it , i will try to help the community with what i can , i will be glad to test things , and develop them , hopefully we can get more devs , and together we can maintain the development for RN7 Pro alive
diamantik said:
Ok thank you
I had order my device , when i will receive it , i will try to help the community with what i can , i will be glad to test things , and develop them , hopefully we can get more devs , and together we can maintain the development for RN7 Pro alive
Click to expand...
Click to collapse
Sure thing ?
It will boot, try fastboot erase userdata, but you can't flash any ROM (MIUI) atm, as it has encryption bug, which needs to be fixed by the OP!
Vatumb said:
Not able to Boot.
1. Fastboot boot twrp_violet.img not working.. Phone reboots normally.
2. So booted TWRP manually (Volume Up + Power) And Phone stuck on TWRP Logo Screen.
See the attachments for more info.
Click to expand...
Click to collapse
Has anyone else tested this and does it seem to be working fine? I'm quite scared in flashing recoveries :/
---------- Post added at 09:28 PM ---------- Previous post was at 08:34 PM ----------
twrp's stuck on the twrp logo btw
moriyaprateek said:
Has anyone else tested this and does it seem to be working fine? I'm quite scared in flashing recoveries :/
---------- Post added at 09:28 PM ---------- Previous post was at 08:34 PM ----------
twrp's stuck on the twrp logo btw
Click to expand...
Click to collapse
The recovery has the encryption bug atm as stated by @talk2indrajit in the last post. So, you will have to erase userdata via fastboot first. I suggest you take a backup, get rid of Miui and continue with the said process and flash the newly built LOS16 by @Dyneteve (if you seek to flash a custom ROM).
Can anyone update the twrp to 3.0.3?
Not able to flash vbmeta.img fastboot mode..
Is any other way to flash vbmeta without fastboot mode because my platform tools fastboot not work gives error unknown fastboot command.. Please replay..
Aj51 said:
Is any other way to flash vbmeta without fastboot mode because my platform tools fastboot not work gives error unknown fastboot command.. Please replay..
Click to expand...
Click to collapse
Download latest adb from here
https://developer.android.com/studio/releases/platform-tools
When can it decrypt /data?
Vatumb said:
Not able to Boot.
1. Fastboot boot twrp_violet.img not working.. Phone reboots normally.
2. So booted TWRP manually (Volume Up + Power) And Phone stuck on TWRP Logo Screen.
See the attachments for more info.
Click to expand...
Click to collapse
Same problem happen with me
kishangupta009 said:
Same problem happen with me
Click to expand...
Click to collapse
Don't use this command, it was mentioned somewhere, it doesn't work for now, you need to flash it , fastboot flash recovery recname.img.
Guys this TWRP is not working , gets stuck at TWRP logo !
Try the another : https://forum.xda-developers.com/re...ficial-3-2-3-redmi-note-6-pro-violet-t3912400
ok, so here's an anecdote.
when i flashed it for the first time using fastboot command, i got it stuck on the logo as well. then i looked it up, and i found this vbmeta thing, which i don't really know what is. got it to flash using platform tools (vbmeta), then flashed the other twrp on this site, and booted into it. (went with the other twrp because that is what the youtube video was using as well, and i just wanted to get over the loop, didn't think to test out)
so, successfully booted into twrp(OTHER)
from there i had to flash the lineage vendor patch cuz can't load any roms (that i tried) without it. tried flashing rom and gapps, worked. this works, no problem. (maybe some of you might want to check if the vbmeta thing was required, or if you can straight flash the older twrp from commands.)
then i went back, wiped out stuff (cache,dalvik, system and data, NOT vendor) and i flashed twrp(THIS) using twrp(OTHER), just to see
got twrp(THIS) to boot successfully.
problem here now is that it spits an error on fkin digest verification for any rom. if i can't even flash a rom, i can't get beyond that. error being "digest verification failed" or something like that.
im tired of this twrp, someone should maybe test things out further, idk where to go from here. this just flat out doesn't work.
kuhru said:
ok, so here's an anecdote.
when i flashed it for the first time using fastboot command, i got it stuck on the logo as well. then i looked it up, and i found this vbmeta thing, which i don't really know what is. got it to flash using platform tools (vbmeta), then flashed the other twrp on this site, and booted into it. (went with the other twrp because that is what the youtube video was using as well, and i just wanted to get over the loop, didn't think to test out)
so, successfully booted into twrp(OTHER)
from there i had to flash the lineage vendor patch cuz can't load any roms (that i tried) without it. tried flashing rom and gapps, worked. this works, no problem. (maybe some of you might want to check if the vbmeta thing was required, or if you can straight flash the older twrp from commands.)
then i went back, wiped out stuff (cache,dalvik, system and data, NOT vendor) and i flashed twrp(THIS) using twrp(OTHER), just to see
got twrp(THIS) to boot successfully.
problem here now is that it spits an error on fkin digest verification for any rom. if i can't even flash a rom, i can't get beyond that. error being "digest verification failed" or something like that.
im tired of this twrp, someone should maybe test things out further, idk where to go from here. this just flat out doesn't work.
Click to expand...
Click to collapse
Thank you for trying it out previously. I have released a new build today with the latest TWRP version (3.3.0.0) and now the "digest-verification" bug has been fixed.
{
"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 is an open source, community project. A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like LineageOS or OmniROM.
Disclaimer
I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Rooting your phone may void warranty so don't root your device unless you know what you are doing.
Downloads
Latest for OneUi-3.1
TWRP (Official link)
vbmeta
Odin tool
First time Installation
Note: custom vbmeta needs to be flashed to disable the verification of custom mods, this is a one time flashing in stock firmware
Backup your data
Unlock the Bootloader, View thread
Reboot to Download mode [Check Key Combos Below]
Disable auto reboot in Odin options, Flash vbmeta.tar in AP slot using Odin tool
Reboot again to Download mode and now Flash twrp-[$version]-m30s.img.tar in AP slot using Odin tool
Boot into TWRP Recovery [Check Key Combos Below]
Decrypt Internal Storage - Flash DM-Verity ForceEncrypt disabler
Wipe -> Format Data
Reboot -> System(without root) | Recovery(with root)
Updating TWRP
Download the latest version of twrp-[$version]-m30s.img
Reboot to TWRP recovery -> Install -> Install Image & Select twrp-[$version]-m30s.img, choose recovery partition & swipe to flash
Reboot to Recovery
Patching TWRP with Magisk
Download the latest Magisk Manager here & Install
Download/Copy the TWRP image to your device
Press the Install button in the Magisk card
Make sure “Recovery Mode” is checked in options.
In most cases it should already be automatically checked.
Choose “Select and Patch a File” in method, and select the TWRP image
Magisk Manager will patch the image to [Internal Storage]/Download/magisk_patched.img.
Proceed with the above steps to flash Magisk Patched TWRP.
Key Combos
OneUi-3.0+ Requires usb connected to PC for getting into TWRP
Download Mode - Turn off device, Press and hold [vol + & vol -] connect usb to PC
Recovery Mode - Turn off device, Press and hold [vol + & Power] release power button after screen on, continue pressing [vol +]
Magisk System - Turn off device, Press and hold [vol + & Power] release both keys after screen on
TWRP->Reboot->Recovery to get into Magisk enabled System
Other Downloads
Mega
XDA:DevDB Information
TWRP 3.5.0, Tool/Utility for the Samsung Galaxy M30s
Contributors
santhoosh, thirdsty
Source Code: https://github.com/santhosh6194/android_kernel_samsung_m30s
DT: https://github.com/santhosh6194/android_device_samsung_m30s
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2020-01-15
Created 2020-01-14
Last Updated 2021-05-12
Changelogs:
Stable v2.0
- TWRP Official
- Added option to wipe vendor and product
- Supports GSI (MTP)
- Kernel tweaks
Stable v1.4
- Updated TWRP version to 3.4.0-0
- Based on latest BTG1 & BTF3 Sources
Stable v1.3
- Fixed reboot during backup
- Used Linaro GCC
- Made some changes to MTP
Stable v1.2
- Supports android 10 update
- Used latest BT6 sources
Stable v1.1
- Changes in MTP, more stable now
- Reverted Ext4 with f2fs on data partition
- Kernel changes
Stable v1
- Based on ASL2 firmware, do not flash on other firmware
- Fixed kernel panic during data wipe in twrp
- Fixed Random reboots occurred after magisk installation
Beta v03
- Fixed brightness slider
- Removed Selinux Always enforce
Beta v02
- Fixed color inversion
- F2FS changed to Ext4 for data partition in twrp
Beta v01
- Initial Builds
Note: This Twrp recovery works with custom kernel, changes to kernel that makes Twrp with magisk work without bugs.
Kernel Changes:
GPU drivers integrated with kernel
Added more cpu governors and i/o schedulers
Removed a bug which causes kernel panic
Removed Selinux always enforce
Thanks for the development brother....
Thank you so much, this was much needed
any chance of this one becoming Official????
sanctioned_k said:
any chance of this one becoming Official????
Click to expand...
Click to collapse
I'm not sure
I confirmed It worked on Galaxy M30s, Thanks @santhoosh for developing it, to boot system with magisk we must Reboot to RECOVERY, I think you need to edit it on the top page. I have created video for rooting it and proofing that it worked. Security protection worked with no issue.
redymedan said:
I confirmed It worked on Galaxy M30s, Thanks @santhoosh for developing it, to boot system with magisk we must Reboot to RECOVERY, I think you need to edit it on the top page. I have created video for rooting it and proofing that it worked. Security protection worked with no issue.
://youtu.be/knqWamnaeho
Click to expand...
Click to collapse
Thank you
redymedan said:
I confirmed It worked on Galaxy M30s, Thanks @santhoosh for developing it, to boot system with magisk we must Reboot to RECOVERY, I think you need to edit it on the top page. I have created video for rooting it and proofing that it worked. Security protection worked with no issue.
Click to expand...
Click to collapse
Thanks for the efforts !
On my way trying , but I'm on a SM-M3070(not 307F) , does this works ?
Thanks for the efforts !
On my way trying , but I'm on a SM-M3070(not 307F) , does this works ?
Click to expand...
Click to collapse
This TWRP is only for ASL2 Firmware, November update. You can try it.. if something goes wrong or failed, just flash the ROM to make it works again.. so i suggest you to download the firmware before root.. I can not answer it.. it works or not, I don't have the model number on my hand..
redymedan said:
This TWRP is only for ASL2 Firmware, November update. You can try it.. if something goes wrong or failed, just flash the ROM to make it works again.. so i suggest you to download the firmware before root.. I can not answer it.. it works or not, I don't have the model number on my hand..
Click to expand...
Click to collapse
Thanks !
Mine is M3070ZCU2ASL2 , looks still have a chance , wish a good luck to me (´・ω・｀).
EDIT : It works on M3070 !
Hi @santhoosh, could you porting this TWRP to Galaxy A50s. As we know M30s and A50s have same platform comes with Exynos 9611 and Android 9 Pie, thanks.
---------- Post added at 03:15 AM ---------- Previous post was at 03:13 AM ----------
lfk0000 said:
Thanks !
Mine is M3070ZCU2ASL2 , looks still have a chance , wish a good luck to me (´・ω・｀)
Click to expand...
Click to collapse
Let we know if it works on M3070, it will help other..
redymedan said:
Hi @santhoosh, could you porting this TWRP to Galaxy A50s. As we know M30s and A50s have same platform comes with Exynos 9611 and Android 9 Pie, thanks.
---------- Post added at 03:15 AM ---------- Previous post was at 03:13 AM ----------
Let we know if it works on M3070, it will help other..
Click to expand...
Click to collapse
I will try that later, I need to make sure this twrp is stable and bug free. So Porting it will be easy. Waiting for more users to try on it
I will try that later, I need to make sure this twrp is stable and bug free. So Porting it will be easy. Waiting for more users to try on it
Click to expand...
Click to collapse
Nice to hear that, let me know if you are ready to port it.. I will be the first to test it. About this TWRP I have used it from last night for daily activity until now there is no issue or bug.. and also I activated some security protection. Thank You
redymedan said:
Nice to hear that, let me know if you are ready to port it.. I will be the first to test it. About this TWRP I have used it from last night for daily activity until now there is no issue or bug.. and also I activated some security protection. Thank You
Click to expand...
Click to collapse
Which device you are using?
santhoosh said:
Which device you are using?
Click to expand...
Click to collapse
I have some devices M30s, A50, A50s, right now I used M30s for testing the TWRP
redymedan said:
Hi @santhoosh, could you porting this TWRP to Galaxy A50s. As we know M30s and A50s have same platform comes with Exynos 9611 and Android 9 Pie, thanks.
---------- Post added at 03:15 AM ---------- Previous post was at 03:13 AM ----------
Let we know if it works on M3070, it will help other..
Click to expand...
Click to collapse
It works , everything goes right as the tutorial , I have the magisk installed properly.
But I used the magisk manager to install the riru-core and EdXposed , after a reboot , the exposed didn't show up , at the same time the magisk has gone ( magisk manage says there is no magisk onboard ).
So I boot my phone to download mode and flash TWRP_ASL2_MagiskPatched.tar via odin agian , then to TWRP format data and flashing Disable_Dm-Verity_ForceEncrypt_01.15.2020.zip , but it does't work , there is still no magisk .
Any suggestion ?
EDIT : soveled ,by pressing "vol + & power " to power on , magisk shows up agian !!! Now working on installing xpsoed.
It works , everything goes right as the tutorial , I have the magisk installed properly.
But I used the magisk manager to install the riru-core and EdXposed , after a reboot , the exposed didn't show up , at the same time the magisk has gone ( magisk manage says there is no magisk onboard ).
So I boot my phone to download mode and flash TWRP_ASL2_MagiskPatched.tar via odin agian , then to TWRP format data and flashing Disable_Dm-Verity_ForceEncrypt_01.15.2020.zip , but it does't work , there is still no magisk .
Any suggestion ?
Click to expand...
Click to collapse
You must Reboot to recovery, if it does not work. You must start at the beginning by flashing the stock ROM, format data will not solve the problem.. I have experienced about that. for Xposed framework I will test it, it may be you missed a step..
lfk0000 said:
It works , everything goes right as the tutorial , I have the magisk installed properly.
But I used the magisk manager to install the riru-core and EdXposed , after a reboot , the exposed didn't show up , at the same time the magisk has gone ( magisk manage says there is no magisk onboard ).
So I boot my phone to download mode and flash TWRP_ASL2_MagiskPatched.tar via odin agian , then to TWRP format data and flashing Disable_Dm-Verity_ForceEncrypt_01.15.2020.zip , but it does't work , there is still no magisk .
Any suggestion ?
Click to expand...
Click to collapse
Everytime you reboot normally the system without magisk will be loaded, to enable magisk on boot 'turn off device, press and hold [vol + & power] release both keys when screen turns on. This will enable magisk on boot and this is how it works for devices like ours which have system as root. And edxposed I have tested it before having bootloop issues, it might or might not work