Database Develop

[Recovery][17.02.2017][3.0.3] Unofficial TWRP for the Huawei Nova (hwcan)

TeamWin Recovery Project 3.0.3
WARNING #1: Unlocking BL and flashing a custom recovery voids your warranty. Please make sure to contact your carrier/seller if your phone is still under warranty after unlocking the bootloader.
WARNING #2: Make sure you have enabled OEM unlock and unlocked bootloader before trying to flash this. How you can successful root and install TWRP will be described below.
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
HOW-TO UNLOCK BOOTLOADER
Get bootloader Unlock code here (for more Information look in this thread)
Install minimal adb and fastboot
Plug in your phone and make sure all huawei drivers got installed
Enable developer options in settings as described above.
Enable OEM unlock, enable USB debugging (both in developer options)
Open the adb tool you installed recently
Type fastboot devices (now a device number should show up)
Type fastboot reboot-bootloader (your phone will now boot into bootloader, if not, you haven't set up drivers or adb/fastboot correctly)
This step will wipe all your data! Type:
Code:
fastboot oem unlock xxxxxxxxxxxxxxxx
(xx is for your unlock code)
Ones it's done type:
Code:
fastboot reboot
Your phone will reboot and you have an unlocked bootloader!
You can now go on installing TWRP on your device
HOW-TO INSTALL
Make sure you enabled OEM unlock in settings, if you haven't please do that now by tipping 10 times on build number (to activate developer options), than open developer options and go to OEM unlock, enable it
Have an unlocked bootloader is required! (In my case, I called huawei and received the unlock code 12 hours later)
Download the TWRP recovery from the download section below
Make sure you got fastboot drivers installed (I will describe this below in how to unlock your bootloader)
Open the adb/fastboot application on your pc and go to the directory where your TWRP img file is downloaded
Boot your phone into download mode (First method: fastboot reboot-bootloader while connected to pc. Second method: power off your phone, hit power on and volume down until it boots to download mode)
Check again if there is written: unlocked phone!
If yes type now into your adb/fastboot terminal:
Code:
fastboot flash recovery twrp_huawei_generic_a53_YYYYMMDD.img
Type:
Code:
fastboot reboot
Now boot into recovery by pressing: power+volume up+volume down at the same time
Enjoy twrp
HOW-TO ROOT
Backup, just in case
Have an unlocked bootloader and TWRP installed from above (take one from december)
We will use this root method: Phh's superuser
Download latest official phh superuser zip here.
Put the zip on your external sd card of your phone (since we can't access /data in twrp)
Boot into twrp and flash the downloaded file
Install latest Material phh apk: Release post
Now you are rooted, congrats!
SUPPORTED DEVICES
CAN-L01
CAN-L11
MLA-L03
(Test your Device, if you want to take the risk, and I'll add it to this list )
DOWNLOAD
CHANGES
21.12.2016: First release.
22.12.2016: Backup all your partitions.
16.02.2017: Cleanup, little fixes bump to 3.0.3-0 (Note: Root is just supported for 3.0.2)
17.02.2017: Turn Crypto off again.
KNOWN ISSUES
Encryption is not supported yet!
SOURCE CODE
TWRP: TWRP source code (7.1 branch)
Device tree (International: hwcan (master branch)
CREDITS
TWRP master @jcadduono
For helping a newby: @Tkkg1994
CONTRIBUTIONS
Gerrit for TWRP: Omni gerrit
Gerrit for officially supported devices: TWRP gerrit
XDA:DevDB Information
TWRP for Huawei Nova, Tool/Utility for the Huawei Nova/Nova Plus
Contributors
Xelfmade
Source Code: https://github.com/Xelfmade/android_device_huawei_hwcan
Version Information
Status: Beta
Current Beta Version: 3.0.3-0
Beta Release Date: 2016-12-22
Created 2016-12-21
Last Updated 2017-02-17
XDA:DevDB Information
TWRP for Huawei Nova, Tool/Utility for the Huawei Nova/Nova Plus
Contributors
Xelfmade
Source Code: https://github.com/Xelfmade/android_device_huawei_generic_a53
Version Information
Status: Beta
Current Beta Version: 3.0.3-0
Beta Release Date: 2016-12-22
Created 2016-12-21
Last Updated 2017-02-17

Great! Thanks for this big step for this wonderful device!

Download link for the twrp image does not work...pls help

mshinni80 said:
Download link for the twrp image does not work...pls help
Click to expand...
Click to collapse
AndroidFileHost has some problems right now..show a little patience and look a little later for it..

Cheers xelfmade! Just wanted to ask if this is specifically for the nova or the nova plus? Or is it compatible with both models? Thanks!

Can we backup all partitions and restore them (with decrypted data off course)?
And does knock on screen to take screenshot work? Someone told it don't work anymore after root?

uchihasparky said:
Cheers xelfmade! Just wanted to ask if this is specifically for the nova or the nova plus? Or is it compatible with both models? Thanks!
Click to expand...
Click to collapse
You can try it on the Nova plus and report me if it works or not. If it doesn't work write me a private message and I sent you the stock recovery.. ?
merlin21 said:
Can we backup all partitions and restore them (with decrypted data off course)?
And does knock on screen to take screenshot work? Someone told it don't work anymore after root?
Click to expand...
Click to collapse
Not now, I'll upload a newer version were you can backup and restore all partitions..
I'm rooted and it just works. I think it's because he formatted /data for decrypt it.

good morning...can I also use SuperSU. Coz I would prefer that over Phh's superuser.
I assume that it won't make a difference, but I want to be sure!
Thx in advance

mshinni80 said:
good morning...can I also use SuperSU. Coz I would prefer that over Phh's superuser.
I assume that it won't make a difference, but I want to be sure!
Thx in advance
Click to expand...
Click to collapse
You can try it, but I don't expect it to work..

Xelfmade said:
I'm rooted and it just works. I think it's because he formatted /data for decrypt it.
Click to expand...
Click to collapse
What should I try first to don't get this problems? Don't touch data while installing twrp and phhs su?
I'm on can-11 and believe my data is encrypted from original rom?!
And did you edit the config file in superuser. zip?
The linked one has following setting :
eng verity crypt

I cant access data or anything else in TWRP... I dont have an sd-card yet. is there no other way to install the superuser zip??

mshinni80 said:
I cant access data or anything else in TWRP... I dont have an sd-card yet. is there no other way to install the superuser zip??
Click to expand...
Click to collapse
To get access on /data, you have to format it in the wipe menu.

merlin21 said:
What should I try first to don't get this problems? Don't touch data while installing twrp and phhs su?
I'm on can-11 and believe my data is encrypted from original rom?!
And did you edit the config file in superuser. zip?
The linked one has following setting :
eng verity crypt
Click to expand...
Click to collapse
No I don't.

So if we don't wipe the data partition we could read it like before after root? And is the data encrypted afterwards?
Sorry for so many questions [emoji56]

merlin21 said:
So if we don't wipe the data partition we could read it like before after root? And is the data encrypted afterwards?
Sorry for so many questions [emoji56]
Click to expand...
Click to collapse
We can't read /data wether the phone is rooted or not..
The phone is encrypted as soon as you choose a locking method.

-=MoRpH=- said:
To get access on /data, you have to format it in the wipe menu.
Click to expand...
Click to collapse
So I have to wipe it again, like it happened after unlocking the bootloader? Then I could plug it and copy the zip file on the internal storage to run it?

If u use the latest version, try the following steps:
-- First format /data
-- reboot the Recovery
-- copies the files from your pc to the internal storage
Gesendet von iPhone mit Tapatalk

work for Europe version CAN-L11
my mobile was rooted with some error but root work perfect and thx again. willing to soon see cyanogen roms

-=MoRpH=- said:
If u use the latest version, try the following steps:
-- First format /data
-- reboot the Recovery
-- copies the files from your pc to the internal storage
Gesendet von iPhone mit Tapatalk
Click to expand...
Click to collapse
so format /data is inevitable?

Yes
Gesendet von iPhone mit Tapatalk

unlocked working bootloader but unable to flash anything...

houston we have a problem...
5 bucks for any good idea!
I have an old xt1068 (titan) that after an (official) update it becames a small brick... (it was stock, no modded bootloader or whatevere, just stock!)
today I decided to give it a chance but then only thing I reach is the bootloader
whatever thing (official retail firmware) I try to flash it doesn't work...
so I unlocked the bootloader with success to give a try a custom rom but suddenly I get a issue...
I can't install latest twrp (I tried also a couple of older ones), I can only boot trough (latest) twrp but whatever rom I install I get error7
I noticed that when it reboots the content (/sdcard /data and /system) is untouched even if from shell I can remount rw... it seems that I can delete but in reality I don't delete anything
I tried almost everything... if I try to re-stock upon reboot I reach the dead android robot
the device is an xt1068, bootloader 48.87 (30.06.2016), unlocked (status code 3)
any (good) ideas?

O this thing is happened to me , i has on stock 5.0 and i updated to a new version ,but after i get only bootloop so i unlocked the bootloader and flash the latest twrp , and if i try to install any custom rom twrp give me some partition are corrupt. Enter in TWRP open WIPE > Advanced Wipe > (check your corrupt partition ,in my case is the data) > Repair or Change File System > Change File System > Ext3 or Ext4 > Swipe to Change (if this don't work try olso resize partition or repair partition)

HiR3x said:
O this thing is happened to me , i has on stock 5.0 and i updated to a new version ,but after i get only bootloop so i unlocked the bootloader and flash the latest twrp , and if i try to install any custom rom twrp give me some partition are corrupt. Enter in TWRP open WIPE > Advanced Wipe > (check your corrupt partition ,in my case is the data) > Repair or Change File System > Change File System > Ext3 or Ext4 > Swipe to Change (if this don't work try olso resize partition or repair partition)
Click to expand...
Click to collapse
no way... I tried but nothing changes... it seems that partitions are read-only
anyway I'm not able to flash twrp (no error it just doesn't install), I can only boot twrp but again nothing changes, I tried soon after booting twrp to gain root trought supersu/magisk, all works without error but upon reboot partitions aren't touched at all

I have the exact same issue on the exact same phone.
However, what I have noticed is the fact that after SuperSu is flashed (Booting through TWRP recovery once), it doesn't actually flash at all. But what surprised me was that after the flashing, the phone reboots instead of taking me back to the recovery.
A good idea would be that maybe the bootloader isn't actually unlocked for everything. Maybe the company making the device just doesn't want us to get a new one.
In any case, I never give. I will keep trying.
---------- Post added at 09:08 AM ---------- Previous post was at 08:37 AM ----------
The solution is simply using a different TWRP version. I had mentioned my concerned earlier and I was right. We wer einitially flashing a wrong TWRP in the device and hence the problem. I found the solution in this video here: https://www.youtube.com/watch?v=9_9vkJvzWcU
However, the TWRP and Su can be found here if the guy who uploaded the video has deleted it:
https://drive.google.com/open?id=1rSyDJoeOVVFHCbNa_jkfH9HUnDoZqBhd

I am glad to hear that it helped you to resolve your problem
ni6hant said:
I have the exact same issue on the exact same phone.
However, what I have noticed is the fact that after SuperSu is flashed (Booting through TWRP recovery once), it doesn't actually flash at all. But what surprised me was that after the flashing, the phone reboots instead of taking me back to the recovery.
A good idea would be that maybe the bootloader isn't actually unlocked for everything. Maybe the company making the device just doesn't want us to get a new one.
In any case, I never give. I will keep trying.
---------- Post added at 09:08 AM ---------- Previous post was at 08:37 AM ----------
The solution is simply using a different TWRP version. I had mentioned my concerned earlier and I was right. We wer einitially flashing a wrong TWRP in the device and hence the problem. I found the solution in this video here: https://www.youtube.com/watch?v=9_9vkJvzWcU
However, the TWRP and Su can be found here if the guy who uploaded the video has deleted it:
https://drive.google.com/open?id=1rSyDJoeOVVFHCbNa_jkfH9HUnDoZqBhd
Click to expand...
Click to collapse
I am glad to hear that it helped you to resolve your problem all the required downloading links are working fit and fine it's my channel show me some love via comments and likes on my video

mandar91 said:
I am glad to hear that it helped you to resolve your problem all the required downloading links are working fit and fine it's my channel show me some love via comments and likes on my video
Click to expand...
Click to collapse
Already commented a liked.

ni6hant said:
I have the exact same issue on the exact same phone.
However, what I have noticed is the fact that after SuperSu is flashed (Booting through TWRP recovery once), it doesn't actually flash at all. But what surprised me was that after the flashing, the phone reboots instead of taking me back to the recovery.
A good idea would be that maybe the bootloader isn't actually unlocked for everything. Maybe the company making the device just doesn't want us to get a new one.
In any case, I never give. I will keep trying.
---------- Post added at 09:08 AM ---------- Previous post was at 08:37 AM ----------
The solution is simply using a different TWRP version. I had mentioned my concerned earlier and I was right. We wer einitially flashing a wrong TWRP in the device and hence the problem. I found the solution in this video here: https://www.youtube.com/watch?v=9_9vkJvzWcU
However, the TWRP and Su can be found here if the guy who uploaded the video has deleted it:
https://drive.google.com/open?id=1rSyDJoeOVVFHCbNa_jkfH9HUnDoZqBhd
Click to expand...
Click to collapse
thank you for help but it didn't work... rebooting into recovery lands me on "dead robot" saying "no command", then after 1 minute it reboots... and reboots... and so on...
I think I tried almost everything... I'm really lost

How come!
How can it happen. It is Moto G 2?
suiller said:
thank you for help but it didn't work... rebooting into recovery lands me on "dead robot" saying "no command", then after 1 minute it reboots... and reboots... and so on...
I think I tried almost everything... I'm really lost
Click to expand...
Click to collapse

ni6hant said:
How can it happen. It is Moto G 2?
Click to expand...
Click to collapse
this is what I see from bootloader...

[RECOVERY][X704F][OFFICIAL] TWRP 3.3.X for Lenovo Tab4 10 Plus

Official Downloads
https://twrp.me/lenovo/lenovo_X704F.html
Unofficial Downloads
https://www.androidfilehost.com/?w=files&flid=295687
Changelog for unofficial builds
twrp-3.3.1-0-X704F-20190604-codeworkx.img
- Updated to twrp 3.3.1
- Updated prebuilt kernel
- Removed lenovocust from backup
twrp-3.3.0-0-X704F-20190523-codeworkx.img
- initial build
Sources
Device tree: https://github.com/Teamwin/android_device_lenovo_X704F
Kernel: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953

I've seen you are working with yener90 for this device. His TWRP is valid for F, L and few other variants.
Are you able to let us know if yours is the same? Or still testing and too early to know?
Thank you (I follow you in the OnePlus 5 project too).

Flowah123 said:
I've seen you are working with yener90 for this device. His TWRP is valid for F, L and few other variants.
Are you able to let us know if yours is the same? Or still testing and too early to know?
Thank you (I follow you in the OnePlus 5 project too).
Click to expand...
Click to collapse
That seems to be the case
"TARGET_OTA_ASSERT_DEVICE := TB-X704A,TB-X704F,TB-X704L,TBX704,tb_x704a,tb_x704f,tb_x704l"
(https://github.com/codeworkx/android_device_lenovo_X704F/blob/android-9.0/BoardConfig.mk)

There's official support now.
https://twrp.me/lenovo/lenovo_X704F.html

twrp-3.3.1-0-X704F.img verified working on a new TB-X704V. Everything seems to be working.
---------- Post added at 19:36 ---------- Previous post was at 19:04 ----------
Maybe I spoke too soon.
I tried installing Yener90's Lineage OS 16 image only my TB-X704V device and it failed to boot. That's fine, but then I tried to restore the OEM image that I had backed up previously. Unfortunately, I am not able to get back to a booting system.

black.kahder said:
twrp-3.3.1-0-X704F.img verified working on a new TB-X704V. Everything seems to be working.
---------- Post added at 19:36 ---------- Previous post was at 19:04 ----------
Maybe I spoke too soon.
I tried installing Yener90's Lineage OS 16 image only my TB-X704V device and it failed to boot. That's fine, but then I tried to restore the OEM image that I had backed up previously. Unfortunately, I am not able to get back to a booting system.
Click to expand...
Click to collapse
Look at the other thread. 3.3.0 works as expected. Use the old twrp for my current ROM or wait for the next update, which will support 3.3.0

I don't have experience customizing TWRP images for specific devices, so let me apologize in advance for my n00b questions...
How similar are the x704f and x705f tablets? I'm wondering if it might be possible to use an x704f TWRP image on an x705f. Lenovo recently released a stock ROM for Pie on the x705f. Now I'm finally able to unlock the bootloader. The previous stock ROM would not respond to fastboot oem unlock commands. I was then able to fastboot flash a bootloader image pre patched with Magisk so now the tab is rooted and happy. However, I still feel insecure without TWRP as it seems to be a key tool that I use for emergency ADB access, flashing, and making nandroid backups. How big of a project do you think it would be to make a customized image for the x705f? Do you think that is something where I would have to start from scratch? Or could the x704f image be used as a template that I could easily modify with information specific to the x705f?
Thanks for your time. I truly appreciate any help or advice you can give me on this.
Chaser

on my tb-x704f twrp on starts in landscape orientation. the last version i used was 3.2.3 and here i could use both orientations.
i also can't restore an backup because i can't write to the system partition. can this https://forum.xda-developers.com/showpost.php?p=79681018&postcount=259 fix the problem?

gene2 said:
i also can't restore an backup because i can't write to the system partition. can this https://forum.xda-developers.com/showpost.php?p=79681018&postcount=259 fix the problem?
Click to expand...
Click to collapse
No, it won't, it's a magisk module that allows R/W to the system partition after boot up to
facilitate some apps. that require it for full root access.

The problem was that i had no r/w to system partition. the restore works, but the system doesn't start. i have a boot loop with the lenovo logo. i have wiped dalvik, cache and system. after that i also made the normal wipe. then i restored the backup and after restart i have the boot loop. is there anything more to do? this was all i have to do on my other devices.

gene2 said:
The problem was that i had no r/w to system partition. the restore works, but the system doesn't start. i have a boot loop with the lenovo logo. i have wiped dalvik, cache and system. after that i also made the normal wipe. then i restored the backup and after restart i have the boot loop. is there anything more to do? this was all i have to do on my other devices.
Click to expand...
Click to collapse
Sounds like encryption is compromised, restore stock ROm, re-boot and start again.
See my other post to you here:-
https://forum.xda-developers.com/showpost.php?p=80273515&postcount=5

Hello, I have tried TWRP for TB-X704F on TB-X704A, but though my bootloader is unlocked, I have the latest SDK tools, and fastboot flash recovery recovery.img seems to take, nothing I do causes the device to boot into TWRP. I cannot sideload lineagos using stock recovery, and so for now I seem to be stuck. Any suggestions? I'd like to move past Android 7.1 for a more secure OS.

I've had the EXACT same problem with a TB-X704A. I've been waiting for someone else to say so. I'm sorry I don't have a solution but I'm hoping someone more knowledgeable then me sees our problem. Thanks to everyone, especially codeworkx who does this stuff!

Mddaddy said:
Hello, I have tried TWRP for TB-X704F on TB-X704A, but though my bootloader is unlocked, I have the latest SDK tools, and fastboot flash recovery recovery.img seems to take, nothing I do causes the device to boot into TWRP. I cannot sideload lineagos using stock recovery, and so for now I seem to be stuck. Any suggestions? I'd like to move past Android 7.1 for a more secure OS.
Click to expand...
Click to collapse
You have to reboot to recovery manually not via fastboot. Unplug from pc and hold power and volume up it should boot into twrp this way cus f version should work
---------- Post added at 04:02 AM ---------- Previous post was at 03:55 AM ----------
kirknado18 said:
You have to reboot to recovery manually not via fastboot. Unplug from pc and hold power and volume up it should boot into twrp this way cus f version should work
Click to expand...
Click to collapse
Twrp for tb x704f should work on all 704 versions but you have to boot into recovery manually not through adb fastboot it wont boot up that way for some reason. Let me know if this solves the problem.

I wanted to update from LineageOS 16 to LineageOS 17. Instructions there say to upgrade to latest TWRP (https://forum.xda-developers.com/th...m-lineageos-17-0-lenovo-tab4-10-plus-t4016705). I downloaded the unofficial twrp-3.3.1-0-X704F-20190604-codeworkx.img, flashed using adb, but when trying to go into recovery mode - will not go into recovery. Tries, then reboots again, and goes into LineageOS 16.
Downloaded the "official" version form (https://dl.twrp.me/X704F/), version twrp-3.4.0-0-X704F.img, again flashed using adb - again same results. Cannot get into recovery mode, boots twice and goes back into LineageOS 16.
So - something didn't go quite right - how do I get into recovery mode?

tundrwd said:
I wanted to update from LineageOS 16 to LineageOS 17. Instructions there say to upgrade to latest TWRP (https://forum.xda-developers.com/th...lineageos-17-0-lenovo-tab4-10-plus-t4016705). I downloaded the unofficial twrp-3.3.1-0-X704F-20190604-codeworkx.img, flashed using adb, but when trying to go into recovery mode - will not go into recovery. Tries, then reboots again, and goes into LineageOS 16.
Downloaded the "official" version form (https://dl.twrp.me/X704F/), version twrp-3.4.0-0-X704F.img, again flashed using adb - again same results. Cannot get into recovery mode, boots twice and goes back into LineageOS 16.
So - something didn't go quite right - how do I get into recovery mode?
Click to expand...
Click to collapse
Unplug from USB. Hold power and volume up buttons until the bootloader loads. Use the volume rocker to select "Recovery mode". Press power button to confirm.

jfaheyfan said:
Unplug from USB. Hold power and volume up buttons until the bootloader loads. Use the volume rocker to select "Recovery mode". Press power button to confirm.
Click to expand...
Click to collapse
I'm aware of how to get into recovery - it WON'T go into recovery. Starts up, the Moto screen flashes, it reboots, Moto screen again, then loads LineageOS. So I simply cannot get into recovery once selecting "Recovery Mode".

tundrwd said:
I'm aware of how to get into recovery - it WON'T go into recovery. Starts up, the Moto screen flashes, it reboots, Moto screen again, then loads LineageOS. So I simply cannot get into recovery once selecting "Recovery Mode".
Click to expand...
Click to collapse
What model is your tablet?

I have an A model and an F model. I've used the same TWRP on both the A and F. This particular instance is just the A model - TBX-704A

tundrwd said:
I have an A model and an F model. I've used the same TWRP on both the A and F. This particular instance is just the A model - TBX-704A
Click to expand...
Click to collapse
You're not the first:
https://forum.xda-developers.com/showpost.php?p=81254945&postcount=12
https://forum.xda-developers.com/showpost.php?p=82183753&postcount=13
Not sure of the significance, but "Moto" doesn't appear in the boot sequence of my TB-X704N (changed to TB-X704L after I installed LOS 17.1). I get "Lenovo" in an orange rectangle.
My next step would be to try https://dl.twrp.me/X704F/twrp-3.3.1-0-X704F.img . Better yet would be to hear from someone who's installed LOS 17.1 on an "A" model.
---------- Post added at 08:03 PM ---------- Previous post was at 07:42 PM ----------
I installed TWRP 3.4.0 on my TB-X704N (Chinese Tab 4 10+ with 4G) three weeks ago. I went on to install LOS 17.1 (https://forum.xda-developers.com/th...7-0-lenovo-tab4-10-plus-t4016705/post81141501). Everything went well just by following instructions. Thank you, codeworkx!

TWRP asking for password for Decrypt Data on (8.1) international global rom

Hello guys,
just wanna asking again,.. I was going to flash magisk on red magic. I already succeed in flashing the TWRP. But, unfortunately, the TWRP was asking for a password to Decrypt Data...
Does anyone know the solution for this?
I already try to put pin on android and use it on TWRP still no luck here. Is there is a way to decrypt the phone from the system itself??
any suggestions will be great :fingers-crossed:

ianseer said:
Hello guys,
just wanna asking again,.. I was going to flash magisk on red magic. I already succeed in flashing the TWRP. But, unfortunately, the TWRP was asking for a password to Decrypt Data...
Does anyone know the solution for this?
I already try to put pin on android and use it on TWRP still no luck here. Is there is a way to decrypt the phone from the system itself??
any suggestions will be great :fingers-crossed:
Click to expand...
Click to collapse
Flash official recovery from twrp website. If I remember right it will work. But change language to English

If you haven't already find solution you must do factory reset through twrp option to unlock it ,of course this action will wipe all your data.

strakell said:
If you haven't already find solution you must do factory reset through twrp option to unlock it ,of course this action will wipe all your data.
Click to expand...
Click to collapse
Data partition he needs to wipe.

ianseer said:
Hello guys,
just wanna asking again,.. I was going to flash magisk on red magic. I already succeed in flashing the TWRP. But, unfortunately, the TWRP was asking for a password to decrypt Data...
Does anyone know the solution for this?
I already try to put pin on android and use it on TWRP still no luck here. Is there is a way to decrypt the phone from the system itself??
any suggestions will be great :fingers-crossed:
Click to expand...
Click to collapse
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-%28FAQ%29
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/project-treble/trebleenabled-device-development/descendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened your appetite!
have fun!

ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/pr...escendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened you appetite!
have fun!
Click to expand...
Click to collapse
Does the songs are getting played into the gsi? Treble GSI have issues like overheating and no sound while playing music. Means no ringtones either. I had put logs for phh but he didn't worked as he is busy. As all gsi uses phh base and fixes, the issues are same across the gsi.
Plus- in pie Chinese vendor the treble support is gone. So no more treble in pie update. Only we have legacy support on 8.1.
I had tried to work onto updating Omni but my motherboard went down. It got burnt. You know how to cook ROMs right ! Why don't you try?
Plus the latest gsi no longer boot idk the reasons with the July updates. Reply to me I am trying to donate a device to anyone who can work on this phone

ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/pr...escendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened you appetite!
have fun!
Click to expand...
Click to collapse
You answering all of my question very nice and clear... Yes i will having fun next week, i hope... (Still in other city now, i need my phone)... But, when the time comes, i will try it and post the update here... big thanks, Appriciate it... Yes i'm hungry now

methuselah said:
Does the songs are getting played into the gsi? Treble GSI have issues like overheating and no sound while playing music. Means no ringtones either. I had put logs for phh but he didn't worked as he is busy. As all gsi uses phh base and fixes, the issues are same across the gsi.
Plus- in pie Chinese vendor the treble support is gone. So no more treble in pie update. Only we have legacy support on 8.1.
I had tried to work onto updating Omni but my motherboard went down. It got burnt. You know how to cook ROMs right ! Why don't you try?
Plus the latest gsi no longer boot idk the reasons with the July updates. Reply to me I am trying to donate a device to anyone who can work on this phone
Click to expand...
Click to collapse
If only i can help you guys out cooking the rom... I'm only animator and designer... Not chef programmer or coder

methuselah said:
Does the songs are getting played into the gsi? Treble GSI have issues like overheating and no sound while playing music. Means no ringtones either. I had put logs for phh but he didn't worked as he is busy. As all gsi uses phh base and fixes, the issues are same across the gsi.
Plus- in pie Chinese vendor the treble support is gone. So no more treble in pie update. Only we have legacy support on 8.1.
I had tried to work onto updating Omni but my motherboard went down. It got burnt. You know how to cook ROMs right ! Why don't you try?
Plus the latest gsi no longer boot idk the reasons with the July updates. Reply to me I am trying to donate a device to anyone who can work on this phone
Click to expand...
Click to collapse
YES, at this moment sound is a problem in GSI ROMs. In call you have sound but not in media.
I am still looking for solutions.

ABM30 said:
YES, at this moment sound is a problem in GSI ROMs. In call you have sound but not in media.
I am still looking for solutions.
Click to expand...
Click to collapse
There are logs on phh thread about sound and other issues on gsi. Take a look if you have any knowledge. You don't need to take logs again I guess. But new GSI don't even boot last time this month when I checked. Maybe I was wrong.
It's just my point of view. You should try to bring up lineageOs with Omni sources coz lot of developers are there to help you if you have knowledge. The device tress are there from Omni. Well 8.1 is still there as lineageOs is still updating and giving security fixes. And most of commits are there for ok our phones in Omni GitHub.

ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-%28FAQ%29
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/project-treble/trebleenabled-device-development/descendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened your appetite!
have fun!
Click to expand...
Click to collapse
Hello, me again...
I'm trying to do the method that you've explained...
there's a new problem... right now, already try to connect my phone to USB on pc, it always says "USB supplying power on attached device" even for fastboot mode it doesn't work the computer still not recognize anything.. already tried different computer, already tried different cables too... no luck...
Now, I can go to emergency recovery with stock nicely but cannot go to the usual recovery cuz i already installed twrp but the phone itself is encrypted device so nothing to do there, I'm thinking about wiping userdata from emergency recovery,... is it okay to do this? cuz maybe I'm thinking after I wiping the userdata and everything I can get my USB connection again (cuz before i've had similar issue but after install new rom it's working nicely almost with every cable),... what do u guys think? thanks in advance

ianseer said:
Hello, me again...
I'm trying to do the method that you've explained...
there's a new problem... right now, already try to connect my phone to USB on pc, it always says "USB supplying power on attached device" even for fastboot mode it doesn't work the computer still not recognize anything.. already tried different computer, already tried different cables too... no luck...
Now, I can go to emergency recovery with stock nicely but cannot go to the usual recovery cuz i already installed twrp but the phone itself is encrypted device so nothing to do there, I'm thinking about wiping userdata from emergency recovery,... is it okay to do this? cuz maybe I'm thinking after I wiping the userdata and everything I can get my USB connection again (cuz before i've had similar issue but after install new rom it's working nicely almost with every cable),... what do u guys think? thanks in advance
Click to expand...
Click to collapse
Well, if you are encrypted you will need to uncrypt your phone.
!!!!!!!But you will lose everithing saved in internal memory!!!!!!!!
Just follow steps 1 to 8 from my previous guide. Then you can reinstall the ROM. If you will install International ROM you will get encrypted again if you don't run Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip right after installing ROM in TWRP!!!!!!!
Wiping everything with original recovery is the best way to clear your phone!!! sometimes is mandatory this, even with advanced wipe in TWRP you wont achieve what you can with original recovery wipe!

Back to report...
Already finished all the things need to be done... and ABM30 method is working nicely.... now, I can enjoy all the root goodness in my red magic with original global rom.
really this is what I'm looking for... Thanks a lot.
Ps: just wanna share for the USB to pc connectivity problems: what I did was connect it on fastboot mode, and do fastboot command for unlocking your red magic.... wait around 5 min, unplug it if nothing happens, plug it again and wait again (until many times), after that you will see your fastboot command from wait mode into something successful... (i dunno why).
and then do reflash the recovery...
for the resurrection remix, I will try it and post it on new thread.... seems interesting

ianseer said:
Back to report...
Already finished all the things need to be done... and ABM30 method is working nicely.... now, I can enjoy all the root goodness in my red magic with original global rom.
really this is what I'm looking for... Thanks a lot.
Ps: just wanna share for the USB to pc connectivity problems: what I did was connect it on fastboot mode, and do fastboot command for unlocking your red magic.... wait around 5 min, unplug it if nothing happens, plug it again and wait again (until many times), after that you will see your fastboot command from wait mode into something successful... (i dunno why).
and then do reflash the recovery...
for the resurrection remix, I will try it and post it on new thread.... seems interesting
Click to expand...
Click to collapse
Why are flashing without any output. Flash phh treble and help in sorting out bugs.

methuselah said:
Why are flashing without any output. Flash phh treble and help in sorting out bugs.
Click to expand...
Click to collapse
I will... btw, do u know if we in treble. what happened with led strip on the back? is it only for notification? or turned off completely?

ianseer said:
I will... btw, do u know if we in treble. what happened with led strip on the back? is it only for notification? or turned off completely?
Click to expand...
Click to collapse
well it doesn't work. It's a part of kernel I guess. There are no sounds from loudspeaker. and there are huge issues with pie in phh treble. He needs logs for that. You can't even login into the google account. There are logs with on treble Phh thread. August images are there. Start taking logs after reading the thread. You will be happy to help him.

ianseer said:
I will... btw, do u know if we in treble. what happened with led strip on the back? is it only for notification? or turned off completely?
Click to expand...
Click to collapse
Did you posted any log?

ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: [url]http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file[/URL]
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : [url]http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file[/URL]
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : [url]http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file[/URL]
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: [url]https://forum.xda-developers.com/project-treble/trebleenabled-device-development/resurrection-remix-phh-treble-t3767688[/URL]
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
[url]https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list[/URL] ,
or here:
[url]https://forum.xda-developers.com/project-treble/trebleenabled-device-development[/URL]
About treble experimentation here: [url]https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-%28FAQ%29[/URL]
For example I like the DESCENDANT 3.1.1 : [url]https://forum.xda-developers.com/project-treble/trebleenabled-device-development/descendant-android-pie-custom-rom-ver-t3840578[/URL] but I can not make working gapps on it....till now at least
So, I think i have opened your appetite!
have fun!
Click to expand...
Click to collapse
Hello sir, I followed each and every step, but device ended up in bootloop. Mostly a soft brick. Every time I power on the device, the logo comes and phone turns off.
I even tried to patch the fstab in /vendor/etc. Same results.
By the way, I could not get the V114 stock global rom which you have mentioned but was able to get V109 stock global rom. If you have the link of the stock rom you mentioned, please provide a link for it. I will just revert back to stock and use it that way. Seems like the device doesn't wants to have an unlocked bootloader and a uncrypted data state ?

ianseer said:
Back to report...
Already finished all the things need to be done... and ABM30 method is working nicely.... now, I can enjoy all the root goodness in my red magic with original global rom.
really this is what I'm looking for... Thanks a lot.
Ps: just wanna share for the USB to pc connectivity problems: what I did was connect it on fastboot mode, and do fastboot command for unlocking your red magic.... wait around 5 min, unplug it if nothing happens, plug it again and wait again (until many times), after that you will see your fastboot command from wait mode into something successful... (i dunno why).
and then do reflash the recovery...
for the resurrection remix, I will try it and post it on new thread.... seems interesting
Click to expand...
Click to collapse
I'm facing issues with this. I followed every step as mentioned by ABM30. But the device in now on bootloop. Infact, I do have the twrp as recovery but device state is locked and the system isnt booting up. Help please

Zenith9082 said:
I'm facing issues with this. I followed every step as mentioned by ABM30. But the device in now on bootloop. Infact, I do have the twrp as recovery but device state is locked and the system isnt booting up. Help please
Click to expand...
Click to collapse
you mean twrp mentioned that your device is locked?

[RECOVERY][UNOFFICIAL][ROOT] TWRP for Galaxy A70

Team Win Recovery Project 3.x, or TWRP3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
[I]#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/[/I]
I’d recommend to read everything in this post, if you care about your expensive phone.
Let’s start with the installation process
If you already unlocked your bootloader, start with step 3.
If you are already rooted, start with step 4.
If you already installed a previous version of TWRP, start with step 4.
If you already have TWRP installed and just want to root, start with step 5.
First you need to unlock your bootloader. You can do so by enabling developer settings first, enable oem unlocking, then shut down your phone, hold volume up and down at the same time and while holding them plugin your charger. Your phone now should show a green screen with instructions to unlock the bootloader. Just follow them and after the unlocking your data should get wiped. After that your device will boot up and land in setup screen. Do not setup anything, just skip as much as possible, because your phone will get wiped again. Enable developer settings and make sure oem unlocking is greyed out and enabled. (If it does not show up, connect to a network first!)
Now you need to overwrite vbmeta partition, so you can flash third party partitions. Download vbmeta.tar then go into download mode on your device. Put vbmeta.tar to AP in Odin, click start. This should finish pretty quickly, so pay attention when your device reboots, because you need to boot into recovery (Hold power and volume up after the screen turns black). When booted into recovery, wipe your data and reboot normally into system. Now you can setup your phone as usual and make sure oem unlocking is still greyed out and enabled!
Time to flash recovery. Download (link is at the end of this post) the latest version as zip and extract it. You should end up with one single file named recovery.img. Pack it as tar with 7zip or any other compression tool you prefer. This packed tar file should only contain recovery.img and nothing else, also make sure the name is still recovery.img, otherwise Odin will refuse to flash it. In Odin put the tar file in AP and simply hit start. Congrats you now have TWRP installed!
(Optional) You might have lost root access by flash TWRP if you followed this standard guide for rooting. If you did lose it and want to gain root access again (you can also root your device with this method, even when you never rooted your device), download the latest Magisk Manager from the canary channel and install the apk to your phone.
If you are on stock:
Push the recovery.img file you just download for TWRP to your phone. Open Magisk Manager and hit install and patch a file. Select recovery.img and Magisk should start the patching process. Once Magisk is done, boot into TWRP. Backup your boot partition first and afterwards go into install and then hit install image on the bottom right of the screen. Select /sdcard/Download/magisk_patched.img and install it to boot. Now reboot and Magisk should work. If you run into issues after this, go into TWRP and restore the boot partition you backed up previously.
If you are on an AOSP based rom:
Reboot to TWRP. Create a backup with boot partition. Reboot back to system, then open Magisk and hit install and patch a file. Locate the TWRP backup folder and look up your backup you just created. Select boot.emmc.win for patching. Once Magisk is done, reboot back to TWRP. Go into install and then hit install image on the bottom right of the screen. Select /sdcard/Download/magisk_patched.img and install it to boot. Now reboot and Magisk should work. If you run into issues after this, go into TWRP and restore the boot partition you backed up previously.
So that was the easy part. The hard part is to completely read these following points!
Encryption/Decryption
Decryption works on this TWRP release, but only partially. That means you have to open the Settings Application first on your phone and disable a feature called strong protection. You can find it in Settings->Biometrics and security>Other security settings. It doesn’t matter when you disable it. Flash TWRP first and disable it, fine. Disable it and flash TWRP afterwards, fine. Never disable it, also fine, TWRP just fails to decrypt your data, but won’t do any harm. When this feature gets turned off, the device will generate a key which doesn't require any authentication for decryption, currently only this allows TWRP to decrypt the data partition successfully. This only applies to stock roms though, if you are using an AOSP based rom, then you don't have to do any of this.
Disabling decryption
Disabling decryption will create many problems. First TWRP will refuse to unmount system partition and thus you might run into problems flashing various zips. So I advise you to not disable decryption. If you still want to disable it you have to open terminal in TWRP and type in "stop servicemanager" everytime you want to unmount the system partition.
Backup and Restore
Because of encryption it's more complicated to backup your data partition.
If you want to backup data you have to make sure TWRP successfully decrypted your internal storage, otherwise you will run into problems backing up.
Restoring is even more complicated. Every time you set up a rom, new crypto keys will be generated and you can't backup these. That means if you want to restore data you have to restore the whole rom first excluding data. Format data partition completely, boot it up, then go back to TWRP and restore data. You will lose your internal storage, so I'd recommend you move important stuff to external storage.
Developers specific details
Sources
https://github.com/Grarak/android_device_samsung_a70q-twrp
https://github.com/Grarak/android_device_samsung_a70q
https://github.com/Grarak/android_bootable_recovery-1
Recovery image size
For some reason the ramdisk has a size limit, so I used LZMA compression to get its size down as much as possible.
During kernel compilation you will run into a DTC error. Apparently Samsung didn’t bother to update their DTC source in the kernel and you have to use their precompiled binary. I edited my kernel sources to automatically use their dtc binary.
Credits
Device tree of Redmi Note 7 Pro (https://github.com/TeamWin/android_device_xiaomi_violet). Helped a lot!
Topjohnwu for the detailed installation guide (https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root)
TWRP Galaxy S10 thread for describing System-as-root pretty well
(https://forum.xda-developers.com/ga...ecovery-twrp-3-3-0-galaxy-s10-exynos-t3924856)
Downloads
https://github.com/Grarak/android_device_samsung_a70q-twrp/releases (Also changelog)
Note The download is a zip file, unpack it and you will get the recovery image. To flash it in Odin pack it as tar with 7zip or a compression tool of your liking.

reserved

nice work, I'll buy the phone in this 2 days to start some works.

Thanks bro ?
Screenshot please

thanks alot ! development can start on this phone ! (i confirm twrp work)

BK☑️ said:
thanks alot ! development can start on this phone ! (i confirm twrp work)
Click to expand...
Click to collapse
Which version do you have?

devilhunter47 said:
Which version do you have?
Click to expand...
Click to collapse
TWRP version is 3.3.1
actual firmware is A705FNXXU3ASG6_A705FNOXM3ASG6_BTU (july security patch) (United kingdom)
prev. firmware was A705FNXXU1ASE4_A705FNOXM1ASE4_XEF (may security patch) (France)
edit 1 : the ui freeze completly when phone is booted up , had to flash all back
i'm going to flash A705FNXXU1ASD1_A705FNOXM1ASD1_BTU (april security patch) (United kingdom) and see if it boot correctly...
edit 2 : cant flash previous firmware due to 'security reasons' ,i flashed back stock recovery, it doesnt freeze anymore, i guess we will have to wait for a custom kernel

cant you use this to flash GSI images and then use magisk? or does that not bypass the boot image problem?

MTP
Grarak said:
FAQ
When TWRP can't work with Magisk, then what's the point of this?
TWRP can work with Magisk, if the firmware you have is compatible. (Read first post).
But yes, right now there are no reasons to have TWRP installed, but you have to start development somewhere and having a working custom recovery is a pretty good first step.
Click to expand...
Click to collapse
MTP doesnt work in this build
edit: it work in this build thanks
---------- Post added at 09:38 PM ---------- Previous post was at 09:30 PM ----------
kristiansja said:
cant you use this to flash GSI images and then use magisk? or does that not bypass the boot image problem?
Click to expand...
Click to collapse
i dont think this build is made for treble roms, so probably not

BK said:
MTP doesnt work in this build
Click to expand...
Click to collapse
Uploaded the wrong version. Fixed

Grarak said:
Uploaded the wrong version. Fixed
Click to expand...
Click to collapse
lemme check
---------- Post added at 09:57 PM ---------- Previous post was at 09:52 PM ----------
BK said:
lemme check
Click to expand...
Click to collapse
edit : it work now thanks!

Thanks dev! Astonished at the progress you've made despite Sammy's carelessness

BK☑️ said:
lemme check
---------- Post added at 09:57 PM ---------- Previous post was at 09:52 PM ----------
edit : it work now thanks!
Click to expand...
Click to collapse
With July security patch?

Okay, so can anybody else see if system or system images backup crashes TWRP?

FriendlyNeighborhoodShane said:
Okay, so can anybody else see if system or system images backup crashes TWRP?
Click to expand...
Click to collapse
yep , i tried backups yesterday but twrp crash when backing up system.img
---------- Post added at 09:04 AM ---------- Previous post was at 09:01 AM ----------
devilhunter47 said:
With July security patch?
Click to expand...
Click to collapse
i was refering to MTP , the link been fixed, MTP work now , but phone crash after boot up , or just wont boot at all, i were also stuck in prenormal RMM, thats why it wouldnt boot

Grarak said:
FAQ
twrp reboot itself when transfering files and freeze forever , have to flash whole firmware again everytime
Click to expand...
Click to collapse

Kernel source A70Q
Grarak said:
FAQ
When TWRP can't work with Magisk, then what's the point of this?
TWRP can work with Magisk, if the firmware you have is compatible. (Read first post).
But yes, right now there are no reasons to have TWRP installed, but you have to start development somewhere and having a working custom recovery is a pretty good first step.
Click to expand...
Click to collapse
i found kernel sources from there https://github.com/Qiangong2/android_kernel_samsung_a70q , is this the source you worked with?

BK said:
Grarak said:
FAQ
twrp reboot itself when transfering files and freeze forever , have to flash whole firmware again everytime
Click to expand...
Click to collapse
Seems to be a kernel problem. Probably have to wait for Samsung to update their sources.
BK said:
i found kernel sources from there https://github.com/Qiangong2/android_kernel_samsung_a70q , is this the source you worked with?
Click to expand...
Click to collapse
No
Click to expand...
Click to collapse

Grarak said:
FAQ
When TWRP can't work with Magisk, then what's the point of this?
TWRP can work with Magisk, if the firmware you have is compatible. (Read first post).
But yes, right now there are no reasons to have TWRP installed, but you have to start development somewhere and having a working custom recovery is a pretty good first step.
Click to expand...
Click to collapse
i contacted the guys from Samsung Opensource Center for kernel and platform source release, ill see what they say...

How to install TWRP can anyone tell step by step....