Related
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?
Hi,
So i coulden't wait and had to try out JPC firmware. Personally i didn't like it at all, so i went back to JM7. 1 thing i did not like is my product code changed from XEN to KOR.
And here is how to fix that easly:
I tested this on 2.1 cause i was on JM7 when i found this out, but this works with JPC/JPH also.
this fix is for those who do not have (correct) .bak files in the /efs/ directory!
- First make sure you are ROOT and install a Terminal Emulator (can be found in the market)
- Now open the Terminal, enter ''su'' to gain root access
- Enter: cp /efs/nv_data.bin /sdcard/
- Connect you're SGS to the usb and download ''nv_data.bin'' to your computer
- Open ''nv_data.bin'' with notepad or wordpad and search for ''KOR'' change this to the product code matching your country (red marked text should be changed). Im dutch, so mine is XEN. The line looks like this:
Code:
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿMP 0.800 ÿ[COLOR="Red"]KOR[/COLOR] GT-I9000HKD[COLOR="Red"]KOR[/COLOR]
- Now simply save your changes.
- Connect your SGS with usb, upload ''nv_data.bin'' to internal sdcard.
- Disconnect USB !
- Open Terminal Emulator and enter ''su''
- Now enter: cp /sdcard/nv_data.bin /efs/nv_data.bin
Also enter: rm -rf /efs/nv_data.bin.md5
- Close terminal, Reboot Phone. And Voila!!! Product Code restored!!
**IF YOUR SIMCARD DOESN'T WORK AFTER THIS, EXECUTE THE FOLLOWING**
- adb shell
- su
- busybox chown 1001:1001 /efs/nv_data.bin
- reboot
You can also do this from the Terminal Emulator if you don't have ADB on your PC! Like this:
-su
-chown 1001:1001 /efs/nv_data.bin
-reboot
I hope it's easy to follow my steps, it works guaranteed.
UPDATE - 13/09
Some people say you don't have to create a new md5, just remove the old one on the phone. kaffre and i tested this, the phone recreates the md5 file for you. So i've updated the steps in my tutorial, to make it even more easy!
UPDATE - 15/09
Simcard fix added. Thanks to tokinux
I`d suggest using a hex editor instead of any wordpad/notepad editor ...
Methyldioxide said:
Hi,
So i coulden't wait and had to try out JPC firmware. Personally i didn't like it at all, so i went back to JM7. 1 thing i did not like is my product code changed from XEN to KOR.
So f*ck that and here is how to fix that easly:
I tested this on 2.1 cause i was on JM7 when i found this out, but im 99% sure this works with JPC also.
- First make sure you are ROOT and install a Terminal Emulator (can be found in the market)
- Now open the Terminal, enter ''su'' to gain root access
- Enter: cp /efs/nv_data.bin /sdcard/
- Connect you're SGS to the usb and download ''nv_data.bin'' to your computer
- Open ''nv_data.bin'' with notepad or wordpad and search for ''KOR'' change this to the product code matching your country. Im dutch, so mine is XEN. The line looks like this:
Code:
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿMP 0.800 ÿKOR GT-I9000HKDKOR
- Now simply save your changes.
- Download a md5 creator tool, i use MD5SUMMER
- Create a MD5 file using ''nv_data.bin" and save this as ''nv_data.bin.md5''
- Open ''nv_data.bin.md5'' with notepad and delete all the lines beside the line wich is similar to this one: 4ba37998243f14158884c5f464933398 (ofcourse your line of numbers is different ! ) Save the md5 file.
- Now your md5 file should be exactly 32bytes (this is the same size of the md5 file used by samsung, so please follow this step carefully)
- Connect your SGS with usb, upload ''nv_data.bin.md5'' and ''nv_data.bin'' to internal sdcard.
- Disconnect USB !
- Open Terminal Emulator and enter ''su''
- Now enter: cp /sdcard/nv_data.bin.md5 /efs/nv_data.bin.md5
cp /sdcard/nv_data.bin /efs/nv_data.bin
- Close terminal, Reboot Phone. And Voila!!! Product Code restored!!
I hope it's easy to follow my steps, it works guaranteed.
Click to expand...
Click to collapse
editing those files is there a risk of changing the IMEI in 004999010640000 ??
i think something similar happened to me and now i'm with XXXXXXX as product code and that fake IMEI.......
Narcissus85 said:
editing those files is there a risk of changing the IMEI in 004999010640000 ??
i think something similar happened to me and now i'm with XXXXXXX as product code and that fake IMEI.......
Click to expand...
Click to collapse
My imei did never change, also not after product code restore
For me it seems to be easier to do it with the *#272*hhmm#* solution.
Read about this here: http://forum.xda-developers.com/showthread.php?t=779580
Its doing also a hardreset.. so backup you data!
In case you dont want a hard-reset, this manual solution is much better! So Thx, Methyldioxide for your work and sharing with us!
Donald Nice said:
For me it seems to be easier to do it with the *#272*hhmm#* solution.
Read about this here: http://forum.xda-developers.com/showthread.php?t=779580
Its doing also a hardreset.. so backup you data!
In case you dont want a hard-reset, this manual solution is much better! So Thx, Methyldioxide for your work and sharing with us!
Click to expand...
Click to collapse
but his doesnt change the product code! i did it and still is KOR.
what is true is that putting the right csc is making my phone act like a normal one so at the end having a KOR phone gives me no problems at the moment...
Donald Nice said:
For me it seems to be easier to do it with the *#272*hhmm#* solution.
Read about this here: http://forum.xda-developers.com/showthread.php?t=779580
Its doing also a hardreset.. so backup you data!
In case you dont want a hard-reset, this manual solution is much better! So Thx, Methyldioxide for your work and sharing with us!
Click to expand...
Click to collapse
*#272*hhmm#* only changes the CSC settings indeed, not the actual product code. With warrenty this can be an issue. So i preffer my original product code
Did this actually change the product code or did your Galaxy S replace the changed nv_data.bin file from the backup .nv_data.bak file?
The default action is to use the bak file to write a new nv_data.bin if the original is missing or corrupt. If your original .nv_data.bak still had the original code in it this could be what happened.
I´ve copied my original nv_data.bin and nv_data.bin.md5 to my pc und used md5summer to check if the md5 hash stored in nv_data.bin.md5 is a normal md5 hash of the filesize.
The Hash generated with md5summer didn´t match!!!
Seems to be not an normal md5 hash of the filesize. There must be more.
If i do steps from OP the product code of my phone changes to XXXXXXXX.
Have used an Hex Editor and md5summer. Also tried WinMD5, same ****.
Aery said:
I´ve copied my original nv_data.bin and nv_data.bin.md5 to my pc und used md5summer to check if the md5 hash stored in nv_data.bin.md5 is a normal md5 hash of the filesize.
The Hash generated with md5summer didn´t match!!!
Seems to be not an normal md5 hash of the filesize. There must be more.
If i do steps from OP the product code of my phone changes to XXXXXXXX.
Have used an Hex Editor and md5summer. Also tried WinMD5, same ****.
Click to expand...
Click to collapse
You dont read proper, plz read the steps carefully and you will create the correct md5 hash. I think your problem is that you did not open nv_data.bin.md5 after you generated it and deleted all lines beside the HASH line. This all is stated clearly in my steps, and you shouldent have any issue.
EDIT: The nv_data.bin.md5 you generated should be exactly 32bytes! else you did not follow my steps properly
ghostgull said:
Did this actually change the product code or did your Galaxy S replace the changed nv_data.bin file from the backup .nv_data.bak file?
The default action is to use the bak file to write a new nv_data.bin if the original is missing or corrupt. If your original .nv_data.bak still had the original code in it this could be what happened.
Click to expand...
Click to collapse
Nope, i wish it was that easy for me This works only if you backup up your rom with Clockworks for example.
Methyldioxide said:
You dont read proper, plz read the steps carefully and you will create the correct md5 hash. I think your problem is that you did not open nv_data.bin.md5 after you generated it and deleted all lines beside the HASH line. This all is stated clearly in my steps, and you shouldent have any issue.
EDIT: The nv_data.bin.md5 you generated should be exactly 32bytes! else you did not follow my steps properly
Click to expand...
Click to collapse
I´ve much knowledge about computers, linux (running a lenny root server) and so on. I´m not stupid. ;-)
In nv_data.bin.md5 there is only the hash code and its 32 bytes.
Will try hashing the file under ubuntu or debian and report back. Maybe windows is doing **** here.
This is very crazy.
My original files:
nv_data.bin -> DBT
hash in nv_data.bin.md5 -> 3012f56623f1a296c1ecd33ee8f0819b
Hash of nv_data.bin (windows, md5summer) -> 1e44ea7702c0e6b603c01ef0bf5508b0
Hash of nv_data.bin (ubuntu, md5sum) -> 1e44ea7702c0e6b603c01ef0bf5508b0
With my original Files Product Code of Phone is DBT.
If i use the md5 Hash generated by md5summer, put it in nv_data.bin.md5 Phone says XXXXXXXX.
Pretty strange.
Aery said:
This is very crazy.
My original files:
nv_data.bin -> DBT
hash in nv_data.bin.md5 -> 3012f56623f1a296c1ecd33ee8f0819b
Hash of nv_data.bin (windows, md5summer) -> 1e44ea7702c0e6b603c01ef0bf5508b0
Hash of nv_data.bin (ubuntu, md5sum) -> 1e44ea7702c0e6b603c01ef0bf5508b0
With my original Files Product Code of Phone is DBT.
If i use the md5 Hash generated by md5summer, put it in nv_data.bin.md5 Phone says XXXXXXXX.
Pretty strange.
Click to expand...
Click to collapse
I've been looking to correctly generate the .md5 file as well. As you can see Samsung uses more than just the file contents for generating the MD5 hash. An interesting thing is that when the phone recreates the nv_data.bin file based on the .nv_data.bak file it also regenerated the md5 file. The hash in this file was different from the one in the backup (original and backup were exactly the same nv_data with the same product code). So I suspect at least the timestamp of the file is also taken into account. I already tried diffenent scenario's but did not manage to generate a correct hash yet.
Aery said:
This is very crazy.
My original files:
nv_data.bin -> DBT
hash in nv_data.bin.md5 -> 3012f56623f1a296c1ecd33ee8f0819b
Hash of nv_data.bin (windows, md5summer) -> 1e44ea7702c0e6b603c01ef0bf5508b0
Hash of nv_data.bin (ubuntu, md5sum) -> 1e44ea7702c0e6b603c01ef0bf5508b0
With my original Files Product Code of Phone is DBT.
If i use the md5 Hash generated by md5summer, put it in nv_data.bin.md5 Phone says XXXXXXXX.
Pretty strange.
Click to expand...
Click to collapse
i was talking about this in my post....check ur imei too...
THANKS
Using the steps in 1st post, I could change my Product code from KOR to INU after updating to JPC thro kies.
Thanks.
Its not working. cant generate a correct md5 file.
Is the Imei stored in the nv_data.bin too????
Imei is not on that file, but /efs/imei/bt.txt if i recall that correctly.
And my fix does work great, if you cannot create a correct md5 then it's prolly cause you do it wrong. I bet if you send me your modified file and i make the md5 for you it will work.
Sent from my GT-I9000 using XDA App
At that location there's the bluetooth mac aaddress.
I think your product code reverted to the original because you damaged your nv_data.bin and nv_data.bin.md5 files and the phone recreated them from the backup.
If you don't have backups don't try this.
Sent from my GT-I9000 using XDA App
Methyldioxide said:
Hi,
So i coulden't wait and had to try out JPC firmware. Personally i didn't like it at all, so i went back to JM7. 1 thing i did not like is my product code changed from XEN to KOR.
And here is how to fix that easly:
I tested this on 2.1 cause i was on JM7 when i found this out, but im 99% sure this works with JPC also.
- First make sure you are ROOT and install a Terminal Emulator (can be found in the market)
- Now open the Terminal, enter ''su'' to gain root access
- Enter: cp /efs/nv_data.bin /sdcard/
- Connect you're SGS to the usb and download ''nv_data.bin'' to your computer
- Open ''nv_data.bin'' with notepad or wordpad and search for ''KOR'' change this to the product code matching your country. Im dutch, so mine is XEN. The line looks like this:
Code:
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿMP 0.800 ÿKOR GT-I9000HKDKOR
- Now simply save your changes.
- Download a md5 creator tool, i use MD5SUMMER
- Create a MD5 file using ''nv_data.bin" and save this as ''nv_data.bin.md5''
- Open ''nv_data.bin.md5'' with notepad and delete all the lines beside the line wich is similar to this one: 4ba37998243f14158884c5f464933398 (ofcourse your line of numbers is different ! ) Save the md5 file.
- Now your md5 file should be exactly 32bytes (this is the same size of the md5 file used by samsung, so please follow this step carefully)
- Connect your SGS with usb, upload ''nv_data.bin.md5'' and ''nv_data.bin'' to internal sdcard.
- Disconnect USB !
- Open Terminal Emulator and enter ''su''
- Now enter: cp /sdcard/nv_data.bin.md5 /efs/nv_data.bin.md5
cp /sdcard/nv_data.bin /efs/nv_data.bin
- Close terminal, Reboot Phone. And Voila!!! Product Code restored!!
I hope it's easy to follow my steps, it works guaranteed.
Click to expand...
Click to collapse
I did it!!!!
but, if I can , there's a small error,you 've to correct the red line ''nv_data.bin.md5'' in "nv_data.md5" .... this worked for me....
very helpfull guide, greetings mate
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
! C:\Users\user\Desktop\N7100XXDMB2_N7100OLBDMA4_XSE.zip: CRC failed in N7100XXDMB2_N7100OLBDMA4_N7100DXDLK5_HOME.tar.md5. The file is corrupt
That is what I get every time I try to extract the file. It gets to 99% and then errors out. I've redownloaded twice already. Am I doing something wrong?
Try using 7zip if you arent and tell us if it continues... also have you tried re-downloading? might just be a simple corruption?
Try another browser or download client to get the file
Sent from my GT-N7100 using Tapatalk 2
Userade said:
Try using 7zip if you arent and tell us if it continues... also have you tried re-downloading? might just be a simple corruption?
Click to expand...
Click to collapse
after try to extract with 7zip, it got extracted with md5 on it but still get the eror notice (corrupt file) on rar file. Then does this md5 file save to flash?
Rename the *.md5 you just extracted from the original *.zip to... *.md5.zip extension. Then extra the file you've just renamed again. If you can extract the contents to see files like recovery.img, then the md5 is safe to use. Else try a different browser...
You don't need to unzip it.
Check it's checksum and match it if it's available.
Also check the source.
You can also try to flash it directly.
It won't be flashed if it has a corrupt hash.
Sent from my GT-N7100 using xda app-developers app
Checksum hash miss match doesn't mean the data is corrupted because the hash is appended to the end of the tar file. If you can untar (or unzip if you prefer) the contents successfully, means you can rebuild the *.tar.md5 to flash with odin or just flash the extracted contents using mobile odin...:good:
Close antivirus while downloading as well extract.
Check log of antivirus, if there is reports regarding virus notice for zip file then select restore and try extract.
Sent from my GT-N7100 using xda premium
zhaolung said:
! C:\Users\user\Desktop\N7100XXDMB2_N7100OLBDMA4_XSE.zip: CRC failed in N7100XXDMB2_N7100OLBDMA4_N7100DXDLK5_HOME.tar.md5. The file is corrupt
That is what I get every time I try to extract the file. It gets to 99% and then errors out. I've redownloaded twice already. Am I doing something wrong?
Click to expand...
Click to collapse
You must download it again. Your zip is corrupted.
Sent from my GT-N7100 using xda premium
Possibly corrupted as at source.
Sent from my GT-N7100 using xda app-developers app
I want to update LineageOS and created a backup before attempting the update. Unfortunately the MD5 checksums of the the data partition files data.ext4.win000 and data.ext4.win001 don't check out. Even after several tries.
Is anyone else having this problem?
My TWRP Version is 3.1.1-0-0
seesawCharli said:
I want to update LineageOS and created a backup before attempting the update. Unfortunately the MD5 checksums of the the data partition files data.ext4.win000 and data.ext4.win001 don't check out. Even after several tries.
Is anyone else having this problem?
My TWRP Version is 3.1.1-0-0
Click to expand...
Click to collapse
Do you mean you created a backup successfully but then when you attempt restore the checksum It fails?
Or do you mean during backup?
IronRoo said:
Do you mean you created a backup successfully but then when you attempt restore the checksum It fails?
Or do you mean during backup?
Click to expand...
Click to collapse
The backup runs through without any errors.
When I tried to restore a backup about a month ago the checksum was incorrect and the restore failed. Therefore I reinstalled Lineage OS from scratch.
It was okay because the install was still quite fresh at that time anyway.
This time I wanted the verify the checksums in advance on my pc. The checksums of the boot.emmc.win and system.ext4.win files are fine.
Only the two data partition files fail to verify.
seesawCharli said:
The backup runs through without any errors.
When I tried to restore a backup about a month ago the checksum was incorrect and the restore failed. Therefore I reinstalled Lineage OS from scratch.
It was okay because the install was still quite fresh at that time anyway.
This time I wanted the verify the checksums in advance on my pc. The checksums of the boot.emmc.win and system.ext4.win files are fine.
Only the two data partition files fail to verify.
Click to expand...
Click to collapse
OK, I understand now. I ran a backup with TWRP 3.1.1-3 (tryout) & like you it ran fine. I can't really check md2 checksum at the moment as away on holiday & haven't found a good app that does md2 (tried Hash Droid but it just gives error msg even though permissions set correctly etc).
What are you using on PC to check?
IronRoo said:
OK, I understand now. I ran a backup with TWRP 3.1.1-3 (tryout) & like you it ran fine. I can't really check md2 checksum at the moment as away on holiday & haven't found a good app that does md2 (tried Hash Droid but it just gives error msg even though permissions set correctly etc).
What are you using on PC to check?
Click to expand...
Click to collapse
I'm using Hashtab which nicely integrates into the file property window in Windows.
But you could also use this command line utility which is already part of Windows:
Code:
CertUtil -hashfile C:\TEMP\MyDataFile.img MD5
seesawCharli said:
I'm using Hashtab which nicely integrates into the file property window in Windows.
But you could also use this command line utility which is already part of Windows:
Click to expand...
Click to collapse
OK, will have a look at it when get back to my PC. I've never tried it on PC. I have TWRP set to use SHA2 checksum. Have you tried that?
IronRoo said:
OK, will have a look at it when get back to my PC. I've never tried it on PC. I have TWRP set to use SHA2 checksum. Have you tried that?
Click to expand...
Click to collapse
No, I didn't know I could change the checksum algorithm. I'll try that!
Edit: I couldn't find a setting to change the checksum algorithm. Where can you set it? Maybe the option was introduced in your newer TWRP version?
seesawCharli said:
No, I didn't know I could change the checksum algorithm. I'll try that!
Edit: I couldn't find a setting to change the checksum algorithm. Where can you set it? Maybe the option was introduced in your newer TWRP version?
Click to expand...
Click to collapse
It's the last option in settings, it's partially obscured on my i9195 & I need to scroll up to see it fully (using ne0zone build from XDA thread)
IronRoo said:
It's the last option in settings, it's partially obscured on my i9195 & I need to scroll up to see it fully (using ne0zone build from XDA thread)
Click to expand...
Click to collapse
hmm, I don't seem to have as many settings as you. I don't need to scroll. I've attached a screenshot.
If the hash verification works for you I'll install your twrp version