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) > GSMServer Products > Medusa


Reply
 
LinkBack Thread Tools Display Modes
Old 05-13-2018, 10:56   #1 (permalink)
Freak Poster
 
s a dot com's Avatar
 
Join Date: Jul 2012
Location: karachi
Age: 31
Posts: 296
Member: 1779651
Status: Offline
Sonork: 100.1603336
Thanks Meter: 97
Thumbs up Motorola XT1080 invalid CID [Solved]


motorolla xt1080 invalid cid

hi to medusa team to day i m facing one problem

replace emmc

1 i have old emmc cid backup

2 i have new emmc

3 i first erase all then i write old cid with medusa pro software

4 fectoury repair with xml file

5 after replce new emmc in mobile i m facing one problem invalid cid

how can solve this error?

here is picture

https://imageshack.com/a/img922/1567/CbAm75.png

Last edited by Octopus box; 05-29-2018 at 13:17.
  Reply With Quote
Old 05-14-2018, 04:50   #2 (permalink)
Product Supporter
 
Medusa Box's Avatar
 
Join Date: Mar 2011
Location: Octopus-team
Posts: 9,360
Member: 1538383
Status: Offline
Sonork: 100.1587278
Thanks Meter: 3,398
Hi.

Quote:
1 i have old emmc cid backup
Post here Software log with connect operation of your old eMMC and with reading this CID backup, we will check, whether You have read out CID backup correctly.

Quote:
3 i first erase all then i write old cid with medusa pro software

4 fectoury repair with xml file
Also post here full Software log with connect operation, writing CID backup operation and with "Factory Repair" operation, we will check.
  Reply With Quote
Old 05-15-2018, 19:34   #3 (permalink)
Freak Poster
 
s a dot com's Avatar
 
Join Date: Jul 2012
Location: karachi
Age: 31
Posts: 296
Member: 1779651
Status: Offline
Sonork: 100.1603336
Thanks Meter: 97
motorolla xt1080

old emmc logs

Model Settings:
Interface : eMMC
Voltage : 1.8V
Bus Mode : 1 bit
Bus speed : Auto

Connecting...
Device : Sandisk eMMC SEM32G
Page size : 512 B
Block size : 512 B
Block count : 61071360
Size : 29.12 GB (29820.00 MB)
---------------------------------------------------------------
CID Info

CID : 45010053454D33324707139F55C39083
Manufacturer ID : 0X45
Device/BGA : BGA (Discrete embedded)
OEM/Application ID : 0X00
Product name : SEM32G
Product revision : 0.7
Product serial number : (hex) 139F55C3
Manufacturing date : 09/2013
---------------------------------------------------------------
CSD Info

CSD : D00F00320F5903FFFFFFFFFF8A40407F
CSD structure : CSD version No. 1.2
SPEC version : 4.1, 4.2, 4.3, 4.4, 4.41, 4.5,
4.51, 5.0, 5.01, 5.1
Data read access time1: 10 ms
TRAN speed : 26 MHz
READ block length : 512 Bytes
WP group enable : YES
PERM_WRITE_PROTECT : NO
TMP_WRITE_PROTECT : NO
---------------------------------------------------------------
EXTCSD Info

Revision 1.6 (for MMC v4.5, v4.51)
Erase block size : 512 Kbytes
Boot1 size : 4096 Kbytes
Boot2 size : 4096 Kbytes
RPMB size : 4096 Kbytes

Partition config : (0x38) 00111000
Boot partition enable : User area
(Bus width = 1Bit)
Boot ACK : No boot acknowledge sent (default)

Boot bus conditions : (0x00) 00000000
Boot bus width : x1 (sdr) or x4 (ddr) bus width in boot operation mode (default)
Reset boot bus conditions : Reset bus width to x1, single data rate and backward compatible timings after boot operation (default)
Boot mode : Use single data rate + backward compatible timings in boot operation (default)

RST_n function : (0x01) RST_n signal is permanently enabled

Partitioning support : Device supports partitioning features
Max enhanced data size: 15253504 Kbytes
Partitions attribute : 0x0
Part setting completed: 0x0
GP partition 1 size : 0 b
GP partition 2 size : 0 b
GP partition 3 size : 0 b
GP partition 4 size : 0 b
Enhanced area size : (0x0) 0 b
Enhanced area start : (0x0) 0 b

---------------------------------------------------------------Searching Android build info...
Not found
---------------------------------------------------------------
Backup EXT_CSD saved to file C:/Program Files/Medusa Pro Software/EXT_CSD Backups/SEM32G_15_05_2018_22_58_10.bin.
Connect successful.
---------------------------------------------------------------
SW: 1.5.5; FW: 1.23.


old emmc cid:

CID : 45010053454D33324707139F55C39083



now i m going to new emmc

erase all partation new emmc

Erasing partition GPT... Done.
Erasing partition modem... Done.
Erasing partition sbl1... Done.
Erasing partition sbl2... Done.
Erasing partition sbl3... Done.
Erasing partition aboot... Done.
Erasing partition rpm... Done.
Erasing partition tz... Done.
Erasing partition utags... Done.
Erasing partition logs... Done.
Erasing partition padA... Done.
Erasing partition sbl2Backup... Done.
Erasing partition sbl3Backup... Done.
Erasing partition abootBackup... Done.
Erasing partition rpmBackup... Done.
Erasing partition tzBackup... Done.
Erasing partition utagsBackup... Done.
Erasing partition padB... Done.
Erasing partition modemst1... Done.
Erasing partition modemst2... Done.
Erasing partition mbl... Done.
Erasing partition hob... Done.
Erasing partition dhob... Done.
Erasing partition persist... Done.
Erasing partition ssd... Done.
Erasing partition fsg... Done.
Erasing partition sp... Done.
Erasing partition misc... Done.
Erasing partition pds... Done.
Erasing partition cid... Done.
Erasing partition logo... Done.
Erasing partition clogo... Done.
Erasing partition devtree... Done.
Erasing partition boot... Done.
Erasing partition recovery... Done.
Erasing partition kpan... Done.
Erasing partition cache... Done.
Erasing partition padC... Done.
Erasing partition system... Done.
Erasing partition customize... Done.
Erasing partition userdata... Done.
Erasing is finished.
SW: 1.5.5; FW: 1.23.


now i m going to emmc service rab
copy old cid : 45010053454D33324707139F55C39083

open edit cid and past old cid then write

Changing CID to 45010053454D33324707139F55C39083.
Write CID succesfully completed.
Disconnected.

now i m going to fectory repair rab
flash file with xml

Selected file: H:/motorolla/ultra max/CFC_obake-maxx_verizon-user-4.4.4-SU6-7.7-release-keys.xml/CFC_obake-maxx_verizon-user-4.4.4-SU6-7.7-release-keys.xml.
File parsing finished.
Writing MBR...Done.
#greenWriting primary GPT...Done.
#greenWriting secondary GPT...Done.
#greenWrite data verification is enabled.
Writing. Please wait...
Writing partition modem... Done.
#greenWriting partition sbl1... Done.
#greenWriting partition sbl2... Done.
#greenWriting partition sbl3... Done.
#greenWriting partition aboot... Done.
#greenWriting partition rpm... Done.
#greenWriting partition tz... Done.
#greenErasing partition modemst1... Done.
#greenErasing partition modemst2... Done.
#greenWriting partition fsg... Done.
#greenWriting partition logo... Done.
#greenErasing partition clogo... Done.
#greenWriting partition boot... Done.
#greenWriting partition recovery... Done.
#greenErasing partition cache... Done.
#greenErasing partition customize... Done.
#greenErasing partition userdata... Done.
#greenWriting is finished.
SW: 1.5.5; FW: 1.23.
#blue

now sold new emmc in mobile phone

i m facing this error again

https://imageshack.com/a/img922/1567/CbAm75.png


kindly help me medusa team how to solve this
  Reply With Quote
Old 05-16-2018, 04:57   #4 (permalink)
Product Supporter
 
Medusa Box's Avatar
 
Join Date: Mar 2011
Location: Octopus-team
Posts: 9,360
Member: 1538383
Status: Offline
Sonork: 100.1587278
Thanks Meter: 3,398
Quote:
old emmc cid:

CID : 45010053454D33324707139F55C39083
This is not that CID, which You need from old eMMC. CID, which You have mentioned above - this is eMMC Card IDentification register, it contains the eMMC identification information (Manufacturer ID, Product Name, Product Revision, Product Serial Number, Manufacturing Date and some others) used during the Device identification phase (eMMC protocol).

But You need CID partition (not eMMC CID register backup) from old eMMC from firmware area (partition, like GPT, modem, system etc). As I see from connection log of your old eMMC, partitions' area is damaged and Software can't detect any partition on it:
Quote:
Searching Android build info...
Not found
This means, that You don't have necessary CID partition backup from old eMMC. Unfortunately, it is not possible to repair this device correctly without having original CID partition backup.
  Reply With Quote
Old 05-16-2018, 08:58   #5 (permalink)
Freak Poster
 
s a dot com's Avatar
 
Join Date: Jul 2012
Location: karachi
Age: 31
Posts: 296
Member: 1779651
Status: Offline
Sonork: 100.1603336
Thanks Meter: 97
Quote:
But You need CID partition (not eMMC CID register backup) from old eMMC from firmware area (partition, like GPT, modem, system etc). As I see from connection log of your old eMMC, partitions' area is damaged and Software can't detect any partition on it:
how can i backup old emmc firmware area likr gpt,modem and sytem can u help me
  Reply With Quote
Old 05-16-2018, 09:11   #6 (permalink)
Product Supporter
 
Medusa Box's Avatar
 
Join Date: Mar 2011
Location: Octopus-team
Posts: 9,360
Member: 1538383
Status: Offline
Sonork: 100.1587278
Thanks Meter: 3,398
Connect the old eMMC and post here full Software log. If Software will detect partitions, You can read out necessary partitions. If Software will not detect partitions, this mean, that partition table (and probably other data on eMMC) is damaged and not possible to read out necessary partition(s).
  Reply With Quote
Old 05-16-2018, 15:01   #7 (permalink)
Freak Poster
 
s a dot com's Avatar
 
Join Date: Jul 2012
Location: karachi
Age: 31
Posts: 296
Member: 1779651
Status: Offline
Sonork: 100.1603336
Thanks Meter: 97
old emmc logs here chek

Model Settings:
Interface : eMMC
Voltage : 2.8V
Bus Mode : 1 bit
Bus speed : Auto

Connecting...
Device : Sandisk eMMC SEM32G
Page size : 512 B
Block size : 512 B
Block count : 61071360
Size : 29.12 GB (29820.00 MB)
---------------------------------------------------------------
CID Info

CID : 45010053454D33324707139F55C39083
Manufacturer ID : 0X45
Device/BGA : BGA (Discrete embedded)
OEM/Application ID : 0X00
Product name : SEM32G
Product revision : 0.7
Product serial number : (hex) 139F55C3
Manufacturing date : 09/2013
---------------------------------------------------------------
CSD Info

CSD : D00F00320F5903FFFFFFFFFF8A40407F
CSD structure : CSD version No. 1.2
SPEC version : 4.1, 4.2, 4.3, 4.4, 4.41, 4.5,
4.51, 5.0, 5.01, 5.1
Data read access time1: 10 ms
TRAN speed : 26 MHz
READ block length : 512 Bytes
WP group enable : YES
PERM_WRITE_PROTECT : NO
TMP_WRITE_PROTECT : NO
---------------------------------------------------------------
EXTCSD Info

Revision 1.6 (for MMC v4.5, v4.51)
Erase block size : 512 Kbytes
Boot1 size : 4096 Kbytes
Boot2 size : 4096 Kbytes
RPMB size : 4096 Kbytes

Partition config : (0x38) 00111000
Boot partition enable : User area
(Bus width = 1Bit)
Boot ACK : No boot acknowledge sent (default)

Boot bus conditions : (0x00) 00000000
Boot bus width : x1 (sdr) or x4 (ddr) bus width in boot operation mode (default)
Reset boot bus conditions : Reset bus width to x1, single data rate and backward compatible timings after boot operation (default)
Boot mode : Use single data rate + backward compatible timings in boot operation (default)

RST_n function : (0x01) RST_n signal is permanently enabled

Partitioning support : Device supports partitioning features
Max enhanced data size: 15253504 Kbytes
Partitions attribute : 0x0
Part setting completed: 0x0
GP partition 1 size : 0 b
GP partition 2 size : 0 b
GP partition 3 size : 0 b
GP partition 4 size : 0 b
Enhanced area size : (0x0) 0 b
Enhanced area start : (0x0) 0 b

---------------------------------------------------------------Searching Android build info...
Ok

Disk/Image size : 47c00000 bytes
Device sector size : 512 bytes
Partition offset : 3244032
Number of sectors : 4325376
Device Manufacturer :motorola
Device Platform :msm8960
Build ID :SU6-7.7
Display Build ID :SU6-7.7
Release ID :4.4.4
Device Model :XT1080
Device Name bake_verizon
Architecture ABI :armeabi-v7a
Architecture ABI2 :armeabi
Build Description bake_verizon-user 4.4.4 SU6-7.7 5 release-keys

Backup EXT_CSD saved to file C:/Program Files/Medusa Pro Software/EXT_CSD Backups/SEM32G_16_05_2018_19_00_17.bin.
Connect successful.
---------------------------------------------------------------
SW: 1.5.5; FW: 1.23.
P00: GPT (00000000, 00000100) 128 KB
P01: modem (00000100, 00032000) 100 MB
P02: sbl1 (00032100, 00000BB8) 1500 KB
P03: sbl2 (00032CB8, 00000BB8) 1500 KB
P04: sbl3 (00033870, 00000404) 514 KB
P05: aboot (00034870, 00000400) 512 KB
P06: rpm (00035428, 0000011C) 142 KB
P07: tz (00035810, 000001A4) 210 KB
P08: utags (00035BF8, 00000400) 512 KB
P09: logs (00035FF8, 00000800) 1024 KB
P10: padA (000367F8, 00001808) 3076 KB
P11: sbl2Backup (00038000, 00000BB8) 1500 KB
P12: sbl3Backup (00038BB8, 00001000) 2048 KB
P13: abootBackup (00039BB8, 00000BB8) 1500 KB
P14: rpmBackup (0003A770, 000003E8) 500 KB
P15: tzBackup (0003AB58, 000003E8) 500 KB
P16: utagsBackup (0003AF40, 00000400) 512 KB
P17: padB (0003B340, 00000CC0) 1632 KB
P18: modemst1 (0003C000, 00001800) 3072 KB
P19: modemst2 (0003D800, 00001800) 3072 KB
P20: mbl (0003F000, 00001000) 2048 KB
P21: hob (00040000, 00000500) 640 KB
P22: dhob (00040500, 00000010) 8 KB
P23: persist (00040600, 00004000) 8 MB
P24: ssd (00044600, 00000010) 8 KB
P25: fsg (00044610, 00001800) 3072 KB
P26: sp (00045E10, 00000800) 1024 KB
P27: misc (00046610, 00000400) 512 KB
P28: pds (00046A10, 00001800) 3072 KB
P29: cid (00048210, 00000100) 128 KB
P30: logo (00048310, 00002000) 4 MB
P31: clogo (0004A310, 00002000) 4 MB
P32: devtree (0004C310, 00000800) 1024 KB
P33: boot (0004CC00, 00005000) 10 MB
P34: recovery (00051C00, 00005000) 10 MB
P35: kpan (00056C00, 00004000) 8 MB
P36: cache (0005AC00, 002BCC00) 1402 MB
P37: padC (00317800, 00000800) 1024 KB
P38: system (00318000, 00420000) 2112 MB
P39: customize (00738000, 00008000) 16 MB
P40: userdata (00740000, 032F5F00) 25.48 GB
Backuping Gpt partition...
Opening C:/Program Files/Medusa Pro Software/Backups/SEM32G_Gpt_0x0_0x100_16_05_2018_19_00_17.bin file...
Reading. Please wait... Done.
Elapsed time 00:00:00
SW: 1.5.5; FW: 1.23.
Backuping Cid partition...
Opening C:/Program Files/Medusa Pro Software/Backups/SEM32G_Cid_0x48210_0x100_16_05_2018_19_00_17.bin file...
Reading. Please wait... Done.
Elapsed time 00:00:00
SW: 1.5.5; FW: 1.23.

now tell me next step
  Reply With Quote
Old 05-16-2018, 15:17   #8 (permalink)
Product Supporter
 
Medusa Box's Avatar
 
Join Date: Mar 2011
Location: Octopus-team
Posts: 9,360
Member: 1538383
Status: Offline
Sonork: 100.1587278
Thanks Meter: 3,398
Hello.

As You can see from Software log, original backup of Cid partition was done by Software automatically after the device been connected:
Quote:
P29: cid (00048210, 00000100) 128 KB
Quote:
Backuping Cid partition...
Opening C:/Program Files/Medusa Pro Software/Backups/SEM32G_Cid_0x48210_0x100_16_05_2018_19_00_17.bin file...
Reading. Please wait... Done.
To write this Cid backup file to new eMMC, do the next:

1. Connect the device (new eMMC).
2. Select "Custom" option in Software.
3. Select "Hex block" type of data.
4. Set "Start: 00048210".
5. Set "Length: 00000100".
6. Press "Write" button, select Cid backup file "SEM32G_Cid_0x48210_0x100_16_05_2018_19_00_17. bin" and write it.
  Reply With Quote
The Following 2 Users Say Thank You to Medusa Box For This Useful Post:
Old 05-29-2018, 13:05   #9 (permalink)
Freak Poster
 
s a dot com's Avatar
 
Join Date: Jul 2012
Location: karachi
Age: 31
Posts: 296
Member: 1779651
Status: Offline
Sonork: 100.1603336
Thanks Meter: 97
succes here is logs thanks to medusa team

Selected file: H:/motorolla/ultra max/CFC_obake-maxx_verizon-user-4.4.4-SU6-7.7-release-keys.xml/CFC_obake-maxx_verizon-user-4.4.4-SU6-7.7-release-keys.xml.
File parsing finished.
Writing MBR...Done.
Writing primary GPT...Done.
Writing secondary GPT...Done.
Write data verification is enabled.
Writing. Please wait...
Writing partition modem... Done.
Erasing partition modemst1... Done.
Erasing partition modemst2... Done.
Writing partition fsg... Done.
Writing partition logo... Done.
Erasing partition clogo... Done.
Writing partition boot... Done.
Writing partition recovery... Done.
Erasing partition cache... Done.
Erasing partition customize... Done.
Erasing partition userdata... Done.
Writing is finished.
SW: 1.5.5; FW: 1
  Reply With Quote
The Following User Says Thank You to s a dot com For This Useful Post:
Reply

Bookmarks


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 21:17.



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.26031 seconds with 8 queries

SEO by vBSEO