It was a surprise for me too. It was long time ago, but as far as I remember users have reported that the camera did not work when they flashed 470 baseband on M040 / M050 / M070.
It seems like the software writes something to modemst, something that is incompatible between Korean and US versions, probably due format or encryption changes. So as soon as I found out that clearing fixes boot issue, I decided that it was better to remove the dirty fix that was copying some caches or whatever the data really was.
Unfortunately I've deleted that file since then. I really doubt that someone would decrypt it and make use of it.
Here's a link to baseband M070.
Thank you!
I can't imagine what in modem FW could lead camera to failure.
There could be the problems when you flash Main FW from the one device and Modem FW from another This is predicable because there could be differences in Android<->ModemFW API's.
What is ModemST
ModemST1 and ModemST2 are the two partitions that hold Qualcomm EFS - proprietary encrypted data scructure, containing NVRAM and (may be) some other proprietary data.
There is also FSG partition (abbreviated File System Gold) which should contain clear factory image of EFS (backup). However this partition often doesn't used to recreate damaged EFS structures.
Some facts about EFS (mostly called NVRAM because NVRAM is main and only part stored on the EFS):
Please not confuse Qualcomm EFS with other EFS called techs, like Windows EFS, other EFS types in Android phones, like Samsung's one. The only common here is the abbreviated name.
EFS always contains NVRAM, however some customized FW can store NVRAM in other places. E.g. some Samsung Galaxy series store NVRAM in the separate database, located on the standard ext4 partition, mounted to the Android.
EFS always contains only the data, no code there.
EFS is always encrypted, however there could be some very rare customized modem FW's that does NOT encrypt EFS.
I have never heard the one have decrypted EFS. I would like to decrypt but don't know how. Too much labour/time req'd to explore.
EFS encryption is customized in every device and often changes when global FW updates ocure (like Android version change). This could lead to FW incompatibility and disability to flash back to the previous FW. Another limitation of such a downgrades related to the partition shifts. Some partitions could be resized upon FW upgrade so to downgrade you should resize them back. I've noticed C811_M070_baseband.zip has rare 100MB modem partition images, however another images are more 'generic' 64Mb sized. Real data size inside is about 40MB (It's standard FAT32 image).
Some devices use device specific encryption keys (hardware keys), so the ported ModemSTx paritions will not decrypt on the identical device, and this will lead to the modem failure and connectivity absence. It seems Casio didn't used such keys.
In most cases NVRAM stores IMEI(s), MAC's (later referred as I and M to avoid relevancy checks) and other ID's (excluding Android ID). However some custom designs store ID's in other places. It seems Casio use encrypted EFS to store NVRAM but I can't realize why didn't anyone notices IMEI loss after ModemSTx erasure. It seems Casio store ID'd somewhere else. I've no device to explore.
NVRAM store RF calibration variables. NVRAM loss should lead to loss of the calibration settings.
To calibrate device back you should have rare RF calibration equipment also suitable to write setting to the particular device's NVRAM. The only place where this equipment could be found is Casio's original assembly facility.
However, in case of the NVRAM/EFS damage/loss, modem FW will reinitialize NVRAM with default values. Some FW have enough values to fully init NVRAM and bring the 'default' connectivity back. Some (may be) could be reinited by the FSG data. Some will require to write some NVRAM backup that will allow modem FW to start correctly. I never heard some Qualcomm based device have had valuable connectivity loss due to the calibration issues. You can always clone NVRAM from the identical device and it will back the 'normal' connectivity. But no warranties, as usually.
Full NVRAM database / files backup can be made with QPST .
QPST nor Android/apps don't work with NVRAM directly. They work with the ModemFW and ModemFW is the only code which manage NVRAM and EFS itself.
QPST works with the Modem FW via diagnostics COM port using Qualcomm proprietary binary protocol. Android works with ModemFW via the more standard RIL API.
Use QPST-> Software Download -> Backup to be on the safe side. Other QPST related tools can miss some NVRAM parts! Old and outdated RF_NV_ITEM_Manager, able to edit NVRAM directly on the devices often damage NVRAM on the modern devices. Backup procedure will create .qcn file with all the valuable NVRAM contents in the binary UNencrypted form (or XML-encoded binary). You can use QCNView util (QPST bundled) to edit ITEM's and files and export/import ITEM's to the text files. Most ITEM's contain binary values, so you should know what this ITEM can and should hold to fix or change some parameters. There are thousands of ITEMs in the NVRAM. Very complicated to explore and understand all, especially w/o docs.
You can Restore .qcn backup to the another (identical, sometimes similar) device even though ModemST encryption keys may differ, so the whole ModemSTx partitions exchange would be impossible. In most cases you should patch I's/M's before flashing .qcn to the another deivce to obey the I designation rules and warranty conditions. Notr that empty (null) and All-zeros I's are not accepted by most provider's cell's as acceptable, so the connectivity will not be possible unless you flash in some acceptable I's. Interesting fact, most providers in Russia accept 'Chinese' I's like 123456789012345 independently of the fact that millions of devices in the world have this (or similar) I and this I doesn't pass Luna algorithm check, required by the GSM standard.
I changing (not fixing) is a crime only in the UK. Some countries deny I changes with no/small penalties. In most countries (incl Russia) nobody cares which I you have. Furthermore.,nowadays, tracking of the citizens (domestic of intl.) is not I based, to be correct, it is not I-only based. There are much more powerful on-the-fly tracking techs available to the modern agencies. That's why they don't care.
If you're really wanted, you can't escape unless you will simply drop all the phones and CC's and will not get another ones. Also you, most probably, should never contact anyone who you have ever contacted online/offilne before. Trust me. Matrix never sleeps.
In most cases NCK and other lock's data also stored in NVRAM. Data can be plain binary flags/codes or encrypted in some encoded blocks. Deleting the whole block in most cases will lock the device. and you should write some encrypted block with 'unlocked flag inside' to unlock device. Many devices do NOT store NCK data in NVRAM. Once I saw NCK data was stored in the secret part of EFS, but not in the NVRAM itself nor in the standard file system, replicable by the QPST. Separate partitions with proprietary data structures can be used to store locks.
Some particular ModemST images still available with corresponding ModemFW in this post
http://androidforums.com/threads/rom-stock-jelly-bean-4-1-2-m040.803260/page-8#post-6753655
Read description there at first!
Link:
https://app.box.com/s/zuxfb9jupkwka4sq1cmf
You can flash that FW and ModemST, then reboot and make NVRAM backup by QPST to the . qcn file.
The flash back your preferred modem FW (reboot) and try to restore .QCN. This should import settings and avoid you ModemST encryption problems. But this does not warrant you problem solvation.
also, most probably you can find in NVRAM and edit settings related to the LTE channels support and add or remove some preferred there.
Sorry guys, wanna sleep...
There could be another valuable proprietary partitions.
You should always look the way to get full flash of the working device (and way to restore) to be on the safe side. Casio allows to get full flash using QHSUSB_DLOAD 9006 mode (eMMC is mapped to PC as Mass Storage Device, discussed here widely). This mode provided by the SBL so it will not be available in case of partition damage or SBL level loader failure. To restore bricked device use QPST eMMC Tool and Casio C811 loaders published here nu nugiedha:
http://androidforums.com/threads/casio-c811-soft-brick-possible-fix.967172/
You can read instructions and discussion (in Russian) in the 4pda.ru Casio C!-201L topic.
http://4pda.ru/forum/index.php?showtopic=497930&view=findpost&p=50105534
