Because there are too many people ask about "how to decrypt data" and "how to re-encrypt data",
I write a guide to tell you how to decrypt/re-encrypt data partition.
[Change log for V2:]
1. Update script to no-verity-opt-encrypt-6.0.zip
2. Decryption support for Android Oreo and Android Nougat
[Why we need decrypt data partion?]
1. Install MultiRom/MultiBoot
2. Some Roms only work on decrypted device
3. For better performance
[Disadvantage]
1. Low security (Cracker can access your file, and remove lock screen pin from TWRP)
2. It need to wipe your data/internal storage to decrypt data partition.
Decrypt data partition with magisk:
1. Go to “Wipe” section, tap “Format Data”, and type “yes”
2. Transfer Rom and no_verity_op5_v2.zip to the device over MTP
3. Go to “Install” section, select ROM, and swipe to confirm the flash
4. Go to “Install” section, select magisk.zip, and swipe to confirm the flash
5. Go to “Install” section, select no_verity_op5_v2.zip, and swipe to confirm the flash
6. Reboot
PS. you should format data before flashing no_verity_op5.zip.
Re-Encrypt data partition:
1. Go to “Wipe” section, tap “Format Data”, and type “yes”
2. Transfer stock Oxygen Rom to the device over MTP
3. Go to “Install” section, select the Oxygen rom, and swipe to confirm the flash
4. Reboot
[Proof]
No magic here. What you see is real.
[How it work?]
OnePlus 5 uses FBE(File-Based Encryption) to encrypt data partition.
The latest no-verity-opt-encrypt zip ( https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ ) only replace "forceencrypt" to "encryptable".
It didn't replace "fileencryption", so your data partition is still encrypted.
In order to decrypt data partition, I modified the no-verity-opt-encrypt.zip by myself.
The no_verity_op5_v2.zip will replace "fileencryption" to "encryptable".
boot.img/ramdis/fstab.qcom
{
"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"
}
Mtp transfer means .. I tried after wiping format data I tried to transfer the required file by using my laptop with original data cable , but data transfer is showing but not transferring actually waited a long .. but no transfer happens ..
aneeshmbabu said:
Mtp transfer means .. I tried after wiping format data I tried to transfer the required file by using my laptop with original data cable , but data transfer is showing but not transferring actually waited a long .. but no transfer happens ..
Click to expand...
Click to collapse
You need reboot recovery, before you use MTP.
In order to use MTP, you need remount your data partition.
snowwolf725 said:
You need reboot recovery, before you use MTP.
In order to use MTP, you need remount your data partition.
Click to expand...
Click to collapse
Hi thanks for the replay , presently i flashed twrp and magisk also I'm in Franco custom kernel , so can i possible to decrypt data,
I'm very new in one plus 5 , coming from Motorola phones , so kindly give me a step wise process for a beginner .. thanks in advance ..
Does no_verity_op5.zip still work after system update?
sinnbro said:
Does no_verity_op5.zip still work after system update?
Click to expand...
Click to collapse
No, you need re-flash it after system update.
Because system update will replace boot with stock version.
If you forget to re-flash zip file, your device will unable to boot.
snowwolf725 said:
[Why we need decrypt data partion?]
4. For better performance
Click to expand...
Click to collapse
Does someone know what "better performances" means ?
I decrypted my OP3 but honestly I didn't noticed any change in performances (except opening TWRP)...
According to this process, can I also decrypt the stock rom?
snowwolf725 said:
No, you need re-flash it after system update.
Because system update will replace boot with stock version.
If you forget to re-flash zip file, your device will unable to boot.
Click to expand...
Click to collapse
Thanks
snowwolf725 said:
No, you need re-flash it after system update.
Because system update will replace boot with stock version.
If you forget to re-flash zip file, your device will unable to boot.
Click to expand...
Click to collapse
Or worse, the device will boot fine and proceed to encrypt your drive...
Why is magisk required?
ChavitoArg said:
Why is magisk required?
Click to expand...
Click to collapse
You don't need to flash magisk, if you don't want it.
Fif_ said:
Or worse, the device will boot fine and proceed to encrypt your drive...
Click to expand...
Click to collapse
Yes, you are right.
It will also encrypt your device.
So in order to remain unencrypted i have to flash this after a custom kernel, dont they include this feature already? Sorry for the questions, but im new to this device.
ChavitoArg said:
So in order to remain unencrypted i have to flash this after a custom kernel, dont they include this feature already? Sorry for the questions, but im new to this device.
Click to expand...
Click to collapse
Yes, you have to flash it every time you write the boot partition: flash a ROM or OTA.
Note that if you use Magisk, Magisk by default automatically turns off DM Verity and force encrypt, so there's no need to flash both no_verity_op5.zip and Magisk, just Magisk is fine.
snowwolf725 said:
[Why we need decrypt data partion?]
...
4. For better performance
Click to expand...
Click to collapse
Really ?
I have a few questions for the sake of clarity, as an experience I had makes me question if Magisk handles this. Blu_spark kernel will not boot when flashed with Magisk on my decrypted, stock OOS device - I believe status of encrypted/decrypted and FBE are two separate things based on the reply from eng.stk. it seems to use that kernel while decrypted, I still need to flash no-verity zip, even with Magisk.
This thread states both that you don't need to flash this if using Magisk, but that you need to flash this anytime you modify boot IMG - ROM flash, OTA, etc. I'm trying to nail down when I need this zip and when I don't - very curious if there's some solid info on when to use this in flashing and when not to. Guide is great as is for decrypting - just wanna stay that way.
@wrongway213
Hi,
maybe this will help you: https://forum.xda-developers.com/showpost.php?p=73311252&postcount=114
is decryption needed for xposed as official release has come out?
Sent from my OnePlus5 using XDA Labs
HonPig said:
is decryption needed for xposed as official release has come out?
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
No, new version of xposed supports encrypted data partition.
Which twrp is recommended for decrypt device?
Related
Unofficial release -TWRP recovery for the Galaxy A8 - SM-A810F/DS, Exynos 7420
{
"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.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
Update 17/4/2017
TWRP 3.1.0-1 MM build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
NOTE: To flash the modem, first it needs to be renamed to modem.bin.img
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.
How we got here: https://forum.xda-developers.com/sa...w-time-to-getting-support-a8-2016-sm-t3511148
Instructions:
Flash with ODIN 3.10.7.
Put your device in DOWNLOAD mode.
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 + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.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: twrp_3.1.0-1_sm-a810f_17417
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage:
(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
Credits: Me, Teamwin, my testers(majinawaz, RootAgain)
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Awesome work dear if i able to buy a beer for you i must buy it
First, thanks boss @ashyx for great work. If you remember, I was first who asked yoi for twrp for this good phone. In meantime I bought it, and you make twrp. I tried it immediately and got this results :
Maybe it is important that I first done ota to newest offered AQA1 update.
Than odin flash twrp. All ok. Reboot to it and format data from wipe menu.
Hot error cant mount pcifs (maybe different name, I forgot, I can see again sorry).
Then flash supersu and patch and got same error, pcifs?
Root is working perfect but mount not. I back in twrp and see mount, it sees data. But tried some twrp install zip and got same error. And no app.
So obviously it is not mounted good...
Is there solution?
Thanks biggest
ivanox1972 said:
First, thanks boss @ashyx for great work. If you remember, I was first who asked yoi for twrp for this good phone. In meantime I bought it, and you make twrp. I tried it immediately and got this results :
Maybe it is important that I first done ota to newest offered AQA1 update.
Than odin flash twrp. All ok. Reboot to it and format data from wipe menu.
Hot error cant mount pcifs (maybe different name, I forgot, I can see again sorry).
Then flash supersu and patch and got same error, pcifs?
Root is working perfect but mount not. I back in twrp and see mount, it sees data. But tried some twrp install zip and got same error. And no app.
So obviously it is not mounted good...
Is there solution?
Thanks biggest
Click to expand...
Click to collapse
Post the recovery log file, so I can take a look.
How boss and which to do and to send result of it?
ivanox1972 said:
how boss and which to do and to send result of it?
Click to expand...
Click to collapse
twrp > advanced > save log
@ashyx boss strange thing, it seems it works with this error message? Look picture. I boot to twrp, data mounted, give classic backup job.
It did system and data and boot and on end message
Failed to mount cpefs.
Maybe actually it works, with this dummy message?
ivanox1972 said:
@ashyx boss strange thing, it seems it works with this error message? Look picture. I boot to twrp, data mounted, give classic backup job.
It did system and data and boot and on end message
Failed to mount cpefs.
Maybe actually it works, with this dummy message?
Click to expand...
Click to collapse
It's a protected partition so it can't mount. I should just remove it from the fstab.
You can just ignore it.
Thanks boss, so this is 100,% functional terp I can totally believe in backups and everything else?
ivanox1972 said:
Thanks boss, so this is 100,% functional terp I can totally believe in backups and everything else?
Click to expand...
Click to collapse
I don't see why not, the main partitions are able to be backed up.
After phone user Super burn recovery and their code is the code?
I could not do it. Do you have a video? Mount data failed
Awesome work
@ashyx Hi buddy, adb doesnt seems to work in twrp
AL_IRAQI said:
@ashyx Hi buddy, adb doesnt seems to work in twrp
Click to expand...
Click to collapse
Disable MTP in TWRP.
ashyx said:
Disable MTP in TWRP.
Click to expand...
Click to collapse
i already did that, it says device offline
BTW
did you think about pushing tree to official ?
AL_IRAQI said:
i already did that, it says device offline
BTW
did you think about pushing tree to official ?
Click to expand...
Click to collapse
I'd suggest installing the ADB drivers whilst in recovery mode.
Check device manager has detected it as an ADB device.
Hello ashyx adb is not working and shows adb device offline any solution please
[email protected] said:
Hello ashyx adb is not working and shows adb device offline any solution please
Click to expand...
Click to collapse
Disable MTP in TWRP first.
Thanks for your reply i will try it and reply you soon bro
{
"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 Honor 8 Pro (DUK)
Code:
OpenKirin presents unofficial TWRP for stock EMUI 5.x.
Intended for usage on stock emui 5.x in combination with unlocked bootloader .
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-duk.img
3. reboot to recovery!
Rooting Methods
Code:
[B][U]1. Official PHH Superuser Beta 310[/U][/B]
1. download and flash [URL="http://superuser.phh.me/superuser-r310-beta.zip"]official PHH Superuser Beta 310[/URL]
2. install "Phh Superuser" from Google Play
3. Enjoy!
Downloads
Code:
[LIST]
[URL="https://github.com/OpenKirin/android_device_honor_duk/releases/download/3.1.1-1/twrp-3.1.1-1-duk.img"][U]download twrp-3.1.1-1-duk.img[/U][/URL]
[/LIST]
FAQ
Code:
Q: What's the code status?
A: 25. June 2017
Q: which H8 Pro models are supported?
A: every model should be supported.
Q: Can i use this TWRP with decrypted /data?
A: Yes you can! (Check FAQ)
Q: Can i install Magisk?
A: No (encrypted /data), Yes (decrypted /data)
Q: Does official SuperSU work?
A: No (encrypted /data), Yes (decrypted /data)
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 fileencryption disabled in fstab
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]
XDA:DevDB Information
TWRP, Tool/Utility for the Honor 8 Pro
Contributors
OldDroid, surdu_petru, XePeleato
Source Code: https://github.com/OpenKirin/android_device_honor_duk
Version Information
Status: Beta
Created 2017-06-23
Last Updated 2017-06-25
Reserved
Changelog
Code:
[B]TWRP 3.1.1-1[/B]
* fix twrp on emmc based devices
Man that was fast. Will definitely flash this after I get my H8 Pro.
Sent from my Honor 8 using XDA Labs
Hello,
I tested the package, unfortunately after the flash and first boot impossible to return under android.
If I remember correctly there was a problem of mount point.
To get out I had to flasher the recovery and system partitions of the original rom.
Having to reset my phone I have no log, but if you need anything else do not hesitate.
@ +
Via google translate
blattes86 said:
Hello,
I tested the package, unfortunately after the flash and first boot impossible to return under android.
If I remember correctly there was a problem of mount point.
To get out I had to flasher the recovery and system partitions of the original rom.
Having to reset my phone I have no log, but if you need anything else do not hesitate.
@ +
Via google translate
Click to expand...
Click to collapse
this should work for every h8 pro utilizing emmc storage:
https://drive.google.com/open?id=0BxWP2gF_0Bd_OHBPWDctZmJCanc
It has been tested.
Regards
Can we use Magisk instead? Or the loop issue back in Honor 8 is also here?
OldDroid said:
this should work for every h8 pro utilizing emmc storage:
It has been tested.
Regards
Click to expand...
Click to collapse
I flashed it, it works fine.
Thanks
adriansticoid said:
Can we use Magisk instead? Or the loop issue back in Honor 8 is also here?
Click to expand...
Click to collapse
Magisk 13 works fine.
Just flashed the Magist beta and installed the Magisch Manager 5.
-=MoRpH=- said:
Magisk 13 works fine.
Just flashed the Magist beta and installed the Magisch Manager 5.
Click to expand...
Click to collapse
That's great news. Thanks for confirming. :highfive:
Sent from my Honor 8 using XDA Labs
I flashed emmc version and supersu. For going in twrp I've to clic in the middle of the volume button and the power on.
Interesting, i tried to install it but i'm stuck with installion...i know how to enter fastboot mode with phone plugged to my computer with android sdk on, but the adb files look to be missing when i check with cmd...
Can anyone here give a quick tutorial ? Thanks
New Version (3.1.1-1) available - You can find more infos in OP.
This release fixes partition mounting on emmc 5.1 based devices
Source code is now also up and can be built!
https://github.com/OpenKirin/android_device_honor_duk
Regards
Wow that was faster than I could learn to do it.
Great job. May I ask how you got the important informations to build this?
Did you inject su into the image to gain root and then read all the detailed data through terminal or adb or root file explorer?
Just asking cause i train my brain more and more in my spare time and want to get behind the knowledge base to learn. :good:
First of all thank you for your work, I got the Recovery, root, Magisk, etc. running.
I have 2 Questions:
1. the internal storage when I boot to the recovery looks like enrypted (lots of random named folders). Is it possible to decrypt it for now, since there is currently no custom kernel available?
2. Can I flash the Firmware update to 130b in TWRP? If yes, wich package do I need to choose?
Cheers
Would this work on the Chinese V9 variant?
smouker said:
First of all thank you for your work, I got the Recovery, root, Magisk, etc. running.
I have 2 Questions:
1. the internal storage when I boot to the recovery looks like enrypted (lots of random named folders). Is it possible to decrypt it for now, since there is currently no custom kernel available?
2. Can I flash the Firmware update to 130b in TWRP? If yes, wich package do IP need to choose?
Cheers
Click to expand...
Click to collapse
Format the whole internal storage to remove encryption.
adriansticoid said:
Format the whole internal storage to remove encryption.
Click to expand...
Click to collapse
can I restore Data via TWRP without problems?
adriansticoid said:
Format the whole internal storage to remove encryption.
Click to expand...
Click to collapse
After testing, formatting the whole internal storage does not work.
To restart the partition is new encrypt
smouker said:
can I restore Data via TWRP without problems?
Click to expand...
Click to collapse
Yes it should work. Just make sure that both backup and restore destinations are either both encrypted or both decrypted.
blattes86 said:
After testing, formatting the whole internal storage does not work.
To restart the partition is new encrypt
Click to expand...
Click to collapse
What do you mean to restart the partition is new encrypt?
adriansticoid said:
Yes it should work. Just make sure that both backup and restore destinations are either both encrypted or both decrypted.
What do you mean to restart the partition is new encrypt?
Click to expand...
Click to collapse
sorry for my bad english.
After restart the phone...
TWRP 3.2.1_r12 Moto Z2 Play (albus)
{
"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 changelog : Here
Working/Bugs : Need to press power button two times for touch to work
Please do read the installation guide note !
IMPORTANT NOTE :
1. At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
2. Encryption is enabled by default
3. If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Installation Guide :
1. Make sure you have unlocked bootloader
2. Reboot to bootloader
3. fastboot flash recovery twrp-xxxx.img (if you want permanent flash) or
fastboot boot twrp-xxxx.img (if you want temporary boot)
Download Link :Here
Tree : Here
XDA:DevDB Information
TWRP-ALBUS, Tool/Utility for the Moto Z2 Play
Contributors
rahulsnair
Source Code: https://github.com/TeamWin
Version Information
Status: Beta
Created 2018-01-03
Last Updated 2018-02-03
I've been using this today to set up my phone fresh. I created a backup, installed stock twrp flashable rom, installed magisk, and magisk module zips all just fine.
Thanks for this.
Trying to set up my new Moto Z2 Play today.
I just unlocked the bootloader, so I'm good there. I wanted to install Magisk and leave it mostly stock. If I was going to just "fastboot boot twrp.img'' (instead of flashing) can I use this TWRP or should I just follow the instructions and use the TWRP version in this other thread?
Is this version more functional?
Would I be able to make a backup if I boot the TWRP instead of flashing?
Can I use the SD Card/internal storage with this version or do I have to still use the OTG cable and a flash drive to hold the DM Verity and Magisk ZIPs?
Hi,
I tried several times to backup my StockROM before modification, but TWRP always stuck at "Updating Partition Details". Any ideas what to do to solve this Problem? By the way, I just booted into TWRP, didn't flash it to my device. Thx
JRapsky said:
Hi,
I tried several times to backup my StockROM before modification, but TWRP always stuck at "Updating Partition Details". Any ideas what to do to solve this Problem? By the way, I just booted into TWRP, didn't flash it to my device. Thx
Click to expand...
Click to collapse
my experience is, you have to flash TWRP.
I don't think it has the necessary read/write permissions to do a full backup otherwise.
3.1.2_r18 version released. Check download link in OP
hi guys.
I successed to twrp temporary boot.
Successed to full backup (with all check).
Is it safe for permanent flash twrp right now?
p/s: After backup success, I reboot my phone and check TWRP folder but nothing here
so why?
fastboot boot twrp-xxxx.img
freeze at teamwin logo
O flash twrp and its ok
rodacoregio said:
fastboot boot twrp-xxxx.img
freeze at teamwin logo
Click to expand...
Click to collapse
Twrp temporary boot works fine for me.
Some guys said install it can fix your problem.
I'm trying to flash, but it show me
(bootloader) Image not signed or corrupt
But Temporary boot works fine, how do I fix that.
Bootloader was unlocked.
On restarting, it show me BAD KEY. is it normal?
Mark2014 said:
I'm trying to flash, but it show me
(bootloader) Image not signed or corrupt
Temporary boot works fine, how do I fix that.
Bootloader was unlocked.
On restarting, it show me BAD KEY. is it normal?
Click to expand...
Click to collapse
That's normal,
TWRP isn't 'signed' by MOTOROLA.
Just reboot and enjoy.
kewlzter said:
That's normal,
TWRP isn't 'signed' by MOTOROLA.
Just reboot and enjoy.
Click to expand...
Click to collapse
It show me No command when i reboot to recovery mode by command
adb reboot recovery
was I wrong somethings ?
OS's still boot fine.
Mark2014 said:
It show me No command when i reboot to recovery mode.
was I wrong somethings ?
Click to expand...
Click to collapse
Flash TWRP again. it didn't take.
I flashed it three times in a row.
that "no command" with Robot, is the stock recovery.
kewlzter said:
Flash TWRP again. it didn't take.
I flashed it three times in a row.
that "no command" with Robot, is the stock recovery.
Click to expand...
Click to collapse
tks. it works.
I trying format Internal Memory: TWRP ->Wipe Memory -> Format Data; write "yes"
, but its show Failed
Àfter that, I check Internal Memory and it's empty.
I want to flash [ROM][UNOFFICIAL][64Bit][11-Mar]LineageOS-15.1[Albus][Moto Z2 Play]
in https://forum.xda-developers.com/z2-play/development/rom-lineageos-15-1-t3731228
Now can I continues flash that ROM copied in SD card?
Mark2014 said:
tks. it works.
I trying flash Internal Memory: TWRP ->Wipe Memory -> Format Data; write "yes"
, but its show Failed
Àfter that, I check Internal Memory and it's empty.
I want to flash [ROM][UNOFFICIAL][64Bit][11-Mar]LineageOS-15.1[Albus][Moto Z2 Play]
in https://forum.xda-developers.com/z2-play/development/rom-lineageos-15-1-t3731228
Now can I continues flash that ROM in SD card?
Click to expand...
Click to collapse
Did you do a FULL backup including your EFS?
IF so try it and see, I haven't tried the Lineage build yet, still too many bugs.
but so long as you backup you shouldn't be afraid to explore.
kewlzter said:
Did you do a FULL backup including your EFS?
IF so try it and see, I haven't tried the Lineage build yet, still too many bugs.
but so long as you backup you shouldn't be afraid to explore.
Click to expand...
Click to collapse
Tks. I did a full backup .
tks again.
I will try now.
I make a full backup, so can I restore that backup file after LineageOS?
This works when go command fastboot boot .... ?
I'm having an issue... I've successfully flashed r18, but it cannot seem to mount the data partition. It fails to mount (just hangs for a moment when you check the box next to data), fails to wipe (Could not mount/data and unable to find crypto footer... Failed to mount '/data' (Invalid argument)).
Never mind... I just tried it a 3rd time and it worked. Not sure what's going on there.
**OK** Now, I've flashed the Unofficial LOS and OpenGapps from the thread by OP, following all instructions, and the phone boots to recovery every time I try to boot to system...
Recent success, z2 Play XT1710-06
Just to add to the success stories: A newly-purchased Moto z2 Play, variant XT1710-06 dual SIM, Android 7.1.1, RETLA release channel, build NPSS26.118-19-1-6. My object was to install root only, not (at this time) do any custom ROM flashes.
With this in mind: I used TWRP-3.2.1-0(Albus) after doing the initial bootloader unlock. Quirks noted during install was that I needed to repeat the 'fastboot flash recovery' option 3-4 times to get TWRP to stay put in the 'recovery' partition. Also, as an experiment, I tried renaming the TWRP image to 'recovery.img' (which seems to help).
Once TWRP was in place, I downloaded and installed the most current Magisk (v16). It worked perfectly, the first time, no issues at all (and it even knew to install its management app on its own). Despite my initial leanings, I chose not to try SuperSU due mainly to the developer changes at Chainfire HD (original developer retired, product bought up by some unnamed Chinese group).
Now I get to reinstall all my apps... (sigh). Such is the price of getting the phone we Really Want...
I hope this makes life easier for others.
Keep the peace(es).
{
"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"
}
DUAL BOOT PATCHER
DualBootPatcher is an open-source app that allows multiple ROMs to be installed on a single Android device. It does its best to work with existing code and does not require explicit support from ROMs. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary.
Warning: This method requires one time factory reset.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_data-slot.zip file will be created. For example,
Lineage-14.1-oxygen.zip
After patching would create a new
Lineage-14.1-oxygen_data-slot.zip
If you want to root secondary rom, then download Magisk 12.zip given below(Do not use other version, you can update that later from magisk manager app) and patch it like you did with rom
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher.apk from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Secondary: Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
Now Let's Start
1) Boot into recovery
2) Make a backup of /system /data /boot on SD Card (it's important to make it on sd card!)
3) Wipe internal storage (it will erase all of your data including photos, music etc on internal storage. So make sure you moved them or made their backup)
4) Restore your backup and boot to your ROM
5) Install Dual Boot Patcher.
6) Install patched rom as secondary on /system or on /data partition - it's your choice. There is lot of space for 3 roms in /system.
If you want to root secondary ROM and flash patched magiskv12.
7) Select your secondary ROM in ROM list and reboot.
Steps to be followed on Secondary Rom
8) Install Dual Boot Patcher.
9) Install MagiskManager.apk (see attachment)
10) Open Magisk Manager
11) Go to Modules-> press "+" button -> search for Magisk_v15.3.zip -> hold your finger on it -> press "Open". Wait for installation end. Now press close button. Don't restart
12) Open Dual Boot Patcher -> confirm for change current kernel
13) Reboot and voila! You have fully working secondary ROM with Magisk!
FAQ's (FAQ)
Do I need to wipe again for third or next rom?
No, wiping is only required for one time, you can flash as many roms(your device can handle) after that.
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Note:
You must always select 'Data-slots' as installation location for secondary roms on Redmi Note 4x. You can also use 'Extsd-slots' if you want to install on external storage.
If your using MIUI (Multirom, Xiaomi.eu, etc), you may need to enable documents app by going to Settings> Installed Apps before trying to patch any file in DBP.
Don't use official MIUI as primary rom.
If you're not able to boot, your phone vibrates 5 times and then reboot to TWRP after installing secondary rom, it might be that your data partition is encrypted. To fix this follow the instructions below:
First backup all your data including Internal Storage, then boot to TWRP>WIPE>FORMAT DATA then type 'yes' and tap enter. Now reboot and retry DBP.
Source/Credits:
https://dbp.noobdev.io
@chenxiaolong
@bad_request (Thanks for the XDA Post And Guide)
@mario_R (For step by step guide and errors.)
Downloads: https://dbp.noobdev.io/downloads/ and Download latest files
~ Hit Thanks button below if I helped you ~
*Reserved
**Reserved
Already flashed LOS 14.1 and RR as secondary in data slot everything work fine only issue is audio headphone jack not working otherwise cool.
drmuruga said:
Already flashed LOS 14.1 and RR as secondary in data slot everything work fine only issue is audio headphone jack not working otherwise cool.
Click to expand...
Click to collapse
...which is an issue pertaining to the RR custom rom and has nothing to do with this multi boot tool
I just tried last 5 days. When I choose second rom and reboot, it goes into recovery. Can't boot up second rom. Renew primary rom,wipe data and try dbp again and again. But not successed. Now my primary rom is Los 14.1 and trying second rom as miui global dev rom 8.1.11. Please help me.
jbmc83 said:
...which is an issue pertaining to the RR custom rom and has nothing to do with this multi boot tool
Click to expand...
Click to collapse
Yes , this tool working great , my problem is known to roms .
Patch roms and files in data slot not secondary slot in which is only one room can boot as secondary. Data slot for multiple roms flashing. And I never update ramdisk which leads to boot into recovery instead of system .
What's the use of dualboot we have only two ROMs to download.. Lol!
Now we should have at least two stable roms to taste this
nikz106 said:
What's the use of dualboot we have only two ROMs to download.. Lol!
Click to expand...
Click to collapse
not quite correct ^^
we have:
miui stable
miui developer
xiaomi.eu
miui pro
miui globe
lineage os 14.1
resurrection remix
so you could try a total of SEVEN different roms with this tool!
jbmc83 said:
not quite correct ^^
we have:
miui stable
miui developer
xiaomi.eu
miui pro
miui globe
lineage os 14.1
resurrection remix
so you could try a total of SEVEN different roms with this tool!
Click to expand...
Click to collapse
+1 to this.
Mgphyo126 said:
I just tried last 5 days. When I choose second rom and reboot, it goes into recovery. Can't boot up second rom. Renew primary rom,wipe data and try dbp again and again. But not successed. Now my primary rom is Los 14.1 and trying second rom as miui global dev rom 8.1.11. Please help me.
Click to expand...
Click to collapse
Anyone?
mario_R said:
Anyone?
Click to expand...
Click to collapse
Twrp >> wipe >> format data..
And it's ok now. ??
when patching the primary rom (update ramdisk)it reboots to recovery after the vibrations
didn't install any secondery roms -- yet
primary : MIUI globeROM 7.12.21
app version : 9.3.0.r327.gb3914310-snapshot
if it's relevant > i have magisk 15.3 --magisk edits the boot.img > may the issue be related to that ? was i supposed to remove magisk before? magisk in not the problem > i tried with original boot,img with supersu
edit : also i remember formatting the data before flashing this rom .. wil i have to reformat ?! >>>>> seems that miui encrypts the data with every flash !!
edit 2: i skipped ramdisk update for the primary rom and flashed a secondery rom in /system -- so .. is it the format issue ? if i format now will i have to reformat everytime i flash a rom ?? bcoz i clearly remember formatting before installing this primary rom
edit3 : problem solved with formating data again !!
DON'T set lock screen !!
you will end up locked away from your primary rom
----------
in my case the primary was globerom and secondary was lineage os
---------
if you already locked from your rom you can boot twrp and open terminal and write
cd data/system
rm *.key
and reboot
kalawy said:
when patching the primary rom (update ramdisk)it reboots to recovery after the vibrations
didn't install any secondery roms -- yet
primary : MIUI globeROM 7.12.21
app version : 9.3.0.r327.gb3914310-snapshot
if it's relevant > i have magisk 15.3 --magisk edits the boot.img > may the issue be related to that ? was i supposed to remove magisk before? magisk in not the problem > i tried with original boot,img with supersu
edit : also i remember formatting the data before flashing this rom .. wil i have to reformat ?! >>>>> seems that miui encrypts the data with every flash !!
edit 2: i skipped ramdisk update for the primary rom and flashed a secondery rom in /system -- so .. is it the format issue ? if i format now will i have to reformat everytime i flash a rom ?? bcoz i clearly remember formatting before installing this primary rom
edit3 : problem solved with formating data again !!
Click to expand...
Click to collapse
Good that you solved it. But for your knowledge and to any user: updating RAMDISK is not necessary. It's necessary only for "App sharing" feature, but I don't recommend it because it causes sometimes bootloops on secondary ROM. Even even creator of DualBoot patcher said it may be unstable.
Kapil Tapsi said:
If you want to root secondary rom, then download latest magisk and patch it like you did with rom
Click to expand...
Click to collapse
Thanks for mention me in your thread, but remove that line, it will cause bootloop. First you need to patch Magisk_v12.zip and install it, then install latest Magisk_v15.3.zip as a module in MagiskManager. Like I wrote in my guide
mario_R said:
Good that you solved it. But for your knowledge and to any user: updating RAMDISK is not necessary. It's necessary only for "App sharing" feature, but I don't recommend it because it causes sometimes bootloops on secondary ROM. Even even creator of DualBoot patcher said it may be unstable.
Click to expand...
Click to collapse
I figured that out ... the hard way :crying:
mario_R said:
Good that you solved it. But for your knowledge and to any user: updating RAMDISK is not necessary. It's necessary only for "App sharing" feature, but I don't recommend it because it causes sometimes bootloops on secondary ROM. Even even creator of DualBoot patcher said it may be unstable.
Thanks for mention me in your thread, but remove that line, it will cause bootloop. First you need to patch Magisk_v12.zip and install it, then install latest Magisk_v15.3.zip as a module in MagiskManager. Like I wrote in my guide
Click to expand...
Click to collapse
Thanks mario_R for the guide and trick. I did it hassle free as I already had my internal decrypted. But I noticed some people having problem with installation.
it worked and the 2nd rom booted correctly then i added magisk 15.3 and set kernel .. the next boot the phone boots to the primary rom and stuck at bootanimation
when checking from recovery it appears that data partition cant be read and twrp asks for password
i managed to format and restore a backup
but what exactly caused this ??
app share have a high chance of breaking secondery rom
{
"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:
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 recovery 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.
Kernel Features:
latest kernel source release
disabled security stuff/knox/proca/logging/audit/useless features
Recovery Features:
TWRP 3.5.2, Android 10
Built in 64-bit mode
Super partition support
Added custom super binary to help with managing super partitions ( more on that in post #3 )
Native rw mount dynamic partitions
Native GSI flashing
Native dynamic partitions resize/wipe/backup/restore
Working MTP and ADB only!
How to install?
Spoiler: ODIN(Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Press the volume down + volume up button whilst the phone is connected to a pc to boot in download mode;;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol down + bixby key + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, factory reset data and redo from step 5!
Download TWRP.tar from download link below;
Open odin and place the TWRP.tar file in AP slot and press start. Once you press start, keep holding power and volume up button and the device will reboot to recovery mode.
* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this Internal storage won't work in TWRP
Flash the encryption_disabler.zip from the link below to disable internal storage encryption and patch stock recovery restoration.
Additionally, flash TWRP_Bootlogo_patcher to patch warning screens when booting the device.
If you want to root, flash Magisk.
Spoiler: TWRP
If you're coming from other TWRP versions, download TWRP.img, reboot to recovery, tap Install > Install Image > Navigate to downloads folder > select TWRP.img > Select Recovery and swipe to confirm flash. Go to reboot and reboot to recovery and the changes will have taken place.
Downloads:
TWRP-3.5.2-m31-v1.0
Encryption Disabler
TWRP_Bootlogo_patcher
Sources:
Device Tree: https://github.com/soulr344/android_device_samsung_m31
Kernel Source: https://github.com/soulr344/android_kernel_samsung_m21nsxx/tree/prebuilt
TWRP Source: https://github.com/soulr344/android_bootable_recovery/commits/android-10.0
Credits:
TeamWin, corsicanu, ananjaser1211, jesec, epicX67, exynos-nigg, testers and anyone else who made this possible.
Changelog:
v1.0
Initial Release
More in github release page
MISC LINKS
Telegram Channel
Telegram Group
TeamWin Official Website
FAQ
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you flashed encryption disabler zip / formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.
Q: Why do i need to format data partition?
A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Q: I can't flash anything with TWRP. Internal Storage has some random folders with weird name.
A: Format Data and flash encryption disabler.
Info about custom super partition helper binary. (Irrelevant because of native logical partitions but yeah, its present)
It's meant to help with managing partitions inside the super partition itself. It has some functions built in like mount, unmount, flash and format. Here is a brief rundown on what each of them do.
Partitions that are supported are:
system, system_root, vendor, odm, product
Click to expand...
Click to collapse
Please note that system_root is an alias of system and umount is an alias of unmount.
All of these commands are runnable through TWRP Terminal ONLY!
Code:
super mount partition
This will mount partition in rw mode in mountpoint in fstab.
Code:
super unmount[or umount] partition
This command will unmount given partition and make it read only.
Code:
super format partition
This command will format given partition as ext4 inside super partition.
Code:
super flash partition /path/to/image.img
Flashes image.img to partition.
You can also flash GSI (Generic System Image) using this command. Simply run:
Code:
super flash system /path/to/gsi.img
For Custom ROM Developers:
You can use this as an alternative to mount/format/unmount partitions that are inside super partition normally.
Code:
run_program("/sbin/super", "format", "system"); # formats system
run_program("/sbin/super", "mount", "system"); # mounts system as rw
run_program("/sbin/super", "unmount", "system"); # unmounts system and makes it ro
Hello there,
I followed all steps and in the end ended up having with the device only showing the Samsung logo after I flashed magisk (magisk version here: https://magisk.me/zip/). I had a 64gb version of the SM-M315 running the latest android 11 version provided by samsung (current date: 10.04.2021). I have not yet managed to escape the bootloop, veen when trying to restart the warnings appear and then the samsung logo displays. I have made a pre-root version backup, but have not yet managed to return to the recovery.
Edit: I am aware that I have might bricked my device and just wanted to ask if there is anything that I could do just in the case that my assumption is wrong.
Karen3443 said:
Hello there,
I followed all steps and in the end ended up having with the device only showing the Samsung logo after I flashed magisk (magisk version here: https://magisk.me/zip/). I had a 64gb version of the SM-M315 running the latest android 11 version provided by samsung (current date: 10.04.2021). I have not yet managed to escape the bootloop, veen when trying to restart the warnings appear and then the samsung logo displays. I have made a pre-root version backup, but have not yet managed to return to the recovery.
Edit: I am aware that I have might bricked my device and just wanted to ask if there is anything that I could do just in the case that my assumption is wrong.
Click to expand...
Click to collapse
nope, you havent bricked. start by flashing stock rom again, the flash twrp, AND BE SURE to flash encryption disabler and format data. thats all and it should boot. if you skip encryption dissabler, then the stock recovery will auto restore itself(which seems your case)
if i do this:
11* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this Internal storage won't work in TWRP
will i lose my data? because i dont have sd card so if i lose my data i wont be able to do the next steps.
Thanks. I successfully installed twrp and rooted my phone. I also successfully installed Encryption Disabler. But, unfortunately couldn't install TWRP_Bootlogo_patcher. Every time I try to flash it, it always ended with Error: 1, showing “device is not compatible.”
I am on latest one UI 3.1, which released just yesterday. Is this happening as my rom is too latest for ur supplied zip file? Hope, u will answer soon. Thanks again.
NB: I already formatted data by typing “yes”.
drcarlox said:
if i do this:
11* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this Internal storage won't work in TWRP
will i lose my data? because i dont have sd card so if i lose my data i wont be able to do the next steps.
Click to expand...
Click to collapse
yes, you'll lose your data. so, backup anthing important
Ahamadmusa said:
Thanks. I successfully installed twrp and rooted my phone. I also successfully installed Encryption Disabler. But, unfortunately couldn't install TWRP_Bootlogo_patcher. Every time I try to flash it, it always ended with Error: 1, showing “device is not compatible.”
I am on latest one UI 3.1, which released just yesterday. Is this happening as my rom is too latest for ur supplied zip file? Hope, u will answer soon. Thanks again.
NB: I already formatted data by typing “yes”.
Click to expand...
Click to collapse
tap tag on the github page of bootlogo patcher and download the latest version
soulr344 said:
tap tag on the github page of encryption disabler and download the latest version
Click to expand...
Click to collapse
Thanks, it worked. Now waiting for custom rom.
soulr344 said:
tap tag on the github page of encryption disabler and download the latest version
Click to expand...
Click to collapse
i'm getting 404 page not found error,can you provide link?
kogkita said:
i'm getting 404 page not found error,can you provide link?
Click to expand...
Click to collapse
ok found it by searching through google,thx buddy.
M31 Android 11 ONEUI 3.1 TWRP_Bootlogo_patcher couldn't install
If any custom rom comes for m31 in future,is there any possibility to decrease cpu and gpu voltage offsets?(custom kernel support ?)
dont work on android 10
w ont install any thing
w ont format partition
wont mont any partition
système data or cache or dalvik cache
zrekkab said:
dont work on android 10
w ont install any thing
w ont format partition
wont mont any partition
système data or cache or dalvik cache
Click to expand...
Click to collapse
it might be a mistake here(states android 10),but on telegram page it was mentioned android 11 only,try upgrading to 11 and flash,all modules perfectly worked for me.
ensonahmet said:
M31 Android 11 ONEUI 3.1 TWRP_Bootlogo_patcher couldn't install
Click to expand...
Click to collapse
htt ps :/ /github. com/corsicanu /TWRP_Bootlogo_patcher /releases/tag/ v1.3 ,remove the spaces and download this 1.3v file
Thanks
Now build v2
I solved the solution by installing the Indian version of SM-M315F INU M315F XXU2BUC1