Database Develop

[Q] No network/service over Onecosmic ICS 4.2

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.

Struggling With ICS EFS/IMEI Restore

Hey all,
I should mention first that I have a DesireHD and have never worked with a Sammy before today.
I went about looking to root and upgrade my friends SGS.
Followed this guide and all went swimmingly.
I got my head around what ODIN is and does, what files are what and how the procedures work for Samsung phones.
ICS booted and performed exceedingly well apart from the IMEI problems.
Now, over the past few hours Ive tried everything from as many guides I could find about backing up and restoring /efs. Nothing is working.
Ive tried all flavours of ICS ROMS but they all end up with a completely blank IMEI and unknown details in the phone status menu.
If I flash back to stock GB located in the kit from the guide all is well, phone works. ICS - no IMEI.
I took several backups of /efs using RootExplorer, Nitrality and taring through ADB. The restore just not work.
I also manually fixed permissions through RE and also using ADB shell.
The only common thing is that the IMEI through *#06# is completely blank, not 0's or 049 etc, just blank.
What would be my next step from here to get it working with ICS? Have I missed something? Is it just not going to work with this particular device?
I probably wont have the phone again till next week as I left it on rooted stock GB for now so have plenty of time to dig a little deeper into the issue ut would appreciate any help.
Thanks

Hello.Ive been on ics since the beggining and at first i had no problems at all.Last couple of weeks i started to have problems with phone signal and imei.Kinda lost baseband,huge battery drain,phone shutdowns and when restarted no imei or baseband unknown.Went back to Gingerbread and all was ok despite some battery usage but my phone has 2 years and i cant ask too much of my old battery.Was kinda disapointed but today i flashed Elite rom http://forum.xda-developers.com/showthread.php?t=1621976 and for my surprise the phone handle well without loosing imei or baseband.
So my advice is to get chainfires recovery for gingerbread and then flash Elite rom.It will give you a bootloop when restarting so you have to remove the battery,get to recovery and flash the rom again. Good luck
PS- Dont forget to wipe data,cache,dalvik and system before you flash

Dude360 said:
I probably wont have the phone again till next week as I left it on rooted stock GB for now so have plenty of time to dig a little deeper into the issue ut would appreciate any help. Thanks
Click to expand...
Click to collapse
Check this out
http://forum.xda-developers.com/showpost.php?p=26827676&postcount=4512"

what to do next
Dude360 said:
Hey all,
What would be my next step from here to get it working with ICS? Have I missed something? Is it just not going to work with this particular device?
download nitrality from market restore efs then reboot worked for me
Click to expand...
Click to collapse

hullfc27 said:
download nitrality from market restore efs then reboot worked for me
Click to expand...
Click to collapse
Already tried that with no luck.
xsenman said:
Check this out
http://forum.xda-developers.com/showpost.php?p=26827676&postcount=4512"
Click to expand...
Click to collapse
Coolio, theres a couple of apps in there that I hadnt come across so Ill defo give them a try at the weekend!

*sigh*
Still no luck with any of those apps.
Im gonna try everything from scratch tomorrow using the original CWM backup I did rather than from the rooted stock I flashed from the guide.
Am I missing something here? It seems that no matter what I try it will always give me a blank IMEI.

It wouldn't be by any chance be a I9000m or b? Probably a stupid question, but you never know.
Using GT-I9000 my sent Tapatalk 2 from.

Did you backup the efs before your first flash, the procedure I have always used is root stock rom copy efs and flash custom rom. Not sure if cwm backs up efs in a nandroid
Sent from my Nexus S using XDA

adytum said:
It wouldn't be by any chance be a I9000m or b? Probably a stupid question, but you never know. .
Click to expand...
Click to collapse
I pretty sure its just a standard I9000, it was Vodafone UK branded before I got my grubby mits on it and I read a guide specifically for the M which lead me to believe it wasnt anything special. When on official GB its just says I9000 still?
thecoogster said:
Did you backup the efs before your first flash, the procedure I have always used is root stock rom copy efs and flash custom rom. Not sure if cwm backs up efs in a nandroid.
Click to expand...
Click to collapse
I only really went of this from the guide:
THIS ROM AUTOMATICALLY SAVES YOUR IMEI FOR RESTORING IN CASE YOU LOSE IT!
after seeing that I took a manual backup of it the /efs as well and every time I flashed with ODIN using the GB flash kit from the guide I checked that the phone side was working then took another backup of it then.
I have several copies of it made from the GB kit, tared in adb and several apps used to back it up.
Your right with the CWM backup though, I read a post that said /efs is a separate partition that doesn't get backup up with CWM
My thinking at the minute is that either Ive missed something related to the branding side of it. I know one DHD I did needed things like a goldcard etc as it was Orange branded or the /efs backups I have have somehow been corrupted.
Now, Im still getting used to the versioning of Samsung FWs. Its currently on
Code:
GT_I9000_XWJW5_XDJV1_OXXJVC_Sbl
is this newer or older than
Code:
CWM ValuePack XXJVU Odex/Deodexed 2.3.6 [06-01-2012]
? It works fine on the first GB one.
Im thinking of flashing the second one today with odin then trying the stock AOKP rom as it doesnt install a kernal but flash Semaphore seperately. All the other ICS roms I tried flash a kernal before hand if that could make a difference?
Man, gotta say this /efs has proper knocked me over. Im not great with non-HTC products lol

Have you tried flashing semaphore.tar from the semaphore ics thread before anything else? It's kind of an all around wonder medicine for flashing issues.
Using GT-I9000 my sent Tapatalk 2 from.

Dude360 said:
Man, gotta say this /efs has proper knocked me over. Im not great with non-HTC products lol
Click to expand...
Click to collapse
remount the EFS folder as read write
Have a look here from one of my earlier posts. It should help.
I can remember that i did have some issues in writing to the EFS folder because it was mounted as read only

still got same problem i keep losig my imei after each reboot...
it comes back if i plugin the charger...
this thing doesnt happend to me when to GB...
i went back to stock and slimICS and this still happends...
every ICS rom gives me same results...

Try this
http://forum.xda-developers.com/showthread.php?t=859914
[HOW TO] /efs Folder backup + Restore NV_DATA.BIN
How I restored the IMEI is in the penultimate post. It workes for me without no problems.

Hello
This is a guide to show you how to restore your 0 IMEI with DFS.
It has worked fine with my IDEOS X5 U8800.
1. Tools
a. Drivers for U800
http://www.sendspace.com/file/9t8no8
ttp://www.sendspace.com/delete/9t8no8/14e9692a8bd3daa4f69e0e738090d4ee
b. Software for restore
http://www.sendspace.com/file/g6thp8
http://www.sendspace.com/delete/g6th...29440decadcf6a
2. Enable debugging by USB in the settings.
In call type * # * # 2846579 # * # * http://postimage.org/image/tnj4s2dyj/
3. Go to ProjectMenu -> Background settings -> Usb port settings put the Manufacture mode and corfim.
4. Go again to ProjectMenu -> Background settings -> Qualcomm backround open settings put the background open. Password 0 and corfim.
5. Go again to ProjectMenu -> Background settings -> Log setting -> Log switch put log on and corfim.
6. Now conect your phone to pc and install the drivers.
You must see this at your device manager http://postimage.org/image/5lrm61agd/
7. Instal DFS and run.
8. Click Ports, select the port with the signature DBAdapter Reserved Interface (double click) to close.
http://postimage.org/image/3l3bmfyzr/
9. In the DM select Qualcomm.
http://postimage.org/image/6bmt1908z/
10) Press the SPC, the bottom will Device Unlocked.
11) Select Programming and in the IMEI write yours and press Write.
http://postimage.org/image/dmbp29q35/
13) Check Imei, may appear after a reboot, if not try a few more times to try to set the port speed to 115200 (box to the left of DM)
Check IMEI *#06#
As soon as the IMEI restored change:
* # * # 2846579 # * # * -> ProjectMenu -> Background settings -> Usb port settings to put on the Manufacture mode google mode (or normal if you do not get up google)
* # * # 2846579 # * # * -> ProjectMenu - > Background settings -> Qualcomm backround open settings put close
Good luck..

OK mate I know this is redundant but flash back to GB if you have efs back it up flash cm9 only cm9 not other ICS ROM then check imei is still right if not restore backup you should now be in the clear to flash other ICS and jb roms this is an issue so many people have
Sent via that ninja standing right behind you

just flash cyanogenmod 9.1.0 stable ...

restore imei Samsung Galaxy S i9000, m110s
Restore only!
Samsung Galaxy S i9000, m110s
(& may be others Galaxy S)
What you need:
1. root access
2. the ability to copy, move files to the phone.
3. about 1-2 days.
4. $ 20
INSTRUCTIONS:
1. Make quality photo sticker under the battery (with the correct imei), as well as photo of incorrect IMEI number on the screen.
Do not use Photoshop. Thus you can damage the gadget )
Short comment how you lose imei.
2. Copy the / efs from the root to sd card or other safe place.
3. From the same folder gat nv_data.bin (with broken imei) and send to [email protected].
4. After recieving corrected copy of nv_data.bin place it in the root /efs
5. Reboot your phone, check the *#06# (If something does not work, you have a backup / efs)
6. Pay $ 20 for z298613675777
7. DO NOT share your corrected nv_data.bin.

Won't boot after flashing DerTeufel'S [ROM] Jellybean [4.1.1]

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

I just cannot do a nandroid backup - help pls

Am on criskelo 11.2 with speedmod kernel 3.13.
All is fine, it appears I have root (titanium etc works) and a check with 'got root' returns an ok response.
The phone is behaving itself nicely and is nice and smooth.
The problem comes when I try and do a nandroid backup using cwm.
It gets a liitle way in and then freezes (forever!)
Things I've tried to cure this...
1) Rolling back to stock GB and then re-rooting, then full 3 wipes, then reinstall criskelo rom.
2) Rolling back to a pre-rooted GB rom, then all 3 wipes, then re-install croskelo
2) Flashing other kernels, notecore etc
3) Installing superuser 3.1.1.zip with cwm and its binary update.zip
4) Installing SuperSU app from play store - it says needs to update binaries, and when I try it just says 'installation failed!'
5) Installing superuser app from play, this time when I try and update binaries it does helpfully say ' remounting /system as rw... fail!'
which leads me to believe this is a root problem, even though no other app is complaining.
6) doing a search on this forum (before you all tell me to do this!)
I have been trying to solve this for over a week now, and it feels like I have read everything on this forum but I may have missed something.
Can anybody steer me in the right direction please?

Maybe you dont need a nandroid backup, it doesnt backup efs anyway.
Could be a kernel issue, or space issue. Not sure.
Sent from my GT-N7000 using Tapatalk 2

baz77 said:
Maybe you dont need a nandroid backup, it doesnt backup efs anyway.
Could be a kernel issue, or space issue. Not sure.
Click to expand...
Click to collapse
Cheers, you might be right, but I have always used nandroid before flashing a new rom,
may I ask what you use to backup then, when you change rom?

jonnybruce said:
Cheers, you might be right, but I have always used nandroid before flashing a new rom,
may I ask what you use to backup then, when you change rom?
Click to expand...
Click to collapse
Have you tried updating cwm? I believe older versions had this problem.
Sent from my GT-N7000 using xda premium

SpyderTracks said:
Have you tried updating cwm? I believe older versions had this problem.
Click to expand...
Click to collapse
No I haven't Spyder, although I have tried a few different roms whic all have differing versions of cwm right?
which one is the latest then, and how do I install it, would it be an update zip?

jonnybruce said:
Cheers, you might be right, but I have always used nandroid before flashing a new rom,
may I ask what you use to backup then, when you change rom?
Click to expand...
Click to collapse
I am a heavy flasher and prevent issues caused by restores to get a clean taste of roms. Nandroids I tried, but I havent found a rom I wanted to go back on always, flash so much that it just takes to long.
Efs with a tool in one if my threads, suggestion by Chasmodo. DrKetan has a good toolbox thread in general section.
I manually backup photos and such with a file explorer. Calander/Contacts/email in gmail,
whatsapp and special app stuff also manually transfer folder from sdcard and back.
Messages I dont care for. Neither made calls list.
Occasionally I do restore app if dissapeared from market with Titanium, but only app, not data. I save backups on external. Cause I clean sdcard also.
Sent from my GT-N7000 using Tapatalk 2

jonnybruce said:
No I haven't Spyder, although I have tried a few different roms whic all have differing versions of cwm right?
which one is the latest then, and how do I install it, would it be an update zip?
Click to expand...
Click to collapse
The latest version for Note N7K is 6.0.1.2.. chek the below link... download option is there
http://www.clockworkmod.com/rommanager/

jonny, i feel your problem is due to partial root.
could you copy files into system in root explorer ?
did adaway work in applying hosts file ?
for criskelo rom too you should choose CF root kernel during the flashing process, then later you may change to your preference

Thanks baz & nokia, much appreciated.
I am running PA 1.99 now and it has the new cwm (you can tell because it has a grey background now!)
And rraaka, you are correct, I cannot copy anything to system
Not sure how I can get full root back though, I have used Dr Ketans rooting tool many times to try and cure this issue as well as flashing pre-rooted GB roms with Odin.
Not sure what else I can do.
But am starting to agree with baz now, I can do without nandroid (it takes ages anyway) and just use titanium to restore.
Everything is working fine with my partial root (except nandroid) anyway so not sure I care anymore!
Am enjoying Paranoid Android by the way, JB is fun.
I do miss the samsung apps though, I don't suppose those have been jellybeaned yet??

nope not yet, nothing Touchwizz like spen etc.
There is a cwm flashable of samsung apps that works pretty good on cm9, not sure if it works on cm10 or jb.
gaining full root shouldnt be to difficult, update binaries and then you know for sure.
The one that has worked wel for me is the ssu only zip from this post but then again thats on stock stuff.
http://forum.xda-developers.com/showthread.php?t=1841288
For custom roms/kernels the ones supplied with it are build in to work out of the box.
Once fully clean install, a nandroid can work but thats fully clean
Sent from my GT-N7000 using Tapatalk 2

Thanks baz, am going to go back to the start (stock ICS) and try that link to try and get my full root back, looks interesting.

Ok, I have full root again now!
here's what I think I remember what I did...
Downloaded the first two Su & busybox zips using method1 on the link that Baz kindly shared with me and popped them on my sd card ready.
http://forum.xda-developers.com/showthread.php?t=1746794
Downloaded and flashed the latest UK Carphone Warehouse stock ICS rom with odin.
Rebooted to stock recovery - applied update zip - flashed first the SU and then Busybox zips downloaded earlier.
Rebooted phone to check all was ok.
Located superSU app and ran it to check - and first it said it didn't recognise my phone model, hmmm...
So I downloaded mobile odin from play and flashed abyss 4.2 kernel
Rebooted to recovery, full 3 wipes and rebooted system.
Ran superSU again and magically it updated binaries and for the first time in 2 weeks it said 'sucessful', I was very pleased!
Rebooted to recovery and flashed Criskelo 11.2 again (have gone back to this from PA until things are a bit more stable)
Restored all my apps from TB all good.
Checked Adaway and it was more than happy to replace host file, and root explorer is also happy.
Cool

[Q] ESF Issue after putting on 4.2.2

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