The best thing is to make both (QA & removeSIMlock) with MAIN (.mbn used for flashing)
The best thing is to make both (QA & removeSIMlock) with MAIN (.mbn used for flashing)
Can I get a lil help on how to restore the GDFS file generated from Setool2? I kinda want the phone to go back to where it was before when i first got it... wanna just unlock it without touching the mainfirmware and so on, thanks guys, i cant find a guide on that =(
Restore the GDFS: select the phone type, press the ...(three dots) button next to Misc files box, select the GDFS backup and press the Write GDFS button.
Then reflash the MAIN firmware, and follow the unlocking guide step by step(DO NOT skip any step).
Something bad happend. I followed your "restore the GDFS" procedure, and when its writing the GDFS back (I quadruple checked and its the right file for the phone), it says "Failed, this is fatal" message at the end... So i guess it didnt write through with the GDFS. So right now Im gonna reflash the main, FS and custom file with XS++ then reunlock the phone with "Remove Sim lock" tutorial and see if all these will revive the phone...
Am i doing something wrong here? why won't the phone be recovered with the original GDFS file created by Setool2?
T__________T
thanks for all the help, may need a lil more T________T
Heres the log:
Welcome to SEtool2 ( LITE edition ) v 1.11
supported DB2010/DB2012 CID49/50/51/52, DB2020 CID49/51/52
Loaded 51 flash descriptors
ChipID:9900,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:52
Speed:921600
OTP LOCKED:1 CID:51 PAF:1 IMEI:XXXXXXXXXXXX CERT:RED
FLASH CID:52 COLOR:RED
LDR:061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
Flash ID check:897E
Flash props sent ok
CSloader version:
070410 1557 HANCXC1250562_DB2020_CSLOADER_R3A009
loader startup: executed
CSloader refused to start GDFS services,error is:29
failed, that is fatal
Elapsed:35 secs.
Above is what happened when i tried write the correct GDFS file
ChipID:9900,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:52
Speed:921600
OTP LOCKED:1 CID:51 PAF:1 IMEI:XXXXXXX CERT:RED
FLASH CID:52 COLOR:RED
LDR:061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
Flash ID check:897E
Flash props sent ok
CID52 BYPASS PROCEDURE STARTED
Processing part1...
CSloader version:
070410 1557 HANCXC1250562_DB2020_CSLOADER_R3A009
Processing part2...
Processing part3....
OTP LOCKED:1 CID:51 PAF:1 IMEI:XXXXXXXXX CERT:RED
FLASH CID:52 COLOR:RED
LDR:061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
Flash ID check:897E
Flash props sent ok
verify block error
last blk:45460000,00010000
CID52 BYPASS PROCEDURE FINISHED
Above is what happened when i tried the "Remove Sim Lock“ procedure after writing GDFS failed...Weird thing happened, it didnt ask me to click yes to remove patch or no to apply it...So i guess theres something wrong.
Simox or Jasmin or Sea if you guys need any of my log, let me know =/
Last edited by yayo830; 11-25-2008 at 01:56 AM.
Only QA patch goes thrue Bypass DB2020, all other patches goes thrue quick access in Setool2lite (unmark bypass and mark quick access) if you install QA patch
Is your phone working right now? If yes, then follow carefully the whole unlocking procedure step by step. If the phone isn't works, then reflash the MAIN firmware, and then try to restore the GDFS.
Ok, so for reflashing the Main Firmware, first click quick access, then "add" the main firmware, then click on flash? or should I do that with XS++? or how do i reflash the main firmware?
NO, you just add main and flash,without quick access
Ok thanks Sea, will do so, cross my finger
flash main report:
ChipID:9900,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:52
Speed:921600
OTP LOCKED:1 CID:51 PAF:1 IMEI:XXXXXXXXXXXX CERT:RED
FLASH CID:52 COLOR:RED
LDR:061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
Flash ID check:897E
Flash props sent ok
writing C:\Documents and Settings\Admin\Desktop\W580_R8BE001_MAIN_TAIWAN_LA _RED52\W580_R8BE001_MAIN_TAIWAN_LA_RED52.mbn
CURRENT FLASH FILE CID:52
SSW uses complete hash, hash len is:9200
Will flash 460 blocks...
SSW loading returns:0
Elapsed:271 secs.
Unlocking report:
2 things happened: First, it happened again, its asking me some block value differs, do I wish to continue, if i click yes, and apparently they will overwrite the block value. That will just make my phone not able to turn on. If i skip that by clicking "no", it will skip the block value writing part. But the problem is that I won't be able to do the final part of the Remove Sim Lock procedure. The Remove_Sim_lockXXXXX.vkp simply wont work, like the following:
Going to execute VKP script....
ChipID:9900,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:52
Speed:921600
Trying to launch embedded bootloader...
Abort all operations.
embedded flashloader not responds !
Elapsed:26 secs.
Also, the Phone's GDFS recover runs smoothly this time, i guess i should be a lil happy bout it, thanks guys =)
Last edited by yayo830; 11-26-2008 at 04:01 AM.
Here is what I have done with Identify with SEtool2:
ChipID:9900,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:52
Speed:921600
Flash ID check:897E
Flash props sent ok
OTP LOCKED:1 CID:51 PAF:1 IMEI:XXXXXXXXXXXX CERT:RED
FLASH CID:52 COLOR:RED
Model:W580i
Brand:Generic
MAPP CXC article: R8BE001 prgCXC1123478_TAIWAN_LA
MAPP CXC version: R8BE001
Language Package:ROGERS
CDA article: CDA102774/167
CDA version: R4A
Default article: cxc1123364
Default version: R8BE001
Network LOCKED
Operator: 302-72
Elapsed:17 secs.
Currently im using mainfirmware: W580_R8BE001_MAIN_TAIWAN_LA_RED52
File System: W580_R8BE001_FS_TAIWAN_RED52
custom files from XS++: W550 Apac
At the very beginning, after i did the Remove_sim lock procedure (didnt turn on to check if it works, still got that "block value differ" thing came up), i used XS++ and flashed the main, FS and custom.
So am i using the correct mainfirmware? I believe I am but why it kept on poping out with that "block value differs, do you wish to continue" whenever i try to quick_access the vkp of it?
There are currently 1 users browsing this thread. (0 members and 1 guests)