Guest dt_matthews Posted October 12, 2011 Report Posted October 12, 2011 Isn't it possible to find the unlock through matematics?...if you have 3 different IMEI + unlock codes then maybe a relationship can be found? Just an idea because I was thinking how its possible to make a unlock generator. in theory I think you are right but I suspect it would in practice be some pretty serious maths to find the pattern that resolves to a repeatable algorithm and hence an unlock code generator, if nothing else the number of input parameters that it might use could be quite extensive (i.e. imei, other unique hardware identifiers, other network assigned id's) etc.
Guest Amphoras Posted October 12, 2011 Report Posted October 12, 2011 Isn't it possible to find the unlock through matematics?...if you have 3 different IMEI + unlock codes then maybe a relationship can be found? Just an idea because I was thinking how its possible to make a unlock generator. It would probably be difficult, but maybe possible. Unfortunately we only have one IMEI/unlock code so can't really do anything.
Guest Navie Posted October 12, 2011 Report Posted October 12, 2011 It would probably be difficult, but maybe possible. Unfortunately we only have one IMEI/unlock code so can't really do anything. I guess its a good thing that there are no decimal numbers involved, unless they are rounded.
Guest Navie Posted October 12, 2011 Report Posted October 12, 2011 (edited) Here is some mathematics, its extremely simple and if you can find a simple link then you can get close to an answer... Lets says our IMEI numbers are 63 and 79, yeah? Now lets pretend the code is generated in the following way, the IMEI numbers are in brackets, the algorithm exists of *2.1 +49.7 * 10 / 52... (63) * 2.1 + 49.7 * 10 / 52 = 35.0 (79) * 2.1 + 49.7 * 10 / 52 = 41.4615384 If you can't get the right answer...press equals after every function and then continue, so...you do 63 * 2.1 and then press equals, then you multiply by 49.7 and press equals and so on. So... IMEI is 63 and unlock code is 35.0 IMEI is 79 and unlock code is 41.4615384 Now we have these 2 sets of IMEI + unlock codes. All we do is find the ratio for both the unlock codes for the 2 sets we already have: Once again...the unlock codes are 41.4615384 and 35.0 41.4615384 - 35.0 = 6.4615384, now we have this number we can relate this to both the IMEI numbers (63 and 79) by the difference, the differece between 79 & 63 is 16, so...divide 6.4615384 by 16 and we have...0.40384615, this is the number we will use to find the unlock code for any given IMEI number (we will call 0.40384615 the "base number"), the base number will be used in conjunction to one of the sets we already know the IMEI + unlock for (we will use 79 in this case). Okay...now lets say we want to find the unlock for the IMEI number of 100, all we do is take the base number (0.40384615) and multiply it by the difference of the 'known set' number of 79 as previosuly mentioned, 100 -79 = 21, so 0.40384615 * 21 = 8.48076915, all we have to do now is add the unlock code of the IMEI for 79: 8.48076915 + 41.4615384 = 49.94230755 You can check whether the unlock for IMEI number 100 is right or not: (100) * 2.1 + 49.7 * 10 / 52 = 49.94230769, the numer 49.94230769 is not exactly correct, that must be to not fully rounding off the numbers or missing out something somewhere! Edited October 12, 2011 by Navie
Guest glossywhite Posted October 12, 2011 Report Posted October 12, 2011 Here is some mathematics, its extremely simple and if you can find a simple link then you can get close to an answer... Lets says our IMEI numbers are 63 and 79, yeah? Now lets pretend the code is generated in the following way, the IMEI numbers are in brackets... (63) * 2.1 + 49.7 * 10 / 52 = 35.0 (79) * 2.1 + 49.7 * 10 / 52 = 41.4615384 So... IMEI is 63 and unlock code is 35.0 IMEI is 79 and unlock code is 41.4615384 Now we have these 2 sets of IMEI + unlock codes. All we do is find the ratio for both the unlock codes for the 2 sets we already have: Once again...the unlock codes are 41.4615384 and 35.0 41.4615384 - 35.0 = 6.4615384, now we have this number we can relate this to both the IMEI numbers (63 and 79) by the difference, the differece between 79 & 63 is 16, so...divide 6.4615384 by 16 and we have...0.40384615, this is the number we will use to find the unlock code for any given IMEI number (we will call 0.40384615 the "base number"), the base number will be used in conjunction to one of the sets we already know the IMEI + unlock for (we will use 79 in this case). Okay...now lets say we want to find the unlock for the IMEI number of 100, all we do is take the base number (0.40384615) and multiply it by the difference the 'known set' number of 79 as previosuly mentioned, 100 -79 = 21, so 0.40384615 * 21 = 8.48076915, all we have to do now is add the unlock code of the IMEI for 79: 8.48076915 + 41.4615384 = 49.94230755 You can check whether the unlock for IMEI number 100 is right or not: (100) * 2.1 + 49.7 * 10 / 52 = 49.94230769, not exactly correct, that must be to not fullt rounding off the numbers somewhere! I can just picture someone stumbling upon this thread, and trying out the codes... :lol:
Guest Navie Posted October 12, 2011 Report Posted October 12, 2011 Here is some mathematics, its extremely simple and if you can find a simple link then you can get close to an answer... Lets says our IMEI numbers are 63 and 79, yeah? Now lets pretend the code is generated in the following way, the IMEI numbers are in brackets... (63) * 2.1 + 49.7 * 10 / 52 = 35.0 (79) * 2.1 + 49.7 * 10 / 52 = 41.4615384 So... IMEI is 63 and unlock code is 35.0 IMEI is 79 and unlock code is 41.4615384 Now we have these 2 sets of IMEI + unlock codes. All we do is find the ratio for both the unlock codes for the 2 sets we already have: Once again...the unlock codes are 41.4615384 and 35.0 41.4615384 - 35.0 = 6.4615384, now we have this number we can relate this to both the IMEI numbers (63 and 79) by the difference, the differece between 79 & 63 is 16, so...divide 6.4615384 by 16 and we have...0.40384615, this is the number we will use to find the unlock code for any given IMEI number (we will call 0.40384615 the "base number"), the base number will be used in conjunction to one of the sets we already know the IMEI + unlock for (we will use 79 in this case). Okay...now lets say we want to find the unlock for the IMEI number of 100, all we do is take the base number (0.40384615) and multiply it by the difference the 'known set' number of 79 as previosuly mentioned, 100 -79 = 21, so 0.40384615 * 21 = 8.48076915, all we have to do now is add the unlock code of the IMEI for 79: 8.48076915 + 41.4615384 = 49.94230755 You can check whether the unlock for IMEI number 100 is right or not: (100) * 2.1 + 49.7 * 10 / 52 = 49.94230769, not exactly correct, that must be to not fullt rounding off the numbers somewhere! I know the algorithm will be much more complex than this, however...its possible to find a solution, you can maybe do it by trial and error, which may take years, however...if a mathematical way of getting to a number can be fonud then the unlock solution can be found. One thing I have read on here is that the unlock may exist of a random number and if this were the case then that would make things extremely difficult.
Guest Navie Posted October 12, 2011 Report Posted October 12, 2011 (edited) I can just picture someone stumbling upon this thread, and trying out the codes... :lol: That was an example, the possibility does exist though to apply the same sort of method for the IMEI + unlock codes, whatever the algorithm is...its possible to get the solution if random numbers aren't added. Edited October 12, 2011 by Navie
Guest TouchyAndalou Posted October 12, 2011 Report Posted October 12, 2011 If anybody goes to school or university tomorrow and stumbles across a janitor with a name badge reading "Good Will hunting" scribbling complex sums and equations on a blackboard, please ask him to solve our little unlock problem!
Guest putbinoot Posted October 12, 2011 Report Posted October 12, 2011 One thing I have read on here is that the unlock may exist of a random number and if this were the case then that would make things extremely difficult. Don't quote me on this but there is no such thing as a random number, zte and orange will have their own algorithm based on the imei number i think with the two results used to obtain the code. Just my un educated guess.
Guest tillaz Posted October 12, 2011 Report Posted October 12, 2011 (edited) Don't quote me on this but there is no such thing as a random number, zte and orange will have their own algorithm based on the imei number i think with the two results used to obtain the code. Just my un educated guess. they may not be random but i think orange do add numbers to the code as its now 16 digits long, & from wot other people have said.. Edited October 12, 2011 by tillaz
Guest Navie Posted October 13, 2011 Report Posted October 13, 2011 they may not be random but i think orange do add numbers to the code as its now 16 digits long, & from wot other people have said.. If there was 3 sets of IMEI + unlock codes then I think I could try and related the numbers, 2 sets for forming a relationship between the two and the last set for checking to see if the relationship holds true.
Guest gregorv Posted October 13, 2011 Report Posted October 13, 2011 do we really have only one unlock code? zta skate owners with unlock codes, pleaseeee send ime1 and unlock codes to NAVIE
Guest gitf@ce Posted October 13, 2011 Report Posted October 13, 2011 Didn't Daddy Tickles and dadashi both say they had one?
Guest Amphoras Posted October 13, 2011 Report Posted October 13, 2011 Didn't Daddy Tickles and dadashi both say they had one? Yes, we have Daddy Tickles.
Guest Navie Posted October 13, 2011 Report Posted October 13, 2011 If you guys can post your IMEI numbers and codes please, that's would be great, I need 3 sets.
Guest gitf@ce Posted October 13, 2011 Report Posted October 13, 2011 I've just been in touch with a guy at Orange, and spun a bit of a yarn about one of the OMC's I have. He seems quite confident I will get my code between 7-14 days. If I do I have no problem sharing my details just like Daddy Tickles did. Fingers crossed ;)
Guest gregorv Posted October 13, 2011 Report Posted October 13, 2011 of course you can send codes via private messages, so orange can not make any problems (ime1 lock?)
Guest Navie Posted October 13, 2011 Report Posted October 13, 2011 of course you can send codes via private messages, so orange can not make any problems (ime1 lock?) Yeah...that's a good idea :)
Guest glossywhite Posted October 13, 2011 Report Posted October 13, 2011 Strings dump of "qcnvitems.odex" from /system/framework: 7cq5] 1$ R 45B* 4$ R !r2R !b##P !Sp !Sp !b##P %#UU !b##P #50S !r##P !"5! !r#SR !b##P Cn J Cn J cn G Cn J cn G $#DU 3n G q 5 "#!V "#!V "#!V "#!V "#!V "#!V "#!V n : &5aY Dn G Dn G BYTE %02d : %s raw data = ? raw data = a 1 ci nv23 ilength is NvBdAddrType ilength is NvIntegerEx ilength is NvProxiCalDataType ilength is NvTouchCalDataType ilength is NvWifiAddrType ilength is raw data respone date= ### getMobDirNumber() ### setMobDirNumber() %02x%02x%02x%02x %02x%02x%02x%02x%02x%02x %02x:%02x:%02x:%02x:%02x:%02x %08x%08x%08x%08x%08x%08x%08x %d : #***zhoujing*** parseMeid %s = 0x%x $***zhoujing***NvMeidType::mMeid=0x%x %***zhoujing***QcNvItems::setMeid():%s 00000000 0123456789abcdef 44444 5555 <clinit> <init> AutoAnswer BC0 A BC0 B BC1 BC10 BC11 BC12 BC14 BC15 BC16 BC2 BC3 BC4 BC5 BC6 BC7 BC8 BC9 BaseQCNvItemType.java DCS 1800 EGSM 900 EccListType FALSE GSM 450 GSM 480 GSM 750 GSM 850 GSM PCS 1900 GSM railways 900 GetEmInfo GetPesnFromCard GetPesnFromPhone GetPrlVersion HEADER_SIZE IQcNvItems.java !Incorrectly formatted IP Address. Indexofinfo Invalid phone number LBSS LENGTH_OF_ZTE_SMS_DESTNUMBER LENGTH_OF_ZTE_SMS_INFO LENGTH_OF_ZTE_SMS_PREFIX LLII LOG_TAG Landroid/os/AsyncResult; Landroid/util/Log; )Lcom/android/internal/telephony/IccUtils; 1Lcom/android/qualcomm/qcnvitems/BaseQCNvItemType; 6Lcom/android/qualcomm/qcnvitems/IQcNvItems$AutoAnswer; 6Lcom/android/qualcomm/qcnvitems/IQcNvItems$SidNidPair; 9Lcom/android/qualcomm/qcnvitems/IQcNvItems$VocodeSetting; +Lcom/android/qualcomm/qcnvitems/IQcNvItems; ,Lcom/android/qualcomm/qcnvitems/QcNvItemIds; :Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$EccListType; BLcom/android/qualcomm/qcnvitems/QcNvItemTypes$Nv23SmsRegisterType; ?Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvAutoAnswerType; ALcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvBandPref3263Type; =Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvBandPrefType; ;Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvBdAddrType; 5Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvByte; <Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvCallCntType; ;Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvCdmaChType; >Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvDirNumberType; BLcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvEmFactoryInfoType; ?Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvHomeSidNidType; =Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvImsi1112Type; @Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvImsiAddrNumType; <Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvImsiMccType; 9Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvImsiType; 8Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvInteger; :Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvIntegerEx; =Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvLockCodeType; 8Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvMDNType; 9Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvMeidType; 9Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvMin1Type; 9Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvMin2Type; @Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvPrefVoiceSoType; ALcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvProxiCalDataType; ?Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvRfBcConfigType; <Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvSecCodeType; 6Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvShort; ?Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvSidNidPairType; ;Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvSidNidType; 8Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvSidType; =Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvSysSwVerType; ALcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvTouchCalDataType; =Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvWifiAddrType; ILcom/android/qualcomm/qcnvitems/QcNvItemTypes$nv_em_locknetworkInfo_type; ILcom/android/qualcomm/qcnvitems/QcNvItemTypes$nv_em_manufactoryInfo_type; ALcom/android/qualcomm/qcnvitems/QcNvItemTypes$nv_zteSmsInfo_type; .Lcom/android/qualcomm/qcnvitems/QcNvItemTypes; *Lcom/android/qualcomm/qcnvitems/QcNvItems; *Lcom/android/qualcomm/qcrilhook/QcRilHook; "Ldalvik/annotation/EnclosingClass; Ldalvik/annotation/InnerClass; !Ldalvik/annotation/MemberClasses; Ldalvik/annotation/Throws; Ljava/io/IOException; Ljava/io/PrintStream; Ljava/lang/Boolean; Ljava/lang/Byte; Ljava/lang/Character; Ljava/lang/Class; Ljava/lang/Exception; Ljava/lang/Integer; Ljava/lang/Long; !Ljava/lang/NumberFormatException; Ljava/lang/Object; Ljava/lang/Short; Ljava/lang/String; Ljava/lang/StringBuilder; Ljava/lang/System; Ljava/lang/Throwable; Ljava/lang/reflect/Array; Ljava/nio/ByteBuffer; Ljava/nio/ByteOrder; )Ljava/security/InvalidParameterException; NAM: %d, SID: %d NAM: %x, mDigits: %x NV_AIR_CNT_I NV_ANALOG_HOME_SID_I NV_AUTO_ANSWER_I NV_BAND_PREF_16_31_I NV_BAND_PREF_32_63_I NV_BAND_PREF_I NV_BD_ADDR_I NV_BD_ADDR_SIZE NV_COUNT_I NV_DETECT_HW_RESET_I NV_DIAG_DEBUG_CONTROL_I NV_DIAG_DEBUG_DETAIL_I NV_DIR_NUMBER_I NV_DIR_NUMBER_PCS_I NV_DIR_NUMB_SIZ NV_DS_DEFAULT_BAUDRATE_I NV_ECC_LIST_I NV_ECC_NUMBER_SIZE NV_EM_BOARDSERIAL_SIZE NV_EM_LINEINFO_SIZ NV_EM_LOCKNETWORKINFOR_I NV_EM_MANUFACTORYINFOR_I NV_EM_SER_SIZ NV_EM_TESTFLAG_SIZE NV_EM_TESTINFO_SIZ NV_ERR_FATAL_OPTIONS_I NV_EVRC_PRI_I NV_EXP_PESN_I NV_EXP_PRL_I NV_GPS1_PDE_ADDRESS_I NV_GPS1_PDE_PORT_I NV_HOME_SID_NID_I NV_IMSI_11_12_I NV_IMSI_I NV_IMSI_MCC_I NV_IMSI_T_11_12_I NV_IMSI_T_ADDR_NUM_I NV_IMSI_T_MCC_I NV_IMSI_T_S1_I NV_IMSI_T_S2_I NV_LOCK_CODE_I NV_LOCK_CODE_SIZE NV_MAX_HOME_SID_NID NV_MAX_MDN_DIGITS_SIZE NV_MAX_MINS NV_MAX_NUM_OF_ECC_NUMBER NV_MAX_SID_NID NV_MEID_I NV_MEID_SIZ NV_MIN1_I NV_MIN2_I NV_MOB_CAI_REV_I NV_NET_SEL_MODE_PREF_I NV_PCDMACH_I NV_PREF_MODE_I NV_PREF_VOICE_SO_I NV_PROXIMITY_CALIBRATION_DATA_I NV_PROXI_CALIBRATION_DATA_SIZE NV_RF_BC_CONFIG_I NV_ROAM_CNT_I NV_ROAM_PREF_I NV_SCDMACH_I NV_SEC_CODE_I NV_SEC_CODE_SIZE NV_SID_NID_I NV_SMSOPEN_I NV_SMS_GW_CB_USER_PREF_I NV_SMS_SELFREGISTER_I NV_SMS_SELREGISTER_SIZ NV_SPC_CHANGE_ENABLED_I NV_SYS_SW_VER_I NV_SYS_SW_VER_SIZE NV_TOUCH_CALIBRATION_DATA_I NV_TOUCH_CALIBRATION_DATA_SIZE NV_WIFI_ADDR_SIZE NV_WIFI_MAC_ADDR_I Nv23SmsRegisterType NvAutoAnswerType NvBandPref3263Type NvBandPrefType NvBdAddrType NvByte NvCallCntType NvCdmaChType NvDirNumberType NvEmFactoryInfoType NvHomeSidNidType NvImsi1112Type NvImsiAddrNumType NvImsiMccType NvImsiType NvInteger NvIntegerEx NvLockCodeType NvMDNType NvMeidType NvMin1Type NvMin2Type NvPrefVoiceSoType NvProxiCalDataType NvRfBcConfig:%08x NvRfBcConfigType NvSecCodeType NvShort NvSidNidPairType NvSidNidType NvSidType NvSysSwVerType NvSysSwVerType ilength is: NvTouchCalDataType NvWifiAddrType PGSM 900 &Parameter out of range : 0<=sid<=32767 QC_NV_ITEMS QcNvItemIds.java QcNvItemTypes QcNvItemTypes.java QcNvItems instance created. QcNvItems.java RESERVED 2 Received: SID:%d, NID:%d SIZE_OF_BYTE SIZE_OF_INT SIZE_OF_LONG SIZE_OF_NV_EM_LOCKNETWORK SIZE_OF_NV_EM_MANUFACTORYINFOR SIZE_OF_NV_PREF_MODE SIZE_OF_NV_ZTE_SMS SIZE_OF_SHORT SidNidPair TRUE TYPE Unable to Set Auto Answer Unable to Set locknetwork_num Unable to Set smsinfo #Unable to nv_reset_net_selpref_mode Unable to nv_reset_pref_mode Unable to nv_reset_roam_pref &Unable to nv_reset_sms_gw_cb_user_pref /Unable to read Auto Answer Value from NV Memory VLII VOICE_13K VOICE_13K_IS733 VOICE_4GV_NARROW_BAND VOICE_4GV_WIDE_BAND VOICE_EVRC VOICE_IS_96 VOICE_IS_96_A VOICE_WVRC VocodeSetting WCDMA I IMT 2000 WCDMA II PCS 1900 WCDMA III 1700 WCDMA IV 1700 WCDMA IX 1700 WCDMA V 850 WCDMA VI 800 WCDMA VII 2600 WCDMA VIII 900 WLAN EU 2400 WLAN EU 5000 WLAN FRA 2400 WLAN FRA 5000 WLAN JPN 2400 WLAN JPN 5000 WLAN SPN 2400 WLAN SPN 5000 WLAN US 2400 WLAN US 5000 7[Lcom/android/qualcomm/qcnvitems/IQcNvItems$SidNidPair; @[Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvSidNidPairType; [Ljava/lang/Object; [Ljava/lang/String; 8[[Lcom/android/qualcomm/qcnvitems/IQcNvItems$SidNidPair; A[[Lcom/android/qualcomm/qcnvitems/QcNvItemTypes$NvSidNidPairType; accessFlags addPaddingBytes allocate analogHomeSid append array bArray bd_addr bdaddr booleanValue byteBoard byteeminformation byteinfor bytes bytesToHexString bytesmsinfo call getemmanufactoryInfo cby, get_nv_detect_hw_reset: cby, get_nv_diag_debug_control: cby, get_nv_diag_debug_detail: cby, get_nv_err_fatal_options: cby, get_nv_sys_sw_ver: cby, set_nv_detect_hw_reset: cby, set_nv_diag_debug_control: cby, set_nv_diag_debug_detail: cby, set_nv_err_fatal_options: charAt charValue createBufferWithNativeByteOrder createByteBuffer decode dest dirNumber disableAutoAnswer disableAutoAnswer() doNvRead doNvRead() Failed : %s doNvWrite doNvWrite() Failed : %s dsDefaultBaudrate eccList ecc_list : %s emInfo emfactoryinfo eminformation enable enableVLog error : em of read nv133:133 error : em of read nv:22 error : read nv89:89 evrcEnabled exception format gateway getAirCount getAirCount() getAnalogHomeSid getAnalogHomeSid() getAutoAnswer getAutoAnswerRings getAutoAnswerRings() getBand getBoardSerial getBytes getDirNumber getDirectoryNumber getDsDefaultBaudRate getDsDefaultBaudRate() getEccList getEccList() getEcclist getEmailGateway getGpsOnePdeAddress getGpsOnePdeAddress() getGpsOnePdePort getGpsOnePdePort() getHomeOrigVoiceSo getHomePageVoiceSo getHomeSidNid getHomeSidNid() getImsi1112 getImsi1112() getImsiMcc getImsiMcc() getImsiNumber getImsiNumber() getImsiT1112 getImsiT1112() getImsiTAddrNum getImsiTAddrNum() getImsiTMcc getImsiTMcc() getImsiTs1 getImsiTs1() getImsiTs2 getImsiTs2() getInt getLockCode getLockCode() getLong getMin1 getMin1() getMin2 getMin2() getMobCaiRev getMobCaiRev() getMobDirNumber getNid getNvBandPref getNvBandPref3263 getNvDirNumber getNvDirNumber() getNvRfBcConfig getPcdmach getPcdmach() getPrefVoiceSo getPrefVoiceSo() getRings getRoamCount getRoamCount() getRoamOrigVoiceSo getScdmach getScdmach() getSecCode getSecCode() getShort getSid getSidNid getSidNid() getSize getSpcChangeEnabled getSpcChangeEnabled() getTestFlag getZteSmsInfo get_nv_bd_addr get_nv_bd_addr: get_nv_detect_hw_reset get_nv_diag_debug_control get_nv_diag_debug_detail get_nv_err_fatal_options get_nv_proximity_cal_data get_nv_proximity_cal_data: get_nv_sys_sw_ver get_nv_touch_cal_data get_nv_touch_cal_data: get_nv_wifi_mac_addr get_nv_wifi_mac_addr: getemmanufactoryInfo getlocknetworkInfo gpsOnePdeAddress gpsOnePdePort homeOrigVoiceSo homePageVoiceSo homeSidNid ilength imsi1112 imsiMcc imsiT1112 imsiTAddrNum imsiTMcc imsiTS1 imsiTS2 intToIpAddress intsms ipAddr ipAddress ipAddressStringToInt irawdata isAllZero isDigit isEnabled isEvrcEnabled itemId lBand lBandBitMax lLeftMove lMeid length lockCode lock_code:%s locknetworkInfo locknetwork_num locknetworkinfo logString longValue mAutoAnswer mBytes mChannelA mChannelB mCount mDigits mDirNumber mEccList mEmManufactoryInfo mEvrcCapabilityEnabled mHomeOrigVoiceSo mHomePageVoiceSo mImsi mImsi1112 mImsiMcc mLocknetworkInfo mMDN mMeid mMin1 mMin2 mNam mNid mNum mNvBandPref mNvBandPref3263 mNvRfBcConfig mPair mQcRilOemHook mRoamOrigVoiceSo mSid mVal mZteSmsInfo min1 min1Value min2 min2Value minString minToPhString mobCaiRev nam:%02x, NvBandPref:%04x nam:%d, Count:%d "nam:%x, channel_a:%d, channel_b:%d nam:%x, dir_number:%s gnam:%x, evrc_capability_enabled:%s, home_page_voice_so=%d, home_orig_voice_so=%d, roam_orig_voice_so=%d nam:%x, iimsi_mcc:%d nam:%x, imsi:%d nam:%x, imsi_11_12:%d nam:%x, min1[0]:%x, min1[1]:%x nam:%x, num:%d name nativeOrder newInstance nv106prl nv23smsinfo nv478pesn nvBandPref nvBandPref1631 nvBandPref3263 nvItem nvRfBcConfig nv_em_locknetworkInfo_type nv_em_manufactoryInfo_type nv_factory_reset ,nv_factory_reset, Clean the WCDMA releate NV .nv_factory_reset, reset NV_NET_SEL_MODE_PREF_I &nv_factory_reset, reset NV_PREF_MODE_I nv_reset_net_selpref_mode nv_reset_pref_mode Vnv_reset_pref_mode, reset NV_NET_SEL_MODE_PREF_I to CM_NETWORK_SEL_MODE_PREF_AUTOMATIC Bnv_reset_pref_mode, reset NV_PREF_MODE_I to NV_MODE_GSM_WCDMA_ONLY 2nv_reset_pref_mode, reset NV_SMS_GW_CB_USER_PREF_I nv_reset_roam_pref Anv_reset_roam_pref, reset NV_ROAM_PREF_I to 0xff CM_ROAM_PREF_ANY nv_reset_sms_gw_cb_user_pref nv_zteSmsInfo_type order pack param parseByte parseInt parseLong parseMeid parseShort parseUnsignedByte parseUnsignedInt parseUnsignedShort pcdmach phNumber phString phStringToMin1 phStringToMin2 phoneCnt ppString prefVoiceSo pref_mode printStackTrace println proxi_cal_hi $proxi_cal_hi:0x%x, proxi_cal_lo:0x%x proxi_cal_lo putInt putLong putShort radix requestData responseData result retVal retval rings roamOrigVoiceSo roam_pref sBoardSerial sStrToByte sTestFlag scdmach secCode sec_code:%s sendQcRilHookMsg sendQcRilHookMsg1 setAddr setAirCount setAirCount() setAnalogHomeSid setAnalogHomeSid() setAutoAnswer setAutoAnswer() setAutoAnswerRings setAutoAnswerRings() setData setDirNumber setDirectoryNumber setDsDefaultBaudRate setDsDefaultBaudRate() setEccList setEccList() setEmailGateway setEvrcEnabled setGpsOnePdeAddress setGpsOnePdeAddress() setGpsOnePdePort setGpsOnePdePort() setHomeOrigVoiceSo setHomePageVoiceSo setHomeSidNid setHomeSidNid() setImsi1112 setImsi1112() setImsiMcc setImsiMcc() setImsiNumber setImsiNumber() setImsiT1112 setImsiT1112() setImsiTAddrNum setImsiTAddrNum() setImsiTMcc setImsiTMcc() setImsiTs1 setImsiTs1() setImsiTs2 setImsiTs2() setLockCode setLockCode() setMDN setMeid setMin1 setMin1() setMin2 setMin2() setMobCaiRev setMobCaiRev() setMobDirNumber setNid setNvDirNumber setNvDirNumber() setPcdmach setPcdmach() setPesnToCard setPesnToNv23() setPrefVoiceSo setPrefVoiceSo() setRoamCount setRoamCount() setRoamOrigVoiceSo setScdmach setScdmach() setSecCode setSecCode() setSid setSidNid setSidNid() setSpcChangeEnabled setSpcChangeEnabled() setVer setZteSmsInfo set_nv_bd_addr set_nv_bd_addr: set_nv_detect_hw_reset set_nv_diag_debug_control set_nv_diag_debug_detail set_nv_err_fatal_options set_nv_proximity_cal_data set_nv_proximity_cal_data: set_nv_sys_sw_ver set_nv_touch_cal_data set_nv_touch_cal_data: set_nv_wifi_mac_addr set_nv_wifi_mac_addr: setlocknetworkInfo size skipPaddingBytes smsInfo spcChangeEnabled split status strBandName strBands strMeid stresn strpesn strprlver strraw strret strreturn substring sys_sw_ver table temp tempValue this toBinaryString toByteArray toCharArray toDebugString toMACString toString toUnsignedString touch_cal touchdata vLog val=%d value valueOf wifiAddrs wifi_addr wifiaddr wyb!!getZteSmsInfo wyb!!setZteSmsInfo ,yangxiangling ---BoardSerial:%s, TestFlag:%s +yangxiangling NvBandPref3263Type length is 'yangxiangling NvBandPrefType length is yangxiangling, nv_band_pref: #yangxiangling, nv_band_pref_16_31: #yangxiangling, nv_band_pref_32_63: yangxiangling, nv_rf_bc_config: zte em information nv133 zte em information nv22 zte sms info nv89 #zte write locknetwork_num to nv133 zte write smsinfo to nv89 zteSmsInfo ztesmsinfo Kx<< Kx<< Kx<< Kx<<< Kx<< KZK[ KZK\ KiKi KZKZ <--- KiKii KZKZZ ,9M<K y;RK ,<LK uJAK KiKK KiKi KZKZ KZKZ <--i ,<KK ZZZU KiKi KZKZ <[yyx Kx<xy KZL<<<=y KZL<<K=y KZL<<K=y KZ==y W=iiKiiLy KZZZ ,y{\x [-k\ !@xZ %KxxyZ /system/framework/core.odex /system/framework/bouncycastle.odex x{w+ /system/framework/ext.odex /system/framework/framework.odex /system/framework/android.policy.odex /system/framework/services.odex /system/framework/core-junit.odex PKLC p) ` PAMR< q4AFA DA # ' ! !%! #! 14 AQc !!# !# !# !# "!# !# !# !# !#"113 3 !!# !# !# !# %"# # !#"113 # !#"113 C !"!! "!# !# !# !# !#"113 13 "!33 "!# !# !# !# !#"113 !!# !# !# !# !#"213 DNEA
Guest philmein Posted October 13, 2011 Report Posted October 13, 2011 (edited) doing a forum search of qcnvitems makes me think you are on the right path for the unlock may the gods be with you glossywhite search results http://android.modaco.com/index.php?app=core&module=search&do=search&fromMainBar=1 for qcnvitems Edited October 13, 2011 by philmein
Guest tillaz Posted October 13, 2011 Report Posted October 13, 2011 (edited) i think all this has been looked at before... its in the NAND 100% otherwise the unlocked rom dump of the skate would unlock the OMC... my advice would be to look threw the tpt image for the OMC & the tpt image for the zte skate and compare the the differences.... but i think the NAND is heavily encrypted Edited October 13, 2011 by tillaz
Guest x.balli.x Posted October 13, 2011 Report Posted October 13, 2011 can anyone please read the NAM / NV items using QPST and post the line at nv133 , this code might help us get something , #zte write locknetwork_num to nv133
Guest Chris Banks Posted October 13, 2011 Report Posted October 13, 2011 If you guys can post your IMEI numbers and codes please, that's would be great, I need 3 sets. I'm sorry to say, but I very much doubt you would be able to work out an algorithm with just three sets of numbers. It won't be as easy as IMEI*(Some magic number) I would have thought its most likely that the IMEI is first converted into a MD5 hash, and an algorithm works with those values. Has anyone tried requesting the unlock code by saying they are going to be out of the country? Something like saying you want to use a native orange SIM from a different country... I don't know where I heard this idea to be honest, might well be nonsense!
Guest Ritvesh Posted October 13, 2011 Report Posted October 13, 2011 I'm sorry to say, but I very much doubt you would be able to work out an algorithm with just three sets of numbers. It won't be as easy as IMEI*(Some magic number) I would have thought its most likely that the IMEI is first converted into a MD5 hash, and an algorithm works with those values. Has anyone tried requesting the unlock code by saying they are going to be out of the country? Something like saying you want to use a native orange SIM from a different country... I don't know where I heard this idea to be honest, might well be nonsense! Yes, I have tried to do so. I am actually in Mauritius; I have requested an unlock from Orange, but in-vain! They ask me to keep the sim active for three months and request for the code which I will receive after 3 months.. :(
Guest hotrocks72 Posted October 13, 2011 Report Posted October 13, 2011 Found the following gingerbread 2.6.35 source code links for zte skate on their website. I was wondering if it would help unlock the monte carlo. http://support.zte.c...px?type=service
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now