Many webpages offer information about these 3 files, but there are many contradictions so I got confused.
I'm searching for a gentle guide to understand these 3 files well.
Thx
Ahmad Alghadban said:
Many webpages offer information about these 3 files, but there are many contradictions so I got confused.
I'm searching for a gentle guide to understand these 3 files well.
Thx
Click to expand...
Click to collapse
They aren't 3 files.
EFS refers to a partition on your device that contains radio/modem/nvdata/baseband/IMEI related software.
CERT refers to certificate files required by the EFS partition(signature for IMEI).
QCN is just the file extension that Qualcomm uses for specific EFS, IMEI, baseband related files. I couldn't find an explanation of exactly what the QCN file extension stands for but it certainly stands for "Qualcomm something something", it probably has something to do with Qualcomm network certification (Q= Qualcomm, C= Certificate?Certified? N= Network).
Everything you asked about resides in the EFS partition to make your radio/modem work correctly.
The only time you should ever need to know, understand or use these files is if you want to backup or restore your EFS/IMEI. Other than that, you should never have any need to know anything about or do anything with this part of your device's software. Messing with this part of your software can brick the device if you aren't careful or if you don't use the right files.
Droidriven said:
...
QCN is just the file extension that Qualcomm uses for specific EFS, IMEI, baseband related files. I couldnt find an explanation of exactly what the QCN file extension stands for but it certainly stands for "Qualcomm something something", it probably has something to do with Qualcomm network certification (Q= Qualcomm, C= Certificate?Certified? N= Network).....
Click to expand...
Click to collapse
Found an answer: QCN = Qualcomm Calibration Network
Droidriven said:
They aren't 3 files.
EFS refers to a partition on your device that contains radio/modem/nvdata/baseband/IMEI related software.
CERT refers to certificate files required by the EFS partition(signature for IMEI).
QCN is just the file extension that Qualcomm uses for specific EFS, IMEI, baseband related files. I couldn't find an explanation of exactly what the QCN file extension stands for but it certainly stands for "Qualcomm something something", it probably has something to do with Qualcomm network certification (Q= Qualcomm, C= Certificate?Certified? N= Network).
Everything you asked about resides in the EFS partition to make your radio/modem work correctly.
The only time you should ever need to know, understand or use these files is if you want to backup or restore your EFS/IMEI. Other than that, you should never have any need to know anything about or do anything with this part of your device's software. Messing with this part of your software can brick the device if you aren't careful or if you don't use the right files.
Click to expand...
Click to collapse
Perfect, Thank you
Related
My imei no got lost while restoring backup using cwm..... i looked around the forum and the ".nv_data" method will not do because my efs folder has a file named "essiv" only and nothing else.....
if someone would confirm what files are contained in thier efs folder and mail it to me also i'll be grateful......
I don't think the 'efs folder' of one device can be used with other devices as it contains the device's IMEI number.
Could you elaborate a bit as to what did you do that resulted in the loss of your IMEI number ? It would help others avoid it in future.
Well.... i restored the same backup file couple of times 'coz i was trying to flash a new theme...btw i am on stock indian 2.3.5......
the files in efs folder can be edited using hex editor (read somewhere in the s2 forum...i don't remeber which thread) so the imei no. in that file can be modified...
Hi,
Apologies if this is in the wrong forum location.
I am looking for some help or guidance on decoding a BIN file that has been extracted from a very ropey phone.
Its a BMW X6 Key Fob
http://www.kakatech.com/mini-key-handset-phone-bmw-x6/
http://www.ebay.co.uk/itm/worlds-sm...b-mobile-uk-stock-fast-despatch-/251117679362
I have the full 8MB BIN file. The baseband is MTK6252.
I can see some bits of data, but not much else, its all jibberish (for a better word) I can not find simple data, i.e. the IMEI.
If anybody has seen anything like this, know of any tools etc its much appreciated.
Rgds,
DG
Hi,
MTK usually encrypts the sim data, that's why you can't see it in plaintext.
Former MTK chipsets used wearleveling in combination of FAT.
Cheers
Hey guys,
Does anybody have a qcn back-up file for the MI 4 LTE-CU?
I need it very bad. I flashed wrong modem firmware and now my nvram (12, 13, 16th partition) is corrupted . I have no IMEI, baseband and cellular info.
Hope someone can help me.
Ruud
Try Qualcomm IMEI Writer or QPST tools.
I tried them both but I need a qcn file complete. I do not know how to write a complete qcn file myself.
If I can get a similar qcn file from the same device I can change the IMEI into my own using QPST and a heximal IMEI converter.
rudge79 said:
I tried them both but I need a qcn file complete. I do not know how to write a complete qcn file myself.
If I can get a similar qcn file from the same device I can change the IMEI into my own using QPST and a heximal IMEI converter.
Click to expand...
Click to collapse
dropbox.com/s/nhf0he391kmtrou/mi4.QCN?dl=0[/url]
yingice said:
dropbox.com/s/nhf0he391kmtrou/mi4.QCN?dl=0[/url]
Click to expand...
Click to collapse
Is it the LTE FDD version of MI4? I tried to flash it using QPST but no success so far.
It can not reset NVram it says. Complaining about incompatible model number.
Thanks for your help! I going to examine the file later this week and then give it another try. Probably coming weekend.
Greetings
It works!! Finally I got it. I used XVI32 writer to change the IMEI in the above qcn file. With Qfil I was able to restore the adopted qcn file.
Many thanks for sharing, Yingice!!
Solved!
I want to make a full copy of a MTK6580 smartwatch firmware before make changes on it, but MTK droid tools I used before with other MTK devices can´t detect this... please, I need a starting point on how to do it with this device...
Thanks
A starting point:
SP FlashTool, a scatter file of similar device and cat /proc/parti*
Then change the starting addresses and sizes to match yours.
CXZa said:
A starting point:
SP FlashTool, a scatter file of similar device and cat /proc/parti*
Then change the starting addresses and sizes to match yours.
Click to expand...
Click to collapse
THANKS. I am not sure if I can access to /proc/ folder, from the device or the PC, or if partitions will list all addresses, but I wil try. I have scatter (and firmware ) of the same device (other brand, but same hardware) but I don´t know if same hardware with different firmware could have different partition addresses., so I didn´t use it to save my actual firm.
Thanks again this is a good starting point. :good::good:
Worked, I´ve got the /proc/par* addresses. I will try to do the backup now. THANKS
Hello all, I am trying to unpack man files to add volte support to a device that has all the hardware needed, but it is not enabled in software and I would like to try and change that. From all my research the files I need are all in the baseband and in .mbn file format, but I cannot find out how to unpack them. Any help would be appreciated!
ghidra or IDA
I'm more conversant with Qualcomm ELF files, hashing, signing and certs.
These seem to have replaced the older MBN.
MBN files are signed. If you mod you'll have to work around this somehow.
See: https://github.com/openpst/libopenpst/blob/master/include/qualcomm/mbn.h
https://github.com/jnaulet/dloadtool/blob/master/mbn.h
Renate said:
I'm more conversant with Qualcomm ELF files, hashing, signing and certs.
These seem to have replaced the older MBN.
MBN files are signed. If you mod you'll have to work around this somehow.
See: https://github.com/openpst/libopenpst/blob/master/include/qualcomm/mbn.h
https://github.com/jnaulet/dloadtool/blob/master/mbn.h
Click to expand...
Click to collapse
I see. This device is quite old and well, to say the least it isn’t an android device either. I’m assuming I would need to find a workaround for this even as it’s running an os that’s nearly a decade old now?
I know that the carrier bundles on this device are signed as well, but people were able to get around that, and this chip was supposedly made with the hexagon DSP and Qualcomm has documentation on how to program for this specific chip/version
aIecxs said:
ghidra or IDA
Click to expand...
Click to collapse
Unfortunately these don't appear to work, or im using them incorrectly
well, maybe you're not an reverse engineer
aIecxs said:
well, maybe you're not an reverse engineer
Click to expand...
Click to collapse
Maybe it’s my first time even hearing of either of those programs and can’t even get one of them to launch without insta crashing, and the other spitting out an error whenever I try to unpack the files.
no problem. just 10 year studying stuff and try again
https://github.com/lololosys/awesome-baseband-research
Hi,
I've probably managed to reverse engineer the MBN. I was able to create my own MBN and load it back.
If anyone wants to get an information, send me a message
RockL79 said:
Unfortunately these don't appear to work, or im using them incorrectly
Click to expand...
Click to collapse
rename it to *.zip
Vortuks said:
Hi,
I've probably managed to reverse engineer the MBN. I was able to create my own MBN and load it back.
If anyone wants to get an information, send me a message
Click to expand...
Click to collapse
they are only ELF files packed in an image, aren't they?
yeah ELF files, with 3 segments. I'm not sure about my knowledge about ELF vs MBN, but I've managed & have a program to extract $ repackage back. I've tested it on Pixel 2 XL and it's working (added support for my country).
WoKoschekk said:
rename it to *.zip
Click to expand...
Click to collapse
unfortunately that didnt work for me either. It could be that the device im trying to work on is quite old and maybe something else has changed since then