Decryption on CM13 and RR M now working with latest TWRP - Verizon Motorola Droid Turbo General

An announcement that I know will make some of you as happy as it made me:
Our wonderful @baybutcher27 has posted a version of TWRP that can decrypt phones that are running CM13 or CM13-based roms. Get it here: https://www.androidfilehost.com/?w=files&flid=39562 (version 3.0.2-0 mod 2 as of today).
When I first attempted to use it, it didn't work. I suspect that this was because I previously did a factory reset (formatted the data partition) using the stock Droid Turbo recovery menu. Once I formatted this partition using this version of TWRP and re-encrypted, everything worked fine.

Related

Working encryption?

Encryption used to be broken for OPT.
Some time passed since the last time I was looking for ROMs for the OPT - are there any ROMs (OxygenOS?) with working encryption?
Also, in CM13 there used to be a bug where you weren't able to call emergency numbers, is that still the case with CM14.1?
And last question, do I still have to use a special version of TWRP & Android 6.0 or can I use the official sources?
I also have this question
Few weeks back started testing with device encryption started with last OxygenOS 2.x.x encrypted worked fine but little laggy on some task.
The twrp I had didn't decrypted so I was stuck on this ROM, some days ago I read about official oos3.1 has encryption working... But how to flash if I didn't had a working decryption on twrp tried hybrid recovery but they didn't boot to recovery.
Reverted to official twrp-3.0.0-2oneplus2.img using fastboot and decryption of data was successful, now the flash process begins.
Backup.
Flash latest signed official OnePlus2Oxygen_14_OTA_020_all_1608262242.zip
Flashed especial supersu.zip for oos3
Flashed official twrp-3.0.2-2-oneplus2.img
Rebooted to recovery and decryption was successful.
Rebooted device... Input password for decryption couple of times some reboots, Android starting and then it booted fine.
Now I'm on encrypted oos3 coming from oos2 with a working recovery.
I'll test some N Roms today.
Sent from my ONE A2005 using Tapatalk
Tried Tesla and slim nougat have a warning about successfully decryption but data is corrupt and reset is necessary, restored oos3 and working fine
Sent from my ONE A2005 using Tapatalk
Latest halogenOS (xos) and cm14 encryption works
Sent from my ONE A2005 using Tapatalk

[Solved] recovery/data TWRP Oreo

Hi,
My OP5 worked like a charm with Resurrection Remix 5.8.5, but recently my pin was randomly unrecognised, and I solved it with lock key files suppression. I ended up to restore a backup but got a bootloop, that occured with every rom I tried.
I had bootloader unlocked and magisk flashed.
I finally managed to flash and boot Resurrection Remix 6.0 (after wiping every partition), but at every reboot, when in twrp 3.2.1.0 (also tried on 3.1.1), I'm unable to mount data partition. Also it doesn't ask for my pin as it did before all those reflashing. The rom seems to have no issue (except some bugs).
I tried reflashing twrp without result and deleting internal storage is working so far as long as I don't reboot. I found some threads with similar problems about Oreo's related roms but I don't know if they are related to my issue.
I'm currently on RR6.0, bootloader unlocked, twrp 3.2.1.0 and no root, and encrypted by default.
Do you have any idea on this ?
Thanks for your help.
nonnaryplayer said:
Hi,
My OP5 worked like a charm with Resurrection Remix 5.8.5, but recently my pin was randomly unrecognised, and I solved it with lock key files suppression. I ended up to restore a backup but got a bootloop, that occured with every rom I tried.
I had bootloader unlocked and magisk flashed.
I finally managed to flash and boot Resurrection Remix 6.0 (after wiping every partition), but at every reboot, when in twrp 3.2.1.0 (also tried on 3.1.1), I'm unable to mount data partition. Also it doesn't ask for my pin as it did before all those reflashing. The rom seems to have no issue (except some bugs).
I tried reflashing twrp without result and deleting internal storage is working so far as long as I don't reboot. I found some threads with similar problems about Oreo's related roms but I don't know if they are related to my issue.
I'm currently on RR6.0, bootloader unlocked, twrp 3.2.1.0 and no root, and encrypted by default.
Do you have any idea on this ?
Thanks for your help.
Click to expand...
Click to collapse
Are you using the twrp from twrp.me or a modded recovery like codeworkx or blu spark? The original recoveries from twrp.me don't work on oreo.
Try using these recoveries:
Codeworkx: https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/recovery/
Blue spark: https://forum.xda-developers.com/devdb/project/dl/?id=28224
Zohair.ul.hasan said:
Are you using the twrp from twrp.me or a modded recovery like codeworkx or blu spark? The original recoveries from twrp.me don't work on oreo.
Try using these recoveries:
Codeworkx: https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/recovery/
Blue spark: https://forum.xda-developers.com/devdb/project/dl/?id=28224
Click to expand...
Click to collapse
It worked Thanks ! I flashed codeworkx and all went fine : data is mounted at every boot, encryption unlock in recovery, flashing and restore.
I should have waited to flash oreo but this rom is the first to get me out of my bootloop hell so I'll stick with it for now.
Thanks again !
No problem Glad to see your issue got fixed.

Need some help - Strange OP6T storage issues after flash

Hello, I have a T-Mobile 6T which thanks to the XDA thread about bypassing T-mobile, is running the international firmware so I didn't have to kiss their butt trying to unlock the bootloader. Yesterday I decided to try the Resurrection Remix rom since it is unclear whether the Lineage 16 rom supports the in-display fingerprint reader, and I am too busy at work and too lazy to read the entire thread to see if it does.
I followed the instructions and updated my OxyOS to the latest .15 release via TWRP which I also updated to the latest version via OTG using a USB drive because I was unable to unencrypt using the older Blu-Spark TWRP version I had installed. After the OxyOS update (on both partitions) I flashed TWRP again, rebooted to recovery and installed Pico Gapps.
I found the Resurrection Remix rom to be very buggy and I hate the way the in-display biometric works (very slow and I don't like the paw print used as fingerprint placement). Anyway I started installing apps and after 4 apps installed, it says there is no space left in storage.
Nothing will update, and when I try to check storage with any file explorer it says "access denied" or just won't load. I've tried everything. Wiped the data and did factory reset, then flashed stock rom again and same issue. What am I doing wrong?
That looks like a messed up flash. And is pretty common. Considering that A/B is still new and everyone has his own method of flashing. So assuming you can make it back to latest Stock OOS (9.0.15 right now). If you dunno how to then simple reboot to recovery, flash OOS ZIP and then TWRP. Again Reboot to Recovery from within TWRP (Reboot -> Recovery) and again flash OOS ZIP and TWRP Installer. For TWRP I recommend you to grab the latest one (3.3.1-6 as of now). Once flashed, Format Data (Wipe -> Format Data -> YES) and Reboot. Wait for it to boot up. Now you should be on Stable Stock OOS with TWRP Installed.
Now Download ROM of your Choice (RR, LOS, Bootleggers, whatever). You will also need the latest TWRP Installer (same as above) and Gapps (Nano/ Stock Recommended) and Magisk if you want to Root. Reboot to Recovery, flash ROM ZIP and TWRP Installer ZIP. Wait for it to Finish. Reboot to Recovery. Once in TWRP, again flash ROM and TWRP Installer. Once done, again. Reboot to Recovery from Within TWRP. (Read above on how to). Now, flash Gapps. Magisk if you want to Root. Once done, again do a Format Data. Reboot and be patient for ROM to boot. And then tell me wether this works or Not. Good Luck.

[appeal][p]z3 dual D6633 patch for running z3 roms

hi guys
i need a patch for z3 dual that would be able to run z3 single-sim roms on z3 dual in android 9 pie
can any develpoer make it for me?please
thanks
please
somebody help meeeeeee
I found some patch on old oreo Z3 thread.
Also, I read the LOS 15 thread today. You need a specific TWRP for D6633. But I can't find this file.
This patch only tested on oreo ROMs so I don't know if it will work on pie.
Anyway, there you go.
You'll need a clean flash. The steps are:
- Flash TWRP 3.3.1 (if you want to install LOS 16.0, flash the boot.img from the .zip)
- reboot to TWRP, wipe everything (system, cache, dalvik, data, internal storage. BUT if you store the ROM and gapps file on internal storage, DO NOT wipe internal storage)
- flash ROM, Gapps, reboot to TWRP
- flash this dualsim patch, reboot to system
Good luck.
Zerikwan said:
I found some patch on old oreo Z3 thread.
Also, I read the LOS 15 thread today. You need a specific TWRP for D6633. But I can't find this file.
This patch only tested on oreo ROMs so I don't know if it will work on pie.
Anyway, there you go.
You'll need a clean flash. The steps are:
- Flash TWRP 3.3.1 (if you want to install LOS 16.0, flash the boot.img from the .zip)
- reboot to TWRP, wipe everything (system, cache, dalvik, data, internal storage. BUT if you store the ROM and gapps file on internal storage, DO NOT wipe internal storage)
- flash ROM, Gapps, reboot to TWRP
- flash this dualsim patch, reboot to system
Good luck.
Click to expand...
Click to collapse
thanks man appreciate that
problem still exist
ive got another problem too
after flashing a rom i want to boot to recovery but recovery doesnt load i mean it just reboots again and again
i tried many wayz but still cant go to TWRP after flashing rom
foli2 said:
thanks man appreciate that
problem still exist
ive got another problem too
after flashing a rom i want to boot to recovery but recovery doesnt load i mean it just reboots again and again
i tried many wayz but still cant go to TWRP after flashing rom
Click to expand...
Click to collapse
Sorry, I forgot to mention that.
The TWRP 3.3.1 from the link is only work on LOS 16.0. If you flash another ROM with TWRP 3.3.1, the TWRP will break.
In other word, you must flash the correct TWRP for the ROM. Also, in the past, there is a specific TWRP for Z3 dual but the link is dead.
Zerikwan said:
Sorry, I forgot to mention that.
The TWRP 3.3.1 from the link is only work on LOS 16.0. If you flash another ROM with TWRP 3.3.1, the TWRP will break.
In other word, you must flash the correct TWRP for the ROM. Also, in the past, there is a specific TWRP for Z3 dual but the link is dead.
Click to expand...
Click to collapse
i got frustrated completely

Mi 9T goes in boot loop when trying to install magisk generated boot image

I had custom rom Evolution 4.5 and the phone was rooted and working well. but then I updated to Evolution 5.1.
Now I have TWRP but no root. Also TWRP cannot decrypt data even when entering correct password.
I read on this forum that i need magisk modified boot image and need to be installed using fastboot. I took out boot.img from Evolution 5.1 rom & patched using magisk. but when i installed it using fastboot the phone went in boot-loop. Had to reinstall rom (thank god for twrp) again to make it work. but my phone is unrooted. How do i root it?
Thanks XDA community.
emailme0909 said:
I had custom rom Evolution 4.5 and the phone was rooted and working well. but then I updated to Evolution 5.1.
Now I have TWRP but no root. Also TWRP cannot decrypt data even when entering correct password.
I read on this forum that i need magisk modified boot image and need to be installed using fastboot. I took out boot.img from Evolution 5.1 rom & patched using magisk. but when i installed it using fastboot the phone went in boot-loop. Had to reinstall rom (thank god for twrp) again to make it work. but my phone is unrooted. How do i root it?
Thanks XDA community.
Click to expand...
Click to collapse
FIXED.
A few things have changed with new versions of everything (evolution 5.1 is Android 11, new TWRP, new Magisk version etc) so things needed doing differently from the usual tutorials (for Android 10).
Formatted data + wiped data, cache & system using twrp.
Flashed the ROM (Evolution 5.1) and booted into it.
Added pattern unlock (not password) - so twrp can work (twrp's current version cant decrypt files using password)- reboot to recovery..
Now, installed MagiskR.zip using TWRP + reboot to rom (to make sure it still boots) - reboot to recovery.
now installed Magisk v21.0.zip & rebooted. - check using root checker- phone is rooted.
Installed root checker application & checked if the phone is rooted. - it was.
Hope this helps someone.

Categories

Resources