Database Users

TWRP - Can't Mount, internal Storage 0MB

So I wanted to install Blackball's Genesis ROM on my AL00 P10+. Unlocked bootloader just fine, installed TWRP, which appeared to work OK as well. When I boot into TWRP though (and I tried various versions already); I can't do much. Internal Storage is not recognized, shown as 0MB (SD card storage is recognized though). I can't mount anything other than my SD card, Wiping anything just gives error messages about being unable to mount xyz. Backup screen shows me no partitions to back up.
Things I have already tried from searching other threads:
- fastboot format userdata (command not allowed)
- Set a PIN in settings (never being asked for it in TWRP as I supposedly should be)
- advanced Wipe, change file system (already all on ext4, no effect)
- Switch off any encryption (switched off TrustSpace with no effect, nothing else found)
Any hint on where else to look or how to facilitate debugging my issue would be much appreciated!

Did you tried to install the rom in twrp?
Did you format data in twrp so you can see the internal storage.
Before doing anything,do a backup in twrp at least for oeminfo.

No, I never get to the point of installing anything and I have nothing to select for backup. How would I go about formatting?

khaberz said:
So I wanted to install Blackball's Genesis ROM on my AL00 P10+. Unlocked bootloader just fine, installed TWRP, which appeared to work OK as well. When I boot into TWRP though (and I tried various versions already); I can't do much. Internal Storage is not recognized, shown as 0MB (SD card storage is recognized though). I can't mount anything other than my SD card, Wiping anything just gives error messages about being unable to mount xyz. Backup screen shows me no partitions to back up.
Things I have already tried from searching other threads:
- fastboot format userdata (command not allowed)
- Set a PIN in settings (never being asked for it in TWRP as I supposedly should be)
- advanced Wipe, change file system (already all on ext4, no effect)
- Switch off any encryption (switched off TrustSpace with no effect, nothing else found)
Any hint on where else to look or how to facilitate debugging my issue would be much appreciated!
Click to expand...
Click to collapse
use it
drive.google.com/open?id=0B-NCtYJ6s_GAUHI1QW1PS0EwUHRNdEhvckVHckVKcU9KNENR

nguyennc said:
use it
drive.google.com/open?id=0B-NCtYJ6s_GAUHI1QW1PS0EwUHRNdEhvckVHckVKcU9KNENR
Click to expand...
Click to collapse
Thank you so much - this resolved it. Much appreciated!
Now I am getting a lot of failed to mount /dev/block/platform/ff3b0000 - will research and check in the ROM thread on this.
Thanks again!

khaberz said:
Thank you so much - this resolved it. Much appreciated!
Now I am getting a lot of failed to mount /dev/block/platform/ff3b0000 - will research and check in the ROM thread on this.
Thanks again!
Click to expand...
Click to collapse
All ROM is not support for AL00.
You should convert AL00 to L29.

nguyennc said:
All ROM is not support for AL00.
You should convert AL00 to L29.
Click to expand...
Click to collapse
According to https://forum.xda-developers.com/p10-plus/development/rom-fromfuture-genesis-b150-t3617126 AL00 is supported with the right datafiles. Or am I missing something?

khaberz said:
According to https://forum.xda-developers.com/p10-plus/development/rom-fromfuture-genesis-b150-t3617126 AL00 is supported with the right datafiles. Or am I missing something?
Click to expand...
Click to collapse
I had tried everything. But partitions not compatible.

nguyennc said:
I had tried everything. But partitions not compatible.
Click to expand...
Click to collapse
I see...where did you get the L29 image?

khaberz said:
I see...where did you get the L29 image?
Click to expand...
Click to collapse
* You try. I hope you will succeed. But not ok for me.
1. https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
2. https://forum.xda-developers.com/p1...nvert-to-dualsim-huawei-p10-plus-vky-t3605071
* 100% success. I had buy 5 Credits and used 2. If you need, I will send free.
https://funkyhuawei.club/rebranding

nguyennc said:
* You try. I hope you will succeed. But not ok for me.
1. https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
2. https://forum.xda-developers.com/p1...nvert-to-dualsim-huawei-p10-plus-vky-t3605071
* 100% success. I had buy 5 Credits and used 2. If you need, I will send free.
https://funkyhuawei.club/rebranding
Click to expand...
Click to collapse
Thanks a lot! I have Blackball looking at the problem in the ROM thread now. If he can't resolve it, I'll do that. Thank you!

Just to wrap this up for now: I did rebrand to L29 via funkyhuawei, found a TWRP that could read my filesystems (from https://forum.xda-developers.com/p10/development/testers-twrp-t3585256 ). Now I get Error 7 installing any ROM. No idea why. I went back to original AL00.
Any attempts to just root the device have failed as well.
From some other threads, there is some indication that my EMMC storage causes problems with some TWRPs. Most devices purchased in Europe have UFS and are therefore not affected.
Right now, I am keeping my eyes out for a TWRP that may work with my device.

nguyennc said:
use it
drive.google.com/open?id=0B-NCtYJ6s_GAUHI1QW1PS0EwUHRNdEhvckVHckVKcU9KNENR
Click to expand...
Click to collapse
Is that reliable?
Problem solved through link:
https://forum.xda-developers.com/ga...-twrp-oreo-t3769254/post76036701#post76036701

TWRP 3.2.1 for H901

The following is the latest version of TWRP compiled for the T-mobile V10 Model H901.
https://androidfilehost.com/?fid=818070582850501883
MD5SUM: b89d341cd61da31a5348d8f6b3c75c97
The heavy lifting was done by the twrpbuilder project who were generous enough to compile TWRP for our device. They also provide their services to see TWRP is available for devices that don't yet have it. I've personally used this version to do a backup and restore but can't guarantee there won't be issues. If there are while you are still in twrp you should go to the advanced section and copy the log to your external sd card. This log will help them diagnose any issues.
The project is located at: https://twrpbuilder.github.io
Their XDA thread is located here: https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253
If you already have TWRP installed installation is as follows: Click Install, choose Image file, navigate to where the TWRP img file is located on your external sdcard and flash that img to the recovery partition. Back out to the root dir and you can select reboot then recovery...it should bounce you right back into recovery and you should see the new version loaded. If you have root in the rom and run into issues the app "flashify" can reflash TWRP 3.0 so make sure you also have it's img available.
This is pretty much only for folks who already have twrp to update to the latest. If you are on nougat you are still stuck until an exploit is released that works for nougat the way dirtycow did for marshmallow and below. *update* an exploit to give root to nougat users is now available thanks to @runningnak3d here: https://forum.xda-developers.com/tmobile-lg-v10/general/root-h901-nougat-t3773942

Reserved Post #1

Reserved Post #2

famewolf said:
The following is the latest version of TWRP compiled for the T-mobile V10 Model H901.
https://www.androidfilehost.com/?fid=8180705828505018
MD5SUM: b89d341cd61da31a5348d8f6b3c75c97
Click to expand...
Click to collapse
Looks to me like that URL should read
https://androidfilehost.com/?fid=818070582850501883
[ EDIT ] Yup, confirmed.. The URL I listed works fine.
Thanks for the file!
:laugh::silly:

NYLimited said:
Looks to me like that URL should read
https://androidfilehost.com/?fid=818070582850501883
[ EDIT ] Yup, confirmed.. The URL I listed works fine.
Thanks for the file!
:laugh::silly:
Click to expand...
Click to collapse
You are correct. For some reason a few characters got truncated. I've corrected the url in post #1.

famewolf said:
The following is the latest version of TWRP compiled for the T-mobile V10 Model H901.
https://androidfilehost.com/?fid=818070582850501883
MD5SUM: b89d341cd61da31a5348d8f6b3c75c97
The heavy lifting was done by the twrpbuilder project who were generous enough to compile TWRP for our device. They also provide their services to see TWRP is available for devices that don't yet have it.
Click to expand...
Click to collapse
Just as an aside, this version seems to correct (mostly) the date issue of previous TWRP versions for the V10. Versions before this one used to generate a default date (folder name) for the backup dating back to the 1970s as I recall.
This one has the correct month and day and time and the year is only 1 off - it showed 2017 on my very quick attempt to play with it.
One additional note to those installing it via TWRP itself - after selecting image flash , MAKE SURE you specify RECOVERY partition, not BOOT! Specifying BOOT will most likely have some less than desirable results.. :laugh:

NYLimited said:
Just as an aside, this version seems to correct (mostly) the date issue of previous TWRP versions for the V10. Versions before this one used to generate a default date (folder name) for the backup dating back to the 1970s as I recall.
This one has the correct month and day and time and the year is only 1 off - it showed 2017 on my very quick attempt to play with it.
One additional note to those installing it via TWRP itself - after selecting image flash , MAKE SURE you specify RECOVERY partition, not BOOT! Specifying BOOT will most likely have some less than desirable results.. :laugh:
Click to expand...
Click to collapse
I've passed on the date issue. Uncertain if he'll generate another build though.

famewolf said:
I've passed on the date issue. Uncertain if he'll generate another build though.
Click to expand...
Click to collapse
Seems that either nobody is using this version or nobody knows about it or they just have nothing to say..
Anyway, as you know, I have spent a fair amount of time recently working with this and installing it. A couple of observations that may be worth noting..
I double checked and I did set a screen timeout on TWRP. Previous versions would first, dim the screen, followed by turning it off completely. If you had the device near you on a desk while backing up the screen lighting up again when TWRP completed was a sure signal that it was finished.
This version of TWRP dims the screen but the screen is never turned off completely. A minor annoyance I suppose but something is different from previous versions.
During the /data partition backup I noted a (to me) new display in yellow: "Backups of data do not include any files in internal storage such as pictures or downloads"
Seriously? Is this something new? Certainly the display is but I always kinda relied on all that being backed up with /data and having the ability to restore them. This is a more serious issue for me which may make me consider going backward..
Thoughts?

NYLimited said:
Seems that either nobody is using this version or nobody knows about it or they just have nothing to say..
Anyway, as you know, I have spent a fair amount of time recently working with this and installing it. A couple of observations that may be worth noting..
I double checked and I did set a screen timeout on TWRP. Previous versions would first, dim the screen, followed by turning it off completely. If you had the device near you on a desk while backing up the screen lighting up again when TWRP completed was a sure signal that it was finished.
This version of TWRP dims the screen but the screen is never turned off completely. A minor annoyance I suppose but something is different from previous versions.
During the /data partition backup I noted a (to me) new display in yellow: "Backups of data do not include any files in internal storage such as pictures or downloads"
Seriously? Is this something new? Certainly the display is but I always kinda relied on all that being backed up with /data and having the ability to restore them. This is a more serious issue for me which may make me consider going backward..
Thoughts?
Click to expand...
Click to collapse
I use my v10 as my backup phone now. On my HTC U11 life when I make a nandroid it shows that it is not backing up files on internal storage. I think this is normal now on the latest version of twrp.

NYLimited said:
Seems that either nobody is using this version or nobody knows about it or they just have nothing to say..
Anyway, as you know, I have spent a fair amount of time recently working with this and installing it. A couple of observations that may be worth noting..
I double checked and I did set a screen timeout on TWRP. Previous versions would first, dim the screen, followed by turning it off completely. If you had the device near you on a desk while backing up the screen lighting up again when TWRP completed was a sure signal that it was finished.
This version of TWRP dims the screen but the screen is never turned off completely. A minor annoyance I suppose but something is different from previous versions.
During the /data partition backup I noted a (to me) new display in yellow: "Backups of data do not include any files in internal storage such as pictures or downloads"
Seriously? Is this something new? Certainly the display is but I always kinda relied on all that being backed up with /data and having the ability to restore them. This is a more serious issue for me which may make me consider going backward..
Thoughts?
Click to expand...
Click to collapse
On your last issue this is business as usual...twrp has NEVER backed up the internal SDCARD unless you selected the sdcard entry in the list of sections to be backed up. DCIM (pictures) and the Downloads folder/dir have never been included.
As to the dimming, you can check in settings to see if something can be configured however each person compiling twrp can set their own options as to how they want it to function. There is no guarantee or expectation that Person B is going to use the same options as Person A. You are of course free to compile your own copy configured the way you would prefer it to behave but the process was enough of a pain in the butt I just requested twrpbuilder to generate one as I kept getting errors. The process to compile it also appears poorly documented.

sabresfan said:
I use my v10 as my backup phone now. On my HTC U11 life when I make a nandroid it shows that it is not backing up files on internal storage. I think this is normal now on the latest version of twrp.
Click to expand...
Click to collapse
I kinda suspected that but that is, at best, a questionable choice since I don't even have the option to check or uncheck a selection for it. Not happy..
famewolf said:
On your last issue this is business as usual...twrp has NEVER backed up the internal SDCARD unless you selected the sdcard entry in the list of sections to be backed up. DCIM (pictures) and the Downloads folder/dir have never been included.
Click to expand...
Click to collapse
Not quite. INTERNAL is not the SD Card. Internal is emulated sd on /0. In TWRP if you tap select storage, for example, you can pick "internal" or "SD" for backup destination, as one example.
I keep a fair number of things in /Download - things I grab in my travels, things I save there for later use.. whatever. I'll have to device a Tasker module or something for copying all those to the actual SD card...

NYLimited said:
I kinda suspected that but that is, at best, a questionable choice since I don't even have the option to check or uncheck a selection for it. Not happy..
Not quite. INTERNAL is not the SD Card. Internal is emulated sd on /0. In TWRP if you tap select storage, for example, you can pick "internal" or "SD" for backup destination, as one example.
I keep a fair number of things in /Download - things I grab in my travels, things I save there for later use.. whatever. I'll have to device a Tasker module or something for copying all those to the actual SD card...
Click to expand...
Click to collapse
A fairly recent app/utility created by @kdrag0n called Tipatch brings a long-needed resolution to the table regarding "full backups" of Data using TWRP. In a nutshell, Tipatch installs to your Android device as a basic APK. Within the simple GUI, once root permissions are granted (In-Place Patching) Tipatch will decompile, patch, recompile and flash the patched TWRP to /recovery, effectively patching your TWRP build to backup the contents of Internal Storage (emulated SD card) as part of Data itself, so that backups will now include those Internal Storage contents such as downloads, photos, videos, game data, and other various files. I've tried it on this particular build of TWRP and it works without any issues. There are options to patch TWRP without root permissions as well. There are Windows, Mac & Linux versions available too. If you are patching TWRP on a device with an A/B partitioning scheme, the patched TWRP can be installed on both A & B using a one-click option. Of course, one insurmountable caveat to patching TWRP with Tipatch is that wiping Data now will also wipe Internal Storage (emulated SD card). In short, the utility works on pretty well all device types and chipset platforms (Exynos, Kirin, Snapdragon, MediaTek, etc.). The latest Tipatch update, v1.6, includes support for TWRP builds that use LZMA compression, and removes the now-misleading notification previously listed when backing up Data -- that Internal Storage (/data/media/ path / emulated SD card) contents are not backed up. Anyway guys, here is a link to the Tipatch Discussion & Support thread: https://forum.xda-developers.com/android/apps-games/app-twrp-tipatch-backup-internal-t3831217
The latest Tipatch v1.6 app is also available on the Play Store and many other app & apk repos for Android. Versions for Windows, Mac and Linux can be downloaded using the above link.

Broken black screen - TWRP working but encrypted, & file transfer not enabled default

Broken black screen - TWRP working but encrypted, & file transfer not enabled default
Hi all, novice here
OnePlus 5
OxygenOS (OnePlus5Oxygen_23_OTA_040_all_1811051816_c6670cf.zip) I think.
rooted
twrp-3.2.3-0-20180822-codeworkx-cheeseburger.img
I dropped my phone and I think a car ran over it. Screen is black and touchscreen not functional. At first the screen was fragmented and I could see parts of my home screen, but now it is totally black. So I think the phone itself is functional.
I can boot to TWRP and use ADB. I can navigate through the internal files system. I wish to copy the files to my PC. If I navigate to /sdcard, the folders have names like "wvTioi91z2FNnyelsUoraA" which I assume means they are encrypted. I can researched for 4 days and tried multiple methods. I have tried commands like mount, twrp decrypt 14789 for my lock pattern, to no avail.
I have tried a program called [email protected] to simulate touchscreen movements after booting to the system, but I'm flying blind.
I guess I want to know if this is all futile. I want to get my data off before I send it to OnePlus to get fixed because they will likely wipe it.
If I could somehow swipe down from the top when booted to the system and select MTP mode or whatever, I should be fine. But this is not working. Can I flash a different TWRP without losing data while removing encryption? I am not sure if I have USB debug mode on or off.
Any advice would be highly appreciated.

I had the same problem. But twrp decrypt <lockpattern> was the solution for me.
No idea why it do not work for you.
If you can get it into fastmode you could theoretically flash or just boot any recover you want without wiping anything.

Qnorsten said:
I had the same problem. But twrp decrypt <lockpattern> was the solution for me.
No idea why it do not work for you.
If you can get it into fastmode you could theoretically flash or just boot any recover you want without wiping anything.
Click to expand...
Click to collapse
Thanks. I think Android is having trouble matching the passwords.
Attempting to decrypt data partition via command line.
Iecrypting FBE for user 0
password filename is '/data/system/gatekeeper.pattern.key'
get_ce_key_directory_path 0: /data/misc/vold/user_keys/ce/0
Skipping non-key .Skipping non-key ..get_ce_key_paths adding: /data/misc/vold/user_keys/ce/0/current
Trying user CE key /data/misc/vold/user_keys/ce/0/currentOpenssl error: 0Failed to find working ce key for user 0Couldn't read key for 0e4crypt_unlock_user_key returned fail
I have another OnePlus 5 with Pie installed. After this error, I copied gatekeeper.pattern.key and then all of the contents in /data/system from my other OnePlus 5 to my broken OnePlus 5. It did not work.
I'm trying to make all of the encrypted passwords match somehow.

Encryption Questions

In Settings > Security & Location > Encryption & Credentials it says, "Phone not encrypted".
I want to encrypt my phone to protect the data in case I lose the phone, but is it working? Any important things I should know?
My key concerns:
1. Will I still be able to do OTA updates of LineageOS microG after encrypting?
2. Will I be able to backup phone using TWRP?
3. Will I be able to restore backups with TWRP?
4. Can I decrypt backups using TWRP to get my data?
I found a bunch of old threads from 2014 and it sounded unstable to encrypt. I don't see newer threads though.
Thank you for any guidance you may be able to provide as I am a LineageOS noob (less than 1 month experience!) .

Before this official TWRP update it was not working.
I encrypted my phone before one month ago. when i downloaded and installed the OTA update, the decryption pattern did not recognized. I was damn sure about the correct pattern to unlock but it didn't worked. I need to reset my phone to make it working.
I am not sure if its working now after updates from both TWRP and Lineage os.
please reply if any one know about current situation.
[NOTE]: If you are noob and trying to encrypt your phone, then keep backup of your internal storage and all apps, Sms and Contacts etc. because, after encryption, you can not access files and appdata from internal storage.

[email protected] said:
I encrypted my phone before one month ago. when i downloaded and installed the OTA update, the decryption pattern did not recognized. I was damn sure about the correct pattern to unlock but it didn't worked. I need to reset my phone to make it working.
Click to expand...
Click to collapse
Thank you for this! Possibly saved me. I don't care about accessing my encrypted data through TWRP, but I do want to be able to do OTA. I also want my data protected if I lose my phone.
In the latest release of TWRP 3.4.0-0 there seem to have done lots of work on encryption
Encryption
ext4Crypt Wrapped Key Update - Peter Cai
Fix upgrading encryption key if export fails - Peter Cai
Fix wrapped key support for devices without metadata partition - mauronofrio
Don't skip decryption when using block map file in order to write to /data in ORS - CaptainThrowback
FDE - Decrypt master key first - AndroidableDroid
vold_decrypt - set Android version and patch level automatically - CaptainThrowback
Set wrapped decrypt support by twrp flag - Peter Cai
Don't try wrapped support unless needed - mauronofrio
restore ext4 policy on /data/cache - Bigbiff
multiuser decryption - Noah Jacobson
FDE retry - AndroidableDroid
Click to expand...
Click to collapse
So, tell me about encryption. posted on Reddit --> This thread from 2 years ago on reddit has some phones working with encryption and some not working.
So who else is running full disk encryption on their LineageOS install? I guess I have to try it and pray next week.

Dr Fone recovery option messed up my phone getting "Enter your password to start up device" and No support single sku

When I plugin my Samsung Galaxy J7 Prime and then select recovery module and it show as connected and then I select android data recovery option and then select recover documents only and then click next. Then it show and detected device model, downloading package and it went like that till 99% uncertain if it hit 100% or not and then it caused my device to reboot and after it reboot now it is asking for a password to start up device but I tried device screen password, google account password and samsung account password but all didnt work. Thus it shows have 7 attempts left before factory reset itself.
The boot up looks a bit different from normal too, unsure if it is coming through a different type of boot and if there is a way to reverse to how it was earlier?
In recovery mode it shows in recovery log pid 2064 ran. where first line filesystem table code was;
0/ efs ext4/ dev/block/platform/1354000.dwmmc0/by-name/EFS(/dev/block/mmcblk0p3) 0
and in following
#ls /cache/recovery
ksmg
-rw------root root 8190724 2022-04-02 11:19 last_ode_dumpstate_err_check_password.log
From what I could see further in log it seems like maybe dr fone tried to root phone since I see files seem to have been overwritten probably as same file name shown where earlier recorded in time stamp as either 2017 or 2008 and underneath that dst is run with today tim stamp.
What would be method to solve to get back to normal working state without any data loss?
It seems when check via dr fone transfer showing as mem capacity 2797mb and 1362mb used whereas it should show as 32Gb, also when start up it says Enter your password to start up your device but I am certain I enter correct passwords but it is not verifying. Also in recovery mode it shows No support single sku supported api:3.
And when try backup option no files come up on scan does that mean the Dr fone recovery package that it installed wiped out the data? Or is it like in another different boot system for recovery? How to solve this problem?
Also any backup software you think could backup stuff before applying any drastic fixes

I think your phone internal storage is corrupted because of Dr. Fone and this is caused by the data encryption inside the phone and I think that it requires the encryption password, and to solve this problem, you must flash a modified recovery like TWRP or CWM and then pull all the data by making a MOUNT of the internal storage it will only works on old Android version 6.x or 7.x but you can try

My android is 6.0.1 so I think it should work, do you have any video tutorials or a thread with stepwise instructions to get twrp or cwm to backup current data and later restore?
Also any idea if use the dr fone repair device feature it might fix?

Dr.Fone only one thing do transfer WhatsApp chat between android and iOS all else features not work perfect so try another way, ask google how mount internal storage on android phones by twrp it’s easy and not need a tutorial just flash a custom recovery and don’t let device to boot enter recovery mode immediately and go to mount and press mtp or mount storage

Looks like the device name has got renamed as well best try to see if have a file explorer or manager for android so can see if files still intact? Any pc softwares that can be used to clarify without need to unlock screen since it is asking for a pass saying Enter your password to start up your device but I am certain I enter correct passwords but it is not verifying.
If the files are intact then I can try twrp or odin cf root flashing to see if can flash home version file so files possibly stay intact. Or if they are anyways not then will try factory reset via recovery mode and then will need recommendation of good software to recover data for free
Any ideas?

That app is trashware. Do Not use!
If a factory reset doesn't clear it you'll need to reflash the stock rom.
The data is lost... that's my opinion.
Always backup all critical data redundantly to at least two hdds that are physically and electronically isolated from each other and the PC... or you will lose data, eventually!
NEVER encrypt a data backup drive.
Do copy/paste file transfer, verify file size and folder count match. Test for readability.
NEVER clone music data bases, copy/paste only.
Do not use compression or apps like SmartSwitch to backup critical data, they can fail you miserably.
You can never have too many backup data drive. Avoid using flash memory; quality hdds have better memory retainment. Store in more than one location. Near lightning strikes can wipe them; a metal earth grounded box or safe is best.

blackhawk said:
That app is trashware. Do Not use!
If a factory reset doesn't clear it you'll need to reflash the stock rom.
The data is lost... that's my opinion.
Always backup all critical data redundantly to at least two hdds that are physically and electronically isolated from each other and the PC... or you will lose data, eventually!
NEVER encrypt a data backup drive.
Do copy/paste file transfer, verify file size and folder count match. Test for readability.
NEVER clone music data bases, copy/paste only.
Do not use compression or apps like SmartSwitch to backup critical data, they can fail you miserably.
You can never have too many backup data drive. Avoid using flash memory; quality hdds have better memory retainment. Store in more than one location. Near lightning strikes can wipe them; a metal earth grounded box or safe is best.
Click to expand...
Click to collapse
Can you recommend a free pc software that could possibly backup device in current state? Or a free pc software that could do data recovery without need to root phone so if I do go ahead with flash and it wipes data or i do factory reset then I could try to get backup data.

NW_Work said:
Can you recommend a free pc software that could possibly backup device in current state? Or a free pc software that could do data recovery without need to root phone so if I do go ahead with flash and it wipes data or i do factory reset then I could try to get backup data.
Click to expand...
Click to collapse
Not on an unrooted phone. You can try this.
If you used Drfone it has likely already encrypted the data with their own encryption key.
Hopefully some of your data is backed up somewhere else because this is a dead horse... I believe.
I be more concerned about salvaging the phone at this point. It's a tough lesson from the U of hard knocks... don't repeat it. Sorry.