yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] bames:
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
[Captivate Android Development] Slowazz28:
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
[Captivate Android Development] bames:
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....
[Captivate Android Development] Slowazz28:
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
[Captivate Android Development] lanisan:
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
[Captivate Android Development] bames:
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 |
[Captivate Android Development] hansonmi:
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
[Captivate Android Development] hansonmi:
the only thing you can really do is fix your product code and/or unlock codes (see other threads)... the nv_data.bin files are used by kies and the market to keep track of the programs you have downloaded, etc... that is why it is important that you back up your /efs/ folder prior to flashing anything over you stock captivate... that way you can restore the files when you flash adn you will not have problems with the market not knowing what you have already downloaded.
[Captivate Android Development] lanisan:
Chance you might have those links bookmarked?

"the only thing you can really do is fix your product code and/or unlock codes (see other threads)"
[Captivate Android Development] bames:
reposted my guide for a totally self-contained restore (all done on phone w/o ADB and without moving files between PC and phone)

http://xdaforums.com/showthread.php?p=9965113#post9965113
[Captivate Android Development] hansonmi:
thats great, but your nv_data files should be kept on a PC for safe keeping...
[Captivate Android Development] lanisan:
is there a thread someone can point me to since I never initially backed mine up?

Thanks
[Captivate Android Development] bames:
if you read the guide i recommend backing the EFS folder up to your PC as well. But in a pinch you can create an extra backup folder both on the internal and external sd cards until you have access to a computer to transfer a copy of the backups as well.
[Captivate Android Development] bames:
if you never originally backed them up make backups of what you have in efs now and try the fix here or in my thread using the nv_data.bin you have.

The fix should work and once your product code and imei are correct you now have healthy nv_data files to backup. Some people just backup the nv_data files but i recommend backing up the whole EFS folder to your PC.
[Captivate Android Development] NOFSBIGE:
if our product code was changed by installing a different rom why can it not be changed back by installing another rom?? or by and update.zip
[Captivate Android Development] hansonmi:
certain roms are from other phones... for example a lot of the captivate roms come from the Vibrant which has different product codes... Since i have never made a ROM I am not sure how difficult it would be to make one that does not change the product code. Some ROM makers are looking into it... and to access the /efs/ folder on your phone you need to have root access. It is the ROM install process that writes to the /efs/ folder, I am not sure if there is a way to make a clockwork recovery .zip that would change it back or not... that is not my area of expertise.
[Captivate Android Development] bames:
has only happened to me once and even returning to stock would not repair my nv_data files or restore product code / IMEI
[Captivate Android Development] LightningGA:
I tried the above method and everything seemed to work fine but when I back up the "corrected" file from the phone it now says "SGH-I897ZKATMB"

I tried it three times and it does the same thing every time. And yes I am changing it to "SGH-I897ZKAATT"

An ideas?
[Captivate Android Development] rootnik:
I'm not understanding why this is even a big deal. If flashing a rom overwrote the code in the first place, would it be difficult to create a rom that sets the correct product ID?

I'm not a dev by no means, but I see allot of people in a panic over this and I guess I just want to understand why.
[Captivate Android Development] rwj5279955:
I used 2 file explorers. They both show an empty efs folder.

Now what?
[Captivate Android Development] bames:
because if you wanted to return your phone or completely go back to stock with unroot and be in a state that your warranty isn't in a state of void that would be detected you would need to have the proper imei and product code.
[Captivate Android Development] rwj5279955:
I got it changed in hex edit, but it won't save. Saying "already in use by another process"

Any idea what this means?
[Captivate Android Development] Slowazz28:
Thanks

Thank you very much for the help. Hex editor on the phone did the trick. ;):D
[Captivate Android Development] quy:
I pulled nv_data and cannot find SGH when searching via Hex editor. Please advise.
[Captivate Android Development] bames:
depends on what hex editor you are using some have their own quirks when searching or jumping directly to a line.

WHAT HEX EDITOR ARE YOU USING?

for starters make sure its case perfect a few of them are picky.

i recommend PsPad.

If your using it and want to search for SGH rather than using FIND you actually have to use INCREMENTAL SEARCH then type SGH.

With PsPad you can jump right to the lines by using SEARCH....GOTO LINE

and entering $00188000 and you should see all the lines you need to see on the screen (lines 188000, 188010, 188020).

If your using HEX EDITOR ANDROID app use JUMP TO and enter 0188008
[Captivate Android Development] bames:
no problem...glad it did the trick in correcting product code in your nv_data.bin.

Once you had rebooted did it restore your original IMEI as well??
[Captivate Android Development] chrisd000111:
For some reason I cant get the efs to backup. I extracted the file and when I run it, it works fine and says it backed up. Somehow I cant seem to find where it backed up at, I even tried to search for the file.

so now i cant open it in hex edit to even do anything further. I'm somewhat of a noob so if im just doing something stupid or am looking for the file in the wrong place i appologize
[Captivate Android Development] bames:
Just use root explorer.

COPY function and copy the entire EFS folder to your external SD.

connect to pc and mount. Copy EFS from your ext SD to your hard drive for safe keeping.
[Captivate Android Development] bames:
USE root explorer or android mate

make sure you select to view hidden fles/folders.
[Captivate Android Development] bames:
Are you making sure to delete all the nv_data.bak files??

delete every nv_data file except for the nv_data.bak.md5.

The only nv_data files that should be in your efs when your run the shell commands in adb or terminal explorer before reboot are:

1. The newly edited nv_data.bin

2. the nv.data.bak.md5
[Captivate Android Development] LightningGA:
I thought I did but I'll try it again.
[Captivate Android Development] chrisd000111:
ok thanks, i got the folder copied to my ext card already. I'll work on correcting the product code tomorrow. Thanks

now once i change the product code in hex edit which i have done. I'll replace the new nv_data.bin, but from here im not familiar with chown it. cause when i install busybox it says installed but nothing actually happens. From what i searched, is this what i do.

Open Terminal Emulator and run the following commands:

su

busybox chown 1001:1001 efs/nv_data.bin

reboot

6.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

when you run the update file will that chown it and reboot, cause thats the only spot im confused
[Captivate Android Development] chrisd000111:
should that second file be .nv_data.bak.md5 thats what mine is, I just wanna be clear. so all we will have is two files in the whole efs folder
[Captivate Android Development] bames:
yes that should be it

upon rebooting a new .nv_data.bin.md5 should be generated as well as a new .nv_data.bak should be generated from the correct nv_data.bin

When you use SGS TOOLBOX to check your product code you will also generate backups of all 4 nv_data files in a folder on your internal sd that is named PRODUCTCODECHECK. If you had the proper codes you will have successfully generated healthy backups of these files that could be saved elsewhere.

The files will be located in a folder withing:

/sdcard/productcodecheck
[Captivate Android Development] tbong777:
SGS says I have no nv_data.bak file.... Nor do I have an nv_data.bin.md5 file....

Sure enough in RE I don;t have any nv_data.bak or md5 files..except nv2 which I did not touch

i think I deleted the nv_data.bak.md5 file then ran permissions....oops.

So the Phone does not create it's own back up files?
[Captivate Android Development] fallguy7822:
This halfway worked for me my product code is now att but i have a generic IMEI. I opened my IMEI in a hex editor and it was changed so i tried on a hope and a prayer to change it in the hex editor save it and copy and replace the one on my phone well it didn't work still have the generic IMEI
[Captivate Android Development] sold1erjjt:
Yeah um... i'm trying to restore my IMEI with HexEdit, where is it located?
[Captivate Android Development] bames:
had u unlocked your phone / sim
[Captivate Android Development] sremick:
Ok I'm a little confused about what the main "problem" is that this "fix" is addressing.

I've gathered it has something to do with using the market, and unlocking, but that's about it. Can we newbies get some more specifics? I actually did a manual backup of /efs/ to my external SD before flashing Perception... but that's it. I haven't used this backup folder yet for anything. I'm not clear on how I'm affected right now and the specifics of what I should do to remedy the situation.
[Captivate Android Development] jack man:
Thanks to all of you that posted the detailed information in this thread. It helped my immensely. I needed to get back to stock 2.2 after flashing several different ROMs and now Kies works with my phone thanks to you guys.
[Captivate Android Development] Mr.Immaculate:
Apparently not all ROMs mess this up?

I've installed a few different ROMS, and both my product code and IMEI still match the sticker on the back.
[Captivate Android Development] jack man:
I don't know a definite answer to your question. ATT replaced my captivate last week because of a hard brick (and of course I played dumb saying that I didn't know what happend, and I was still under warranty). I had a 1007 build on the first one, and the new one is a 1008 build. I never had any problems on the 1007 with flashing any roms and going back to stock 2.1 and/or 2.2 (except when the battery accidentally fell out during one of the flashes which hard bricked it). When I got the 1008 build the 2 button combo to get to download mode comes and goes at random, then I fugured out that the nv_data.bin file had been corrupted from flashing custom ROMS since KIES was saying "unregistered device" when I tried to connect to it.

On the 1008 cap I had only installed Continuum v4 and Cognition 4.1.1. Even though I didn't have problems with those ROMS, I guess it was one of them that messed up the nv_data file. It's all good now though because of the fix in this thread.
[Captivate Android Development] doctorbva:
I leveraged a combo of this and the original instructions with the batch files and it worked great. The only change I would suggest is to run the commands from Terminal Emulator w/in the phone rather than in adb shell. Terminal Emulator worked better for me.

Thanks a lot for these instructions. You got my phone to work with Kies Mini again (for testing purposes ;))
[Vibrant Q&A, Help & Troubleshooting] Elizaks:
I am very new to this, but I have rooted Vibrant. Everything has been working fine for the most part, things have been going downhill. All day today it's just been extremely slow and when I take pics they either show up in the gallery with a long delay or not at all, I can find them in the files directory. Also, my emails were not being received nor could I send any. After uninstalling a few un-needed apps (I had over 11 GB of memory left to begin with and an empty SD), clearing cache, etc, I decided to just factory reset. I couldn't find anything that could possibly be clogging up my phone. I did, and it got a little better. I am getting my emails now, however, I tried to redownload some of my apps, and I've had major problems. Some of them downloaded completely and then just disappeared. Some of them downloaded and worked, but it took a couple of hours to download a few apps. I have no idea what to do at this point, any advice would be very much appreciated.
[Droid 2 General] sudermatt:
I loaded one of these ROMs and it had an amazing Files app that would allow me to go out and search my wiki Network for files on other computers. This was incredibly useful. I believe it was on fission. The problem is.... I need the Verizon Hotspot app that is Not on fission. Is there any way I could get the APk for the Files app?

Thanks in advance....

Matt
[Droid 2 General] phrozen87:
The files app you are talking about I am pretty sure is the motorola blur files app. The 3g app is also available on fission via the rom downloader along with the tether patches if you need those, so there are really 2 things you could do to get it:

If you prefer to use fission with it built in you can get the 3g app by:

1) re-install fission and the rom manager from their website

2) download and install the verizon 3g app and tether patches from the rom manager and install those

If you prefer to use another rom here is the Blur File Manager in a .zip. Just reboot recovery and install it as a .zip. No need to mount or anything as it will do that itself.

DISCLAIMER: I just pulled this file off my phone, so I have no idea if it will actually work or not (it may require missing libraries), you are downloading and using it at your own risk, but it should work.

http://www.mediafire.com/?9icr269ytito6jt

You could also always grab a copy of some app like root explorer off the market which I think is better anyway!
[Droid 2 General] sudermatt:
EWE ROQUE!

Exactly what I needed!
[EVO 4G Q&A, Help & Troubleshooting] squick:
How can I tell if my phone is sleeping when it should be. I've done a lot of modifications, roms, kernels, etc... I have come across a couple of threads talking bout sleep and want to try to make sure my phone is running up to par.

Several of those posts were talking bout how there phone is not sleeping when the screen is off.
[EVO 4G Q&A, Help & Troubleshooting] nuggyunlimited:
Juice plotter records how your battery decrease check it out

Swyped From Eva Running Myn's RLS4!
[Galaxy S I9000 Q&A, Help & Troubleshooting] askar79:
Hi to all,

I have Galaxy S with official firmware 2.2 I9000JPJPG and me as many others from the middle east Arab countries need to upgrade to the version 2.2.1 I9000XXJPU or I9000XXJPX .

the problem it's not support Arabic language, is there are any possibility to make 2.2.1 version firmware to support that language (at least Arabic reading and writing capabilities )
[Galaxy S I9000 Q&A, Help & Troubleshooting] tmThEMaN:
Check this

http://xdaforums.com/showthread.php?t=887950&highlight=arabic+support
[Vibrant Q&A, Help & Troubleshooting] relmnop:
I recently purchased a Samsung Vibrant to replace my Nexus One. I was quite happy with it at first, impressed by the beautiful screen and how light the phone was, but was quickly disappointed by the pathetic iPhone-ripping Android version implemented by Samsung.

One problem that is particularly annoying is that I cannot receive long text messages from my boyfriend, a vanilla Droid user on Verizon. After the 180 someodd characters, apparently the text converts to an MMS. On my Nexus, I used to receive these as multiple texts. On the new Vibrant, I get multiple texts all saying "<<Content Not Supported>>".

So what gives? This only happens with Verizon customers that I know of (I also tested from my mother's LG flip phone). Is anyone else having this problem? I have scoured the internet for the past few weeks trying to find a solution but haven't found one.

Any advice would be appreciated! I'm an intermediate to advanced Android user and have been debating rooting the Vibrant. I rooted my Nexus One and voided the warranty, and then found myself among the lucky early buyers with the defective power button. I'd prefer to keep the warranty intact however will do anything to fix this problem.
[Vibrant Accessories] blazin619:
I have a zagg full body kit for sale.

http://www.zagg.com/invisibleshield/samsung-vibrant-galaxy-s-t959-cases-screen-protectors-covers-skins-shields.php

It is on the website for $24.99. Will accept best offer because I have no use for it. Only selling inside the states. I am in San Diego, CA. Will meet up or take paypal. Thanks for looking.

PM me with your offers.
[G1 Q&A, Help & Troubleshooting] add119:
At least with wifi,gps,bluetooth file sharing working &audio.

Camera & Video recording and google apps as well.

A2sd Integrated.

Anything else beyond that is a plus.
[G1 Q&A, Help & Troubleshooting] BlaqkAudio:
He does this on the HeroC forums too. He still doesn't get how deving works.
[G1 Q&A, Help & Troubleshooting] MusicMan374:
Wasn't it announced that 2.3 is too large to fit on the g1's memory? Froyo just barely fits...

Sent from my T-Mobile myTouch 3G Slide
[G1 Q&A, Help & Troubleshooting] ForTehWolf:
they're working on it, heres a pretty stable port by ezterry: (No GPS yet)

http://xdaforums.com/showthread.php?t=882356
[G1 Q&A, Help & Troubleshooting] yohshua:
if you look in the g1 dev section you will see there are some full 2.3 roms there try them out and see if they fix for what you are looking for
[G1 Q&A, Help & Troubleshooting] creezalird:
there are about 3 gb roms are being developed in the G1 dev section

- ezGingerbread

- CM7 unofficial

- COS-DS