Database Develop

[Q] FIX Device ID: How?

Thanks to the good folks here i've just upgraded my Galaxy S to the leaked JPM firmware. So far so good - much faster than JPK I was on.
However - I'm having problems with the Appbrain Fast Web Installer and seem to have found out that it's due to the android device ID being the same because we're all using the same ROM (or something) (http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=798644)
So.... How can I find out what my Device ID was/should be and how can I then change it to be "correct".
Any help much appreciated. Seems it might be a common issue....

Have you tried checking whether your IMEI changed after flashing? Type *#06# and if your IMEI starts with 0049... (I think...) then you need to do what almost everyone has been doing since JPC ... follow the instructions from here or some other threads from around here.
If your IMEI is fine, then I have no idea...

nonreviad said:
Have you tried checking whether your IMEI changed after flashing? Type *#06# and if your IMEI starts with 0049... (I think...) then you need to do what almost everyone has been doing since JPC ... follow the instructions from here or some other threads from around here.
If your IMEI is fine, then I have no idea...
Click to expand...
Click to collapse
Thanks for info - checked my IMEI and it seems to be fine - i.e. the one i registered with my insurance with (starts 3547)
I've read the thread you linked to trying to figure out what's what but I can't see anywhere how to find out what my product code is/was/should be or how I can change it. I've seen stuff about backing stuff up (nv_data?) but I'm not aware of having changed these.
All I've done to my phone - flashed JMX and now JPM and applied SuperOneClickv1.4-ShortFuse root. Will that have changed my product code?
I'm a bit lost with this one.

Use sgs toolbox to see the crc code.
Sometimes you got the right code in the backup file.
Just do a backup of all file on a safe place. The remove the 2 original file. Restart.
You need to be rooted for this.
Sent from my GT-I9000 using XDA App

DamianGto said:
Use sgs toolbox to see the crc code.
Sometimes you got the right code in the backup file.
Just do a backup of all file on a safe place. The remove the 2 original file. Restart.
You need to be rooted for this.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
A bit of info that might help(?):
I loaded up SGS toolbox and pressed ""check product code" it says:
---------------------
Got root access
Copied nv_data files...
nv_data.bin could not be read!
No backup .nv_data.bak found!
-----------------------------------------
I'm guessing that's bad news?!
Under Firmware Info it says:
------------------------------
PDA: I9000XXJPM
PHONE: I9000XXJPM
CSC: I9000OXAJPM
Build Info: 2010. 10
--------------------------------------
When I tap CSC selection it says: "USSD code running" and then "UNKNOWN APPLICATION"
When you say to backup 2 original files - i'm guessing it looks like I don't have those. Is there another way I can check or is it definite from the above. If I don't have the original files am I stuck? Can I get them from anywhere else? Are they default to a phone by region or carrier (my phone is from O2 in the UK and is the 8gb version)
If you say delete the original files (which aren't there it seems) - am I right in thinking this will them make the phone auto-generate new ones? (I really have no idea what these files are for or what they do).
What's the next thing to try? Can I get hold of the missing files from somewhere? Do I even need them? And how do I restore the Product ID (if it's changed!)?
Thanks

Have you checked the path manually for them?
If they are not there you are in deep water.
Its you personal data for the phone and you can't use others file.
Search this forum for help about this.
I can only give you a advice what i would do if i had that problem.
I would flash a original firmware that is lower than its on kies.
Then i would upgrade thought kies.
Then i would check if the crc code is there and right.
If it still wrong then i guess i would make the phone look like it was out of the box and return it.
If the code is right i would make a backup(full) and on this files( to my external sdcard).
Then i would upgrade to jpm/jp6.
Sent from my GT-I9000 using XDA App

DamianGto said:
Have you checked the path manually for them?
If they are not there you are in deep water.
Its you personal data for the phone and you can't use others file.
Search this forum for help about this.
I can only give you a advice what i would do if i had that problem.
I would flash a original firmware that is lower than its on kies.
Then i would upgrade thought kies.
Then i would check if the crc code is there and right.
If it still wrong then i guess i would make the phone look like it was out of the box and return it.
If the code is right i would make a backup(full) and on this files( to my external sdcard).
Then i would upgrade to jpm/jp6.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Hi - thanks for reply
I've checked the /efs folder with Root Explorer and it seems i've got:
.android - folder
.nv2.bak
.nv2.bak.md5
.nv_data.bak
.nv_data.bak.md5
.nv_state
/imei - folder
nv_data.bin
nv_data.bin.md5
Now i'm guessing this is good? is it all in the right folder?
Just to clarify - I've never messed with this folder - I've only ever flashed with Kies and cleared the cache and restored factory settings with recovery. I've also formatted internal and external memory card.
So are these files my original files? How can I tell? Are these included with the Rom's I've flashed? (JPK and now JPM)
I've copied the entire efs folder to a safe place - is there anything else I should backup also incase I can't restore it?
SGS toolbox still says:
---------------------
Got root access
Copied nv_data files...
nv_data.bin could not be read!
No backup .nv_data.bak found!
-----------------------------------------
Why can't SGS toolbox read the files?
Many Thanks

Maybe I am not following this thread correctly, but your last post deals with IMEI and unlock data. Your first post said you needed to change your deviceID. You even link to the Captivate thread that discusses the problem AND in that captivate thread is a link to change Device ID - http://forum.xda-developers.com/showpost.php?p=8604909&postcount=3550
review that post as it tells you where your device ID is located (it is not in the nv_data.bin file). Also, in the captivate thread, one person said he just made one up and that worked for him.
If you mess up with nv_data.bin you will mess up your IMEI and any unlock the phone has - so I caution you be careful.

I made a thread with the solution
http://forum.xda-developers.com/showthread.php?t=815503
This should work.

alsheron said:
Hi - thanks for reply
I've checked the /efs folder with Root Explorer and it seems i've got:
.android - folder
.nv2.bak
.nv2.bak.md5
.nv_data.bak
.nv_data.bak.md5
.nv_state
/imei - folder
nv_data.bin
nv_data.bin.md5
Now i'm guessing this is good? is it all in the right folder?
Just to clarify - I've never messed with this folder - I've only ever flashed with Kies and cleared the cache and restored factory settings with recovery. I've also formatted internal and external memory card.
So are these files my original files? How can I tell? Are these included with the Rom's I've flashed? (JPK and now JPM)
I've copied the entire efs folder to a safe place - is there anything else I should backup also incase I can't restore it?
SGS toolbox still says:
---------------------
Got root access
Copied nv_data files...
nv_data.bin could not be read!
No backup .nv_data.bak found!
-----------------------------------------
Why can't SGS toolbox read the files?
Many Thanks
Click to expand...
Click to collapse
I had the same problem.
I installed Busybox from the App Market and it solved the problem.

abumuqaatil said:
I had the same problem.
I installed Busybox from the App Market and it solved the problem.
Click to expand...
Click to collapse
thanks...had same problem and that solved it

[Dev] Help needed, no apps in market??

I created a custom Rom, a really great mash up for people that like certain things from eugenes R2 final and Nero using KA6 while also implementing a very nice stock look (stock gingerbread messaging, dialer, contacts)... calling it Frankenstein. I of course will give credit and am not taking any credit away from these real great devs... this is just a mash-up.
This is where I need my [Help] while doing this, testing on my vibrant etc. I have managed to mess up my market.... my phone started off by not being able to connect (data) at all, and only having basic phone ability (mms, callling out).. I have fixed that, but no matter if I odin back to stock, do the eugene froyo odin/reformat back to jfd.. the market will not update. No apps really whatsoever... I get more apps when going to a rom like Nero V5 vs. stock JFD.. so this tells me that I am getting the market the way it was when they were implemented into the roms? but even with nero v5 im still missing a great deal such as titanium backup, file managers... even little things like doodle jump....
anyone that can provide detail that leads to a fix i will happily donate $15 via paypal, no big deal.
files must be missing, would love help.
Edit: have tried clearing data, resigning in.. all the little things... and as i said i have flashed back to jfd... now im on jfd with apps such as firefox test.. and a bunch of apps that were most likley the first apps ever put on market.. this puzzles me.
Thanks, Brandon

the only featured app right now is auto focus snake.. which looks like a android test app...

http://www.google.com/support/forum/p/Android+Market/thread?tid=55c997eccabf0a6a&hl=en&start=40
seems to be an issue with SGS devices and the market? WTF

Attached is a copy of the vending.apk I've been using in my kangs, and haven't had a problem with it. It shows all apps, on my phone its updated by now, but if it isn't when you push it, it should update properly given a little bit and a reboot. I would say if this doesn't fix your issue, it may be something else in your build. Just push the file to the system/app folder in your build, reboot and test it. Or, copy and replace the vending.apk in your working files, recompile and flash your rom, and test it. Good Luck.

so, select section you want, select free or latest or whatever, and you will see them.... or just search for the app you want

IMEI issue
I had the same issue all test apps in market and really no access.
I had to restore my backup and relock the phone.
Now all is working.

It is because certain apps don't recognize the Vibrant's build number. (T959KA6 is an example of a build number)
Sent from my SGH-T959 using XDA App

No I flashed back to stock tried Nero 5. Nothing helped had to restore nvdata. Imei was something like 004 phone was unlocked and tested on ATT. Look when you go into the market and it popup saying phone kay not support the market. Tried multiple google accounts its linked to your google account and your imei for supported apps on your type of phone.
Sent from my SGH-T959 using XDA App

saintjmf said:
No I flashed back to stock tried Nero 5. Nothing helped had to restore nvdata. Imei was something like 004 phone was unlocked and tested on ATT. Look when you go into the market and it popup saying phone kay not support the market. Tried multiple google accounts its linked to your google account and your imei for supported apps on your type of phone.
Sent from my SGH-T959 using XDA App[/QUOTE
there we go, my imei starts with 004 too, and is not my original imei.. what is the easiest way to restore my files? if you could give step by step that would be great! thanks mate.
Click to expand...
Click to collapse

You have to have a backup copy of your original.
If you do delete the files that start with nv -- in the /efs directory.
You probably can see your original IMEI if you open the file that is hidden in the directory /efs it is .imei -- That held the correct number for my IMEI. not sure if someone knows how to use that if you dont have an original backup of nvdata.bin.
I took nvdata.bin and put it in the /efs directory.
removed all files that start with nv in /efs example nv2data.bak
rebooted phone it built md5 from nvdata.bin.
factory reset and all apps back.
I also coudlnt get my pro license of titanuim backup to register with google checkout until this was completed.

saintjmf said:
You have to have a backup copy of your original.
If you do delete the files that start with nv -- in the /efs directory.
You probably can see your original IMEI if you open the file that is hidden in the directory /efs it is .imei -- That held the correct number for my IMEI. not sure if someone knows how to use that if you dont have an original backup of nvdata.bin.
I took nvdata.bin and put it in the /efs directory.
removed all files that start with nv in /efs example nv2data.bak
rebooted phone it built md5 from nvdata.bin.
factory reset and all apps back.
I also coudlnt get my pro license of titanuim backup to register with google checkout until this was completed.
Click to expand...
Click to collapse
i do have a back up of my efs folder thank god. what program did you use to access your efs folder is what im saying? not sure if i have access to adb commands on this machine that i am using, any other way?
and remember i cant use market, so if someone can maybe provide a program to navigate my phone files from my pc, i can just put back in the nv data

I used root explorer
Sent from my SGH-T959 using XDA App

Can I flash this with clockwork mod? And does the voodoo kernel and sounds work with this?

I created another thread about this as I believe there maybe alot more users with this issue
Sent from my SGH-T959 using XDA App

whit this program you use to access your efs folder
http://www.mediafire.com/?c8x8wvpc9vhcd5x

shon yakobi said:
whit this program you use to access your efs folder
http://www.mediafire.com/?c8x8wvpc9vhcd5x
Click to expand...
Click to collapse
said this version is expired, need to update manually?

saintjmf said:
I used root explorer
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
do you know if there is a rom out there that has this preinstalled? remember i cant get apps because of that market.

The problem [might] be inside the build.prop.
Try changing:
Code:
ro.build.fingerprint=Samsung/SGH-T959/SGH-T959/SGH-T959:2.2/FROYO/UVKA6:user/release-keys
to
Code:
ro.build.fingerprint=Samsung/SGH-T959/SGH-T959/SGH-T959:2.1-update1/ECLAIR/UVJFD:user/release-keys

total commander
whit this program you use to access your efs folder its ok no problom
http://forum.xda-developers.com/attachment.php?attachmentid=494485&stc=1&d=1295487965

IMEI
You're IMEI can easily be found by just taking out your battery and looking under it at the sticker with all the numbers and bar codes. It may just show IME and have either dashes or periods (you can ignore the punctuation). That is your original IMEI (this is nothing more than your serial number, make sure you know what it is because if you ever have a hardware issue and want to still utilize your warranty then they check by this number, and of course unroot the phone first so it won't be considered out of warranty)

[Q] Where are my Clockwork backup files?

Hi,
Ive always used CWM to make my recoveries. But now, with Nexus 7 (CWM touch 6.0.1.9), Im unable to locate the backup files. There is no BACKUP folder in the clockwork folder and while I did a search using google and found many answers for my question, none of them was right. And I didnt make update from 4.1.2 - I cleaned the whole device and flashed stock 4.2.1 via fastboot, so I dont believe there is some directory tree change mess. And there is no BLOBS folder either.
I just flashed the ROM, rooted it using Toolkit, flashed CWM, made a backup - and boom, nothing there, while it is visible in both CWM recovery and ROM manager. I tried renaming the backup in ROM manager and searching for its new name using File Manager (with root privileges), but I was unsuccessful ...
So, please help me or provide me with a relevant link as I dont like TWRP ...
EDIT: I deleted the /SDCARD/CLOCKWORK folder and flashed TWRP. Now, I returned to CWM, made a backup using CWM and not only I dont see the backup itself, it didnt even recreate the CLOCKWORK folder. I just made a full search in the whole filesystem and there is nothing with "clock" in name (nothing relevant). Where is the backup hidden?????

Tried using it today. Its in some God forsaken rabbit hole. First enable root in es file explorer settings. Then look in system for data, media and eventually clockworkmod. That's the help I can give u.
Sent from my Nexus 7 using xda app-developers app

r3a1ist said:
Tried using it today. Its in some God forsaken rabbit hole. First enable root in es file explorer settings. Then look in system for data, media and eventually clockworkmod. That's the help I can give u.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks, but that not the place for me. /data is empty and the only folder found containing "clock" in the file structure is /sstorage/emulated/0/clockwork ... the same as /sdcard/clockwork I was talking about. only three small files and thats it, no BACKUP or BLOBS.
GOT IT!!! I dont know why it wasnt visible with rooted File Manager, but I tried ES and its there ... bam ... THANKS A LOT!
Now, whats the best way to save this stuff to a computer?

its because Jellybean 4.2 uses diff storage paths...
Android 4.2 significantly changes the way how sdcards are handled internally, your data is moved from /sdcard/ into /sdcard/0 on first boot (0 is the 'home directory' of the default user). If you go back to 4.1.2: Don't forget to move the data in 0/ back to the root of your sdcard.
Click to expand...
Click to collapse

Ather said:
its because Jellybean 4.2 uses diff storage paths...
Click to expand...
Click to collapse
Well, Im aware of that. But that doesnt explain why the files are under /data/media/clockwork. Neither it does explain why it wasnt shown/found by File manager with root privileges - although I guess its the problem of the File manager, as ES File Explorer sees that without any problems ...
Now, I switched CWM to save to TAR and made a backup. It created a folder "/data/media/clockwork/backup/2013-01-08-1214" with 9 files, size about 1,1GB. Is it sufficient for me to copy this file to my computer? Im talking about backing up the backup (heh) ...
Also, is it ok that files cache.ext4.tar, data.ext4.tar and system.ext4.tar are 0mb? Thanks!
EDIT: I tried moving a backup folder to my pc, making factory reset, copying it back to where it was and restoring - everything works fine. Although I dont get why google messed the sw insides so much - my Nexus S seems to be much better in the matter of directory tree - and doesnt wipe all my files when doing stock restore from PC ...

[Q] EFS partition

Hello
I have a Samsung Galaxy S with SlimBean Installed, previously I had the stock 2.3.3 XEF version and CM9
When I rooted the device for first time the first thing I did ws backing up the EFS partition, I have made subsequent backups since then. However, the files don't seem to be equal and don't match the .MD5 signatures provided.
Do the files in this partition change over time? Does that mean they are getting corrupted? The most logical thing would be that the signatures matched the files but they don't..
Thank you.

Hello
Any ideas of why this happens and if it's normal?
Thank you.

And I've just checked my phone, the .bak files have dissapeared.
I've got an old backup tho, but why did they dissapeared?
Thanks.
Edit: The rest of the files are in the efs folder, they weren't displayed because Slim filemanager doesn't show hidden files by default.
So the only question remaining is: Do you know why the MD5 signatures don't match the files?
Thank you.

I think since IMEI is unchanged - thats ok. The most important file you have to keep is nv_data.bin (i think that one) it holds your IMEI. So as long as your phone works - no panic.
Sent from my GT-I9000 using xda app-developers app

Hello
Thanks. But why does the hash change and differs from it's MD5 signature?

Probably so.. dont worry about it and keep nv_data.bin just in case.
Sent from my GT-I9000 using xda app-developers app

When you flash back to Stock 2.3.6 with or without Root it will Fix EFS for you ..just to let you know

Flash from cm9 to cm10.x without lost of efs

Hi,
i have a problem that is new to me. I flashed a lot of roms without problems and was on cm10.2. I went back to cm9 and wanted back to cm10.2.
I lost my efs folder and had to flash a stock rom. Now i am on cm9 (mackay rom with gear kernel) and when i flash cm10.2 mackay rom a lost the efs folder everytime.
So now the question:
How can i flash a cm10.2 rom without losing the efs folder?
Kind regards
Srkonus
Sent from my GT-I9000 using xda app-developers app

Its odd that you lose the IMEI from flashing from CM9 to CM10.2, although that happened to me today as well
Two ways to do this,
1.) Go back to stock, then flash in pure CM9, let it boot, then go to CM10.2
2.) Just flash in CM10.2 anyway, you should have backups of your efs (on my phone at least its /sdcard/backup and there's a few folders all beginning with efs). Inside those folders there should be a whole list of files, two of which are nv_data.bin and nv_data.bin.md5.
Download Root Browser/Root Explorer and copy nv_data.bin and nv_data.bin.md5 to /efs, overwrite the existing files. Reboot and it should be solved (I did this today so it worked for me).
Sent from my GT-P7510 using Tapatalk HD

Soryuu said:
Its odd that you lose the IMEI from flashing from CM9 to CM10.2, although that happened to me today as well
Two ways to do this,
1.) Go back to stock, then flash in pure CM9, let it boot, then go to CM10.2
2.) Just flash in CM10.2 anyway, you should have backups of your efs (on my phone at least its /sdcard/backup and there's a few folders all beginning with efs). Inside those folders there should be a whole list of files, two of which are nv_data.bin and nv_data.bin.md5.
Download Root Browser/Root Explorer and copy nv_data.bin and nv_data.bin.md5 to /efs, overwrite the existing files. Reboot and it should be solved (I did this today so it worked for me).
Sent from my GT-P7510 using Tapatalk HD
Click to expand...
Click to collapse
Hi,
thanks for your answer. Unfortionally it works not for me. Replacing the efs folder does not work and also flashing to cm10.x. i would stay at cm9.

srkonus said:
Hi,
thanks for your answer. Unfortionally it works not for me. Replacing the efs folder does not work and also flashing to cm10.x. i would stay at cm9.
Click to expand...
Click to collapse
Possibly this thread could help?
http://forum.xda-developers.com/showthread.php?t=859914
BTW: one can do it either by using ADB or within the app "Terminal Emulator" (by Jack Palevich) with same commands.