Develop Bugs

Taking EFS folder from SGS and putting it in another SGS

So I have an SGS and I screwed up when JPC came out and so I have the default IMEI number and product code of XXX. So out of curiosity, I'm wondering if I took the efs folder of another sgs and putting it in this 'paper weight' phone.
I'm obviously going to have to buy another SGS, but this is a thought that I had. I"m going to take a stab and think that this should work right since it's just like backing up/restoring the efs folder, just putting it on another phone.
I'm just looking for feedback on this idea, it's just going to be a costly solution for me. I'm primarily doing this until there's a solution to restoring the IMEI number for the SGS and then selling the other SGS.

I'm not a developer... but I would assume you would need to edit the new nv_data.bin files using a hex editor before you put them on the bricked device.
If you do a search on downloads.com you ought to find a freeware one.
Use that to search and replace the xxx imei number with that on the barcode on the side of the box.
Please be advised that this is pure speculation as my imei didn't default... but I found I could change my product code in a similar way.

Won't work. the /efs folder stores your IMEI number stuff, and the file's digitally signed. You can't just dump another file from another phone into it to fix the problem.

Well, my device not bricked as i can still use it, its just that i have a default imei and product code. Im aware that its digitally signed, but if im taking a file thats digitally signed by the same product then i would assume thats okay.
A digitally signed file from an one i9000m should be signed the same way as another i9000m would digitally sign a file no?
Sent from my GT-I9000M using XDA App

BakaSenpai said:
Well, my device not bricked as i can still use it, its just that i have a default imei and product code. Im aware that its digitally signed, but if im taking a file thats digitally signed by the same product then i would assume thats okay.
A digitally signed file from an one i9000m should be signed the same way as another i9000m would digitally sign a file no?
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
Yes most likely but then it will have the IMEI of THE OTHER device and that's not what you want. If you change the file then the md5 checksum becomes invalid. However, I thought I read somewhere that the phone would re-create teh checksum file if it's missing. Whether this allows you to change the file I do not know......

ewok666 said:
Yes most likely but then it will have the IMEI of THE OTHER device and that's not what you want. If you change the file then the md5 checksum becomes invalid. However, I thought I read somewhere that the phone would re-create teh checksum file if it's missing. Whether this allows you to change the file I do not know......
Click to expand...
Click to collapse
It won't work, the files are device specific.
EDIT: Aha, found the posts i was looking for.
http://forum.xda-developers.com/showpost.php?p=7509851&postcount=24
http://forum.xda-developers.com/showthread.php?t=743183&highlight=IMEI

It works only for product code...
i restore my DBT product code in this way:
-first copy the nv_data.bin and md5 files with their bak files (4 files)
-reboot
then my sims didnt work right ... (wrong pin error)
-with root explorer i deleted the nv_data.bin and nv_data.bin.md5 files. DONT DELETE the .bak files....
reboot.
my product code is now ok and my sim works.
imei...wrong.

Rawat said:
It won't work, the files are device specific.
EDIT: Aha, found the posts i was looking for.
http://forum.xda-developers.com/showpost.php?p=7509851&postcount=24
http://forum.xda-developers.com/showthread.php?t=743183&highlight=IMEI
Click to expand...
Click to collapse
Bah! Had I only found this earlier, then I guess I wouldn't have posted this questions then. *sigh* I guess i just have to wait for some kind of solution. Thanks Rawat

check if this guy can restore your IMEI
http://forum.samdroid.net/f28/complete-imei-restore-how-1817/
(should be similar methodology)

I tried this and it dosen't work. The device somehow validates the imei..
Sent from my GT-I9000 using XDA App

[DISCUSS] KDZ Files.

Not sure if general is the place for this but I'd like to start a "formal" discussion of the KDZ files and what they precisely contain.
full disclosure: I'm not a pro with all this stuff, I'm primarily just curious, and know my way around well enough I can do some basic investigating
Here's what I've looked at so far, and what I'd like to do:
So far:
The Telus E973 KDZ file retrieved from LG's servers contains a cab file, which was initially extracted using LGExtract (http://forum.xda-developers.com/showthread.php?t=1566532)
Inside the CAB is a .dz file and a .dll (G_TDR_0141.dll)
The .dz file does not contain any headers for existing "known" .dz file formats. (For example: http://www.frenchcoder.com/dzextract-lg-dz-file-format-and-extract-tool-lg-ks20/)
It would seem that flashing the kdz using the method outlined in potatohead's thread does not 100% recover from a brick, but seems to depend on what the actual problem with the phone is.
What I'd like to determine:
What exactly is in the KDZ? Does it contain all stock partitions for the phone or only selective partitions. (such as /system)
Out of pure curiosity, when I have time, I'd like to compare the hex of the .dz file, to see if it contains any of the known stock partitions such as the aboot, boot, or recovery. I have this sinking feeling that it doesn't include the recovery based on chadouming's experiences with it. to see if the .dz file is compressed in some proprietary fashion, or if it's a simple arrangement of the stock partitions with some standardized headers.
Please feel free to contribute, or criticize me, I'd just like to fuel some interest and discussion.

thracky said:
Not sure if general is the place for this but I'd like to start a "formal" discussion of the KDZ files and what they precisely contain.
full disclosure: I'm not a pro with all this stuff, I'm primarily just curious, and know my way around well enough I can do some basic investigating
Here's what I've looked at so far, and what I'd like to do:
So far:
The Telus E973 KDZ file retrieved from LG's servers contains a cab file, which was initially extracted using LGExtract (http://forum.xda-developers.com/showthread.php?t=1566532)
Inside the CAB is a .dz file and a .dll (G_TDR_0141.dll)
The .dz file does not contain any headers for existing "known" .dz file formats. (For example: http://www.frenchcoder.com/dzextract-lg-dz-file-format-and-extract-tool-lg-ks20/)
It would seem that flashing the kdz using the method outlined in potatohead's thread does not 100% recover from a brick, but seems to depend on what the actual problem with the phone is.
What I'd like to determine:
What exactly is in the KDZ? Does it contain all stock partitions for the phone or only selective partitions. (such as /system)
Out of pure curiosity, when I have time, I'd like to compare the hex of the .dz file, to see if it contains any of the known stock partitions such as the aboot, boot, or recovery. I have this sinking feeling that it doesn't include the recovery based on chadouming's experiences with it.
Please feel free to contribute, or criticize me, I'd just like to fuel some interest and discussion.
Click to expand...
Click to collapse
When I used KDZ I had my bootloader relocked and lost cwm.
Sent from my LG-E971 using xda app-developers app

theMaDHakkeR said:
When I used KDZ I had my bootloader relocked and lost cwm.
Sent from my LG-E971 using xda app-developers app
Click to expand...
Click to collapse
Good to know. I think the one case we've had so far where this didn't work had some "advanced" issues, possibly involving partition table being messed up, which I have a feeling the KDZ flash wouldn't touch.

SmartFlash will be nice to have it completely restore everything to factory default and it is easy to use.
But for SmartFlash we need to convert the KDZ files in to BIN and FLS.
There is a tool for that but works only for P990/P970/P920 firmware's.
http://forum.xda-developers.com/showthread.php?t=1692191
Unfortunately the Rom converter does not work with the firmware's from new phones like Optimus G / Optimus 4x.

d0ct0ru said:
SmartFlash will be nice to have it completely restore everything to factory default and it is easy to use.
But for SmartFlash we need to convert the KDZ files in to BIN and FLS.
There is a tool for that but works only for P990/P970/P920 firmware's.
http://forum.xda-developers.com/showthread.php?t=1692191
Unfortunately the Rom converter does not work with the firmware's from new phones like Optimus G / Optimus 4x.
Click to expand...
Click to collapse
I think this is due to the fact that they've made changes in the actual .dz format as any existing tool I've tried cannot find any known headers in the file. When I have some time I'm going to see if I can narrow down any patterns/headers.

thracky said:
Not sure if general is the place for this but I'd like to start a "formal" discussion of the KDZ files and what they precisely contain.
full disclosure: I'm not a pro with all this stuff, I'm primarily just curious, and know my way around well enough I can do some basic investigating
Here's what I've looked at so far, and what I'd like to do:
So far:
The Telus E973 KDZ file retrieved from LG's servers contains a cab file, which was initially extracted using LGExtract (http://forum.xda-developers.com/showthread.php?t=1566532)
Inside the CAB is a .dz file and a .dll (G_TDR_0141.dll)
The .dz file does not contain any headers for existing "known" .dz file formats. (For example: http://www.frenchcoder.com/dzextract-lg-dz-file-format-and-extract-tool-lg-ks20/)
It would seem that flashing the kdz using the method outlined in potatohead's thread does not 100% recover from a brick, but seems to depend on what the actual problem with the phone is.
What I'd like to determine:
What exactly is in the KDZ? Does it contain all stock partitions for the phone or only selective partitions. (such as /system)
Out of pure curiosity, when I have time, I'd like to compare the hex of the .dz file, to see if it contains any of the known stock partitions such as the aboot, boot, or recovery. I have this sinking feeling that it doesn't include the recovery based on chadouming's experiences with it. to see if the .dz file is compressed in some proprietary fashion, or if it's a simple arrangement of the stock partitions with some standardized headers.
Please feel free to contribute, or criticize me, I'd just like to fuel some interest and discussion.
Click to expand...
Click to collapse
I don't know about DZ files, but the wdb format that my P970 uses can be made into a AP bin file that is essentially all the partitions of the phone and all the partitions with size (size on the file, not size of partition on device) 0 is skipped over.
I say split up into partitions but it's actually data blocks and can cross over partitions since it uses raw write to device and it looks like a convenience that it's set up that way.
Check out this thread.
It's a tool for extracting kdz and wdb files (dz planned).

xonar_ said:
I don't know about DZ files, but the wdb format that my P970 uses can be made into a AP bin file that is essentially all the partitions of the phone and all the partitions with size (size on the file, not size of partition on device) 0 is skipped over.
I say split up into partitions but it's actually data blocks and can cross over partitions since it uses raw write to device and it looks like a convenience that it's set up that way.
Check out this thread.
It's a tool for extracting kdz and wdb files (dz planned).
Click to expand...
Click to collapse
I used the tool it's based on, LGExtract, to pull the .cab containing the .dz and the .dll in the first place, however we can't do anything with the .dz at the moment.

thracky said:
I used the tool it's based on, LGExtract, to pull the .cab containing the .dz and the .dll in the first place, however we can't do anything with the .dz at the moment.
Click to expand...
Click to collapse
Oops. Meant to point to LGExtract.
Sent from my LG-P970

Were you able to get a Sprint KDZ file? And if so, can I get a copy?
Thanks!

waldo36 said:
Were you able to get a Sprint KDZ file? And if so, can I get a copy?
Thanks!
Click to expand...
Click to collapse
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=<yourimei>

t1mman said:
http :// csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=<yourimei>
Click to expand...
Click to collapse
*Edited*
Ok, I got the website to send me the files, but they are all in .CAB format instead of KDZ. Do I need to alter them, unpack them, or something else, once they get done downloading?
Thanks!

waldo36 said:
Were you able to get a Sprint KDZ file? And if so, can I get a copy?
Thanks!
Click to expand...
Click to collapse
Already covered this with you on IRC but gonna mention it for anyone else interested:
We have .tot files for AT&T and Sprint to be used with LGNPST, which would be preferred.
Read the respective at&t/sprint LGOG forums for more info.

No KDZ download link after I insert E970 IMEI

piyopiyo81 said:
No KDZ download link after I insert E970 IMEI
Click to expand...
Click to collapse
E970 is AT&T isn't it? You should be using the .tot, and this is not the forum for AT&T or Sprint's Optimus G in the first place.

zVB Brick
Hello XDA Devs,
I successfully rooted my phone and unlocked the bootloader. I kept seeing warnings that if I reset my LG Optimus G (Sprint) after rooting, that it would crash and enter a bootloop. PRetty much Bricked. It wont power on, but I can enter download mode and fastboot mode. I tried to put the stock rom but the KDZ files don't appear. Somebody help!

thracky said:
E970 is AT&T isn't it? You should be using the .tot, and this is not the forum for AT&T or Sprint's Optimus G in the first place.
Click to expand...
Click to collapse
True, but the link does work for sprint. It gives cabs, which turn into tots with conversion. Any idea why some use tot and others use kdz?
Sent from my LG-LS970 using xda app-developers app

Need to extract a bin file from kdz? Contact me
Sent from my LG-P990 using xda app-developers app

[TUTORIAL] How To Extract Files From a TAR.MD5 Stock ROM (SPH-L710)

I recently did this for the E4GT and have been asked to do it here as well.
I've received a TON of PM's and emails asking how to do this and I've decided to do a write-up for everyone. Now to start off, this does not automatically make you a Super Duper Developer, this does not show you how to make your own TAR ROMs, nor does it show you how to make your own Odin One-Clicks. What it does do is show you how to pull files from those stock leaked/official ROMs so that you can proceed to make yourself into a Super Duper Developer!
In essence if the Developer knows what they are doing they could use this method to extract all the files from the build and could then add them to a ZIP and have a stock odexed ROM within minutes and do it all through Windows! Depending on time I may or may not do a tutorial on that as well...
So let's begin!
We've all seen those pesky TAR.MD5 packages that we can flash through Odin. How often have you wanted to look inside them and see what is inside before flashing? There are several ways to do it and the most common answer requires Linux and Dsixda's Kitchen utility. This tutorial gives you the ability to do that through Windows and without having to extract the full ROM. These instructions are specific to the Samsung Galaxy S3 (all variants) but can be used on most Samsung Galaxy phones.
Each TAR.MD5 release contains multiple files. Each of these files corresponds to a specific partition on your device. These files are formatted to be mounted by your device but not by a computer. We will be converting them from a .img.ext4 partition type to an ext4.img type partition so we can mount them and read them through Windows. For this tutorial we will be opening up the system.img.ext4 (the system files partition).
Before you dive in there are a few things you'll need.
- A PC running Windows.
- A stock TAR.MD5 release. Several are available at www.rwilco12.com.
- DiskInternals Linux Reader (must be installed on the Windows PC). You can download DiskInternals Linux Reader here.
- SGS2toEXT4 Utility available here. *Be sure to extract the JAR file from the ZIP archive.
- 7-Zip available here.
For the rest of the tutorial please visit my site: www.rwilco12.com
Enjoy!

Reserved.

Awesome! First!
Sent from my SPH-L710 using xda app-developers app

great it's work fine with me on windows8
if you let me a noop question
can we cook the rom in this way ? i mean after upack the image we can edit the files or the apk or the font and repack it again as a md5.tar extension
is that possible
regards

IRoN MaN9 said:
great it's work fine with me on windows8
if you let me a noop question
can we cook the rom in this way ? i mean after upack the image we can edit the files or the apk or the font and repack it again as a md5.tar extension
is that possible
regards
Click to expand...
Click to collapse
Unfortunately no. That part does require Linux but this could help simplify the process if you prefer a Windows environment.

رد: [TUTORIAL] How To Extract Files From a TAR.MD5 Stock ROM (SPH-L710)
rwilco12 said:
Unfortunately no. That part does require Linux but this could help simplify the process if you prefer a Windows environment.
Click to expand...
Click to collapse
Relly sad hope that you can develop this threat in the future so we can cook the stock roms anyway thank you very much for your answer
Regards

IRoN MaN9 said:
Relly sad hope that you can develop this threat in the future so we can cook the stock roms anyway thank you very much for your answer
Regards
Click to expand...
Click to collapse
I might have some other stuff in the works for you guys here soon.

رد: [TUTORIAL] How To Extract Files From a TAR.MD5 Stock ROM (SPH-L710)
rwilco12 said:
I might have some other stuff in the works for you guys here soon.
Click to expand...
Click to collapse
I can't wait to see your next work

Hey after installing linux reader on windows it shows mf5 file in HEX manner , it dont convert it in .zip file..
any way to do it?

mjp93 said:
Hey after installing linux reader on windows it shows mf5 file in HEX manner , it dont convert it in .zip file..
any way to do it?
Click to expand...
Click to collapse
You need to extract it from the img file by saving it. After extracting you'll need to package it in a ZIP.

I followed the guide to the t and its saying that the image is invalid. Any ideas?

macasus76 said:
I followed the guide to the t and its saying that the image is invalid. Any ideas?
Click to expand...
Click to collapse
What device and what files are you using?

Using windows Vista x64 the file is a I537UCUCNE3 stock odin image. I created a .img file using ext4 tool you posted but the Linux viewer says invalid

The image here shows my created .img file on the left, the Linux reader on the right and the error in the middle

This tutorial is no good anymore.

Finally !!
I found how do that after to waste a day to search one real solution.
Is only to use the ClassyKitchen free version for windows.
I found it here:
https://forum.xda-developers.com/chef-central/android/tool-classykitchen-android-roms-t3862584
Basically, after to open the program, you will choose "create new project" on the tab "Projects utils", and choose the firmware from PC or from mobile root. So, the program will extract the folders and files to PROJECT/system folder, and you will can access them by windows explorer, including the app folder with all original apks.
I was looking for a way to restore the calculator apk after delete it before to find another to replace it.
[ ].

[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

System Dump for SM-R800

Hi All,
I downloaded the ROM for SM-R800 and would like to extract the contents of rootfs.img file.
But no success after renaming the extension to .zip and .rar.
Basically I want the system dump of the watch.
Would someone be able to share it with me?

As an Windows Fanboy... I am using WinHex to extract files from rootfs.img...
Best Regards

adfree said:
As an Windows Fanboy... I am using WinHex to extract files from rootfs.img...
Best Regards
Click to expand...
Click to collapse
Hi adfree,
Thanks for the advise. I installed Winhex, but I am finidng it difficult to extract the data. Openening the rootfs.img I get a lot of hexadecimal numbers as shown below.
Kindly request your guidance.

Here are Screenshots with WinHex...
Other way is to use for instance Tizen Studio and mount in Emulator... longer way...
Never tested with Linux PC...
Best Regards

rockz1991 said:
Hi All,
I downloaded the ROM for SM-R800 and would like to extract the contents of rootfs.img file.
But no success after renaming the extension to .zip and .rar.
Basically I want the system dump of the watch.
Would someone be able to share it with me?
Click to expand...
Click to collapse
How did you dump the ROM for SM-R800?? Can you please explain what you did?

I0T said:
How did you dump the ROM for SM-R800?? Can you please explain what you did?
Click to expand...
Click to collapse
I just googled the firmware. I didn't dump.

adfree said:
Here are Screenshots with WinHex...
Other way is to use for instance Tizen Studio and mount in Emulator... longer way...
Never tested with Linux PC...
Best Regards
Click to expand...
Click to collapse
I tried this but only get a message that size is not a multiple of 512 and there is an incomplete RAW image. Please let me know what steps you took to be able to read this information thanks.

@Mr Bigglesworth
Sorry, still too laz ehm busy to answer PMs...
Can you give full details...
SM-R815?
Because SM-R815U SM-R815F SM-R815W...
And Firmware you tried...
Filename...
Samsung did same "magic"... so few rootfs.img are easily extract able via 7Zip Tool...
Best Regards

Originally I looked at COMBINATION-FT40_R815FXXU1ASB1 (for my 815f). Then failed so I just tried looking in a r800 image (r800xxu1arh3) as my first stage was really to understand the make up and what changes might have happened between firmware, so it didn't need to be the specific firmware for my watch. Both returned the same when using winhex, and both have an error message if trying 7zip, the the file is corrupted. Do you know which firmware might be readable using 7zip as a start? Thanks