Related
Hi there!
Recently I've been trying to upgrade my SGS with a custom ROM, Darky's 4.0. After installing the ROM as instructed (using CWM and copying the ROM to the internal SD card), the ROM Installs, after the 1st boot it keeps looping, see video:
http://www.youtube.com/watch?v=kWrijyv-8PM (not edited, sorry for that)
Original SGS:
GT-I9000T
I9000TUBJG7
Product code: GT-I9000HKTPCW
kernel: 2.6.28
Build: eclair.ubjg5
The first upgrade I made was via Kies reg-hack to: GT-I9000HKDXEU, 'I9000XXJF3/I9000OXAJF3/I9000XXJF3/I9000XXJF3, and it installed Stock Froyo update. The SGS worked fine with exception of the radio, which didn't lock my 3G over the 850 band.
Currently:
9000M running STOCK Australian I9000UGJG8 (due to radio issues, besides the Canadian ROM, this is pretty much the only ROM which modem.bin's works properly with my network, 3G 850MHz).
FW:2.1-update1
Kernel 2.3.29 [email protected] #2
Eclair.UGJG8
I tried with the following STOCK ROMs prior to the custom ROM install: I9000XWJM1, I9000XWJG5, I9000XWJM9 and I9000UGJH2.
I have ALLWAYS made an SD unmount and format, formatted the cache and factory reset. After it loops, the only way to get it back is using downloader mode and installing a STOCK ROM via ODIN (always do a .512 pit repartition)
Any suggestions to make this SGS get the ROM? maybe the kernel is bad?
Cheers!
Have u tried to format everything (exept for sd) and flash again?
Btw i love infected
Sent from my GT-I9000 using Tapatalk
Format everything? Using which app or program?
I've always used the recovery's wipe commands and the *2767*3855# command. Is that enough? or am I missing another cooler and invasive method ? A friend has suggested to use davlik.
Yeah! Infected rulz, that's what I listen when I'm in the bricking-mood lol
As i saw you have cwm installed... Boot in recovery and select mount and storrage and then select eveeything that contains format (boot wont work to format) and dont select format internal sd but DO select format sd-ext
Edit: if it doesnt work write again then ill upload u the kernel that fixed it for me yesterday. Its from this forum but since ive discovered it by coinsidence, i cant remember how its called. U can format everything then select mout usb storrage (in cwm) and push it on the root of sd. Its an update.zip
Sent from my GT-I9000 using Tapatalk
shrooms90 said:
As i saw you have cwm installed... Boot in recovery and select mount and storrage and then select eveeything that contains format (boot wont work to format) and dont select format internal sd but DO select format sd-ext
Edit: if it doesnt work write again then ill upload u the kernel that fixed it for me yesterday. Its from this forum but since ive discovered it by coinsidence, i cant remember how its called. U can format everything then select mout usb storrage (in cwm) and push it on the root of sd. Its an update.zip
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
I gave that a shot, still no cigar. I guess that it goes deeper than just a formatting... maybe that secret kernel u have might brick me... erhm! I mean help me
Shoot! and I'll try it.... this OEM sucky ROM aint working that good over the Australian ROM lol. now I lost access to my cam ! sucks.
Thanx!
Try any universal lagfix kernel with clockwork enabled. Since ur phone is still flashable and ur phone still has funktionality (cwm works) im pretty hopefull that it is software/sd format related. Thats one of those cases where servic centre sais a full flash is needed by now only they are able to do that:-( but till now i always found a way to work around that by trying everything in every way. I always thought my phone is bricked anyhow so it can just get better and by coincidence it worked all of a sudden
Sent from my GT-I9000 using Tapatalk
Ihave I900T with same rom image
and am trying to upgrade to FROYO as well. Any advice on how to do so would be appreciated. Tried the various registry hacks and none have worked. I'm happy to use Odin but not sure which is the correct ROM image to use (from samfirmware). Thanks!
zevrosenthal said:
and am trying to upgrade to FROYO as well. Any advice on how to do so would be appreciated. Tried the various registry hacks and none have worked. I'm happy to use Odin but not sure which is the correct ROM image to use (from samfirmware). Thanks!
Click to expand...
Click to collapse
Well, first thing is first. I've been a couple of weeks away from my SGS tweaking. I'm right know figuring a way to make a backup of my ROM (non-nandroid), in which I can extract the Kernel, Modem and CSC (I received a brand-new unit from my provider, so I will take advantage of it )
That way I can flash them back in case of a screw-up. I didn't have that much luck with modems offered in other ROMs, so I need to keep an OEM copy of my stuff.
Also make a good copy of your /efs folder in case you mess it up. It took me around 3 weeks of reading before I started making any changes to my phone, so I'll recommend doing the same; there's no "quick-start" or quickguide on how to start. You will en up with 6 different windows open reading from everywhere
The FWs from samfw are OEMs. Theres like "not much" of improvemente if you switch to those. Take special attention to the one you chose cause most likely you will lose your 3G and/or 850MHz band. I recommend using only Australian and Canadian ROMs(I9000UGJG8 and I9000UGJH2 worked for me, you might try also I9000UGJK3). Regarding custom ROMs, you will need to try and try until you get it right as our SGS model is not the most popular. This means endless flashing
Cheers.
Sgs froyo flash nam bands
Thanks for the advice. This project consumed my thanksgiving but I finally got a good working SGS in the ATT network. I bought an unlocked SGS from Negri Electronics with the USA 3G bands but it came without FROYO and didn't have the 3 button restore available. After reading and reading (your note about multiple open windows at the same time is all too true!) and trying and trying, I was finally able to get to download mode by installing all the Android SDK tools onto my PC then going in by way of ADB. Far more complicated than a simple registry hack and ODIN but it worked.
I installed the DOC BUJP8 v9 ROM with all the enhancements and AOSP Email (I tried and tried to get stock FROYO email to work with 2 exchange accounts but it was impossibly slow and didn't work) while AOSP is working fine.
It seems, because my SGS had the 850 bands to begin with, that it's working fine. I found this other post on XDA (#770041) that had some keycodes I was able to use (*#2263#) and confirm I still have the 850 band.
Needless to say, make a good backup and be prepared - as already warned - to flash several times and it was ultimately a "trial and error" process that worked.
does anyone have the original brazilian/latinamerican i9000T firmware? I flashed the SGS I got from Negri with spike speedy and it looks like I lost my 850 3G band.
I never did find out how to totally back up the SGS as in back up each PDA, PHONE, and CSC file so as to be able to truly factory default it.
Hi,
I am on Onecosmic 3.1, I tried flashing 4.2, after flashing 4.2 I lost phone signal, it is saying No Service. Again I went back to old 3.1 version, no problem with signal.
So, Please help what should I do to flash 4.2 version on my phone.
Edited: Thanks everyone, I made it work flashing different modem.
Thanks in Advance,
Ajay
Check imei number. Version 4.1 & 4.2 have been corrupting imei number which causes no network
Sent from my GT-P7500 using xda premium
Hmm, for me, in ICSSGS 4.2, I do have phone signal and full service, however, when I pull down my Notification bar, it displays "No service.", which, fortunately, is a lie
Thanks for reply,
So is there any solution for this?
Thanks,
Ajay
I'm a semi noob at the technical stuff, but I seem to remember that this issue can be solved by restoring the backup you have surely made of your EFS folder . This folder contains all the info about your carrier and such.
If you don't have a backup of your EFS folder, I cannot help you with my limited knowledge
Follow these at your own risk or search the forums for a more thorough explanation.
If you have made a backup use something like root explorer to look for the EFS folder in the backup & copy the two files nv_data.bin & nv_data.bin.md5. Now go to the EFS folder on the phone & paste over these to files replacing them with your backups. You can then delete nv.log, .nv_data.bak & nv_data.bak.md5. Or that is what I did and it worked.
If you did not make a backup then you would need to flash a stock rom which usually does the trick (all three files). As your IMEI appears to be fine in v3.1 I would make a backup of 3.1 & use those files. You could also copy the two files out of the efs folder and place them in your root directory then after installing 4.2 just replace the files with the ones you copied.
ajay_lanki said:
Hi,
I am on Onecosmic 3.1, I tried flashing 4.2, after flashing 4.2 I lost phone signal, it is saying No Service. Again I went back to old 3.1 version, no problem with signal.
So, Please help what should I do to flash 4.2 version on my phone.
Thanks in Advance,
Ajay
Click to expand...
Click to collapse
Many pepole who flashed RC4.1 experienced this problem, its due to the IMEI being changed to some default value. this can be fixed if you had backed up your efs folder, if not you have to reflash the official gingerbread then copy the efs folder using ROOT EXPLORER, this will fix the corrupted IMEI issue. This issue has been fixed in RC4.2 so after you get your IMEI fixed, flash RC4.2.
Sent from my GT-I9000 using xda premium
Thanks for your reply.
I will try this and let you know the result. Thanks once again.
-Ajay
I seem to have the same problem, sometimes my phone reboots, and radio is gone. When I check, IMEI-N° isn't displayed, but after some reboots its back.
I did back up the EFS Folder, but how can I stop this from happening on a regular basis?
Regards
lemalsaint said:
I seem to have the same problem, sometimes my phone reboots, and radio is gone. When I check, IMEI-N° isn't displayed, but after some reboots its back.
I did back up the EFS Folder, but how can I stop this from happening on a regular basis?
Regards
Click to expand...
Click to collapse
If you restored your EFS backup it should be ok...but since is happening many times...you can reflash a stock firmware and then flash again your current ROM.
BoBoGrEy said:
If you restored your EFS backup it should be ok...but since is happening many times...you can reflash a stock firmware and then flash again your current ROM.
Click to expand...
Click to collapse
By "backing up" you mean just copy/paste it to the respective folder?
Hello guys. This happened to me as well with onecosmic ICS RC4.2. Will be lashing back stock GB fw as I do not have an efs backup
Hi,
I have tried flashing 4.2 again and checked IEMI number, no change in IEMI number but no Network. It is saying Emergency Calls.
My phone works only in Rc1 or 3.1.
Please help me what should I do, I dont have efs backup.
Thanks,
Ajay
Hi ajay_lanki
the latest Team ICSSGS Build has a script to fix efs folder permission, which should solve the problem. Threat:
http://forum.xda-developers.com/showthread.php?t=1398223
I didn't read through the comments though, can't tell if it works!
Cheers
scubadude said:
Follow these at your own risk or search the forums for a more thorough explanation.
If you have made a backup use something like root explorer to look for the EFS folder in the backup & copy the two files nv_data.bin & nv_data.bin.md5. Now go to the EFS folder on the phone & paste over these to files replacing them with your backups. You can then delete nv.log, .nv_data.bak & nv_data.bak.md5. Or that is what I did and it worked.
If you did not make a backup then you would need to flash a stock rom which usually does the trick (all three files). As your IMEI appears to be fine in v3.1 I would make a backup of 3.1 & use those files. You could also copy the two files out of the efs folder and place them in your root directory then after installing 4.2 just replace the files with the ones you copied.
Click to expand...
Click to collapse
I have tried this, but no luck. Please help me if there is any other way.
Thanks,
Ajay
Sorry fairly new to all of this. If what I did doesn't work for you I can't help. Hopefully someone else can
The next best thing would be to flash a stock Rom of gingerbread and start again
Sent from my GT-P7500 using xda premium
First: RC4.2 doesn't solve IMEI issue, i had it with 4.1, resotred efs, it worked, flashed 4.2, and issue again.
Second: The best way to restore /efs backup is going into /efs BACKUP (not original), multiselect every file, copy, and paste in ACTUAL /efs folder. Then reboot and that's it. If no /efs backup was ever made, the only way to solve imei loss is to go back to a stock rom (wich makes your imei come back), backup /efs from there and go ahead with ICSSGS again.
fps249 said:
First: RC4.2 doesn't solve IMEI issue, i had it with 4.1, resotred efs, it worked, flashed 4.2, and issue again.
Second: The best way to restore /efs backup is going into /efs BACKUP (not original), multiselect every file, copy, and paste in ACTUAL /efs folder. Then reboot and that's it. If no /efs backup was ever made, the only way to solve imei loss is to go back to a stock rom (wich makes your imei come back), backup /efs from there and go ahead with ICSSGS again.
Click to expand...
Click to collapse
scubadude said:
Sorry fairly new to all of this. If what I did doesn't work for you I can't help. Hopefully someone else can
The next best thing would be to flash a stock Rom of gingerbread and start again
Sent from my GT-P7500 using xda premium
Click to expand...
Click to collapse
ajay_lanki said:
I have tried this, but no luck. Please help me if there is any other way.
Thanks,
Ajay
Click to expand...
Click to collapse
ajay_lanki said:
Hi,
I am on Onecosmic 3.1, I tried flashing 4.2, after flashing 4.2 I lost phone signal, it is saying No Service. Again I went back to old 3.1 version, no problem with signal.
So, Please help what should I do to flash 4.2 version on my phone.
Edited: Thanks everyone, I made it work flashing different modem.
Thanks in Advance,
Ajay
Click to expand...
Click to collapse
I've had the same issue. No matter how many times you re-flash the ROM and do FULL wipe, I wont change anything, because FULL wipe is not really "FULL", neither is Factory reset etc. For some reason it needs a "real-FULL-wipe" (Just something I made lol). Anyway you can do it following these steps:
1. Flash an NONE ICS based ROM, say JVU stock ROM .(Download it from Sammobile.com, go into download mode, and flash it using Odin 1.85 with 512 pit file)
(You are on a Stock JVU ROM now)
2. ROOT you JVU ROM. (Any method is fine but I prefer flashing Semphore kernel using Odin, just download the kernel from here, go into download mode, and put the kernel in PDA section and flash, no pit files needed for this).
(You are on a ROOTed Stock JVU ROM now)
3. Flash CM7 stock ROM. (Download CM7 stable version not a nightly version from their website, copy it to your INTERNAL SD Card, go into CWM and flash. If you had issues there just re-flash).
(You are on a stable version of CM7 that is already Pre-rooted)
4. Flash Onecosmic 4.2. (Download it, copy it to INTERNAL SD Card, go into CWM and flash, sometimes it gets stuck on a boot loop or on logo screen, go into CWM using the three buttons combo :Volume up button + Power + Home key. Once you're in CWM re-flash it again.
Do this and I will guarantee that it will solve ANY problem you or anyone else have with Onecosmic ICS 4.2.
Only problem you may encounter with the ROM is External SD card issues, which is caused by either the ROM itself or your own SD card.
A >> "thank you" would be nice . Have a good one.
Hello,
I tried searching for my problem in the forums but I didn't find my exact setup and don't want to brick my phone. (Well maybe it already is)
I had Cyanogenmod 7 for quite a while and tried the Nightlies for 9 some months ago. In the early days of my phone I used ODIN to flash the newest Stock firmwares and then used the chroot kernel to root my phone and install cwm. Since then I installed Cyanogenmod 7 and later Cyanogenmod 9 Nightlies with cwm recover and there was never a problem.
Today I tried the ROM from DerTeufel1980 http://forum.xda-developers.com/showthread.php?p=28819140
I flashed the rom, the addons, the superuser and google now fix. Then I flashed the kernel Devil3_1.0.0-Rc5_datadata_i9000_CFS_BLN_CMC_20120719.zip and fixed permissions. After that my phone wouldn't boot. The boot animation was the old standard android logo.
I managed to get into Devil Kernel Recovery and thought to try a reflash of just the ROM but when I try to "choose a zip" it always tells me
E:can't mount /sdcard/
After that I flashed the kernel with odin and now the phone seems to boot but veeeery slow and it has a ton of flickering the whole time. The bootanimation is the cyanogenmod 9 boot animation. I got into Devil Recovery and I still can't mount the sdcard. And it seems that it doesn't detect my sim card.
I hope you can help me.
Edit: Actually after rebooting several times the boot sped up and I could get into the ROM. I still can't mount the internal sdcard though and I have no phone functionality. It seems that my IMEI number is gone.
Hey
Downgrade your sgs to 2.3.6 valuepack using odin3...
Then root it and use it for a day atleast..
Then flash CM9 nightly..use that for a day too..
Then flash JB...not the same one u did earlier..
Instead Goto teamjellybean.noez.in (ad www.)
Find d latest version of jb and follow the instruction there..
Cheers
Sent from my GT-I9000 using xda app-developers app
Thanks that's exactly what I have done and it worked.
I've seen a lot of folks saying that they might have bricked their phones when some issue occured while flashing a new rom.
Personally whenever I face issues, I just goto the Download mode and Flash a GB rom and then move my way up (GB --> ICS --> JB).
As long as you can go into Download mode, shouldnt be a problem
Fwiw, I lost my IMEI for the first time trying out the JBs. Not sure if it was Slim or DerTeufel's. I ended up with the kind that allows you to connect to your mobile provider, a fake but working IMEI. But when I saw that I tried to go to GB and it didn't come back automagically. And the IMEI was totally wiped so I couldn't even register on the network. Ended up getting to ICS and only then did Root Browser let me write to the efs folder.
Lesson, in short: make a backup zip of your efs folder (to preserve permissions) and double back it up using Nitrality from the Play store.
Glad you got yours back, too.
sent from a telephonic device
tchindalia said:
Hey
Downgrade your sgs to 2.3.6 valuepack using odin3...
Then root it and use it for a day atleast..
Then flash CM9 nightly..use that for a day too..
Then flash JB...not the same one u did earlier..
Click to expand...
Click to collapse
OK, so I'm *definitely* a crappy speed-reader, because I missed this part about waiting on each version. What does the waiting do? I'm now wondering if that means I need to use the phone and, with the restored /efs folder, sometimes later /dev/block/stl3 will repopulate itself with the proper info.
Hey
I asked to wait on roms coz it can just make a few things working...like data..if it doesnt work on 1 rom it would not (probably) work on the next update..(personal experience)..
Cheers
If my post helped, don't mind hitting the Thanks button..
Hi,
I bought a Galaxy S i9000 from someone for cheap because they said it didn't work. Anyways, after getting into ODIN on it and flashing a custom rom, I got it to boot. Problem now is, I think the IMEI number on the phone is screwed up (I get a message on phone startup) and can't connect it to the cell network with my SIM card.
Is there anyway to restore the IMEI number back into the phone, so that I can get it to register properly again? Also, then unlock it?
Thanks,
colhavoc said:
Hi,
I bought a Galaxy S i9000 from someone for cheap because they said it didn't work. Anyways, after getting into ODIN on it and flashing a custom rom, I got it to boot. Problem now is, I think the IMEI number on the phone is screwed up (I get a message on phone startup) and can't connect it to the cell network with my SIM card.
Is there anyway to restore the IMEI number back into the phone, so that I can get it to register properly again? Also, then unlock it?
Thanks,
Click to expand...
Click to collapse
My IMEI got invalid too a few months ago when i flashed a custom CM10 JB Rom.
I got my IMEI back when I flashed back to GB via Odin.
Custom Rom developers advise flashing a CM9 ICS first before a Custom JB to avoid an invalid IMEI.
That's what i did, I got my IMEI back and currently using a custom JB Rom.
To unlock your phone, try to search in General Forum, there are some threads that discusses how to do it.
Yup, had the same thing with an upgrade. It's like the ROM upgrades but the IMEI bits don't.
You need to downgrade to get your IMEI back. Once you have it back DO A NANDROID!!
Then you can try to upgrade again.
It usually happens when you skip a version of android.. eg froyo to JB.
Just downgrade via Odin to stock firmware and upgrade each version in order.
Simple as that.
sent using my fat fingers from the robot eating the apple...
Well, restored to 2.3.6 and worked fine. I then installed CM 7.1 (Worked) then went to CM7.2 (Worked) and when I went to CM 9.0, it then stopped. No message about invalid IMEI or anything, just no bars.
Not sure, reverting back to CM7.2 for now.
You can try doing this process again but now backup your /efs library with Nitrality or some other /efs backup app.... make another copy of the backup in your pc and just restore it when needed...
Sent from my GT-I9000 using xda app-developers app
Before trying to flash, get into recovery and format these partitions:
/datadata
/data
/cache
and delete dalvik cache as well
Reboot phone and let's see if it starts up this time.
When you go back to gb using this app backup your imei
https://play.google.com/store/apps/details?id=com.nfye.insanity.toolbox
If someone help me i definitely HIT THANKS....
VIP1 said:
You can try doing this process again but now backup your /efs library with Nitrality or some other /efs backup app.... make another copy of the backup in your pc and just restore it when needed...
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Hi,
Tried this. I restored back to factory default image, worked.
Upgraded to CM 7.1, worked
Upgraded to CM7.2 Worked. Used Nitrality to backup /efs folder
Upgraded to CM 9.0, did not work. Restored /efs from backup. Did not work. Reboot, did not work.
So, for now it's back to CM7.2. I gave it to a friend to test out, if it works then he will be keeping it for a while and i'll try something else to upgrade it when he wants to. Thanks again for the help, seems it wants to be stubborn.
Hello,
New here and hoping someone can help me with my problem.
I've got an AT&T Captivate i897 that I put Jelly Bean on. The first time I did it, I didn't do the efs back up (the directions that I followed never mentioned it). This caused my phone to have a generic IMEI. After doing some digging, I found out that returning it to the stock GB 2.3.5 would put the correct IMEI back on the phone. I did this, and it did. I did a back up using EFS Pro 1.9.12. I then went back to Jelly Bean, hoping I could do a restore and all would be well. Unfortunately, this is where I am stuck.
EFS Pro 1.9.12 doesn't recognize the phone when I plug it in. I got the newer 2.0.26 version. This recognized the phone, but there was nothing for it to restore. I also tried using a root manager app, but there was no efs folder in there for me to put the back up in to.
If anyone could help, that would be a huuuuge help.
Thanks
If there was no efs folder, should just be able to make one and put the files inside. It's odd this only happens for some people, when I updated to 4.2.2 everything worked fine for me no efs backup etc.
But try putting the folder there anyway, reboot into recovery, fix perms, reboot. Might work (idk I've never had this problem, but putting the required files where they should be and letting the phone fix the permissions should help)
CM10 is the base of most custom ROMs. From stock (rooted and with CWM) flash CM10 and you'll see a backup of your original EFS folder on your internal SD. Check your IMEI in CM10, if good go ahead and flash your favorite JB ROM. Many custom JB ROM's require CM10 flash anyway (to create needed JB file system).
x0ne215 said:
If there was no efs folder, should just be able to make one and put the files inside. It's odd this only happens for some people, when I updated to 4.2.2 everything worked fine for me no efs backup etc.
But try putting the folder there anyway, reboot into recovery, fix perms, reboot. Might work (idk I've never had this problem, but putting the required files where they should be and letting the phone fix the permissions should help)
Click to expand...
Click to collapse
Tried this.. I think. When I plug the phone in and turn it on as mass storge, I get an F drive and a G drive. G seems to have all of the phone info on there, so I just create a folder G:/efs and unrar the backup into that?
Val D. said:
CM10 is the base of most custom ROMs. From stock (rooted and with CWM) flash CM10 and you'll see a backup of your original EFS folder on your internal SD. Check your IMEI in CM10, if good go ahead and flash your favorite JB ROM. Many custom JB ROM's require CM10 flash anyway (to create needed JB file system).
Click to expand...
Click to collapse
I used CM10 to put JB on but I don't see a back up of my original EFS.
ice_w0lf said:
Tried this.. I think. When I plug the phone in and turn it on as mass storge, I get an F drive and a G drive. G seems to have all of the phone info on there, so I just create a folder G:/efs and unrar the backup into that?
I used CM10 to put JB on but I don't see a back up of my original EFS.
Click to expand...
Click to collapse
Which ever drive is the internal sd, if you can't tell put a folder on your EXTERNAL SD named blah and which ever drive doesn't have it is the external. You also fixed the permissions after placing the folder? If it isn't properly chmod'ed, the phone may not recognize it's existence or be able to access it. Once you put the folder on the internal sd, boot into recovery and fix permissions.
Tell me how it goes.
x0ne215 said:
Which ever drive is the internal sd, if you can't tell put a folder on your EXTERNAL SD named blah and which ever drive doesn't have it is the external. You also fixed the permissions after placing the folder? If it isn't properly chmod'ed, the phone may not recognize it's existence or be able to access it. Once you put the folder on the internal sd, boot into recovery and fix permissions.
Tell me how it goes.
Click to expand...
Click to collapse
Ok, here is what I have...
G:/ was my internal sd. So I created G:/efs with my unrar'd back up put into that folder (I'd post a pic, but I'm still under the 10 post rule).
I then reboot the phone into recovery mode, went to advanced, and hit fix permissions. That did its thing, and then I rebooted the system. Checked the phone data and it still has the wrong IMEI.
I'm wondering if at this point I should just wipe it all, return to stock GB, do a back up again (any suggestions for something other than EFS-Pro for backup/restore?), and then put CWM+CM 4.2.2 back on and do a restore.
/efs is a folder in root, not in your storage. Need to use root explorer. Better go to stock to restore your IMEI.
Val D. said:
/efs is a folder in root, not in your storage. Need to use root explorer. Better go to stock to restore your IMEI.
Click to expand...
Click to collapse
Why not just put it in storage then just copy it to root with root explorer? Less work no need to reflash.
I know, but OP is not very confident what to do. Also, just restoring /efs very often won't restore phone's IMEI. The easiest and guaranteed method for him is back to stock.
Ok.. some success! I returned it to stock, did a back up, put the mod back on.. and now I've got the correct IMEI :good:
Now I am trying to take the AT&T sim card from the gophone that I bought so that I wasn't cut off from the world (the phone worked on my contract with my contract number) and put it into the Captivate, and I get Emergency Calls Only. I go into status and I get:
Network: Unknown
Service State: Out of Service
Mobile Network State: Disconnected
My phone number: Unknown
I'm guessing at this point that I just need a new sim card?
Also, thanks for all of the help so far.
Can you try this SIM on another AT&T phone?
What exactly JB ROM you flashed after stock ROM?
Val D. said:
Can you try this SIM on another AT&T phone?
What exactly JB ROM you flashed after stock ROM?
Click to expand...
Click to collapse
SIM works in another AT&T phone (Alcatel OT-510A to be exact).
I used the [NIGHTLY][ROM][4.2.2] CyanogenMod 10.1 for Samsung Captivate right from the Captivate Android Development thread.
Hmm... check what modem (baseband) version you have in Settings>About Phone. With CM10.1 it must be I9000UGKG3, I think.
Val D. said:
Hmm... check what modem (baseband) version you have in Settings>About Phone. With CM10.1 it must be I9000UGKG3, I think.
Click to expand...
Click to collapse
I have I9000UGKG3
Did you try this phone on stock ROM? Was it working with no issues? I'm out of ideas...
I'm not sure about the gophone sim, but glad to hear you got the other one working . Is your contract provider AT&T as well? If not probably would need to be unlocked for use with AT&T.
anyone else think this should be over in q/a forum