problems with phone decryption - General Questions and Answers

I have older device, it is htc 10.
I was using corporate MS Teams on it however at some point corporate required encryption to be done on my phone i got poop-up and trigger encryption.
Now phone consume much more power, i think because of the encryption.
I would like to decrypt the phone however there is no such button.
Any idea how to trigger this decryption without factory reset, it is Android 8.0 ?

It can't be undone normally. Back up all critical data, factory reset.
I never encrypt any device as it will come back to bit you sooner or latter.
-Never- encrypt backup data drives or set PC bios passwords. You are the one most likely to get locked out, sometimes through no fault of your own!!!

seba.kwiat said:
...
I would like to decrypt the phone however there is no such button.
Any idea how to trigger this decryption without factory reset, it is Android 8.0 ?
Click to expand...
Click to collapse
3 methods possible
1.
You can turn your device's /data partition to an unencrypted state if you do a backup of this partition via the adb backup command and play back the backup via the adb restore command.
2.
Boot phone into recovery and then from your computer run
Code:
adb shell "recovery --set_filesystem_encryption=off"
3.
If you need to run it from the phone itself (ie: you don't have a computer nearby to adb with): in a terminal window run
Code:
recovery --set_filesystem_encryption=off

jwoegerbauer said:
3 methods possible
1.
You can turn your device's /data partition to an unencrypted state if you do a backup of this partition via the adb backup command and play back the backup via the adb restore command.
2.
Boot phone into recovery and then from your computer run
Code:
adb shell "recovery --set_filesystem_encryption=off"
3.
If you need to run it from the phone itself (ie: you don't have a computer nearby to adb with): in a terminal window run
Code:
recovery --set_filesystem_encryption=off
Click to expand...
Click to collapse
Could u recommend any terminal app, I have tried a couple but looks like recovery command is missing on them?

Related

[Guide] Backing up BlackShark (and other models too)

Hello, this guide explains how to backup your phone. This guide is intended for the BlackShark (SKR-H0), but works on other models, and other phones too.
So let's begin.
First of all, unlock your phone. This might void your warranty. Expect to lose all data on your device, so backup your internal storage to a pc or a cloud or something.
Boot your recovery (fastboot boot yourrecoveryfilename.img)
When inside the recovery (twrp example), it might ask you to enter a password, or swipe to allow modifications. Just ignore it and do nothing.
Now, connect your phone to your pc, and run the following adb command:
adb shell ls /dev/block/bootdevice/by-name/
You will get a list of files. Those are your phone partitions. You are going to back them up.
For every file (except for userdata, which contains the storage) you find, run the following command:
adb pull /dev/block/bootdevice/by-name/<filename> <filename>.img
Examples:
Code:
adb pull /dev/block/bootdevice/by-name/system_a system_a.img
adb pull /dev/block/bootdevice/by-name/system_b system_b.img
adb pull /dev/block/bootdevice/by-name/boot_a boot_a.img
....
Now you have a full backup. Enjoy it and keep it safe. When you **** up, this backup might be the only thing to save you.
I am late, I have updated to Pie and now TWRP is not working.
or do you have TWRP that works on Pie?
goonoth said:
I am late, I have updated to Pie and now TWRP is not working.
or do you have TWRP that works on Pie?
Click to expand...
Click to collapse
What do you mean it's not working?
gilbert32 said:
What do you mean it's not working?
Click to expand...
Click to collapse
when I push twrp with fastboot boot twrp.img its restart to system instead of recovery.
I think TWRP from https://forum.xda-developers.com/android/development/recovery-unofficial-twrp-recovery-t3892707 is not support on Pie yet.
Or do you have another recovery for Pie?

Backup HTC 10 with broken screen

Hey guys, I am trying to pull data from my HTC 10 via adb. I accidently dunked my phone in water and now my screen is black but still responsive. Phone has usb-debugging enabled but not rooted. I have a second HTC 10 which I am using for reference and a test run. When I boot into recovery, adb devices shows that the device is in sideload mode. What should I do now?
If the data of interest are stored in Android's user-space ( i.e. /storage/emulated/0 AKA /sdcard ) then you at any time can try to pull them by means of ADB
Example code what pulls entire /sdcard folder
Code:
mkdir C:\Data-Pulled
adb devices
adb pull /storage/emulated/0 C:\Data-Pulled
But I can't pull from sideload mode
jwoegerbauer said:
If the data of interest are stored in Android's user-space ( i.e. /storage/emulated/0 AKA /sdcard ) then you at any time can try to pull them by means of ADB
Example code what pulls entire /sdcard folder
Code:
mkdir C:\Data-Pulled
adb devices
adb pull /storage/emulated/0 C:\Data-Pulled
Click to expand...
Click to collapse
RogueDragon117 said:
But I can't pull from sideload mode
Click to expand...
Click to collapse
Confused.
You boot into ADB Sideload mode only if you want to re-flash phone's Stock ROM. To pull data you have to boot phone in ADB Normal mode, means into phone's Android OS.
jwoegerbauer said:
Confused.
You boot into ADB Sideload mode only if you want to re-flash phone's Stock ROM. To pull data you have to boot phone in ADB Normal mode, means into phone's Android OS.
Click to expand...
Click to collapse
The problem is that my phone is password protected. Normally when I connect my phone there is a prompt to confirm usb-debugging. I can't press yes to that prompt because I can't see it. I tried booting to recovery mode but all I could get was sideload mode. I could also load something through sd card, maybe a command somehow?
IMO the problem isn't that your phone is password protected, but that you obviously aren't knowing that on Android side ADB gets loaded/started via phone's bootloader ( keyword: init.rc -> service adbd ).
" I am trying to pull data from my HTC 10 via adb. I accidently dunked my phone in water and now my screen is black but still responsive."
I almost choked reading this ahaha is there a water bucket waiting around also how did you know its still responsive if screen is black also you provably need a screen repair at this point
You can download platform tool on computer. Open shell, use command adb backup all and also use adb pull to copy partition directory.
?
ineedroot69 said:
" I am trying to pull data from my HTC 10 via adb. I accidently dunked my phone in water and now my screen is black but still responsive."
I almost choked reading this ahaha is there a water bucket waiting around also how did you know its still responsive if screen is black also you provably need a screen repair at this point
Click to expand...
Click to collapse
There was a water bucket around. I know the screen is responsive because when I press I can hear sounds coming from the device.
Hey guys, so after letting my phone sit in the sun for two days, the screen is now functioning. I am now trying to backup adb, but it always stops around the 5GB mark.
The command I used on cmd is : adb backup -apk -all.
Did I do something wrong?
jwoegerbauer said:
IMO the problem isn't that your phone is password protected, but that you obviously aren't knowing that on Android side ADB gets loaded/started via phone's bootloader ( keyword: init.rc -> service adbd ).
Click to expand...
Click to collapse
I'm sorry, I don't understand what you are saying, I am very new to this and don't understand a lot of things.
RogueDragon117 said:
I am now trying to backup adb, but it always stops around the 5GB mark.
The command I used on cmd is : adb backup -apk -all.
Did I do something wrong?
Click to expand...
Click to collapse
IMO a complete phone backup via ADB is invoked by
Code:
adb backup "-apk -obb -shared -all -system -f C:\phone-backup.ab"
but I may err, as always ...
why not adb pull data
jjgvv said:
why not adb pull data
Click to expand...
Click to collapse
IMO the far better method because "adb backup" creates a file what is compressed and encrypted, whereas "adb pull" simply creates a file that contains the at 100% readable content of pulled data.
deleted
jwoegerbauer said:
IMO the far better method because "adb backup" creates a file what is compressed and encrypted, whereas "adb pull" simply creates a file that contains the at 100% readable content of pulled data.
Click to expand...
Click to collapse
is internal storage inside data
jwoegerbauer said:
IMO the far better method because "adb backup" creates a file what is compressed and encrypted, whereas "adb pull" simply creates a file that contains the at 100% readable content of pulled data.
Click to expand...
Click to collapse
how encrypted
@jjgvv
The Android Backup (*.ab) file is a compressed TAR. It is compressed using the DEFLATE algorithm. On top of that, there can be AES encryption used. This is determined when you create the backup: if you enter a password then the backup is encrypted, otherwise; there is no encryption, it is only compressed.
jwoegerbauer said:
IMO a complete phone backup via ADB is invoked by
Code:
adb backup "-apk -obb -shared -all -system -f C:\phone-backup.ab"
but I may err, as always ...
Click to expand...
Click to collapse
And will there be an indicator of whether the backup is complete?

How do you backup data in a rooted phone using adb twrp?

I have a Galaxy Note 5 and I have important data in it. The screen is broken so I can't do anything, but I see recovery listed with a bunch of characters when I do
Code:
adb devices
. I can run some adb commands, adb root tells me I have root, I can do "id" inside of adb shell. Though, whenever I try running any twrp commands inside adb shell, it says "TWRP does not appear to be running. Waiting for TWRP to start."
What can I do here? I also see SAMSUNG Android under devices on this linux distro I'm running but I am getting an mtp error whenever I try connecting to it.
Sorry to hear that. If your Samsung Galaxy Note 5 can be detected by the computer via USB cable connecting, and the USB debugging on it is enabled, try Coolmuster Android Backup Manager. Its free backup function can help transfer data to the computer for backup directly. It's easy and safe. Good luck to you.
nazhai said:
Sorry to hear that. If your Samsung Galaxy Note 5 can be detected by the computer via USB cable connecting, and the USB debugging on it is enabled, try Coolmuster Android Backup Manager. Its free backup function can help transfer data to the computer for backup directly. It's easy and safe. Good luck to you.
Click to expand...
Click to collapse
It doesn't seem to be working, well at least not when the phone's in recovery. I'm not sure if I can boot it up normally.
tesiz22 said:
I have a Galaxy Note 5 and I have important data in it. The screen is broken so I can't do anything, but I see recovery listed with a bunch of characters when I do
Code:
adb devices
.
Click to expand...
Click to collapse
Indicates your phone boots into Recovery mode and not into Normal ( ADB ) mode.
To get rid off of booting into Recovery mode you run
Code:
adb devices
adb reboot
Once your phone boots into Normal mode you can pull out the data of interest: take note that adb pull has a size limit, hence probably
Code:
adb pull /sdcard C:\PULLED-DATA
doesn't work as expected if amount of data to pull is >= 2GB in total ( e.g. a stored movie file may have up to 8GB ). That means, to be on safe side, you have to pull the files of interest one-by-one.

Backup with Smart Switch a black screen Galaxy S5 (Unauthorised device in adb - Root - Usb debugging ON - Unlock patern OK - Recovery accessible)

Hi,
I think I've already explain everything in title.
My Galaxy S5 on Android 8 (I think) as her screen broken (black)
Before that it already wokr badly and slowly. I bought a new phone but this one break just before I can transfer data.
I can unlock the patern (I know that because the volume + buton react)
Smart switch say that the phone is locked (even it's not true). Tested on 2 PC
The phone appear in Windows but no file or folder appear.
In adb the device is shown unauthorised and even if I click where the message to unlock should be, notihng append.
The phone is connected on Wifi, apparear in Google Find it but not Samsung find it...
I think that it's already to much information...
My question : how can I do the unlock the phone and do a smart switch backup ? or an other way to transfer data.
Regards
James
The Samsung Galaxy S10 comes with a USB OTG adapter. OTG stands for "On the Go" and is used for the connection between smartphone and USB stick / cable. Connect this USB OTG adapter to the USB Type C port of your Samsung, then connect the USB OTG adapter with USB Type C port of your computer.
You should see the data stored on your Samsung.
jwoegerbauer said:
The Samsung Galaxy S10 comes with a USB OTG adapter. OTG stands for "On the Go" and is used for the connection between smartphone and USB stick / cable. Connect this USB OTG adapter to the USB Type C port of your Samsung, then connect the USB OTG adapter with USB Type C port of your computer.
You should see the data stored on your Samsung.
Click to expand...
Click to collapse
It's an S5. But I have a OTG adaptor for it but my new phone A52s doesn't connect to the S5.
I try with a S7 but I can see that there is a lot autorisation to give on the old phone which will be very hard to do with a black screen.
If ADB is unauthorized, the only way to back up any data would be via a custom recovery. That would require that the device have an unlocked bootloader though
iBowToAndroid said:
If ADB is unauthorized, the only way to back up any data would be via a custom recovery. That would require that the device have an unlocked bootloader though
Click to expand...
Click to collapse
ADB authorised is not require for Smart Switch... I think
And my device have access to recovery and it's root so the bootloader is unlocked.
jameslevalaisan said:
ADB authorised is not require for Smart Switch... I think
And my device have access to recovery and it's root so the bootloader is unlocked.
Click to expand...
Click to collapse
So then flash a custom recovery, and then enter it. That will either give you MTP access to the files and folders, or ADB should also be enabled - and does not require authorization
iBowToAndroid said:
So then flash a custom recovery, and then enter it. That will either give you MTP access to the files and folders, or ADB should also be enabled - and does not require authorization
Click to expand...
Click to collapse
purehaps you have forget that the screen is broken. I can't access the phone for complicated manipulation. I'have already have TWRP installed on it but without a view it's impossible to manipulate it. Also, it's not normal that the phone are not viewed on windows or is shown locked on smart switch.
In recovery mode, the phone isn't show on windows also. Find the MTP option in TWRP without a screen view is very diffucult and dangerous, (the wipe option are near)
If I can access file on phone I will be able to view screenshot and configure it.
jameslevalaisan said:
purehaps you have forget that the screen is broken. I can't access the phone for complicated manipulation. I'have already have TWRP installed on it but without a view it's impossible to manipulate it. Also, it's not normal that the phone are not viewed on windows or is shown locked on smart switch.
In recovery mode, the phone isn't show on windows also. Find the MTP option in TWRP without a screen view is very diffucult and dangerous, (the wipe option are near)
If I can access file on phone I will be able to view screenshot and configure it.
Click to expand...
Click to collapse
1. No, I didn't forget that the screen is broken
2. I wasn't telling you to press anything in TWRP. When it's in TWRP and you plug it in, you will either get MTP and/or ADB access automatically
3. Yes, it is perfectly normal to not have access to the files and folders in Windows, when it's powered on normally. There's a popup on the phone that you have to tap in order to grant permission to the folders and files. That's why it shows up as an empty device when you plug it in while in normal mode
iBowToAndroid said:
1. No, I didn't forget that the screen is broken
2. I wasn't telling you to press anything in TWRP. When it's in TWRP and you plug it in, you will either get MTP and/or ADB access automatically
3. Yes, it is perfectly normal to not have access to the files and folders in Windows, when it's powered on normally. There's a popup on the phone that you have to tap in order to grant permission to the folders and files. That's why it shows up as an empty device when you plug it in while in normal mode
Click to expand...
Click to collapse
Ok excuse me.
Hum when I'm in recovery mode, my phone doesn't appear in Widows. And in adb, I haven't access to all folder. Data is empty for exemple.
For 3. Ok, I don't remember this notification. But I'm shure that I'have already use this phone with my PC. If I wasn't able to ring it on Whastapp, I will think that the phone doesn't works anymore at all. But it's not the case.
jameslevalaisan said:
purehaps you have forget that the screen is broken. I can't access the phone for complicated manipulation. I'have already have TWRP installed on it but without a view it's impossible to manipulate it. Also, it's not normal that the phone are not viewed on windows or is shown locked on smart switch.
In recovery mode, the phone isn't show on windows also. Find the MTP option in TWRP without a screen view is very diffucult and dangerous, (the wipe option are near)
If I can access file on phone I will be able to view screenshot and configure it.
Click to expand...
Click to collapse
ADB commands work by default while in TWRP, you can back up almost anything that your TWRP version allows through your PC using ADB commands, TWRP will serve as intermediary, but you will not go to operate over your broken screen device but through your ADB/fastboot CMD.
In normal mode I can unlock the phone but after that even if I click where the message should appear it doesn't do anything.
In adb I can't access a backup command (and if I can do this, It will not the easyer way to transfer my sms.)
I have some old other phones to see some message exemple and know where to clic but it doesn't works. I have install Vyzor, It asks me a permission but even if I tap in the right of the screen the permission doesn't works.
I also try to transfert a new adb key but I think it doesn't work because Wyzor still ask permission.
jameslevalaisan said:
In normal mode I can unlock the phone but after that even if I click where the message should appear it doesn't do anything.
In adb I can't access a backup command (and if I can do this, It will not the easyer way to transfer my sms.)
Click to expand...
Click to collapse
There is no backup command in ADB that you can use. And the reason that you can't access /data is because that requires going into TWRP settings and mounting the system partition.
What you can do in TWRP is to adb pull all of the files and folders off of the internal storage
Other thing, I can phone my phone with Whatsapp but I can't click to hang off.
iBowToAndroid said:
There is no backup command in ADB that you can use. And the reason that you can't access /data is because that requires going into TWRP settings and mounting the system partition.
What you can do in TWRP is to adb pull all of the files and folders off of the internal storage
Click to expand...
Click to collapse
ok to do have a exemple of command to tap ?
And there no way to just be able to connect my phone with smart switch on windows ?
jameslevalaisan said:
I have some old other phones to see some message exemple and know where to clic but it doesn't works. I have install Vyzor, It asks me a permission but even if I tap in the right of the screen the permission doesn't works.
I also try to transfert a new adb key but I think it doesn't work because Wyzor still ask permission.
Click to expand...
Click to collapse
ADB backup is not to operate while your device is on, but it is to operate while your device is in TWRP mode.
TWRP has integrated by default the ADB options not need to authorize through your broken screen because it is already authorized.
Messages as an app user (the same with root or system user) is part of userdata, you want to back up userdata to restore it after in other device or a scenery where your device get repaired, no?
I'll give you an example, you have to use this command, create a folder on a convenient place onto your PC directory, something like "BACKUP", assuming that you set it up correctly the environment for ADB/fastboot to use it along all of your system, you should open from this newly created folder an CMD (I use the new Windows terminal for easy/comfortable results) then type from the terminal adb shell twrp backup userdata , you'll have the userdata backed up in your PC in less of 2 minutes depending on the size of the partition, and so on successively.
What you can back up from TWRP depends on the restrictions from your TWRP version, you should back up the normal that you can see from the TWRP screen and even more but for example if your TWRP have some issues mounting vendor partition of course the ADB commands can't do the job for this specific partition, but anyway you have a lot you can do through it.
jameslevalaisan said:
ok to do have a exemple of command to tap ?
And there no way to just be able to connect my phone with smart switch on windows ?
Click to expand...
Click to collapse
1. The command depends on what the mount point for your internal storage is. The command would be "adb pull /(mount point)" , so it could be:
adb pull /sdcard
adb pull /storage0/sdcard
Or several others
2. No, you can't connect with Smart Switch without allowing permission on the popup box on the phone screen
Hi guys,
I'm very happy to find here some people to help me. thank you a lot. I just now in recovery mode.
here is some result of command
Code:
adb devices
List of devices attached
487e969e recovery
adb root
adbd is already running as root
adb shell
~ # ls
cache init.recovery.qcom.rc selinux_version
charger init.recovery.service.rc sepolicy
data init.recovery.usb.rc service_contexts
default.prop license sideload
dev oem sys
etc prebuilt_file_contexts system
file_contexts proc tmp
fstab.qcom property_contexts twres
init res ueventd.qcom.rc
init.rc root ueventd.rc
init.recovery.hlthchrg.rc sbin vendor
init.recovery.nano.rc seapp_contexts
~ #
as you can see there is not storage in the ls result
Code:
~ # ls /res
images keys
~ # ls /data
~ # ls /data
Code:
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db ./
adb: error: remote object '/data/data/com.android.providers.telephony/databases/mmssms.db' does not exist
Is there something inspired you ?
iBowToAndroid said:
1. The command depends on what the mount point for your internal storage is. The command would be "adb pull /(mount point)" , so it could be:
adb pull /sdcard
adb pull /storage0/sdcard
Or several others
2. No, you can't connect with Smart Switch without allowing permission on the popup box on the phone screen
Click to expand...
Click to collapse
1. the ls command doesn't show any sdcard or storage
2. Ok bit wyh I can't click on the permission popup ?
SubwayChamp said:
ADB backup is not to operate while your device is on, but it is to operate while your device is in TWRP mode.
TWRP has integrated by default the ADB options not need to authorize through your broken screen because it is already authorized.
Messages as an app user (the same with root or system user) is part of userdata, you want to back up userdata to restore it after in other device or a scenery where your device get repaired, no?
I'll give you an example, you have to use this command, create a folder on a convenient place onto your PC directory, something like "BACKUP", assuming that you set it up correctly the environment for ADB/fastboot to use it along all of your system, you should open from this newly created folder an CMD (I use the new Windows terminal for easy/comfortable results) then type from the terminal adb shell twrp backup userdata , you'll have the userdata backed up in your PC in less of 2 minutes depending on the size of the partition, and so on successively.
What you can back up from TWRP depends on the restrictions from your TWRP version, you should back up the normal that you can see from the TWRP screen and even more but for example if your TWRP have some issues mounting vendor partition of course the ADB commands can't do the job for this specific partition, but anyway you have a lot you can do through it.
Click to expand...
Click to collapse
I try this...
C:\Users\James-23\AppData\Local\Android\Sdk\platform-tools>adb shell twrp backup userdata
TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit.
^C
C:\Users\James-23\AppData\Local\Android\Sdk\platform-tools>adb shell twrp plat-form-tools userdata
TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit.
^C
I'm not sure I understand your command. But it return a result. "Backup" is the name of a folder ? or it's a commande for twrp ?
Is there a way to be sure that twrp is installed (with all my phone, sometime, I don't remember what is on it. The thing it's sure it that this phone is root because I use root function with some app but perhaps just with magisk or Super SU.

Question Write to /data/... folder

I just switched to the Pixel 6a and have botched something with an app I use.
I have the app's files from the old phone, which were in /data/data/com... folder, and want to overwrite files on the new phone, with them.
I did "adb pull ..." on the old phone to get files on the computer and intended to do "adb push ..." to the new,
but I can't get it to connect to adb, in recovery mode.
The old phone had TWRP.
When I rebooted it into recovery and connected with cable to PC, "adb devices" would print:
List of devices attached
<device_ID> recovery
On the new one, when I go into recovery (stock), "adb devices" prints nothing.
When I select the sideload option, "adb devices" prints:
<device_ID> sideload
In this sideload mode, the pull, push, shell... adb commands don't work.
How can I get the Pixel 6a to connect to the computer so that "adb devices" prints:
<device_ID> recovery
?
Stock recovery isn't TWRP! You have no access to anything in your file system.
Svrmirac said:
How can I get the Pixel 6a to connect to the computer so that "adb devices" prints:
<device_ID> recovery
?
Click to expand...
Click to collapse
Use TWRP. Stock recovery has no adbd, only a minimal adbd with no features except a sideload option for signed update.zips
Thank you for the suggestion, @WoKoschekk, but I don't think I can do that.
If I understand correctly, I have to unlock the bootloader to load TWRP.
With an unlocked bootloader, my banking app stops working, which is unacceptable,
and re-locking it apparently wipes all data, which I just jumped through hoops overwriting.
I seem to be at an impasse, with the stock ROM/recovery.
Svrmirac said:
If I understand correctly, I have to unlock the bootloader to load TWRP.
With an unlocked bootloader, my banking app stops working, which is unacceptable,
and re-locking it apparently wipes all data, which I just jumped through hoops overwriting.
Click to expand...
Click to collapse
Yes, (un-)locking wipes all data. But that is exactly the reason why /data is inaccessible from recovery. To keep your data safe.
I don't even think TWRP is a thing for modern pixels
ctfrommn said:
I don't even think TWRP is a thing for modern pixels
Click to expand...
Click to collapse
No it isn't the closing thing you'll find to TWRP on Pixel 6A is the Lineage Recovery.
I would suggest using a tool like Titanium Backup. That allows the saving and reinstating of apps.
Booting a custom recovery requires unlocking the bootlader, which I don't want to do now.
Titanium backup requires rooting as well...
Thank you for the suggestions but I'm counting this one as lost.
You won't be able to directly write to the /data/data/com.your.packagename folder without root. The only options I can think of are
1. Using adb backup... backup your app data from your old phone and restore it to the new phone
Bash:
To backup
# adb backup -noapk com.your.packagename -f backup.adb
To restore
# adb restore backup.adb
2. If the app in question is debuggable, you can assume the application permission and access the folder
Bash:
# adb shell
bluejay:/ $ run-as com.your.packagename
bluejay:/ $ cp -r /storage/emulated/0/Download/backup/* /data/data/com.your.packagename

Categories

Resources