FORUMS
Remove All Ads from XDA

Unlock your Samsung i5500 (Where is my /efs?) [UPDATE]

833 posts
Thanks Meter: 409
 
By tweakradje, Senior Member on 4th November 2010, 12:06 PM
Post Reply Email Thread
17th April 2011, 11:47 PM |#201  
Member
Thanks Meter: 3
 
More
Stop mucking around with random commands and read more carefully, it's /dev/block/stl5 , not /dev/stl5 . I have no idea if /dev/stl5 even exists, and if it does I'd rather not touch it even with a 2 meters pole.


Quote:
Originally Posted by s2003r

Thanks for your reply.
i've seen your thread :
http://forum.xda-developers.com/show...&postcount=174

maybe you could give us the steps taken by you ?

I've also checked :
http://forum.xda-developers.com/show...&postcount=156
did google translate but it did very poor translation.
question:

Code:
dd if=/dev/block/stl5 of=/sdcard/stl5.rfs
dd if=/sdcard/stl5.rfs of=/dev/block/stl5
is that a copy from the phone to sd and then back ... what for ? as i understand it should be enough to make a copy of stl5 on sd then analyse it in hex for unlock code.

thanks

I have no idea if the Ace presents the same symptoms as the i5500, but our phone corrupts the efs once it is copied but will work just fine after being copied back.
Using dd from recovery mode should theoretically not require the second command, but I'd rather keep it there for safety purposes.
As I've said, using dd in recovery mode did NOT damage the phone in any possible way, so that is the safest bet.

As for mounting the SD card, search around. I'm afraid this thread is not a tutorial on how to partition and mount a SD card.
 
 
17th April 2011, 11:51 PM |#202  
motafoca's Avatar
Member
Flag Sao Paulo
Thanks Meter: 134
 
More
Tip for those with still bootable phone but have efs+backup

Mount the backup, format efs using fat and
Copy the files 1 by 1
I did that once and it worked
I bricked my phone during copying the files it rebooted
lol

Still trying odin stuff
17th April 2011, 11:55 PM |#203  
Member
Thanks Meter: 3
 
More
Quote:
Originally Posted by mihaivt

1) 23 is hex for 35. I do not know whether in ops file need to have dec or hex. Benjamin suggest dec(35). Maybe somebody with a bricked phone should try first. My phone can still boot . And using official froyo I5500OXFJPD.tar I can see I have WIFI again.

2) I will compare the 2 files attached by you with the ones in previosly stl5.rfs posted by other user. I want to know whether they are the same or are phone specific.
Anyway is another risc to mount /efs rw and overwrite the 2 files

2603 and 2635 are device specific.
18th April 2011, 12:05 AM |#204  
Inactive Recognized Developer
Thanks Meter: 4,053
 
Donate to Me
More
Look at our OPS file:
Code:
0,mibib
1,qcsbl
2,oemsbl
3,amss
4,arm11boot
5,boot
6,recovery
7,system
8,data
9,csc
10,
Look at the reconstructed OPS (from the nID values, decreased by 1 to match OPS structure):
Code:
0,mibib
1,qcsbl
2,oemsbl
3,amss
4,fota
5,arm11boot
6,???
7,???
8,???
32,???
33,???
34,efs2
35,???
Ignoring the efs and unknown partitions, only the first four are in the correct order!

Let's make some (fairly solid) assumptions:
1. We cannot repartition our phone - the option doesn't exist in Odin v4.28).
2. It is possible to flash an EFS file (as Odin v4.28 specifically has an EFS button).
3. The OPS file structure does *not* match the structure reported by the Android kernel (from the "atag", "BIE: nPartition Information / nID" output seen in dmesg). See above for proof why this appears to be the case.

What do you think?
The Following User Says Thank You to psyke83 For This Useful Post: [ View ] Gift psyke83 Ad-Free
18th April 2011, 01:59 AM |#205  
Inactive Recognized Developer
Thanks Meter: 4,053
 
Donate to Me
More
I've made "some" progress towards resolving the different positions reported by the kernel vs the positions in the OPS file.

Look again at this output (NOTE: I added comments to the end of the line to fill in what the partitions are - some are still speculated):
Code:
[BIF: ] nPartition Information (nVol : 0)
nVer : 0x10000
00 / nID:0x01 / nAttr:0x00001012 / 1stVun: 0 / Units: 6 MIBIB
01 / nID:0x02 / nAttr:0x00001012 / 1stVun: 6 / Units: 2 QCSBL
02 / nID:0x03 / nAttr:0x00001012 / 1stVun: 8 / Units: 3 OEMSBL
03 / nID:0x04 / nAttr:0x00001012 / 1stVun: 11 / Units: 100 AMSS
04 / nID:0x23 / nAttr:0x00001101 / 1stVun: 111 / Units: 97 EFS2
05 / nID:0x25 / nAttr:0x00001101 / 1stVun: 208 / Units: 20 NV_BACKUP???
06 / nID:0x05 / nAttr:0x00001001 / 1stVun: 228 / Units: 100 FOTA????
07 / nID:0x06 / nAttr:0x00001012 / 1stVun: 328 / Units: 8 ARM11BOOT
08 / nID:0x07 / nAttr:0x00001012 / 1stVun: 336 / Units: 40 BOOT???
09 / nID:0x08 / nAttr:0x00001012 / 1stVun: 376 / Units: 40 RECOVERY???
10 / nID:0x09 / nAttr:0x00001012 / 1stVun: 416 / Units: 3 ???
11 / nID:0x21 / nAttr:0x00001101 / 1stVun: 419 / Units: 710 SYSTEM
12 / nID:0x22 / nAttr:0x00001101 / 1stVun: 1129 / Units: 775 DATA
13 / nID:0x24 / nAttr:0x00001101 / 1stVun: 1904 / Units: 100 CSC
Here's what I propose:
  • Odin's OPS file is not based on the nID alone.
  • Odin's OPS file is based on the grouping of the type of partition (nAttr) first, followed by the nID of the partitions only that fit in the current group, in alphanumeric order.
  • It appears that Odin flashes the partitions with nAttr 0x00001012, followed by 0x00001011.


I've come up with this so far (in brackets is the nAttr followed by the nID):

Code:
0,mibib (1012, 0x01)
1,qcsbl (1012, 0x02)
2,oemsbl (1012, 0x03)
3,amss (1012, 0x04)
4,arm11boot (1012, 0x06)
5,boot (1012, 0x07)
6,recovery (1012, 0x08)
7,system (1101, 0x21)
8,data (1101, 0x22)
9,efs2 (1101, 0x23)
10,csc (1101, 0x24)
11,nv_backup (1101, 0x25)
The file doesn't seem right, but it's a hell of a lot better than before - only the CSC is out of place.

Problems:
1. I'm not sure about the boot, recovery, fota and nv_backup partitions - they're just semi-educated guesses.
2. I have no idea what partition nID 0x09 with nAttr 0x00001012 can be. It should be position 7 in the OPS file, but that's impossible as the system partition should be there. Perhaps Odin knows that it should be ignored?
3. The efs partition is now in the position where the csc previously was. I don't think this is right.
18th April 2011, 04:34 AM |#206  
Inactive Recognized Developer
Thanks Meter: 4,053
 
Donate to Me
More
Hmm, maybe my theories are all wrong :P

motafoca and I tested several combination (efs in positions 34,35, 23, 22). The fact is that Odin crashes if you try to flash anything above 10, so that's the limit. We tried to flash efs in positions 9 and 10 - no crash, but it didn't solve the problem. Finally, out of desperation we flashed the partition map that's encoded into the boot image:

The strings from the boot image (apparently): http://pastebin.com/BGgfRqVB

Code:
0,mibib
1,qcsbl
2,oemsbl
3,amss
4,efs2
5,nv_backup
6,fota
7,arm11boot
8,boot
9,recovery
10,parameter
11,system
12,userdata
13,cache
That permanently killed his phone. It seems pretty clear that if you flash something besides arm11boot in slot 4, your phone won't even power on.
18th April 2011, 04:31 PM |#207  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by subpsyke

PLEASE, read this thread fully. Hell, even the first post. Running the commands you quoted will brick your phone. Don't say you haven't been warned.

Hi,
Thanks for your reply
I did read this thread fully and understood that DD BRICKS the phone. No questions here.
Also there are beats and pieces stating that there is a safe way to read stl5 file using - su, but i couldn't find how.
what is clear here is that you need:
1. Rooted your phone
2. use adb
3. Do not use DD method on i5500
not sure what's next...

PS: i'm sorry for noob questions but thats what forums made for.. right ?? ask to be heard

Quote:
Originally Posted by BlocK240

I have no idea if the Ace presents the same symptoms as the i5500, but our phone corrupts the efs once it is copied but will work just fine after being copied back.
Using dd from recovery mode should theoretically not require the second command, but I'd rather keep it there for safety purposes.
As I've said, using dd in recovery mode did NOT damage the phone in any possible way, so that is the safest bet.

As for mounting the SD card, search around. I'm afraid this thread is not a tutorial on how to partition and mount a SD card.

Thanks for reply BlocK240.
18th April 2011, 05:13 PM |#208  
Inactive Recognized Developer
Thanks Meter: 4,053
 
Donate to Me
More
Quote:
Originally Posted by s2003r

Hi,
Thanks for your reply
I did read this thread fully and understood that DD BRICKS the phone. No questions here.
Also there are beats and pieces stating that there is a safe way to read stl5 file using - su, but i couldn't find how.
what is clear here is that you need:
1. Rooted your phone
2. use adb
3. Do not use DD method on i5500
not sure what's next...

No, there is no safe way. It is not possible to read a block device (/dev/stl5 or any other) without using superuser (su) privileges anyway.

Oh, and /dev/stl5 is the same as /dev/block/stl5 - they're just symlinks.
The Following User Says Thank You to psyke83 For This Useful Post: [ View ] Gift psyke83 Ad-Free
21st April 2011, 03:17 PM |#209  
Junior Member
Thanks Meter: 0
 
More
I had the misfortune of following the suggested commands (including the dd) and bricked my phone.
I'd really like to try again - but I don't think any solution has been found yet...

I don't know how the people unlock phones on the market... how do they do it? Does anyone know?
21st April 2011, 08:13 PM |#210  
OP Senior Member
Flag Android
Thanks Meter: 409
 
More
Anyone tried unbricking with this: http://life4gadgets.com/2011/04/18/t...-galaxy-i5500/

Dunno why it should work but it says it does.

Cheers

Strings containing efs found in amss:
Code:
-> strings amss|find /i "efs"
EFS h
 efs_deltree () Failed
/.efs_private/iter/%08ld.lnk
/.efs_private/iter
Assertion efs_iter_callback != NULL failed
VP3: Nothing to store in EFS this session
MMGSDI: efs_read procedure failed
MMGSDI: efs_stat procedure failed
EFS File or Dir Not Found
gsdi_efs.c
MMGSDI: efs_mkdir procedure failed
efs_stat procedure success
MMGSDI: efs_stat procedure failed: %x
 efs_deltree () Failed
Assertion efs_iter_callback != NULL failed
OK IMEI EFS File Ready
Saving GPS-to-RTC offsets to EFS
MC_SlowClk: Write EFS file: %d
MC_SlowClk: Reading EFS file
LOC_MW:loc_pa_access_efs_data, ret_val = %d
LOC_MW ERROR:loc_pa_xlate_efs_data_from_locapi_to_pdapi, unknown operation: %d
LOC_MW ERROR:loc_pa_xlate_efs_data_from_locapi_to_pdapi, data size too large: %d > %d
LOC_MW ERROR:loc_pa_xlate_efs_data_from_locapi_to_pdapi, filename is NULL
LOC_MW ERROR:loc_pa_xlate_efs_data_from_locapi_to_pdapi, filename too long, len=%d, max=%
No Private keys  in the EFS,
secsslcert_init failed: No Keys/ in EFS
secsslcert_init failed: No cert/ in EFS
Num EFS Certs %d
fs_device_efs_flash.c
0:EFS2
EFS: Resultant filename is too long
MMGSDI: efs_stat failed on file "%s".
MMGSDI: efs_read failed.
MMGSDI: efs_write failed.
MMGSDI: efs_open Procedure Failed
MMGSDI: efs_write failed
MMGSDI: efs_write failed.
MMGSDI: efs_open failed.
MMGSDI: efs_stat failed.
NULL efs filename ptr
efs_close procedure failed 0x%x
fs_device_efs_flash.c
EFS init failed Error %d
AF_preset_coefs:%x
Writing PND Freq Bias Data to EFS
EFS: Loading SV No Exist List (%lX)
EFS: Loading SBAS Almanac (%d)
EFS: Loading Almanac (%d)
EFS: Loading SBAS Ephemeris (%d)
EFS: Loading Ephemeris (%d)
Invalid parameters when reading EFS record.
EFS DATABASE SYNC ERROR: ALMANAC
EFS: Loading Iono & UTC
EFS DATABASE SYNC ERROR: IONO / UTC
EFS DATABASE SYNC ERROR: IONO UTC
EFS DATABASE SYNC ERROR: POSITION
EFS DATABASE SYNC ERROR: SV HEALTH INFO
EFS DATABASE SYNC ERROR: EPHEMERIS
EFS DATABASE WRITE: XTRA ALM CORRECTIONS
EFS DATABASE SYNC ERROR: SV NO EXIST LIST
mgp_pe_efs.c
EFS: No Almanac available, so injecting default alm from ROM for SV %d, Week %d, ToA %d
EFS DATABASE SYNC ERROR: ALMANAC - Sv = %2d
EFS DATABASE SYNC ERROR: SBAS ALMANAC - Sv = %2d
EFS DATABASE SYNC ERROR: EPHEMERIS - Sv = %2d
EFS DATABASE SYNC ERROR: SBAS EPHEMERIS - Sv = %2d
EFS: Loading SV Health Page
Unable to get efs ram cache data pointer for almanac correction
Deleting existing %s, size %u in efs.  New File is %u bytes
EFS: Loading SBAS Canned SV List
refSID
refSeconds
UimEfsAPDULog.Txt
EFS LOGGED START(idx=%d, mask=0x%x)
EFS LOGGED END
gps_fs_task:%s EFS_PUT %lu  Error Code: %d
gps_fs_task: EFS_PUT: %s %lu  bytes written : %ld
Invalid EFS SBAS Canned List entry: SBAS PRN = %u, Valid = %u
SBAS_Steer: From EFS CANNED SV - %3d
EFS
ASSERT! efs_lseek() failed!
Read NV_SMS_BEARER_PREFS_I failed: %d
Write NV_SMS_BEARER_PREFS_I failed
Create dir in EFS
Create EFS Dir Failed: %d
efs_lstat error %d
Write to efs failed
Error removing file for EFSLog, or no old file to remove
EFS add failed with error %d.
PBM EFS delete failed with error %d.
Could not write to efs buffers.
pbmefs.c
PBM EFS wrile lock callback error Error %d
Failed NVIM EFS initialization
Assertion TRUE == info->efs_valid failed
/.efs_private/.rollback/%08lX.rbk
/.efs_private/.rollback
/.efs_private/.rollback/%s
hc_detect_RND_NBO( x, start_ref=%u, stop_ref=%u, numrefs=%u )
Matched IA using Request Refs
efs_estdio_init failed, efs_errno=%d.
@IPC Log : ss_qxdm_efs_log_replay_timer_set unset
ALM-ECEFsbasAlmanacSet
Param: GPSDIAG_PA_EFS_DATA
gpsdiag_PaEventsDispatchCb: PDSM_PA_EVENT_EFS_DATA received
create cert/ in EFS
secca_init failed: No cert/ in EFS
Num EFS CAs %d
EFS num CA [%d] is larger than allowed
No CA in the EFS, cannot verify certs
efs_estdio_init failed, efs_errno=%d.
NF: SFT RefSV: %2d RefTimeMs %10lu
15IxFileSystemEfs
Failed NVIM EFS initialization
MMGSDI - GSTK ADDITIONAL EFS READ DURING FCN
Maximum EFsmsp count = %d
EFsmsp PI mask has not SCA indicator!!!
There is no SCA mask in EFsmsp PI  : written to EFsmsp PI mask = %x
efs_open failed for %d errno = %d.
efs_open failed for %d errno=%d.
efs_open failed fd=%d errno=%d.
efs_open failed for fd=%d errno=%d.
efs_open failed errno=%d.
efs_close failed for %d errno = %d
efs_lseek failed for %d errno = %d
efs_stat failed errno = %d
efs_lseek failed for fd = %d errno=%d
efs_close failed for %d errno=%d
efs_lseek failed for %d errno=%d
efs_close failed fd=%d errno=%d
efs_read failed for fd=%d errno=%d
efs_close failed for fd=%d errno=%d
efs_write failed for fd=%d errno=%d
efs_read read wrong num of bytes=%d errno=%d
efs_write wrote wrong num of bytes=%d errno=%d
efs_close failed errno=%d
CELLDB EFS Record not available or cannot be trusted
CELLDB EFS WR: Size mismatch
TM_CORE EFS FILE RESP HANDLER result = %d
EFS File path was truncated.  Destination Length %u
TM_PDAPI: PDSM_PA_EFS_DATA: Null file name or file ptr
TM_PDAPI: PDSM_PA_EFS_DATA: Invalid directory file name,  file_operation %d, file len %d
../../modem/uim/mmgsdi/src/gsdi_efs.c
/.efs_private
/.efs_private/iter
EFS LOGGED END
[4]NLMS_preset_coefs : 0x%x
cakefSh
NV read for bearer prefs failed -- reset all to ALLOWED!!
Corrupt value? Resetting bearer_prefs[%d]=%d to WMS_BEARER_USAGE_ALLOWED(%d)
Assertion TRUE == info->efs_valid failed
MMGSDI: EFS PERSO_FILE MISSING
@IPC Log : ss_qxdm_read_item_from_efs(hndle_ss_ipc_log_reqply = NULL) failed!
@SS_QXDM : diagdiag_ss_qxdm_efs_replay_request()
@SS_QXDM : ss_qxdm_ram_to_efs(log_index =%d) Failed!(ss_qxdm_logging_enable = %d)
@LOG : ss_qxdm_ram_to_efs(log_index = %d, current_ram_cnt = %d)
alm-ecefSBASAlmanac
Sending EndOfModPrdInd refSFN %d start %d end %d
MCCH critInfo refSFN %d curSFN %d latestDRX_SFN %d DRX mode %d already passed
MC msg Delete Freq Bias from EFS rcvd
IxFileSystemEfs::Read returned %d
IxFileSystemEfs::ChMod returned %d
IxFileSystemEfs::Close returned %d
IxFileSystemEfs::Truncate returned %d
IxFileSystemEfs::FTruncate returned %d
IxFileSystemEfs::Write returned %d
IxFileSystemEfs::Initialize returned %d
IxFileSystemEfs::LSeek returned %d
IxFileSystemEfs::ReadLink returned %d
IxFileSystemEfs::SymLink returned %d
IxFileSystemEfs::Unlink returned %d
IxFileSystemEfs::eek:pen returned %d
IxFileSystemEfs::ChOwn returned %d
IxFileSystemEfs::PowerDown returned %d
IxFileSystemEfs::ReadDir returned %d
IxFileSystemEfs::CloseDir returned %d
IxFileSystemEfs::MkDir returned %d
IxFileSystemEfs::RmDir returned %d
IxFileSystemEfs::eek:penDir returned %d
IxFileSystemEfs::StatVfs returned %d
IxFileSystemEfs::FStatVfs returned %d
IxFileSystemEfs::Access returned %d
IxFileSystemEfs::Stat returned %d
IxFileSystemEfs::FStat returned %d
IxFileSystemEfs::LStat returned %d
IxFileSystemEfs::Mount returned %d
IxFileSystemEfs::Umount returned %d
IxFileSystemEfs::Remount returned %d
IxFileSystemEFS.cpp
and for string imei:
Code:
-> strings amss|find /i "imei"
 .... IMEI
oemapi_imei_reboot_ind
Haven't Valid IMEI
oem_imeitool.c
valid_imei1:%d valid_imei2:%d
Need Creat IMEI File
Can't Creat IMEI File
mits/imeitool.txt
OK IMEI EFS File Ready
Assertion imei_ptr != NULL failed
Assertion imeisv != NULL failed
../../mits/oem/oem/oem_imeitool.c
oem_imeitool.c
Can't Creat IMEI File
hsu_conf_sel_nv_get_imei: Failed to read IMEI
*_esn_imei_read(): Couldn't read NV_ESN_I and NV_UE_IMEI_I from NV
IMEI length must be 8
Error=%d reading IMEI
Bad identity length=%d for IMEI
IMEI = %s, Key = %s
ui_ipc_imei_pre_config_cfrm result:
oemapi_imei_pre_config_cfrm result:
send IMEI Start Ind to PDA
Invalid IMEI
ui_ipc_imei_write_item_cnfm result:%d
ui_ipc_imei_start_cfrm result:%d
ui_ipc_imei_compare_ind
ui_ipc_imei_item_write_ind
ui_ipc_imei_check_ind
oemapi_imei_mass_storage_info_ind
oemapi_imei_mass_storage_file_number_ind
ui_ipc_imei_clear_reset_result_ind
ui_ipc_imei_pre_config_noti
ui_ipc_imei_update_item_noti
oemapi_imei_verify_compare_status_noti
oemapi_imei_compare_item_cfrm
oemapi_imei_mass_storage_info_cfrm
oemapi_imei_mass_storage_file_number_cfrm
oemapi_imei_verify_factory_reset_cfrm
oemapi_imei.c
IMEI :len:%d NUM item:%d
can't read imei file
oemapi_imei_verify_factory_reset_event
oemapi_imei_start_event
realTimeIntegrityRequested
IMEI
emergency call is restricted... imei_status .. %d
IMEI TLV Err: NULL
IMEISV TLV Err: NULL
** Packing imei
** Packing imeisv
IMEI:%s len:%d
Couldn't read IMEI
imei
rrc_CipheringModeInfo_rb_DL_CiphActivationTimeInfo_present not present
NV IMEISV_SVN %d > 98 using default value 0
Unable to read IMEI from NV
Assertion imei_ptr != NULL failed
Assertion imeisv != NULL failed
NVRead IMEI failed=%d, use default
NVRead IMEISV_SVN failed=%d, use default
Problem reading IMEI from NV
Invalid IMEI value from NV
IMEI not programmed in NV
oem_imeisec.c
imeisv_length = %d (10)
Invaild IMEISV, check IMEI in NV
imeisv_ascii[%d] = 0x%x
TransmissionTimeInterval
SFN-TimeInfo
DurationTimeInfo
RB-ActivationTimeInfo
IMEI-Digit
RB-ActivationTimeInfoList
MBMS-NetworkStandardTimeInformation-LCR-v890ext
UE-Positioning-GANSS-RealTimeIntegrity
PLCIRATWaitingForListSrchTimeInd
Failed to allocate memory for IMEI
 [1] READ IMEI
 IMEI :
 IMEI NOT ACTIVE
IMEI MATCHED
Failed to allocate memory for IMEI
IMEI not accepted
MMGSDI: Could not get IMEI
MMGSDI: PERSO: IMEI Does not match
PERSO: me_imei length is zero
../../mits/oem/oemapi/oemapi_imei.c
oemapi_imei.c
can't read imei file
IMEI Already exist Error !!
Bad IMEI: %d
IMEI Write command received
Error reading IMEI
IMEI TYPE is correct..%d
IMEI TYPE is not correct..%d
IMEI wrong size %d from ghdi
MMGSDI: PERSO: Could not get IMEI
MMGSDI: PERSO: IMEI is not set or improperly set
IPC_IMEI_PRE_CONFIG
IPC_IMEI_COMPARE_ITEM
IPC_IMEI_WRITE_ITEM
IPC_IMEI_CHECK_DEVICE_INFO
IPC_IMEI_MASS_STORAGE_INFO
IPC_IMEI_VERIFY_FACTORY_RESET
IPC_IMEI_REBOOT
IPC_IMEI_START
iMEI
mbmsNetworkStandardTimeInformation-LCR
gANSS-TimeId
ganssTimeId
gANSS-timeId
transmissionTimeInterval
sfn-TimeInfo
durationTimeInfo
rb-DL-CiphActivationTimeInfo
rb-UL-CiphActivationTimeInfo
timeInfo
realTimeIntegrityRequest
uePositioningGANSSRealTimeIntegrity
ganssRealTimeIntegrity
ue-positioning-GANSS-realTimeIntegrity
ue-positioning-GPS-Real-timeIntegrity
23rd April 2011, 10:05 AM |#211  
Member
Thanks Meter: 3
 
More
Quote:
Originally Posted by tweakradje

Anyone tried unbricking with this: http://life4gadgets.com/2011/04/18/t...-galaxy-i5500/

Dunno why it should work but it says it does.

Cheers

Strings containing efs found in amss:

Code:
-> strings amss|find /i "efs"
EFS h
 efs_deltree () Failed
/.efs_private/iter/%08ld.lnk
/.efs_private/iter
Assertion efs_iter_callback != NULL failed
VP3: Nothing to store in EFS this session
MMGSDI: efs_read procedure failed
MMGSDI: efs_stat procedure failed
EFS File or Dir Not Found
gsdi_efs.c
MMGSDI: efs_mkdir procedure failed
efs_stat procedure success
MMGSDI: efs_stat procedure failed: %x
 efs_deltree () Failed
Assertion efs_iter_callback != NULL failed
OK IMEI EFS File Ready
Saving GPS-to-RTC offsets to EFS
MC_SlowClk: Write EFS file: %d
MC_SlowClk: Reading EFS file
LOC_MW:loc_pa_access_efs_data, ret_val = %d
LOC_MW ERROR:loc_pa_xlate_efs_data_from_locapi_to_pdapi, unknown operation: %d
LOC_MW ERROR:loc_pa_xlate_efs_data_from_locapi_to_pdapi, data size too large: %d > %d
LOC_MW ERROR:loc_pa_xlate_efs_data_from_locapi_to_pdapi, filename is NULL
LOC_MW ERROR:loc_pa_xlate_efs_data_from_locapi_to_pdapi, filename too long, len=%d, max=%
No Private keys  in the EFS,
secsslcert_init failed: No Keys/ in EFS
secsslcert_init failed: No cert/ in EFS
Num EFS Certs %d
fs_device_efs_flash.c
0:EFS2
EFS: Resultant filename is too long
MMGSDI: efs_stat failed on file "%s".
MMGSDI: efs_read failed.
MMGSDI: efs_write failed.
MMGSDI: efs_open Procedure Failed
MMGSDI: efs_write failed
MMGSDI: efs_write failed.
MMGSDI: efs_open failed.
MMGSDI: efs_stat failed.
NULL efs filename ptr
efs_close procedure failed 0x%x
fs_device_efs_flash.c
EFS init failed Error %d
AF_preset_coefs:%x
Writing PND Freq Bias Data to EFS
EFS: Loading SV No Exist List (%lX)
EFS: Loading SBAS Almanac (%d)
EFS: Loading Almanac (%d)
EFS: Loading SBAS Ephemeris (%d)
EFS: Loading Ephemeris (%d)
Invalid parameters when reading EFS record.
EFS DATABASE SYNC ERROR: ALMANAC
EFS: Loading Iono & UTC
EFS DATABASE SYNC ERROR: IONO / UTC
EFS DATABASE SYNC ERROR: IONO UTC
EFS DATABASE SYNC ERROR: POSITION
EFS DATABASE SYNC ERROR: SV HEALTH INFO
EFS DATABASE SYNC ERROR: EPHEMERIS
EFS DATABASE WRITE: XTRA ALM CORRECTIONS
EFS DATABASE SYNC ERROR: SV NO EXIST LIST
mgp_pe_efs.c
EFS: No Almanac available, so injecting default alm from ROM for SV %d, Week %d, ToA %d
EFS DATABASE SYNC ERROR: ALMANAC - Sv = %2d
EFS DATABASE SYNC ERROR: SBAS ALMANAC - Sv = %2d
EFS DATABASE SYNC ERROR: EPHEMERIS - Sv = %2d
EFS DATABASE SYNC ERROR: SBAS EPHEMERIS - Sv = %2d
EFS: Loading SV Health Page
Unable to get efs ram cache data pointer for almanac correction
Deleting existing %s, size %u in efs.  New File is %u bytes
EFS: Loading SBAS Canned SV List
refSID
refSeconds
UimEfsAPDULog.Txt
EFS LOGGED START(idx=%d, mask=0x%x)
EFS LOGGED END
gps_fs_task:%s EFS_PUT %lu  Error Code: %d
gps_fs_task: EFS_PUT: %s %lu  bytes written : %ld
Invalid EFS SBAS Canned List entry: SBAS PRN = %u, Valid = %u
SBAS_Steer: From EFS CANNED SV - %3d
EFS
ASSERT! efs_lseek() failed!
Read NV_SMS_BEARER_PREFS_I failed: %d
Write NV_SMS_BEARER_PREFS_I failed
Create dir in EFS
Create EFS Dir Failed: %d
efs_lstat error %d
Write to efs failed
Error removing file for EFSLog, or no old file to remove
EFS add failed with error %d.
PBM EFS delete failed with error %d.
Could not write to efs buffers.
pbmefs.c
PBM EFS wrile lock callback error Error %d
Failed NVIM EFS initialization
Assertion TRUE == info->efs_valid failed
/.efs_private/.rollback/%08lX.rbk
/.efs_private/.rollback
/.efs_private/.rollback/%s
hc_detect_RND_NBO( x, start_ref=%u, stop_ref=%u, numrefs=%u )
Matched IA using Request Refs
efs_estdio_init failed, efs_errno=%d.
@IPC Log : ss_qxdm_efs_log_replay_timer_set unset
ALM-ECEFsbasAlmanacSet
Param: GPSDIAG_PA_EFS_DATA
gpsdiag_PaEventsDispatchCb: PDSM_PA_EVENT_EFS_DATA received
create cert/ in EFS
secca_init failed: No cert/ in EFS
Num EFS CAs %d
EFS num CA [%d] is larger than allowed
No CA in the EFS, cannot verify certs
efs_estdio_init failed, efs_errno=%d.
NF: SFT RefSV: %2d RefTimeMs %10lu
15IxFileSystemEfs
Failed NVIM EFS initialization
MMGSDI - GSTK ADDITIONAL EFS READ DURING FCN
Maximum EFsmsp count = %d
EFsmsp PI mask has not SCA indicator!!!
There is no SCA mask in EFsmsp PI  : written to EFsmsp PI mask = %x
efs_open failed for %d errno = %d.
efs_open failed for %d errno=%d.
efs_open failed fd=%d errno=%d.
efs_open failed for fd=%d errno=%d.
efs_open failed errno=%d.
efs_close failed for %d errno = %d
efs_lseek failed for %d errno = %d
efs_stat failed errno = %d
efs_lseek failed for fd = %d errno=%d
efs_close failed for %d errno=%d
efs_lseek failed for %d errno=%d
efs_close failed fd=%d errno=%d
efs_read failed for fd=%d errno=%d
efs_close failed for fd=%d errno=%d
efs_write failed for fd=%d errno=%d
efs_read read wrong num of bytes=%d errno=%d
efs_write wrote wrong num of bytes=%d errno=%d
efs_close failed errno=%d
CELLDB EFS Record not available or cannot be trusted
CELLDB EFS WR: Size mismatch
TM_CORE EFS FILE RESP HANDLER result = %d
EFS File path was truncated.  Destination Length %u
TM_PDAPI: PDSM_PA_EFS_DATA: Null file name or file ptr
TM_PDAPI: PDSM_PA_EFS_DATA: Invalid directory file name,  file_operation %d, file len %d
../../modem/uim/mmgsdi/src/gsdi_efs.c
/.efs_private
/.efs_private/iter
EFS LOGGED END
[4]NLMS_preset_coefs : 0x%x
cakefSh
NV read for bearer prefs failed -- reset all to ALLOWED!!
Corrupt value? Resetting bearer_prefs[%d]=%d to WMS_BEARER_USAGE_ALLOWED(%d)
Assertion TRUE == info->efs_valid failed
MMGSDI: EFS PERSO_FILE MISSING
@IPC Log : ss_qxdm_read_item_from_efs(hndle_ss_ipc_log_reqply = NULL) failed!
@SS_QXDM : diagdiag_ss_qxdm_efs_replay_request()
@SS_QXDM : ss_qxdm_ram_to_efs(log_index =%d) Failed!(ss_qxdm_logging_enable = %d)
@LOG : ss_qxdm_ram_to_efs(log_index = %d, current_ram_cnt = %d)
alm-ecefSBASAlmanac
Sending EndOfModPrdInd refSFN %d start %d end %d
MCCH critInfo refSFN %d curSFN %d latestDRX_SFN %d DRX mode %d already passed
MC msg Delete Freq Bias from EFS rcvd
IxFileSystemEfs::Read returned %d
IxFileSystemEfs::ChMod returned %d
IxFileSystemEfs::Close returned %d
IxFileSystemEfs::Truncate returned %d
IxFileSystemEfs::FTruncate returned %d
IxFileSystemEfs::Write returned %d
IxFileSystemEfs::Initialize returned %d
IxFileSystemEfs::LSeek returned %d
IxFileSystemEfs::ReadLink returned %d
IxFileSystemEfs::SymLink returned %d
IxFileSystemEfs::Unlink returned %d
IxFileSystemEfs::eek:pen returned %d
IxFileSystemEfs::ChOwn returned %d
IxFileSystemEfs::PowerDown returned %d
IxFileSystemEfs::ReadDir returned %d
IxFileSystemEfs::CloseDir returned %d
IxFileSystemEfs::MkDir returned %d
IxFileSystemEfs::RmDir returned %d
IxFileSystemEfs::eek:penDir returned %d
IxFileSystemEfs::StatVfs returned %d
IxFileSystemEfs::FStatVfs returned %d
IxFileSystemEfs::Access returned %d
IxFileSystemEfs::Stat returned %d
IxFileSystemEfs::FStat returned %d
IxFileSystemEfs::LStat returned %d
IxFileSystemEfs::Mount returned %d
IxFileSystemEfs::Umount returned %d
IxFileSystemEfs::Remount returned %d
IxFileSystemEFS.cpp
and for string imei:
Code:
-> strings amss|find /i "imei"
 .... IMEI
oemapi_imei_reboot_ind
Haven't Valid IMEI
oem_imeitool.c
valid_imei1:%d valid_imei2:%d
Need Creat IMEI File
Can't Creat IMEI File
mits/imeitool.txt
OK IMEI EFS File Ready
Assertion imei_ptr != NULL failed
Assertion imeisv != NULL failed
../../mits/oem/oem/oem_imeitool.c
oem_imeitool.c
Can't Creat IMEI File
hsu_conf_sel_nv_get_imei: Failed to read IMEI
*_esn_imei_read(): Couldn't read NV_ESN_I and NV_UE_IMEI_I from NV
IMEI length must be 8
Error=%d reading IMEI
Bad identity length=%d for IMEI
IMEI = %s, Key = %s
ui_ipc_imei_pre_config_cfrm result:
oemapi_imei_pre_config_cfrm result:
send IMEI Start Ind to PDA
Invalid IMEI
ui_ipc_imei_write_item_cnfm result:%d
ui_ipc_imei_start_cfrm result:%d
ui_ipc_imei_compare_ind
ui_ipc_imei_item_write_ind
ui_ipc_imei_check_ind
oemapi_imei_mass_storage_info_ind
oemapi_imei_mass_storage_file_number_ind
ui_ipc_imei_clear_reset_result_ind
ui_ipc_imei_pre_config_noti
ui_ipc_imei_update_item_noti
oemapi_imei_verify_compare_status_noti
oemapi_imei_compare_item_cfrm
oemapi_imei_mass_storage_info_cfrm
oemapi_imei_mass_storage_file_number_cfrm
oemapi_imei_verify_factory_reset_cfrm
oemapi_imei.c
IMEI :len:%d NUM item:%d
can't read imei file
oemapi_imei_verify_factory_reset_event
oemapi_imei_start_event
realTimeIntegrityRequested
IMEI
emergency call is restricted... imei_status .. %d
IMEI TLV Err: NULL
IMEISV TLV Err: NULL
** Packing imei
** Packing imeisv
IMEI:%s len:%d
Couldn't read IMEI
imei
rrc_CipheringModeInfo_rb_DL_CiphActivationTimeInfo_present not present
NV IMEISV_SVN %d > 98 using default value 0
Unable to read IMEI from NV
Assertion imei_ptr != NULL failed
Assertion imeisv != NULL failed
NVRead IMEI failed=%d, use default
NVRead IMEISV_SVN failed=%d, use default
Problem reading IMEI from NV
Invalid IMEI value from NV
IMEI not programmed in NV
oem_imeisec.c
imeisv_length = %d (10)
Invaild IMEISV, check IMEI in NV
imeisv_ascii[%d] = 0x%x
TransmissionTimeInterval
SFN-TimeInfo
DurationTimeInfo
RB-ActivationTimeInfo
IMEI-Digit
RB-ActivationTimeInfoList
MBMS-NetworkStandardTimeInformation-LCR-v890ext
UE-Positioning-GANSS-RealTimeIntegrity
PLCIRATWaitingForListSrchTimeInd
Failed to allocate memory for IMEI
 [1] READ IMEI
 IMEI :
 IMEI NOT ACTIVE
IMEI MATCHED
Failed to allocate memory for IMEI
IMEI not accepted
MMGSDI: Could not get IMEI
MMGSDI: PERSO: IMEI Does not match
PERSO: me_imei length is zero
../../mits/oem/oemapi/oemapi_imei.c
oemapi_imei.c
can't read imei file
IMEI Already exist Error !!
Bad IMEI: %d
IMEI Write command received
Error reading IMEI
IMEI TYPE is correct..%d
IMEI TYPE is not correct..%d
IMEI wrong size %d from ghdi
MMGSDI: PERSO: Could not get IMEI
MMGSDI: PERSO: IMEI is not set or improperly set
IPC_IMEI_PRE_CONFIG
IPC_IMEI_COMPARE_ITEM
IPC_IMEI_WRITE_ITEM
IPC_IMEI_CHECK_DEVICE_INFO
IPC_IMEI_MASS_STORAGE_INFO
IPC_IMEI_VERIFY_FACTORY_RESET
IPC_IMEI_REBOOT
IPC_IMEI_START
iMEI
mbmsNetworkStandardTimeInformation-LCR
gANSS-TimeId
ganssTimeId
gANSS-timeId
transmissionTimeInterval
sfn-TimeInfo
durationTimeInfo
rb-DL-CiphActivationTimeInfo
rb-UL-CiphActivationTimeInfo
timeInfo
realTimeIntegrityRequest
uePositioningGANSSRealTimeIntegrity
ganssRealTimeIntegrity
ue-positioning-GANSS-realTimeIntegrity
ue-positioning-GPS-Real-timeIntegrity

It's been stated in the comments by the one who posted that tutorial that it does not work.
Post Reply Subscribe to Thread

Tags
efs, i5500, nv_data.bin, unlock

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes