Related
What is it? Because I want to download the mokeeOS, but the installation is confusing me, so I wanna know if the efs matters
Sent from my SGH-T959V using XDA
1. Yes efs matters a lot
2. I don't know a whole lot but it holds the network info, imei number, and alot of other really important things
Sent from my SGH-T959V using xda premium
Although there is a way to make sure you have a backup, flash this file in cwm
sourceforge.net/projects/teamacid/files/fb/cwm/cm7-efs-backup.zip/download
And there will be two files in the root of your sd card
Efs-backup.tar and efs-backup.tar.md5 ( I suggest save it to your computer, it saved my ass )
And you can restore this backup at anytime by flashing this
sourceforge.net/projects/teamacid/files/fb/cwm/cm7-efs-restore.zip/download
Good luck
Sent from my SGH-T959V using xda premium
Efs is the files system that holds the unique identifiers for your device. Without it, your phone is basically useless. You won't be able to connect to any network properly do things like phone calls, internet, texting, are all degraded, if they even work at all... Make sure you know what you are doing before messing with it. Fb created a vet good guide on the wiki. Follow it to a T!
Sent from my SGH-T959V using XDA
I would suggest using a root browser to copy the EFS folder to somewhere safe on your PC and copy a 2nd back-up to your SD card. I lost IMEI going from CM7 to moKeeOS but was able to easliy restore it with a back-up and a root browser.
The flashable EFS back-up/restore from FB should still be used, but with EFS/IMEI I don't think you can be too careful and backing it up manually as previously stated is a good idea.
Yeah, I keep multiple copies of it on my PC. The reason being is that I copy it whenever I do a backup before a flash. So I have a directory with the date with 3 folders: efs, nandroid, and sdcard. I used adb to copy them:
Code:
cd efs
adb pull /efs/
Probably overkill, but better to be safe than sorry, eh?
Ok, but once you lose IMEI and don't have a backup (I received this phone for repair), then what can I do?
serialteg said:
Ok, but once you lose IMEI and don't have a backup (I received this phone for repair), then what can I do?
Click to expand...
Click to collapse
It's pretty much screwed without the OEM Samsung/Tmo software. You would have to send it to Samsung for repair, or you might get lucky and get an engineer to hook you up, but that is unlikely...
thomas.raines said:
It's pretty much screwed without the OEM Samsung/Tmo software. You would have to send it to Samsung for repair, or you might get lucky and get an engineer to hook you up, but that is unlikely...
Click to expand...
Click to collapse
thanks for the answer. that OEM software isn't available in the forums or anywhere else for us? because I swear I flashed something OEM'ish without root with heimdall.
also, the imei is on the battery part of the phone, can't i fix it?
i read somewhere that you could use a phone just fine without imei on the about phone.
you can use the phone without imei, but it doesn't function as well as it would with it. Also, i was using titanium backup and it said my device's id was changed, and it showed my actual imei. If i were to restore it, would that fix the imei?
EFS help on the SGH-T959V
Basically, I've had a hell of a time with some EFS drama this weekend, made a total noob mistake, but in a stroke of luck I was able to "recover" so to speak my EFS even after it was supposedly "wiped."
After some thorough research and READING and bit of thought, I realized that the PIT mapping layouts between BML and MTD are indeed different, and that in theory if one remaps to BML (in layman's terms a stock partition map) then the EFS data originally on the phone gets correctly remapped (at least in my case it did).
To reiterate:
1. I did a nandroid backup. Basic ****. I hope to god you at least did this step too.
2. I used the cm7-efs-backup.zip script to backup my EFS. This was my first mistake. In my case, I don't know why I'm still researching, this script failed to make a backup .tar on my sdcard or anywhere else for that matter. It didn't throw any error messages either on the screen in the process. Not trying to attack the authors of that script, I'm just saying it didn't work for me this time.
3. I pushed the TWRP boot.img with Heimdall
4. I used the cm7-efs-restore.zip script which also "succeeded" but did nothing to restore any sort of EFS obviously because there was no backup to begin with.
5. I flashed R11 unofficial cm7 and booted up. Everything was fine but the IMEI was corrupted and I confirmed that the new MTD EFS partition was empty. On T-Mobile I could place no calls and only got sporadic and intermittent data access.
It was at this point I was sure I had ruined my phone.
After some more careful reading I realized that the original EFS was still present on the firmware, however the new MTD layout I flashed (wisely) stores its EFS partition in a different physical location. In theory, I thought if I reverted to BML and a stock ROM then I would recover the original EFS. In my case, this was successful.
1. I accessed the most recent "boot.img" file from my most recent nandroid and pushed that back to the device with Heimdall
2. At this point you have to flip your USB drivers back to USB Composite Device.
3. I then used a Heimdall one click to return to a rooted stock KJ6 "Gremlin Remover"
4. Upon restart, everything was fine (sigh of relief)
At this point, I'm still trying to determine why my EFS cannot be backed up with a few automatic tools. I made a backup of the file structure, but even lyriquidperfection's EFS Pro 1.4.7 can't make a backup of the EFS. It can access the ADB Server, but the backup 'fails'.
I'll check back in after I figure out why.
Hopefully this info will help anyone else who has switched to MTD and has a missing EFS.
nick.tansy said:
At this point, I'm still trying to determine why my EFS cannot be backed up with a few automatic tools. I made a backup of the file structure, but even lyriquidperfection's EFS Pro 1.4.7 can't make a backup of the EFS. It can access the ADB Server, but the backup 'fails'.
I'll check back in after I figure out why.
Hopefully this info will help anyone else who has switched to MTD and has a missing EFS.
Click to expand...
Click to collapse
I had similar issues yesterday. If your trying to install the twrp and then downgrade to the version with wifi dont flash the boot.img with heimdall. Follow the instructions for installing via cwm.
Just install the zip that has twrp in it. But follow the directions for normal cwm installation.
Also when trying to make a backup of your efs, make sure system is mounted. I initially did not have any problem but I was on antonx's kernel and when you flash with that recovery it would mount properly. What is happening is system isnt getting mounted. So its making a null backup.
The most important thing to do is when you are trying to make a backup of your efs is mount system!
Hi have you tried the updated EFS Pro v1.7.13? It can now automatically detect the mount point of the '/efs' folder for back up and restore. Also many many bug fixes and new code to communicate with adb.exe alot more quickly and efficiently.
Head over to the forum and check it out.
I already solved this problem, but this would seem useful other people with the same problem. But what forums are you exactly referring to?
Sent from my SGH-T959V using XDA
mierkat09 said:
I already solved this problem, but this would seem useful other people with the same problem. But what forums are you exactly referring to?
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
This one.
http://forum.xda-developers.com/showthread.php?p=18524176
I created a tool a while back for Galaxy S II owners to backup and restore the '/efs' partition and perform basic NV Repair on their devices.
This proved so popular that I recently updated the application which now includes a feature to automatically detect the mount point of the '/efs' partition. This allows any supported device to be used with EFS Pro and also adds support for future devices.
Check out the link below for more info and download:
http://forum.xda-developers.com/showthread.php?p=18524176
Enjoy!
Sent from my GT-I9100 using Tapatalk 2
Hi!
I tried 1.6.8 with my R (GT-i9103). I selected Galaxy S II as device profile because my efs partition is the same (mmcblk0p1, as shows the mount command for the efs partition). And it says "Device Partition Location appears to be invalid! Make sure you have selected the CORRECT Device Profile then try again!".
If I choose "Add Device..." button, I write "Galaxy R" for the Device Name and "mmcblk0p1" as the location and the response is "Partition Location is Invalid! Please try again a VALID Partition Location."
PD: If you prefer, I could copy&paste this post on your original thread, but I imagine you prefer answers per device in their respective places.
coldbeermt said:
Hi!
I tried 1.6.8 with my R (GT-i9103). I selected Galaxy S II as device profile because my efs partition is the same (mmcblk0p1, as shows the mount command for the efs partition). And it says "Device Partition Location appears to be invalid! Make sure you have selected the CORRECT Device Profile then try again!".
If I choose "Add Device..." button, I write "Galaxy R" for the Device Name and "mmcblk0p1" as the location and the response is "Partition Location is Invalid! Please try again a VALID Partition Location."
PD: If you prefer, I could copy&paste this post on your original thread, but I imagine you prefer answers per device in their respective places.
Click to expand...
Click to collapse
Hi there, download the latest version, v1.7.13 as automatic partition location detection has been implemented which should resolve your issue.
Sent from my GT-I9100 using Tapatalk 2
Ok, Thank you very much, lyriquidperfection, it works like a charm right now (1.7.14)... at least to backup the efs partition. Good job, man!!!
What if I flash efs.img from some other SGR... Then two or more devices will have same imei.... Will it be an issue?
I know it may not be great benefit....
Sent via XDA App...
I am a noob here... but....I am a geek.... ;-)
bhargav143 said:
What if I flash efs.img from some other SGR... Then two or more devices will have same imei.... Will it be an issue?
I know it may not be great benefit....
Sent via XDA App...
I am a noob here... but....I am a geek.... ;-)
Click to expand...
Click to collapse
well this is a insane question
i dont think it is possible to flash efs of some other device as md5 sums wont match
xlm13x said:
well this is a insane question
i dont think it is possible to flash efs of some other device as md5 sums wont match
Click to expand...
Click to collapse
Correct plus its illegal anyway.
Sent from my GT-I9100 using Tapatalk 2
He he.... Thanks dudes....and sorry for being foolish.....
Sent via XDA App...
I may be a noob here...
but....I am a geek.... ;-)
EFS Professional v2.0.9 has now been released!
http://forum.xda-developers.com/showthread.php?t=1308546
Sent from my GT-I9305 using Tapatalk 2
Great Tool thank you buddy..:thumbup:
Sent from my GT-I9103 using xda app-developers app
REPLY
lyriquidperfection said:
I created a tool a while back for Galaxy S II owners to backup and restore the '/efs' partition and perform basic NV Repair on their devices.
This proved so popular that I recently updated the application which now includes a feature to automatically detect the mount point of the '/efs' partition. This allows any supported device to be used with EFS Pro and also adds support for future devices.
Check out the link below for more info and download:
http://forum.xda-developers.com/showthread.php?p=18524176
Enjoy!
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Hello Friend Trying to backup my efs partition with the version 2.0.17 but it do not show partitions plz help..USING SAMSUNG GALAXY R GT_9103
please help my phone has no imei after flash a custom rom framework * # 06 # get this IMEI null / null http://imageshack.us/photo/my-images/546/sc20120828223834.png/
http://imageshack.us/photo/my-images/266/sc20120828223733.png/
Try flashing a different modem
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
dutchthomas said:
Try flashing a different modem
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I tried ics and ginger stock and nothing
See if this helps you http://forum.xda-developers.com/showthread.php?t=1611796
kishke said:
See if this helps you http://forum.xda-developers.com/showthread.php?t=1611796
Click to expand...
Click to collapse
I try this method and repair the lock screen that did not work but still not working imei imei null / null thank
That is REALLY BAD.... Not sure what to tell you... Heard someone else did that and they were screwed....
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
If it's only IMEI number that's missing use the search, there was a thread a while back with someone having the same issue, he got told to edit some file and enter his IMEI from the phone's sticker.
aiyoros02 said:
please help my phone has no imei after flash a custom rom framework * # 06 # get this IMEI null / null
Click to expand...
Click to collapse
Exactly what rom framework did you flash?
cschmitt said:
Exactly what rom framework did you flash?
Click to expand...
Click to collapse
Just install the Alpha 3 rom CyanogenMod 10 Chopsticks eat as usual, but I think the problem arose when trying to unlock the sim with an online payment program, since then insert * # 06 # and IMEI it says null / null
aiyoros02 said:
Just install the Alpha 3 rom CyanogenMod 10 Chopsticks eat as usual, but I think the problem arose when trying to unlock the sim with an online payment program, since then insert * # 06 # and IMEI it says null / null
Click to expand...
Click to collapse
Ok, first off did you follow the other post regarding repairing /efs/imei/keystr file if necessary?
Otherwise, sounds like the hidden EFS partitions are corrupt.
Do you have a recent nandroid backup (prior to the unlock attempt)? If so, check the data.ext4.tar for an efs1.bin, efs2.bin, and efs3.bin located in /data/qcks directory.
If you have the efs?.bin files I can walk you through flashing them back into the EFS partitions on the phone. That'll restore the IMEI.
cschmitt said:
Ok, first off did you follow the other post regarding repairing /efs/imei/keystr file if necessary?
Otherwise, sounds like the hidden EFS partitions are corrupt.
Do you have a recent nandroid backup (prior to the unlock attempt)? If so, check the data.ext4.tar for an efs1.bin, efs2.bin, and efs3.bin located in /data/qcks directory.
If you have the efs?.bin files I can walk you through flashing them back into the EFS partitions on the phone. That'll restore the IMEI.
Click to expand...
Click to collapse
if you use the method / efs / imei / keystr, and retrieve the Parameter Display Lock was corrupt, but does not appear imei,
I have nothing, everything was erased trying to repair the error, I did all the wipe and factory reset. maybe find another method
aiyoros02 said:
if you use the method / efs / imei / keystr, and retrieve the Parameter Display Lock was corrupt, but does not appear imei,
I have nothing, everything was erased trying to repair the error, I did all the wipe and factory reset. maybe find another method
Click to expand...
Click to collapse
Sorry to say then, without a nandriod backup you're SOL.
cschmitt said:
Sorry to say then, without a nandriod backup you're SOL.
Click to expand...
Click to collapse
I'm facing same issue with my Skyrocket. Did anyone found any solution for this null/null IMEI?
talk2sharn said:
I'm facing same issue with my Skyrocket. Did anyone found any solution for this null/null IMEI?
Click to expand...
Click to collapse
Check out these threads, there are solutions but you got to pay up at least €10
http://forum.xda-developers.com/showthread.php?t=2288390
http://forum.xda-developers.com/showthread.php?t=2287136
how to use efs1.bin efs2.bin and efs3 bin to restore imei
cschmitt said:
Ok, first off did you follow the other post regarding repairing /efs/imei/keystr file if necessary?
Otherwise, sounds like the hidden EFS partitions are corrupt.
Do you have a recent nandroid backup (prior to the unlock attempt)? If so, check the data.ext4.tar for an efs1.bin, efs2.bin, and efs3.bin located in /data/qcks directory.
If you have the efs?.bin files I can walk you through flashing them back into the EFS partitions on the phone. That'll restore the IMEI.
Click to expand...
Click to collapse
Hi,
I found myself in exact same situation (0 IMEI, corruct EFS, no nv_data.bin files on i727). I however have a nandroid backup and I found and extracted the efs1-3.bin files from /data directory.
Could you please let me know how to flash them into the EFS partition to restore the IMEI.
you are my last hope !!!!!
bmyury said:
Hi,
I found myself in exact same situation (0 IMEI, corruct EFS, no nv_data.bin files on i727). I however have a nandroid backup and I found and extracted the efs1-3.bin files from /data directory.
Could you please let me know how to flash them into the EFS partition to restore the IMEI.
you are my last hope !!!!!
Click to expand...
Click to collapse
howto backup/restore efs
dont know if it will fix the imei though
This may help if You are having "Unknown Baseband" Problem, Low Signal , No 3G
or using XXKP7
DOWNLOAD
http://www.mediafire.com/?24uc31ur1mc9di4
dev0xteam said:
This may help if You are having "Unknown Baseband" Problem, Low Signal , No 3G
or using XXKP7
DOWNLOAD
http://www.mediafire.com/?24uc31ur1mc9di4
Click to expand...
Click to collapse
you do realise that this is a modem file and it can potentially harm the device... I appreciate your effort but I am just worried if some one who is having a low signal problem and flashes this and looses their baseband/IMEI...
Btw what is the version number of the modem file?
It is a XXKPE + some features from the Samsung Service Baseband
Which is enhanced in this modem?
Sent from my GT-I9003 using xda premium
how can install it ?
dev0xteam said:
It is a XXKPE + some features from the Samsung Service Baseband
Click to expand...
Click to collapse
no offence but is it worth that risk??
I was just curious about it so I installed it and have been trying for two hours or so. Not enough time to make conclusions. But I can confirm it is not dangerous (also, if you are on cm, you don't even have to flash from Odin, so you don't touch the radio partition). Picture attached.
Look at the "Versión de banda base" field, which is the baseband. It now says service. Very interesting, thank you!
Sent from my GT-I9003 using xda premium
rodero95 said:
I was just curious about it so I installed it and have been trying for two hours or so. Not enough time to make conclusions. But I can confirm it is not dangerous (also, if you are on cm, you don't even have to flash from Odin, so you don't touch the radio partition). Picture attached.
Look at the "Versión de banda base" field, which is the baseband. It now says service. Very interesting, thank you!
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
how do i install the baseband without odin ??? am lil bit confused with it.
Do you use a cm build newer than cm 10 alpha 4?
Then just copy the modem.bin inside this .tar to /radio, change owner to radio:radio and permissions to 655 and reboot.
If, just in case, it didn't work, just move your old modem.bin to /radio again.
rodero95 said:
Do you use a cm build newer than cm 10 alpha 4?
Then just copy the modem.bin inside this .tar to /radio, change owner to radio:radio and permissions to 655 and reboot.
If, just in case, it didn't work, just move your old modem.bin to /radio again.
Click to expand...
Click to collapse
Well i didn't wait for your reply and flashed it via odin and i lost my IMEI no. .
Could u help me fix this issue now.
I have backup of efs folder thats done by cm10.
anigr88 said:
Well i didn't wait for your reply and flashed it via odin and i lost my IMEI no. .
Could u help me fix this issue now.
I have backup of efs folder thats done by cm10.
Click to expand...
Click to collapse
Easy, download a file explorer with root permissions, copy your efs backup and paste it over the efs folder in "/" (root folder)
You'll get your IMEI instantly (of course reboot).
If that doesn't work, download a modem.bin that works in your country and do what rodero said
giovox said:
Easy, download a file explorer with root permissions, copy your efs backup and paste it over the efs folder in "/" (root folder)
You'll get your IMEI instantly (of course reboot).
If that doesn't work, download a modem.bin that works in your country and do what rodero said
Click to expand...
Click to collapse
Thanks for the info.
let me try and i ll let you know the status.
EDIT : well i just fixed it by flashing xxkpe through odin. I guess my modem file was corrupted.
anigr88 said:
Thanks for the info.
let me try and i ll let you know the status.
EDIT : well i just fixed it by flashing xxkpe through odin. I guess my modem file was corrupted.
Click to expand...
Click to collapse
Good to know, I've had some of those mini-heart attacks when my IMEI got erased too, luckily I have a copy of my efs in every disc, every pc and every sd in my house
Sent from my GT-I9003 using xda app-developers app
giovox said:
Good to know, I've had some of those mini-heart attacks when my IMEI got erased too, luckily I have a copy of my efs in every disc, every pc and every sd in my house
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
I ll try to backup my imei using different methods. Hope that will reduce the mini heart attack for me in future
Nope, it is very unlikely that the problem was caused by the modem, its just that, since alpha 4, our device is using an mtd partition layout and Odin uses a bml partition layout, so you probably just screw up your partitions.
Sent from my GT-I9003 using xda premium
rodero95 said:
Nope, it is very unlikely that the problem was caused by the modem, its just that, since alpha 4, our device is using an mtd partition layout and Odin uses a bml partition layout, so you probably just screw up your partitions.
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
Now i don't have the IMEI issue but i still have the network drop issue and i tried to apply the modem file as u told but i couldn't find any difference in it.
The issue remains almost the same.
I need this network drop issue to be solved because of it am missing many important calls daily.
If some one could help me out, it will be a great help, thanks
I flashed this modem but i am still getting unknown baseband on my phone..any other way?
Sent from my GT-S7562 using xda premium
Hi, I have a t959v and I have been trying to restore my IMEI (that's because I was able to backup my /efs partition).
However, after I flash CM 10.1 for my device, my IMEI is gone, or has turned to 0000000.... or has turned to ASCII characters that I couldn't even read. I tried restoring my nv_data.bin file, done everything I could(googled and tried so many posts, I've lost count already.) and ended up with still, a corrupted/missing IMEI. Well after tinkering with my device, I've found out that the reason why my nv_data.bin (5.2 Mb) corrupts as I transfer it to the /efs partition--it's because my /efs partition is a little bit small, that's why my nv_data.bin ends up in an incompleted transfer state(corrupted file). From 5.2Mb, it falls to around 3-4Mb. No, it's not compressed or anything, it's cut-off, or "cropped" if it's the right term(which I doubt). Now, the my question is, is it possible to resize or grow my /efs partition? If yes, then how? First of all, thanks for spending some time in reading my post. Now, could anybody help me? or if it's such a pain to do, is there an alternative to CM 10.1 that has minimal glitches or bugs? 'Coz it's a pity if I couldn't upgrade from GB. The hardware of this phone is good enough, but the firmware is kinda frustrating(slow, freezes, and worst of all, GB), don't get me wrong, I don't hate GB but for the hardware of this phone, it's too good to just stay in GB. Thanks again!
Reflash back to gingerbread. That should restore your ieme number. Than try again.
Sent from my BNTV250A using XDA Free mobile app
cryzone77 said:
Hi, I have a t959v and I have been trying to restore my IMEI (that's because I was able to backup my /efs partition).
However, after I flash CM 10.1 for my device, my IMEI is gone, or has turned to 0000000.... or has turned to ASCII characters that I couldn't even read. I tried restoring my nv_data.bin file, done everything I could(googled and tried so many posts, I've lost count already.) and ended up with still, a corrupted/missing IMEI. Well after tinkering with my device, I've found out that the reason why my nv_data.bin (5.2 Mb) corrupts as I transfer it to the /efs partition--it's because my /efs partition is a little bit small, that's why my nv_data.bin ends up in an incompleted transfer state(corrupted file). From 5.2Mb, it falls to around 3-4Mb. No, it's not compressed or anything, it's cut-off, or "cropped" if it's the right term(which I doubt). Now, the my question is, is it possible to resize or grow my /efs partition? If yes, then how? First of all, thanks for spending some time in reading my post. Now, could anybody help me? or if it's such a pain to do, is there an alternative to CM 10.1 that has minimal glitches or bugs? 'Coz it's a pity if I couldn't upgrade from GB. The hardware of this phone is good enough, but the firmware is kinda frustrating(slow, freezes, and worst of all, GB), don't get me wrong, I don't hate GB but for the hardware of this phone, it's too good to just stay in GB. Thanks again!
Click to expand...
Click to collapse
Interesting...
champ1919 said:
Reflash back to gingerbread. That should restore your ieme number. Than try again.
Click to expand...
Click to collapse
Sure, but that doesn't answer the original question. Going back to BML (which was on Gingerbread, of course) will restore the original /efs partition. This is because all of the MTD installs do not overwrite the original BML /efs partition.
Now, the concerning issue is that the nv_data.bin shouldn't be getting any bigger then the original (I don't have my sgs4g on hand to verify), but what may have happened is yaffs2 partition options in the kernel may not be the same or formatting may have added more partition data to the filesystem layout that makes the available free space on the partition less. (does this paragraph not make sense? If so, ask and I'll go into more detail)
So, let me ask you to do a test.
WARNING!!! Make sure you backup the EFS partition while on GB before emptying the directory!
Backup EFS (do this from recovery with adb shell):
Code:
su -
mount /efs
mount /sdcard
cd /
tar cf /sdcard/efs-backup.tar /efs
Go back to stock GB. There are Cne-Clicks I made to do this. Root the install and post the output of:
Code:
su -
rm -rf /efs/* /efs/.*
df /efs
Restore EFS (again, from recovery, adb shell):
Code:
su -
mount /efs
mount /sdcard
cd /
tar xf /sdcard/efs-backup.tar
Next, do the same for cm-9.1.0.
After that, do the same with which ever cm-10 or 4.4.x kernel you're using.
Post all of the values here and lets debug that way. I'll bet you that the available free space and total size are DIFFERENT when the partition is empty.
You don't need to restore the EFS on MTD installs, but MAKE VERY SURE you restore the EFS on the BML (Gingerbread) install!!!
Maybe also try different CM10.x and 4.4.x kernels and see if there is a difference. For each test, note which kernel, which rom. Also for each test, flash back to Gingerbread (bml, from the oneclick) before flashing a new rom!
All the nv_data.bin files I have are 262.1kB.
The tar backups the installtion script creates for you should be 700kB or less.
It sounds like something went seriously wrong with the nv_data.bin file you are trying to restore, so I recommend you follow the advice @champ1919 gave you and go back to gingerbread an flash your ROM again.
After you flash make sure that the nv_data.bin file under /efs/root/afs/settings/nv_data.bin is exactly 262.1kB. If that's the case then save the efs backup the install script made for you in a safe place.
Mine from froyo are 256.0 KB for locked and 260 for unlocked., weird..
champ1919 said:
Mine from froyo are 256.0 KB for locked and 260 for unlocked., weird..
Click to expand...
Click to collapse
Interesting. I think all the ones I got were from phones built at around the same time since they have similar text in the nv_data files.
The locked/unlocked files should be the exact same file size every time. All the tends to change is a single 1 in the file becomes a 0 to unlock it.
I had stored them in Dropbox. I betcha one is from the vibrant I lost, but, I thought I deleted it so I would not goof. As soon as I can get to a PC, I'll dig into it somemore. I wonder who wrote that guide years a go on how to hexedit that file. I should give them another thanks.
bhundven said:
Interesting...
Sure, but that doesn't answer the original question. Going back to BML (which was on Gingerbread, of course) will restore the original /efs partition. This is because all of the MTD installs do not overwrite the original BML /efs partition.
Now, the concerning issue is that the nv_data.bin shouldn't be getting any bigger then the original (I don't have my sgs4g on hand to verify), but what may have happened is yaffs2 partition options in the kernel may not be the same or formatting may have added more partition data to the filesystem layout that makes the available free space on the partition less. (does this paragraph not make sense? If so, ask and I'll go into more detail)
So, let me ask you to do a test.
WARNING!!! Make sure you backup the EFS partition while on GB before emptying the directory!
Backup EFS (do this from recovery with adb shell):
Code:
su -
mount /efs
mount /sdcard
cd /
tar cf /sdcard/efs-backup.tar /efs
Go back to stock GB. There are Cne-Clicks I made to do this. Root the install and post the output of:
Code:
su -
rm -rf /efs/* /efs/.*
df /efs
Restore EFS (again, from recovery, adb shell):
Code:
su -
mount /efs
mount /sdcard
cd /
tar xf /sdcard/efs-backup.tar
Next, do the same for cm-9.1.0.
After that, do the same with which ever cm-10 or 4.4.x kernel you're using.
Post all of the values here and lets debug that way. I'll bet you that the available free space and total size are DIFFERENT when the partition is empty.
You don't need to restore the EFS on MTD installs, but MAKE VERY SURE you restore the EFS on the BML (Gingerbread) install!!!
Maybe also try different CM10.x and 4.4.x kernels and see if there is a difference. For each test, note which kernel, which rom. Also for each test, flash back to Gingerbread (bml, from the oneclick) before flashing a new rom!
Click to expand...
Click to collapse
thanks for the fast response bhundven and the rest...
i apologize for not being able to reply as soon as you posted.
going back... i tried reflashing to stock and backed up my efs... however, when i looked at how big it was as a tar(ive tried making an rfs then put it into a tar. this is from the commands cat /dev/block/stl3 > /sdcard/efs.rfs or something like that. im sure that code came from a post here in xda too.) its size is 6.2mb.
and also... i have the log files of my cm10.1 upgrade attempt. posting it in case it would help...
also tried reflashing to stock ang flashing slimkat but the problem persists.
thanks for giving your time in helping me. i will try to reply as soon as i can. thanks again.
Q: is t959v the same as vibrant? been googling but posts are really confusing.. XD
cryzone77 said:
thanks for the fast response bhundven and the rest...
i apologize for not being able to reply as soon as you posted.
going back... i tried reflashing to stock and backed up my efs... however, when i looked at how big it was as a tar(ive tried making an rfs then put it into a tar. this is from the commands cat /dev/block/stl3 > /sdcard/efs.rfs or something like that. im sure that code came from a post here in xda too.) its size is 6.2mb.
Click to expand...
Click to collapse
Nope, that does not work. That is also not what my directions said to do.
cryzone77 said:
and also... i have the log files of my cm10.1 upgrade attempt. posting it in case it would help...
also tried reflashing to stock ang flashing slimkat but the problem persists.
thanks for giving your time in helping me. i will try to reply as soon as i can. thanks again.
Click to expand...
Click to collapse
You kinda buggered up the Quoting of the post, kinda hard to follow. So I removed what I wrote and only quoted what you said so it makes sense. But even after that, I can't really make sense of what you are doing and why you can't follow my directions?!?
cryzone77 said:
Q: is t959v the same as vibrant? been googling but posts are really confusing.. XD
Click to expand...
Click to collapse
It's not confusing at all. SGH-T959V (VibrantPlus) is not the same as SGH-T959 (Vibrant). They are not compatible, and flashing roms between the two will lead to bricks. Make sure that under the battery it says: SGH-T959V
The only thing these two devices have in common is their original provider: T-Mobile
Otherwise, go to the right forum for your phone before following any directions in this forum.
champ1919 said:
Reflash back to gingerbread. That should restore your ieme number. Than try again.
Sent from my BNTV250A using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the quick reply!
Well, the reason why I was trying to flash CM10.1 is to upgrade from GB so if I were to reflash to GB then I would've defeated my purpose.
But, I did try that, and backed up my EFS so as to restore it later on after I have flashed CM10.1 but to no avail.
cryzone77 said:
Thanks for the quick reply!
Well, the reason why I was trying to flash CM10.1 is to upgrade from GB so if I were to reflash to GB then I would've defeated my purpose.
But, I did try that, and backed up my EFS so as to restore it later on after I have flashed CM10.1 but to no avail.
Click to expand...
Click to collapse
Which phone model do you have?
Im running the new slimkat with no issue. Fb's cm11 was just as good. I bounce between those and back to GB when I need tv out with no issues.
Sent from my BNTV250A using XDA Free mobile app
bhundven said:
Nope, that does not work. That is also not what my directions said to do.
You kinda buggered up the Quoting of the post, kinda hard to follow. So I removed what I wrote and only quoted what you said so it makes sense. But even after that, I can't really make sense of what you are doing and why you can't follow my directions?!?
It's not confusing at all. SGH-T959V (VibrantPlus) is not the same as SGH-T959 (Vibrant). They are not compatible, and flashing roms between the two will lead to bricks. Make sure that under the battery it says: SGH-T959V
The only thing these two devices have in common is their original provider: T-Mobile
Otherwise, go to the right forum for your phone before following any directions in this forum.
Click to expand...
Click to collapse
Im sorry for the messed up reply sir, and thanks again for your reply,
Just to confirm, my device is INDEED T959V.
I did the cat > /sdcard/efs.rfs bla bla bla thing in the hope to make an ODIN flashable "fix" in the hope of getting my IMEI and baseband fixed.
And, just as you said, it didn't work. I also tried erasing the /efs by erase_image then mkdir -p /efs and then cd /efs then tar xf /sdcard/efs.tar but that also produced a "cropped" nv_data.bin. Im sorry I can't try your directions as of now because I'm currently using my phone for work, however, I will do as you said as soon as I can free up my device.
Q: Do I need to take my backup before I flash a custom kernel? or is it ok if back it up while using a custom kernel?
Q: So T959V is VibrantPlus, is it the same as Samsung Galaxy S 4G?
Q: So if T959V is VibrantPlus, should I look for ROMs with the naming convention of <rom name>-vibrantplusmtd?
champ1919 said:
Which phone model do you have?
Im running the new slimkat with no issue. Fb's cm11 was just as good. I bounce between those and back to GB when I need tv out with no issues.
Sent from my BNTV250A using XDA Free mobile app
Click to expand...
Click to collapse
I have a T959V.
I tried the SlimKat and SlimSabre but I still got no IMEI even after manual restore. I also tried the CM11 and still have the same problem.
So, when you go back to gingerbread, your number is still hosed?
Sent from my BNTV250A using XDA Free mobile app
cryzone77 said:
Im sorry for the messed up reply sir, and thanks again for your reply,
Just to confirm, my device is INDEED T959V.
I did the cat > /sdcard/efs.rfs bla bla bla thing in the hope to make an ODIN flashable "fix" in the hope of getting my IMEI and baseband fixed.
Click to expand...
Click to collapse
I have no clue where you got those directions.
cryzone77 said:
And, just as you said, it didn't work. I also tried erasing the /efs by erase_image then mkdir -p /efs and then cd /efs then tar xf /sdcard/efs.tar but that also produced a "cropped" nv_data.bin. Im sorry I can't try your directions as of now because I'm currently using my phone for work, however, I will do as you said as soon as I can free up my device.
Click to expand...
Click to collapse
Here it sounds like you are mixing up directions.
cryzone77 said:
Q: Do I need to take my backup before I flash a custom kernel? or is it ok if back it up while using a custom kernel?
Click to expand...
Click to collapse
Go back to stock gingerbread with my oneclick. Read all of the directions here first.
cryzone77 said:
Q: So T959V is VibrantPlus, is it the same as Samsung Galaxy S 4G?
Click to expand...
Click to collapse
Yes
cryzone77 said:
Q: So if T959V is VibrantPlus, should I look for ROMs with the naming convention of <rom name>-vibrantplusmtd?
Click to expand...
Click to collapse
No, we don't call it vibrantplus, because it cause so much confusion with vibrant. we call it galaxys4g for bml or galaxys4gmtd for mtd.
champ1919 said:
So, when you go back to gingerbread, your number is still hosed?
Click to expand...
Click to collapse
I'd like to know the answer to this as well. Good question!
bhundven said:
I have no clue where you got those directions.
Here it sounds like you are mixing up directions.
Go back to stock gingerbread with my oneclick. Read all of the directions here first.
Yes
No, we don't call it vibrantplus, because it cause so much confusion with vibrant. we call it galaxys4g for bml or galaxys4gmtd for mtd.
I'd like to know the answer to this as well. Good question!
Click to expand...
Click to collapse
Well I've tried many posts about restoring nv_data.bin but none of them seems to work. I even tried to edit nv_data.bin by hex. That's how desperate I am to upgrade. XD
By hosed, you mean corrupted or invalid? I use OneClick Heimdall by sir bhundven I believe..
and to answer the question, I get my IMEI and baseband back everytime I flash the OneClick. It's when I try to upgrade to CM++ that I get the null baseband and IMEI.
and to clarify, I got that backup process directions from this post http://forum.xda-developers.com/showthread.php?t=859914
cryzone77 said:
Well I've tried many posts about restoring nv_data.bin but none of them seems to work. I even tried to edit nv_data.bin by hex. That's how desperate I am to upgrade. XD
By hosed, you mean corrupted or invalid? I use OneClick Heimdall by sir bhundven I believe..
and to answer the question, I get my IMEI and baseband back everytime I flash the OneClick. It's when I try to upgrade to CM++ that I get the null baseband and IMEI.
Click to expand...
Click to collapse
Ok, so you go back to gingerbread and get your imei back.
cryzone77 said:
and to clarify, I got that backup process directions from this post http://forum.xda-developers.com/showthread.php?t=859914
Click to expand...
Click to collapse
NO This is not the right place to look for help. Although the 'Galaxy S 4G' is a 'Galaxy S' based-device, it is VERY different from the i9000!!!
Do not use instructions from other device forums!!!
We have documented a lot for this phone in this device forum and on our wiki
As I mentioned before (in this thread) instructions on backing up your efs, and restoring it. Use my instructions and let us know in this thread if you have any problems!
bhundven said:
Ok, so you go back to gingerbread and get your imei back.
NO This is not the right place to look for help. Although the 'Galaxy S 4G' is a 'Galaxy S' based-device, it is VERY different from the i9000!!!
Do not use instructions from other device forums!!!
We have documented a lot for this phone in this device forum and on our wiki
As I mentioned before (in this thread) instructions on backing up your efs, and restoring it. Use my instructions and let us know in this thread if you have any problems!
Click to expand...
Click to collapse
1st, YES I got my IMEI and baseband back, but its a shame if I can't upgrade to CM++(because I don't get my IMEI and baseband after flashing meaning I can't use my phone for work.) because it's a cool rom, it has everything I'm looking for in a custom rom.
AND yeah, I wasn't aware that they were THAT different. Anyways, thanks for pointing that out.
Q: Is there an upgrade path or something that I need to do aside from the standard flashing procedure for these roms?
Bhundven's modified kernel should give you root. You could skip that step of using the oneclickroot and use the heimdall one click (of his kernel) and get cwm & root in one step. It's linked in the link he gave you.
After you install cwm, is that when you loose the imei number? Are you letting the phone fully boot? How were you getting cwm in order to flash the cm?
champ1919 said:
Bhundven's modified kernel should give you root. You could skip that step of using the oneclickroot and use the heimdall one click (of his kernel) and get cwm & root in one step. It's linked in the link he gave you.
After you install cwm, is that when you loose the imei number? Are you letting the phone fully boot? How were you getting cwm in order to flash the cm?
Click to expand...
Click to collapse
Sorry,
What I meant by OneClick is using Heimdall in flashing the purely stock GB rom. After that, I root using Framaroot(successful) then I flash a custom kernel(bhundven's blastoff...IMEI and baseband still ok after this), then I flash CM++ ROM, this is where it gets ugly--I lose my IMEI(null) and baseband(also null). and YES I let the phone fully boot, I even wait around 15mins and try to turn the radio on and off to see if I got my IMEI and baseband back, I also tried taking out the battery and letting the phone loose all it's power and then turning it on, again, to no avail. And to answer the other question, I get CWM through the blastoff kernel.