Related
finally found it after a few hours of searching +316540951000
However when I get in my phone settings and try to update or refresh my smsc # I get Refresh Error or Update Error. CDMA phone... help?
You need to be entering SMSC number in Octal-Hexadecimal format with special leading numbers, to tell android which format is that.
Basically go to (damn xda do not allow me to post links, as I am new user). DO search in google on "Online PDU Encoder and Decoder" - go to first link.
At the bottom, there is a converter for sms message to pdu format. Do the following, remove everything, except you smsc number (with plus sign) convert to pdu. Copy first 16 numbers from pdu. And enter them in your android SMSC update field. Click update - enjoy. It should be working.
Thanked
I should have thanked you years ago. I do remember getting that phone working 100%.
pelmenept said:
You need to be entering SMSC number in Octal-Hexadecimal format with special leading numbers, to tell android which format is that.
Basically go to (damn xda do not allow me to post links, as I am new user). DO search in google on "Online PDU Encoder and Decoder" - go to first link.
At the bottom, there is a converter for sms message to pdu format. Do the following, remove everything, except you smsc number (with plus sign) convert to pdu. Copy first 16 numbers from pdu. And enter them in your android SMSC update field. Click update - enjoy. It should be working.
Click to expand...
Click to collapse
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
Didn't see a "Q&A" thread for Continuum v4...
re: backing up the /EFS folder, I see the instructions link attached, looks like I have to work with adb, which I haven't done yet, I do have an app "super manager" that gives me access to data files like "root explorer".
How do I check to see if my IMEI has already changed, as I'm running Andromeda, (as there'd be no point backing up that folder if it's already differnet than original?) I guess I should look to see if the IMEI on the back of the phone matches the one in system info? I've noticed I no longer have the option in the market to purchase an app to my AT&T acct, was wondering if it might be that device info has changed.
Also, the version of Swype in Continuum is without the microphone I believe? (not a big deal, have barely used the mic)
Thanks
You can enter *#06# from the dialer and the IMEI number that the system has will be displayed.
Sent from my Cappy.
DaveyBB said:
You can enter *#06# from the dialer and the IMEI number that the system has will be displayed.
Sent from my Cappy.
Click to expand...
Click to collapse
Thanks, just looked at it in settings, system info
Hey XDA,
i have a new prob
I installed the new Helly Bean 26.08.2012 an afte start there is a warning:
"A problem was detected with your device.Your device IMEI number is invalid.An invalid IMEI number could cause network issues including the inability to call emergency numbers."
But i can call and send sms.
Anyone knows the prob?
CeeT
Your imei is invalid. Can't you read?
Sent from my GT-I9000 using xda premium
This was a problem on the Vibrant: http://forum.xda-developers.com/showpost.php?p=30644270&postcount=116
There is no efs folder!
What does it says when you dial *#06#
This is the reason why making backup of efs is important when you are on non-official roms. Flash latest gingerbread version with 3 files and re-partition, backup efs, then flash your rom again.
djceet said:
Hey XDA,
i have a new prob
I installed the new Helly Bean 26.08.2012 an afte start there is a warning:
"A problem was detected with your device.Your device IMEI number is invalid.An invalid IMEI number could cause network issues including the inability to call emergency numbers."
But i can call and send sms.
Anyone knows the prob?
CeeT
Click to expand...
Click to collapse
Imei invalid but still able to call/SMS.. Wow.. Howwzat?
Sent from my GT-I9000 using xda premium
You Must Install Stock ROM ( 3 Files ) and when you install 3 files ROM , Every things Should be Ok.
djceet said:
Hey XDA,
i have a new prob
I installed the new Helly Bean 26.08.2012 an afte start there is a warning:
"A problem was detected with your device.Your device IMEI number is invalid.An invalid IMEI number could cause network issues including the inability to call emergency numbers."
But i can call and send sms.
Anyone knows the prob?
CeeT
Click to expand...
Click to collapse
Just do a factory reset, install stock rom and all will be well. THEN backup your EFS folder and flash your new ROM.
sanguinesaintly said:
Just do a factory reset, install stock rom and all will be well. THEN backup your EFS folder and flash your new ROM.
Click to expand...
Click to collapse
You forgot something ...
Root permissions are nedded to backup the EFS folder
so
1. Install Stock Rom for your Device
2. Install Root Kernel for that Rom
3. Install Root Explorer or some other Explorer with ZIP function
4. Backup EFS folder as ZIP !!!! (cause: if you dont back up it as Zip and copy it to an Windows PC all Permissions were lost and you have to set them manually back if you restore the EFS folder)
5. Flash you Custom Rom
6. Restore the EFS backup zip ( its only enough to unpack the zip and copy the folder to the main path of your device
7. If you do it that way you have back your original IMEI
Hope I can help you
Greetz StalCaiRe
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