Related
Download the normal unlock files before you do anything!!! You can find them in the forum.
KIES needs to be off...
1 - You need your phoned to be rooted
2 - Put your phone in usb debug mode
3 - Plug in the usb cable (don't use kies or storage mode)
4 - In the run window type CMD
5 - Go to the folder where you extracted the unlock files. Example c:\Generate Unlock Windows\Generate Unlock Windows
Type dir , you should see a file called adb.exe
6 - Type adb kill-server
Type adb shell
Type su (on your phone you should see the root explorer asking if you want to allow access, choose yes xD duh)
Type cp /efs/nv_data.bak /sdcard !!!IF this doesn't work type this!!!!----> cp /efs/.nv_data.bak /sdcard
Type cp /efs/nv_data.bak.md5 /sdcard !!!IF this doesn't work type this!!!!----> cp /efs/.nv_data.bak.md5 /sdcard
7 - Closed the window.
8 - The file with the code is now on your sdcard, start storage mode and copy the files to the c:\Generate Unlock Windows\Generate Unlock Windows folder (in windows xD)
Be sure that the nv_data.bak and nv_data.bak.md5 are in the same folder as sgux.exe
9 - Edit the Generate_Code.bat
Delete all the code and paste this:
@echo off
cls
echo ===============================================================
echo ===============================================================
echo Generate unlock code for any Samsung Galaxy S
echo ===============================================================
echo ===============================================================
echo Extract code
.\sgux .\.nv_data.bak
.\sgux .\nv_data.bak
echo ===============================================================
echo ===============================================================
echo Please donate to DagentooBoy for the script
echo Please donate to rbnet.it and marcopon for the SGUX utility used in the script
echo ===============================================================
echo ===============================================================
echo Script complete!
pause
10 - Your codes should appear! Save them and send them to you gmail account so you have them for life!
I TAKE NO CREDIT FOR THIS!!!! Just want to help!
Can you please Help me?
I flash & reflash several times, and still can´t resolve this.
I don't have any file with *bak* at this moment.
the files that I have:
# find /efs
find /efs
/efs
/efs/.android
/efs/.android/testAndroid1.bin
/efs/.android/testAndroid2.bin
/efs/.android/testAndroid3.bin
/efs/nv_data.bin
/efs/.imei
/efs/imei
/efs/imei/mps_code.dat
/efs/imei/bt.txt
/efs/imei/.nvmac.info
/efs/nv_data.bin.md5
/efs/.nv_state
/efs/nv_data.jpc
/efs/nv_data.jpc.md5
and de result to nv_data.bin:
E:\Generate Unlock Windows>sgux2 nv_data.bin
SGUX v0.92b (C) 2010 By Mark0 & rbnet
Samsung Galaxy Unlock code eXtractor
(based on info by rhcp0112345 & RazvanG)
Opening file <nv_data.bin>...
Searching code block...
Found.
Searching codes...
Network Control Key: 00000000
E:\Generate Unlock Windows>sgux2 nv_data.jpc
SGUX v0.92b (C) 2010 By Mark0 & rbnet
Samsung Galaxy Unlock code eXtractor
(based on info by rhcp0112345 & RazvanG)
Opening file <nv_data.jpc>...
Searching code block...
Found.
Searching codes...
Network Control Key: 00000000
I've tried to get the code with : .nv_data.bak, nv_data.bin, nv_jpc and bml3.bak. In each case, I got the code 00000000.
I found this in a forum hope this will help
quiron said:
I flash & reflash several times, and still can´t resolve this.
I don't have any file with *bak* at this moment.
the files that I have:
# find /efs
find /efs
/efs
/efs/.android
/efs/.android/testAndroid1.bin
/efs/.android/testAndroid2.bin
/efs/.android/testAndroid3.bin
/efs/nv_data.bin
/efs/.imei
/efs/imei
/efs/imei/mps_code.dat
/efs/imei/bt.txt
/efs/imei/.nvmac.info
/efs/nv_data.bin.md5
/efs/.nv_state
/efs/nv_data.jpc
/efs/nv_data.jpc.md5
and de result to nv_data.bin:
E:\Generate Unlock Windows>sgux2 nv_data.bin
SGUX v0.92b (C) 2010 By Mark0 & rbnet
Samsung Galaxy Unlock code eXtractor
(based on info by rhcp0112345 & RazvanG)
Opening file <nv_data.bin>...
Searching code block...
Found.
Searching codes...
Network Control Key: 00000000
E:\Generate Unlock Windows>sgux2 nv_data.jpc
SGUX v0.92b (C) 2010 By Mark0 & rbnet
Samsung Galaxy Unlock code eXtractor
(based on info by rhcp0112345 & RazvanG)
Opening file <nv_data.jpc>...
Searching code block...
Found.
Searching codes...
Network Control Key: 00000000
Click to expand...
Click to collapse
same result here, followed the procedure, ended up with network code 00000000. any help?
If you need help on unlocking a 2.2 device. Please contact me.
can anybody post a link to which normal unlock files are needed, there are too many unlock files in the forum
rhcp0112345 said:
If you need help on unlocking a 2.2 device. Please contact me.
Click to expand...
Click to collapse
Yes I need it, and I am certainly not the only one.
Can you publish a guide how to proceed ?
I did manage to get rid of this bloody unlocking problem after 9 hours of struggle. I followed the advice here:
http://forum.xda-developers.com/showthread.php?p=7946031#post7946031
I don't know how it worked, I don't care how it worked, its just that now i have a full working sgs with jp3 froyo software installed.
Next rom will definitely be official froyo, no more flic-flacs for me till then.
Fallback after a KOR productcode modification by firmware JPC
I've found a solution to my KOR problem after a JPC firmware upgrade :
History:
I've upgraded my SGS to JPC firmware (2.2). My phone product code has been changed to GT-I9000HKDKOR. Since my phone is simlocked, my local SIM (SFR in France) is not the same model than the phone (KOR), so it asked me an unlock code. I found no code to remove the simlock protection (sgux computed a 00000000 unlock code).
Solution I found :
- Downgrade the SGS to the firmware JM6 (2.1).
- Downloade the file /efs/nv_data.bin to your PC/LINUX/MAC (your phone need to be rooted !).
- Open it in a hexeditor -in fact I've used Windows' notepad++- and search for the "KOR" sequence. This sequence appears 2 times in the bin file. These are nearby each others.
- Change back the KOR sequence to your original product code (this can be found in regedit CURRENT USER / Software / Samsung / Kies / DeviceDB / [a number] / ProductCode). For my personal case, it is a SFR (France) phone, my product code is GT-I9000HKDSFR and a few chars before change KOR by SFR (or whatever your op. code is).
- Then you have to compute a md5sum on the modified nv_data.bin and store the md5 in a file called nv_data.bin.md5. Make sure your md5 file is exactly 32 bytes long, there is no CR/LF at the end of the line. md5sum is available for any plateform, for myself I did it on my Linux box which is my SAN.
- Next step : push back these 2 files in your /efs/ directory and reboot.
To make sure nothing is altered during the reboot process, I've removed the battery to switch off the phone. At the next reboot, no more SIM unlock code request. I've been able to place a call, my phone is back to life !
Can someone takes some time to do this trick on a 2.2 froyo JPC firmware ?
Hope this will help others...
gouroufr2000 said:
I've found a solution to my KOR problem after a JPC firmware upgrade :
History:
I've upgraded my SGS to JPC firmware (2.2). My phone product code has been changed to GT-I9000HKDKOR. Since my phone is simlocked, my local SIM (SFR in France) is not the same model than the phone (KOR), so it asked me an unlock code. I found no code to remove the simlock protection (sgux computed a 00000000 unlock code).
Solution I found :
- Downgrade the SGS to the firmware JM6 (2.1).
- Downloade the file /efs/nv_data.bin to your PC/LINUX/MAC (your phone need to be rooted !).
- Open it in a hexeditor -in fact I've used Windows' notepad++- and search for the "KOR" sequence. This sequence appears 2 times in the bin file. These are nearby each others.
- Change back the KOR sequence to your original product code (this can be found in regedit CURRENT USER / Software / Samsung / Kies / DeviceDB / [a number] / ProductCode). For my personal case, it is a SFR (France) phone, my product code is GT-I9000HKDSFR and a few chars before change KOR by SFR (or whatever your op. code is).
- Then you have to compute a md5sum on the modified nv_data.bin and store the md5 in a file called nv_data.bin.md5. Make sure your md5 file is exactly 32 bytes long, there is no CR/LF at the end of the line. md5sum is available for any plateform, for myself I did it on my Linux box which is my SAN.
- Next step : push back these 2 files in your /efs/ directory and reboot.
To make sure nothing is altered during the reboot process, I've removed the battery to switch off the phone. At the next reboot, no more SIM unlock code request. I've been able to place a call, my phone is back to life !
Can someone takes some time to do this trick on a 2.2 froyo JPC firmware ?
Hope this will help others...
Click to expand...
Click to collapse
You sir are brilliant... back to O2U here! ) I only needed to change one key entry as could find only the one KOR in my nv_data.bin... but otherwise... perfect! )
Thank you SOOOO much... had started worrying that I'd not get my product code back!
It also means that a simlocked phone can be used with another SIM by modifying the same way the nv_data.bin...
Anyway I wont update this phone to JPC. I'll await the next one... JPD seems to be online but no infos yet on the status of this firmware.
in which line did you find the KOR?
i cant find it? >_<
Greg82uk said:
You sir are brilliant... back to O2U here! ) I only needed to change one key entry as could find only the one KOR in my nv_data.bin... but otherwise... perfect! )
Thank you SOOOO much... had started worrying that I'd not get my product code back!
Click to expand...
Click to collapse
I'm clueless here, would you mind posting a step by step including the software used?
gouroufr2000 said:
I've found a solution to my KOR problem after a JPC firmware upgrade :
History:
I've upgraded my SGS to JPC firmware (2.2). My phone product code has been changed to GT-I9000HKDKOR. Since my phone is simlocked, my local SIM (SFR in France) is not the same model than the phone (KOR), so it asked me an unlock code. I found no code to remove the simlock protection (sgux computed a 00000000 unlock code).
Solution I found :
- Downgrade the SGS to the firmware JM6 (2.1).
- Downloade the file /efs/nv_data.bin to your PC/LINUX/MAC (your phone need to be rooted !).
- Open it in a hexeditor -in fact I've used Windows' notepad++- and search for the "KOR" sequence. This sequence appears 2 times in the bin file. These are nearby each others.
- Change back the KOR sequence to your original product code (this can be found in regedit CURRENT USER / Software / Samsung / Kies / DeviceDB / [a number] / ProductCode). For my personal case, it is a SFR (France) phone, my product code is GT-I9000HKDSFR and a few chars before change KOR by SFR (or whatever your op. code is).
- Then you have to compute a md5sum on the modified nv_data.bin and store the md5 in a file called nv_data.bin.md5. Make sure your md5 file is exactly 32 bytes long, there is no CR/LF at the end of the line. md5sum is available for any plateform, for myself I did it on my Linux box which is my SAN.
- Next step : push back these 2 files in your /efs/ directory and reboot.
To make sure nothing is altered during the reboot process, I've removed the battery to switch off the phone. At the next reboot, no more SIM unlock code request. I've been able to place a call, my phone is back to life !
Can someone takes some time to do this trick on a 2.2 froyo JPC firmware ?
Hope this will help others...
Click to expand...
Click to collapse
Looks promising!
Does it have to be JM6 or can JM7 work as well ?
Can anyone with JPC and a locked phone try this and report if it works ?
If we go back to JM6 do the editing and fix the product code then back it up on the PC, update to JPC and push this back to the phone this should work right ?
Any news if its possible to restore the IMEI ?
Ok I'm stupid and I can't make a md5 file of 32 bytes with md5summer for windows, somebody can help me?
edit de file with notepad and delete the 1st 3 lines and the count 32 bytes and delete all the rest.
I tried with JM7 with CSC_I9000TMNJM1 and there is no KOR sequence in nv_data.bin FILE. instead was already TMN, but still asking me for de unlock code.
I tried with JPC and still don't work .
quiron said:
I tried with JM7 with CSC_I9000TMNJM1 and there is no KOR sequence in nv_data.bin FILE. instead was already TMN, but still asking me for de unlock code.
I tried with JPC and still don't work .
Click to expand...
Click to collapse
It means your phone is configured as TMN (dont know which country it is) but if it asks you for unlock code => your SIM is not TMN.
Change TMN to whatever your SIM is... Check in regedit for a history. Anyway downgrade to a previous firmware because JPC is suspected of breaking the nv_data.bin
I don't know if this trick works with another firmware, but theorically it should works the same way...
Nb: do not delete any line in your nv_data.bin ! This is a stupid remark, it can brick your phone.
the solution to 00000000 unlock code
finaly the solution to 00000000 unlock code
http://forum.xda-developers.com/showpost.php?p=7957950&postcount=10
or
http://forum.xda-developers.com/showthread.php?p=7957950&posted=1#post7957950
works to me.
for those of u having a very very hard time trying to unlock the phone after flashing the JPC rom , u must do this :
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
Now your Phone shouldn´t ask for a Code.
after that u can unlock ur phone with the methods shown in this thread . even the unlock android apk works ! very good job developers ty. BAD BAD samsung setting us such a trap.
For me this method didn't work. following exact steps in (b), still asking Network Code, 00000000 was the extracted code but didn't work though.
So after 2 days of struggling this is what I did:
Note that some users warned that if the bak files are corrupted the system will recreate empty files, probably losing IMEI, but this was not my case
1. Flash by Odin to JM7 (I don't think the version matters as long is 2.1)
2. at this time Product code change back from KOR to original ORO, but still asking code
3. root
4. moving back /efs files active to bak, the system will recreate new ones due to moving, so no more active files
mv nv_data.bin .nv_data.bak
mv nv_data.bin.md5 .nv_data.bak.md5
at this time I can see a new nv_data.bin with a smaller size
5. reboot
now working, not asking code
Thanks for the Thread... Might just need it in a few hours
adi_g_s said:
For me this method didn't work. following exact steps in (b), still asking Network Code, 00000000 was the extracted code but didn't work though.
So after 2 days of struggling this is what I did:
Note that some users warned that if the bak files are corrupted the system will recreate empty files, probably losing IMEI, but this was not my case
1. Flash by Odin to JM7 (I don't think the version matters as long is 2.1)
2. at this time Product code change back from KOR to original ORO, but still asking code
3. root
4. moving back /efs files active to bak, the system will recreate new ones due to moving, so no more active files
mv nv_data.bin .nv_data.bak
mv nv_data.bin.md5 .nv_data.bak.md5
at this time I can see a new nv_data.bin with a smaller size
5. reboot
now working, not asking code
Click to expand...
Click to collapse
and did you manage to get the JPC back and unlocked then? I have managed to fix the SIM Network Unlock code problem in a similar way, but using a MoDaCo modded froyo ROM, based on JP3. Now I am considering getting back to JPC, because I saw some nice things in there, but afraid I might get into the same problem. How can we fix this problem and STILL be on JPC?
NOTE: I have tried to use the .apk to get the unlock code now in JP3 rom and with no network unlock and the result is:
Unlock code: NULL
Unfreeze code: NULL
Probably that means that my sgs is unlocked, but how can we find the unlock code, so we can use it in JPC after flash?
ionutz6 said:
and did you manage to get the JPC back and unlocked then? I have managed to fix the SIM Network Unlock code problem in a similar way, but using a MoDaCo modded froyo ROM, based on JP3. Now I am considering getting back to JPC, because I saw some nice things in there, but afraid I might get into the same problem. How can we fix this problem and STILL be on JPC?
Click to expand...
Click to collapse
I think you can use JPC as long as you keep it rooted. If it gets locked, you can do the above procedure (adb shell) and restore the nv_data files
If you need to know how to flash it already rooted, check the "JPC root inside" thread or the "Doc's RomMod JPC" thread. I'm going to test this myself tonight or tomorrow
Cheers m8s
Phk
Phk said:
I think you can use JPC as long as you keep it rooted. If it gets locked, you can do the above procedure (adb shell) and restore the nv_data files
If you need to know how to flash it already rooted, check the "JPC root inside" thread or the "Doc's RomMod JPC" thread. I'm going to test this myself tonight or tomorrow
Cheers m8s
Phk
Click to expand...
Click to collapse
I have tried pretty much ALL things found here in XDA related to JPC last night, in the 10-hour period when I was struggling to bring my sgs back to life. I have upgraded to JPC, rooted it, tried to use several methods to find the unlock code, tried the FAQ#7 from the HOWTO thread, did 1000 other things, nothing worked, Unlock code still present. Perhaps I missed some steps although I don;t think so. I've also downgraded to 2.1 JM6 and tried to get the unlock code here, no go. Still SIM Unlock Code required. Finally I have solved it by upgrading it to a froyo modded rom from modaco, already rooted and then applying the FAQ#7 instructions. Now I am in froyo JP3 (the modded rom from modaco) and pretty scared to try anything else, although I would very much like to get to JPC, since I saw some pretty nice enhancements.
Any thoughts based on this painful story?
adi_g_s said:
For me this method didn't work. following exact steps in (b), still asking Network Code, 00000000 was the extracted code but didn't work though.
So after 2 days of struggling this is what I did:
Note that some users warned that if the bak files are corrupted the system will recreate empty files, probably losing IMEI, but this was not my case
1. Flash by Odin to JM7 (I don't think the version matters as long is 2.1)
2. at this time Product code change back from KOR to original ORO, but still asking code
3. root
4. moving back /efs files active to bak, the system will recreate new ones due to moving, so no more active files
mv nv_data.bin .nv_data.bak
mv nv_data.bin.md5 .nv_data.bak.md5
at this time I can see a new nv_data.bin with a smaller size
5. reboot
now working, not asking code
Click to expand...
Click to collapse
so should i understand that you are now on JM7? How do you get back to JPC?
ionutz6 said:
and did you manage to get the JPC back and unlocked then? I have managed to fix the SIM Network Unlock code problem in a similar way, but using a MoDaCo modded froyo ROM, based on JP3. Now I am considering getting back to JPC, because I saw some nice things in there, but afraid I might get into the same problem. How can we fix this problem and STILL be on JPC??
Click to expand...
Click to collapse
yes now i am on jpc ,and if it decides to ask for a code i have the codes now.
ionutz6 said:
so should i understand that you are now on JM7? How do you get back to JPC?
Click to expand...
Click to collapse
yes I'm on JM7, now the unlock.apk gives me Unlock Code:NULL
I'm hoping that my phone is unlocked now, so Froyo will not ask the code anymore
but IMEI was rewritten by with value 004999... and I have trouble with Market, cannot download.
how to recover my IMEI now?
Many many many thanks
adi_g_s said:
For me this method didn't work. following exact steps in (b), still asking Network Code, 00000000 was the extracted code but didn't work though.
So after 2 days of struggling this is what I did:
Note that some users warned that if the bak files are corrupted the system will recreate empty files, probably losing IMEI, but this was not my case
1. Flash by Odin to JM7 (I don't think the version matters as long is 2.1)
2. at this time Product code change back from KOR to original ORO, but still asking code
3. root
4. moving back /efs files active to bak, the system will recreate new ones due to moving, so no more active files
mv nv_data.bin .nv_data.bak
mv nv_data.bin.md5 .nv_data.bak.md5
at this time I can see a new nv_data.bin with a smaller size
5. reboot
now working, not asking code
Click to expand...
Click to collapse
Finaly I have my phone back. just had to do something else.
I have to edit the file efs/imei/mps_code.dat and change de "KOR" to "TMN". Then I rename the files as mentioned, and my phone came to life.
adi_g_s you're a hero.
adi_g_s said:
yes I'm on JM7, now the unlock.apk gives me Unlock Code:NULL
I'm hoping that my phone is unlocked now, so Froyo will not ask the code anymore
but IMEI was rewritten by with value 004999... and I have trouble with Market, cannot download.
how to recover my IMEI now?
Click to expand...
Click to collapse
I have the exact same behaviour, with Unlock code: NULL, IMEi starting with 004999.. etc. The only thing is that download from market is working ok.
would you care to upgrade now to JPC and see if it requests the unlock code again? I don;t believe that the fact that it looks unlocked now will mean after installing JPC you will have the same condition. Mine was unlocked before trying JPC, as far as I know.
man, i am confused...
I want to give the method by adi_g_s a try but im afraid if I reflash back to JPC it might forever lock my phone.. the unlock APK also sees it as null/null. Right now im with JPC and its unlocked..
adi_g_s said:
For me this method didn't work. following exact steps in (b), still asking Network Code, 00000000 was the extracted code but didn't work though.
So after 2 days of struggling this is what I did:
Note that some users warned that if the bak files are corrupted the system will recreate empty files, probably losing IMEI, but this was not my case
1. Flash by Odin to JM7 (I don't think the version matters as long is 2.1)
2. at this time Product code change back from KOR to original ORO, but still asking code
3. root
4. moving back /efs files active to bak, the system will recreate new ones due to moving, so no more active files
mv nv_data.bin .nv_data.bak
mv nv_data.bin.md5 .nv_data.bak.md5
at this time I can see a new nv_data.bin with a smaller size
5. reboot
now working, not asking code
Click to expand...
Click to collapse
If i flash back to 2.1 and I still get the KOR product code.. I wont be doing the other extra steps right ?
and If i flash back to JPC, should I expect my phone to be asking for an unlock code again ?
EDIT:
and I made a backup of my:
nv_data.bak
nv_data.bin
nv_data.bin.md5
nv_data.jpc
nv_data.jpc.md5
all of these are from POST JPC, so I guess im ready to screw around and flash to JM7 and see if i can get my product code back and if not I can just relfash to JPC again and restore these files so it wont be asking for an unlock code anymore right ?
adi_g_s said:
yes I'm on JM7, now the unlock.apk gives me Unlock Code:NULL
I'm hoping that my phone is unlocked now, so Froyo will not ask the code anymore
but IMEI was rewritten by with value 004999... and I have trouble with Market, cannot download.
how to recover my IMEI now?
Click to expand...
Click to collapse
There is a file in /efs/imei/ folder that contains the imei. if you have a original box perhaps you find there imei written, and that way you can try editing that file and place your original IMEI.
********NOTE*********
i have included a few of the tools you will need as attachments to this post. I will not take any credit for these programs as i was not the developer for them... these people work too hard to have anyone steal their credit... please give credit where credit is due!Your nv_data.bin file and its matching nv_data.bin.md5 files are located on your phone in /efs/
All references that i make to "sd card" or "/sdcard/" refer to your phone's internal SD Card, not an external SD card that you may have installed.
I have created a windows batch file that you can run and it will extract your entire /efs/ folder from your phone to your PC. I am currently working on the batch script to move the edited nv_data.bin files back to your/efs/ folder and do the other adb stuff.
attached is the EFS Extractor.zip file that contains the ADB files and the batch script.
The product code for your AT&T Captivate is: SGH-I897ZKAATT
WARNING… I AM NOT RESPONSIBLE IF YOU BREAK YOUR PHONE FOLLOWING ANY OF THESE INSTRUCTIONS
The Attached EFS Extractor.zip file contains the necessary adb file and a couple batch files. "retrieve efs.bat" copies your entire /efs/ folder to your PC in a folder called /efs_bkup/ in the directory where you unzipped the file and ran the batch program from. The file "update nv_data.bat" takes your edited nv_data.bin file from the root directory where you ran the .bat file from and places in in your phone's /efs/ folder and removes the old copies from your phone... when it is done, it will power cycle your phone.
To fix your nv_data.bin, you will have to have access to the following tools:
A hex editor (search google for hex editors, they have tons of them that are free… I use one called HexEdit and i have it attached)
GalaxyS_One-Click_Root_All_Models (available via XDA-Developers... attached)
ADB (Android Debugging Bridge) This is available by getting the Android SDK at the Android Developers Website (http://developer.android.com/sdk/index.html) or if you downloaded the Galaxy S One Click Root, it is in the directory where you unzipped the files.
BusyBox – Search the google market for “BusyBox”. It will appear and will be the free one from stericson (i have included the .apk as an attachement)
Odin One-Click Downloader (available from XDA)… make sure you get the correct one. There are 2 versions. If you batch number is 1008 then you need the one with the 3-button fix, if you batch number is greater than 1008 then you should need the regular one. Your batch number is written on the sticker on your phone under your battery on the left side right under the words “S/N” where your serial number is listed.
Samsung Kies Mini (gotten from Samsung website)
Download the attached EFS Extractor .zip file. It contains everything you need to copy your /efs/ folder to your PC
Now for what you need to do to get your phone’s nv_data.bin back to normal:
Flash back to stock and then do a master clear using Odin One Click
put phone into USB debugging mode and also check the setting to "stay awake"
connect phone to PC and root and install busybox
extract the attached EFS Extractor.zip file and run the "retrieve efs.bat" file. This will copy your entire /efs/ folder from your phone to your PC in a direcotry called ./efs_bkup/
Using the Hex Editor, edit the file ./efs_bkup/efs/nv_data.bin on your PC to have the correct product code SGH-I897ZKAATT. do an ASCII search for "SGH" to locate the line in the file that contains your product key. then save the edited file to ./nv_data.bin (the root directory where you extracted your ZIP file to on your PC)
run the file "update nv_data.bat" to copy your corrected nv_data.bin to your phone's efs folder and chown it and reboot your phone
change USB Settings on phone back to Kies then open Kies Mini and connect phone.
you should now be able to connect to Kies Mini and not have unregistered device... now would be a good time to back_up your /EFS/ folder... you can now either do Odin One-Click and a master clear, or flash a different rom. You should do Odin if you want to use Kies to get updates to be 100% stock to remove your root and busybox.
The general overview what what you need to do is this for those of you that want to know and/or use other tools to do this
Copy your /efs/nv_data.bin file from your phone to your PC
Use a hexeditor to modify the line in the nv_data.bin file that contains the productcode to contain your correct product code
delete any nv_data.* files from your /efs/ folder on your phone
copy the corrected nv_data.bin file from your PC to your /efs/ folder on your phone
busybox chown 1001:1001 /efs/nv_data.bin
reboot phone
Done!
Now, when you backup your /efs/ folder to your PC you may see files like nv_data.bak and nv_data.bak.md5. Using a hexeditor, open the nv_data.bak file and look at the line that has the product code (ASCII values starting wtih SGH)... if the product code in the .bak file is correct, then delete the nv_data.bin and nv_data.bin.md5 from your /efs/ folder on your phone and reboot your phone. Your phone should then create new .bin and .bin.md5 files from the .bak and .bak.md5 files that will have the proper productcode. You can also optionally rename the .bak and .bak.md5 files on your PC to be .bin and .bin.md5 and copy them to your /efs/ folder on your phone.
You can view what Kies is reading your productcode as by opening your windows registry editor Start>Run>regedit[enter]
Connect phone to PC in Kies(Firmware) mode
Navigate to HKEY_CURRENT_USER/Software/Samsung/KiesMini/FUS
Look at the key "PRODUCTKEY" and what it's value is... if it is correct, then you are good. If not, then something went wrong somewhere.
If you have issues please post the issues you are having and I will update as necessary.
Here is a link to a different thread that contains a program and instructions for restoring your unlock codes if that is what you are trying to do. The .jar (java program is written in frech, but it only asks for the codes you want to use for your unlock codes... i did not make this program so I cannot help you with it.
http://forum.xda-developers.com/showpost.php?p=8983897&postcount=103
Tried to trim this down a little as there are a ton of steps, let me know if any of this is incorrect.
1. Flash back to stock rom, and do a master clear using the Odin3 One-Click Downloader by designgears
2. Root using one-click-root and install busybox, turn on usb development mode + stay awake, and connect to your PC.
3. Open a command prompt window and navigate to the directory where you extracted the one-click-root. Run the following commands:
a. adb shell
b. su
c. cp /efs/nv_data.bin /sdcard/nv_data.bin
d. cp /efs/nv_data.bin /sdcard/nv_data.bin.copy (incase there is a problem)
e. rm /efs/nv_data.*
4. Exit your adb.exe window, mount your phone on your PC and navigate to the internal card. Edit the nv_data.bin with a hexeditor (bpsoft.com) and search (ascii) for "SGH-" (without the quotes)
5. It may be something like SGH-I897ZKATOR or SGH-I897ZKATMB. You need to change this to SGH-I897ZKAATT then save the file, and unmount your phone.
6. Disconnect usb data cable from pc to phone, re-enable usb development mode + stay awake, reconnect.
7. Open a command prompt window and navigate to the directory where you extracted the one-click-root. Run the following commands:
a. adb shell
b. su
c. cp /sdcard/nv_data.bin /efs/nv_data.bin
d. busybox chown 1001:1001 /efs/nv_data.bin
8. Power cycle
Hi hansomni. l've been down this road. Were you successfull with creating Nv_data.bak this way and restoring with that. For example editing nv_data.bak and making a corresponding md5 file and only placing those files in your efs folder and restarting your phone
I had problems creating this file. i would always get an incorrect iemi. This is why i recommend using nv_data repair.zip posted in the tmo vibrant unlock thread not only can you recreate the correct product code but also fix the fffffffff for unlock code.
Have you checked this outhttp://forum.xda-developers.com/showpost.php?p=8983897&postcount=103
mattbeau said:
Hi hansomni. l've been down this road. Were you successfull with creating Nv_data.bak this way and restoring with that. For example editing nv_data.bak and making a corresponding md5 file and only placing those files in your efs folder and restarting your phone
I had problems creating this file. i would always get an incorrect iemi. This is why i recommend using nv_data repair.zip posted in the tmo vibrant unlock thread not only can you recreate the correct product code but also fix the fffffffff for unlock code.
Have you checked this outhttp://forum.xda-developers.com/showpost.php?p=8983897&postcount=103
Click to expand...
Click to collapse
yeah... i have been successful using the steps i outlined... like i said in the original post, this is only to get your product code fixed... i don;t have an unlocked phone so i don't know if that program works... i did use it to check it out, but it is written in frech or something and it never copied the "patched" nv_data files back to my phone... i had to do it manually and still the product code from the created files were wrong. Others say that they have had success using it, but i never did. I took a buch of stuff from a buch of posts on this site to compile the guide here for restoring product codes only.
the .bak files are your backup files that get generated sometimes... usually those files have your correct unlock codes and productcode... to restore them, just delete the non .bak files and remove the .bak extension from the backups... then copy them to your /efs/ folder and powercycle and you should be good. you should keep all your orignial files from your /efs/ folder in a safe place though so you have them to fall back on if you need to. I have never had the .bak files in my /efs/ folder so i haven't ever been that lucky.
devz3r0 said:
Tried to trim this down a little as there are a ton of steps, let me know if any of this is incorrect.
1. Flash back to stock rom, and do a master clear using the Odin3 One-Click Downloader by designgears
2. Root using one-click-root and install busybox, turn on usb development mode + stay awake, and connect to your PC.
3. Open a command prompt window and navigate to the directory where you extracted the one-click-root. Run the following commands:
a. adb shell
b. su
c. cp /efs/nv_data.bin /sdcard/nv_data.bin
d. cp /efs/nv_data.bin /sdcard/nv_data.bin.copy (incase there is a problem)
e. rm /efs/nv_data.*
4. Exit your adb.exe window, mount your phone on your PC and navigate to the internal card. Edit the nv_data.bin with a hexeditor (bpsoft.com) and search (ascii) for "SGH-" (without the quotes)
5. It may be something like SGH-I897ZKATOR or SGH-I897ZKATMB. You need to change this to SGH-I897ZKAATT then save the file, and unmount your phone.
6. Disconnect usb data cable from pc to phone, re-enable usb development mode + stay awake, reconnect.
7. Open a command prompt window and navigate to the directory where you extracted the one-click-root. Run the following commands:
a. adb shell
b. su
c. cp /sdcard/nv_data.bin /efs/nv_data.bin
d. busybox chown 1001:1001 /efs/nv_data.bin
8. Power cycle
Click to expand...
Click to collapse
Yeah, looking at it quickly it looks like all the instructions are correct... maybe abbreviated too much... Thanks for that... i will update with instuctions similar.... i have to remember that there are those folks that have never used adb or know what it is. I will credit you in my update tomorrow. I am used to where i work we have people that use computers that don;t know how to power them on and off so they just leave them on all the time... i have to be very specific on my instructions that i tell them so they can understand... a two second task becomes an all-day event. Just something i am used to doing.
I will be working on a dos script (.bat) file that will do most of the adb stuff so then the users only need a few things to do and just let the scripts take care of the rest.
hansonmi said:
yeah... i have been successful using the steps i outlined... like i said in the original post, this is only to get your product code fixed... i don;t have an unlocked phone so i don't know if that program works... i did use it to check it out, but it is written in frech or something and it never copied the "patched" nv_data files back to my phone... i had to do it manually and still the product code from the created files were wrong. Others say that they have had success using it, but i never did. I took a buch of stuff from a buch of posts on this site to compile the guide here for restoring product codes only.
the .bak files are your backup files that get greated sometimes... usually those files have your correct unlock codes and productcode... to restore them, just delete the non .bak files and remove the .bak extension from the backups... then copy them to your /efs/ folder and powercycle and you should be good. you should keep all your orignial files from your /efs/ folder in a safe place though so you have them to fall back on if you need to.
Click to expand...
Click to collapse
You dont even need to change the extenaion of those files if you power cycle your phone with just .Bak files. Your phone will recreate the nv_data.bin and md5 from those .Bak files and create a log file
Yeah i know the java program is in french. But its only asking you what two codes you want to use for unlocking your phone ( ahh google translate)
And yes the first time i tried the program i had trouble too. I think it helps if you have a good busybox version.
Believe me the easier you can make it the better it will be for everyone. Now if we could just get everyone to back up that folder before flashing anything we wouldnt even need to go down that road. Thanks for your help in this. Ill leave this thread alone now sorry if im intruding. Pm me if you need any help
mattbeau said:
You dont even need to change the extenaion of those files if you power cycle your phone with just .Bak files. Your phone will recreate the nv_data.bin and md5 from those .Bak files and create a log file
Yeah i know the java program is in french. But its only asking you what two codes you want to use for unlocking your phone ( ahh google translate)
And yes the first time i tried the program i had trouble too. I think it helps if you have a good busybox version.
Believe me the easier you can make it the better it will be for everyone. Now if we could just get everyone to back up that folder before flashing anything we wouldnt even need to go down that road. Thanks for your help in this. Ill leave this thread alone now sorry if im intruding. Pm me if you need any help
Click to expand...
Click to collapse
Yeah... the problem is that not everyone knew to do it before flashing as a lot of the ROM pages don't say it (I was one of them that never knew about it)... i knew what the java was saying but since i don't have an unlocked phone, i had no way of testing it to see if it worked for me or not... and on top of that it didn't work with restoring my productcode (i know that becuase i couldn't use Kies until i did things manually)... I tell people to rename the files, becuse i am assuming they copy the contents of their /efs/ folder to a PC or something... then they just have to delete the nv_data files from /efs/ on their phone, and rename the .bak files on their PC and copy them back to their phone's /efs/ so they still have a copy of their original files saved on their PC... plus i don't like relying on the phone doing the renaming because if it doesn't no one will know what went wrong...
Working on Windows Batch (.bat) script
I will be working on doing a windows .bat script that will do most of the dirty work for you... it may take a couple days because where i work the end of the year is the busiest time for me and i don't have a lot of time between work during the week.
I will make the script an attachment and will hopefully be able to zip with the abd files to make life a little easier for everyone.
Thanks for the input everyone.
What line
Could someone that has successfully done this post what line in the hex file the product code is found on. All I get is string not found??? Thanks
Worked great, followed steps exactly as outlined didn't have any problems. Thanks again for this, I've been wanting to have a proper backup of efs folder with correct product code, but could never change it back.
Slowazz28 said:
Could someone that has successfully done this post what line in the hex file the product code is found on. All I get is string not found??? Thanks
Click to expand...
Click to collapse
I used hexedit, and if the line number is in first column it begins on line 188010. I did notice when searching a second time to get line number, that I had to have sgh- in all caps, and once i got string not found, I closed program reopened and searched again using caps (SGH-) it worked several times. Hopes this helps.
Big thanks for posting this.
I'll give this a shot prior to flashing Axura 2.5.
Thanks hansonmi! I got it updated with kies. I done it a lil diffent using root explorer to move files around and used hexeditor to edit files and root explorer to copy back.
great guide.
wish this would have been around the first time i ran into this problem as it was a headache when it happened and the threads and advice on fixing were so fragmented within the forum threads.
The only thing i did differently was that i didn't use ADB on a pc at all during the process (I completed the process using both Root Explorer and Terminal Emulator on my phone and copying files to pc via mounting the phone and its storage as disk drives).
(PS before doing any of this i backup up my efs folder first to my external SD using root explorer and then to my pc via mounting the phones storage)
1. I had already copied my nv_data.bin file to external SD when backing up EFS folder.
2. Connected to pc via usb and mounted for storage (with debugging on)
3. copid nv_data to pc
4. used PsPad to edit the nv_data file in accordance with previous instruction in this thread. (I highly recommend PSpad as a hex editor. Its nice that you can switch back and forth between hex and text editor views) See PS in the end for using PSpad hex editor to find the line you need to edit. That seemed to be the only thing that needed clarified.
5. copy nv_data.bin back to the root directory of external sd
6. use root explorer to move newly edited nv_data from external sd back to original EFS folder.
7. Delete the nv_data..bin.md5 file..i left the backup from efs folder
7. delete any nv_data.baks from efs folder
8. Now the use of Termainl Emulator (download from market). Busybox must be installed as well
9. Open terminal emulator execute following commands:
SU
busybox chown 1001:1001 /efs/nv_data.bin
reboot
(reference to step 4 using hex editor)
PS - These are the steps for editing the hex code and starting with step first step assuming you have copied the nv_data.bin to your PC
1. Open PsPad (or other hex editor)
2. Open nv_data.bin in hex editor mode
3. Go to line 188000 (using search modes you will likely have to enter $00188000 or 00188000) Using PsPad you would do the following:
Select SEARCH from top tool bar. Select GOTO LINE.......then enter $00188000
4. You will see yTMB....SGH_i897ZKATMB (or yTOR....SGH-ZKATOR).
5. Replace that first TMB or TOR with ATT then replace ZKATMB or ZKAATOR with KZAATT
6. Save
7. Now you should have a proper nv_data.bin
HBeezy said:
I used hexedit, and if the line number is in first column it begins on line 188010. I did notice when searching a second time to get line number, that I had to have sgh- in all caps, and once i got string not found, I closed program reopened and searched again using caps (SGH-) it worked several times. Hopes this helps.
Click to expand...
Click to collapse
Ok that worked great except when I get to that line it says productcode several times then a bunch of x's then 11 0's but no SGH- so not sure where to put it in at. The 0's start on line 1880f0 and end on line 188100 ??? Appreciate the help
Slowazz28 said:
Ok that worked great except when I get to that line it says productcode several times then a bunch of x's then 11 0's but no SGH- so not sure where to put it in at. The 0's start on line 1880f0 and end on line 188100 ??? Appreciate the help
Click to expand...
Click to collapse
what hex editor are you using?
i recommend downloading the free PSpad Hex/Txt editor.
1. Open your nv_data file using FILE then OPEN IN HEX EDIT
2. use SEARCH from toolbar commands....GOTO LINE from search menu....options after opening in hex edit mode
3. then search for $00188000
you should see the line you need to edit.
The nice thing about PSPAD is that you can also open the binary file in a Text mode. If you have trouble finding it in the hex editor mode try the following.
1. open PSpad. Goto FILE then OPEN (vs. open in hex edit). This will open in a text editor view/mode.
2. goto SEARCH and select INCREMENTAL SEARCH
3. type SGH and search
(you could also do all the hex editing without moving files to pc if you wanted using HEX EDITOR from market...though for most the PC hex editors might be easier)
if you want to use the android hex editor app to do all the editing on your phone...do the following:
THERE ARE 3 Total Lines you will need to edit:
00188008
00188010
00188020
1. Use Root Explorer to copy nv_data.bin from efs folder to the root directory on your external sd.
2. Use Hex Editor App to open the copy from your external SD.
3. One Open click the capacitive menu button and select jump to address
4. Enter 0188008
This will take you to line 00188008
5. Edit the last or 8th Block so it reads 41.
6. Enter 0188010
7. This will take you to line 00188010. Edit the first two blocks of this line. Replace the #'s so that both of the first two blocks contain 54. (look to the text at the right of screen the first two letter should have changed to TT. To recap you need to edit Block 1 and Block 2 of line 0018010:
LINE 0018010
Block 1 = 54
Block 2 = 54
(text @ right should now read TT....SG)
8. Now look down to line 0018020 and look at the line. If you at the line and to the far right text you will see ATOR or ATMB if your nv_is messed up.
9. You may need to edit blocks 2-4. They should read as follows:
LINE 00188020
Block 2 = 41
Block 3 = 54
Block 4 = 54
(the text at the right of your screen should now read AATT....)
10. Save the file and move it back to efs using root explorer.
PS: Here are how the following lines should read (the ones in bold are the only ones you have to edit as line 00188018 will already be correct):
00188008|2e|34|00|00|00|00|ff|41|.4....A
00188010|54|54|00|00|00|00|53|47|TT....SG
00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK
00188020|41|41|54|54|00|00|00|00|AATT....
bames said:
what hex editor are you using?
i recommend downloading the free PSpad Hex/Txt editor.
1. Open your nv_data file using FILE then OPEN IN HEX EDIT
2. use SEARCH from toolbar commands....GOTO LINE from search menu....options after opening in hex edit mode
3. then search for $00188000
you should see the line you need to edit.
The nice thing about PSPAD is that you can also open the binary file in a Text mode. If you have trouble finding it in the hex editor mode try the following.
1. open PSpad. Goto FILE then OPEN (vs. open in hex edit). This will open in a text editor view/mode.
2. goto SEARCH and select INCREMENTAL SEARCH
3. type SGH and search
(you could also do all the hex editing without moving files to pc if you wanted using HEX EDITOR from market...though for most the PC hex editors might be easier)
if you want to use the android hex editor app to do all the editing on your phone...do the following:
THERE ARE 3 Total Lines you will need to edit:
00188008
00188010
00188020
1. Use Root Explorer to copy nv_data.bin from efs folder to the root directory on your external sd.
2. Use Hex Editor App to open the copy from your external SD.
3. One Open click the capacitative menu button and select jump to address
4. Enter 0188008
This will take you to line 00188008
5. Edit the last or 8th Block so it reads 41.
6. Enter 0188010
7. This will take you to line 00188010. Edit the first two blocks of this line. Replace the #'s so that both of the first two blocks contain 54. (look to the text at the right of screen the first two letter should have changed to TT. To recap you need to edit Block 1 and Block 2 of line 0018010:
LINE 0018010
Block 1 = 54
Block 2 = 54
(text @ right should now read AT....SG)
8. Now look down to line 0018020 and look at the line. If you at the line and to the far right text you will see ATOR or ATMB if your nv_is messed up.
9. You may need to edit blocks 2-4. They should read as follows:
LINE 00188020
Block 2 = 41
Block 3 = 54
Block 4 = 54
(the text at the right of your screen should now read AATT....)
10. Save the file and move it back to efs using root explorer.
PS: Here are how the following lines should read (the ones in bold are the only ones you have to edit as line 00188018 will already be correct):
00188008|2e|34|00|00|00|00|ff|41|.4....A
00188010|54|54|00|00|00|00|53|47|AT....SG
00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK
00188020|41|41|54|54|00|00|00|00|AATT....
Click to expand...
Click to collapse
Ok, So my nv_data.bin must be fubared cause I don't even have lines 188008 or 188018. They go by 10's like 188000, 188010, 188020, ect. And the text to the right of line 188010 starts TT....SG not AT....SG
File
I didn't back this up from my first flash to a custom ROM. Stated at the beginning it says this is likely unfixable. I have run Axura, Cog and Perception Roms (not in that order). Not sure if that makes a difference. Is this still fixable? The problem I have (using new market) is apps are either
A) Installed and not showing so on the market
B) I have them installed and they disappear & have to reinstall them from the market only to have them disappear from my phone again
C) Unable to download them (such as Pocket Legends)
Any feedback is appreciated.
Thanks
Slowazz28 said:
Ok, So my nv_data.bin must be fubared cause I don't even have lines 188008 or 188018. They go by 10's like 188000, 188010, 188020, ect. And the text to the right of line 188010 starts TT....SG not AT....SG
Click to expand...
Click to collapse
my bad
the 188010 should start TT i will correct my original.
but you should be able to find lines 188008 an 18 though you wont need to do anything with 18. Did you try looking at it with the android hex editor app from market?
You won't see the 008 and 018 lines if your using a hex editor on PC you will only see the lines by by 10's.
The section you are referring to are for Using Android Hex Editor App on your phone.
-----------------------
if your using a hex editor on your PC you should see the following when corrected:
188000 | FFFF | FFFF | 5245 | 5630 | 2E34 | 0000 | 0000 | FF41 |
188010 | 5454 | 0000 | 0000 | 5347 | 482D | 4938 | 3937 | 5A4B |
188020 | 4141 | 5454 | 0000 | 0000 | 0000 | 0150 | 024E | 034E |
Slowazz28 said:
Could someone that has successfully done this post what line in the hex file the product code is found on. All I get is string not found??? Thanks
Click to expand...
Click to collapse
It really depends on the editor you are using and you have to make sure you are searching for ASCII...
in the edit that i use, it is line 188010
Hi,
I've taken the defyparts.apk from the zip of the maniac103's rom in order to have the service to download automatically the lto.dat
Currently I'm using CM 7.2 stable (official).
The service is working well but at the end it doesn't copy the temp file to /data/location/lto.dat
I've checked that it downloads the file properly and it creates the temporary file in /data/data/com.cyanogenmod.defyparts/cache but then it deletes it without copying.
This is an extract from the catlog
Code:
V/LtoDownloadService(16998): Download was forced, overriding network type check
D/LtoDownloadService(16998): Downloaded 196600/196600 bytes of LTO data
W/LtoDownloadService(16998): Could not move temporary file to destination
To me it seems some kind of permission settings.
These are the permissions of /data/location
Code:
drwxrwx--x 2 radio radio 4096 Jul 19 19:03 location
and of /data/location/*
Code:
drwxrwx--x 2 radio radio 4096 Jul 19 19:03 .
drwxrwx--x 28 system system 4096 Jul 18 18:58 ..
-rw-rw-rw- 1 root radio 13068 Jul 18 19:14 LEARN_STORE.BIN
prw-rw-r-- 1 radio radio 0 Nov 28 2011 gpscmd
-rw------- 1 radio radio 4364 Jul 18 20:08 gpsdata.nvs
-rw-rw-rw- 1 root radio 2198 Jul 19 19:03 location.cfg
Do you have any hint to get it work?
An other (related question). The gpsconfig.xml from maniac103's is different the following lines are not in my config file.
Code:
LbsEnable="false"
LbsLocal="true"
LbsSyncLto="true"
LbsSyncCells="true"
What do they mean? I've googled it a little bit but I found nothing.
Thanks,
Peppe
PS: some interesting links:
http://forum.xda-developers.com/showthread.php?t=1563534 post about lto on defy
https://github.com/monecafe/android...cyanogenmod/defyparts/LtoDownloadService.java the lto auto download service
/data/location must be radio:system for this to work.
See here.
maniac103 said:
/data/location must be radio:system for this to work.
See here.
Click to expand...
Click to collapse
Yes man! :victory:
I was close to the solution! :silly:
Thanks for *all* the hard work.
Peppe
JB ?
Is the defyparts.apk from Maniac´s rom too different compared to Quarx JB roms ?
I´m willing to do this procedure in Quarx´s JB 20120726 rom
Thanks in advance.
Check this link for automatic lto.dat download:
http://forum.xda-developers.com/showpost.php?p=29490347&postcount=54
It works well with froyo.
In cm7/9/10, insert the code to a right file.
popcorn1122 said:
Check this link for automatic lto.dat download:
In cm7/9/10, insert the code to a right file.
Click to expand...
Click to collapse
I guess that the code made by maniac103 (no offense) is better: it is a service, you can choose if download only on wifi and relies on the api.
Maybe we can ask him to port this to cm9/10 or quarx or epsylon to merge it.
Bye,
Peppe
Hello guys Ok, I have a problem! I am trying to flash my Huawei y560-l01 because it has the encryption error
I created a dload folder in the root of my sdCard and i put in this folder UPDATE.APP file.
I log in recovery mode -> could not wipe cache or wipe data. -> After i insert sdCard into his slot.
I turn on the device and automatically start the update.app installation... but, i got this ERROR: "Can't install this package (Wed Nov 11 0:26:23 CST 2015) over newer build (Mon Nov 30 21:18:44 CST 2015). E:Error in /sdcard/dload/update.App (Status 7)"; that tells me I’m trying install an older build on a newer build and I cant find a newer build online. Please help, with any solutions I can implement