NO read user data files

wlawal

Mobile is Dead,,,,,huawei y6 emmc kmqe10013m Internal Data Possible to Recover..
First i Read User Data File......(10.7Gb)
then i open with UFI file system Browser.......
ufi Box Say--- Not supported filesystem !

I Done Many Mobile on This Way

any Solution.........

wlawal

User area: 14.56 GiB(15,634,268,160 bytes)
Cache size: 64 MiB
Hardware reset function: 1
Partition configuration: 0x08
No boot acknowledge is sent (default)
Boot partition 1 is enabled for boot
Partitioning support: 0x07
Device support partitioning feature
Device can have enhanced technological features
Device partitioning possible
Boot configuration protection: 0x00
Boot bus conditions: 0x02
Bus width: x8 (sdr/ddr), boot mode: sdr(default), reset bus width to x1 sdr(default)
Boot area write protection: 0x00
Power-on write protection: possible
Permanent write protection: possible
Lock status: not locked
User area write protection: 0x50
Password protection features: enabled
Power-on write protection: possible
Permanent write protection: not possible
Lock status: not locked

ANDROID ROM info:
platform: hi6210sft, cpu abi: arm64-v8a
manufacturer: HUAWEI
board: BalongV8R1SFT, name: hi6210sft
brand: hi6210sft, model: hi6210sft
build id: MRA58K, version: 6.0 Marshmallow ()

Custom moviNAND command is not supported for this device(MMC51).
Selected: [SAMSUNG] KMQE10013M-B318/16GB+LPDDR3 16Gb (BGA221)

madgoeslim

wlawal version: 6.0 Marshmallow

For Android 6.0 and above, userdata is encrypted, so its not supported for file system browser to explore the content inside raw files.

umair

madgoeslim is there anyway to recover data in android 6.0 or above??

hermann07

madgoeslim

hermann07

madgoeslim what about this ? samsung j700 android 6.0 data recovery done

https://www.youtube.com/watch?v=ftUiFerszyY

madgoeslim

umair As long as the user data has been decrypted, if only the user understands the process, then it is possible.
But if for forensic purposes, for example if the phone died, then impossible for now.

cucipiring

try this method
https://bit.ly/2LanWAf

smgroupranchi

Connection status: EHCI:HUB:HUB:USB 2.0 High-Speed
Interface: UFI High-Speed
Serial number: 0011-8840-0808
Boot version: 1.04, FW version: 1.12 (Jun 7 2018 00:06:47)
Insertion test... Done.
Init bus...
VCC: 3.3 V, VCCQ: 3.0 V
Bus: 8 bit (HS SDR 52MHz)
Access mode: sector mode
Power supply: dual-voltage (1.70-1.95V, 2.7-3.6V)
Card/BGA: BGA (Discrete embedded) - High density MMC
Manufacturer ID: 0x15 (Samsung)
Product name: RH64AB (0x524836344142), rev: 0x05, serial number: 0x0BBDD44B
Manufacturing date: Mar 2018
CID: 15010052 48363441 42050BBD D44B3506
CSD: D0270132 0F5903FF F6DBFFEF 8E40400C
EXT_CSD revision: 1.8 (MMC v5.1)
Partition info:
Boot1: 4096 KiB
Boot2: 4096 KiB
RPMB: 4096 KiB
User area: 58.24 GiB(62,537,072,640 bytes)
Cache size: 64 MiB
Hardware reset function: 1
Partition configuration: 0x38
No boot acknowledge is sent (default)
User area is enabled for boot
Partitioning support: 0x07
Device support partitioning feature
Device can have enhanced technological features
Device partitioning possible
Boot configuration protection: 0x00
Boot bus conditions: 0x00
Boot area write protection: 0x00
Power-on write protection: possible
Permanent write protection: possible
Lock status: not locked
EXT_CSD backup saved to "\%BACKUPS%\RH64AB_0BBDD44B.ext_csd"

ANDROID System Info:
platform: msm8953, cpu abi: arm64-v8a
manufacturer: Xiaomi
board: msm8953, name: vince
brand: xiaomi, model: Redmi 5 Plus
build id: N2G47H, version: 7.1.2 Nougat (ZQL1711-vince-build-20180710172756)
build description: vince-user 7.1.2 N2G47H V9.6.4.0.NEGMIFD release-keys

crypto state: encrypted?
Custom moviNAND command is not supported for this device(MMC51).
Selected: [SAMSUNG] KMRH60014A-B614/64GB (BGA221)

hilf u sir ufi tem

smgroupranchi

dead mobile redmi data recovire

no recavire hilf sir

Ahmed24

How about this case,
Please reply ,i have same problem ,cannot recovery data .

rudd-o

Have anyone tried to copy dumped data on another working phone and try to get data from there ?

DjalmaFonseca

rudd-o Very interesting your point of view! Something that We must try.
Let's make one Whats group to talk about this process! My number +55 19982290220

madgoeslim

rudd-o Hello,
Just to be clear, on Android Marsmallow and later, there are features called FDE (Full Disk Encryption) that bind userdata partition after user set the password. If you try to make dump full emmc and put in another device, even if you got success, kernel will force encrypt, ask for password to decrypt userdata, if you don't have the password, then the only solution is just format these userdata partition.

vicky927

DjalmaFonseca had you try this to get data?

rudd-o

in my situation the eMMC of a fully damaged redmi note 5 was dumbed but owner confirmed that never had a password so the most possible reason of USERDATA partition was selfencrypted by Qualcomm SOC/Xiaomi

So it may possible to write whole emmc data on another working phone and may work as the SYSTEM and rest partition with IMEI , SN uuid and other data are intact.

madgoeslim

rudd-o Hello,
We are currently under Secure Device Era. Encrypted and sign image is not possible to decrypt, and every device is built in their secure ID, so if other images , for ex: userdata, put in another phone, the load and verify by cryptographic algoritm will end up by resetting all data to their default.

Dhanush

we cant recovery it

rudd-o

madgoeslim The only way is transfer CPU/eMMC ... as logical partition is "married with" CPU like apple devices but less complicated..

joy

what is the difference between user area and userdata?
explian me i am new...

madgoeslim

Jane Yes, you are right.

joy If you want to know more, you can join with us in class : ufi academy

Jane

As I understand:
User area is a part of eMMC and user data( e.g password) are inside of that User area