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.
Related
This Guide is for any user that has a Rom installed. This will back-up almost everything the user has put on the phone.
So, here are some things you need.
Heimdall One Click KB2 - http://forum.xda-developers.com/showthread.php?t=1266172 (thanks to AdamOutler)
1) First, make a nandroid backup.
2) Make an /efs backup (adb pull /efs) (also can use an app called nitrality available in market)
3) Now, you will need to Plug in your phone to the computer. Take ALL the folders on your SD card and copy them to your laptop. (Mine was user/android/sdcardbackup)
4) Remove Micro-sd card, and SIM card
5) Open up your dialer and dial this code *2767*3855# THIS WILL WIPE YOUR SD CARD and /DATA
6) Reboot the Phone
7) put your Phone in download mode, open heimdall One Click and insert the phone and make sure that heimdall recognizes it
8) Flash the new firmware Bootloaders not required
9) Have the Phone Boot up Completely (takes a long time)
10) Check to see if your /efs has been edited. Use this thread http://forum.xda-developers.com/showthread.php?t=881162 (and your efs backup) to get it back.
11) You might want to dial *2767*3855# Just in case if there is anything left.
12) You should be running KB2, have your SD cleared, and ready to be turned into samsung.
Post Questions and comments below!
i decided to save this one, no clue why, just wanted to feel important...
Better include this or your phone might come back with a voided warranty.
http://forum.xda-developers.com/showthread.php?t=881162
bigbooty said:
Better include this or your phone might come back with a voided warranty.
http://forum.xda-developers.com/showthread.php?t=881162
Click to expand...
Click to collapse
It isnt supposed to erase the /efs but ill include it, thanks!
sepherian said:
It isnt supposed to erase the /efs but ill include it, thanks!
Click to expand...
Click to collapse
No. Flashing different roms jacks with your efs. A while back I decided to clean up my phone. Internal storage was a cluster. Just for the hell of it I decided to odin back to stock and master clear, then try the 2.2 kies update. Never had tried it. Well got the unregistered device thing and kies wouldn't update it. Found the thread above and downloaded hex editor and followed the instructions, edited my NV_DATA.BIN and reloaded stock jf6 and this time kies upgraded with no problems.
Flashing many different roms changes your product code even though SG tools said I had a sgh-I897, NV_DATA.BIN said I had something else.
When my cappy messed up, my imei got corrupted. Luckily I messed with around with sgs unlock a few months before and still had my back up and was able to restore it before turning it in. first thing I did with new cappy was back up efs. Product code was different also. Flash enough roms and it can mess up something as someone might be a novice coder and mess your device up.
Sent from my SAMSUNG-SGH-I897 using XDA App
Edit: fixed Imei
Nucleartx said:
When my cappy messed up, my meid got corrupted. Luckily I messed with around with sgs unlock a few months before and still had my back up and was able to restore it before turning it in. first thing I did with new cappy was back up efs.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
meid? i think you mean imei?
bigbooty said:
No. Flashing different roms jacks with your efs. A while back I decided to clean up my phone. Internal storage was a cluster. Just for the hell of it I decided to odin back to stock and master clear, then try the 2.2 kies update. Never had tried it. Well got the unregistered device thing and kies wouldn't update it. Found the thread above and downloaded hex editor and followed the instructions, edited my NV_DATA.BIN and reloaded stock jf6 and this time kies upgraded with no problems.
Flashing many different roms changes your product code even though SG tools said I had a sgh-I897, NV_DATA.BIN said I had something else.
Click to expand...
Click to collapse
Yes, I know. This Flash is not intended to mess with the /efs AT ALL, i have checked the package and it has no reference to /efs in the scripting. The post including the package also says this:
This package does not wipe:
EFS(Where your serial number and carrier information is stored)
Data(where your market apps are stored)
SDCard (where your pictures are stored)
Click to expand...
Click to collapse
So as you can see the number i have them call wipes the data and SD but they have their nandroid and SD backups. The number i have them call also doesnt touch the /efs. Trust me, I tested this method before i posted it and i didnt make an efs backup and my IMEI was perfectly fine afterward. I assume that nothing here messed with my /efs at all.
The only thing that would change the NVdata.bin would be an unlock tool. And i doubt that it even changes it.
OP was updated with more accurate steps.
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
bluenote73 said:
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
Click to expand...
Click to collapse
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM. (you can try dirty flashing but i dont think itll work)
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
EDIT: re read your post, if your feeling adventurous and want to give it a shot, boot into CWM and connect it via usb. you can now get into an ADB shell on your phone by typing 'adb shell' if you have adb all setup and working. (im working from memory here so dont quote me on any of this)
now, you should be able to access your /system folder from that shell. be very careful though, i dont have much experience right here, and if i remember correctly you might not be in the full root directory yet)
if you can get into it try replacing your vold.fstab with a stock one,
if you dont have a stock one lying around, make a nandroid of the current state of the rom, then flash another rom, pull the vold.fstab, then re-restore back to the broken one and restore it (id upload mine but my phone is OOC right now )
after that just reboot and hope it resolves itself, if not then just follow my advice above
and keep that guide i linked to handy, messing around in CWM has the ability to brick your phone, if it does, then just follow that guide.
Klathmon said:
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM.
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
Click to expand...
Click to collapse
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
N00BY0815 said:
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
Click to expand...
Click to collapse
re read your post and updated my last post right after you posted
after dealing with noobies all day, i forget sometimes people want to try big things
Thanks guys. The info I was missing was there's no special trick to attaching adb while in CWM! Just plug in!
My phone is back up and running and partitions are fine as far as I can see after just booting up.
Hi there! I messed up with the vold.fstab filfe on my tablet – I replaced it with a downloaded file with the intention to transfer apps to my external SD card.
Now my tablet is only showing the startup logo and won’t continue loading. I can access recovery mode. Now I want to restore the original vold.fstab file.
My questions:
1. Using the Android SDK, the file explorer does not show any files, though my tablet is recognized.
2. Using adb push, it yields an error: permission denied, how to successfully push the original vold.fstab and replace the existing vold.fstab?
3. If I dump an image of my tablet and edit the dumped image, would this be easier compared to the steps above?
Thanks!
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
BryanF said:
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
Click to expand...
Click to collapse
You need to do an adb remount before you can push. Was it rooted before?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Mansa_noob, yes, my tablet is rooted. I followed some instructions about adb but had an error saying access denied, and also no files are displayed at file explorer. See my posts above. I also mounted it successfully. I will post some sreenshots later.
Please if you have some instructions, I am willing to try.
---------- Post added at 07:06 AM ---------- Previous post was at 07:02 AM ----------
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Hi twitchyEye, it did not work. It attemps to install (using the install update from ext sd card) but then says installation aborted.
Any more suggestions? Thanks
What recovery are you using? I suck with adb so I got nothing on that front.
It was the stock recovery from my Tablet. I don't have it on hand right now, I will post later. The chipset is RK3066. My problem is my tablet has no official support on the internet (maybe becaue it's still new). Model is Skyworth S71(3G).
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
TwitchyEye said:
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
Click to expand...
Click to collapse
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
Yes, I did adb remount and still access denied
BryanF said:
Yes, I did adb remount and still access denied
Click to expand...
Click to collapse
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
BryanF said:
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
Click to expand...
Click to collapse
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I want to try, but the stock recovery is my last hold as I have no stock ROM. If I overwrite the stock ROM, I cannot reinstall it as I don't have a copy of it.
So why not flash cwm with nvflash and then make a backup of your current stock rom? I did exactly that.
Sent from my LG-P999 using xda premium
This is a general CWM question but I could not find any place better to post on XDA, so excuse this if incorrect location.
I have flashed all the Skyrocket ICS roms in the past few days to see which I liked best. Before I flashed a new one, I would make a CWM backup of the current one. Wanting to easily be able to identify the files, I appended the rom name to the end of the CWM filenames after deleting all the characters after the date, which appeared to be a GMT time stamp. Now, when I try to restore any of those files, I get an MD5 checksum error. I am only assuming that this is due to changing the filename and not some other problem. Anyone have any ideas on how to fix this? TIA.
phoneturf said:
This is a general CWM question but I could not find any place better to post on XDA, so excuse this if incorrect location.
I have flashed all the Skyrocket ICS roms in the past few days to see which I liked best. Before I flashed a new one, I would make a CWM backup of the current one. Wanting to easily be able to identify the files, I appended the rom name to the end of the CWM filenames after deleting all the characters after the date, which appeared to be a GMT time stamp. Now, when I try to restore any of those files, I get an MD5 checksum error. I am only assuming that this is due to changing the filename and not some other problem. Anyone have any ideas on how to fix this? TIA.
Click to expand...
Click to collapse
Are you talking about the folder name? Because that shouldnt affect it. Inside the folder that is created for each backup, there are backup files which dont have any dates/times in the filename itself.
I vaguely remember reading about this, but I can't recall how it was resolved. Try updating your can to 5.5.0.4 Touch or 5.8.1.3 (?? something along those lines) and seeing if that resolves it. Outside if that I must ask the obvious, did u Google "md5 checksum error cwm"?
Are you using the same CWM version as you did when you backed up? If you didnt, then thats one reason. You have to stay on the same CWM version, many of these CWM versions floating around have different fixes in there.
One way around this is to go to Advanced Restore and restore all the IMG files from there.
Dixit
ihtfp69 said:
I figured I would post this fix here in case anyone else ran into this problem. This is assuming you did not change the folder names and let Clockworkmod create them. I haven't had it happen until today, but it's not a nice message to see when you are trying to do a restore.
Code:
Checking MD5 sums...
MD5 mismatch!
Do this to fix:
To fix this problem use the code below. Substitute the final folder name for the backup you need to fix.
Code:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
When that finishes, re-run the restore and everything should be fine.
NOTE: As rpearl stated, there could be something really wrong with your nandroid, so use this tutorial as a learning experience and not a fix-all. In my case, everything was fine after restoring. However, that may not always be the case. Do this with caution.
Click to expand...
Click to collapse
Use this method to potentially fix.
dixit said:
Are you using the same CWM version as you did when you backed up?
Dixit
Click to expand...
Click to collapse
That is correct on most of them. I updated to CWM Touch for the last one, but it did not restore either. To check this out, I just did a backup and without changing the name did a restore and it worked fine. The thing that was odd in the backups that would not restore was that it immediately bombed out of the checksum each time as if it was checking the name itself first.
That is brilliant. I did not realize you could generate the MD5 from ADB and stick it right into the folder. Thanks!
The few times this md5 mis-match has happened to me was because (a) the backup was actually messed up (check folder size) probably due to corruption or (b) my SD card was out of space. I've always renamed my backup set similar to yours (I append the ROM name) and it never affects the restore.
bdbx18 said:
The few times this md5 mis-match has happened to me was because (a) the backup was actually messed up (check folder size) probably due to corruption or (b) my SD card was out of space. I've always renamed my backup set similar to yours (I append the ROM name) and it never affects the restore.
Click to expand...
Click to collapse
Are you using touch or standard CWM? I wonder if this only happens in touch version. I will try this in the next few days.
I changed the name of one of the backups I created with CWM touch and it restored fine using touch. I suppose my earlier problem may have been trying to restore a backup created with old CWM using touch version.
well since you are on the subject cwm touch im making a nanadroid backup of my current ics rom right now as i speak. i started about an hour ago and its still on the backing up data part. when i used the older version to make backups i dont remember it taking this long. have any of you had cwm touch take well its been a little over an hour now? i do have more apps on my phone now than i did the last time i made a backup would that matter? should i just jerk the battery out and go back to the older version of cwm i was using? thanks ahead of time for any advice / help you may give i would appreciate it. im trying to backup this rom cause i want to flash a different modem cause the ics modem form the leak is crap and need a backup in case it dont work..
garydv2002 said:
well since you are on the subject cwm touch im making a nanadroid backup of my current ics rom right now as i speak. i started about an hour ago and its still on the backing up data part. when i used the older version to make backups i dont remember it taking this long. have any of you had cwm touch take well its been a little over an hour now? i do have more apps on my phone now than i did the last time i made a backup would that matter? should i just jerk the battery out and go back to the older version of cwm i was using? thanks ahead of time for any advice / help you may give i would appreciate it. im trying to backup this rom cause i want to flash a different modem cause the ics modem form the leak is crap and need a backup in case it dont work..
Click to expand...
Click to collapse
If you are using sk8erwitskil version of the CWM touch (ClockworkMod TOUCH 5.5.0.4 v3.5) then most likely you didnt follow one of the directions on the front page. This is a known issue. Here it is again. You need to create that file on the location you backing upto.
For CWM to recognize the .hidenandroidprogress file you need to boot into CWM and go to mounts and storage>>mount /sdcard then go back to backup & restore and make a restore and it should work everytime (as long as you do the steps in that order and you have the .hidenandroidprogress file in /sdcard/clockworkmod & /sdcard/external_sd/clockworkmod folders)
There is a known bug in ClockworkMod 5.5.0.4 that long file names can POSSIBLY cause backups to hang. There is a solution/workaround:
•boot into recovery
•try to make a backup (no matter if it passes or fails proceed to next step)
•either through terminal emulator or through adb run the following command EXACTLY:
Code:
touch /sdcard/clockworkmod/.hidenandroidprogress
•if you are backing up to external sdcard then run the following:
Code:
touch /sdcard/external_sd/clockworkmod/.hidenandroidprogress
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
garydv2002 said:
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
Click to expand...
Click to collapse
Not sure, I used that for awhile but then went back to the other touch and Ive had those two files still in my directories.
I would go ahead and create those two files (one for internal SD and one for external SD if you got one you are using that is) and try it again. Make sure you call that file exactly the way it is, or copy/paste the code identically if you do it through ADB.
Dixit
garydv2002 said:
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
Click to expand...
Click to collapse
I use that one, takes less than 5 minutes on my class 10 sd.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Well the crazy thing is after sitting there over an hour waiting I finally took out the battery and even though it never said complete all the files are there but I still don't trust that it made a good backup so I deleted those files tried putting in the code above and it still would not work so I flashed back to version 5.0.2.0 thats not touch and it made a perfect backup in under 2 minutes. Might be one of those it just ain't gonna work right on this specific phone thing or it could be the little green gremlins at it again lol... who knows.. I'll just wait for new version of touch to come along and try it. It won't be long till a newer greater version comes along as fast as technology is going today.. thanks for the help. I'm learning more and more each day from you guys on xda.....
Sent from my SAMSUNG-SGH-I727 using XDA
Not sure if this is the cause of the issue but for nandroid backups you can't make a folder name with spaces otherwise you will get an md5 sum error. Try renaming the folder with underscores instead of spaces
The Goal: To create a CWM flash-able .zip that will convert a BML formatted phone to MTD without the need to be included in a rom, creating a standard and simplicity for end-users.
RDU
ROM DEVELOPERS UNITED
AS ONE
CWM BML to MTD Conversion UtilitySupported ROMs:
- Any BML Setup
So here's how it works:
This file will convert your phone's kernel and boot recovery to MTD. Afterwards, you will be able to flash an MTD rom.
ALWAYS make a backup of your data before flashing anything.
If you flash this over an already MTD rom, it will simply abort.
The Latest Version Here. After it finishes, your phone will be stuck in a loop. Pull the battery and 3-finger back into recovery to flash an MTD rom.
UPDATE: (--/--)
Further ideas or customizations from fellow rom developers welcome.
First
This sounds vary usefull on my firends Epics. I think it will speed thing up for me at times depending what they want
Sent from the Drivers Seat of my Suby txting and Driving doing 100MPH+ in a school zone! Ha.
zman519 said:
First
This sounds vary usefull on my firends Epics. I think it will speed thing up for me at times depending what they want
Sent from the Drivers Seat of my Suby txting and Driving doing 100MPH+ in a school zone! Ha.
Click to expand...
Click to collapse
Please note, this is a test version.
It's based on a version I used myself, but being on MTD, I can't test it easily.
There are 3 current scenarios it could yield:
1. Nothing happens.
2. It works perfectly.
3. It works, but puts the phone into a bootloop. This is what the old version did to me... Pop the battery. Boot into recovery. Profit.
So this would theoretically convert a BML ROM to MTD on a person's phone. Sounds great.
As a note to all remember as always to back up before flashing ANYTHING.
Sent from my SPH-D700 using xda premium
kennyglass123 said:
So this would theoretically convert a BML ROM to MTD on a person's phone. Sounds great.
As a note to all remember as always to back up before flashing ANYTHING.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Right now it should format your phone and prep it for a Rom. If it works properly, I'd like to rewrite it to convert and PRESERVE a BML Rom into an MTD Rom.
RandomKing said:
Please note, this is a test version.
It's based on a version I used myself, but being on MTD, I can't test it easily.
There are 3 current scenarios it could yield:
1. Nothing happens.
2. It works perfectly.
3. It works, but puts the phone into a bootloop. This is what the old version did to me... Pop the battery. Boot into recovery. Profit.
Click to expand...
Click to collapse
I understand ;-)
If my budy ever gets a new sdcard, I'll use his phone as a test dumey. The worst that could happen is I have to bust out the usb cable & fire up ODIN
Sent from the Drivers Seat of my Suby txting and Driving doing 100MPH+ in a school zone! Ha.
Ok so currently no data or apps are preserved. It is mostly a blank MTD slate?
Sent from my SPH-D700 using xda premium
kennyglass123 said:
Ok so currently no data or apps are preserved. It is mostly a blank MTD slate?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Yup. I need someone to confirm that it works properly. As I mentioned, I previously used a simpler version to convert myself to MTD and it worked, but it put me in a bootloop. I'm hoping to solve the bootloop so I can create a version to preserve a setup.
RandomKing said:
Yup. I need someone to confirm that it works properly. As I mentioned, I previously used a simpler version to convert myself to MTD and it worked, but it put me in a bootloop. I'm hoping to solve the bootloop so I can create a version to preserve a setup.
Click to expand...
Click to collapse
Well if you ran this and it put you in a boot loop, then it most likely worked properly since this would have formatted/converted your partition map to MTD. The BML rom would have either been erased or just unable to run due to the conversion.
Just a curious question here:
What would you need to do to actually convert an existing BML install to work on the MTD partition map?
nikon120 said:
Well if you ran this and it put you in a boot loop, then it most likely worked properly since this would have formatted/converted your partition map to MTD. The BML rom would have either been erased or just unable to run due to the conversion.
Just a curious question here:
What would you need to do to actually convert an existing BML install to work on the MTD partition map?
Click to expand...
Click to collapse
He said that it worked right in the post you quoted... lol
And I have no diea about the question... I'm kinda curious about this too...
nikon120 said:
Well if you ran this and it put you in a boot loop, then it most likely worked properly since this would have formatted/converted your partition map to MTD. The BML rom would have either been erased or just unable to run due to the conversion.
Just a curious question here:
What would you need to do to actually convert an existing BML install to work on the MTD partition map?
Click to expand...
Click to collapse
Because formatting destroys the existing file structure (it doesn't actually erase files, just overwrites the data that maps out the locations of those files), everything would need to be copied to a temporary location before converting the original location to the new partition type. Then the temp data (backup) would need to be copied back to the original location using the new format.
It is not possible to just change the format while leaving the data in place - those warnings on every format command (in every computerized device - windows, mac, etc) were not a design decision, but a result of a design limitation. The backup/format/restore method is the only way.
flastnoles11 said:
He said that it worked right in the post you quoted... lol
And I have no diea about the question... I'm kinda curious about this too...
Click to expand...
Click to collapse
He also said he was trying to solve the boot-loop problem, not a formatting problem. The clarification was not to assert that the formatting worked - the focus was on explaining the cause of the boot loop, to point out that there is no problem to be solved there because a BML kernel should boot loop when the rest of the partitions are freshly formatted MTD partitions.
The standard BML kernel can't read MTD, so the fact that those partitions are empty is irrelevant. Even if the partitions were converted without data loss (via a backup/convert/restore), the kernel would still need to be MTD-capable (so this by itself will not convert a BML rom to MTD)
Hopefully this clears up some of the confusion...
Sent from my SPH-D700 using XDA
nikon120 said:
Well if you ran this and it put you in a boot loop, then it most likely worked properly since this would have formatted/converted your partition map to MTD. The BML rom would have either been erased or just unable to run due to the conversion.
Just a curious question here:
What would you need to do to actually convert an existing BML install to work on the MTD partition map?
Click to expand...
Click to collapse
A kernel that supports MTD and copy all system, data and cache folder then paste it back after the conversion with the new kernel.
Sent from my SPH-D700 using xda premium
flastnoles11 said:
He said that it worked right in the post you quoted... lol
And I have no diea about the question... I'm kinda curious about this too...
Click to expand...
Click to collapse
Yes he did. I too read his reply.
My response to Random was that since he's put in the bootloop, then it worked for him due to the lack of converting the rom over. Therefore my reply implied that testing more won't hurt anything at all and would be good protocol, but may not be needed since it worked for him given his output.
styles420 said:
Because formatting destroys the existing file structure (it doesn't actually erase files, just overwrites the data that maps out the locations of those files), everything would need to be copied to a temporary location before converting the original location to the new partition type. Then the temp data (backup) would need to be copied back to the original location using the new format.
It is not possible to just change the format while leaving the data in place - those warnings on every format command (in every computerized device - windows, mac, etc) were not a design decision, but a result of a design limitation. The backup/format/restore method is the only way.
Click to expand...
Click to collapse
Ahh yea, I wasn't 100% sure if this was the case. Good breakdown though.
Doesn't seem to be working, I'll be uploading the version I use later on with directions.
I understand the theory, prepping a 100% BML setup for it's MTD future; just out of curiosity, Q: would there be a way to reverse this process so that if you arrive at your destination MTD ROM + change your mind, would it be possible to choose to convert an MTD ROM back to BML w/out having to ODIN (md5.tar + pit...........the way we do currently)?
BTW, am looking forward to testing your proposed conversion utility, just wondering.
nikon120 said:
Well if you ran this and it put you in a boot loop, then it most likely worked properly since this would have formatted/converted your partition map to MTD. The BML rom would have either been erased or just unable to run due to the conversion.
Just a curious question here:
What would you need to do to actually convert an existing BML install to work on the MTD partition map?
Click to expand...
Click to collapse
All I know is that it'd need an mtd kernel. Also, maybe it could work like rfs to ext4 where it backs everything up then restores and flashes an mtd compatible kernel. Theoretically, that should work on samsung tw based roms.
Sent from my SPH-D700 using XDA
Randomking, to fix the bootloop issue, try having it reboot recovery like the cm/miui mtd install scripts do (I think).
Sent from my SPH-D700 using XDA
sonarchist said:
I understand the theory, prepping a 100% BML setup for it's MTD future; just out of curiosity, Q: would there be a way to reverse this process so that if you arrive at your destination MTD ROM + change your mind, would it be possible to choose to convert an MTD ROM back to BML w/out having to ODIN (md5.tar + pit...........the way we do currently)?
BTW, am looking forward to testing your proposed conversion utility, just wondering.
Click to expand...
Click to collapse
Not possible since BML is proprietary. Odin is the only way to get this top secret partition information on our phone.
Sent from my SPH-D700 using xda premium
Thank You!
Edit
NVRMIND
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