Develop Bugs

[SOLVED] Sales Code changed after flashing JPC

Hey out there,
after flashing my german SGS back from JPC to JM7 i had a look at the cusomer.xml file in /system/csc/.
There are two lines that now show KOREAN:
1. <SalesCode>KOR</SalesCode>
2. <Country>Korea</Country>
Before I did the following from the Guide JM7 by Richthofen:
Open Root Explorer and go to the "EFS" folder in the root.
Check the date on .nv_data.bak and .nv_data.bak.md5 files.
If it is earlier than 08/26/2010 you´re clear, if it is later then you may stop reading.
Once the date has been checked, select files nv_data.bin and nv_data.bin.md5 simultaneously and delete (yes, delete) them. Reboot the phone.
Now your phone is in the same condition (atleast permanent memory wise) as it was prior I9000XXJPC update.
Click to expand...
Click to collapse
So normaly my SalesCode should be DBT, so do i have to change it? But i dont know what should be in Country.. i havent written it down. So can someone with a german (o2) phone, with no JPC tell me what shlod be in line 5 <Country>Korea</Country>?
Thx in advance!

i *think* that simply flashing with a german CSC should remedy that.

dont edit the nv_data.bin! if you still have your old .bak files (from before the JPC flash) then just delete the normal.bin and .md5 and the phone will create new files out of the backups. in any case: save the backups to some place safe in case you need them!
just flashing the CSC will not help, because the efs data is not touched by any firmeware (besides JPC)
you can also try flashing back to an older firmware like JM 1 with Odin 1.3 and EFS clear, some people from Android-Hilfe.de reported this repaired the efs for them.
In any case, always back up the efs files!

My /system/csc is fine after using the *#272*hhmm* thing and selected my product code and clicked install.

Asdain said:
dont edit the nv_data.bin! if you still have your old .bak files (from before the JPC flash) then just delete the normal.bin and .md5 and the phone will create new files out of the backups. in any case: save the backups to some place safe in case you need them!
just flashing the CSC will not help, because the efs data is not touched by any firmeware (besides JPC)
you can also try flashing back to an older firmware like JM 1 with Odin 1.3 and EFS clear, some people from Android-Hilfe.de reported this repaired the efs for them.
In any case, always back up the efs files!
Click to expand...
Click to collapse
Will it nuke all records for the EFS and fix it back to the correct product code and IMEI ?
It really puzzles me why such things are not hard coded into the phone it self.

dutchcow said:
My /system/csc is fine after using the *#272*hhmm* thing and selected my product code and clicked install.
Click to expand...
Click to collapse
thanks, this made me restore my product code!
only a couple of clarifications..
- it's *#272*HHMM#
- this makes a factory reset to the phone, deleting all apps and setting, be sure to backup all that stuff before!

Donald Nice said:
So normaly my SalesCode should be DBT, so do i have to change it? But i dont know what should be in Country.. i havent written it down. So can someone with a german (o2) phone, with no JPC tell me what shlod be in line 5 <Country>Korea</Country>?
Click to expand...
Click to collapse
You must follow the point 7 of the first post from this thread:
http://forum.xda-developers.com/showthread.php?t=769400
7. My Phone asks me for a Unlock Code. Product Code has changed to KOR. What to do?
- Your Phone have to be rooted! Busybox is required!
- Start->Run-> cmd
- Change to your SDK\tools Directory e.g cd C:\Program Files (x86)\Android SDK\tools
- adb shell
- su
- cd /efs
- ls -al
If now nv_data.bak AND nv_data.bak.md5 are displayed, do the next few steps marked with (a)
If now .nv_data.bak AND .nv_data.bak.md5 are displayed (dot before filenames), do the next few steps marked with (b).
(a)- mv nv_data.bin nv_data.jpc
(a)- mv nv_data.bin.md5 nv_data.jpc.md5
(a)- mv nv_data.bak nv_data.bin
(a)- mv nv_data.bak.md5 nv_data.bin.md5
(a)- reboot
(b)- mv nv_data.bin nv_data.jpc
(b)- mv nv_data.bin.md5 nv_data.jpc.md5
(b)- mv .nv_data.bak nv_data.bin
(b)- mv .nv_data.bak.md5 nv_data.bin.md5
(b)- reboot
Click to expand...
Click to collapse
The right codes are saved in your device as .bak (backup)
First, you must find out if your needed files contains an . or not before the name. Now you must use way (a) or (b)
- On the first two lines, you make a backup from the (wrong Korean) JPC codes (if something goes wrong )
- Line 3 and 4 overwrites these code with your original backup codes.
- Reboot - reboots you device and the stock countrycode should be restored.
As I understand, these files are digitaly signed, so you shouldn't change something on it to keep the signature.
I've made these steps from JPC to JM2 with an non branded german device with success.
Ah, i forgot something. In this howto it was explained you should use
- ls -al
Click to expand...
Click to collapse
to show you all (even hidden) files in folder /efs.
It should be
ls -a
Click to expand...
Click to collapse

eltommi said:
thanks, this made me restore my product code!
only a couple of clarifications..
- it's *#272*HHMM#
- this makes a factory reset to the phone, deleting all apps and setting, be sure to backup all that stuff before!
Click to expand...
Click to collapse
When I try to do this I get something like an error message "Rejected". And I can't see anything in this EFS folder. There are no files inside it. What to do?

eltommi said:
thanks, this made me restore my product code!
only a couple of clarifications..
- it's *#272*HHMM#
- this makes a factory reset to the phone, deleting all apps and setting, be sure to backup all that stuff before!
Click to expand...
Click to collapse
Thats it! Tahnk you so much!!!!

Donald Nice said:
Thats it! Tahnk you so much!!!!
Click to expand...
Click to collapse
Sorry to disappoint you but as soon as you flash again your product code and sales code will revert to KOR. You really need to fix it in the EFS folder (carefully!!). First thing is to backup somewhere the files .nv_data.bak and .nv_data.md5.bak to be safe.

dnsp said:
Sorry to disappoint you but as soon as you flash again your product code will revert to KOR. You really need to fix it in the EFS folder (carefully!!). First thing is to backup somewhere the files .nv_data.bak and .nv_data.md5.bak to be safe.
Click to expand...
Click to collapse
Yes i know... and i have done this! But thank you for your advice!

Thanks! Thank you so much!!!
I have got my original product code back!
I used JM2, work.
Thanks again.

dnsp said:
Sorry to disappoint you but as soon as you flash again your product code and sales code will revert to KOR. You really need to fix it in the EFS folder (carefully!!). First thing is to backup somewhere the files .nv_data.bak and .nv_data.md5.bak to be safe.
Click to expand...
Click to collapse
I flashed JPC with Kies, then I returned to jm7 followin Richtofen istructions on the first post of jm7 thread..
I checked my .bak..they were dated June..so I deleted nv_data.bin and nv_data.bin.md5 and rebooted recreating new files based on .bak..so I think the stuff on /efs should be ok now..
KOR product code was here until today btw..
so you're telling me that if I flash again it will be back to KOR? despite of the work I made on /efs after flashing jm7?
I'm too lazy to try by myself flashing once more tonight =)
thanks!

eltommi said:
I flashed JPC with Kies, then I returned to jm7 followin Richtofen istructions on the first post of jm7 thread..
I checked my .bak..they were dated June..so I deleted nv_data.bin and nv_data.bin.md5 and rebooted recreating new files based on .bak..so I think the stuff on /efs should be ok now..
KOR product code was here until today btw..
so you're telling me that if I flash again it will be back to KOR? despite of the work I made on /efs after flashing jm7?
I'm too lazy to try by myself flashing once more tonight =)
thanks!
Click to expand...
Click to collapse
You did it right. I was referring to the method below:
eltommi said:
thanks, this made me restore my product code!
only a couple of clarifications..
- it's *#272*HHMM#
- this makes a factory reset to the phone, deleting all apps and setting, be sure to backup all that stuff before!
Click to expand...
Click to collapse
This will give you a non permanent product code. Will go back to KOR again after a re-flash.

dnsp said:
You did it right. I was referring to the other method:
Click to expand...
Click to collapse
I did both of them..some days ago the first one, but KOR was still there..today the second one..uhm..
Ok I'm going to flash again and see what happens =)

scorpio16v said:
You must follow the point 7 of the first post from this thread:
http://forum.xda-developers.com/showthread.php?t=769400
The right codes are saved in your device as .bak (backup)
First, you must find out if your needed files contains an . or not before the name. Now you must use way (a) or (b)
- On the first two lines, you make a backup from the (wrong Korean) JPC codes (if something goes wrong )
- Line 3 and 4 overwrites these code with your original backup codes.
- Reboot - reboots you device and the stock countrycode should be restored.
As I understand, these files are digitaly signed, so you shouldn't change something on it to keep the signature.
I've made these steps from JPC to JM2 with an non branded german device with success.
Ah, i forgot something. In this howto it was explained you should use
to show you all (even hidden) files in folder /efs.
It should be
Click to expand...
Click to collapse
Those are the steps that I did, i got my phone unlocked but the product code and IMEI got messed up.. and I didnt have a back-up of my nv_files... I guess this is be a permanent effect on the phone already .. any chance a service center can restore this ?
EDIT:
Also would anyone know if I flashed to the JM1 firmware like what was said a few posts back and if it messes up the efs folder would it prevent my phone from booting ? I already made a copy of my efs folder using root explorer..

ummm
I try te JPC and then i flash the phone about 3 times.........so at the moment in my efs folder there arent the .bak files.
No way to restore the orginal product code for me?

problem with nv_data.bin.md5

Hi everybody!
Yesterday I installaed the new build JPC and before this I taken a backup of nv_data.bin and nv_data.bin.md5 but this morning I've deleted my MD5 file.......
I've try to calculate another MD5 checksum but this is different. I made md5 from JPC's nv_data.bin and this is different than hash inside of nv_data.bin.md5
Do anyone know generate a correct hash?
I used MD5sum.exe in Windows and md5sum of busybox.
Thanks

dont u have a backup file .nv_data.bak.md5 in /efs?

Mikulec said:
dont u have a backup file .nv_data.bak.md5 in /efs?
Click to expand...
Click to collapse
No. Because I already run two flash
Sent from my GT-I9000 using XDA App

anyone have idea?

Nothing?
It's impossible that no one know to made this md5...
Sent from my GT-I9000 using XDA App

I've tried many many times but without good result..........probably there is a "salt" in .md5, not only generated on the file.

tokinux said:
I've tried many many times but without good result..........probably there is a "salt" in .md5, not only generated on the file.
Click to expand...
Click to collapse
I tried much way but nothing...
My problem isn't the IMEI code or Product Code but the code to unlock, infact with Windows application I can see the two code (network and unlock) but with SGS with "SGS Unlock" I can't see these two code...

[Q] Converting raw BIN dump to something useful

Hi All
I've searched and not found much info on this.
I've got a dump of an HTC HD7 using the Riff box (JTAG). The file is a 512MB BIN file.
Basically I would like to be able to see the files inside it. Ideally I would like to see the files/folders/structure inside the dump. I don't know how difficult or easy this is, so forgive me if I'm asking for the impossible. But is there a way of converting the bin file to something like a cab/nbh or even the files/folders so that I can view them in explorer or some similar tool?
At the moment I'm viewing the file in a hex editor trying to carve out certain files. But I figure since the file system and structure is known on Windows Phone 7, there may be a way of converting the entire image to a better support format.
So if anyone can suggest any tools or ways of doing this, it would be much appreciated.
Thanks

How do you use the jtag to get a dump of it? I don't know if you can use htcrie or not (search in this forum for the tool)
Sent from my SGH-i917 using XDA Windows Phone 7 App

snickler said:
How do you use the jtag to get a dump of it? I don't know if you can use htcrie or not (search in this forum for the tool)
Click to expand...
Click to collapse
I use the Riff Box which is supposed to a dump of the ROM/NAND, which it did, into a .bin file.
I've tried htcrie, but it doesn't load the bin file. I've tried looking for a tool that converts the .bin to a nbh, but found nothing so far

puunda said:
I use the Riff Box which is supposed to a dump of the ROM/NAND, which it did, into a .bin file.
I've tried htcrie, but it doesn't load the bin file. I've tried looking for a tool that converts the .bin to a nbh, but found nothing so far
Click to expand...
Click to collapse
Where do you get a riff box from? I want to dump my rom. I would look into the Windows Mobile threads and see if there is a tutorial OR pm ansar or xboxmod and see if they can help out. If possible can you provide how to obtain an use the riff box?
Sent from my SGH-i917 using XDA Windows Phone 7 App

nbh or nb it's for bootloader to write to nand, so it will have diff format with nand dump.

ted973 said:
nbh or nb it's for bootloader to write to nand, so it will have diff format with nand dump.
Click to expand...
Click to collapse
I'm not sure. I took a complete dump of the HD7 and it gave me a 512MB file in a .bin format. I believe that includes the bootloader and everything else, but I could be wrong.
I don't mind what kind of file it gets converted to, as long as I can view the files inside. Thanks

puunda said:
I'm not sure. I took a complete dump of the HD7 and it gave me a 512MB file in a .bin format. I believe that includes the bootloader and everything else, but I could be wrong.
I don't mind what kind of file it gets converted to, as long as I can view the files inside. Thanks
Click to expand...
Click to collapse
Try this thread http://forum.xda-developers.com/showthread.php?t=1260757 . There's something on there that speaks about WP7 Binary tools.

snickler said:
Try this thread http://forum.xda-developers.com/showthread.php?t=1260757 . There's something on there that speaks about WP7 Binary tools.
Click to expand...
Click to collapse
I've looked on that thread and have downloaded the tools. I've also messaged the author of the tool, but not got a reply yet. It looks like the tools which does work on the raw dump/bin files are for the logo and bootloader, not the entire image.
I'm still working on it, but there seems to be a lot of info that I need to sort though.

You may use Qualcomm tool from riff plugin. It's view all partitions

Missed this one.
No questions in the development section please!
Thread Closed

[Q] Product code: "Not active" / Kies won't update / N7100

Hi,
My problem is Kies won't update my phone - GT-N7100 (a well known message that the device is not supported, with triple (xxx) in place of the CSC code at the end of this message). Also when I use Check Fus on my phone, in the Product Code field it says "Not active" like below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And this is what Kies says:
I think the lack of Product Code might be the reason why Kies doesn't update. I don't care about Kies so much but I just want to know what's wrong and try to resolve it.
What I did:
1. I bought the phone unbranded, unlocked, and it came with XEF CSC (FW: XXALJ1).
2. I changed the CSC to XEO with CSC Select (from Google Play) --> Phone wiped.
3. After this I upgraded to the newest XXALJ3 FW.
And then when trying to update with Kies it displays the message as above and Check Fus reports PC Not Active. As far as I know it should display full product code in the PC field so in this case: GT-N7100TADXEF (I don't know if the PC also changes when changing the CSC, in case it changes it should of course display GT-N7100TADXEO). I wiped the phone a few times, went back to the original FW (XXALJ1), changed the CSC back to XEF but no luck.
I've gone through many sites/forums but didn't find the answer. Also I didn't mess with EFS folder, I have my proper IMEI. Is there a possibility that CSC Select app did something wrong to the phone? I don't think so because if I'm right it only triggers Samsung's built-in Preconfig menu, so it should't do any harm. I regret not checking if Kies works properly before changing the CSC.
So the big question is: where the phone reads the PC from (where it's stored?) and how to make the Product Code appear as it should?
EDIT:
I figured out the problem lies within the nv_data.bin file in EFS folder. Inside of this file there's a string "Not active". The same string is present in the backup copy (.nv_data.bak). I tried to edit the file with hex editor and put the right product code in place of "Not Active" string but I can't generate proper md5 hash for it (it seems it's not a regular md5 hash that Samsung uses). And when you delete nv_data.bin.md5 it won't recreate one automatically as it was the case in earlier phones. It will just use the backup file. Even when I deleted .nv_data.bak, .nv_data.bak.md5 and nv_data.bin and nv_data.bin.md5 and uploaded only the modified nv_data.bin with proper product code - it somehow restored the files from somewhere else (I heard there is a hidden partition or something with another backup files) and again I have PC: Not active.
I think the solution would be to somehow create md5 hash of that modified nv_data.bin file that's accepted by the phone but I don't know how.

Great Work
Hi brother im also facing the same problem can you please help me.
tom369 said:
Hi,
My problem is Kies won't update my phone - GT-N7100 (a well known message that the device is not supported, with triple (xxx) in place of the CSC code at the end of this message). Also when I use Check Fus on my phone, in the Product Code field it says "Not active" like below:
And this is what Kies says:
I think the lack of Product Code might be the reason why Kies doesn't update. I don't care about Kies so much but I just want to know what's wrong and try to resolve it.
What I did:
1. I bought the phone unbranded, unlocked, and it came with XEF CSC (FW: XXALJ1).
2. I changed the CSC to XEO with CSC Select (from Google Play) --> Phone wiped.
3. After this I upgraded to the newest XXALJ3 FW.
And then when trying to update with Kies it displays the message as above and Check Fus reports PC Not Active. As far as I know it should display full product code in the PC field so in this case: GT-N7100TADXEF (I don't know if the PC also changes when changing the CSC, in case it changes it should of course display GT-N7100TADXEO). I wiped the phone a few times, went back to the original FW (XXALJ1), changed the CSC back to XEF but no luck.
I've gone through many sites/forums but didn't find the answer. Also I didn't mess with EFS folder, I have my proper IMEI. Is there a possibility that CSC Select app did something wrong to the phone? I don't think so because if I'm right it only triggers Samsung's built-in Preconfig menu, so it should't do any harm. I regret not checking if Kies works properly before changing the CSC.
So the big question is: where the phone reads the PC from (where it's stored?) and how to make the Product Code appear as it should?
EDIT:
I figured out the problem lies within the nv_data.bin file in EFS folder. Inside of this file there's a string "Not active". The same string is present in the backup copy (.nv_data.bak). I tried to edit the file with hex editor and put the right product code in place of "Not Active" string but I can't generate proper md5 hash for it (it seems it's not a regular md5 hash that Samsung uses). And when you delete nv_data.bin.md5 it won't recreate one automatically as it was the case in earlier phones. It will just use the backup file. Even when I deleted .nv_data.bak, .nv_data.bak.md5 and nv_data.bin and nv_data.bin.md5 and uploaded only the modified nv_data.bin with proper product code - it somehow restored the files from somewhere else (I heard there is a hidden partition or something with another backup files) and again I have PC: Not active.
I think the solution would be to somehow create md5 hash of that modified nv_data.bin file that's accepted by the phone but I don't know how.
Click to expand...
Click to collapse

bevybeast said:
Hi brother im also facing the same problem can you please help me.
Click to expand...
Click to collapse
I haven't find a solution yet so I can't help you but I'll post here in case I fix this. I'm rather counting on others' advice because I've already spent many hours trying to find the solution without success.

product code
tom369 said:
I haven't find a solution yet so I can't help you but I'll post here in case I fix this. I'm rather counting on others' advice because I've already spent many hours trying to find the solution without success.
Click to expand...
Click to collapse
You can try FREE SRS PRODUCT CODE CHANGER SAMSUNG FOR KİES UPDATE program.

ersan19 said:
You can try FREE SRS PRODUCT CODE CHANGER SAMSUNG FOR KİES UPDATE program.
Click to expand...
Click to collapse
you did try that program?

ersan19 said:
You can try FREE SRS PRODUCT CODE CHANGER SAMSUNG FOR KİES UPDATE program.
Click to expand...
Click to collapse
Thanks for the tip, unfortunately I can't check it because being helpless and with no clues how to resolve the issue I've sent the phone to the service center before I saw this message. But maybe bevybeast who's also facing this problem as written above can check it and report back if it works.

thanx for sharing this, OP
I had this exact same problem. I messed up with GalaxSim Unlock from Play to see if I'd be able to unlock my phone so my EFS files were changed. I decided I don't need it yet so I restored a backup (with the tool described in this thread: http://forum.xda-developers.com/showthread.php?t=1922473 ) and I was pretty sure I got it back to the original.
after I read your description I decided to take another look and found that my NV_DATA.BIN contained a "Not Active" code as it appeared to have been written a very long time ago. I tried again and again and wasn't able to restore the backup, after restart nv.log was showing:
Code:
Tue Dec 18 14:08:49 2012: cracking detected
Tue Dec 18 14:08:49 2012: NV backup has been rebuilt
Tue Dec 18 14:08:49 2012: NV restored
well, luckily I had a backup made with GalaxSim Unlock itself and when I tried restore from the application it worked.
I don't get what "Not Active" is doing there in the first place but it's quite dangerous in case anything goes wrong with the current nv_data.bin, the system will restore to some data that is fishy to say the least. So far I only noticed the "Product Code" was wrong inside but who knows what else is not that obvious

ersan19 said:
you did try that program?
Click to expand...
Click to collapse
Hi ersan19,
I did try it but unfortunately it seems to do nothing - I get the message that product code changed successfully but nothing more really happens. Even after restarting the phone. It won't even change the CSC, not to mention the complete product code. I even disconnected the phone and tried to change the code and it said product code changed OK
@primusmagestri: I'm happy this topic helped you.

i am having the same prob ... so did anyone have a solution to this prob .. or should i send my phone to service center ..... ?

but this happened to me after restoring animage of the efs .. which was taken when the phone was normal

can any one give me the product code of note 2 (n7100) uae ..

Hi,
If you really don't want to send the phone to the service centre the only way I see is to change the nv_data.bin file content (in EFS) folder and put the proper product code string for your phone. The problem is - you also have to calculate md5 hash for it, which is NOT a regular md5 and I don't personally know how to calculate it. In older firmwares you could just delete the .md5 file and the system would calculate the md5 but now it's not this way and you have to put the correct md5 checksum file. If you don't, the nv_data.bin will be recreated from nv_data.bak file. And in case you deleted both these files, the system will recreate them from nv_core.bak file.
There's still chance you have proper product code in either nv_data.bak or nv_core.bak file. If you find the right product code in nv_data.bak just delete nv_data.bin and you should be ok. If only nv_core.bak has good product code, you delete both nv_data.bin and nv_data.bak. You can check the contents of the files with hex editor. Remember to make EFS folder backup before doing anything, and remember that messing with those files can lead to serious trouble if you do something wrong. And of course you need root access for it.
Or maybe there's someone here who would like to share with us the md5 calculation method Samsung is using?

tom369 said:
Or maybe there's someone here who would like to share with us the md5 calculation method Samsung is using?
Click to expand...
Click to collapse
Big thanx for the info ..and waiting for some to tell us how to fix it

devil_slayer said:
can any one give me the product code of note 2 (n7100) uae ..
Click to expand...
Click to collapse
gt-n7100rwdxsg

I am also having the same issue. This happened to my phone after I used CSC Changer app from Play store(In root mode)..
Now I have to update my phone using ODIN only.. Hope somebody will come up with a solution.

AlanDS said:
I am also having the same issue. This happened to my phone after I used CSC Changer app from Play store(In root mode)..
Now I have to update my phone using ODIN only.. Hope somebody will come up with a solution.
Click to expand...
Click to collapse
You have to repair product code with any service box,ex- z3x ,and after that use CSC Galaxy S/s2/s3 from Google Play in ROOT MODE and choose your product code.
All data will be erased. Now flash your phone with odin again,star phone and wipe data again in recovery.

Bruno_rv said:
You have to repair product code with any service box,ex- z3x ,and after that use CSC Galaxy S/s2/s3 from Google Play in ROOT MODE and choose your product code.
All data will be erased. Now flash your phone with odin again,star phone and wipe data again in recovery.
Click to expand...
Click to collapse
can you please explain in detail?

I'm having the same problem with my note 3. Anyone found the solution yet?
Sent from my SM-N9005 using XDA Premium 4 mobile app

Same problem. Any fix for this ?

Same issue.
Sent from my GT-N7100 using XDA Premium 4 mobile app

[Q] Edit Unlock_Code.bin

I was wondering, since it looks like HTCdev has stopped working, would it be possible to alter the Unlock_code.bin file that comes from HTCdev that works for my device to work with another device? I just opened the bin file with notepad to verify that we could edit the file. If we could figure out what makes the Unlock_code.bin file work with my device, maybe we could create a new Unlock_code.bin file to work with a different device, or at least that was what I was thinking.

I'm not smart enough to know that answer, but I'd be willing to throw mine in as well.
I know that unlock code is probably the key, but I haven't seen what's inside that file yet. I can't imagine you could just change that code for your device (since you can still get that code) - that would be too easy.
Sent from my HTC6500LVW using Tapatalk 4

I need about 4 of them so I can see whats the same vs whats different.

This is a piece of what you find in the Unlock File - 潻刈ഌ垀皅꜂Ẩ筣 - it is in the ball park of 120 characters long, that is just a guesstimate.

Yeah its a bunch of gibberish like it's encrypted or encoded or something. Will send mine over in a few if you think it's worth looking at.
Sent from my HTC6500LVW using Tapatalk 4

*Removed due to incorrect information*
This is the font I used to help display the characters better - http://www.prokerala.com/downloads/fonts/AnjaliOldLipi.ttf - to install in Win 7 download the file, double click to open, select install on the top left of the window. After that you will be able to select the font in the font list in notepad or whatever text editor you choose.
- Edit - I was incorrect in stating that it was in Malayalam, that appears to only be for ഌ , the part about the font helping better display the characters is true.

Guys, it's not gonna be in a human readable language because that would be dumb of HTC since anyone would be able to replicate the unlock then. Best bet is that comparing several using a hex editor will help.

Isnt the file signed? Thats the whole point of the token really? If you edit it you would lose the signature?

Notepad++ is a good translator And thats how it looks like when you go from ASCII to HEX the Bold is what I coun't convert.
Code:
894009A6BCAB49F9AFB7D42D5F8A6F49
7465B991F0D7F613FA9DD0DAF2D23C27
BD6D3951EFBF892065
97832A471A4B663C84412681030E1925
96563BFCBD7EA8C12406A99131757C42
9AAB1412B82271777FD78ED08D732B31
828DEE3C78C6F6B973A76FCF800C4A0B
410B
D717C8ED04EEFCE23604A5
C7E445D763BEAA86DCFE1145626F[B][U]‹ÿ[/U][/B]73D99D3739E772C6136F"51DC3797
450166F8004461596BA4
85ECF55695D17B7967240B27F94CC481
C320CD7E2B86620BEEA0F0E5C8C7A216
565BF3A6762C3FC662EA0F7B40C5FDA0
7962739CBB1286A32F5BB9B3A6597374
B8E346CC17178ADA1FC66BA18BA905F7
5F4D59C87E97E69CD186353B

I went ahead and did a conversion as well. I know 123421342 said that these were signed files but is there a way to copy the signature that is associated with the Unlock_Code.bin file? I do not really understand how signed files work, but HTCdev gives a different file per user, are the signatures the same on all of the Unlock_Code.bin files or is it a unique signature for each bin file that only works with your device?
Also, I do not know what I did differently when translating my bin file to Hex but it appeared that all of it was translated.
Code:
E6BDBBE58888E0B48CE59E80E79A85EA
9C82E1BAA8E7ADA3E88D91EF86B8ECA6
BFE7A4B8E79383E0ACA0EFA885E5A19C
E4809EEFA398E3A398E48FA1EBBFAFEC
A584E8BD8CE790AEE598B0E9B8B4ECA1
ADE8AC93E9B786E2AAACF394B386EEA1
A2E79289EB8FBFEEACA8EE8EADE59698
EAB898E1AFA6E2939FEBAA81E0B0B1E9
87B1EF94BDE0B4A2E79FA3EA968EEC81
A0ED83B2E6A88EE8A89BE5A788E4B1BC
E18EAAED8395E7B59FE2A4AFE29BB5EE
99BEE6A0B9EBB3ACEB9A82EE9C90EFB9
8BEE9888E698A4EE8DA1EC82A6E28EB3
F3A4B198E49689E281B3EB9F98E99ABF
E69A8BE786B6F1B1A396EC9AB3EF89B4
E38F92EEA48BE2BE8AEF90AFEAB19CE7
A796E1B2A7DE93E8AAB6E3BC8CE1938A
EFAD81EC8F89EC8B87E5B292EE85B6EA
BC86E7A9B0ECB8A1E4AF82E2A29BE281
9ADD99EE9FB3C394E4ADBEE2AF80EE9E
83E1A3BEEC81A5EE9295E3AA9AE58090
E598B3ECA696E6B3BAE0A497E884ABEA
B89AE6B1BCE29A99ECB0AFE2BF88E585
AFEE82BEEBBF84

Wozzie said:
I went ahead and did a conversion as well. I know 123421342 said that these were signed files but is there a way to copy the signature that is associated with the Unlock_Code.bin file? I do not really understand how signed files work, but HTCdev gives a different file per user, are the signatures the same on all of the Unlock_Code.bin files or is it a unique signature for each bin file that only works with your device?
Also, I do not know what I did differently when translating my bin file to Hex but it appeared that all of it was translated.
Code:
E6BDBBE58888E0B48CE59E80E79A85EA
9C82E1BAA8E7ADA3E88D91EF86B8ECA6
BFE7A4B8E79383E0ACA0EFA885E5A19C
E4809EEFA398E3A398E48FA1EBBFAFEC
A584E8BD8CE790AEE598B0E9B8B4ECA1
ADE8AC93E9B786E2AAACF394B386EEA1
A2E79289EB8FBFEEACA8EE8EADE59698
EAB898E1AFA6E2939FEBAA81E0B0B1E9
87B1EF94BDE0B4A2E79FA3EA968EEC81
A0ED83B2E6A88EE8A89BE5A788E4B1BC
E18EAAED8395E7B59FE2A4AFE29BB5EE
99BEE6A0B9EBB3ACEB9A82EE9C90EFB9
8BEE9888E698A4EE8DA1EC82A6E28EB3
F3A4B198E49689E281B3EB9F98E99ABF
E69A8BE786B6F1B1A396EC9AB3EF89B4
E38F92EEA48BE2BE8AEF90AFEAB19CE7
A796E1B2A7DE93E8AAB6E3BC8CE1938A
EFAD81EC8F89EC8B87E5B292EE85B6EA
BC86E7A9B0ECB8A1E4AF82E2A29BE281
9ADD99EE9FB3C394E4ADBEE2AF80EE9E
83E1A3BEEC81A5EE9295E3AA9AE58090
E598B3ECA696E6B3BAE0A497E884ABEA
B89AE6B1BCE29A99ECB0AFE2BF88E585
AFEE82BEEBBF84
Click to expand...
Click to collapse
It's like making an md5 hash. If you change a single bit the hash is changed. If you change the contents htc would have to sign it again so it has the private key signature
Sent from my HTC6435LVW using xda app-developers app

Please excuse my ignorance, I really do not have much knowledge of file signatures.
If HTC can resign the bin file, what is stopping us from doing something similar? Isnt it possible to view and make a copy of the file signature before it is altered? I realize these sort of things are in place to not be circumvented but the same could be said about all the work that has been developed here on XDA to unlock bootloaders along with other things.

Wozzie said:
Please excuse my ignorance, I really do not have much knowledge of file signatures.
If HTC can resign the bin file, what is stopping us from doing something similar? Isnt it possible to view and make a copy of the file signature before it is altered? I realize these sort of things are in place to not be circumvented but the same could be said about all the work that has been developed here on XDA to unlock bootloaders along with other things.
Click to expand...
Click to collapse
It's like a checksum, I presume. If the data changes, the signature changes as well to match the checksum. Unless you have inside knowledge of this, it will be extremely difficult to hack the tokens.
Meaning, if you change the data inside the file, you can't reuse the signature.

karn101 said:
It's like a checksum, I presume. If the data changes, the signature changes as well to match the checksum. Unless you have inside knowledge of this, it will be extremely difficult to hack the tokens.
Meaning, if you change the data inside the file, you can't reuse the signature.
Click to expand...
Click to collapse
Would it be possible to extract the signature of a file that has not been altered and then add that signature to an altered file?
I know it seems like a lot of work but if we could figure out how to create our own Unlock_Code.bin files, not only this phone but possibly other HTC phones might be able to use this method.

Wozzie said:
Would it be possible to extract the signature of a file that has not been altered and then add that signature to an altered file?
I know it seems like a lot of work but if we could figure out how to create our own Unlock_Code.bin files, not only this phone but possibly other HTC phones might be able to use this method.
Click to expand...
Click to collapse
No files are signed with a private key unless we have the key by stealing it or leaking it we can't sign things with their signature
Sent from my HTC6435LVW using xda app-developers app

Wozzie said:
Would it be possible to extract the signature of a file that has not been altered and then add that signature to an altered file?
I know it seems like a lot of work but if we could figure out how to create our own Unlock_Code.bin files, not only this phone but possibly other HTC phones might be able to use this method.
Click to expand...
Click to collapse
The signature changes with the file. The unaltered file's signature would not match the alerted file.
Sent from my HTC6500LVW using Tapatalk 4

anyone attempted to super CID it? make the phone similar to the sprint or other cdma with the same bootloader to get the code to unlock on htcdev?
just throwing that out there. i wont be on the ONE till late this year so i wont be able to work on it. :/

synisterwolf said:
anyone attempted to super CID it? make the phone similar to the sprint or other cdma with the same bootloader to get the code to unlock on htcdev?
just throwing that out there. i wont be on the ONE till late this year so i wont be able to work on it. :/
Click to expand...
Click to collapse
That would be an interesting approach. Or at least try to change the CID to T-Mobile or something. I honestly don't think it would work though.

synisterwolf said:
anyone attempted to super CID it? make the phone similar to the sprint or other cdma with the same bootloader to get the code to unlock on htcdev?
just throwing that out there. i wont be on the ONE till late this year so i wont be able to work on it. :/
Click to expand...
Click to collapse
Have to be s-off don't ya?
Code:
(bootloader) [SD_ERR] The project does not support SD card
(bootloader) E0902910 E0902E20
FAILED (status read failed (Too many links))
finished. total time: 0.003s

Flyhalf205 said:
Have to be s-off don't ya?
Click to expand...
Click to collapse
thought you already had s-off? this wont work for ya? idk what bootload you guys are on. :/
http://forum.xda-developers.com/showthread.php?t=2314582