GSM Shop GSM Shop
GSM-Forum  

Welcome to the GSM-Forum forums.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features.
Only registered members may post questions, contact other members or search our database of over 8 million posts.

Registration is fast, simple and absolutely free so please - Click to REGISTER!

If you have any problems with the registration process or your account login, please contact contact us .

Go Back   GSM-Forum > Product Support Sections > Hard/Software Products (official support) > Easy-Jtag / Easy-Jtag Plus

Easy-Jtag / Easy-Jtag Plus The official support section. You can ask here your question and get answer regarding using Easy-Jtag / Easy-Jtag Plus.

Reply
 
LinkBack Thread Tools Display Modes
Old 03-17-2017, 10:35   #1 (permalink)
No Life Poster
 
KrzychuG's Avatar
 
Join Date: Apr 2003
Location: Torun, Poland
Age: 40
Posts: 1,192
Member: 25996
Status: Offline
Thanks Meter: 253
Lumia 520 eMMC dump via JTAG - not dumping full 8GB


I tried couple times. First attempt was to cut the first 1GB and start from there as i only need userdata. I set start(HEX) as 0x000040000000 and length as 0x000200000000 (8Gb preset). It dumped 4GB. It wasn't a complete dump, some of the data i required were corrupted so i decided to dump full 8GB from the start, selected 32Gb preset and again, it read 4GB only.

Log from dumping full 8GB with 32Gb preset. Don't mind the "continue ... bytes" as i had to renew the connection since it breaks every once in a while. Dump itself is a 4 294 967 296 bytes, 4GB.

Quote:
Initialising: NOKIA LUMIA 520 Config ver.:1.00
I/O Level set to : 2200 mV
Box S/N: ************** ,FW Ver.: 01.58
Connecting to Target...
JTAG device: MSM8227.
CPU IDCODE : 0x4F1F0F0F Mfg.: 0x787, Part: 0xf1f0, Ver.: 0x4
CPU Manufacturer: Samsung , CPU Name: ARM7GEN
JTAG device: MSM8227.
CPU IDCODE : 0x207D00E1 Mfg.: 0x070, Part: 0x07d0, Ver.: 0x2
CPU Manufacturer: QUALCOMM , CPU Name: MSM8227
Halting CPU...
Initialize hardware...
Starting target communication...
Detecting emmc memory parameters of bank (0) ...
EMMC #0 : ID : 0x00000015 Name : M8G2YC Size : 7.3 G , (15269888) Blocks
EMMC #1 : ID : 0x00000015 Name : M8G2YC Size : 4.0 M , (8192) Blocks
eMMC flash device(s) found, Device ID : 0x00150000
Continue 0x0000A8D10000 bytes from emmc adress 0x0000572F0000
Dumped 0 bytes in 48995.632812s (0.000 KiB/s) OK.
I am now trying to dump another 4GB with starting from 0x000100000000 to see what it'll produce but even if this works fine, it's a bit annoying to do that way.
  Reply With Quote
Old 04-01-2019, 13:31   #2 (permalink)
Junior Member
 
Join Date: Mar 2019
Location: Germany
Posts: 3
Member: 2903119
Status: Offline
Thanks Meter: 1
I have the same problem. Want to create a 16GB dump via JTAG. Did you find out why it is or did you find a solution? Or do you always create 4Gb parts and put them together?
  Reply With Quote
Old 04-01-2019, 13:48   #3 (permalink)
Product Supporter
 
layder's Avatar
 
Join Date: Jun 2002
Location: Belarus
Age: 47
Posts: 3,187
Member: 13148
Status: Offline
Thanks Meter: 2,948
Quote:
Originally Posted by Carla1 View Post
I have the same problem. Want to create a 16GB dump via JTAG. Did you find out why it is or did you find a solution? Or do you always create 4Gb parts and put them together?
Lumia 520 have a 8MB Flash IC
You need save dump to NTFS partition, not FAT32.
Temp folder need to be at NTFS partiton also

FAT32 have limit for 4GB files, opened for write
  Reply With Quote
Old 04-01-2019, 21:58   #4 (permalink)
No Life Poster
 
KrzychuG's Avatar
 
Join Date: Apr 2003
Location: Torun, Poland
Age: 40
Posts: 1,192
Member: 25996
Status: Offline
Thanks Meter: 253
Quote:
Originally Posted by Carla1 View Post
I have the same problem. Want to create a 16GB dump via JTAG. Did you find out why it is or did you find a solution? Or do you always create 4Gb parts and put them together?

To be honest i don't remember. I guess i dumped the other part and joined files togeter (this can be done with a hex editor or just "copy /b file_a + file_b"). It's also possible this was fixed at some point.


@layder, i would be surprised if anyone would still use FAT32 as a main filesystem. There was a problem in dumping data over 4GB back in 2017 and i was already using NTFS on every drive i had connected so that wasn't an issue.
  Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


 



All times are GMT +1. The time now is 06:51.



Powered by Searchlight © 2024 Axivo Inc.
vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2023 -
Page generated in 0.12229 seconds with 8 queries

SEO by vBSEO