Related
Thanks to the good folks here i've just upgraded my Galaxy S to the leaked JPM firmware. So far so good - much faster than JPK I was on.
However - I'm having problems with the Appbrain Fast Web Installer and seem to have found out that it's due to the android device ID being the same because we're all using the same ROM (or something) (http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=798644)
So.... How can I find out what my Device ID was/should be and how can I then change it to be "correct".
Any help much appreciated. Seems it might be a common issue....
Have you tried checking whether your IMEI changed after flashing? Type *#06# and if your IMEI starts with 0049... (I think...) then you need to do what almost everyone has been doing since JPC ... follow the instructions from here or some other threads from around here.
If your IMEI is fine, then I have no idea...
nonreviad said:
Have you tried checking whether your IMEI changed after flashing? Type *#06# and if your IMEI starts with 0049... (I think...) then you need to do what almost everyone has been doing since JPC ... follow the instructions from here or some other threads from around here.
If your IMEI is fine, then I have no idea...
Click to expand...
Click to collapse
Thanks for info - checked my IMEI and it seems to be fine - i.e. the one i registered with my insurance with (starts 3547)
I've read the thread you linked to trying to figure out what's what but I can't see anywhere how to find out what my product code is/was/should be or how I can change it. I've seen stuff about backing stuff up (nv_data?) but I'm not aware of having changed these.
All I've done to my phone - flashed JMX and now JPM and applied SuperOneClickv1.4-ShortFuse root. Will that have changed my product code?
I'm a bit lost with this one.
Use sgs toolbox to see the crc code.
Sometimes you got the right code in the backup file.
Just do a backup of all file on a safe place. The remove the 2 original file. Restart.
You need to be rooted for this.
Sent from my GT-I9000 using XDA App
DamianGto said:
Use sgs toolbox to see the crc code.
Sometimes you got the right code in the backup file.
Just do a backup of all file on a safe place. The remove the 2 original file. Restart.
You need to be rooted for this.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
A bit of info that might help(?):
I loaded up SGS toolbox and pressed ""check product code" it says:
---------------------
Got root access
Copied nv_data files...
nv_data.bin could not be read!
No backup .nv_data.bak found!
-----------------------------------------
I'm guessing that's bad news?!
Under Firmware Info it says:
------------------------------
PDA: I9000XXJPM
PHONE: I9000XXJPM
CSC: I9000OXAJPM
Build Info: 2010. 10
--------------------------------------
When I tap CSC selection it says: "USSD code running" and then "UNKNOWN APPLICATION"
When you say to backup 2 original files - i'm guessing it looks like I don't have those. Is there another way I can check or is it definite from the above. If I don't have the original files am I stuck? Can I get them from anywhere else? Are they default to a phone by region or carrier (my phone is from O2 in the UK and is the 8gb version)
If you say delete the original files (which aren't there it seems) - am I right in thinking this will them make the phone auto-generate new ones? (I really have no idea what these files are for or what they do).
What's the next thing to try? Can I get hold of the missing files from somewhere? Do I even need them? And how do I restore the Product ID (if it's changed!)?
Thanks
Have you checked the path manually for them?
If they are not there you are in deep water.
Its you personal data for the phone and you can't use others file.
Search this forum for help about this.
I can only give you a advice what i would do if i had that problem.
I would flash a original firmware that is lower than its on kies.
Then i would upgrade thought kies.
Then i would check if the crc code is there and right.
If it still wrong then i guess i would make the phone look like it was out of the box and return it.
If the code is right i would make a backup(full) and on this files( to my external sdcard).
Then i would upgrade to jpm/jp6.
Sent from my GT-I9000 using XDA App
DamianGto said:
Have you checked the path manually for them?
If they are not there you are in deep water.
Its you personal data for the phone and you can't use others file.
Search this forum for help about this.
I can only give you a advice what i would do if i had that problem.
I would flash a original firmware that is lower than its on kies.
Then i would upgrade thought kies.
Then i would check if the crc code is there and right.
If it still wrong then i guess i would make the phone look like it was out of the box and return it.
If the code is right i would make a backup(full) and on this files( to my external sdcard).
Then i would upgrade to jpm/jp6.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Hi - thanks for reply
I've checked the /efs folder with Root Explorer and it seems i've got:
.android - folder
.nv2.bak
.nv2.bak.md5
.nv_data.bak
.nv_data.bak.md5
.nv_state
/imei - folder
nv_data.bin
nv_data.bin.md5
Now i'm guessing this is good? is it all in the right folder?
Just to clarify - I've never messed with this folder - I've only ever flashed with Kies and cleared the cache and restored factory settings with recovery. I've also formatted internal and external memory card.
So are these files my original files? How can I tell? Are these included with the Rom's I've flashed? (JPK and now JPM)
I've copied the entire efs folder to a safe place - is there anything else I should backup also incase I can't restore it?
SGS toolbox still says:
---------------------
Got root access
Copied nv_data files...
nv_data.bin could not be read!
No backup .nv_data.bak found!
-----------------------------------------
Why can't SGS toolbox read the files?
Many Thanks
Maybe I am not following this thread correctly, but your last post deals with IMEI and unlock data. Your first post said you needed to change your deviceID. You even link to the Captivate thread that discusses the problem AND in that captivate thread is a link to change Device ID - http://forum.xda-developers.com/showpost.php?p=8604909&postcount=3550
review that post as it tells you where your device ID is located (it is not in the nv_data.bin file). Also, in the captivate thread, one person said he just made one up and that worked for him.
If you mess up with nv_data.bin you will mess up your IMEI and any unlock the phone has - so I caution you be careful.
I made a thread with the solution
http://forum.xda-developers.com/showthread.php?t=815503
This should work.
alsheron said:
Hi - thanks for reply
I've checked the /efs folder with Root Explorer and it seems i've got:
.android - folder
.nv2.bak
.nv2.bak.md5
.nv_data.bak
.nv_data.bak.md5
.nv_state
/imei - folder
nv_data.bin
nv_data.bin.md5
Now i'm guessing this is good? is it all in the right folder?
Just to clarify - I've never messed with this folder - I've only ever flashed with Kies and cleared the cache and restored factory settings with recovery. I've also formatted internal and external memory card.
So are these files my original files? How can I tell? Are these included with the Rom's I've flashed? (JPK and now JPM)
I've copied the entire efs folder to a safe place - is there anything else I should backup also incase I can't restore it?
SGS toolbox still says:
---------------------
Got root access
Copied nv_data files...
nv_data.bin could not be read!
No backup .nv_data.bak found!
-----------------------------------------
Why can't SGS toolbox read the files?
Many Thanks
Click to expand...
Click to collapse
I had the same problem.
I installed Busybox from the App Market and it solved the problem.
abumuqaatil said:
I had the same problem.
I installed Busybox from the App Market and it solved the problem.
Click to expand...
Click to collapse
thanks...had same problem and that solved it
Unlike other cases posted previously...
All files in efs were deleted, including all hidden .bak files
Now, kies displayed my phone have a product code of XXXXXXXXX and a fake IMEI...
Is it possible to restore the nv_data.bin and other files??
Please help! Thanks....
I have the same problem, is there a solution for that?? Please answer!
Did you install sgs toolbox and used it's check product code function before you deleted your efs? If yes, there is still a chance. If no, there are currently no public fix available yet.
Sent from my GT-I9000 using XDA App
We are on the same boat, as what francis posted. No public fix yet but pretty sure there will be.. its just a matter of time.
the same thing happened to me yesterday when i flashed Cyanogenmod 7, got fake imei but everything worked just fine (call, data, market).
today i deleted everything from efs folder using Root Explorer then installed i9000XWJS5 then, surprise, i got my original imei back.
do not know how and do not know if it will work on you but it worth a try
The same thing happened to me.
If I dial *#06# no imei appears.
In order to use the phone everytime I boot up I have to give r/w permission to system folder. Otherwise it doesn't recognize the sim card.
It seems to me that that the device is not anymore able to recognize itself.
If I try to install CM or other AOSP rom I have status 7 error.
In Rom manager I have a window where I should select wich kind of device it is.
In fastweb installer there is a list of devices and I have to choose wich of them I am using.
I know that there is nothing to do with warranty. But is it possible to go back to a stage where it is possible to install AOSP rom?
Thanks
don't know it may work or not, but some custom roms make a backup of the efs folder on sdcard under /sdcard/backup/efs or /sdcard/backup/efs-XXX
(XXX= some numbers). you can try to restore it from there.
again don't know for sure...
Normallary Not
hellboy2703 said:
don't know it may work or not, but some custom roms make a backup of the efs folder on sdcard under /sdcard/backup/efs or /sdcard/backup/efs-XXX
(XXX= some numbers). you can try to restore it from there.
again don't know for sure...
Click to expand...
Click to collapse
Thanks.
I have checked, but there is no backup.
I know the only one to blame it's me.
Do you think that there is anyway to make possible installing AOSP rom?
Watch out! That guy below me is spam! (User @yankee86)
So. my IMEI is jacked up. I made a copy of /efs when I got the phone but instead of making an archive I did a straight copy, Seems like the fat filesystem owned the permissions.
I am trying to restore from that backup but I am not having luck. People say you can just drop those files into place but it seems that they are replaced after every reboot. What do the permissions need to be? I see that ownership needs to be 1001:1001. Also, can I do this on JH7 with any success?
If your flashed back to stock OTA JH7? Shouldn't need to have to restore them.
Only need to input that (if Android ID doesn't work) - you should be able to copy it using ADB shell and SU.
cp /dir/foo /dir/newfoo
I used the CWM flashable zip to get back to JH7, didn't use odin (im not at home yet, and this was eating away at me at work, heh).
Ill flash back with odin and then see where that gets me. For my own sanitys sake, could you tell me what the permissions are on your files in /efs?
i have a fix that worked for me posted in the dev section
bames said:
i have a fix that worked for me posted in the dev section
Click to expand...
Click to collapse
Hmm..my product id is correct (...AATT). Maybe my current files are only half borked. Ill try restoring to jf6 with odin and see where I get. Thanks for the reply
z28james said:
Hmm..my product id is correct (...AATT). Maybe my current files are only half borked. Ill try restoring to jf6 with odin and see where I get. Thanks for the reply
Click to expand...
Click to collapse
once in jf6 if your imei isn't corrected then delete everything but the nv_data.bin and .nv_data.bak.md5.
use android terminal emulator to execute following (must have busybox installed)
su
busybox chown 1001:1001 /efs/nv_data.bin
reboot
avgjoegeek said:
If your flashed back to stock OTA JH7? Shouldn't need to have to restore them.
Only need to input that (if Android ID doesn't work) - you should be able to copy it using ADB shell and SU.
cp /dir/foo /dir/newfoo
Click to expand...
Click to collapse
fyi android id is different than the device id. Device ID = IMEI.
I see my problem, the efs directory I have is from my OLD captivate. Arrrg....I have no backup of my current /efs. The random nv_data.bin it creates has the correct product code already.
There must be something in the phone that knows the imei as this is why it was not accepting my dropped in files (the files from my old phone).
Ah well...ill use it till ATT blocks the test IMEI "lose" mine and go get a refurb as I have insurance.
FYI, the stock original firmware does not create those .bak files from what I could see. I bet your files had jacked product IDs but perhaps the part that went with your IMEI was still intact. This would be why my phone wont accept my old phones nv_data.bin?
once your in stock
run the terminal emu commands you should have baks once your system reboots.
I can delete my baks
run the term commands reboot and they will generate again.
if you have both bin.md5 and bak.md5 delete the bin and run terminal commands.
bames said:
once your in stock
run the terminal emu commands you should have baks once your system reboots.
I can delete my baks
run the term commands reboot and they will generate again.
if you have both bin.md5 and bak.md5 delete the bin and run terminal commands.
Click to expand...
Click to collapse
None of those files get generated for me or exist. If I remove everything, a generic nv_data.bin and .imei get created. Thats it. If I copy over the files from my old captivate, I believe they do get created but since the IMEI in that file does not match whatever is being checked in the phone, new files are created anyways.
I suppose nobody as of now knows how to generate the string that is in the nv_data.bin based on an IMEI so it seems that I am out of luck.
Perhaps some shady place in town can help me repair the IMEI or something
I ended up calling Samsung today. I described the problem (damaged IMEI) and they sent me a pre-paid shipping label to send it off to Plano TX to have them take a look (i'm in Austin).
I will let you guys know how this turns out.
My phone is on its way back to me. They ended up swapping the mainboard under warranty.
I suppose if you have a damaged IMEI and can deal with using an old phone for a week, consider sending it over to samsung.
did you have to pay for new mainboard? cause i got the same problem but i am not the orginal owner for the phone.
Jeez, that's wild. What is the correct way to go about backing up the necessary information while the phone is still stock? Planning on rooting (but not unlocking) my gf's Captivate and want to make sure I leave a proper trail of breadcrumbs.
Phateless said:
Jeez, that's wild. What is the correct way to go about backing up the necessary information while the phone is still stock? Planning on rooting (but not unlocking) my gf's Captivate and want to make sure I leave a proper trail of breadcrumbs.
Click to expand...
Click to collapse
It was no cost. They could see based on the IMEI that it was still in warranty. My mistake is I forgot to make a backup of /efs. If you make a backup before doing the OTA update, the unlock code in in clear text
z28james said:
It was no cost. They could see based on the IMEI that it was still in warranty. My mistake is I forgot to make a backup of /efs. If you make a backup before doing the OTA update, the unlock code in in clear text
Click to expand...
Click to collapse
So just back up that efs folder and that's it? Anything else?
This phone was purchased used on Craigslist so I don't there's any warranty remaining. It's a 1007 so it's older...
Phateless said:
So just back up that efs folder and that's it? Anything else?
This phone was purchased used on Craigslist so I don't there's any warranty remaining. It's a 1007 so it's older...
Click to expand...
Click to collapse
Well, the warranty period is a year and so since its been less than a year since the captivates release, you should be good. It would seem the only way it would be out of warranty would be if samsung for some reason deemed it to be at some point. Im sure you could call samsung with the IMEI and verify.
In my case, my product ID had become damaged. My problem is although I had a backup of /efs, it was for my first captivate, not my current. I deleted /efs and moved the backup into place. Seeing that it was the nv_data.bin for some other phone with another IMEI (the IMEI is encrypted inside that file) it instead replaced the files with a generic set of files and the dreaded test IMEI.
Since nobody had a good way to write the IMEI to that file as it expects, I was SOL.
If I could do it again, I would make a .99 cent jig (I did this using a wonderful thread here labeled something like "make a jig without cutting up USB cable) which gets you into download mode if odin or something soft bricks your phone, root, make a backup of /efs and then take a nandroid backup. I THINK I remember reading that sgstools can backup /efs for you but in the sticky there is a method on how to make a .tar of /efs (good as this will retain permissions/ownership as if you straight copy them to the sd card with fat32, the filesystem does not understand linux permissions and blows them away).
Master-Clear did the trick 4 me
OP I had the same exact same problem here. I spent many hours looking for a fix, N/G, nothing I tried would work. Didn't want to go to AT&T so I took a big chance and went into the efs folder and started deleting files one at a time. When I was through the efs was empty, did this with Root Explorer. When I did a reboot I wound up with a different IMEI, had NO data connection, NO APN, but wifi worked fine. I then did a factory reset from CW which did nothing, still no data connection. More time down so I loaded up ODIN3 One-Click and did a Master Clear. This was the last thing I was going to try before a trip to your friendly AT&T store. Well low and behold after the Master Clear and a reboot everything is back to normal! My IMEI is correct, APN is back, 3G working, wifi working. TITS! What a rush!
TommyZee said:
OP I had the same exact same problem here. I spent many hours looking for a fix, N/G, nothing I tried would work. Didn't want to go to AT&T so I took a big chance and went into the efs folder and started deleting files one at a time. When I was through the efs was empty, did this with Root Explorer. When I did a reboot I wound up with a different IMEI, had NO data connection, NO APN, but wifi worked fine. I then did a factory reset from CW which did nothing, still no data connection. More time down so I loaded up ODIN3 One-Click and did a Master Clear. This was the last thing I was going to try before a trip to your friendly AT&T store. Well low and behold after the Master Clear and a reboot everything is back to normal! My IMEI is correct, APN is back, 3G working, wifi working. TITS! What a rush!
Click to expand...
Click to collapse
Do you know where I can find this ODIN3 one-click and how to do a master clear?
I created a custom Rom, a really great mash up for people that like certain things from eugenes R2 final and Nero using KA6 while also implementing a very nice stock look (stock gingerbread messaging, dialer, contacts)... calling it Frankenstein. I of course will give credit and am not taking any credit away from these real great devs... this is just a mash-up.
This is where I need my [Help] while doing this, testing on my vibrant etc. I have managed to mess up my market.... my phone started off by not being able to connect (data) at all, and only having basic phone ability (mms, callling out).. I have fixed that, but no matter if I odin back to stock, do the eugene froyo odin/reformat back to jfd.. the market will not update. No apps really whatsoever... I get more apps when going to a rom like Nero V5 vs. stock JFD.. so this tells me that I am getting the market the way it was when they were implemented into the roms? but even with nero v5 im still missing a great deal such as titanium backup, file managers... even little things like doodle jump....
anyone that can provide detail that leads to a fix i will happily donate $15 via paypal, no big deal.
files must be missing, would love help.
Edit: have tried clearing data, resigning in.. all the little things... and as i said i have flashed back to jfd... now im on jfd with apps such as firefox test.. and a bunch of apps that were most likley the first apps ever put on market.. this puzzles me.
Thanks, Brandon
the only featured app right now is auto focus snake.. which looks like a android test app...
http://www.google.com/support/forum/p/Android+Market/thread?tid=55c997eccabf0a6a&hl=en&start=40
seems to be an issue with SGS devices and the market? WTF
Attached is a copy of the vending.apk I've been using in my kangs, and haven't had a problem with it. It shows all apps, on my phone its updated by now, but if it isn't when you push it, it should update properly given a little bit and a reboot. I would say if this doesn't fix your issue, it may be something else in your build. Just push the file to the system/app folder in your build, reboot and test it. Or, copy and replace the vending.apk in your working files, recompile and flash your rom, and test it. Good Luck.
so, select section you want, select free or latest or whatever, and you will see them.... or just search for the app you want
IMEI issue
I had the same issue all test apps in market and really no access.
I had to restore my backup and relock the phone.
Now all is working.
It is because certain apps don't recognize the Vibrant's build number. (T959KA6 is an example of a build number)
Sent from my SGH-T959 using XDA App
No I flashed back to stock tried Nero 5. Nothing helped had to restore nvdata. Imei was something like 004 phone was unlocked and tested on ATT. Look when you go into the market and it popup saying phone kay not support the market. Tried multiple google accounts its linked to your google account and your imei for supported apps on your type of phone.
Sent from my SGH-T959 using XDA App
saintjmf said:
No I flashed back to stock tried Nero 5. Nothing helped had to restore nvdata. Imei was something like 004 phone was unlocked and tested on ATT. Look when you go into the market and it popup saying phone kay not support the market. Tried multiple google accounts its linked to your google account and your imei for supported apps on your type of phone.
Sent from my SGH-T959 using XDA App[/QUOTE
there we go, my imei starts with 004 too, and is not my original imei.. what is the easiest way to restore my files? if you could give step by step that would be great! thanks mate.
Click to expand...
Click to collapse
You have to have a backup copy of your original.
If you do delete the files that start with nv -- in the /efs directory.
You probably can see your original IMEI if you open the file that is hidden in the directory /efs it is .imei -- That held the correct number for my IMEI. not sure if someone knows how to use that if you dont have an original backup of nvdata.bin.
I took nvdata.bin and put it in the /efs directory.
removed all files that start with nv in /efs example nv2data.bak
rebooted phone it built md5 from nvdata.bin.
factory reset and all apps back.
I also coudlnt get my pro license of titanuim backup to register with google checkout until this was completed.
saintjmf said:
You have to have a backup copy of your original.
If you do delete the files that start with nv -- in the /efs directory.
You probably can see your original IMEI if you open the file that is hidden in the directory /efs it is .imei -- That held the correct number for my IMEI. not sure if someone knows how to use that if you dont have an original backup of nvdata.bin.
I took nvdata.bin and put it in the /efs directory.
removed all files that start with nv in /efs example nv2data.bak
rebooted phone it built md5 from nvdata.bin.
factory reset and all apps back.
I also coudlnt get my pro license of titanuim backup to register with google checkout until this was completed.
Click to expand...
Click to collapse
i do have a back up of my efs folder thank god. what program did you use to access your efs folder is what im saying? not sure if i have access to adb commands on this machine that i am using, any other way?
and remember i cant use market, so if someone can maybe provide a program to navigate my phone files from my pc, i can just put back in the nv data
I used root explorer
Sent from my SGH-T959 using XDA App
Can I flash this with clockwork mod? And does the voodoo kernel and sounds work with this?
I created another thread about this as I believe there maybe alot more users with this issue
Sent from my SGH-T959 using XDA App
whit this program you use to access your efs folder
http://www.mediafire.com/?c8x8wvpc9vhcd5x
shon yakobi said:
whit this program you use to access your efs folder
http://www.mediafire.com/?c8x8wvpc9vhcd5x
Click to expand...
Click to collapse
said this version is expired, need to update manually?
saintjmf said:
I used root explorer
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
do you know if there is a rom out there that has this preinstalled? remember i cant get apps because of that market.
The problem [might] be inside the build.prop.
Try changing:
Code:
ro.build.fingerprint=Samsung/SGH-T959/SGH-T959/SGH-T959:2.2/FROYO/UVKA6:user/release-keys
to
Code:
ro.build.fingerprint=Samsung/SGH-T959/SGH-T959/SGH-T959:2.1-update1/ECLAIR/UVJFD:user/release-keys
total commander
whit this program you use to access your efs folder its ok no problom
http://forum.xda-developers.com/attachment.php?attachmentid=494485&stc=1&d=1295487965
IMEI
You're IMEI can easily be found by just taking out your battery and looking under it at the sticker with all the numbers and bar codes. It may just show IME and have either dashes or periods (you can ignore the punctuation). That is your original IMEI (this is nothing more than your serial number, make sure you know what it is because if you ever have a hardware issue and want to still utilize your warranty then they check by this number, and of course unroot the phone first so it won't be considered out of warranty)
Hello guys, a friend of mine just gave me his phone because "it has got a problem" he said. He just flashed a ROM from CMW, but he noticed that there was no service. the problem is that, if I dial *#06# there is the CORRECT IMEI, but if I search for the EFS folder, there is no trace of it. how is this possible? the IMEI shown in the phone also corresponds to the IMEI wrote on the back of the phone... so it's clearly correct. how this could be possible? I tried adding manually the EFS folder using root explorer (and mounting it as R/W), but after the reboot the phone automatically delete the folder I created.. any idea? thank you!
blak24 said:
Hello guys, a friend of mine just gave me his phone because "it has got a problem" he said. He just flashed a ROM from CMW, but he noticed that there was no service. the problem is that, if I dial *#06# there is the CORRECT IMEI, but if I search for the EFS folder, there is no trace of it. how is this possible? the IMEI shown in the phone also corresponds to the IMEI wrote on the back of the phone... so it's clearly correct. how this could be possible? I tried adding manually the EFS folder using root explorer (and mounting it as R/W), but after the reboot the phone automatically delete the folder I created.. any idea? thank you!
Click to expand...
Click to collapse
Look in My Android Solutions
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
nothing worked for me.. I tried to flash an earlier version of android, gingerbread, and the EFS folder was recreated but was incomplete. there were no "imei" folder into efs folder, and also there were no nv_core.back files, ecc... despite this, the IMEI number was shown correctly in the phone, but no signal/data... :S
blak24 said:
nothing worked for me.. I tried to flash an earlier version of android, gingerbread, and the EFS folder was recreated but was incomplete. there were no "imei" folder into efs folder, and also there were no nv_core.back files, ecc... despite this, the IMEI number was shown correctly in the phone, but no signal/data... :S
Click to expand...
Click to collapse
Have you tried restoring the original firmware and checked? If not you should do that.
http://forum.xda-developers.com/showthread.php?t=1102881
:fingers-crossed:
no network service issue with jelly bean
I have a similar issue here.
First of all I flashed usin this guide:
thehelptimes.com/install-jelly-bean-on-galaxy-s-i9000-how-to-official-rom-android-4-1
provider is congstar (T-Mobile reseller)
*#06# gives me the correct IMEI
/efs folder exist
/efs/imei too
I tried killing the nv_data.bin in order to have the phone recreate it. That happened, now the phone asked for a pin at reboot but the pin doesn´t get
accepted. It also doesn´t get locked after 3 attempts. It just doesn´t get accepted.
Then I noticed that the rights of the nv_data.bin are different than the other files. I changed that but it got changed back after reboot and the pin still isn´t accepted.
I have no idea whats wrong. Next attempt back to gingerbread :-/
EMnEL said:
Have you tried restoring the original firmware and checked? If not you should do that.
http://forum.xda-developers.com/showthread.php?t=1102881
:fingers-crossed:
Click to expand...
Click to collapse
yep I tried restoring gingerbread, and, as I said, the phone created the efs folder, but it was incomplete... there were no IMEI folder, other folders were missing, and there were NO nv_data.bin files. I tried reflashing jelly bean and the efs folder was, again, completely missing...
Alright, I am gone back to XJVP but this wasn´t much help.
No signal either.
IMEI still shown by dialing *#06#
as of forum.xda-developers.com/showpost.php?p=26827676&postcount=4512
I need to get into root to kill the efs folder.
So I am back to XXJVU (gingerbread) now to get it rooted.
Before root there is still no network yet but I still can display the IMEI 3547.... (which is listed in the settings too).
Alright now I am going to root it. Hope this helps somehow.
I have the strong feeling that this phone ends up as a mp3/mp4 player
UPDATE....
- Alright, according to this I better not kill the efs by ODIN ? I didn´t yet. forum.xda-developers.com/showthread.php?t=1114958
- I checked the efs folder and noticed it is pretty much holding the same content as
in an efs offered for download "i9000 358001043596739 efs.rar" at 199.91.153.60/pa6q9c9bboog/eyyse638dh3kncn/i9000++358001043596739+efs.rar
So it looks pretty much like it should, I can see my perfect IMEI but it still doesn´t work. I am lost. No clue.
Back in my I9003 the SIM just works perfect so it is obviously not an issue of the SIM
UPDATE 2...
- flashed back to XXJP1 Froyo which was a bad idea now the IMEI is empty - F**K!
- going back to XXJVU now
UPDATE 3...
- Back to XXJVU still no signal however it detected at least T-Mobile at boot and gave me a radio box to select T-Mobile.
Sometimes the signal strength shows one bar (two bars when I am going to the window that points in direction of the sender)
though it should be fairly more here as other phones proof. No matter what that means anyway it says there is no service.
UPDATE 4...
- Compared the mobile settings with the i9003 and noticed that the i9003 shows EDGE, the i9000 GPRS
Alright, I got it back to GT_I9000_XXJQ3_XXJPY_DBTJS2 and made an official upgrade to the latest stock via KIES then. Nothing better.
I assume thise phone got a hardware defect then. Even though it doesn´t seem too logical