All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 32 posts ]  Go to page 1, 2  Next
Author Message
 Post subject: eMMC chip access
PostPosted: January 17th, 2019, 14:36 
Offline

Joined: January 17th, 2019, 14:14
Posts: 14
Location: United Kingdom
I have been struggling via various methods to access the data on the eMMC drive of my laptop.

I tried using an e-Mate by MOORC correctly using the data sheet

I then sent it to a mobile phone specialist centre for them to read it. They can see the data is there, but it has a password block. I gave them my pin over the phone for them to access the data. The trouble is the only access they currently have would delete the data, there is no point in that. They do deal with mobile phones mostly, laptop eMMC rarely, they are finding difficulty in getting through, even asking their police friends for advice with no positive results. This is the screen print url of their access programme, followed by other data

https://onedrive.live.com/?cid=9344F523FDB4C079&id=9344F523FDB4C079%212343&parId=9344F523FDB4C079%212342&o=OneUp

Compression if OFF
Z3X EasyJtag Software ver. 3.4.0.2
Loading eMMC GEN2 Firmware... IO: 2800 mV
Initial pull results:
clock: 1878mV pin connected ok
command: 1879mV pin connected ok
data0: 1879mV pin connected ok
data1: 1877mV pin connected ok
data2: 1877mV pin connected ok
data3: 1878mV pin connected ok
data4: 1882mV pin connected ok
data5: 1878mV pin connected ok
data6: 1879mV pin connected ok
data7: 1877mV pin connected ok
Box S/N: EEB718796A161AAE, ,FW Ver.: 02.31
Box IO Level:2800 mV
CLK Rate:42000 kHz
Bus Width:8bit,SDR
HiPower mode is off!
---------- eMMC Device Information ----------

eMMC CID : 45010044463430363401300EB8B234C1
eMMC CSD : D00F00328F5903FFFFFFFFEF8A404023
eMMC Manufacturer ID: 0045 , OEM ID: 0100
eMMC Date: 03/2017 Rev.0x1
eMMC NAME: DF4064 , S/N: 806271154
eMMC NAME (HEX): 444634303634
EMMC ROM1 (Main User Data) Capacity: 59640 MB , 0x747C000 pages , 0xE8F800000 bytes
EMMC ROM2 (Boot Partition 1) Capacity: 4096 kB
EMMC ROM3 (Boot Partition 2) Capacity: 4096 kB
EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 kB
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
EMMC Password Locked: Yes
Extended CSD rev 1.8 (MMC 5.1)
Boot configuration [PARTITION_CONFIG: 0x00] No boot partition configured.
Boot bus config [177]: 0x00 , width 1bit , Partition config [179]: 0x00.
H/W reset function [RST_N_FUNCTION]: 0x00
High-capacity WP group size [HC_WP_GRP_SIZE: 0x00004000]
Partitioning Support [PARTITIONING_SUPPORT]: 0x07
Device support partitioning feature
Device can have enhanced tech.
Partitioning Setting [PARTITION_SETTING_COMPLETED]: 0x00
---------------------------------------------
Backup saved: DF4064_ 806271154_20190117_1407.extcsd
=============================================
Extended CSD rev 1.8 (MMC 5.1)
=============================================
Card Supported Command sets [S_CMD_SET: 0x01]
HPI Features [HPI_FEATURE: 0x01]:
implementation based on CMD13
Background operations support [BKOPS_SUPPORT: 0x01]
Max Packet Read Cmd [MAX_PACKED_READS: 0x3f]
Max Packet Write Cmd [MAX_PACKED_WRITES: 0x3f]
Data TAG support [DATA_TAG_SUPPORT: 0x01]
Data TAG Unit Size [TAG_UNIT_SIZE: 0x03]
Tag Resources Size [TAG_RES_SIZE: 0x03]
Context Management Capabilities [CONTEXT_CAPABILITIES: 0x05]
Large Unit Size [LARGE_UNIT_SIZE_M1: 0x00]
Extended partition attribute support [EXT_SUPPORT: 0x03]
Generic CMD6 Timer [GENERIC_CMD6_TIME: 0x19]
Power off notification [POWER_OFF_LONG_TIME: 0x19]
Cache Size [CACHE_SIZE] is 4096 KiB
------------------------- eMMC v5+ -------------------------
Supported modes [SUPPORTED_MODES: 0x03]
FFU features [FFU_FEATURES: 0x00]
Operation codes timeout [OPERATION_CODE_TIMEOUT: 0x10]
FFU Argument [FFU_ARG: 0x00000000]
Number of FW sectors correctly programmed[NUM_OF_FW_SECT_CORR_PROG: 0]
Vendor proprietary health report:
[VENDOR_PROPRIETARY_HEALTH_REPORT[301]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[300]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[299]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[298]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[297]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[296]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[295]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[294]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[293]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[292]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[291]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[290]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[289]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[288]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[287]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[286]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[285]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[284]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[283]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[282]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[281]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[280]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[279]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[278]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[277]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[276]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[275]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[274]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[273]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[272]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[271]]:0x00
[VENDOR_PROPRIETARY_HEALTH_REPORT[270]]:0x00
_(Device life time estimation type B [DEVICE_LIFE_TIME_EST_TYP_B: 0x03]
i.e. 20% - 30% device life time used
_(Device life time estimation type B [DEVICE_LIFE_TIME_EST_TYP_A: 0x03]
i.e. 20% - 30% device life time used
Pre EOL information [PRE_EOL_INFO: 0x01]
i.e. Normal

Optimal read size [OPTIMAL_READ_SIZE: 0x08]
Optimal write size [OPTIMAL_WRITE_SIZE: 0x08]
Optimal trim unit size [OPTIMAL_TRIM_UNIT_SIZE: 0x08]
Device version [DEVICE_VERSION: 0x53 - 0x41]
Firmware version:
[FIRMWARE_VERSION[261]]: 0x20
[FIRMWARE_VERSION[260]]: 0x20
[FIRMWARE_VERSION[259]]: 0x32
[FIRMWARE_VERSION[258]]: 0x34
[FIRMWARE_VERSION[257]]: 0x30
[FIRMWARE_VERSION[256]]: 0x32
[FIRMWARE_VERSION[255]]: 0x30
[FIRMWARE_VERSION[254]]: 0x32
Power class for 200MHz, DDR at VCC= 3.6V [PWR_CL_DDR_200_360: 0xdd]
-------------------------------------------------------------
Generic CMD6 Timer [GENERIC_CMD6_TIME: 0x19]
Power off notification [POWER_OFF_LONG_TIME: 0x19]
Cache Size [CACHE_SIZE] is 4096 KiB
Background operations status [BKOPS_STATUS: 0x03]
1st Initialisation Time after programmed sector [INI_TIMEOUT_AP: 0x5a]
Power class for 52MHz, DDR at 3.6V [PWR_CL_DDR_52_360: 0x00]
Power class for 52MHz, DDR at 1.95V [PWR_CL_DDR_52_195: 0xdd]
Power class for 200MHz at 3.6V [PWR_CL_200_360: 0xdd]
Power class for 200MHz, at 1.95V [PWR_CL_200_195: 0x00]
Minimum Performance for 8bit at 52MHz in DDR mode:
[MIN_PERF_DDR_W_8_52: 0x00]
[MIN_PERF_DDR_R_8_52: 0x00]
TRIM Multiplier [TRIM_MULT: 0x03]
Secure Feature support [SEC_FEATURE_SUPPORT: 0x55]
Boot Information [BOOT_INFO: 0x07]
Device supports alternative boot method
Device supports dual data rate during boot
Device supports high speed timing during boot
Boot partition size [BOOT_SIZE_MULTI: 0x20]
Access size [ACC_SIZE: 0x08]
High-capacity erase unit size [HC_ERASE_GRP_SIZE: 0x01]
High-capacity erase timeout [ERASE_TIMEOUT_MULT: 0x03]
Reliable write sector count [REL_WR_SEC_C: 0x01]
High-capacity W protect group size [HC_WP_GRP_SIZE: 0x10]
Sleep current (VCC) [S_C_VCC: 0x08]
Sleep current (VCCQ) [S_C_VCCQ: 0x07]
Sleep/awake timeout [S_A_TIMEOUT: 0x12]
Sector Count [SEC_COUNT: 0x0747c000]
Minimum Write Performance for 8bit:
[MIN_PERF_W_8_52: 0x0a]
[MIN_PERF_R_8_52: 0x0a]
[MIN_PERF_W_8_26_4_52: 0x0a]
[MIN_PERF_R_8_26_4_52: 0x0a]
Minimum Write Performance for 4bit:
[MIN_PERF_W_4_26: 0x0a]
[MIN_PERF_R_4_26: 0x0a]
Power classes registers:
[PWR_CL_26_360: 0x00]
[PWR_CL_52_360: 0x00]
[PWR_CL_26_195: 0xdd]
[PWR_CL_52_195: 0xdd]
Partition switching timing [PARTITION_SWITCH_TIME: 0x03]
Out-of-interrupt busy timing [OUT_OF_INTERRUPT_TIME: 0x0a]
I/O Driver Strength [DRIVER_STRENGTH: 0x1f]
Card Type [CARD_TYPE: 0x57]
CSD structure version [CSD_STRUCTURE: 0x02]
Command set [CMD_SET: 0x00]
Command set revision [CMD_SET_REV: 0x00]
Power class [POWER_CLASS: 0x0d]
High-speed interface timing [HS_TIMING: 0x00]
Erased memory content [ERASED_MEM_CONT: 0x00]
Boot configuration bytes [PARTITION_CONFIG: 0x00]
Not boot enabled
No access to boot partition
Boot config protection [BOOT_CONFIG_PROT: 0x00]
Boot bus Conditions [BOOT_BUS_CONDITIONS: 0x00]
High-density erase group definition [ERASE_GROUP_DEF: 0x00]
Boot write protection status registers [BOOT_WP_STATUS]: 0x00
Boot Area Write protection [BOOT_WP]: 0x00
Power ReadOnly locking: possible
Permanent ReadOnly locking: possible
Read Only lock status: not locked
User area write protection register [USER_WP]: 0x00
FW configuration [FW_CONFIG]: 0x00
RPMB Size [RPMB_SIZE_MULT]: 0x20
Write reliability setting register [WR_REL_SET]: 0x1f
Write reliability parameter register [WR_REL_PARAM]: 0x15
Enable background operations handshake [BKOPS_EN]: 0x02
H/W reset function [RST_N_FUNCTION]: 0x00
HPI management [HPI_MGMT]: 0x00
Partitioning Support [PARTITIONING_SUPPORT]: 0x07
Device support partitioning feature
Device can have enhanced tech.
Max Enhanced Area Size [MAX_ENH_SIZE_MULT]: 0x000925
Partitions attribute [PARTITIONS_ATTRIBUTE]: 0x00
Partitioning Setting [PARTITION_SETTING_COMPLETED]: 0x00
General Purpose Partition Size [GP_SIZE_MULT_4]: 0x000000
[GP_SIZE_MULT_3]: 0x000000
[GP_SIZE_MULT_2]: 0x000000
[GP_SIZE_MULT_1]: 0x000000
Enhanced User Data Area Size [ENH_SIZE_MULT]: 0x000000
Enhanced User Data Start Address [ENH_START_ADDR]: 0x000000
Bad Block Management mode [SEC_BAD_BLK_MGMNT]: 0x00
Periodic Wake-up [PERIODIC_WAKEUP]: 0x00
Program CID/CSD in DDR mode support [PROGRAM_CID_CSD_DDR_SUPPORT]: 0x01
Native sector size [NATIVE_SECTOR_SIZE]: 0x00
Sector size emulation [USE_NATIVE_SECTOR]: 0x00
Sector size [DATA_SECTOR_SIZE]: 0x00
1st initialization after disabling sector size emulation [INI_TIMEOUT_EMU]: 0x0a
Class 6 commands control [CLASS_6_CTRL]: 0x00
Number of addressed group to be released[DYNCAP_NEEDED]: 0x00
Exception events control [EXCEPTION_EVENTS_CTRL]: 0x0000
Exception events status [EXCEPTION_EVENTS_STATUS]: 0x0000
Extended Partitions Attribute [EXT_PARTITIONS_ATTRIBUTE]: 0x0000
Packed command status [PACKED_COMMAND_STATUS]: 0x00
Packed command failure index [PACKED_FAILURE_INDEX]: 0x00
Power Off Notification [POWER_OFF_NOTIFICATION]: 0x00
Control to turn the Cache ON/OFF [CACHE_CTRL]: 0x00
Done.


Top
 Profile  
 
 Post subject: Re: eMMC chip access
PostPosted: January 17th, 2019, 17:22 
Offline

Joined: January 17th, 2019, 14:14
Posts: 14
Location: United Kingdom
Attachment:
image.png
image.png [ 101.07 KiB | Viewed 4038 times ]
The screen print from the company that is trying to extract the data:


Top
 Profile  
 
 Post subject: Re: eMMC chip access
PostPosted: January 17th, 2019, 17:33 
Offline
User avatar

Joined: June 11th, 2013, 17:01
Posts: 1296
Location: Phoenix, AZ USA
Can you give us more details about the laptop- make, model, OS etc and why do you need to extract the data from the eMMC?

_________________
HDD, SSD, Flash and RAID Data Recovery


Top
 Profile  
 
 Post subject: Re: eMMC chip access
PostPosted: January 17th, 2019, 19:20 
Offline

Joined: January 17th, 2019, 14:14
Posts: 14
Location: United Kingdom
Acer Aspire Windows 10 - no bootable device - tried everything to access it, so eventually took it off the board, now the chip can be seen, which is progress, but it cannot be accessed without going through the password bit, any other route deletes the data - the data is clearly what I need to see again


Top
 Profile  
 
 Post subject: Re: eMMC chip access
PostPosted: January 17th, 2019, 19:47 
Offline
User avatar

Joined: June 11th, 2013, 17:01
Posts: 1296
Location: Phoenix, AZ USA
Clare wrote:
Acer Aspire Windows 10 - no bootable device - tried everything to access it, so eventually took it off the board, now the chip can be seen, which is progress, but it cannot be accessed without going through the password bit, any other route deletes the data - the data is clearly what I need to see again

I am not too familiar with that model, however I am surprised its an eMMC chip.
Did you physically remove the chip from the board? ie desolder it?
Can you send a picture of the chip and the logic board.

_________________
HDD, SSD, Flash and RAID Data Recovery


Top
 Profile  
 
 Post subject: Re: eMMC chip access
PostPosted: January 17th, 2019, 19:56 
Offline

Joined: January 17th, 2019, 14:14
Posts: 14
Location: United Kingdom
Yes, I got a more experienced person to desolder it for obvious reasons. The chip is with a professional - usually mobile phone data extraction outfit as you can see above all the data in a small paragraph. I was too surprised, it is a thin model but I did expect a proper hard drive, I'd have my precious data easily if that were the case.


Top
 Profile  
 
 Post subject: Re: eMMC chip access
PostPosted: January 17th, 2019, 20:06 
Offline
User avatar

Joined: June 11th, 2013, 17:01
Posts: 1296
Location: Phoenix, AZ USA
With this type of set up (chip on logic board), it is always preferable to try to access the data with the chip on the board by every means possible before removing the chip. ie logic board work. A lot of chips can also be encrypted, so removing the chip can make the data unrecoverable.

I would strongly suggest you take it to a professional data recovery company rather than the cellphone store. While they may charge more for the recovery, they may well be able to tap into the data partitions on the chip which does require specialist equipment and knowledge.

_________________
HDD, SSD, Flash and RAID Data Recovery


Top
 Profile  
 
 Post subject: Re: eMMC chip access
PostPosted: January 17th, 2019, 20:23 
Offline

Joined: January 17th, 2019, 14:14
Posts: 14
Location: United Kingdom
I did ask a professional data recovery company first and thy could not do anything for me, after taking it to a computer repair shop. I also did try every option available with the chip on the board. I joined several forums for advice which I followed, I also contacted Acer

I have tried every possible on board option - I am fully aware this is the final option available. For it to see the chip is progress.
I tried a boot usb, EaseUS and plenty of other stuff.

Please focus on answering the question re the password access.

I keep looking at this when I get a notification of hope of a workable solution, please, if you can provide one, do - it is about passworded access.


Top
 Profile  
 
 Post subject: Re: eMMC chip access
PostPosted: January 18th, 2019, 3:25 
Offline

Joined: October 24th, 2009, 15:22
Posts: 645
Location: Poland
For eMMC chip there is few method to access to data:
1. soldering to chip on board by wires from "kitchen" site.
2. Chip-off and read by adapter via working controller
3. Chip-off and read directly from nand (the most advanced method)

Never meet such situation where we can't read dump due to encryption. We read it on hardware level, not software level. (I have only one case per last 10 years, which was blocked and it was SD monolith card from special device).

_________________
Odzyskiwanie danych


Top
 Profile  
 
 Post subject: Re: eMMC chip access
PostPosted: January 18th, 2019, 4:05 
Offline

Joined: January 17th, 2019, 14:14
Posts: 14
Location: United Kingdom
Thank you.

Who would you recommend to perform these tasks?


Top
 Profile  
 
 Post subject: Re: eMMC chip access
PostPosted: January 18th, 2019, 4:11 
Offline

Joined: October 24th, 2009, 15:22
Posts: 645
Location: Poland
Hmm... let me think :)

_________________
Odzyskiwanie danych


Top
 Profile  
 
 Post subject: Re: eMMC chip access
PostPosted: January 18th, 2019, 4:35 
Offline

Joined: January 17th, 2019, 14:14
Posts: 14
Location: United Kingdom
Please don't mock, not presume I know, I am new to this and would like to see my data. I have been trying since late November and am tiring of this but know I cannot give up. If you perform these tasks this attitude erodes trust. I do not know the name of your organisation or links to it. Please can responders to this thread reply constructively with information so you can help me.


Top
 Profile  
 
 Post subject: Re: eMMC chip access
PostPosted: January 18th, 2019, 4:42 
Offline

Joined: October 24th, 2009, 15:22
Posts: 645
Location: Poland
Sorry it was just joke :) Here is more info: http://odzyskiwanie-danych.com.pl/monol ... abase.html
We specialize in this kind of recovery.

_________________
Odzyskiwanie danych


Top
 Profile  
 
 Post subject: Re: eMMC chip access
PostPosted: January 18th, 2019, 6:02 
Offline
User avatar

Joined: January 28th, 2009, 10:54
Posts: 2876
Location: Greece
+1, arvika is your man.

_________________
WD Trusted Partners
http://www.northwind.gr
SandForce SSD Recovery
Ransomware Reverse Engineering - NoMoreRansom! partners


Top
 Profile  
 
 Post subject: Re: eMMC chip access
PostPosted: January 18th, 2019, 6:17 
Offline

Joined: June 12th, 2017, 5:42
Posts: 8
Location: Nottingham
Clare, we are UK and can attempt recovery on eMMCs if you prefer to keep it in the country. DM me.

_________________
https://lc-tech.co.uk/


Top
 Profile  
 
 Post subject: Re: eMMC chip access
PostPosted: January 18th, 2019, 9:39 
Offline
User avatar

Joined: June 11th, 2013, 17:01
Posts: 1296
Location: Phoenix, AZ USA
Arvika. A lot of these laptops with onboarding chips are encrypted with BitLocker by default which is decrypted through the Windows password. The new Surface is like this. So you cannot decrypt it through the chip. Just saying.

_________________
HDD, SSD, Flash and RAID Data Recovery


Top
 Profile  
 
 Post subject: Re: eMMC chip access
PostPosted: January 18th, 2019, 11:05 
Offline

Joined: January 17th, 2019, 14:14
Posts: 14
Location: United Kingdom
The chip is being returned to me as the data could not be reached:

Do any of you have the equipment to get through and so can you help?

JOB DESCRIPTION:

Windows Laptop / Tablet eMMC Data Recovery Service


Notes for POST: Clare Kingston (38868) From Engineer:
chip arrived.

chip reballed / cleaned up by mike

chip ready for scheduled dump wednesday

chip detected ok

attempted to read eMMC, but fails due to emmc chip is password protected !!

I cannot attempt to remove password without wiping data :(




After much research, i am told the chip is ultimately encrypted, by what is unknown, there are multiple types of encryption the manufacturers can use.

the only possible solution is to re attach the chip back to the logic board and let a high level pc data recovery company try inline data recovery.

However i have been advised that this may not yield a result, even if the chip is attached successfully, which has a low success rate, they still may not get past the encryption on the chip


sorry i could not be any more help with this.

Mark




LOG
===


---------- eMMC Device Information ----------

eMMC CID : 45010044463430363401300EB8B234C1
eMMC CSD : D00F00328F5903FFFFFFFFEF8A404023
eMMC Manufacturer ID: 0045 , OEM ID: 0100
eMMC Date: 03/2017 Rev.0x1
eMMC NAME: DF4064 , S/N: 806271154
eMMC NAME (HEX): 444634303634
EMMC ROM1 (Main User Data) Capacity: 59640 MB
EMMC ROM2 (Boot Partition 1) Capacity: 4096 kB
EMMC ROM3 (Boot Partition 2) Capacity: 4096 kB
EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 kB
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
EMMC Password Locked: Yes <<===============================================================
Extended CSD rev 1.8 (MMC 5.1)
Boot configuration [PARTITION_CONFIG: 0x00] No boot partition configured.
Boot bus config [177]: 0x00 , width 1bit , Partition config [179]: 0x00.
H/W reset function [RST_N_FUNCTION]: 0x00
High-capacity WP group size [HC_WP_GRP_SIZE: 0x00004000]
Partitioning Support [PARTITIONING_SUPPORT]: 0x07
Device support partitioning feature
Device can have enhanced tech.
Partitioning Setting [PARTITION_SETTING_COMPLETED]: 0x00
---------------------------------------------


Top
 Profile  
 
 Post subject: Re: eMMC chip access
PostPosted: January 18th, 2019, 11:43 
Offline

Joined: January 17th, 2019, 14:14
Posts: 14
Location: United Kingdom
The chip is on the way back to me as the data could not be accessed. I've been trying to view the Arvika website - it does show my eMMC chip - but weirdly the simple task of page translation is not working for me, perhaps due to worry I cannot think. I still have the logic board if that helps.


Top
 Profile  
 
 Post subject: Re: eMMC chip access
PostPosted: January 18th, 2019, 12:37 
Offline
User avatar

Joined: June 11th, 2013, 17:01
Posts: 1296
Location: Phoenix, AZ USA
I agree with Northwind that Arvika is your man to get the data if anyone can. I am just trying to manage your expectations.

_________________
HDD, SSD, Flash and RAID Data Recovery


Top
 Profile  
 
 Post subject: Re: eMMC chip access
PostPosted: January 18th, 2019, 13:09 
Offline

Joined: January 17th, 2019, 14:14
Posts: 14
Location: United Kingdom
Thank you, after trying since November my expectations are sadly managed. I have started to look into BitLocker to see if it is possible to get the key, I don't know how that works. Arvika - I have looked on the English bit of your page for instructions, I will tell you when I have the chip, you can further advise as you think, Thank you


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 32 posts ]  Go to page 1, 2  Next

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 5 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group