Firmware matching

Printable View

05-29-2009
narqval

Firmware matching

Greetings to all,
I have registered yesterday, and thanks to the information on this site/community, successfully removed the sim-lock on my K610i cell phone. But, now I have a question, maybe an answer too, just need confirmation or correction on some, and a few answers.

First this is the log (SETool2Lite) of my cellphone:

Code:

ChipID:9900,EMP protocol:0301 PHONE IS RED RETAIL PRODUCT FLASH CID detected:52 Speed:921600 Flash ID check:2019 Flash props sent ok OTP LOCKED:1 CID:51 PAF:1 IMEI:35381301964876 CERT:RED FLASH CID:52 COLOR:RED Model:K610i MAPP CXC article: R1GB001 prgCXC1250374_GENERIC_TH MAPP CXC version: R1GB001 Language Package:T_MOB_INT_B CDA article: CDA102497/12 CDA version: R13A Default article: cxc1250376 Default version: R1GB001 Network LOCKED Operator: 219-01

1. Suppose I want to put on some other firmware or convert it to W660. If I understood correctly, only things that have to match is the platform (DB2020), FLASH CID(52), and Language Package (T_MOB_INT_B), identified by CDA article (CDA102497/12). The version (R1GB001) can be any. Also, it would be possible to change the language by patching the cell with the FSfirmware+cust.pack combo, EU_5 for example.
Am I right about this somebody please confirm/correct.

2. On that logic, if I was to mod my cell to W660 I would have to find w660main, w660FS, w660custom, all matching the above mentioned values. After flashing with the 3 firmwares, next thing would be to generate quick access patch and then patch the lock, and bugfixes (camera drv, light etc).

3. Im noticing that it still says that my cellphone is locked, regardless of the fact that it actually isnt. Is that normal?

4. Whats the difference between K610 and K610i, i patched my K610i main with the K610 one. Havent noticed any difference but suspect i would lose 3G connectivity? Or is it the same cellphone, but everyone is dropping the 'i'?

Regards,
Narqval
05-29-2009
trimesh

Re: Firmware matching

1) Correct - although certain languages require specific main firmware, too - you can get away with mixing things up quite a bit, but it's safest to keep everything matched.

2) Yes - if you are changing the model, then you should reflash everything, and any patches will need to be reapplied.

3) This is normal - the SIM lock state is being read from the security zone, and that is still locked - but the patch means that it's ignored.

4) The "K610" is the basic model number - the "i" suffix indicates that it's the "international" variant - there is also a "K601im" that has i-Mode support. Some other phones have "c" (China) and/or "a" (America) variants. If something (like a firmware) is marked simply as "K610" it means that it's applicable to all variants.
05-29-2009
narqval

Re: Firmware matching

So bottom line, I am not in any way limited by the

Code:

MAPP CXC article: R1GB001

thingy? And from that fact, any version of W660 firmware would work as long as you have all 3 packs matching (main,fs,cust.), the only thing that has to match with the original firmware is platform (DB2020) and CID(52).

Oh and one more question, what is GDFS in relation to main-firmware,fs-firmware and custom-pack? Does it contain one/all of them or does one of those 3 contain GDFS, or is GDFS a separate entity?

Also how does one extract fs-firmware. For example I have a FS-firmware which is not listed on this site's download page. Suppose I want to extract it and share it here, can I do that myself or are those obtained in some other way?
05-29-2009
trimesh

Re: Firmware matching

OK, that string ("R1GB001") is just the current firmware version - you can flash any version you like into the phone. The main and FS versions should match (although you can often get away with it if they don't), but the cust pack is not tied to any specific firmware version.

Normally you need to make sure the model matches - the platform (like DB2020) is not specific enough to be sure that it will work - two phones could have the same platform but different radios / UI / display / camera / flash size / etc. - and in some cases (most notably when flashing firmware designed for a phone with a larger flash chip into a phone with a smaller flash) you can overwrite something critical (such as the GDFS) and brick your phone.

The GDFS is separate from the main firmware and the filesystem - and it contains quite a lot of data that is phone specific (such as the calibration settings for the hardware, IMEI, simlock state) - some of the fields are encrypted and/or signed, so changing them is not trivial.

There is another area of the flash called the "EROM" - this is generally only updated by the SE service tools when changing the CID - it's actually the bit of code you are talking to when you connect the USB cable with the "C" button held down.

You can read the flash out using various service tools - but when you do this it lacks the digital signatures that the original flashes have, so it's not that useful, since the standard flashing tools won't accept it.
05-29-2009
narqval

Re: Firmware matching

Ok got it, so those firmwares in the download area are obtained in some other way then.

I also presume that I should NEVER run the SE firmware update (neither PC via cable/or live from cellphone) because that would make my CID go higher = screwed.

Finally, is there a way to mod the alarm clock behavior. I really hate it going from mute to full-loud, and not being able to customize snooze interval.

I guess this concludes my questions for this thread, still a lot of stuff I want to know but those I have to research more before asking any more questions, oh and thanx alot trimesh, you gave me the exact information I wanted :)
06-04-2009
ahsai

Re: Firmware matching

nargval

Since u have successfully unlocked your K610i, can you walk me through it. I have done some reading on this forum as well as other but a bit confused.

FYI my K610i software setting says as per below.

R1CD001
prgCXC1250539_H
UTCHISON_TH
R1CD001

EROM:R3A011
prgCXC1250487_ER
OM_DB2020_THEL
MA_FOTA_SIMLOC
K_FLAFLA_SIBLEY_
SEMCUSB

I haven't started yet just I need some clarification before I go. I need to patch my phone using setool2 lite v1.11 and this patch is generated from the main firmware R1CD001, right ?

So this R1CD001 I need to find the firmware or can use R1GB001 ?

Can you give me a list of the files you need and where to download ?

Thanx
06-05-2009
narqval

Re: Firmware matching

Quote:

I haven't started yet just I need some clarification before I go. I need to patch my phone using setool2 lite v1.11 and this patch is generated from the main firmware R1CD001, right ?

So this R1CD001 I need to find the firmware or can use R1GB001 ?

Can you give me a list of the files you need and where to download ?

First, you need to know your CID number (erom cid, flash cid, NOT the OTP cid). If it is 52 or lower you can patch it, if it's greater than 52 it may be doable but I don't know how and certainly not by this method.
Second, yes you need the original R1CD001 for patching, and since there isn't one for download you can't patch it the same way I did.
But I presume that you could replace the firmware with some other, R1GB001 for example, and then patch the new firmware.

Ok, now lets presume that your cid is lesser than 52. The patching process would go like this:

1.) Follow the tutorial here and replace the firmware with some other.

2.) After that you can do the paching the same way I did, following this tutorial. Side note: your platform is DB2020 so make sure to read the correct part of the tutorial.

Main points to consider:

- Always make a GDFS backup (one before 1., and one before 2.)
- The battery has to be 100% full to make sure the cellphone doesnt turn off during flashing. Also check the quality of the cable connection, you dont want to lose contact during flashing.
- When you flash, you must flash both the MAIN and FS firmwares, the version of those must be the same (R1GB001 or some other, as long as its the same its ok).
- Also you have to "finalize" by patching the customizations pack, this has to match the FS firmware language (T_MOB_INT_A for example) so choose FS/custom carefully to match your language.
- If you dont know which firmware to choose, I would go with one that has the most FS/customs available for download if you want to cycle them later without having to flash MAIN and patch it up over again.

- After patching all 3 of the above (1st tutorial), your phone will still be locked, but it will be branded/debranded depending on the FS firmware you have chosen. Turn it on after completing the 1st tutorial to see if everything is ok.
- To unlock it, you can follow the guide mentioned under 2nd tutorial.

Hope this helps and good luck with the patching.

Regards,
Narqval

P.S. Although I strongly believe this method will work, it couldn't hurt to verify this with some of the experienced forum members, since i'm still new and inexperienced when it comes to this and had never tested the 1st part myself.
06-07-2009
ahsai

Re: Firmware matching

Hahaha. Thanx man.

I am also inexperience but since you successfully unlock your k610i, you did clarify a few items stuck in my head for a few days. If I have any trouble I hope I can get your advice later.

Btw, I am blur about your statement "- Also you have to "finalize" by patching the customizations pack, this has to match the FS firmware language (T_MOB_INT_A for example) so choose FS/custom carefully to match your language." ???

I thought I needed a Main and FS firmware only but here you mention something about customization pack which is new to me. What is this and is this a 3rd part of software that I need to flash at the same time after doing Main and FS ?
06-07-2009
riders4sia

Re: Firmware matching

Quote:

Originally Posted by ahsai

Hahaha. Thanx man.

I am also inexperience but since you successfully unlock your k610i, you did clarify a few items stuck in my head for a few days. If I have any trouble I hope I can get your advice later.

Btw, I am blur about your statement "- Also you have to "finalize" by patching the customizations pack, this has to match the FS firmware language (T_MOB_INT_A for example) so choose FS/custom carefully to match your language." ???

I thought I needed a Main and FS firmware only but here you mention something about customization pack which is new to me. What is this and is this a 3rd part of software that I need to flash at the same time after doing Main and FS ?

you need to flash custpack "finalise", if you don't, you will have configuration error on your phone
06-07-2009
narqval

Re: Firmware matching

Quote:

Btw, I am blur about your statement "- Also you have to "finalize" by patching the customizations pack, this has to match the FS firmware language (T_MOB_INT_A for example) so choose FS/custom carefully to match your language." ???

I thought I needed a Main and FS firmware only but here you mention something about customization pack which is new to me. What is this and is this a 3rd part of software that I need to flash at the same time after doing Main and FS ?

Yes it's actually the 3rd part, but it's not really software itself, just some images, configuration files etc but you need that to make it all work because if you don't flash customs pack or flash it with the wrong one you will get "configuration error" like riders4sia already said.

Anyway, the point I wanted to make is that your phone languages will depend on which FS firmware you flashed your phone with. There was a list of FS matched up with languages somewhere but I can't find it anymore. You can also add/remove languages later on somehow but I haven't studied that because I'm satisfied with what I got.
So, 1.main 2.FS 3.customs 4.patch up and voila :)

BTW, did you find out your CID number?
06-10-2009
ahsai

Re: Firmware matching

Thanx for the advice. I would be doing it this weekend when I am free.

Anyway, I plan to use K610_R1JG001_MAIN_HONG_KONG_TH_RED52 , K610_R1JG001_FS_HONG_KONG_RED52 and K610i_CDA102497_102_R5A_Maxis_Malaysia. What do you think ?

I have not found my CID yet but I thought whatever it was the case I still need to reflash to CID 52 cause my K610i is locked to 3 network in the UK. FYI, my bro gave this K610i to me so I need to reflash it so that Chinese language can be supported besides English as native. Hence thats why I choose Hong Kong for Main and FS.
06-10-2009
narqval

Re: Firmware matching

it won't work with that Custom pack. You need the same one as the FS, so
HB1-06_Gen_CDA102568_104_R5A_GENERIC_HONG_KONG would be the choice.

Also, your phone MUST be CID52, and RED. You can check that simply by plugging it in to XS++, or choosing IDENTIFY with setool2lite.
If its lower than 52, you can upgrade to 52 with XS++ (it will automatically ask to upgrade).
If its 53, then you cant flash with XS++/setool2lite and you cant downgrade as far as i know.
06-10-2009
Jona

Re: Firmware matching

So you got all these different packs, but is there also a way to add single items for example to expand the dictionary maybe create your own on the computer and convert it to a format that the phone understands and then upload it?
06-11-2009
ahsai

Re: Firmware matching

OK, I finally confirm that my k610i is CID49. I make a GDFS backup as describe in the tutorial in this forum. Success and I keep the *.bin file in a folder.

Then I try to flash my phone to CID52.......unsuccessful. It said something about error 19 something like that. I was using "Main" and "FS" file both as Hong_Kong while customization pack was K610i_CDA102497_102_R5A_Maxis_Malaysia. I don't know what I did wrong. Any advice ? :(

Sorry I miss out on your post earlier on. I will try to download the customization file you recommended. However, since my phone is CID49, can I still upgrade/flash to CID 52 using setool lite ? From your post you are recommending me to use XS++ to upgrade. Can't setool lite do the upgrading ?

Thanx
06-11-2009
narqval

Re: Firmware matching

You can't flash your phone to CID52 by applying CID52 firmware. CID52 is prerequisite to CID52 firmware, and is independent of it.
You must first upgrade to CID52, and then flash the firmware. You can't do it with SETool2Lite, but must use XS++.
It is as simple as running XS++, and when asked to upgrade to CID52, clicking YES, no extra files required or anything.
After you do that, you can do the flashing with SETool2Lite as described in tutorial.
06-13-2009
ahsai

Re: Firmware matching

narqval

I finally manages to complete everything. You are right, I have to use XS++ to upgrade from CID 49 to CID 52. As long as I follow all the procedure it became apparent that all this tutorial and advice was on the right track.

However I got the scare of my life when after I did everything (upgrade, flashing and then unlocking by patch) and after testing it ok......the 2nd time when I turn on the hp, it went dead. Totally black.....with red light blinking 5 times (EROM dead).

I panic. I went googling etc.......was supposed to be easy to recover but then setool, xs++ both could not even recognise the hp. No communication port.....nothing. After doing some analysis and try and error, I suspected something to do with the driver. So I uninstall the usb driver and reinstall it again and did a few tries. At last setool manages to read my hp. So after following instruction and press repair.....EROM was ok back. Had been using it for 2 days now. Seem ok. Touch wood :)

Thanx for the advice and support.

Next project would be my dad's k750i which he got cheated by the authorised SE people. Send in for repair and yet those unscrupulous SE technician mess it all up and charge him exhorbitantly. You have this phone ?
06-16-2009
czubek

Re: Firmware matching

I would like to debrand an ATT W760a. I found the main & fs ok but the only custpak I found is W760a_1212-6828_R10A_ATT_USA. I fear this is not a match for the generic america main & fs. If wrong custpak is there another way to accomplish?
06-16-2009
docmagoo2

Re: Firmware matching

think you can use pretty much any generic cust pack....
06-16-2009
czubek

Re: Firmware matching

I remain skeptical. previous posts in this thread indicated the custpak file had to match the fs file. I havn't seen much of any match.
06-19-2009
narqval

Re: Firmware matching

Quote:

...Had been using it for 2 days now. Seem ok. Touch wood :)

Congratz, you scared me there for a moment :)

Quote:

Next project would be my dad's k750i which he got cheated by the authorised SE people. Send in for repair and yet those unscrupulous SE technician mess it all up and charge him exhorbitantly. You have this phone ?

k750i is DB2010 so you should read the same guide as for K610i, but the DB2010 part, never done it myself, but the guide is proven to be good i think.
06-19-2009
narqval

Re: Firmware matching

Quote:

Originally Posted by czubek

I would like to debrand an ATT W760a. I found the main & fs ok but the only custpak I found is W760a_1212-6828_R10A_ATT_USA. I fear this is not a match for the generic america main & fs. If wrong custpak is there another way to accomplish?

I dont know about W760a, I have only seen W760i on the download list.

Generally, the thing to match is the FS and MAIN firmware version (R1GB001 for example) and FS and custpack version (only the language string, T_COM_INT_A for example). Although, I have been told that some other combinations are possible. From what I've learned, this kind of matching is sure to work, for more info and explanation, read the thread from the beginning. After all, I have started it with almost the same question :)